[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Info about SVN

From: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Tue, 17 Apr 2012 22:02:04 +0200

Guten Tag Balta, Andre,
am Dienstag, 17. April 2012 um 19:30 schrieben Sie:

> I have a list of
> requirement that my information management software needs to do. I was
> hoping you could confirm if SVN can or cant do the following:

Did you even read any documentation or whatever about what Subversion
actually is? You could have answered most of your questions on your
own. Subversion is focused on version control of "information" in
files, it's not a general "information management software", whatever
that means.


> * Assign authorized users with groups, roles and permissions
> (CRUD)



> * Web based view and interface


> * Support TLS/SSL

Yes, over WebDAV.

> * Support digital signatures (certificates/CAC)

Next time you really should take at least 5 minutes to describe what
you want to do with digital signatures. Subversion version them as
files, but I doubt that's what you want. Using WebDAV you may
configure Apache to use server and client side certificates for
authentification. Subversion doesn't sign the repository content and
checks signtures.

> * Support Content management

Subversion does manage content of files, if this is what you want.
It's not a CMS like Joomla or else.

> o XML documents

Man, really, 5 minutes to describe what you want... Subversion does
version XML-files, if you want it to do.

> o XSLT (transforms)

...and it versions XSLT files, but it's not a XSLT processor.

> o Cascading Style sheets

You can version it as file.

> o 3D models (COLLADA) - view or javascript

You can version it as file.

> o Serve Javascript enabled web pages

You can version it as file.

> * Support creation of task items, assignment to action officers,
> suspense date and status

Subversion is not a ticket system, but can be integrated with popular
ones like Bugzilla, Trac etc. in different ways.

> * Support version control of content (tied to issues)

Depends on issue tracker and it's integration, but yes.

> * Support workflow for content

Depends on what you mean with workflow, Subversion does provide
mechanisms to lock files, excluding someone else to change it.

> * User defined workflow schemas

Users can lock files, branch, merge and if you sit down and write this
as a workflow template for your users, it will version it.

> * Automated promotion based on criteria
> * User promotion limited by access

Subversion provides server and client side hooks to "promote based on
criteria" and even "something".

> * Support e-mail notification on state change

Server side hooks exist for things like that.

Mit freundlichen Grüßen,

Thorsten Schöning

Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow
Received on 2012-04-17 22:02:38 CEST

This is an archived mail posted to the Subversion Users mailing list.