Contributing guidelines are incomplete about how we use issues and boards
Right now the contributing guidelines present a stub about where to file issues and merge requests and explain simply how we branch off. In course of thinking about #30 (closed) it appears possible to extend it with:
- description templates for issues and merge requests.
- an explanation about how the board view is used to coordinate the work on the issues.
- an explanatoin of the git branching model with the
develop
mainline and how releases tomaster
are coordinated.