Quote:
|
Originally Posted by schettj
Version control would be nice, but unless you go with some web-based cvs it's not gonna work with the distributed development you're going to have here. I I don't think sourceforge is gonna work... hm Maybe it would.
We could check in the non-binary bits of the kitchen (no one should be patching binaries anyway) and that way we can track the changes/merge etc. I use CVS on my own kitchen (after getting burned myself making too many changes, and not having a known good version left  )
So... that should not be a legal issue with MS (no MS code) - setting up the tree would be a bit of work, but you should then be able to check it out and overlay it on top of a kitchen with binaries. |
Schettj, I was contemplating your post here on my long drive into work. I understand the complexity and your concerns with distributed development, as it relates to version control. And I began thinking, "What's the simplest way that we could do this?", and here's what I came up with:
We have no shortage of people willing to help with this project. Why not get a volunteer to be the "keeper" of the code. Once the developers deliver their changes, it would be this person's job to merge these changes into the new build and track the changes. Since we're really only delivering files and registry changes, off-the-shelf tools are available to make this easier. This would require that person to have a developer's level expertise, but I think it's better than having to setup a source control server, which is overkill for what we're trying to do.
What do you think?