GHOP

My web host doesn't enable mod rewrite rules by default. Some other CMS's such as WordPress autowrite the rewrite rules into an autogenerated .htaccess file at install time.

there are several different ways for modules to restrict access to users. There're various hooks and design philosiphies. These methods should be discussed in a page that outlines how you would implement each of them.

Discuss db_rewrite_SQL, hook_perm, hook_access_grants, etc.

The versioncontrol.install file had in extra common in the query to create the commits table.

I have attached the diff between the broken file and fixed file.

The Version Control API module is a relatively new module that provides functions for interfacing with the server side of version control systems (VCS). In order to work, Version Control API needs at least one VCS backend module that provides the specific VCS's functionality. At the moment, only a back end for CVS has been written (see references).

For this task, you will create a module similar to the Version Control API -- CVS backend module but which instead provides an implementation of the Subversion version control system (SVN). You should also have a look at the example "FakeVCS backend" that ships with Version Control API itself, and the overall OVERVIEW.txt for a better understanding of the API's main concepts.

Your module should have functionality similar to what is currently present in the CVS backend. There is already a Version Control API -- SVN backend (see references) project and some starter code is available (database schema + most of the user interface extensions that are required for Subversion). Also, halkeye's standalone Subversion module (see references, too) has a lot of code for interfacing with Subversion, you can likely make good use of that.

Deliverables:

The Version Control API module is a relatively new module that provides functions for interfacing with the server side of version control systems (VCS). In order to work, Version Control API needs at least one VCS backend module that provides the specific VCS's functionality. At the moment, only a back end for CVS has been written (see references).

For this task, you will create a module similar to the Version Control API -- CVS backend module but which instead provides an implementation of the Git version control system. You should also have a look at the example "FakeVCS backend" that ships with Version Control API itself, and the overall OVERVIEW.txt for a better understanding of the API's main concepts.

Your module should have functionality similar to what is currently present in the CVS backend.

Deliverables:
* A new versioncontrol_git.module that implements the required functions for Version Control API backends. These are mostly functions that transform the revision data from the database representation to the API's array format. Here's the exact list of required functions:
* hook_versioncontrol_backends()
* versioncontrol_git_get_commit_actions()
* versioncontrol_git_get_directory_item()
* versioncontrol_git_get_commit_branches()
* versioncontrol_git_get_branched_items()
* versioncontrol_git_get_tagged_items()

Note: We consider this task to be more important than the related task of implementing a Git backend for the Version Control API. However, you may choose whatever task interests you most.

The Version Control API module is a relatively new module that provides functions for interfacing with the server side of version control systems (VCS). In order to work, Version Control API needs at least one VCS backend module that provides the specific VCS's functionality. At the moment, only a back end for CVS has been written (see references).

For this task, you will create a module similar to the Version Control API -- CVS backend module but which instead provides an implementation of the Mercurial version control system. You should also have a look at the example "FakeVCS backend" that ships with Version Control API itself, and the overall OVERVIEW.txt for a better understanding of the API's main concepts.

Your module should have functionality similar to what is currently present in the CVS backend.

Deliverables:
* A new versioncontrol_hg.module that implements the required functions for Version Control API backends. These are mostly functions that transform the revision data from the database representation to the API's array format. Here's the exact list of required functions:
* hook_versioncontrol_backends()
* versioncontrol_hg_get_commit_actions()