Changes

* Naomi Dushay, Stanford University Library, ndushay@AT stanford.edu* Bess Sadler, Stanford University Library, bess@stanford.DOT edu(as mouthpiece for multiple contributors)

Transition points in who is the primary developer on an actively developing code base can be a source of frustration for everyone involved. We've tried to minimize that pain point as much as possible through the use of agile methods like test driven development, continuous integration, and modular design. Has optimizing for developer happiness brought us happiness? What's worked, what hasn't, and what's worth adopting? How do you keep your project in a state where you can easily hand it off?