incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Re: Suspending Projects
Date Tue, 28 Jul 2009 21:32:12 GMT
I think we need to consider the risk to Apache of leaving the svn repo  
in a r/o state.

According to the XAP status page, 
  the copyright and distribution rights have not been verified, so  
IMHO the repository has not been vetted.

I think we should disable svn access entirely.

On a different note, I agree that suspension isn't the right term. I'd  
go with retirement or dormancy.


On Jul 27, 2009, at 6:55 PM, David Crossley wrote:

> Noel J. Bergman wrote:
>> This thread really needs to be put to a conclusion as policy and  
>> procedure.  On the table we have:
>> Suspension would include:
>>  -- disable the mailing lists (no need to moderate)
>>  -- disable commit access (no need to review changes)
>>  -- change the index of projects
> Some steps are listed at:
> "Dormant or Retired
> - Remove from the ReportingSchedule.
> - In the Projects in incubation table, move it to the "Dormant" or  
> "Retired" section.
> - Remove entry from right-side panel. (doc)
> "
> (Note that there are a number of links to direct docs in there.)
>> The idea being to both flag it as dormant, and to remove the  
>> oversight requirements that we have, by disabling anything  
>> requiring oversight.
>> There seems to be some disagreement over the word "suspend", which  
>> is being used in reference to an existing dormant state, not  
>> sending someone to the Headmaster's office to be removed from school.
> Going dormant, or retiring.
> "Suspend" is not used on our main table of incubating projects:
> just "Dormant" or "Retired".
> -David
>> There also seems to be a disagreement over the idea that inactive  
>> projects don't require oversight, but I feel that if we don't close  
>> the mailing lists, they will not be properly moderated (moderators  
>> still have to wade through spam looking for any faint signal), and  
>> people would wonder why they send messages that get lost.  And we  
>> don't want to miss commit messages.  It is best to structureally  
>> disable the resources than to trust in lack of use.
>> 	--- Noel
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Craig L Russell
Architect, Sun Java Enterprise System
408 276-5638
P.S. A good JDO? O, Gasp!

View raw message