Get involved with the Git migration!

Want to help migrate drupal to git? Great! This page overviews the different parts of the migration process, with a focus on making it easy for you to jump in wherever you'd like. See the Migration Roadmap for a more in-depth overview of what the migration entails.

Phase 2 of the migration has a lot of work to do, and it's spread all over the place. Being so spread out makes it hard for folks to know where to jump in and help. So instead, we've come up with these three loose avenues for participation - "Developing, Documenting, and Deciding." If you'd like to help, you should read through the stuff below and then ping sdboyer over email, twitter, or irc, saying, "I'd like to help with Development/Documenting/Deciding!" He'll get you squared away.

Develop

If you're a code monkey, we can definitely put you to work. There's modules to develop, a migration path to test, test sites to debug, and server settings to tinker with. The modules are the lowest-hanging fruit, and these are ones that really need love right now:

1. Version Control API
2. Version Control Git Backend
3. Version Control / Project integration

Getting the latest branches of these modules finished and working is an absolute must for the migration. The 2.x branch of vc api is what this whole system will be based on, and we're trying to finish it up.

There's LOTS of other dev work to be done, too, including work on the migration path, experimenting with server setups, and work on the packaging script.

Document

It's been soundly agreed upon that documentation is just as essential as code for the success of this migration. Of course, 'documentation' covers a wide range. Here's the general picture of what we want to accomplish:

1. Create a 1:1 analogue of the CVS Handbook. There's a prototype, and an issue to discuss it.
2. Create a 'Git Instructions' module, analogous to the CVS Instructions module.
3. Develop an "open source training curriculum" that will prepare new drupallers/git users for using git to contribute to and work on Drupal projects. (will provide a link here to that discussion once it's kicked off)

Decide

Want to be heard, but not do any work? This is for you! (kidding :P) There are a lot of things about the way d.o works, and the way we work with d.o, that are being decided by this migration - for example, we need to decide how commit statistics should work, and on how we'll replace $Id$ tags Some of these are decisions that can be taken now, while others we'll only realize as we run across them well doing other work. In both cases, though, we need to sort them out as a community for the migration to proceed. So if you're too strapped for time to offer anything but your voice, that's ok - just make sure you follow the migration gremlin, as crucial decisions are primarily be announced there.