On Thu, February 2, 2012 10:41 am, don kretz wrote:
Good - then exactly what does it have to do with using a VCS to store document versions (compared to, say, the way they are stored now where anyone can acquire any format they want, but can't submit any new versions except to I guess a whitewasher?)
When you say "document versions" do you mean subsequent iterations of a single document, or multiple variations of a document ("snowflakes")? If the former, then a VCS records all the iterations, who was responsible, what the changes were, and allows a user to pick any historical version. It enables a smooth evolution of the file as our understanding of the requirements improve. If the latter, then it may or may not have anything to do with it at all, but I don't care. I'm not interested in a system to build a snowdrift. That's Mr. Newby's vision, not Mr. Hutchinson's. As for getting a new and improved version out of the master control system and into the traditional repository, that's also a problem I'm not interested in for the moment. I want to build a system that the White Washers could turn to if they were so inclined. If they don't want to take advantage of it, that's not my problem. You can lead a horse to water, but you can't make him drink.