If nobody is willing to put a component to "dormant" state, then the
label doesn't make any sense. I would vote to remove the dormant state
in general.
If we don't have any need of a specific component we can put it to
attic.apache.org too.
No need to duplicate things.
If we don't have a "dormant", I would like to see the content of
CHALLENGE.txt
somewhere on the website: people who have dedicated themselves to work
active on the
component. If no-one signed up, it is unlikely to get issues fixed
quickly.
In addition I like the "last release" column.
Here is a widget:
http://svnsearch.org/svnsearch/repos/ASF/search?view=widgets&path=%2Fcommons%2Fproper
It does also work on components level:
http://svnsearch.org/svnsearch/repos/ASF/search?view=widgets&path=%2Fcommons%2Fproper%2Flogging
Cheers
On 15 Oct 2013, at 17:50, Gary Gregory wrote:
On Tue, Oct 15, 2013 at 11:30 AM, Ralph Goers
<ralph.go...@dslextreme.com> wrote:
Personally, I like the idea of having a last release date AND a list
of people who are active in the project. The only problem is that
people who go inactive rarely remove themselves from the list.
The only to solve that is with automation, like a list of the people
who committed over the last month for example. There must be an SVN
widget we can add to the site to see some useful stats.
Gary
Ralph
On Oct 15, 2013, at 7:48 AM, Jörg Schaible
<joerg.schai...@scalaris.com> wrote:
Hi Gary,
Gary Gregory wrote:
On Tue, Oct 15, 2013 at 2:15 AM, Phil Steitz
<phil.ste...@gmail.com>
wrote:
On 10/14/13 10:59 PM, Paul Libbrecht wrote:
Le 15 oct. 2013 à 07:33, Dave Brosius <dbros...@apache.org> a
écrit :
I couldn't disagree more. Dormant/attic means the project has
leprosy.
I don't know the answer to this, but wondering, has there ever
been a
commit to an attic'ed project? I personally would never think of
doing
that.
As probably the only person that "supports"' Jelly, a dormant to
be for
sure, I find the word leprosy outrageous.
I am happy to stay on list, I even read posts regularly, but I
cannot
find time or motivation to fix bugs or do new releases. I respond
to any
Jelly question I find.
Jelly has gone 1.0 and is in use here and there.
I would expect users to be interested to make it advance to come
to jira
and suggest fixes; I am happy to negotiate them and apply them,
and
maybe, if things get excited, there might be a release one day.
However, moving it to a place where you would never commit would
sign
its death.
The proposal is not to move it anywhere, just designate it as
dormant so people know no one is currently working on it.
We could avoid labeling a project with any words by simply listing
the
last release date. Each project in turn could have a section in its
overview with a history of releases. This would help users make up
their mind.
Based on a release date only, vfs is dormant. Therefore I like Hen's
approach, since every committer (or even interested user) has now
the
possibility to make his interest/commitment explicit.
Actually we could repeat the this challenge on a yearly base (again
with an
empty file). A dormant label can get away in an instance if enough
people
show interest. It would be even better without a dormant section in
svn
(with Git it is gone anyway). Currently it takes more effort to
awake a
component.
Just because a component is "dormant" does not mean that its
maturity has
gone.
- Jörg
---------------------------------------------------------------------
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
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---
http://www.grobmeier.de
@grobmeier
GPG: 0xA5CC90DB
