Slashdot Mirror
Open Source Bug Tracking for Visual SourceSafe?
rfsayre asks: "My employer has been looking into bug tracking options for use with Microsoft Visual SourceSafe, and while I don't have the authority or the resolve to encourage migration from the various MS tools that are in use, I would like to see an Open Source bug tracking system used, instead of Visual Intercept from Elsinore Technologies. Mainly I'm concerned that my employer will try to go as cheap as possible, and I think providing access to everyone from developers to QA interns could get expensive. Of course, what good is bug tracking if not everyone has access to it? So please, show me some Open Source alternatives that talk to SourceSafe, preferably with web based access."
If you're trying to get someone to move away from VSS, and are looking for more opinions on it (I haven't seen any actual *facts* yet, but there are plenty of opinions), a reasonably respected one would probably be Joel Spolsky's (from Joel on Software). He was the Microsoft "Program Manager" from VBA (the version of Visual Basic that Office uses for scripting).
Basically, MS doesn't use it internally - they don't trust it. Apparently they use a lot of their own stuff in development (for example -- Joel was on the Excel team, and they all used Excel for project planning, and added in project planning features, making it reasonably good for development planning. Here are the details). For NT (-> 2K -> XP) they used something called SLM, which was replaced by something else. Here's a USENIX paper on it.
His company has a bug tracking system ("FogBUGZ") too, and if you buy a site license ($1995) -- which covers the whole project team -- you get the source and are allowed to modify it and use your modified versions internally. See here for more info. It doesn't integrate with VSS, unfortunately ;-)