[fdo-internals] More Site Cleanup

Jason Birch Jason.Birch at nanaimo.ca
Mon Jan 15 16:56:01 EST 2007

The revisions are repository-wide.
I believe that the ACLs could be configured based on directory:
and mailing list functionality could probaby be placed into a
post-commit hook script that parses the paths of the committed files and
sends the note to the appropriate -commit list.


From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Robert Bray
Sent: Monday, January 15, 2007 13:23
To: FDO Internals Mail List; Shawn Barnes
Subject: Re: [fdo-internals] More Site Cleanup

SVN can only provide access control, revisions, mailing list, etc at the
repository level. So to merge them into one repository would mean the
commiter list would need to be the same for all of FDO. I don't really
have an issue with that approach, but that is not the way it is setup


Jason Birch wrote: 

	Is there a reason why you are staying with multiple SVN
instances, instead of merging the providers into the core and managing
access at the node level?
	I'm pretty sure that Trac instances have to have a 1:1
relationship with SVN repositories.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20070115/82ba06f9/attachment.html

More information about the fdo-internals mailing list