Skip to content

Latest commit

 

History

History
50 lines (40 loc) · 2.05 KB

CONTRIBUTING.md

File metadata and controls

50 lines (40 loc) · 2.05 KB

Contributing to GTT Project

We want to make contributing to this project as approachable and transparent as possible.

Code of Conduct

GTT Project has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.

Our Development Process

We use GitHub to sync code to and from our internal repository. We'll use GitHub to track issues and feature requests, as well as accept pull requests.

Pull Requests

We actively welcome your pull requests.

  1. Fork the repo and create your branch from develop.
  2. If you've added code that should be tested, add tests.
  3. If you've changed APIs, update the documentation.
  4. Ensure the test suite passes.
  5. Make sure your code lints.
  6. “sign off” your commits to indicate that you agree to the terms of the DCO.

Developer Certificate of Origin (DCO)

Before we can include your contribution in the GTT Project, you need to give us your permission. To indicate that you agree to the terms of the DCO, you “sign off” your contribution by adding a line with your name and e-mail address to every Git commit message:

git commit --signoff

Issues

We use GitHub issues to track public bugs. Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue. If possible please provide a minimal demo of the problem.

Coding Style

Start reading our code and you'll get the hang of it. We optimize for readability: This is open source software. Consider the people who will read your code, and make it look nice for them.

License

By contributing to GTT Project, you agree that your contributions will be licensed under the license indicated in the repositories LICENSE file.

References

This document was adapted from the open-source contribution guidelines for Facebook's Draft