Overview of Initiatives, people involved, development processes, communications and management processes, the Gates, etc.
[Work in progress, please correct any misinformation!]
Current people involved in the D8 Initiatives as leads, maintainers, or project management support:
- Greg Dunlap (heyrocker): Build systems and change management initiative lead
- Larry Garfield (crell): Web services and context initiative lead
- Kris Vanderwater (EclipseGC): Blocks & Layouts Everywhere Initiative lead
- Jeff Burnz (jmburnz): Design initiative lead
- Gábor Hojtsy: Multilingual/i18n initiative lead
- Jacine Luisi (jacine): HTML5
More info about core initiatives: http://drupal.org/community-initiatives/drupal-core
Project management and process support
- Melissa Anderson (eliza411): Project management support (git/agile/docs specialty)
- Chris Strahl (chrisstrahl): Project management support (agile specialty)
- Ariane Khachatourians (arianek): Project management support (agile/docs specialty)
Project and people management
Easy ways to do "agile"
Suggestions on how to kickoff and run monthlong sprints:
- Sprint planning: at the start of the month, meet briefly with whoever you work with the most (on IRC or if you like, by voice) and decide what to work on for the month.
- Tag the issues you want to deal with during the sprint using the format "Sprint: June 2011" so that there is a consistent tag across all initiatives (ideally you don't want to start any new issues in the current sprint once it's in progress, unless there is something critical).
- Convince a bunch of people to dedicate themselves for the month and get them done!
- At the end, start anew and decide what should be in the next sprint, not necessarily bringing issues forward that weren't completed in the last one (it's all about reevaluating priorities on an ongoing basis).
- If you want to and feel like people would be into it, you can also do a Sprint retrospective meeting and briefly review what did and didn't go well, and learn for next round (to continually improve process).
- At the end of each sprint, you should have new functionality ready to demo (if desired) or to funnel through the "gates" to be committed to the master branch of your Initiative or HEAD.
How to find and keep contributors/volunteers
- Make sure your g.d.o group is up to date and has some consistent activity.
- Start a Twitter account to get visibility and a quick communication channel.
- Publicize at events, online, with Drupal.org frontpage posts, etc.
- Be sure to clearly document easy ways for people to get involved.
- Hold at least a weekly meeting at a regular time on IRC, you may get people showing up who want to see how they can help.
Issue tracking and project workflows
"Sprints" (or Iterations) and "Phases"
- Be very conservative when choosing how many, and which, issues to tackle for the month-long sprint. Start small so you can actually finish them and avoid people getting discouraged.
- Any issue you put into a sprint should be able to be complete within a single sprint. If that doesn't sound realistic, break the issue down into smaller sub-issues.
- If the functionality you're working on is larger than what can be done in one sprint, you may want to break that into a few phases. This will also make it easier to merge back into the master branch.
The "Gates" (to where?!)
Liason: Jennifer Hodgdon (jhodgdon)
Code + git
See http://groups.drupal.org/node/148184 for now.
Build systems and change management : http://groups.drupal.org/build-systems-change-management/cmi
Web Services and Context Core Initiative: http://groups.drupal.org/wscci
Design 4 Drupal: http://groups.drupal.org/design-drupal
Build systems and change management: #drupal-contribute
Web Services and Context Core Initiative: #drupal-contribute
Design 4 Drupal: #drupal-design (Note: http://groups.drupal.org/design-drupal is the central communication hub.)
Internationalization: #drupal-contribute or #drupal-i18n