High-level principles related to the development of the system

1. Software assets to be held on GitHub.
2. Software to be licensed under the Apache 2 license.
3. Code repositories will use the GitFlow branching model.
   1. Contributors make changes by submitting pull requests.
   2. Editors review pull requests for consistency prior to merging into develop.
   3. Periodically, editors create a release candidate (where appropriate, editors will seek wider review of release candidate assets including clinical review, Connectathon testing and so on).
   4. Following successful review, assets are marked as active and published to master branch.
4. Software assets will follow Semantic Versioning.
   1. Major versions will be maintained in parallel for a period of time before deprecation.
5. GitHub webhooks will be used to automatically build and publish software assets to a public test instance.