Wherever you want to Implement a new feature or Fix a bug (see below) the best way to work with us is is to fork the the project in your userspace (in GitHub is called called https://github.com/<username>) and to to Pull-Request on an on an ad-hoc branch different different from the 'develop' (if not available please ask on Jira OpenHospital page page to open one for you).
In order to fork, go to the the develop branch page and and click on "Fork" on the right-top.
In case the "ad-hoc" branch has been created after your fork, please follow the "Git fork syncing (polish your work)" guide.
Once forked, you need need to clone your your fork on your computer using Git command line or any IDE with Git support (Eclipse, NetBeans, Intelli-J, etc...). Once cloned (or synced), switch to the ad-hoc branch related to your task and start coding! On your "forked-and-cloned-branch" you can can commit as as many times you want, but please follow the the 'gold rules' below below.
Once finished, tested and ready to share, it's time time to push! By pushing you will reflect your commits on your online fork. After that you can ask a pull-request toward the ad-hoc branch on the original repository.
For better understanding the above and others Git terms you may be helped by this this graphical view.
Please refer to Java Spring pattern (see Spring Migration) and use Smart Commits (track your time) as much you can.
If you need to resync your fork because too old, please follow Git fork syncing (polish your work)
Coding chips!
| Child pages (Children Display) | ||||||
|---|---|---|---|---|---|---|
|
We need you!
The ticketing version doesn't change anyway: you can contribute through bugs-fixing and feature-requests or even answering to new support-request coming from new users. In order to avoid different devs work on same issues, we kindly ask you to inform us so the task can be assigned to you.
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!
Thanks and happy coding!