SlapOS repository rules=======================Short version for impatient---------------------------'master' branch is always stable. One shall never work in this branch. Oneshall expect reversion or removal of his commits in 'master' branch, if theyare not because of merging another branch.Everyone has to create branch, basing on 'master' or any other branch. Allwork shall be done in such branch. It is advised to review it before merginginto 'master'. It is very good habit to tag such merges.A bit more background---------------------SlapOS repository 'master' branch is supposed to be stable. No new work isaccepted on this branch. Each time someone uses (clones, extends) 'master'branch it is supposed to work (as far as it was tested).Tags on 'master' branch are supposed to be repeatable software definitionsforever. All versions and external links shall be setup in a way, that theywouldn't change in day, month, year, etc.Everyone can make his own branch to introduce new software to SlapOS. Thereare no rules about those branches, as each software is specific.It is good idea to ask for review before merging changes into 'master' branch.Peer review can detect issues not detected by testing, development or selfanalysis.After some software is stabilised and no more work is planned it is acceptableto remove such abandoned branch in order to minimise amount of branches.