>It isn't having the patches in svn in a timely manner that's the >biggest help (though definitely nice), it's getting the immediate >feedback and growing the code organically as a team ensuring all work >is relevant that's the real magic. Absolutely, in a Patch > Review > Commit cycle , review is definitely a nice opportunity for a new contributor to learn about the project. I think what is really helping me here is to understand whats going on in the "committers head".
> it's very easy to bounce ideas back and forth, try stuff > out in code, see how it looks, learn from it and add more ideas on > top of it. We can tweak it here and there and all the while we're > working on the same code *in svn*. I'm just thrilled. I cannot agree more. It is so much fun working this way, and I guess thats what kept me going on this issue and improving it. > Everyone who wants to contribute to open source should take a page from your > >book. Wow!!, A statement like this coming from a person like you is a big thing for me. Thanks!! > > The shorter the time between proposal, patch, and commit the better. Totally agree BTW, as hungry as I am for documentation at this moment, I am thinking of putting your thoughts in the contributors guide :) > -David > > -- Karan Singh Malhi
