summaryrefslogtreecommitdiff
path: root/CONTRIBUTING
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2010-09-23 18:24:47 +0200
committerantirez <antirez@gmail.com>2010-09-23 18:24:47 +0200
commit30d31cc8bb416f67183a218f1511ef517eb9ae3b (patch)
tree187c363e0f4f43152d7287cee8cc9be0a684bb13 /CONTRIBUTING
parent963238f713f02e538cf0f5851f3337173116ea39 (diff)
downloadredis-30d31cc8bb416f67183a218f1511ef517eb9ae3b.tar.gz
Contributing file added
Diffstat (limited to 'CONTRIBUTING')
-rw-r--r--CONTRIBUTING13
1 files changed, 13 insertions, 0 deletions
diff --git a/CONTRIBUTING b/CONTRIBUTING
new file mode 100644
index 000000000..644b59911
--- /dev/null
+++ b/CONTRIBUTING
@@ -0,0 +1,13 @@
+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 an high resistence.
+
+2. Drop a message to the Redis Google Group with a proposal of semantics/API.
+
+3. If steps 1 and 2 are ok, use the following procedure to submit a patch:
+
+ a. Fork Redis on github
+ b. Create a topic branch (git checkout -b my_branch)
+ c. Push to your branch (git push origin my_branch)
+ d. Create an issue in the Redis google code site with a link to your patch
+ e. Done :)
+
+Thanks!