Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Subject: Re: [DRAFT] request Apache Forrest TLP setup
From: David Crossley <crossley@apache.org>
To: forrest-dev@xml.apache.org
In-Reply-To: <1085777536.40b7a68074ca7@secure.solidusdesign.com>
References: <1085733160.28445.4907.camel@ighp>  <40B73D2B.107@brondsema.net>
	 <1085777370.28446.6479.camel@ighp>
	 <1085777536.40b7a68074ca7@secure.solidusdesign.com>
Content-Type: text/plain
Organization: 
Message-Id: <1085892044.23980.1402.camel@ighp>
Mime-Version: 1.0
Date: 30 May 2004 14:40:45 +1000
Content-Transfer-Encoding: 7bit

Dave Brondsema wrote:
> Quoting David Crossley:
> > Dave Brondsema wrote:
> > > David Crossley wrote:
> > > 
> > > > *) Do we want a separate "cvs" mailing list and archive?
> > > > At the moment it automatically comes to "dev".
> > > 
> > > Yes.  Or not archive the "cvs" list at all.  All that history is in the 
> > > repository.  Either way, I don't like commit emails cluttering the dev 
> > > list when I'm browsing it.
> > 
> > I gather that we must have the diffs coming to a mailing
> > list so as to ensure proper oversight. Each committer should
> > be subscribed to that list.
> > 
> > I too think that it should be a separate list. Also we will
> > have the Wiki diffs coming to that list.
> 
> Yes I agree that we should have it.  But I don't think we need to archive it.

What is the reason that you do not want it to be archived?

Yes the history is in the repository and we should be safer
with SVN, and not lose or mangle history like what happened
with Cocoon.

I see it as useful to have an archive. It provides a way
to search for past commits. It provides a way to easily
refer to a specific commit if ever we need to prove something.

Evidently having an archive enables a mechanism for code review
in case of break-in and compromise of the system.

Looking at Eyebrowse i see that many projects do have an
archive of their "cvs" list.

--David