From a97e332df4ebc1842368dd9b16ead65b6ea572ce Mon Sep 17 00:00:00 2001 From: James Zern Date: Mon, 29 Jun 2020 19:43:18 -0700 Subject: [PATCH] add CONTRIBUTING.md serves as a brief introduction and adds a link to the gerrit instructions on webmproject.org. Bug: webm:1669 Change-Id: If1d483eb48e2edcda8c51e66bdd1a86b7c35b986 (cherry picked from commit 220b00dd0d624a24a081fa60e35b024357c506ad) --- CONTRIBUTING.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 000000000..577c96a6b --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,30 @@ +# 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 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 +use a [Gerrit](https://www.gerritcodereview.com) instance hosted at +https://chromium-review.googlesource.com for this purpose. + +See https://www.webmproject.org/code/contribute/submitting-patches for an +example of a typical gerrit workflow. + +## Community Guidelines + +This project follows +[Google's Open Source Community Guidelines](https://opensource.google.com/conduct/). -- 2.40.0