#D7CX

Drupal 7 has been released. As expected, it appears to be a significant improvement over Drupal 6 and earlier versions. Congratulations to the core team for this major milestone!

But what about essential contributed modules? The #D7CX (Drupal 7 Contrib Experience) effort was intended to ensure that Drupal 7 did not suffer the same fate as the Drupal 6 release -- many modules were not available for Drupal 6 well after its release (the problem continues to this day).

In order to make the biggest possible impact, we need as many modules as possible to have full Drupal 7 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.

We are collecting 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. [...]

My experience shows that availability of stable contributed modules is crucial to adoption: I delayed migration from Drupal 5 to Drupal 6 on my existing web sites for well over a year, and when rolling out a new web site that would have been perfectly suited to Drupal, I chose to roll out with Drupal 5 due to the availability of fully released and tested contributed modules.

As a former Drupal contrib module developer, I understand the difficulties related to upgrading modules for each major version's new release. I'm just now getting back into Drupal module development, and with the Drupal 7 release now a reality, I wanted to know how successful the #D7CX pledge effor twas. So I started digging around, looking for contributed modules with a full

As of today, 1/9/2011, here are some of my favorite Drupal contributed modules that do not have a full Drupal 7 release available on the project homepage. (Most have alpha, beta, or -dev versions available, and they may be perfectly usable on a production site, though I'd suggest a thorough test first.)