TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Yet it is true that Svn, like CVS, is built on a concurrent
versioning model rather than “lock-modify-unlock”: it's built for
collaboration. While you may set file-level locks (as of Svn 1.2),
the system isn't designed for every checkout to be a "reserved
checkout" (locked).
Have you considered whether locking is so important? Let's say that
James and Kirk check-out `Manual.doc` for editing at more or less
the same time. James, who finishes first, commits his back as part
of changeset 51. A little later, Kirk commits his back in changeset
52. It obviously doesn't contain James's changes.
Tiberius notices that this has happened -- there are only five
people in the group -- and it's trivial for him to check-out both
versions 51 and 52, merge them *in MS Word* (applying some necessary
judgment), and commit back version 53.
Let's think about Tiberius. Doesn't he represent a necessary role
in any case? Mustn't somebody be in charge? Seems as though it's
hoped that file-locking can replace all need for communication. But
can it? Is that even wise?
It may be that you're needing something more like enterprise content
management. Maybe John P. can get you a discount on Documentum, or
perhaps you're willing to enter SharePoint hell. If not, take a
look at Alfresco:
You'll still need best practices, but it seems that Alfresco (which
I've only tested, not lived with) provides a means for embedding
them. It's platform neutral and potentially free to use, if you can
live with community support (forum, Wiki) and don't need purchased
support.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l