commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Grobmeier <grobme...@gmail.com>
Subject Re: [all] Move Jelly to dormant/orphaned?
Date Mon, 09 Jan 2012 17:31:36 GMT
>>> Project states, if wanted, should be on the Wiki in a list, "this is
>>> how we feel about projects, but a committer can still commit and do
>>> work"
>>
>> That's a separate issue from attracting outside contributions.
>>
>> But I think there are some components that are clearly not going to be
>> developed further, e.g. because the need for them has gone away.
>
> Good point. But does that mean we need more states than alive and
> dead? Thinking about The Princess Bride...
>
> I was thinking of the edge case where someone wants a bug fix in a
> sleepy project because they have to fix an older application that uses
> the component directly or indirectly.

He still can as he can do in dormant or sandbox components. No big deal for me.
I am fine with putting a component to dormant instead of having a fourth state.
It should be easy to put a component to sleep or wake it up again.
Probably not even moving them in svn, jsut indicating in a "components
health page" at commons.a.o




>
> Gary
>
>>
>>> 2c,
>>> Gary
>>>
>>>>
>>>>> 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
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>>
>>
>> ---------------------------------------------------------------------
>> 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
>



-- 
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


Mime
View raw message