On 5/17/06, Yves Moisan <email@example.com> wrote:
> I was thinking of setting up Subversion to
> manage our software projects, so I figured I'd call repositories based on the
> software project names (then trunk, branches ...), but someone here suggested we
> could also manage customer projects with Subversion.
> I called this post "general artifact management" because I'm not quite sure what
> I'm hitting here (SCM/CRM ...). Anyhow, the structure that would be managed
> would be of this kind :
> - Project#
> - SubProject#
> - Data (general resources about the SubProject)
> - Documentation
> - CAD files
> - Image files
> - XML files ... (any number of directories as a function of file type)
> - Customer input
> - Deliverables
> My fear is that this is not quite the SCM sweet spot Subversion is there for and
> I'm not sure Subversion is the best overall tool for that. Or it could be used
> to manage the file directories, but maybe some other aplication on top of
> Subversion could be used for the rest. The idea is that we would like to be
> able to reproduce exactly what was delivered to the customer and potentially
> launch deliverable branches. Anyone out there using Subversion that way ?
Sounds like you're looking for a hybrid document management and change
management system. SVN isn't going to be a silver bullet, but you
could definitely use it as the core of such a system. The branching,
version tracking, etc. is of course SVN's strong suit - maybe build a
database and GUI or web interface around it to manage the metadata
about the documents themselves? Properties can be used for metadata
as well, but they're not terribly searchable.
You might want to check out Trac, a wiki that works with and
integrates with SVN.
It's not a common scenario, but people do use SCM systems as document
repositories without any code in them at all. You just don't hear
about it often.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu May 18 18:54:26 2006