Drupal.org Git Team

Welcome

The Git migration is complete, but the work is ongoing. Join us!

Documentation: Git handbook
Documentation: Git handbook issue queue
Support using Git - #drupal-gitsupport
Places to jump in: git low hanging fruit
Follow announcements on Twitter: @DrupalGitGremln
Coordinate in IRC - Developers #drupal-vcs
Issue queue: git phase 3
Background: Migrating Drupal.org to Git

Phasing out -p0 patches - May 31?

Posted by rfay on April 6, 2011 at 6:05pm

When we did the Git migration, we set up the testbots to continue to allow both -p0 (old style Drupal patches) and -p1 (the normal Git style patches), but started encouraging the community to switch. This allowed existing patches on issues to continue to test OK, and avoided irritating everybody enormously.

However, now we have a problem. How do we teach people to successfully apply patches if there can be more than one kind? I think we have to phase out -p0 patches sooner rather than later. This would mean:

We're BACK!

Posted by tizzo on April 5, 2011 at 3:21pm

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!

First bi-weekly Git Phase Next Demo!

Posted by tizzo on April 5, 2011 at 3:19pm

Start:

2011-04-12 15:00 - 15:20 America/New_York

Organizers:

sdboyer

eliza411

tizzo

Event type:

Online meeting (eg. IRC meeting)

In the first of our bi-weekly feature demo, sdboyer will show off our progress with git service hooks which will and tizzo will demo our forthcoming drupal based repository browser and some of the integration that the browser will enable!

Join us at https://shomeya.webex.com/shomeya/j.php?ED=150662272&UID=1180140542&RT=MiM0
Telephone Number: 1-408-600-3600
Access Code: 805 789 868

Drupalcon Git Sprint

Posted by tizzo on March 11, 2011 at 9:36pm
Last updated by Josh The Geek on Sat, 2011-03-12 13:33

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

Git Phase Next presentation from DrupalCon Chicago

Posted by dww on March 11, 2011 at 1:36am

Here are some links to our presentation at DrupalCon Chicago:

Slides on Google Docs
Presentation at chicago2011.drupal.org (hopefully soon the video will be posted there).

Enjoy,
-Derek

Drupal.org Git Sub-Teams

Posted by webchick on March 7, 2011 at 6:45pm
Last updated by eliza411 on Mon, 2011-04-25 23:40

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

Git on Drupal.org: Basic Training Screencast

Posted by rfay on March 2, 2011 at 3:58am

There is now a Using Git on Drupal.org screencast to help people learn how to use our new tools.

Live Git Training/Support

Posted by rfay on February 26, 2011 at 7:40pm
Last updated by rfay on Tue, 2011-03-29 04:07

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.

Pre-deployment notes

Posted by eliza411 on February 24, 2011 at 10:33pm

Two features which will not be available immediately after deployment:

RSS feeds for commit logs
Summary page files listing

File listings can still be accessed from commitlogs.

Drupal.org Scheduled Downtime Thursday, February 24, 23:00 UTC

Posted by eliza411 on February 24, 2011 at 5:13pm

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.

Git Release Notes

Posted by Josh The Geek on February 24, 2011 at 1:16am

Important: Git release notes has been updated. Please use 6.x-2.2 now, 6.x-2.1 did many unholy things.
Unimportant: GRN has been updated again. 6.x-2.3 (http://drupal.org/node/1073648) has bugfixes and a new feature.

Git Release Notes (http://drupal.org/project/grn) (note that the link has changed) is a Drush extension equivalent of cvs-release-notes, which lives in the tricks repo (what will happen to it after tggm?).

Git instructions and workflows

Posted by eliza411 on February 22, 2011 at 7:52pm

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.

Questions about Git that I didn't find anywhere

Posted by lelizondo on February 21, 2011 at 11:52pm

I've been using github for a while now, and I've been reading the new docs for the Great Git Migration and I have a few questions:

Will I be able to create and push unlimited branches (with any name), even if I don't create a Project Release for that branch.
Will I be able to delete branches and tags as easy as I do it with Github.
Will I be able to fork any project, even if I don't own or co-maintain it?
What about Pull Requests, will that work? How?

Thanks

Drupal 7 module upgrade features and Git

Posted by femrich on February 20, 2011 at 11:05am

I confess I don't know enough about either CVS or Git to meaningfully discuss the migration. I've been reading through materials and have yet to find answers to my questions, from the perspective of a drupal user not maintaining modules. Perhaps someone here could help me out?:

1) Will the change to git change the ways I interact with modules and themes? Will I still download material as I have done with CVS? Will I still be able to use the Drupal7 procedure of simply pointing to a tarball link in order to install modules/themes?

Aegir rebels now consider migrating back to drupal.org - some questions...

Posted by anarcat on February 19, 2011 at 4:43pm

Aegir migrated away from Drupal.org more than a year ago because it needed git magic to do proper maintenance of its code (but also wanted to merge the modules in the install profile to simplify maintenance). Now that Drupal.org is migrating to git (yaaaay! thank you!), we're reconsidering that decision, and have opened the discussions on our forum to see if that would be a good idea: http://community.aegirproject.org/node/369

My main questions to you guys are those two:

Git Migration Documentation Sprint

Posted by eliza411 on February 19, 2011 at 2:17am

Start:

2011-02-22 18:00 - 21:00 America/Los_Angeles

Organizers:

eliza411

Event type:

Sprint

During the Portland Drupal Users group's regular 4th Tuesday Brewpal, I'll be guiding a face-to-face and virtual documentation sprint at 6pm PST on February 22 at the Lucky Lab on 1945 NW Quimby. Virtually, we'll gather on Freenode in #drupal-gitsupport. There's something for everyone from complete beginner to expert. I'll be creating a list of specific topics, and you'll choose to do one of the following:

Test the steps in sections of documentation for clarity and accuracy
Copyedit sections of existing documentation
Create detailed issues and use cases for missing documentation
Write missing documentation
Document recommended workflows in your favorite graphical environment

it's a great way to get familiar with the changes that are coming.

Existing contributor test plan

Posted by eliza411 on February 18, 2011 at 7:22pm
Last updated by eliza411 on Wed, 2011-02-23 17:09

Things project maintainers should verify before the Git migration. This involves some test commits and branches and release and stuff, which we can’t encourage you to do on the live drupal.org once this is deployed for real.

What to do with current CVS Applications?

Posted by zzolo on February 18, 2011 at 7:45am

How do we handle current CVS Applications given the change to Git in a week. Your input is appreciated:
http://drupal.org/node/1065558

Git migration launch date re-set to Thursday, February 24.

Posted by eliza411 on February 15, 2011 at 9:58pm

After careful deliberation, the Git Migration Team has decided to postpone launch one week to Thursday, February 24 at 3pm PST to allow time for final server configuration and additional testing.*

All the the individual components involved in the Git migration have been tested in the staging environment but bringing them together on the production hardware has taken longer than we allowed for. The team agreed we would all feel much more comfortable with a buffer of at least two full days of uninterrupted community testing prior to deployment.

Project API

Posted by gdd on February 11, 2011 at 1:22pm

Sam asked me to post here after we talked about this topic on IRC.

Subscribe with RSS

Drupal.org Git Team

Welcome