98
edits
Changes
→Coding an Academic Library Intranet in Drupal: Now We're Getting Organizized...
We chose Drupal as our intranet platform because of its extensibility, flexibility and community support. We are also moving our entire library web presence to Drupal in 2013 and will be soliciting any advice on which modules to use/avoid and which third-party services to wrangle into the Drupal environment. Should we use Drupal as the back-end to our entire Web presence? Why or why not?
== Hands off! Best Practices and Top Ten Lists for Code Handoffs ==
* Naomi Dushay, Stanford University Library, ndushay@stanford.edu
* Bess Sadler, Stanford University Library, bess@stanford.edu
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?
== How to be an effective evangelist for your open source project ==
* Bess Sadler, Stanford University Library, bess@stanford.edu
The difference between an open source software project that gets new adopters and new contributing community members (which is to say, a project that goes on existing for any length of time) and a project that doesn't, often isn't a question of superior design or technology. It's more often a question of whether the advocates for the project can convince institutional leaders AND front line developers that a project is stable and trustworthy. What are successful strategies for attracting development partners? I'll try to answer that and talk about what we could do as a community to make collaboration easier.
[[Category:Code4Lib2013]]
