Hi I have a couple of comments / questions on the subject. 1. I like the idea of code.google.com since we are already using the Google Groups. 2. Is Douglas server repairable? Is it only the two hard drives that failed or is it more severe? Thanks and have a nice day! Andrew Lynch From: n8...@googlegroups.com [mailto:n8...@googlegroups.com] On Behalf Of Wayne Warthen At the risk of causing some strong reactions, I propose the idea of using one of the existing source code control sites. The obvious ones to me are www.sourceforge.net (well known) and code.google.com (since we are already using groups.google.com). I am still playing around with them, but thus far prefer the simple, clean code.google.com system. They all have integrated support for the popular source code control systems including Subversion (which is what we have been using), Git, and Mercurial. We can continue to use all of the same client tools we have been. These sites are free, reliable, and provide a nice set of ancillary tools like issue tracking, wiki, notifications, and reporting. I would not try to create one central project for all of N8VEM, rather suggest that each project create it's own and the Wiki would have a page that provides an index of the projects that exist. I would still advocate that "releases" of code be posted on the Wiki directly because I expect that many N8VEM builders have no desire to deal with source code management. I will go even further and suggest that GIT may be a better fit for the actual version control engine for us. It is more oriented toward distributed development. However, if each project was setup independently, it would be possible for each project owner to make this decision themselves. -Wayne -- |