1399669fcSantirezNote: by contributing code to the Redis project in any form, including sending 2399669fcSantireza pull request via Github, a code fragment or patch via private email or 3399669fcSantirezpublic discussion groups, you agree to release your code under the terms 4399669fcSantirezof the BSD license that you can find in the COPYING file included in the Redis 5*ebbc4ebbSantirezsource distribution. You will include BSD license in the COPYING file within 6*ebbc4ebbSantirezeach source file that you contribute. 7399669fcSantirez 8278304ccSantirez# IMPORTANT: HOW TO USE REDIS GITHUB ISSUES 930d31cc8Santirez 10278304ccSantirez* Github issues SHOULD ONLY BE USED to report bugs, and for DETAILED feature 11278304ccSantirez requests. Everything else belongs to the Redis Google Group. 1230d31cc8Santirez 13278304ccSantirez PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected 14278304ccSantirez bugs in the Github issues system. We'll be very happy to help you and provide 15278304ccSantirez all the support in the Redis Google Group. 16278304ccSantirez 17278304ccSantirez Redis Google Group address: 18278304ccSantirez 19278304ccSantirez https://groups.google.com/forum/?fromgroups#!forum/redis-db 20278304ccSantirez 21278304ccSantirez# How to provide a patch for a new feature 22278304ccSantirez 23278304ccSantirez1. Drop a message to the Redis Google Group with a proposal of semantics/API. 24278304ccSantirez 25278304ccSantirez2. If in steps 1 you get an acknowledge from the project leaders, use the 26278304ccSantirez following procedure to submit a patch: 2730d31cc8Santirez 28e491a1a1SJan Oberst a. Fork Redis on github ( http://help.github.com/fork-a-repo/ ) 2930d31cc8Santirez b. Create a topic branch (git checkout -b my_branch) 3030d31cc8Santirez c. Push to your branch (git push origin my_branch) 31e491a1a1SJan Oberst d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ ) 3230d31cc8Santirez e. Done :) 3330d31cc8Santirez 3430d31cc8SantirezThanks! 35