1. Note: by contributing code to the Redis project in any form, including sending
  2. a pull request via Github, a code fragment or patch via private email or
  3. public discussion groups, you agree to release your code under the terms
  4. of the BSD license that you can find in the COPYING file included in the Redis
  5. source distribution. You will include BSD license in the COPYING file within
  6. each source file that you contribute.
  8. * Github issues SHOULD ONLY BE USED to report bugs, and for DETAILED feature
  9. requests. Everything else belongs to the Redis Google Group:
  11. PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected
  12. bugs in the Github issues system. We'll be very happy to help you and provide
  13. all the support in the mailing list.
  14. There is also an active community of Redis users at Stack Overflow:
  16. # How to provide a patch for a new feature
  17. 1. If it is a major feature or a semantical change, please don't start coding
  18. straight away: if your feature is not a conceptual fit you'll lose a lot of
  19. time writing the code without any reason. Start by posting in the mailing list
  20. and creating an issue at Github with the description of, exactly, what you want
  21. to accomplish and why. Use cases are important for features to be accepted.
  22. Here you'll see if there is consensus about your idea.
  23. 2. If in step 1 you get an acknowledgment from the project leaders, use the
  24. following procedure to submit a patch:
  25. a. Fork Redis on github ( )
  26. b. Create a topic branch (git checkout -b my_branch)
  27. c. Push to your branch (git push origin my_branch)
  28. d. Initiate a pull request on github ( )
  29. e. Done :)
  30. 3. Keep in mind that we are very overloaded, so issues and PRs sometimes wait
  31. for a *very* long time. However this is not lack of interest, as the project
  32. gets more and more users, we find ourselves in a constant need to prioritize
  33. certain issues/PRs over others. If you think your issue/PR is very important
  34. try to popularize it, have other users commenting and sharing their point of
  35. view and so forth. This helps.
  36. 4. For minor fixes just open a pull request on Github.
  37. Thanks!