In order to contribute to HospitalRun codebase, developers need:
Everything you need to be a contributor member
To setup the development toolchain we recommend the use of Visual Studio Code as IDE, nvm for the management of different versions of Node, and yarn for a fast, reliable, and secure dependency management (install it as a global package with npm i -g yarn). Furthermore, you need an GitHub account that has SSH access enabled.
HospitalRun is a community project. We invite your participation through financial contributions, issues, and pull requests!
Contributions are always welcome. Before contributing please read the code of
conduct and
search the issue tracker; your issue
may have already been discussed or fixed in master
. If you're new to the project,
maybe you'd like to open a pull request to address one of good-first-issue.
To contribute, fork HospitalRun, commit your changes, and send a Pull Request.
In order to optimize the workflow and to prevent multiple contributors working on the same issue without interactions, a contributor must ask to be assigned to an issue by one of the core team members: it's enough to ask it inside the specific issue.
Feature requests should be submitted in the issue tracker, with a description of the expected behavior & use case, where they’ll remain closed until sufficient interest, e.g. :+1: reactions, has been shown by the community. Before submitting a request, please search for similar ones in the closed issues.
HospitalRun is a member of the Open JS Foundation. As such, we request that all contributors sign our contributor license agreement (CLA).
For more information about CLAs, please check out Alex Russell’s excellent post, “Why Do I Need to Sign This?”.