You are hereBlogs / moshe weitzman's blog / Launching the D7CX movement ... and a Contrib Release Manager

Launching the D7CX movement ... and a Contrib Release Manager


By moshe weitzman - Posted on 01 July 2009

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.

#D7CX

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:

  1. By D7 release day, help the top 40 modules achieve final release..
  2. Publish and promote upgrade documentation.
  3. Encourage developers to share upgrade tips and tricks. Many of us re-implement the same patterns during an upgrade.
  4. Assure that tools are available for upgraders (coder, deadwood, simpletest service, ...).
  5. 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.
  6. 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.

Tags
  • #D7CX: I pledge that FileField will have a full Drupal 7 release on the day that Drupal 7 is released.
  • #D7CX: I pledge that ImageField will have a full Drupal 7 release on the day that Drupal 7 is released.
  • #D7CX: I pledge that Fivestar will have a full Drupal 7 release on the day that Drupal 7 is released.
  • #D7CX: I pledge that Flag will have a full Drupal 7 release on the day that Drupal 7 is released.
  • #D7CX: I pledge that Webform will have a full Drupal 7 release on the day that Drupal 7 is released.

This is a great idea and I hope that it will motivate many maintainers to be prepared for D7.

I wuv you Nate x

Hopefully FileField & ImageField will not be ported at all... they will simply ship with core. As for Webform, will it be ported or be re-written to use the Fields API?

A preliminary port of VotingAPI 2 to Drupal 7 is now in CVS (http://drupal.org/node/506920) -- there are a few specific rough edges I'd like to polish up now that Drupal 7 features can account for some of the old workarounds, but I've tested it with a roughly ported version of Plus1 module (http://drupal.org/node/506936) and it's working.

A *very* important first step is to get the tools you mention ported to D7 ASAP-- Deadwood in particular. (I wonder if the API changes are relatively frozen to embark on this?)

I guess an alternate and less ambitious (but potentially fruitful) pledge could be "I pledge to post/review patches to the #D7CX modules' issue queues". =)

Good idea. Pledges can be customized and posted anywhere. Just include #D7CX in the pledge. Google finds all.

"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?"

I nominate Moshe Weitzeman.

Wow, great initiative. :)

Comment notify and Pathauto are in.

Token is a piece of cake to update and may still be a candidate for core...so it seems inappropriate to include in this list. Should it not be in core, it will certainly be ready for D7 on the day D7 releases.

What a great idea to help encourage module maintainers! I just pledged to have XML sitemap and Path redirect to be ready with Drupal 7.

This is a really great idea, but I suggest using some additional criteria for deciding what modules to prioritize for D7, other than just the frequency of downloads. Although that is a useful criterion to consider, it may be more important to consider how modules can be combined to work together to create powerful and useful Drupal sites, and how well they interoperate.

I suggest taking the set of 28 contrib modules that Acquia has included in their distribution, which they have carefully selected and chosen for interoperability and functionality. I.e., these modules are guaranteed (by Acquia's work) to work together out of the box, and to provide key functionality for many Drupal sites.

Another useful set of contrib modules to consider is the set of 31 contrib modules that Lullabot included in the module distribution for their book, Using Drupal. Again, this set of modules were carefully chosen by Lullabot to interoperate and provide the key functionality that they wanted to demonstrate for the various social networking and other sites that they demo'ed in their book. I.e., these modules also are guaranteed (by Lullabot's work) to work together out of the box, and to provide key functionality for many Drupal sites.

Here is a link to a list of the contrib modules included in the Acquia 1.2.6 distribution: Acquia_Contrib_Modules

Here is a link to a list of the contrib modules includes in the Using Drupal book: UsingDrupal_Contrib_Modules

Here is a link to a numbered list of the top 150 contrib modules, based on frequency of download: Top-150_Contrib_Downloads

As can be seen, many of the Acquia and Using Drupal modules are the same, and not all of the top 40 downloads are necessarily included in those sets, or include all of the key modules in those sets.

