Implement collaborative feature branch workflows

[aufdenkampe]

During the RESPEC-LimnoTech workshop to kickoff HSP2 collaboration (March 24-25, 2020), we decided to use a Feature Branch workflow similar to:

Our related decisions can be summarized as:

• RESPEC's master branch will considered the official public facing release branch
  • Only RESPEC will have control of this branch
• RESPEC’s develop branch is the key development branch for all new features
• LimnoTech pull updates to their fork at LimnoTech/HSPsquared
• LimnoTech work in their forked repo, and will generally issue Pull Requests to /respec/HSPsquared/develop (and potential other feature branches).
  • LimnoTech will be responsible for merge conflicts generated by any Pull Request
  • LimnoTech may issue a Pull Request to Respec's master branch for updates to documentation
• RESPEC & LimnoTech will work on new features in Feature branches created from develop

We set up some of this workflow with https://github.com/respec/HSPsquared/pull/29 and associated branch creation.

We also decided to use create GitHub Issues in RESPEC's repo for tracking shared objectives and tasks, to main an archive of progress & solutions. LimnoTech will use their issue tracker only for smaller granular task tracking that don't add value to cumulative documentation.

cc: @rheaphy, @PaulDudaRESPEC, @steveskrip, @ptomasula

[aufdenkampe]

It seems we're all following these collaborative workflows. I'll close this issue.