Git team lightning talks

I'll be showing a mockup of a user interface for managing repository settings, including the service hooks described by sdboyer in the last talks and the much-in-demand ability to choose a default branch so developers can do away with master completely.

We'll be discussing three resources during the repository interface lightning talk, which I'm setting out for reference:

• The context for the repository interface: http://groups.drupal.org/files/Repo_setting_context.png
• How modules interact to produce project pages: http://groups.drupal.org/files/project.png and http://groups.drupal.org/files/git_access.png
• A preliminary mock-up: http://bit.ly/hh1GDl This is a multi-page mockup. Use the links on the right to navigate or leave comments.

We really look forward to feedback on the contributor interface! Join us at 3:00pm Eastern / noon Pacific on Tuesday, April 26, 2011. Git team lightning talks last 20 minutes in total.

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

as per sdboyer:

it's a framework for letting things know when people push code to drupal.org, with a lot of power & granularity about just *what* we tell them

so it could be telling twitter to go *ding!*, or it could be telling coder to run a new automated analysis. point is, `git push` is an incredibly important event, and this lets us notify stuff when it happens.

To clarify ... we have two new features to introduce on Drupal.org:

1) Setting a Default Branch: Git assumes that a repository's default branch is master, but because most of Drupal.org's repositories support projects--modules, themes, and installation profiles--that have branches particular to a specific core version of Drupal, master doesn't really work. By adding the ability to set a default branch other than master, maintainers can ensure that people download the most appropriate active branch by default and that the branch name will tell them if it's compatible with a different version than what they intend to work with.

2) Service Hooks: As yoroy quotes above, service hooks are a way to tell something or someone outside a Git repository on Drupal.org about a 'git push' event there. This area is more complex than the setting of default branches and will be implemented some time afterward.

The user interface is a blocker for both of these features.

• webchick
• rfay
• tizzo
• eliza411
• sdboyer

• Arabic
• Alappuzha
• Event Platform
• Western Ohio User Group
• Goa Drupal Community
• Liverpool
• Chandigarh Drupal Geeks (C.D.G.)
• API-First Working Group
• Compony opinionated developers
• 4SPOTS