>Thanks for the reply. My the requirement was that the
>people on the third floor would not have to be taught
>new software whilst maintaining one single active
>version of their documents!
Well, good luck with that :)
>I was hoping I would not have to install any client software because that means
>the people on the third floor need to be persuaded to use it and shown how
>to use it, reminded to use it and how to use it and helped while they are using it..
As a sysadmin myself, I can completely identify with your hope to not
have to install new software. However, if you want rev-control,
you're going to need to install something. Even if you use MS's VSS
product, you'll still have all these same concerns, since, afaik, no
one has come up with an OS-independant, time-based, revision-control
network file system yet. And, ideally, that's what we all really
need :)
>What I'd read on microsofts and subversion site
>yesterday gave me the impression its MS office was
>webDAV enabled and there would be some sort of innate
>version control (at least implementing a locking model
>were only one person can check the document out).
MS Office does have webDAV capability, though I believe it's more a
feature of the OS, not Office. And I believe, but may be wrong, that
they only slightly tweaked their Office code's normal rev-control
feature to operate with a "Web Folder". I have no idea how well
this works, if at all. Most likely you'll need to be running an IIS
web server to get all the functionality they promise.
The Apache/WebDAV/SVN combination does in fact allow you to mount the
repository as a "Web Folder". WebDAV itself, despite the fact that V
stands for Versioning, does not provide for any versioning
capability. That part is upto the DeltaV protocol. However, the
DeltaV protocol is not yet mature enough, nor moving fast enough to
provide svn with all it needs. Therefore, the SVN repository has some
very specific APIs, which are not part of the standard WebDAV/ DeltaV
protocols.
>I had read on the webDAV site in the FAQ's that DAV
>could replace CVS in the future, but at the moment it
>only employs the locking model.
That is an eventual goal of DAV/DeltaV, but I think it's going to be
a long time in coming.
>I will install tortoise and see how complicated it is.
At the very least, it shouldn't be more complicated than Visual
Source Safe, and the back end repository is a *lot* better and more
flexible :)
I wouldn't worry too much about having to install/support tortoise.
They seem to have a pretty active development group. Try it out, set
up an internal web site with a Wiki, and document as you go. Point
people at the wiki for the basic install/set up procedures and
encourage them to contribute to the docs :)
--
Seeya,
Paul
GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 30 15:52:04 2003