BoF Discussion notes from Denver 2012 DrupalCon

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

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.
  • Should we write and make available a series of service hooks (events for commits) that could be made available to developers? Example: triggering the testing system whenever needed, such as after a push, or handling of a comment during a push.
  • In our database, we have several tables (e.g. version_control_operations and version_control_items) with tens of thousands of rows which would need to be duplicated for each branch or new repo. We need to come up with a way to minimize the impact of the exploding resources duplicated during each fork or branch.

Desired Suggestions and Improvements
(Most improvements will need to wait until the D7 port is functionally complete)
1. Duplicate all features of Github
2. Per-issue repositories
3. Port everything to D7 (possible already started and in-progress?)
4. Tracking and organizing the various forks within a project.
5. Provide better integration of sandboxes and parent projects (http://drupal.org/node/1451668)
6. Make pull requests less painful by ...
7. Should per-issue repositories branches' have a way to surface all of the changesets in one place at the top of the issue, rather than only being able to see them linearly scattered throughout the issue?
8. What if the fieldable comments in the issue queues can be set up to track the user's per-issue change branch?
9. Create an "Add my branch to this issue" widget that associates one of 'your' branches to an issue if the user's code happens to be related. The branch chosen by the user would have to be moved into the appropriate per-issue repo.
10 .

The Plan For Drupal 7
A. Clear all the blockers from the current issues first, before beginning anything.
B. Install the plumbing for Activity Streams and Service Hooks first, even if it doesn't fully function.
C.