+1 to push any inactive projects to the attic. they can always be
moved back if real activity begins.

2010/3/28 Henri Yandell <flame...@gmail.com>:
> 2010/3/28 Phil Steitz <phil.ste...@gmail.com>:
>> Niall Pemberton wrote:
>>> On Sun, Mar 28, 2010 at 7:22 PM, Henri Yandell <flame...@gmail.com> wrote:
>>>> 2010/3/28 Rafał Krupiński <r.krupin...@gmail.com>:
>>>>> 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* components
>>> 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, so
> 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 url
> for the retired page and the process for restarting a component.
>
> Hen
>
> ---------------------------------------------------------------------
> 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

Reply via email to