Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of ralph.goers@dslextreme.com
 designates 209.85.210.171 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [ALL] Commons Attic
From: Ralph Goers <ralph.goers@dslextreme.com>
In-Reply-To: <BANLkTimoEMx_ouLc+0Ext0kmM94=tNJ21w@mail.gmail.com>
Date: Sun, 10 Apr 2011 23:17:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <08AEC2BF-E8ED-4B20-AC8C-F8F2DD757FF9@dslextreme.com>
References: <BANLkTimoEMx_ouLc+0Ext0kmM94=tNJ21w@mail.gmail.com>
To: "Commons Developers List" <dev@commons.apache.org>

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? =20

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:
>=20
> * Proper: Released components.
> * Sandbox: Active pre-release components.
> * Dormant: Inactive pre-release components.
>=20
> There's an obvious (to me) need for Proper to split into active and
> inactive. Given the existing name, inactive proper =3D attic.
>=20
> So:
>=20
> * Proposal #1: Create a Commons Attic.
>=20
> 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.
>=20
> Next up is to identify the first candidate to a Commons Attic. Jelly
> is the lucky winner (by looking at dates in SVN).
>=20
> It hasn't had a commit in a year, and its last meaningful commit (to a
> user) was in December 2008.
>=20
> So:
>=20
> * Proposal #2:  Move Jelly to Commons Attic.
>=20
>=20
> Hen
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>=20


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