From fee207e8bdb780389ad385bd831c8f11f0793ac6 Mon Sep 17 00:00:00 2001 From: Steven Bazyl Date: Fri, 15 Feb 2013 15:21:21 -0800 Subject: [PATCH] Add guide for would-be contributors --- CONTRIB.md | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 CONTRIB.md diff --git a/CONTRIB.md b/CONTRIB.md new file mode 100644 index 0000000000..1e65911f85 --- /dev/null +++ b/CONTRIB.md @@ -0,0 +1,32 @@ +# How to become a contributor and submit your own code + +## Contributor License Agreements + +We'd love to accept your sample apps and patches! Before we can take them, we +have to jump a couple of legal hurdles. + +Please fill out either the individual or corporate Contributor License Agreement +(CLA). + + * If you are an individual writing original source code and you're sure you + own the intellectual property, then you'll need to sign an [individual CLA] + (http://code.google.com/legal/individual-cla-v1.0.html). + * If you work for a company that wants to allow you to contribute your work, + then you'll need to sign a [corporate CLA] + (http://code.google.com/legal/corporate-cla-v1.0.html). + +Follow either of the two links above to access the appropriate CLA and +instructions for how to sign and return it. Once we receive it, we'll be able to +accept your pull requests. + +## Contributing A Patch + +1. Submit an issue describing your proposed change to the repo in question. +1. The repo owner will respond to your issue promptly. +1. If your proposed change is accepted, and you haven't already done so, sign a + Contributor License Agreement (see details above). +1. Fork the desired repo, develop and test your code changes. +1. Ensure that your code is clear and comprehensible. +1. Ensure that your code has an appropriate set of unit tests which all pass. +1. Submit a pull request. + -- 2.30.2