Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of phil.steitz@gmail.com
 designates 74.125.83.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=AZgV5vsDC3S08c/bd3hT9mx1I6zDTcsfVdVrPfUusFl6qKN/3e5Chj5TYtPzzxb3Li
         Rl54H2Ex3ggltQs/EPDaj5eehpYgQbjvPpOFK6XoWLpI0+xazxknubzj1f4PVjHVXdjG
         LlAmE8oz+H0VKyW/t3XQHm/8EFH+EfpTD+7yM=
Message-ID: <4DD19AB5.6090405@gmail.com>
Date: Mon, 16 May 2011 14:44:21 -0700
From: Phil Steitz <phil.steitz@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: Re: [VOTE] Revised dormancy policy
References: <4DD1645A.7070307@gmail.com>
 <E7C290E9-1137-4CA0-9E85-8065C7BBD48C@hoplahup.net>
In-Reply-To: <E7C290E9-1137-4CA0-9E85-8065C7BBD48C@hoplahup.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

On 5/16/11 2:34 PM, Paul Libbrecht wrote:
> Sorry Phil,
>
> I missed that one. I would like to adjust that policy at line:
>>    d) svn remains open (but no commits without revival vote)
> It seems slightly too harsh to me.
> Since jelly is among the heaviest targeted ones here, I think the whole dormancy aspect would fit but preventing commits sounds like the best way to "cap off any attempt of revival".
> Couldn't we say
>
Good point.  I would be OK with that change.

Phil
>>    d) svn remains open (but no release without revival vote)
> ? Or something similar that prevents active development?
>
> thanks in advance
>
> Paul
>
> Le 16 mai 2011 � 19:52, Phil Steitz a �crit :
>
>> I would like to take the proposal made in [1], modified per
>> discussion on that thread to a VOTE, so we can start implementing
>> the policy.
>>
>> The provisions are as follows:
>>
>> 0) To move a component to dormant requires a VOTE.   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":
>>    a) the main web site and site navigation links show the
>> component as dormant
>>    b) the component site and component JIRA page display a "dormant
>> disclaimer" (TBD)
>>    c) JIRA remains open (not merged into Commons-Dormant, but JIRA
>> project page displays disclaimer)
>>    d) svn remains open (but no commits without revival vote)
>>
>> 2) To revive a component requires another VOTE resulting in 3 +1s
>> from ASF committers interested in bringing the zombie back to life. 
>> Revival VOTEs are majority rule.
>>
>> votes, please.  This VOTE will remain open for at least 72 hours.
>>
>> Comments, as well as votes, are welcome from all community members. 
>> I will revise the policy and restart the VOTE if necessary.
>>
>> Thanks!
>>
>> Phil
>>
>> [1] http://markmail.org/message/bbnuxxozsnkapfhr
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>


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