Launching the D7CX movement ... and a Contrib Release Manager
Update: #D7CX pledges are for all, not just top 40 module maintainers. all modules should pledge. non maintainers pledge help w/ docs, QA. there is a pledge for everyone.
Drupal 7 is going to be a phenomenal release. The code is miles ahead of Drupal 6, and the D7UX work is poised to bring us a giant leap forward. I really think we are going to make a major difference in CMS land and in the world in general with this release.
In order to make the biggest possible impact, we need most of the top 40 Contrib modules to have full Drupal7 releases on the day when core Drupal 7 is released. Our failure to accomplish this for Drupal 6 was devastating. So, let's turn our attention toward #D7CX - Drupal 7 Contrib Experience.
I want to collect pledges from maintainers to support the #D7CX effort. A pledge consists of writing a statement like below at the top of your project page on drupal.org. Here are my three pledges ...
- #D7CX: I pledge that Organic groups will have a full Drupal 7 release on the day that Drupal 7 is released.
- #D7CX: I pledge that Devel will have a full Drupal 7 release on the day that Drupal 7 is released.
- #D7CX: I pledge that Drush will have a full Drupal 7 release on the day that Drupal 7 is released.
By following this convention, your module is automatically added to the list of all supporting modules.
Now, please go ahead add pledge statements to your modules, or offer to help out in the issue queues of the modules that you care about.
Contrib Release Manager
I propose that we name a Contrib Release Manager position who acts as a peer of Angie Byron, the Drupal 7 branch maintainer. The responsibilities of this role are:
- By D7 release day, help the top 40 modules achieve final release..
- Publish and promote upgrade documentation.
- Encourage developers to share upgrade tips and tricks. Many of us re-implement the same patterns during an upgrade.
- Assure that tools are available for upgraders (coder, deadwood, simpletest service, ...).
- Build a team of people for each major module. Maintainers are not superheroes. We need people to prune the issue queue, perform QA, write tests, write code, write docs, and so on.
- Communicate Contrib update status on a weekly basis. Cheerlead each module as it releases its alpha/beta/rc/final versions.
Which names come to mind for you when you read this list? Who has the people skills to motivate and support our mercurial module developers?
Post a comment here or on your blog with thoughts about these proposals. Let's try to remain positive, and not devolve into "Bob can't upgrade until Suzy upgrades" and so on. If your module has dependencies, then you are a benefactor of that dependancy; help it upgrade. Communicate and collaborate up and down your Drupal stack.