Drupal.org Git Team

Leading Drupal's migration from CVS to Git made something eminently clear to me (and eliza411, the migration's PM): there's a lot that's broken about how we manage, maintain, and improve drupal.org (and its subsites). Since then, I've been gradually chatting up more and more people with the idea that we could build a structured, participatory model for updating and adding new features to drupal.org. And that if we do it right, it could become a best-practice model for (Drupal) site management (open, participatory) workflows.

Join the Git team for our regularly scheduled, semi-weekly demonstration of progress on new features for Git and Drupal.org. This is a great opportunity to see what's happening and find a way to become part of the team. We'll be looking at interface mock-ups for new functionality: adding service hooks and setting a default branch.

Location: https://shomeya.webex.com/shomeya/j.php?ED=150662272&UID=1180180112&RT=MiM0
Dial-in: 1-408-600-3600 (You should be able to join via your computer's headset.)
Access code: 805 789 868

This started life over as a comment I posted at #1059966-20: Change recommended format for commit messages (no more '#1234 by abc') but I'm moving it here at eliza411's suggestion to hopefully gather more feedback on the proposal...

Sorry I didn't suggest this sooner, but I just came up with it today while I was happily doing Git commits on a plane. ;)

Instead of:

How about this?

It means we can now start adding new features above and beyond the ones that were provided in the old CVS days. In the interest of fostering community involvement and pushing ourselves to ship new stuff regularly, we'll be doing demos every two weeks to show off new features that we're developing for Drupal.org. These demos will be brief (held to 20 minutes) and will provide a tour of what we have working. And the first one is coming right up!

The git team is sprinting in Superior A on the last day of Drupalcon! This page will track our issues and our progress.

• generalize d.o git hooks to make generic git hooks that we can ship with versioncontrol_git (Drupal.org testing profile related)
• Associate dummy projects with git clones for versioncontrol
• Propertly review halstead git parser patch
• Write a vc_git git parser using libgit2

Here's who to talk to about what. Exact contents of this page still in progress.

Lead maintainers

• Overall: Sam "sdboyer" Boyer
• UX: Melissa "eliza411" Anderson

Specific subsystems

• Version Control API*

  • Marco "marvil07" Villegas

• Project*

  • Derek "dww" Wright
  • Mike "mikey_p" Prasuhn

• Project Git instructions

  • Michael "halstead" Halstead

• Job system

  • Justin "beejeebus" Randell

• Twisted SSH

  • Trevor "chizu" Hardcastle

• Repository browser

  • Howard "tizzo" Tyson

Initiatives

Weekly scheduled live support sessions with screensharing by both leaders and participants (using webex),

If you can, before coming please watch (and do) 22-minute screencast. You'll be more ready for a deeper set of topics at these.

We'll cover whatever territory the attendees want to cover.

Reposted from the Drupal.org Front page to be available during downtime. During down time, check https://twitter.com/drupalgitgremln for periodic updates.

Drupal.org will have approximately 12 hours of scheduled downtime, Thursday, February 24, 23:00 UTC (3PM PST, 6PM EST). We will be performing the CVS to Git migration. This is the most comprehensive and extensive change to Drupal.org in recent history - perhaps ever, therefore, the Infrastructure & Git Migration teams need an adequate time buffer to perform the migration, verify the data, and check for and resolve any issues.

What does “downtime” mean?

The following parts of the *.drupal.org will be inaccessible for the duration of the migration:

• The main drupal.org website, including all download pages, issue queues, forums, and search.
• Write access to cvs.drupal.org.
• Account creation on any of the Drupal.org sub-sites, including groups.drupal.org, api.drupal.org, and chicago2011.drupal.org.

Some areas of the drupal.org infrastructure remain unaffected, including:

• Drush commands such as drush dl.
• Read-only access to cvs.drupal.org. CVS repositories will be maintained in read-only mode for at least a year following the migration.

We regret that it was not feasible to provide a read-only copy during the downtime and apologize for the inconvenience this extended downtime will cause to the community, but it’s hard to overstate the incredible transformation this move will enable for our community’s collaboration. With Drupal 8 development kicking off soon, and code sprints happening in DrupalCon Chicago in just over a week, having a strong platform from which to work is vital for our project’s future.

Thank you very much for your patience and understanding. Please keep your eyes on https://twitter.com/drupalgitgremln and http://groups.drupal.org/drupal-org-git-migration-team for updates.

I’ve been working on Drupal.org documentation and Project Git Instructions (the contextual cut-and-paste directions provided for each project) not because I’m particularly the best person for the job but because as project manager for the migration, I have a vested interest in the community’s successful transition and, more importantly, I’ve been the least busy person who also has access to the team. It’s hard to document what doesn’t exist, and the project has been moving at breakneck speed to be ready for Chicago DrupalCon.