commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Steitz <>
Subject Re: Future of Transaction subproject
Date Fri, 16 Apr 2010 23:31:43 GMT
Oliver Zeigermann wrote:
> This seems to ask a more general question and it is an important one:
> How to retire components that have releases?
> Do we want to settle this more generally, before we proceed with
> retiring this component?

I agree we should solve the general problem and I think there are
good ideas on this thread about how to do that.  Here is what I think:

1) I agree with those who have said that the attic is not
appropriate for inactive commons components that have had releases.

2) I do not like the words "retire" or "retired."  The present case
is extreme; but in general it is not correct to assume that the
component will never be re-activated, nor do we want people to get
the impression that revival is impossible.  Especially if we get
more aggressive in identifying inactive components, we should be
expecting and welcoming the prospect of components going inactive
and then coming back to life.  I would prefer to stick with either
"dormant" or "inactive."

3) I agree that we should separate sandbox dormant|inactive from
proper dormant|inactive


> If so: How do we settle this? I am a little bit afraid that the
> discussion leads to nothing blocking *any* action.
> What do you think?
> Oliver
> 2010/4/16 Paul Benedict <>:
>> We could also push the projects into the Apache Attic.
>> 2010/4/16 Niall Pemberton <>:
>>> 2010/4/5 Oliver Zeigermann <>:
>>>> Folks!
>>>> The only discussion seems to be about "how to retire the project", not
>>>> "if to retire the project". This means to me we all agree to at least
>>>> temporarily retire it and there is no more discussion about how to do
>>>> it.
>>>> As the Apache commons way of retiring seems to be to move it to the
>>>> dormant section that is what I propose.
>>> Up to now everything in dormant has been sandbox components that were
>>> never released. In my mind *retiring* a proper component that has had
>>> releases is different from a sandbox component that became inactive.
>>> I'm wondering if we should distinguish between these two scenarios
>>> rather than just putting them all together in dormant?
>>> Niall
>>>> What are the next steps? Do we need a formal vote? Or are we just doing it?
>>>> - Oliver
>>>> 2010/3/29 Paul Benedict <>:
>>>>> +1 to push any inactive projects to the attic. they can always be
>>>>> moved back if real activity begins.
>>>>> 2010/3/28 Henri Yandell <>:
>>>>>> 2010/3/28 Phil Steitz <>:
>>>>>>> Niall Pemberton wrote:
>>>>>>>> On Sun, Mar 28, 2010 at 7:22 PM, Henri Yandell <>
>>>>>>>>> 2010/3/28 Rafał Krupiński <>:
>>>>>>>>>> On 28.03.2010 20:13, Henri Yandell wrote:
>>>>>>>>>>> Unless anyone speaks up for it, I'm all for our
making a Retired
>>>>>>>>>>> section and moving Transaction to it. Possibly
we could relabel
>>>>>>>>>>> 'Dormant' then to be more Sandbox focused and
consider some others for
>>>>>>>>>>> Retired (Attributes, Discovery, Modeler jump
to mind).
>>>>>>>>>> You mean something like Apache Attic?
>>>>>>>>> Fair point. Let's assume moving it to the Attic. I'm
not sure it'll be
>>>>>>>>> a perfect fit, but if it doesn't we can always maintain
our own
>>>>>>>>> Retired page.
>>>>>>>> I guess I shouldn't be telling you how the attic works, but
IMO its
>>>>>>>> for projects which don't have a functioning PMC. Thats not
the case
>>>>>>>> for Commons so I think it would be better to keep *retired*
>>>>>>>> here.
>>>>>>> +1 - and I am not sure we can really distinguish "retired" from
>>>>>>> "dormant."  Not breathing is not breathing and resurrection is
>>>>>>> resurrection. :)
>>>>>> Xang went to the Attic from the XML PMC, and Slide + Taglibs (minus
>>>>>> those that went to Tomcat) are expected to go there from Jakarta,
>>>>>> it's definitely not been limited only to those without PMCs. I think
>>>>>> we could do either option and am not tied to either.
>>>>>> Attic-wise... I was thinking of making a page there, much as Taglibs
>>>>>> will have, which will list retired components.
>>>>>> Commons-wise, we'd have a retired page and probably link to it from
>>>>>> the Attic page as an FYI. So really all we're talking about is the
>>>>>> for the retired page and the process for restarting a component.
>>>>>> Hen
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail:
>>>>>> For additional commands, e-mail:
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail:
>>>>> For additional commands, e-mail:
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail:
>>>> For additional commands, e-mail:
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> For additional commands, e-mail:
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message