summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authordanielsdeleo <dan@opscode.com>2012-09-17 13:56:45 -0700
committerdanielsdeleo <dan@opscode.com>2012-09-17 13:56:45 -0700
commitaf6097a2c57fb0f0af4c79be07ce6064007b0519 (patch)
treea3f7d6fe31ba10ccde673ea2d7b076eaf1d3d5c9
parenta0747549867ac8ae624afea984238d872366f8ad (diff)
downloadchef-levelup-contributing.tar.gz
explain the contributing process in CONTRIBUTING.mdlevelup-contributing
-rw-r--r--CONTRIBUTING.md21
1 files changed, 21 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b803182c75..b60c5a02c0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,3 +1,24 @@
+# How to Contribute
+
+## Prerequisites
+* Create an account on our [bug tracker](http://tickets.opscode.com)
+* Sign our contributor agreement (CLA). You can [sign it
+online](https://secure.echosign.com/public/hostedForm?formid=PJIF5694K6L).
+It only takes a few minutes, and you don't give away rights to your
+contribution. If you're contributing on behalf of your employer, have
+your employer fill out our [Corporate
+CLA](https://secure.echosign.com/public/hostedForm?formid=PIE6C7AX856)
+
+## Submitting Your Patch
+* Create a ticket for your change. This helps us track the changes in
+each release and give you credit when your contribution ships.
+* When your patch is ready, mark the ticket as resolved on the ticket
+tracker. Include a link to your patch (github branch, pull request) in
+your comment.
+* If you're submitting a pull request, be sure to reference the ticket
+number in your pull request.
+
+# References
Chef Project home pages:
* Wiki: http://wiki.opscode.com/display/chef