Thank you for checking out our Curation Admin Tools work. We welcome contributions from everyone! By participating in this project, you agree to abide by the Mozilla Community Participation Guidelines.
-
Slack channel (Mozilla staff only): #p-curation-tools
-
File issues/questions on Github: https://github.com/Pocket/curation-admin-tools/issues. We typically triage new issues every Monday.
If you've found a bug, or have a feature idea that you you'd like to see, follow these simple guidelines:
-
Pick a thoughtful and concise title for the issue (ie. not Thing Doesn't Work!)
-
Make sure to mention your browser version, OS and basic system parameters (eg. Chrome 62, Windows XP, 512KB RAM)
-
If you can reproduce the bug, give a step-by-step recipe
-
Include stack traces from the console(s) where appropriate
-
Screenshots and screen recordings welcome!
-
When in doubt, take a look at some existing issues and emulate
If you are new to the repo, you might want to pay close attention to these tags, as they are typically a great way to get started: Good First Bug, Bug, Chore, and Polish. If you see a bug that is not yet assigned to anyone, start a conversation with an engineer in the ticket itself, expressing your interest in taking the bug. If you take the bug, someone will set the ticket to Assigned to Contributor, so we can be proactive about helping you succeed in fixing the bug.
When you have some code written, you can open up a Pull Request, get your code reviewed, and see your code merged into the codebase.
Please review the README for instructions on setting up your development environment, installing dependencies and building the extensions.
You have identified the bug, written code and now want to get it into the main repo using a Pull Request.
All code is added using a pull request against the main branch of our repo. Before submitting a PR, please go through this checklist:
-
All unit tests must pass (and if you haven't written a unit test, please do!)
-
Fill out the pull request template as outlined
-
Please add a PR / Needs Review tag to your PR (if you have permission). This starts the code review process. If you cannot add a tag, don't worry, we will add it during triage.
-
Make sure your PR will merge gracefully with main at the time you create the PR, and that your commit history is 'clean'
You have created a PR and submitted it to the repo, and now are waiting patiently for you code review feedback. One of the projects module owners will be along and will either:
-
Make suggestions for some improvements
-
Give you a 👍 in the comments section, indicating the review is done and the code can be merged
Typically, you will iterate on the PR, making changes and pushing your changes to new commits on the PR. When the reviewer is satisfied that your code is good-to-go, you will get the coveted R+ comment, and your code can be merged. If you have commit permission, you can go ahead and merge the code to main, otherwise, it will be done for you.
Our project prides itself on it's respectful, patient and positive attitude when it comes to reviewing contributor's code, and as such, we expect contributors to be respectful, patient and positive in their communications as well.
We like this overview by Chris Beams on "How to Write a Git Commit Message".
The tl;dr is:
The project team meets weekly (in a closed meeting, for the time being), to discuss project priorities, to triage new tickets, and to redistribute the work amongst team members. Any contributors tickets or PRs are carefully considered, prioritized, and if needed, assigned a reviewer.