This page collects the guidelines established in the git experiment.

This is a work in progress.

ASF GIT repositories are currently hosted at

For understanding the technical aspects of GIT and SVN please read SVNvsGIT. This will help you to grok the design decissions

Project Structure

  1. Each project should have a way to share PMC-private code. This can be a separate repo or just branches secured by naming convention (e.g. branches/private/...). It is for confidential legal stuff like trademark contracts, creds for community accounts like twitter, etc
  2. Each project has at least one GIT repository which contains the main project and is read/writable for all committers
  3. Some projects might need additional GIT repositories containing project parts which have a completely separated lifecycle from the main project. This can be various build-tools (checkstyle-rules, project specific maven-plugins which are needed to build the project) or the project site. This is needed because a GIT branch and tag always affects the whole repository

GIT Hooks

We need to apply some hooks to the GIT repos to prevent the user from changing a few things.

  1. It must not be possible to change the history of a project or delete certain branches. Any sha1 in master or any productive brunch must not be allowed to get changed!
  2. git-rebase, git-stash and stashing via git-rebase -i is only allowed if the history of external contributions remains preserved.

Social Aspects

  1. Pulling from some external (non hosted) repository must only happen if all the respective commits are done by a person which has an iCLA on file.
  2. Incorporating changes from other contributors (no iCLA on file) must only be handled via JIRA attached patches because of legal reasons (the 'grant inclusion under ALv2' flag in JIRA).

Cutting Releases with GIT

Apache Maven supports the usage of GIT with the maven-scm-providers-git since 2008.

Be aware that the branch created by a release with GIT always covers the whole repository.