summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2015-10-27 12:06:26 +0100
committerantirez <antirez@gmail.com>2015-10-27 12:07:54 +0100
commitc5f9f199df65d8ef4d39048776dc0e8ad94289fb (patch)
treef0e7b84c5f45159a54d2e0c2deffbc4365d2ab2f
parentc7ec1a367af33c66db228084ba9fbb72f8d1fc33 (diff)
downloadredis-c5f9f199df65d8ef4d39048776dc0e8ad94289fb.tar.gz
CONTRIBUTING updated.
-rw-r--r--CONTRIBUTING14
1 files changed, 9 insertions, 5 deletions
diff --git a/CONTRIBUTING b/CONTRIBUTING
index f7b6836f7..b33aacb3e 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -12,15 +12,17 @@ each source file that you contribute.
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.
+ all the support Reddit sub:
- Redis Google Group address:
-
- https://groups.google.com/forum/?fromgroups#!forum/redis-db
+ http://reddit.com/r/redis
+
+ There is also an active community of Redis users at Stack Overflow:
+
+ http://stackoverflow.com/questions/tagged/redis
# How to provide a patch for a new feature
-1. Drop a message to the Redis Google Group with a proposal of semantics/API.
+1. If it is a major feature or a semantical change, please post it as a new submission in r/redis on Reddit at http://reddit.com/r/redis. Try to be passionate about why the feature is needed, make users upvote your proposal to gain traction and so forth. Read feedbacks about the community. But in this first step **please don't write code yet**.
2. If in step 1 you get an acknowledge from the project leaders, use the
following procedure to submit a patch:
@@ -31,4 +33,6 @@ each source file that you contribute.
d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ )
e. Done :)
+For minor fixes just open a pull request on Github.
+
Thanks!