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 in the Redis Google Group. 16 17 Redis Google Group address: 18 19 https://groups.google.com/forum/?fromgroups#!forum/redis-db 20 21# How to provide a patch for a new feature 22 231. If it is a major feature or a semantical change, write an RCP (Redis Change Proposal). Check the documentation here: https://github.com/redis/redis-rcp 24 252. If in step 1 you get an acknowledge from the project leaders, use the 26 following procedure to submit a patch: 27 28 a. Fork Redis on github ( http://help.github.com/fork-a-repo/ ) 29 b. Create a topic branch (git checkout -b my_branch) 30 c. Push to your branch (git push origin my_branch) 31 d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ ) 32 e. Done :) 33 34For minor fixes just open a pull request on Github. 35 36Thanks! 37