diff options
author | antirez <antirez@gmail.com> | 2012-10-06 12:04:27 +0200 |
---|---|---|
committer | antirez <antirez@gmail.com> | 2012-10-06 12:04:38 +0200 |
commit | f4eb4b335264f2a88316a7fd8752d740f1a3cb63 (patch) | |
tree | 127095254b290249386ad70dc92791a6bcbeb8cb | |
parent | 500dddc26499319a7e60be996487078e07e921ac (diff) | |
download | redis-f4eb4b335264f2a88316a7fd8752d740f1a3cb63.tar.gz |
CONTRIBUTING file updated.
-rw-r--r-- | CONTRIBUTING | 20 |
1 files changed, 17 insertions, 3 deletions
diff --git a/CONTRIBUTING b/CONTRIBUTING index 623c5a6ec..1ecd13945 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -1,8 +1,22 @@ -1. Enter irc.freenode.org #redis and start talking with 'antirez' and/or 'pietern' to check if there is interest for such a feature and to understand the probability of it being merged. We'll try hard to keep Redis simple... so you'll likely encounter high resistance. +# IMPORTANT: HOW TO USE REDIS GITHUB ISSUES -2. Drop a message to the Redis Google Group with a proposal of semantics/API. +* Github issues SHOULD ONLY BE USED to report bugs, and for DETAILED feature + requests. Everything else belongs to the Redis Google Group. -3. If steps 1 and 2 are ok, use the following procedure to submit a patch: + PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected + bugs in the Github issues system. We'll be very happy to help you and provide + all the support in the Redis Google Group. + + Redis Google Group address: + + https://groups.google.com/forum/?fromgroups#!forum/redis-db + +# How to provide a patch for a new feature + +1. Drop a message to the Redis Google Group with a proposal of semantics/API. + +2. If in steps 1 you get an acknowledge from the project leaders, use the + following procedure to submit a patch: a. Fork Redis on github ( http://help.github.com/fork-a-repo/ ) b. Create a topic branch (git checkout -b my_branch) |