commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Grobmeier <grobme...@gmail.com>
Subject Re: [VOTE] Revised dormancy policy
Date Thu, 19 May 2011 05:23:25 GMT
I like the new dormancy suggestion, plus:

> I am OK with changing "revival" to require only
> one ASF committer.

and:

>> If someone goes and
>> keeps on working stuff ... well ... then that status is nullified by
>> merit. (not through a single commit though) I don't see a reason to
>> forbid svn access

dormancy should be a "lean status" easy to change into sandbox or
active component. dormancy should be something else than the attic.

however i think it will be pretty hard to decide if a component is
dormant or just inactive

>
>
> Phil
>>
>> Emmanuel Bourg
>>
>>
>>
>> Le 16/05/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
>
>



-- 
http://www.grobmeier.de

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


Mime
View raw message