[PROPOSAL] Project meta-data in subversion repositories

GOAL

To allow high-level applications create "projects" and
"branches or tags within project", in the location by an agreed and
configurable convention. This would also allow hook scripts, such as
those preventing modification of /tags, to be written more portably.

IMPLEMENTATION

Property "svn:project:<projectname>" on '/', containing a spec like:

[path]
trunk = /path/to/trunk
branches = /path/to/branches
tags = /path/to/tags
hooks = /path/to/hooks

[address]
admin = admin@host.org
commit_url = svn+ssh://svn.host.org/project
public_url = svn://svn.host.org/project

There should be a list of standard names of commonly used meta-data,
including at least those listed above. None of these meta-data should be
mandatory.

Where to put the property:

* Versioned property on '/',
  - Pros: Versioned.
  - Cons: Requiring read access on '/' to make use of the meta data.

* Unversioned property on r0
  - Pros: Works out-of-box with repository that has acl.
  - Cons: Unversioned.

Personally I'd prefer the r0 one, as versioning such properly is
actually not so interesting, while having the properties more
accessible would make it easier to build applications on it.

Cheers,
CLK

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 11 01:09:44 2006