On May 8, 2009, at 4:15 PM, 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... :).
>
> 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.
>
> 1. Is there a prepared list of specifications / requirements that
> only svn can meet available somewhere?
>
> 2. If not or there are additional requirements you folks know about
> please mention them on the list.
>
> My deadline for submitting this list is COB Monday, 11 May 2009.
> I'll be happy to wrap up the discussions here with a summery of svn
> only requirements so that others can benefit.
>
> -Andrew
How about at least setting the requirements such that a number of open-
source tools would do? I seriously doubt that Subversion has
something so unique and vital that you can't find with other open
source version control systems. Seems to me that looking at the setup
costs would be a good thing. That's not to say that Subversion
wouldn't do the job. You mainly want to convince them not to use the
expensive bloated solution right?
-steve
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2122357
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-08 23:18:55 CEST