In the last year I've been responsible for several crucial tasks which impact
the Pipeline team and MPC as a whole.

Notables:
- Created a GeoCache swapper tool that saves artist-time

  15 minutes x per-geocache x shot x job

  Take the Sour patch kids jobs. If we assume there are 6 sour patch kids on
  screen at once and 5 shots per commercial (and there's been 2 jobs in recent
  memory), that's 15 hours of time saved. And we can now use this tool on every
  job forever. It'll have massive savings now and into the future

- Prepped several repositories for ion / Maya 2018
- Refactored lightingtools for the first maya 2018 build
- Improved the speed of Maya camera publishing. In one measured case taking
  a publish time from 16 minutes down to 50 seconds
- Created a centralized logging system that all of MPC now uses
- Redefined our dependency tracking rules for ftrack assets, which can now be
  used to build other tools (example: a tool I also wrote, ftrack_dependencyViewer) which were otherwise impossible to do.

Additional task breakdown:
- Created FtrackRead, the node which is used by Nuke compositors to interface
  with ftrack
- Built a geometry and rig asset checker for Maya, which contains over 20
  quality-assurance checks to make sure assets are published correctly
- Added blg.exr support for Nuke

This work is done on top of the tools that I regularly maintain as well as
support tickets.

Ion migration:
	And if I can speak to MPC's Pipeline as a whole for a moment, the ion migration
	was a huge undertaking that involved everyone on the team. Before most of the
	team began work, I took on the task of fixing our largest repository called
	"tvcTools" which had several problems which affected several repositories. The
	extent of the problem was only really known until after I took the task but I
	did it because I had a feeling that things were worse than we thought.

	And as it turned out, that's exactly what happened. The work was hard but I'm
	glad I took the initiative because I'm confident we would not have gotten a
	Maya 2018 build out for January 2018 if we had to make changes to tvcTools
	while the rest of the team made their changes to the other repositories.

General Pipeline Overview:
	Looking towards the future of MPC pipeline a bit, until recently, jobs had been
	set on a pipeline environment that was several months behind what the rest of
	the team had written.  As of writing, we are only 3 months behind the latest
	build (as opposed to several). Once more jobs have tested our most recent beta,
	MPC will be completely caught up to the changes Pipeline has been doing.
	I've made it a personal mission of mine to get all of MPC on the most recent tools.

What's Next:
	The last aspect of our CG pipeline that still needs to be ported to ion,
	our rigging tools, was recently assigned to me to do.
	I cannot wait to finish this so that MPC CG can finally move to Maya 2018!