Drupal.org Git Team

Welcome

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

Drupal.org Git Team

eliza411's picture

Git Scrum Call

Start: 
2012-05-18 13:00 - 13:30 America/Los_Angeles
Organizers: 

Note the time change!

Currently happening on Skype. Ping me via my contact form or in #drupal-vcs with your Skype info to get dialed in.

  1. A very brief go-round (10 minutes total) where you tell:
    • What you have done since we last talked.
    • What you are working on before our next call.
    • If you are you blocked (and if so, by what).
    • If you have a topic for longer discussion after the go-round.
  2. Discussion (20 minutes)
fotuzlab's picture

Code standard check at the time of git commit

Was wondering if we could include pre-commit git hooks in module/theme repositories to check drupal coding standards. (Like the ones provided by http://drupal.org/project/git_hooks).
This would help in standardizing the code on d.o

The only problem I find is ... new contributors may find it irritating and hence put them off.

Thoughts???

eliza411's picture

Git Scrum Call

Start: 
2012-05-11 10:00 - 10:30 America/Los_Angeles
Organizers: 

Currently happening on Skype. Ping me via my contact form or in #drupal-vcs with your Skype info to get dialed in.

  1. A very brief go-round (10 minutes total) where you tell:
    • What you have done since we last talked.
    • What you are working on before our next call.
    • If you are you blocked (and if so, by what).
    • If you have a topic for longer discussion after the go-round.
  2. Discussion (20 minutes)
eliza411's picture

Git Scrum Call

Start: 
2012-05-04 10:00 - 10:30 America/Los_Angeles
Organizers: 

How do i commint my new project

I have started a new project,I need to commit my codes .How do i commit my code Please help

webchick's picture

Upgrade Drupal.org to Drupal 7 Sprint!

Start: 
2012-04-23 (All day) - 2012-04-27 (All day) America/Los_Angeles

The week of April 23 - April 27, the Drupal Association is sponsoring a sprint, hosted by the Oregon State University Open Source Lab, to upgrade Drupal.org from Drupal 6 to Drupal 7!

The sprint will be mainly focused on the following areas, and the following attendees will be there:

Read more
webchick's picture

Drupal.org Office Hours

Start: 
2012-04-09 11:00 - 12:00 America/Los_Angeles
Organizers: 

Come to Drupal.org office hours to share what you're working on and help us come up with the weekly drupal.org hit list!

Stop by #drupal-infrastructure from 11am to 12pm Pacific Time (18:00 - 19:00 UTC).

BoF Discussion notes from Denver 2012 DrupalCon

The Current Needs, as outlined by @sdboyer

  • Git components are currently managed by several disparate tools, Puppet, ...
  • Version control git modules are functionally complete, but need to make it through testing.
  • Setting of default branches is now tested and working.
  • Sdboyer needs to distribute more of his current server management responsibilities to other people, but there are access and permissions blockers. Marco, Howard, Pat, @drumm, @bejeebus, and @webchick are available to help. @drumm will email OSL to ask for the needed access changes.
Read more

Can't cut dev release

Hi,

For some reason I am not able to cut new dev release since migration. I have checked into the HEAD and the 6.x-1.x release and it still doesn't seem to build any ideas?

http://drupal.org/project/apachesolr_views

I'm sure its just a training issue, but your help would be appreciated

Regards,

Dave

sdboyer's picture

Building a Drupal.org deployment pipeline

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.

Read more
eliza411's picture

Git team lightning talks

Start: 
2011-05-10 12:00 - 12:20 America/Los_Angeles

Join us from noon - 12:20pm PDT to learn about the two Git-related Google Summer of Code projects: Drupal.org Auth compatible Git and Http daemons and Version Control Activity logging, Activity Streams and Development Statistics.

WebEx: https://shomeya.webex.com/shomeya/j.php?ED=150662272&UID=1180180112&RT=MiM0
Access code: 805 789 868
Phone Number: +1-408-600-3600

eliza411's picture

Git team lightning talks

Start: 
2011-04-26 15:00 - 15:20 America/New_York
Organizers: 

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

rfay's picture

Testbots now use git to apply patches, so binary patches and copies/moves work in patches

The testbots now use git to apply patches, so binary patches and copies/moves work in patches. See the issue.

To create a binary patch: git format-patch --binary --full-index --stdout

To create a moves-and-copies patch (one that magically moves and copies): git format-patch -C -M --stdout

Change convention for referencing issues in commit messages?

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:

Issue #1234 by xxx

How about this?

[#1234] by xxx

Read more
rfay's picture

Phasing out -p0 patches - May 31?

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:

Read more
tizzo's picture

We're BACK!

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!

Read more
tizzo's picture

First bi-weekly Git Phase Next Demo!

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

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

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

Read more

Git Phase Next presentation from DrupalCon Chicago

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

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

Subscribe with RSS Syndicate content

Drupal.org Git Team

Group organizers

Group events

Add to calendar

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: