Just chiming in here with regard to contributing code. I actually have the
opposite problem here where I can generally contribute patches but I'm a
total n00b with respect to writing specs. I'd be more inclined to contribute
more if there was an outline/example for submitting a patch and it's
Hi Shane,
On Feb 11, 2009, at 12:44 PM, Shane Witbeck wrote:
Just chiming in here with regard to contributing code. I actually
have the
opposite problem here where I can generally contribute patches but
I'm a
total n00b with respect to writing specs. I'd be more inclined to
contribute
On Wed, Feb 11, 2009 at 11:32 AM, Ittay Dror itt...@tikalk.com wrote:
Assaf Arkin wrote:
Specs really really help. A patch could look simple and trivial, maybe
it's
a one line fix, but writing the spec and then accepting the patch is more
work than accepting a tested patch.
If you
On Wed, Feb 11, 2009 at 11:53 AM, Rhett Sutphin
rh...@detailedbalance.netwrote:
Hi,
On Feb 11, 2009, at 1:32 PM, Ittay Dror wrote:
Assaf Arkin wrote:
Specs really really help. A patch could look simple and trivial, maybe
it's
a one line fix, but writing the spec and then accepting the
On Wed, Feb 11, 2009 at 11:32 AM, Ittay Dror itt...@tikalk.com wrote:
Assaf Arkin wrote:
Specs really really help. A patch could look simple and trivial, maybe
it's
a one line fix, but writing the spec and then accepting the patch is more
work than accepting a tested patch.
If you
GitHub is definitely the easiest way to contribute code. Though, I haven't
had any contributions accepted yet, so who am I to say? (hint, hint) ;-)
Alternatively, using Git to develop a patch and then JIRA to submit isn't
too bad either. Once you get over the initial learning curve (which
