2020-03-02 20:47:43 +00:00
|
|
|
# How to Contribute
|
|
|
|
|
|
|
|
|
|
We'd love to accept your patches and contributions to this project. There are
|
|
|
|
|
just a few small guidelines you need to follow.
|
|
|
|
|
|
|
|
|
|
## Contributor License Agreement
|
|
|
|
|
|
|
|
|
|
Contributions to this project must be accompanied by a Contributor License
|
|
|
|
|
Agreement. You (or your employer) retain the copyright to your contribution;
|
|
|
|
|
this simply gives us permission to use and redistribute your contributions as
|
|
|
|
|
part of the project. Head over to <https://cla.developers.google.com/> to see
|
|
|
|
|
your current agreements on file or to sign a new one.
|
|
|
|
|
|
|
|
|
|
You generally only need to submit a CLA once, so if you've already submitted one
|
|
|
|
|
(even if it was for a different project), you probably don't need to do it
|
|
|
|
|
again.
|
|
|
|
|
|
|
|
|
|
## Code reviews
|
|
|
|
|
|
|
|
|
|
All submissions, including submissions by project members, require review. We
|
2020-04-06 18:43:20 +00:00
|
|
|
use [Dawn's Gerrit](https://dawn-review.googlesource.com/) for this purpose.
|
|
|
|
|
|
|
|
|
|
Tint generally follows the Google C++ style guide. There is a clang-format file
|
|
|
|
|
provided and a `tools/format` script which will run the formatter. There is also
|
|
|
|
|
a `tools/lint` script to run a linter. Overall try to use the same style and
|
|
|
|
|
convention as code around your change.
|
2020-03-02 20:47:43 +00:00
|
|
|
|
|
|
|
|
## Community Guidelines
|
|
|
|
|
|
|
|
|
|
This project follows
|
|
|
|
|
[Google's Open Source Community Guidelines](https://opensource.google.com/conduct/).
|
