Don't think a time limit will do the trick here. It is just if everyone thinks or feels the
component is dormant*. You mention in your reply to Robert that it will be based on commits, which
is also not the way to go (although can be an indicator, depending on the number of commits). When I
find a bug message about documentation I will try to fix that, which already means a commit, but by
no way means the component is active again.
A good way to find dormant components is to have a look at bugzilla. We have a shitload of issues
there that probably never will be resolved. I have this on my todo list to propose something to make
that more managaeble (ehh just set to closed or resolved won't fix) very old issues, at least those
without any comments from committers (latka comes to mind, issues from 2003 are still open there).
Other issues which are old and assigned, I will try to ping the assignee.
In some cases, I could even start applying patches where there are complete patches provided (with
tests, etc), to give the community a chance to drive development of those dormant components, with
of course some oversight.
In short : it would be nice to see a cleanup of bugzilla (probably better start a seperate VOTE
about this). People can always reopen an issue if they are still interested to see something fixed
after more than eg a year waiting to get their problem solved.
*) dormant in this mail doesn't specifically mean the svn dormant.
Mvgr,
Martin
Henri Yandell wrote:
Specifically with respect to Latka, but applicable to all Commons components.
How do we want to handle released (ie non-sandboxed) components that
have gone dormant? Do we add a new component called Legacy (or
something like that)?
So:
Released
Legacy
Unreleased
Dormant
Currently we have 6 months as the time to drop out of the unreleased
(sandbox) section and into the dormant section. How long would we want
to be looking at to start a vote to drop things from Released into
Legacy? 1 year? 2 years?
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
