As we worked to get the Alpine Executive Center up and running, we made new versions of a lot of scripts. It wasn’t just a matter of dragging and dropping existing scripts in, although in retrospect it could have been more like that than it was. But even if we had done the very best along those lines, there are always going to be version changes as we go along. How could we manage them?
We passed scripts back and forth frequently. The result of that was that we almost always had almost the right version in our inventory and we could almost always almost find it. In other words, to quote our government, “Mistakes Were Made”.
We would have done better, I believe, if we had had a small CVS or Subversion repository, and the habit of always keeping the current scripts in there. If we needed to make a change, we might edit a script in place, but if so, we would then extract it and make it the current version in the repository. That way, everyone (just two of us but you never know) would be able to see the current versions whenever we needed to make another change. It might also make it easier to keep all the vehicles and rezzers synched up. Certainly wouldn’t make it worse.
It might even have been possible to have used the test bed on our own land more extensively, and then use a code repository as a staging area for loading the AEC’s objects. In any case, the repository, and using it in a patterned way, would give us more certainty that we knew what was running at any given time. It might even have saved us from one slightly unfortunate branch that still troubles me.
I’m not sure where we could host such a thing. Perhaps there is a free location out there, and I believe that Dizzi controls some RL web sites where we might put these things. In any case, I think it would help.