[redis.git] / CONTRIBUTING

1. Enter irc.freenode.org #redis and start talking with 'antirez' and/or 'pietern' to check if there is interest for such a feature and to understand the probability of it being merged. We'll try hard to keep Redis simple... so you'll likely encounter high resistance.

2. Drop a message to the Redis Google Group with a proposal of semantics/API.

3. If steps 1 and 2 are ok, use the following procedure to submit a patch:

    a. Fork Redis on github ( http://help.github.com/fork-a-repo/ )
    b. Create a topic branch (git checkout -b my_branch)
    c. Push to your branch (git push origin my_branch)
    d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ )
    e. Done :)

Thanks!
Commit	Line	Data
5215ab14	1	1. Enter irc.freenode.org #redis and start talking with 'antirez' and/or 'pietern' to check if there is interest for such a feature and to understand the probability of it being merged. We'll try hard to keep Redis simple... so you'll likely encounter high resistance.
30d31cc8	2
	3	2. Drop a message to the Redis Google Group with a proposal of semantics/API.
	4
	5	3. If steps 1 and 2 are ok, use the following procedure to submit a patch:
	6
e491a1a1	7	a. Fork Redis on github ( http://help.github.com/fork-a-repo/ )
30d31cc8	8	b. Create a topic branch (git checkout -b my_branch)
30d31cc8	9	c. Push to your branch (git push origin my_branch)
e491a1a1	10	d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ )
30d31cc8	11	e. Done :)
	12
	13	Thanks!