"Project Albatross" is done, and my neck sure feels good with the weight
lifted from it. I've started in on my "real" work, and the day to
day management of programming stuff needs to be revisited. (Don't mention how the next round of "albatross" changes are already in the works. Thanks.)
We have a home-grown and not so great web-based project management
system at work, which we augment with a wiki. Both run on hardware that's
past its prime and overloaded. It's funny how we manage to saddle ourselves
with the junk. I'm sure there's a replacement system is waiting in a box
someplace. To be fair, there's more pressing projects for our systems
staff to work on, and their group was, until just recently, short staffed.
I used to be there, so I cut them much slack. (Hurry up you guys! )
However, our software repository hardware WAS just upgraded, and along
with it came an installation of BugZilla for defect/enhancement tracking.
Of course, no one asked me what software to use for this project.
would have been my first choice.) Ironically, I'm the only person using
BugZilla thus far. Considering that I used the wiki for this stuff before, BugZilla is way better, but it has a few annoyances that we're trying to resolve. I'm keeping my options open for another product though.
On the version control front, I'm got resistance when I asked for subversion to be installed on
that new box. I only plan to use it in tunnel mode, so it's a very simple
install even. As subversion 1.1 is now final, I'll be switching my code
repositories as soon as they install it for me. (Even if they don't, actually. Mwah ha ha!)
In the end, I hope these changes improve my work and the work of my
entire extended group. We have much to learn and many next actions.