good contribution documentation

[robot-o]

with the adaptation of github project management features the documentation needs to provide people with the ability of hitting the ground running completely on their own

acceptance criteria

• [ ] explains development setup
• [ ] explains git flow branching model
• [ ] explains conventional commits
• [ ] explains issue -> project -> pullrequest -> merge -> close issue automation and workflow
• [ ] is understood and agreed upon by the entire core team to be suitable

[thorsteneb]

Robotos notes on git flow from the discord:

another thing near and dear to my heart is keeping our version control organized. for this, i propose the following: semantic versioning for...versioning: https://semver.org/ git flow for branches: https://nvie.com/posts/a-successful-git-branching-model/ conventional commits for ...commits: https://www.conventionalcommits.org/en/v1.0.0/ i made it a habit to at least always write my commits in convcommit spec, some of you might have noticed on the backend repo during corridorcrunch i know its unbelievably hard to bring up the discipline for some of this but after a while it becomes habitual ...also we can have github checks enforce them if we want