Excerpts from Andrei Thorp's message of Thu Nov 05 21:38:26 -0500 2009: > On Sat, Oct 31, 2009 at 9:03 AM, William Morgan > <wmorgan-...@masanjin.net> wrote: > > Suggestions welcome. > > I propose promoting Rich Lane to commiter if he's up for it and > doesn't have access yet. From what I can tell, he's done a terrific > job thus far, and has a lot of experience with Sup.
Thanks! If William doesn't have the free time, I would be glad to help out. Rather than committing directly to mainline, I'd rather keep a public repo that I apply incoming patches to and that William can pull from. This way I could do a lot of the first-line work and he could get a more stable flow of patches to make releases from. For my own process suggestion: I can imagine that a lot of William's work caused by being the central repository is reviewing the patches that get sent in. I'd like for anyone who feels interested to read through incoming patches and comment on them. I don't want any strict processes just yet, but I'd like to see a couple of positive reviews (depending on the complexity of the patch, etc) before things get merged. Distributing the workload and ensuring code quality are only a couple of my motives here. I know I feel more comfortable sending out a patch if I'm sure someone will catch my mistakes before it's merged. Also, it's a great way for people who aren't yet familiar with the codebase to start contributing. If anyone's interested and wants to get started right away, definitely take a look at the immediate-updates patches I sent in yesterday. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk