httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brad Nicholes" <BNICHO...@novell.com>
Subject Fwd: Re: [PROPOSAL-VOTE] Adopt lazy consensus for backports...
Date Wed, 17 Nov 2004 01:17:24 GMT
moving to dev@ list

>>> aaron@clove.org Tuesday, November 16, 2004 5:21:28 PM >>>
+1

Lazy consensus applied in this way will help the less popular parts
of our codebase to continue to evolve and stabilize. Up to this point,
only the most popular patches have been getting enough attention
to receive the required three +1s. Going in this direction is
definitely
the right way to go.

p.s. why is this on the pmc list? we have committers who aren't
PMCers,
right?

-aaron


On Nov 16, 2004, at 3:08 PM, Brad Nicholes wrote:

>    During ApacheCon several httpd PMC members got together to
discuss
> current issues with the httpd project and to try to find better ways
to
> manage the project.  One of the issues that was discussed heavily
was
> the current policy of RTC vs CTR.  The feeling of some of the PMC
> members is that the RTC policy as it is currently implemented on the

> 2.0
> branch, is causing unnecessary overhead which has resulted in the
> slowdown of activity in the httpd project.  One proposal that was
made
> would be to adopt a lazy consensus rule.  Basically what this means
is
> that when a backport is proposed in the STATUS file, after a period
of
> time and if the proposal has not recieved any 0 or -1 votes, it
would
> automatically be approved for backport by lazy consensus.  The
purpose
> for this proposal is to avoid stagnation of backport proposals in
the
> STATUS file simply due to the lack of votes.
>
>
> Brad
>


Mime
View raw message