Summary
| Table of Contents |
|---|
...
Wherever you want to Implement a new feature or Fix a bug (see below) the best way to work with us is to fork the project in your userspace (in GitHub is called https://github.com/<username>) and to Pull-Request on an ad-hoc branch different from the 'develop' (if not available please ask on Jira OpenHospital page to open one for you).
Please refer to Java Spring pattern (see Spring Migration) and use Smart Commits as much you can.
And don't forget the 'gold rules'!
- Fork, develop & merge-request (pull-request)
- Double analyze the existing code, don't write what is already written, be DRY (Don't Repeat Yourself)
- Dumb code is better than clever one when is time to share
- Write comments when only "YOU" know what you are doing
- Optimize only after achieved
- Less is more!
If you need more instructions please read here.
Write documentation
OpenHospital has a community based documentation created through a wiki (right where this page is).
...
At this point, the OpenHospital developers will see your pull request and work with you (either in JIRA comments, or in Github comments) to ensure your fix is clean and ready for integration. After responding to any issues, your code will be committed. You should no longer need to update the JIRA ticket and can rest assured your contribution is highly valued and will be acted upon in a timely manner!
Translate the software
We are really thankful for your contributions up to now and everyday we work to evolve OpenHospital software and to ease contributors work. For this reason we decided to start using Transifex as translation tool for our leading product.
Briefly:
- Create an account on Transifex and join the team: Transifex OpenHospital Project
- Happy translations!
The platform is very user-friendly, just try it! If you run into problems please read these instructions.