|
| 1 | +# Contributing guidelines |
| 2 | + |
| 3 | +We welcome any kind of contribution to our software, from simple comment or question to a full fledged [pull request](https://help.github.com/articles/about-pull-requests/). |
| 4 | + |
| 5 | +A contribution can be one of the following cases: |
| 6 | + |
| 7 | +1. you have a question; |
| 8 | +1. you think you may have found a bug (including unexpected behavior); |
| 9 | +1. you want to make some kind of change to the code base (e.g. to fix a bug, to add a new feature, to update documentation); |
| 10 | +1. you want to make a new release of the code base. |
| 11 | + |
| 12 | +The sections below outline the steps in each case. |
| 13 | + |
| 14 | +## You have a question |
| 15 | + |
| 16 | +1. use the search functionality [here](https://github.com/mitigation-controller/mitc/issues) to see if someone already filed the same issue; |
| 17 | +1. if your issue search did not yield any relevant results, make a new issue; |
| 18 | +1. apply the "Question" label; apply other labels when relevant. |
| 19 | + |
| 20 | +## You think you may have found a bug |
| 21 | + |
| 22 | +1. use the search functionality [here](https://github.com/mitigation-controller/mitc/issues) to see if someone already filed the same issue; |
| 23 | +1. if your issue search did not yield any relevant results, make a new issue, making sure to provide enough information to the rest of the community to understand the cause and context of the problem. Depending on the issue, you may want to include: |
| 24 | + - make use of the bug report template; |
| 25 | + - the [SHA hashcode](https://help.github.com/articles/autolinked-references-and-urls/#commit-shas) of the commit that is causing your problem; |
| 26 | + - some identifying information (name and version number) for dependencies you're using; |
| 27 | + - information about the operating system; |
| 28 | +1. apply relevant labels to the newly created issue. |
| 29 | + |
| 30 | +## You want to make some kind of change to the code base |
| 31 | + |
| 32 | +1. (**important**) announce your plan to the rest of the community *before you start working*. This announcement should be in the form of a (new) issue; |
| 33 | +1. (**important**) wait until some kind of consensus is reached about your idea being a good idea; |
| 34 | +1. if needed, fork the repository to your own Github profile and create your own feature branch off of the latest dev commit. While working on your feature branch, make sure to stay up to date with the dev branch by pulling in changes, possibly from the 'upstream' repository (follow the instructions [here](https://help.github.com/articles/configuring-a-remote-for-a-fork/) and [here](https://help.github.com/articles/syncing-a-fork/)); |
| 35 | +1. we make use of the Gitflow branching method, see [here](https://github.com/mitigation-controller/mitc/wiki/Branch-Management) |
| 36 | +1. make sure the existing tests still work by running `run_tests.m`; |
| 37 | +1. add your own tests (if necessary); |
| 38 | +1. update or expand the documentation; |
| 39 | +1. update the `CHANGELOG.md` file with change; |
| 40 | +1. [push](https://docs.github.com/en/github/using-git/pushing-commits-to-a-remote-repository#pushing-tags) your feature branch to (your fork of) the MitC repository on GitHub; |
| 41 | +1. create the pull request to the `dev` branch, e.g. following the instructions [here](https://help.github.com/articles/creating-a-pull-request/). |
| 42 | + |
| 43 | +In case you feel like you've made a valuable contribution, but you don't know how to write or run tests for it, or how to generate the documentation: don't let this discourage you from making the pull request; we can help you! Just go ahead and submit the pull request, but keep in mind that you might be asked to append additional commits to your pull request. |
| 44 | + |
| 45 | +## You want to make a new release of the code base |
| 46 | + |
| 47 | +To create release you need write permission on the repository. |
| 48 | + |
| 49 | +1. Create a release branch from the dev branch. |
| 50 | +1. Check author list in `citation.cff` and `.zenodo.json` files |
| 51 | +1. Follow the compiling and packaging steps described [here](https://github.com/mitigation-controller/mitc/wiki/Compile-and-package) |
| 52 | +1. Update the `CHANGELOG.md` to include changes made |
| 53 | +1. Follow the steps [here](https://github.com/mitigation-controller/mitc/wiki/Compile-and-package) to package and compile the application. |
| 54 | +1. Goto [GitHub release page](https://github.com/mitigation-controller/mitc/releases) |
| 55 | +1. Press draft a new release button |
| 56 | +1. Fill version, title and description field |
| 57 | +1. Press the Publish Release button |
| 58 | + |
| 59 | +A Zenodo entry will be made for the release with its own DOI. |
| 60 | + |
| 61 | +These contributing guidelines are based on the description in this [repository](https://github.com/matchms/matchms/blob/master/CONTRIBUTING.md) |
0 commit comments