commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Jakarta-commons Wiki] Update of "ProposalSandboxPruning" by RobertBurrellDonkin
Date Sun, 24 Jul 2005 16:13:43 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification.

The following page has been changed by RobertBurrellDonkin:

The comment on the change is:
Created page on sandbox archiving proposal (as well as I can remember)

New page:
= Proposal Sandbox Pruning =

A proposal for better sandbox managed emerged from discussions at ApacheConEurope2005. Here
IIRC is the consensus. Hopefully, folks with better memories will dive in and correct any

Of course, other folks are encouraged to improve the proposal but it might be better to post
to commons-dev about any major changes (so it can be discussed) rather than just diving in.

== Rational ==

The sandbox contains many components which are no longer active. This confuses users. It increases
the time required to checkout the sandbox. It also makes it more difficult for folks not familiar
with the commons to see that we're demonstrating oversight.

== Formal Process ==

 1. An inactive component is any component that not had any commits made in the last six months.

 1. Any component which has been inactive is a candidate for archiving.
 1. Any inactive component can be archived by lazy consensus.
 1. A directory called dormant will be created as a child of commons.
 1. This directory will be read-only except for archiving activities. 
 1. To archive a component, the component directory will be moved from the sandbox to the
dormant directory.
 1. A component can be unarchived (back into the sandbox) by a vote.
 1. The website for the component will be retained but marked as dormant.

== Social Process ==

Probably best to batch these together and tidy up the sandbox a couple of times a year. Probably
announce dates in advance so that folks get a chance to speak up.

Though any component can be archived by lazy consensus, netiquette requires a proposal to
give the chance for any committers interested in that component to reply. There is no pressing
reason for haste and so an appropriate duration should be chosen for the vote.

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

View raw message