Describe repository rules and guideliness

[bitphage]

Write CONTRIBUTING section or separate document with description how developers should provide contributions.

• No force push allowed to master and release branches
• Perform your work in feature branches. Before creating a PR, rebase your changes on top of the base branch. History in the base branch thus should be fast-forward
• Branch naming for features and fixes should be in viz-000-description format, where 000 is an issue id
• "Release branch" is a branch where PRs from tip branches are going, for example viz-v0.19. When code is ready for release, a tag objects should be created pointing to a commit in release branch
• Releases must contain previous tag in their history to preserve consistency
• Avoid direct commits into master and release branches. Use PRs instead which must be approved by another commiter
• Delete original branches and tags (except ones we will use as starting point)

[bitphage]

http://www.jillesvangurp.com/2011/07/16/using-git-and-feature-branches-effectively/

About branching. Actually, we can avoid using master and release branches together for now. We can have master only and feature branches for single features development.

For the feature:

• master is for Continuous Development and Integration
• release branch can be created to follow feature freeze (while master can be used for the futher development)