We are in the process of setting up the version control system so that we can start with the task of refactoring the Adapt output framework and developing the authoring tool front end.
For this purpose, we have set up separately hosted Git and Gitlab environments at http://git.adaptlearning.org/users/sign_in (btw, the version control link at the top of this site also takes you there).
Fabien is working through the configuration of the system today and tomorrow and will set the founding developers up with access to this.
The way we have decided to set this up is as follows:
There will be two repositories / projects (One for the authoring tool and another for the output framework). This way, we can keep the commit histories separate and enable developers to work with the output framework on its own. On the downside, this means that developers working with the authoring tool have to check out two repositories and we have to provide clear instructions as to where to place the folders in relation to each other.
We will use the Gitflow process. Fabien is preparing a document to explain exactly how this applies to our project, seeing as we will have two repositories working together. As part of this, we will also document the branching strategy and process and post this up for review. We have attempted to stick closely to what we see industry best practice being. This also includes naming conventions and relevant branch name prefixes such as 'hotfix' and 'feature'. There is a very good description at http://nvie.com/posts/a-successful-git-branching-model/ (the summary PDF is also attached to this post).
We will incorporate peer review from the start. We will configure the 'master' and 'develop' branches as protected branches. They will require at least one other committer before changes can be incorporated. Also, the code in these branches should always be stable.
Fabien will be in touch to set you up with access and post the full documentation here for review.