Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Andrei Thorp <garoth@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] slowly catching up
Date: Thu, 05 Nov 2009 23:13:05 -0500	[thread overview]
Message-ID: <1257476207-sup-3459@zyrg.net> (raw)
In-Reply-To: <80055d7c0911051838m855262bi93d149549de2da8c@mail.gmail.com>

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-sup@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


  reply	other threads:[~2009-11-06  4:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-31 14:03 William Morgan
2009-11-02  7:29 ` Tero Tilus
2009-11-03 18:14   ` William Morgan
2009-11-06  2:38 ` Andrei Thorp
2009-11-06  4:13   ` Rich Lane [this message]
2009-11-06 13:47     ` William Morgan
2009-11-07  7:09       ` Rich Lane
2009-11-07  9:34         ` Tero Tilus
2009-11-07 16:56         ` William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1257476207-sup-3459@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=garoth@gmail.com \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox