Per-project metadata (Was: SV: .svn directories)

At 9:38 PM +0200 8/25/03, Jesper Bork wrote:
>
>Much in line with your thoughts and from years of experience from a
>project-centered environment handling around 25 projects a year, I
>believe that an SCM provides the maximum overall benefit in a
>commercial environment by combining the loose coupling of the
>copy-modify-merge source code approach taken by CVS and Subversion
>together with decentralized non-intrusize per-project meta-data and
>finally centralized statistics allowing e.g. project managers and
>method & tools depts. to get an overall view of e.g. repository
>status. While avoiding locks due to going on holidays while having
>something checked out is a technical issue, it is still an
>organizational issue to catch the guy doing that or maybe - as we
>allow - taking charge of someone elses workspace, if necessary to
>get the project moving.

I get most of that, but what do you mean by "decentralized
non-intrusive per-project meta-data"? Can you give some examples of
the meta-data you're thinking of, how they don't intrude (or, how
other data _do_ intrude, I suppose)?

-- 
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org