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 https://groups.google.com/forum/m/#!forum/Redis-db 14 15 PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected 16 bugs in the Github issues system. We'll be very happy to help you and provide 17 all the support in the mailing list. 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 don't start coding 26straight away: if your feature is not a conceptual fit you'll lose a lot of 27time writing the code without any reason. Start by posting in the mailing list 28and creating an issue at Github with the description of, exactly, what you want 29to accomplish and why. Use cases are important for features to be accepted. 30Here you'll see if there is consensus about your idea. 31 322. If in step 1 you get an acknowledgment from the project leaders, use the 33 following procedure to submit a patch: 34 35 a. Fork Redis on github ( http://help.github.com/fork-a-repo/ ) 36 b. Create a topic branch (git checkout -b my_branch) 37 c. Push to your branch (git push origin my_branch) 38 d. Initiate a pull request on github ( https://help.github.com/articles/creating-a-pull-request/ ) 39 e. Done :) 40 413. Keep in mind that we are very overloaded, so issues and PRs sometimes wait 42for a *very* long time. However this is not lack of interest, as the project 43gets more and more users, we find ourselves in a constant need to prioritize 44certain issues/PRs over others. If you think your issue/PR is very important 45try to popularize it, have other users commenting and sharing their point of 46view and so forth. This helps. 47 484. For minor fixes just open a pull request on Github. 49 50Thanks! 51