A careful comparison of these three sets of modules, and others, by those interested in participating in the d7cx effort should provide a good starting point for prioritizing modules to prepare by the D7 release.

I'll have Date ready, at least everything that doesn't require Views. When Views is released, I'll have the Views and Calendar integration ready.

I am definitely concerned about the explosion of hooks in Drupal 7. But here's what I'll pledge, I'll work to get testing.drupal.org to do testing of Drupal 7 contributed modules.

I'll also commit to try to get tools like deadwood and codermodule integrated with testing.drupal.org so that we can try do automated upgrades and testing so folks can see how well their patches are performing.

Kieran

#D7CX: I pledge that WP2Drupal will have a full Drupal 7 release on the day that Drupal 7 is released (or be merged into something else).

This makes me happy. It means we designer/shop-owner-types can start selling D7 to real clients much earlier. Yeah!

With CCK in core, the big question will be Views....... Views? Are ya taking the pledge?

How about you pledge to help Earl and the rest of the team deliver it?

This is not the place to ask. Your help is warmly appreciated http://drupal.org/node/363410 here.

#d7cx I will be done with the Views query builder in July.

Great idea. Thanks for spearheading this.

#D7CX: I pledge that Backup and Migrate will have a full Drupal 7 release on the day that Drupal 7 is released.

I'd like to help out with cat herding whereever I can. I'm currently directing my efforts towards Redesign, but by the September RC I should have more cycles available, and some additional experience to fall back upon.

Keep me in mind, and poke me if something is needed.

...not that it's in the top 40 or anything, but I know this will motivate me to get it done. Nice idea!

#D7CX: I pledge that Search Lucene API 2.0 will have a full Drupal 7 release on the day that Drupal 7 is released.

This is a great idea, as the lack of stable module ports really hampered D6 adoption for quite a some time.

I think it would be great to not only limit this fantastic innitiative to modules, but have it for themes as well. I pledge to have Grassland, Elements, mulpo, Dropshadow, and Blue Zinfandel to have full Drupal 7 releases on the day that Drupal 7 is released. I just changed the #D7UX link Moshe suggested to have a list of themes instead of modules, I hope other themers add they're themes to the list, especially the more popular ones. Thanks for starting this Moshe, #D7CX rules! #D7CX for themes

#D7CX: I pledge that Sky will have a full Drupal 7 release on the day that Drupal 7 is released.
#D7CX: I pledge that Skinr will have a full Drupal 7 release on the day that Drupal 7 is released.

Sounds like a really good plan. Count me in!

  • #D7CX: I pledge that Shadowbox theme will have a full Drupal 7 release on the day that Drupal 7 is released.
  • #D7CX: I pledge that Clean theme will have a full Drupal 7 release on the day that Drupal 7 is released.
  • #D7CX: I pledge that Block edit theme will have a full Drupal 7 release on the day that Drupal 7 is released.

The Acquia themes are now on the list :)

The pledge idea is a great initiative.

I'll think some more about the idea of a contributed repository maintainer. We can discuss this in Paris.

I'll pledge some later on too!

#D7CX: I pledge that Bookmarks will have a full Drupal 7 release on the day that Drupal 7 is released.

Great initiative everyone!

#D7CX:I pledge that Darkblue will have a full Drupal 7 release on the day that Drupal 7 is released.

#D7CX:I pledge that Joomla will have a full release on the day that Drupal 7 is released.

Hah - nice one. You gotta sign a clever post like this.

Wow 7 pages of modules in the D7CX search results :) I'd really like to see this promoted even more, should have a frontpage Drupal.org post.

Hoping that Views and Panels will pledge ;) poor Earl.

- Sean Bannister

This is also pretty relevant: Port Upgrade Status/Assist to 6.x. It's actually an upgrade from d5 -> d6, but that's the nature or the module - it will always be one release behind.