Drupal code sprint formats

I've been asked to facilitate a code sprint at Drupal Camp Delhi in a couple weeks.  I've never led a code sprint before, but I have participated in several.  I'm thrilled to do it, but then there are a lot of logistical questions that are rasied.  What format it should take? Who and how many should attend?  Will there be beer?  These are serious questions that I don't have clear answers to.  I thought about it and decided to describe the different formats I've witnessed.

General "grab an issue" sprint.

People show up and work on what they are interested in already.  They collaborate and ask each other questions, but generally just keep it informal and working groups form organically.
  • Preparation: Low
  • Easy to get involved: Yes, but tough for complete newbies unless there is prep.
  • Tangible results: Low
  • Group size: Any

Organized "grab an issue" sprint

A facilitator picks a bunch of issues ahead of time, organizes them (perhaps by experience level or skill type) and then doles them out to people who want to work on them.  People can work in pairs, or individually, but the end result is some amount of traction on a particular topic (piece of core, module, documentation, etc).  Angie


Getting paid in candy: How Acquia is building the next generation of Drupalists

My employer Acquia is a commercial open source company.  That means that they make money (commercial) off of software they don't own (open source) and there are more than one of us (company).  It should be clear then that Acquia's survival is totally dependent on the success of the software it provides services around, Drupal.  

Drupal has been doing exceptionally well as of late.  In fact, Acquia just relased "the showcase"; it is a website detailing over 1000 high profile Drupal sites.  To name drop a few, The Whitehouse, Amnesty International, NCAA, The Economist,, and many, many more.  Drupal is charchterized by having a very robust community of thousands of developers, rapid innovation, successful conferenceslocal community organizing and a thriving ecosystem of service providers.  

The main thing threatening Drupal's growth right now is a lack of expert Drupal talent to meet the demand.   We now compete with the very largest proprietary systems and software companies in all industries.  We have the tech, it's proven, but we need enough people to execute.



How to reach 90% and make it stick: Lessons from Acquia's DrupalCon training