Git Phase Next: The Promised Land

Time slot: 
March 10th, 3:45 PM - 4:45 PM
Room: 
Sheraton 4 & 5
Track: 
Drupal Community
Experience: 
Intermediate

At DrupalCon San Francisco, we presented a panel discussion entitled The exodus: leading Drupal out of CVS where we introduced the effort to migrate Drupal.org from CVS to Git. By the time DrupalCon Chicago happens, we hope to have already done the initial migration and completed what we've been calling Git Phase 2. To find out what that means for you, don't miss Git on Drupal.org: It's Easier Than You Think!.

However, this initial phase of the Git migration is only the first step. Although Drupal contributors will have the great functionality that Git provides at their disposal, in many ways, the Drupal development workflow will be similar to how it is now -- people will still work in issue queues, upload patches, and so on. Throughout the migration, we've been considering more far-reaching changes to really take advantage of the decentralized nature of Git, but have been postponing these to what we affectionately refer to as "Phase Next".

This session will provide a brief overview of the current state of collaboration tools on Drupal.org, but then outline the various proposals for deeper changes. It'll also be a great chance to solicit feedback from the community and get your ideas on how we can build a promised land of easy and powerful collaboration on Drupal.org using all the power that Git allows.

Video on archive.org.

Intended audience: 

Anyone who contributes any kind of code (modules, themes, distributions, etc) on drupal.org, anyone involved in Drupal core development at any level, or anyone who thinks they might want to do any of those things someday.

Questions answered by this session
Question 1: 
Why aren't we just using GitHub for Drupal development?
Question 2: 
When will drupal.org be more like GitHub?
Question 3: 
Will I always have to contribute to Drupal core by uploading patches?
Question 4: 
I thought "forking" was bad. Why are we planning to make it so easy to fork each other's code? Shouldn't we be fostering more collaboration, instead? (Trick question)
Question 5: 
How will the automated testing system handle all this Git repository forking and cloning?
Git Phase Next: The Promised Land has been selected and voting is closed.

Diamond Sponsors

 
Palantir.net
VPS NET

Platinum sponsors

 
workhabit
Trellon

Gold Sponsors

 
HotDrupal.com
NorthPoint
Treehouse Agency
Microsoft
Duo
Chapter Three
Drupal Connect