On 19 Oct 2013, at 17:22, Henri Yandell wrote:
On Sat, Oct 19, 2013 at 7:25 AM, Christian Grobmeier
<grobme...@gmail.com>wrote:
Being in the attic is NOT a permanent thing. Get active developers,
leave
the attic. If a project doesn't make any sense, stay in the attic.
We are having an attic but called it "dormant".
The difference is that we have a a piece of code that no one is
working on
now and call it dormant. We are still here. The attic is when there is
no
one at Apache being responsible for the code. One of our development
patterns is to swarm on different components which means that other,
still
looked after codebases, receive less attention while we're swarming on
another component. Dormant fits nicely here.
OK. Let's assume we are just not working on this component for the
moment.
It simply means that no one is currently actively working on it, but
it
tells you nothing about its maturity or feature completeness.
However, if
we get a security report on one of this components, I am quite sure
that we
will react with a new release in time.
Given that normal releases will take a long time at Commons I doubt.
There is a security issue for this dormant components JavaDoc:
http://commons.apache.org/**dormant/clazz/apidocs/index.**html<http://commons.apache.org/dormant/clazz/apidocs/index.html>
Nobody reacted (includes me).
Sounds like Attic.
All of the dormant components are ready for the attic?
http://commons.apache.org/dormant/cache/apidocs/index.html
http://commons.apache.org/dormant/contract/apidocs/index.html
http://commons.apache.org/dormant/convert/apidocs/index.html
http://commons.apache.org/dormant/events/apidocs/index.html
http://commons.apache.org/dormant/feedparser/apidocs/index.html
http://commons.apache.org/dormant/jjar/apidocs/index.html
http://commons.apache.org/dormant/latka/apidocs/index.html
http://commons.apache.org/dormant/mapper/apidocs/index.html
http://commons.apache.org/dormant/messenger/apidocs/index.html
http://commons.apache.org/dormant/resources/apidocs/index.html
http://commons.apache.org/dormant/scaffold/apidocs/index.html
http://commons.apache.org/dormant/threadpool/apidocs/index.html
http://commons.apache.org/dormant/workflow/apidocs/index.html
http://commons.apache.org/dormant/xmlio/apidocs/index.html
The javadoc issue aside I think not a single dormant component
fulfills the branding requirements:
http://www.apache.org/foundation/marks/pmcs#attributions
I have only briefly looked on them, but at least the footer seems to be
incorrect
in all these cases.
These are two serious issues which sound to me that we are not
having a good oversight (or interest) of our dormant components.
Attic components are marked as read only. We don't take new user
reports,
they don't have a mailing list, their website has a big banner saying
'attic'. So moving out of the Attic involves the infrastructure
changes to
make something writeable again. There's also a difference in that
dormant
components accumulate new issues to work on.
Attic: The conversation at Apache has been turned off until such a
time as
demand returns and we have to find a new place for conversation.
Dormant: Things are just quiet, and ready to return as demand returns.
The challenge is to not be sloppy and pretend that every component is
'just
quiet' and is ready to return when the need is great (the King Arthur
pattern :) ).
OK :-)
Then maybe we are missing the process to finally decide when a component
is ready for the attic.
Cheers
Christian
Hen
---
http://www.grobmeier.de
@grobmeier
GPG: 0xA5CC90DB
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
