Re: [CT-NG] Patch approval process

[Oron Peled <oron at actcom dot co dot il>]

On Tuesday, 20 ×October 2009 23:32:10 Thomas Petazzoni wrote:
> I think it is far too much formal for the current size of the project.
> Most of the open-source projects handle the issue of scaling the
> reviewing process by nominating maintainers for sub-systems of the
> project, these maintainers being fully-responsible for reviewing and
> acknowledging the patches.

IMHO, this structure may impose a lot more formalities (who are the
subsystem maintainer, how to appoint them, defining clear boundaries, etc.)
So it's justified with big projects that have a long history.

> I don't think that a complicated voting-based process is going to work,

I agree that it shouldn't be overly formal and if I understood Yann's
correctly it basically boils down to something like "thumbs up/down"
with some rough guidelines about pass/reject criteria.

Since Yann made it clear he intends to keep his position as the
benevolent dictator, I'm looking at the proposed process as some
kind of a "recommendation system" to make it easier for Yann in
the most common cases -- sounds good to me.

BTW: I happened to "test" this when I sent a minor patch to the list
few days ago -- got a small reject from Alan Clark about a specific
part (regretfully in private mail and not to the list) and later a
more thorough response (reject) from Yann -- that was a quick
process and validated my doubts about the necessity of this patch.
[rpmlint problems]

Bye,

-- 
Oron Peled                                 Voice: +972-4-8228492
oron@actcom.co.il                  http://users.actcom.co.il/~oron
No, You Can't Have My Rights, I'm Still Using Them

--
For unsubscribe information see http://sourceware.org/lists.html#faq