Re: [all] archiving sandbox components [WAS Re: [Messenger] Abandonware?]

[Phil Steitz <ph...@gmail.com>]

Looks good.  Couple of clarifying questions:

1. What happens to nightly builds, if the component has been set up to
have them?
2. What happens to jars in the "internal" snapshot repo
(/www/cvs.apache.org/repository)?

My HO would be best to stop nightlies (which will start failing anyway
;-) and to remove the snapshot jars.

I like the idea of doing the "cleanup" as a group a couple of times a
year.  As stated in the proposal, though,  we need to make sure to
give community members sufficient time to weigh in.  Here is a
suggestion:

* Generate a monthly report listing the apparently dormant sandbox
components, posted to both commons-dev and commons-user.   Understand
if this may be seen as an annoyance, but it is one way to keep the
surprises to a minimum.  If mailing list volume is a concern (though
one more message a month is a drop in the bucket ;-), this could be
posted to a web page somewhere.
* Every six months, kick off a VOTE (technically, a bunch of lazy
consensus VOTEs) based on the most recent report.
* Agree informally to spawn separate discussion threads for each -1
(binding or not).  Allow a month for these discussions.  At the end of
the month, archive any components that have not mustered binding -1's.

Phil


On 7/24/05, robert burrell donkin <ro...@blueyonder.co.uk> wrote:
> On Sun, 2005-07-24 at 16:27 +0100, robert burrell donkin wrote:
> > On Sun, 2005-07-24 at 10:33 -0400, Henri Yandell wrote:
> >
> > <snip>
> >
> > > As he was the only developer on Messenger, the one in Commons is
> > > effectively deprecated in favour of the Codehaus project. We need to
> > > come up with a dormancy process for the sandbox to make this more
> > > clear.
> >
> > hi hen
> >
> > managed to have a chat with some folks at apachecon and a reasonable
> > proposal emerged. i'll pull something together now on the wiki now.
> 
> http://wiki.apache.org/jakarta-commons/ProposalSandboxPruning
> 
> comments welcomed
> 
> - robert
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
>

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

Re: [all] archiving sandbox components

[Stefan Bodewig <bo...@apache.org>]

On Sun, 24 Jul 2005, robert burrell donkin
<ro...@blueyonder.co.uk> wrote:

> we'd also need to check with gump to ensure that removing the
> component doesn't beak anything.

In particular Gump will tell you if anybody else depends on the
component.

Stefan

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

Re: [all] archiving sandbox components [WAS Re: [Messenger] Abandonware?]

[Henri Yandell <fl...@gmail.com>]

On 7/24/05, robert burrell donkin <ro...@blueyonder.co.uk> wrote:


> if such a report was automated then we'd probably need to wait until the
> zones are up and running. we'd need a volunteer to code it also.
> 
> if such a report was manually generated, this would mean someone
> volunteering to create and maintain it.

I like Phil's report idea too. 

A basic version can be read straight off of
http://svn.apache.org/viewcvs.cgi/jakarta/commons/sandbox/

The last time somebody ran something global will show for any inactive
projects. Currently this would mean that only compress, contract,
i18n, id, javaflow, jci and pipeline would count as active, everyone
else having had at least 4 months of inactivity. Harder to tell beyond
that as Dirk did a global 4 months ago.

Hen

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

Re: [all] archiving sandbox components [WAS Re: [Messenger] Abandonware?]

[robert burrell donkin <ro...@blueyonder.co.uk>]

On Sun, 2005-07-24 at 11:31 -0700, Phil Steitz wrote:
> Looks good.  Couple of clarifying questions:
> 
> 1. What happens to nightly builds, if the component has been set up to
> have them?
> 2. What happens to jars in the "internal" snapshot repo
> (/www/cvs.apache.org/repository)?
> 
> My HO would be best to stop nightlies (which will start failing anyway
> ;-) 

+1

> and to remove the snapshot jars.

i don't really know anything about the snapshot repo. 

we'd also need to check with gump to ensure that removing the component
doesn't beak anything.

> I like the idea of doing the "cleanup" as a group a couple of times a
> year.  As stated in the proposal, though,  we need to make sure to
> give community members sufficient time to weigh in.  Here is a
> suggestion:
> 
> * Generate a monthly report listing the apparently dormant sandbox
> components, posted to both commons-dev and commons-user.   Understand
> if this may be seen as an annoyance, but it is one way to keep the
> surprises to a minimum.  If mailing list volume is a concern (though
> one more message a month is a drop in the bucket ;-), this could be
> posted to a web page somewhere.

interesting idea...

if such a report was automated then we'd probably need to wait until the
zones are up and running. we'd need a volunteer to code it also.

if such a report was manually generated, this would mean someone
volunteering to create and maintain it. 

> * Every six months, kick off a VOTE (technically, a bunch of lazy
> consensus VOTEs) based on the most recent report.
> * Agree informally to spawn separate discussion threads for each -1
> (binding or not).  Allow a month for these discussions.  At the end of
> the month, archive any components that have not mustered binding -1's.

sounds good

- robert


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