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

Re: Request: Specifications / Requirements that only svn can meet

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 8 May 2009 22:50:08 +0100

On Fri, May 08, 2009 at 01:15:23PM -0700, webpost_at_tigris.org wrote:
> Folks,
>
> I work for a government contractor that is likely to force us into using an extremely
> overpriced and unnecessarily complicated version control system adored by pointy-haired managers everywhere (you probably know the one... :).

Hmmm... I think your case is clear to me ;)

> I have been asked to submit requirements for our new version control
> system. In an effort to delay or prevent the onset of ill-rationality
> I want to present requirements that can be met *ONLY* by svn.

It is open source. Using the software is free of charge. You don't
depend on a single vendor to provide support, so there is no vendor
lock-in when it comes to support.

If Subversion does not fulfill your requirements you can improve it.
The community is run very professionally. Have you already noted the
refreshing lack of flame wars on our lists? The developer community
is very open for constructive contributions from users, so getting things
into the code base that your organisation really needs is very much
possible if you communicate well with the community and contribute
in a constructive and co-operative manner.

With enough skill and patience, you can even grow your own in-house
committers that co-maintain Subversion for you together with the rest
of the community. The place where I work has done that. And you are
encouraged to do this as well when using Subversion in your organisation,
without having to commit to any formal agreements. The only thing that's
required is maintaining a healthy relationship to the community.
By definition, a proprietary vendor cannot provide this.

Stefan
Received on 2009-05-08 23:50:59 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.