Skip to content

Latest commit

 

History

History
51 lines (34 loc) · 3.65 KB

CONTRIBUTING.md

File metadata and controls

51 lines (34 loc) · 3.65 KB
Raw

Join the development

  • Before you join the development, please set up the project on your local machine, run it and go through the application completely. Press on any button you can find and see where it leads to. Explore! You'll be more familiar with what is where and might even get some cool ideas on how to improve various aspects of the app.
  • If you would like to work on an issue, drop in a comment at the issue. If it is already assigned to someone, but there is no sign of any work being done, please free to drop in a comment so that the issue can be assigned to you if the previous assignee has dropped it entirely.

Contributing

Contribute with Gitpod

When contributing to this repository, please first discuss the change you wish to make via issue, or the official Slack channel.

Get started running server in development mode, see Dev environment quick start guide

Pull Request Process

  1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
  2. Check that there are no conflicts and your request passes Travis build. Check the log of the pass test if it fails the build.
  3. Give the description of the issue that you want to resolve in the pull request message.
    • The format of the commit message to be fixed is fix:[Description of the issue] Fixes #[issue number] Example: fix: Add toast warning in MainActivity.java Fixes #529
    • We are following conventional commit with a set of standard prefixes (fix, feat, doc, build, test…), with the addition of:
      • l10n for translations
      • taxonomy for PR modifying a taxonomy
  4. Wait for the maintainers to review your pull request and do the changes if requested.

Contributions Best Practices

Check before committing

You can save you sometime by running some checks locally before committing.

make checks should work.

Commits

  • Write clear meaningful git commit messages (Do read here).
  • Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged(For more info click here).
  • When you make very, very minor changes to a PR of yours (like for example fixing a failing Travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix(Learn how to squash at here).
  • When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers, and you'll also get reviews quicker.

Feature Requests and Bug Reports

When you file a feature request or when you are submitting a bug report to the issue tracker, make sure you add steps to reproduce it. Especially if that bug is some weird/rare one.

Code of Conduct

For our Code of Conduct, you should head over here.