HSLynk is an open source project and your contribution is very much appreciated.
- Check for open issues (in a separate repo at https://github.com/servinglynk/hmis-lynk-open-source-docs/issues, to keep the code repo lean) or open a fresh issue to start a discussion around a feature idea or a bug.
To-do: add issue submission guidelines.
- Fork the repository on Github and make your changes in a branch. We use Vincent Driessen's branching methodology illustrated here: http://nvie.com/posts/a-successful-git-branching-model/ . For branch and tag names, please use: https://github.com/servinglynk/hmis-lynk-open-source-docs/wiki/Release-and-branching-conventions .
To-do: add Lint code validation instructions.
- Send a pull request (with the branch as the target).
To-do: add pull request review process description.
- Please document early and often on the wiki at https://github.com/servinglynk/hmis-lynk-open-source-docs/wiki
A big thank you goes out to everyone who has helped with the project, the doc contributors and code contributors and everyone who took the time to report issues and give feedback. (adapted from this)
HSLynk is published under version 2 of the Mozilla Public License. It is important that the codebase continue to be publishable under that license. To make that possible, here are some guidelines on including 3rd party code in the codebase.
If you submit code that you wrote or that you have authority to submit from your employer or institution, you give it to us under version 2 of the Mozilla Public License. If the material you submit is already licensed under a more permissive license (BSD, MIT, ISC), you can tell us that and give it to us under that license instead.
Please make the license of the code clear in your pull request. Tell us who wrote it, if that isn't just you. If the code was written for an employer, tell us that too. Tell us what license applies to the code, especially if it differs from the project's Mozilla Public License, version 2.
If you submit third-party code that doesn't come from you or your employer, and it does not contain a license statement, please tell us the license that applies to the code and provide links to whatever resources you used to find that out. For some examples, see the LICENSE and METADATA parts of Google's guide to introducing third-party code. (adapted from this)