On 10/15/2013 10:31 AM, Torsten Curdt wrote:
I monitor commits, rarely check JIRA, follow and sometimes answer mails and
close to never develop code for that component anymore - maybe once or
twice a year when I go through JIRAs.

Now what?

I appreciate the initiative but don't see this working too well for me.

If this was all just one repo and dormant was just a "not actively
developed" flag this would be a little easier.

While Henri suggested in his initial email that non-active components should be 'moved' to Attic/Dormant, he already indicated later that no decision or even conclusion should be drawn yet.

Lets first build up some data on the current status, which I think is a very sensible thing to do (regularly even).

If and how 'dormant' components should be flagged IMO should be a separate discussion once we have clearer view which components would fall in such category.

I myself would agree to just 'flag' such components, recorded in some status file somewhere and probably should (automatically?) get a warning banner up on their site so the *end users* are aware of this status.

Moving a component in svn under /dormant (if its not there already) seems to me a change not really needed to get the point across. Again: the primary target here IMO are the *end users*, not temporarily MIA developers.

And moving a component into the the Attic is something completely different all together. Maybe feasible as well for some 'forever dormant' components, but not to be decided lightly for sure.

Even better if there was a script that regularly checks different
conditions and updates the flag on the website accordingly.

That would work for me as well. Not sure though how easy such script can be made, which criteria to check and how to quantify them (svn, release tags, JIRA, mailing lists, etc.)

Ate


cheers,
Torsten



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

Reply via email to