1Note: by contributing code to the Redis project in any form, including sending 2a pull request via Github, a code fragment or patch via private email or 3public discussion groups, you agree to release your code under the terms 4of the BSD license that you can find in the COPYING file included in the Redis 5source distribution. You will include BSD license in the COPYING file within 6each source file that you contribute. 7 8# IMPORTANT: HOW TO USE REDIS GITHUB ISSUES 9 10* Github issues SHOULD ONLY BE USED to report bugs, and for DETAILED feature 11 requests. Everything else belongs to the Redis Google Group. 12 13 PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected 14 bugs in the Github issues system. We'll be very happy to help you and provide 15 all the support Reddit sub: 16 17 http://reddit.com/r/redis 18 19 There is also an active community of Redis users at Stack Overflow: 20 21 http://stackoverflow.com/questions/tagged/redis 22 23# How to provide a patch for a new feature 24 251. 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**. 26 272. If in step 1 you get an acknowledge from the project leaders, use the 28 following procedure to submit a patch: 29 30 a. Fork Redis on github ( http://help.github.com/fork-a-repo/ ) 31 b. Create a topic branch (git checkout -b my_branch) 32 c. Push to your branch (git push origin my_branch) 33 d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ ) 34 e. Done :) 35 36For minor fixes just open a pull request on Github. 37 38Thanks! 39