I'm sure I've been pretty conspicuous lately by my absence. The reason is simple: I've been involved in a pretty big project, and simply have not had much time for anything else. I know, I had planned on creating a wonderful demo application, complete with docs and stuff, because I thought my time at this client was winding down. Turns out to have been the proverbial "calm before the storm", and I've been quite busy ever since.
I wish I could say that I'm finally able to spend some time on that project again, but unfortunately, that's not the case. I'm still in the middle of a lot of work, and don't see an end for at least a few months. That brings me to my main concern: framework maintenance. I've seen a series of bug reports here (yes, I still read the digests!), but have not been able to test, fix and re-test them. So I have an idea: let's make this truly a group project.
The catch, of course, is version control. I keep the Codebook source in Visual Source Safe on my server, but that doesn't really solve the problem - how will anyone else check something out and check it in? The only way to do that that I know is to use <a href="http://www.sourcegear.com/sos/index.htm" target="_blank">Source Offsite</a>, but that poses its own problem: the license fee. Each license is US$239, and they require each unique user to purchase a license (i.e., no "concurrent" licenses). That seems kind of steep, unless you already own a license.
So does anyone else have any ideas? I'd like to make this as open as possible, while still maintaining some consistency.
<font color="#cc0000"> ___/
/
__/
/
____/</font>
Ed Leafe
©2001 Ed Leafe |
