I use subversion to manage source code and documents. The biggest challages
have been
* Transaction not found bug reduced users confidence
* Teaching managers how to use subversion
* My disk is filling up fast. One project had a gig worth of svn data.
In any event I went for a structure like this....
* Company 1
* Business Development
* Business Support
* Framework
* Library1
* Trunk
* Branches
* Tags
* Library2
* Library3
* Management
* Our People
* Projects
* Project1
* Proposal
* Task initiation
* Correspondance
* Planning and management
* Work
* Source
* Trunk
* Branches
* Tags
* Deliverable
* Invoices
* Close Out
* Project2
* Project3
* Company 2
* Company 3
Of course the structure you choose will be dependent on your own business,
the nature of the information you want to store etc.
Daniel.
_____
From: Luis Braga [mailto:lbraga@fpf.br]
Sent: Wednesday, 22 September 2004 3:52 AM
To: users@subversion.tigris.org
Subject: Idea to manager documents
Hi
I whant manager documents with subversion, documents kind: process,
conventions, templates and more, this documents will be used to many people:
developers, managers, adm, accountant and others.
To development I did a tree as below:
myProjetc
---trunk
------src
------lib
------doc
------img
---tags
---branches
But to put only documents donīt make sense create trunk, tags and branches,
all users will access the files only to read, (copy and do your self
document based on templates).
I imagine a tree like that:
mydocs
------dept xxx
-----------file1.dot
-----------file2.dot
-----------file1.xlt
------dept yyy
-----------file1.dot
-----------file2.dot
-----------file3.ppt
Any one have other ideas?
Received on Tue Sep 21 22:40:44 2004