commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <>
Subject Re: [ALL] Commons Attic
Date Mon, 11 Apr 2011 20:23:53 GMT
I'm all for moving to the Attic instead of a Commons Attic. Phil's
email makes me think that we have very little that would be up for the
Attic; but we do have some candidates and I'd like to see us clearly
defining the dead from the dormant. Also to drive us to think about
telling the dead from the dormant (or stable).

Moving to the Attic is a bigger step; that will be valuable to make us
think carefully and work to justify why something is still alive. We
often feel like the developer who always comments out code instead of
developing it.


On Sun, Apr 10, 2011 at 11:17 PM, Ralph Goers
<> wrote:
> I'm having a problem distinguishing "dormant" from "attic".  Just because one had releases
and the other didn't they should go to different places for their final resting place?
> I'm not really clear on what happens to incubator projects that fail. I know there is
no "incubator dormant" or "incubator attic" and I don't believe any incubator projects have
ever moved to the attic.
> I'm not clear why commons should have an attic (or dormant) subproject.  The attic is
perfectly capable of housing Commons Jelly. It already contains several Jakarta subprojects.
> My proposal would be to move all of the dormant subprojects and any inactive proper projects
to Apache Attic.
> Ralph
> On Apr 10, 2011, at 10:12 PM, Henri Yandell wrote:
>> Currently we have 3 areas in which components live:
>> * Proper: Released components.
>> * Sandbox: Active pre-release components.
>> * Dormant: Inactive pre-release components.
>> There's an obvious (to me) need for Proper to split into active and
>> inactive. Given the existing name, inactive proper = attic.
>> So:
>> * Proposal #1: Create a Commons Attic.
>> An alternative is to send our attic'd items to the Apache Attic; but I
>> think we're enough of a mini-ecosystem that it makes sense to manage
>> our Attic'd components locally. Moving into the Commons Attic would be
>> very simple; we'd keep permissions etc and do more around updating the
>> components website to indicate it's now in the Attic. We might go as
>> far as to close down its JIRA.
>> Next up is to identify the first candidate to a Commons Attic. Jelly
>> is the lucky winner (by looking at dates in SVN).
>> It hasn't had a commit in a year, and its last meaningful commit (to a
>> user) was in December 2008.
>> So:
>> * Proposal #2:  Move Jelly to Commons Attic.
>> 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:

View raw message