On Thu, May 5, 2011 at 3:35 PM, Phil Steitz <phil.ste...@gmail.com> wrote: > As Hen has pointed out a couple of times, we have quite a few > Commons proper components that are no longer under active > development. I would like to propose that we extend the "dormant" > classification on the web site to include components that have had > releases. I am not sure whether we need to distinguish internally > within this group or do svn moves. I will start by proposing just > the minimalist approach: > > 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. > <snip/>
I'd recommend lazy consensus votes that are open 10-ish days / couple of weeks -- this is how we've been making decisions on moving Jakarta bits to Attic. Lazy consensus because enough folks may not be bothered to chime in if its truly dormant, though Commons is different here :-), and long duration because we want to maximize chances of people seeing the vote. -Rahul > 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 > d) svn remains open (maybe made read only? Could just agree to > no commits.) > > 2) To revive a component requires another VOTE resulting in 3 +1s > from ASF committers interested in bringing the zombie back to life. > > Phil > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
