Joined forces in porting?

Drupal 6 is out now for almost 5 months, but a lot of modules haven't been ported to D6. Yet people seem to screaming for them and with cck and views 2 almost being ready, maybe it's time to join forces and help out other contrib module maintainers. I've got a couple of thoughts I want to throw out in the wild and see if anyone else is interested in this topic.

Which modules?

This won't be easy to decide. It's not because I'm not using module foo for reason bar while other people use it everyday that we should ignore this. Au contraire, there are a lot of them out there used by many people (read: non-technical-geeks with little programming knowledge) which can't be ignored at all. There is a list on where mostly maintainers themselves post the status of their module. Maybe we could create a list (wiki-style) in this group with modules people would like to see ported where activity in that direction seems to be non-existant.

When ?

Anytime! We could even submit a session or a BoF at the upcoming Drupalcon in Szeged or even sit down with some people during the code-sprint and see who's willing to take up what during that time. I'm also proposing a new irc-channel called #drupal-porting (duh) to announce your porting time. After that, your idle time should at least be one hour before you may speak again ;)


Easy: submit patches into the issue queue so people can review and test. Using the coder module, you should be able to get small modules ported in no time at all. You're free to use vim and your knowledge of the api any time if you rather want to do it the hard way of course.

Who will do what ?

That's for every individual to decide. But, if we have a list, we can somehow try to delegate so not everyone is working on the same port at the same time. Everyone is invited to help out, but let's organise and make Drupal 6 a pre-killer release :)

Off topic, I just signed up to Drupalcon Szeged. I you haven't , now is the time as the deadline untill the 1st of july is almost there. It's cheap, just go for it!


Submitted by Jose on June 27, 2008 - 04:54

It is interesting to see how fast drupal core moves and how modules stay behind; maybe if core absorbed modules as important and functional as CCK and Views (also the excellent advanced help module and its developer), this asymmetry could be balanced a bit.

Recently, I also noticed that people got together, submitted patches and tested helping the developers of the following (extremely important) modules port to Drupal 6; it was a show of exemplary community development:
- XML Sitemap (already in dev version)
- Image Cache (working version in CVS)

A module that in my mind needs dev help and is crucial to moving on is:
- Imagefield for CCK

You are here