Version Control API

PROJECT INFORMATION

Project page on drupal.org: http://drupal.org/project/versioncontrol_soc08

DESCRIPTION

The Version Control API together with it's backend modules decouples the Project module from a specific Revision Control System by providing a RCS-independent API. One of the major goals of this project is to make the Version Control API ready for actual usage on drupal.org. This will make it possible to use any of the supported RCSes on Drupal 6 and thus also on drupal.org. It is also planned to fix a couple of existing issues with Version Control and to implement some new features which will lead to increased flexibility and enhance the utility of Version Control.

The Version Control API, which originates from jpetso's last year's SoC project, has largely decoupled the Project module from cvs.module. This project will unleash the full pontential of the Version Control API and make it production ready for a new set of users including drupal.org.

You can find the proposal discussion here. You will also find the final version of the proposal there.

PROJECT TIMELINE

Until May 26:

• Create wiki page on groups.drupal.org.
• Create project on drupal.org.
• Fax my Student Foreign Certification (= tax related documentation) and Proof of Enrollment to Google.
• Read through the Contributor's Guide .
• Learn how to port modules to Drupal 6.
• Learn what changed since Version Control API 5.x-1.x.
• Create a blog.

May 26 - June 16:

• Port Version Control API to Drupal 6.
• Port Commit Log to Drupal 6.
• Port Commit Restrictions to Drupal 6.
• Port Account Status to Drupal 6.
• Port CVS Backend to Drupal 6.
• Port Project Node Integration to Drupal 6.
• Port Subversion Backend to Drupal 6.

June 17 - July 6:

• Adapting the release node integration which currently heavily depends on CVS. As this will require major refactoring of the project_release.module this can be considered as one of the most crucial tasks of this project.
• Survive university exams.

July 7:

• Submit mid-term evaluation to Google.

July 8 - August 11:

• Finish the script started by hunmonk to migrate existing cvs.module data to the various Version Control API tables.
• Fix http://drupal.org/node/209402.
• Implement get_directory_contents().
• Prevent the creation of branches through backdoor.
• Implementing subversion module's functionality in a Project and Version Control API based solution.
• Make it possible to have multiple accounts per user and per repository. This will require changes in the Version Control API and the modules.
• Create authentication method plugins to be more flexible with account authentication. This will make it possible to support multiple methods of authentication. Details: http://drupal.org/node/223891

August 11 - August 18:

• Scrub code.
• Further testing.
• Improve documentation.

After 19:

• Write and submit final evaluation.
• Submit required code samples.
• Recieve SoC shirt, party and be happy.

• Live happily ever after. :)

STATUS UPDATES

June 4:

1. What did you get done this week?
   • I finally finished setting up my development enviroment and started working on the D6 port of the Version Control API. I did not get very much done this week because i was at a conference from Thursday to Sunday.
2. What are you planning to do over the next week?
   • I am going to meet with jpetso tomorrow to discuss further action. What is planned is to continue to work on the port of the Version Control API.
3. Is there anything you're blocked on?
   • I don't think that there will be any major distractions for the next two weeks. I want to get done as much as possible in the next two weeks before my finals will get going (June 17 - June 30).

May 26 and before:

• Setting up development enviroment.
• First meeting with jpetso.
• Getting to know the code.
• Getting to know CVS and SVN.
• Setting up wiki page and project. Getting a CVS account.