On 1/29/2012 6:03 PM, Greg Newby wrote:
When you write of standalone version control systems, do you mean using svn/hg/git out of the box, and developing all the other software for our needs?
Yes, sort of. Even TRAC requires a stand-alone Subversion installation; TRAC just interfaces into it. CVS is probably sufficient to our needs, and one of your servers probably has CVS already installed on it (it tends to be part of a standard Linux distribution). If that's what you want to do, it's just a matter of setting up users, collecting private SSH keys, building a CVS repository, etc. CVS is what I used for www.ebookcoop.net. If you think we would be moving to TRAC eventually, maybe a stand-alone installation of Subversion would work. If you, or others, think that a more distributed, high-maintenance, low-bandwidth solution is better, choose Git or Mercurial. I'm primarily a Windows workstation user and Tortoise makes clients for all four. I'm happy with whatever you pick, and I think most of the others would be as well. Don't pick RCS or VSS as they are not designed for concurrent access. When I said "sort of," I was referring specifically to the "developing all the other software," part. For page-at-a-time editing I think the Wikimedia engine could be adapted. For development wiki's, defect tracking and RSS feeds, we may want to adopt TRAC in the future. I'm a firm believer in not reinventing wheels. A Frankenstein's monster approach could work.