Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of goyathlay.geronimo@gmail.com
 designates 66.249.92.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Ygzya3OMiSjIeC9XmoLynz6a35o7NbdeUiE5tUDqJf4AU5rN65WnaW5Em/x5tT+DA//noNI4TEGTCUq0Ni5rEFTzJJ+HYbVcPb8F61eSWpH0DUpa3zf0cfRQ47FxeT/Hpyirz4XXJHQ5H0izgbTw5i3jwDtVuxCpqS4KW2Bn6ps=
Message-ID: <c278ac970606190923y139d5086u461c4d2d46f33c94@mail.gmail.com>
Date: Mon, 19 Jun 2006 12:23:08 -0400
From: "Prasad Kashyap" <goyathlay.geronimo@gmail.com>
To: dev@geronimo.apache.org, coar@apache.org
Subject: Re: Request change to RTC Process
In-Reply-To: <44943525.4000700@Golux.Com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <B0E977E8-3FE0-42F7-A39D-B8DAFE79DB67@gmail.com>
	 <44941004.8070503@Golux.Com>
	 <74e15baa0606170833o1d07cd28mde39cc2dabb364e6@mail.gmail.com>
	 <44943525.4000700@Golux.Com>

On 6/17/06, Rodent of Unusual Size <Ken.Coar@golux.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> I don't consider this valid, either.  If you have the
> time to be a committer, you have the time to be part of
> the community and collaborate with your peers on the
> project.  One thing about RTC is that it tends to promote
> interaction, since people are dependent on each other and
> the occasional quid pro quo -- unlike the everyone haring
> off in his own direction with no-one else watching that
> can occur (and has occurred) under CTR.
>
> No-one says you have to test *anyone* else's patches.  Unless,
> of course, you hope they'll test *yours*, which is where
> the collaboration-for-the-project aspect comes in.  So if
> you don't find time to test someone else's code, regardless
> of for whom he may work, don't expect him to spend a lot
> of time testing *yours*.
>

True. But this quid pro quo holds good only for code submitted by
committers. Consider the case of active contributors who are
non-committers. If they choose to work on JIRAs in the wish list, it
will be quite a herculean task for them to get a sign-off from 3
committers. The "you scratch my back, I'll scratch yours" convenience
is not available for non-committers.

Going by this thread, if the committers of the project are
apprehensive about the RTC model and are requesting changes, then
contributors have an even tougher task cut out for them.  I hope that
doesn't sent a message to the community that only patches from
committers have any chance of getting in. I hope that doesn't
de-moralize the non-committers and turn them away from the project.

The RTC is not entirely bad either. It is a good thing to happen to
the project but not in it's present form. What would be good for
Geronimo would be take the best of RTC and CTR.

Here's something to think about -
1) Bug fixes (esp. blockers)  shouldn't need a review.
2) Improvements need atleast ONE +1 vote by a commiter. RTC turns into
CTR after 15 days. A reminder message to be sent 3 days before the
model changes to CTR.
3) Features need THREE +1 votes by other committers. RTC turns into
CTR after 30 days. A reminder message to be sent 7 days before the
model changes to CTR

Just a suggestion.

Cheers
Prasad.


> - --
> #ken    P-|}
>
> Ken Coar, Sanagendamgagwedweinini  http://Ken.Coar.Org/
> Author, developer, opinionist      http://Apache-Server.Com/
>
> "Millennium hand and shrimp!"
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iQCVAwUBRJQ1JZrNPMCpn3XdAQKLAQQAx58qgOEEdnrL79vPuXn8AWYwgrVcwH1j
> X7cnZsvTGmQ4uZW7GiCjjkU2E0H0gGMIRUHFCuV8lul85DectAxE3+4M6pYPAG8v
> wzg8OOYUl4Wmv6s31M1VDBruCseGLh01c+ilYl2G61mM+c+Ppt3dduD/VCqQDeao
> 38KzZSDD1WM=
> =M+w0
> -----END PGP SIGNATURE-----
>