Sprint 1 was primarily dedicated to making key decisions necessary for the project to move forward. What follows is a brief summary of all issues tagged for the sprint with links to the background discussions.
Completed Tasks:
-
Repository Structure
Instead of having projects sub-divided as /drupal, /contributions/modules, /contributions/themes, and so on as we currently do, place projects in the same top-level directory.
Read more at: http://groups.drupal.org/node/91699
-
Branch/Tag naming in Git
Lift the requirement to use specific branch naming patterns when committing, except when the tag/branch is intended to translate into an actual release and tarball, as follows:
Description CVS Git 7.0-alpha6 official release (core) DRUPAL-7-0-ALPHA6 7.0-alpha6 6.x-2.3 official release (contrib) DRUPAL-6--2-3 6.x-2.3 6.x-dev release (core) DRUPAL-6 6.x 6.x-2.x-dev release (contrib) DRUPAL-6--2 6.x-2.x Read More at http://groups.drupal.org/node/85269
-
$ID Tags
Remove all historical $Id$ tags to prevent merge conflicts and ensure stale information doesn't make it into the new git repositories. Because of the limitations of git's keyword expansion, we will NOT be replacing $Id$ with anything else. Drupal files will be unadorned by in-file meta-packaging info. Packaging scripts will be expanded to include a MANIFEST-like file.
Read More at http://drupal.org/node/819874
-
Access Control
Using the Twisted Web Framework, develop a git version of the python-twisted daemon to authenticate via keys or passwords and integrate it into our ACL System to provide:
1. High Performance - Able to easily handle our users concurrently checking out/checking in/branching/etc. Also with the ability to handle the fact that we may have a lot of temporary issue branches.
2. SSH Key Authentication - Wanted by many core developers
3. Password Authentication - Wanted by less technical users
4. User DB Not Tied to LDAP/UNIX/PAM or drupal.org credentials - Being tied to real user accounts is just not doable, we have too many cvs account for this to be manageable.
5. Use the standard SSH DaemonRead More at http://drupal.org/node/714034
-
Job Queueing System
Use Hudson to manage our web-triggered jobs. Rather than being used directly, Hudson will be called by PHP in two ways:
1. direct pass-throughs which allow the calling PHP to determine exactly what logic should be run, in which case Hudson is just a dumb wrapper
2. more structured jobs that take arguments from PHPIdeally we'll start with the direct pass-throughs and move toward structured jobs wherever possible to gain the benefit of Hudson’s trend and failure reporting data.
Read More at http://drupal.org/node/893108
-
Recording Commit Statistics
Generate commit statistics based exclusively on the commits that live in the project repository itself. Maintainers will decide what credit is ultimately given based on how they merge and what they push.
Read More at http://drupal.org/node/782408
-
Recommended Merge Workflow
Standard rebase/merge with the exception that maintainers should get in the habit of using the --no-ff option to git merge when merging in changes made by other people to ensure no fast-forward merges.
Read More at http://drupal.org/node/782408
-
Developer Code of Conduct
Allow the user to agree the the following with one checkbox, once it's been run by legal.
I will only commit GPL v2+ code and resources to the Drupal code repository.
I will cooperate with the Drupal Security Team as needed.
I will adhere to and have read the Drupal Code of Conduct.
I agree to the Drupal Code Repository Terms of Service.Read more at: http://drupal.org/node/892312
Resolved Bugs Reports:
- Fix fatal errors in log parser - Version Control API - Git Backend -- http://drupal.org/node/904664
- dbtng module ignores default prefix - DBTNG -- http://drupal.org/node/895534
Open and Postponed Tasks:
- Git Migration Status Update -- http://drupal.org/node/904682
- Separate "operations" concept back out into commits, branch/tag ops, and a true activity stream [d2] -- http://drupal.org/node/879600
- Review for additional TODOs related to d.o conversion to git -- http://drupal.org/node/782584