Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
Sender: jcarman@carmanconsulting.com
In-Reply-To: <4DEE890D.6050103@gmail.com>
References: <4DEE890D.6050103@gmail.com>
From: James Carman <james@carmanconsulting.com>
Date: Wed, 8 Jun 2011 07:16:47 -0400
Message-ID: <BANLkTik9SYmx7k9axQ4HytZkNOL=fkHzkg@mail.gmail.com>
Subject: Re: [VOTE] Revised dormancy policy - take 3
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I really don't like the idea of having a vote to revive something.
I'd say that if a commons committer has an itch, then let them scratch
it in the sandbox if they want to.  Do we really need a special
procedure here?  Can't we just say that you have to revive it into the
sandbox and then follow the normal promotion procedures to get it back
into proper?  If someone runs into a security issue or something, they
can just copy the code in SVN into the "sandbox" branch and then
figure it out.  When it's ready, it can be voted into the proper again
and released.  So, lifecycle is:

[Sandbox] -> Proper -> Dormant -> Sandbox -> Proper

The initial [Sandbox] is optional, I guess.

On Tue, Jun 7, 2011 at 4:24 PM, Phil Steitz <phil.steitz@gmail.com> wrote:
> Thanks, all, for the great comments on the previous versions [1][2].
> I have tried to incorporate them.
>
> Revised Dormancy Policy
>
> 0) To move a component to dormant requires a VOTE. =A0 A single -1
> suffices to postpone the action; but a -1 in a dormancy vote is
> really a +1 to help sustain or advance the component. Dormancy VOTEs
> will remain open for two weeks.
>
> 1) When a component is voted "dormant":
> =A0 =A0a) the main web site and site navigation links show the
> component as dormant
> =A0 =A0b) the component site and component JIRA page display a "dormant
> disclaimer" (TBD)
> =A0 =A0c) JIRA remains open (not merged into Commons-Dormant, but JIRA
> project page displays disclaimer)
> =A0 =A0d) svn remains open (but no release without a revival VOTE)
>
> 2) To revive a component requires a VOTE. =A0Any ASF committer interested=
 in bringing the zombie back to life can initiate this action. Revival VOTE=
s
> are majority rule.
>
> 3) Dormant status for a Commons component is not a substitute for the Apa=
che Attic. =A0Components that we decide are obsolete or for other reasons a=
re unlikely to ever be revived should be moved to the Apache Attic. =A0To r=
etire a component to the Attic requires a vote similar to 0).
>
> votes, please. =A0This VOTE will remain open for at least 72 hours.
>
>
> Thanks!
>
> Phil
>
> [1] http://markmail.org/message/bbnuxxozsnkapfhr
> [2] http://markmail.org/message/3bot5xiazanqavqg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org