Name		Name	Last commit message	Last commit date
parent directory ..
attachments		attachments
how-to		how-to
img		img
legal		legal
mockup		mockup
user-guides		user-guides
README.md		README.md
continuous-integration.md		continuous-integration.md
make-shortcuts.md		make-shortcuts.md
proethos2-update-es.md		proethos2-update-es.md
proethos2-update.md		proethos2-update.md
relations-between-proethos2-and-XML-ICTRP.md		relations-between-proethos2-and-XML-ICTRP.md
translation-guide.md		translation-guide.md
ubuntu-troubleshooting.md		ubuntu-troubleshooting.md
user-guides.md		user-guides.md

README.md

Development Guide and How to Contribute

Contributing

If you want to contribute to Proethos2 and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on Github, new technologies and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request.

How to make a clean pull request

Look for a project's contribution instructions. If there are any, follow them.

Create a personal fork of Proethos2 on Github.
Clone the fork on your local machine. Your remote repo on Github is called origin.
Add the original repository as a remote called upstream.
If you created your fork a while ago be sure to pull upstream changes into your local repository.
Create a new branch to work on! Branch from develop if it exists, else from master.
Implement/fix your feature, comment your code.
Follow the code style of Proethos2, including indentation.
Run the tests!
Write or adapt tests as needed.
Add or change the documentation as needed.
Push your branch to your fork on Github, the remote origin.
From your fork open a pull request in the correct branch. Target Proethos2's develop branch if there is one, else go for master!
If the maintainer requests further changes just push them to your branch. The PR will be updated automatically.
Once the pull request is approved and merged you can pull the changes from upstream to your local repo and delete your extra branch(es).

And last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code.