Welcome to the repository! We're excited you're here and want to contribute.
We hope that these guidelines make it as easy as possible to get involved. If you have any questions that aren't discussed below, please let us know by opening an issue.
We welcome all contributions from documentation to testing to writing code. Don't let trying to be perfect get in the way of being good - exciting ideas are more important than perfect pull requests.
- Issues are individual pieces of work that need to be completed to move the project forwards. A general guideline: if you find yourself tempted to write a great big issue that is difficult to describe as one unit of work, please consider splitting it into two or more issues.
Before you open a new issue, please check if any of our open issues covers your idea already.
The list of labels for current issues includes:
-
These issues contain a task that a member of the team has determined we need additional help with.
If you feel that you can contribute to one of these issues, we especially encourage you to do so!
-
These issues contain a question that you'd like to have answered.
Opening an issue is a great way to start a conversation and get your answer.
-
These issues are particularly appropriate if it is your first contribution to the repository, or to GitHub overall.
-
These issues are suggesting new features that can be added to the project.
If you want to ask for something new, please try to make sure that your request is distinct from any others that are already in the queue. If you find one that's similar but there are subtle differences please reference the other enhancement in your issue.
-
These issues are reporting a problem or a mistake in the project.
The more details you can provide the better! If you know how to fix the bug, please open an issue first and then submit a pull request.
-
_We like to model best practice, so the package itself is managed through these issues.
We appreciate all contributions to monitoring-ecosystem-resilience. THANK YOU for helping us.
All project management, conversations and questions related to the project happens here in the monitoring-ecosystem-resilience repository.
In brief, the structure for making a contribution is as follows:
- Identify a specific change that needs to be made to the repository. Open a new issue (after checking one does not already exist!) and describe the change, include why you are making it.
- Create a new branch corresponding to this issue. The new branch will house all the changes that you make to the repository in an isolated location. As discussed in more detail below, new branches should be created using the latest version of the
developbranch. - Make commits to the new branch you have created.
- Submit a pull request to add the modifications in your new branch back into
develop.
When a significant milestone has been reached, and the develop branch is known to be in a stable configuration, the master branch will be updated via a pull request from develop. In general, commits should not be made to either the master or develop branches. Pull requests to develop are fine (and encoraged), while pull requests to master will happen in a coordinated way.
The following steps are a more detailed guide to help you contribute in a way that will be easy for everyone to review and accept with ease.
1. Comment on an existing issue or open a new issue referencing your addition
This allows other members of the team to confirm that you aren't overlapping with work that's currently underway and that everyone is on the same page with the goal of the work you're going to carry out.
This blog is a nice explanation of why putting this work in up front is so useful to everyone involved.
2. Create a new branch or Fork the monitoring-ecosystem-resilience repository to your profile
If you are a collaborator on the repository with write access, then you can make a new branch. We recommend that you start from the latest version of the develop branch, and create a new one from there. This is the branch we use for active deleopment of the repository, while stable (but not cutting edge) versions are in the master branch. The name of your new branch should ideally be in the format: <feature|bugfix>/<issue-number>-<short-description>. For example, if you were addressing Issue number 111 which was about incorrect JSON filenames, it could be something like:
git checkout develop
git pull
git checkout -b bugfix/111-fix-json-filenames
Now you can go to step #3, where you actually fix the problem! :)
In case you want to learn more about "branching out", this blog details the different Git branching models.
If you don't have write access to the repository, you can fork it to your own profile. This is now your own unique copy of the repo. Changes here won't affect anyone else's work, so it's a safe space to explore edits to the code!
Make sure to keep your fork up to date with the master repository, otherwise you can end up with lots of dreaded merge conflicts.
Try to keep the changes focused. If you submit a large amount of work all in one go it will be much more work for whomever is reviewing your pull request.
While making your changes, commit often and write good, detailed commit messages. This blog explains how to write a good Git commit message and why it matters. It is also perfectly fine to have a lot of commits - including ones that break code. A good rule of thumb is to push up to GitHub when you do have passing tests then the continuous integration (CI) has a good chance of passing everything.
Please do not re-write history! That is, please do not use the rebase command to edit previous commit messages, combine multiple commits into one, or delete or revert commits that are no longer necessary.
4. Submit a pull request
A "pull request" is a request to "pull" the changes you have made in your branch back into another branch of the repository. The source branch will be the new branch you created in order to address the issue you created/choose. The destination branch should generally be develop, where all main code development takes place. Avoid making pull requests into the master branch (pull requests into master should happen in a coordinated way using a stable configuration of develop as the source branch).
We encourage you to open a pull request as early in your contributing process as possible. This allows everyone to see what is currently being worked on. It also provides you, the contributor, feedback in real time from both the community and the continuous integration as you make commits (which will help prevent stuff from breaking).
When you are ready to submit a pull request, make sure the contents of the pull request body do the following:
- Describe the problem you're trying to fix in the pull request, reference any related issues and use keywords fixes/close to automatically close them, if pertinent.
- List changes proposed in the pull request.
- Describe what the reviewer should concentrate their feedback on.
If you have opened the pull request early and know that its contents are not ready for review or to be merged, add "[WIP]" at the start of the pull request title, which stands for "Work in Progress". When you are happy with it and are happy for it to be merged into the main repository, change the "[WIP]" in the title of the pull request to "[Ready for review]".
A member of the team will then review your changes to confirm that they can be merged into the main repository. A review will probably consist of a few questions to help clarify the work you've done. Keep an eye on your GitHub notifications and be prepared to join in that conversation.
You can update your fork of the repository and the pull request will automatically update with those changes. You don't need to submit a new pull request when you make a change in response to a review.
You can also submit pull requests to other contributors' branches! Do you see an open pull request that you find interesting and want to contribute to? Simply make your edits on their files and open a pull request to their branch!
What happens if the continuous integration (CI) fails (for example, if the pull request notifies you that "Some checks were not successful")? The CI could fail for a number of reasons. At the bottom of the pull request, where it says whether your build passed or failed, you can click “Details” next to the test, which takes you to the Travis page. You can view the log or rerun the checks if you have write access to the repo by clicking the “Restart build” button in the top right (you must be logged in to Travis CI with your GitHub account see the “Restart build” button).
GitHub has a nice introduction to the pull request workflow, but please get in touch if you have any questions.
Docstrings should follow numpydoc convention. We encourage extensive documentation.
The python code itself should follow PEP8 convention whenever possible, with at most about 500 lines of code (not including docstrings) per script.
These Contributing Guidelines have been adapted from the Contributing Guidelines of The Turing Way! (License: MIT)