Drupal.org project repositorities should really be hosted or at least mirrored on Github. Not only is this an opportunity to share Drupal with a community of developers who don't naturally gravitate to Drupal.org's project pages, GIthub provides significant functionality that d.o.'s issues system does not provide: the ability to fork code, the ability to associate teams and milestones with projects, and (most exciting for me) the ability to associate issue numbers with git commit messages and have github automatically generate code review comments with links to diffs. This is a much better way of collaborative coding that Drupal.org's system where people have to upload patches and then upload new new patches ad infinitum until a satisfactory fix is created.

http://www.echoditto.com/blog/drupal-sans-github-missed-opportunity

This can be done either by publicly cloning and mirroring to Github or by paying for an Enterprise Github account so that Drupal.org has its own internal Github.

An additional incentive for doing this should be the opportunity to escape from Drupal.org's currently very convoluted code which is used to manage its issues queues. I know that code has been around for a long time and has done wonderful things for the Drupal community, but it is getting pretty long in the tooth, and I've talked with developers who say that it has become a challenge to maintain and upgrade. Maybe this is a good moment to think about migrating to a different system so we can leave some of that legacy code behind.

Comments

WorldFallz’s picture

WorldFallz commented
Project: Drupal.org site moderators » Git on Drupal.org
Component: Other » Documentation

This was discussed as part of the CVS migration, and I'm pretty sure it's still a no go:

Note: While these statistics are interesting, note that a remotely-hosted service such as GitHub is off the table, because it violates the #1 thing we don't want to lose: keeping drupal.org central collaboration hub for Drupal.

For context see http://groups.drupal.org/node/48818

But I'm moving it to an issue queue with a higher likelihood of catching the eyes of the right people.

sheldon rampton’s picture

sheldon rampton commented

WorldFallz: I think the CVS to git migration was a huge step forward, and I would not have proposed moving to GitHub at that moment because simply migrating everything from CVS was already a challenging undertaking. Now that the smoke has cleared from that migration, however, I think it is possible to improve things further, and it does not have to be a "remotely-hosted service" that would displace drupal.org as the "central collaboration hub for Drupal."

Github has an enterprise version that would let Drupal.org host its own internal GitHub with all of the tools that GitHub provides, including the ability to fork, send pull requests, track issues and manage repositories. This internal GitHub could live at a Drupal.org domain, just as it does now:

https://enterprise.github.com/

Alternately, d.o. could use some scripting to keep the Drupal git repos synced/mirrored on the public GitHub, with any commits to one repo automatically pushing to the other repo.

WorldFallz’s picture

WorldFallz commented

I wasn't really weighing in one way or the other-- I was just letting you know what the decision was, and moving the issue.

pmackay’s picture

pmackay commented

I would very much like to see the idea of an enterprise GitHub installation being used for Drupal.org. This would keep the community focussed on d.o. while offering significant development benefits.

pmackay’s picture

pmackay commented
Issue summary: View changes

minor tweaks