commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [all] Move Jelly to dormant/orphaned?
Date Mon, 09 Jan 2012 15:42:20 GMT
On Mon, Jan 9, 2012 at 9:55 AM, Christian Grobmeier <grobmeier@gmail.com> wrote:
> On Mon, Jan 9, 2012 at 3:42 PM, Gary Gregory <garydgregory@gmail.com> wrote:
>> I think the whole formality of project state should be replaced with a
>> live activity widget like can be seen on other sites. Commit activity
>> and such. If someone were thinking of contributing to a project, the
>> incentive would be removed or seriously diminished by a dead/sleepy
>> project state.
>
> Interesting idea.
>
> You mean something like that?
> https://www.ohloh.net/p/commons-compress
>
> Any ideas how we can get this data out from svn?
> Probably besides svn an interesting metric is the number of discussion on ml.
>
> Question is how realistic is it we get something hacked together in
> for example ruby?

This is another kind of visualization:
http://sourceforge.net/projects/hsqldb/stats/scm?repo=SVNRepository

I do not know what the best metric is, just that it would be nice to
have /something/. See my other reply to Sebb in this thread.

Thank you,
Gary

>
> Cheers
> Christian
>
>>
>> Gary
>>
>> On Jan 9, 2012, at 6:59, Christian Grobmeier <grobmeier@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> Jelly did not see any activity for nearly two years:
>>> http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fcommons%2Fproper%2Fjelly
>>>
>>> Last release was in 01.2010.
>>>
>>> We had already discussion on a process to move proper components into
>>> another state, be it "dormant" or "inactive". I would like to
>>> resurrect this discussion. We have had a lots of discussion in the
>>> past: somebody wanted to progress with somehting, like graduating
>>> graph or using Java 5 in a component and the response sometimes was we
>>> have to less man power at Commons.
>>>
>>> Therefore I think we need to tell the people for which components they
>>> can expect releases and for which ones not. Otherwise outsiders may
>>> look at a huge bunch of components and see only little activity.
>>> Wouldn't it be better instead to show only a handful components which
>>> are actively developed?
>>>
>>> Looking at Jelly, it is orphaned. No releases, no releases to be
>>> expected. I would like to move it to dormant or to a new transition
>>> state, if people wish so, maybe called "orphaned" or "inactive" or
>>> whatever.
>>>
>>> What are your thoughts?
>>>
>>> Cheers
>>> Christian
>>>
>>> --
>>> http://www.grobmeier.de
>>> https://www.timeandbill.de
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>



-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
Spring Batch in Action: http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

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


Mime
View raw message