Code contributions

⚠️ This page is stale and is kept for reference only. The branching model described here refers to v5-era clarin-dev branch.

• fork the project (or synchronize your fork with ufal/clarin-dspace)
• create topic/feature branch off of clarin-dev branch git checkout -b myFeature clarin-dev (or just git checkout -b myFeature if you are on clarin-dev)
• commit your changes locally, add reasonable description, and eventually publish (push) your changes ( you'll need to get familiar with git add, git commit, git push. Google is your friend or https://git-scm.com/doc)
• create a pull request. Be sure to select ufal/clarin-dspace and not DSpace/DSpace or any other of the available forks. You should create the pull request against clarin-dev branch
• the pull requests will eventually be reviewed, discussed and/or merged
• there will be testathons and the tested features will be merged to clarin branch. This branch should always be deployable and tested.