Posted by eliza411 on April 12, 2011 at 8:14pm
Start:
2011-04-26 15:00 - 15:20 America/New_York Event type:
Online meeting (eg. IRC meeting)
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
Attachment | Size |
---|---|
Repo_setting_context.png | 77.42 KB |
project.png | 265.51 KB |
git_access.png | 190.87 KB |
Comments
Repository mangement interface
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.
Resources for Tuesday's lightning talk
We'll be discussing three resources during the repository interface lightning talk, which I'm setting out for reference:
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
Service hooks
as per sdboyer:
To clarify...
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.