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-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
