Probably not the best time to ask this considering people are busy for the next release, but we're looking at trac for a project (apparently) and I remembered that there was a Xiph plan to move away from it. Does anyone have time to recall the reasons (I don't need an essay, just a keyword or two would be appreciated. -- imalone
I was the person who had a bee in my bonnet about moving away. The reasons were mostly out of box usability and the fact the the documentation is hell bent on explaining all the innards rather than telling you how to actually use it for anything. I still really don't see what it gives us that Bugzilla didn't. Not that Bugzilla was any great shakes. Oh and the 'wiki nature' plus having no utility for removing the constant influx of spam is a real pain too. You can only remove the wikispam by hand editing the database last I checked. "Oh, but you can write a little tool to do that for you!" say the Trac advocates. Well, if it's so easy... why hasn't anyone done it? Why isn't that included? Monty
2008/5/5 Ian Malone <ibmalone at gmail.com>:> Probably not the best time to ask this considering people are busy for > the next release, but we're looking at trac for a project (apparently) > and I remembered that there was a Xiph plan to move away from it. Does > anyone have time to recall the reasons (I don't need an essay, just a > keyword or two would be appreciated.I like trac for the way you can cross-index changesets against bug reports (eg. you write "fixes ticket:37" in an svn commit, and when you view that commit in trac it is hyperlinked to the bug report). I don't like it for it's spam attraction, as a result of which our trac fairly uselessly requires you to have an existing account in order to log bugs. I've heard good things about redmine recently, a similar project but with better user management and captchas and stuff, and perhaps some other features. You might want to check that out instead. Conrad.
On 4-May-08, at 12:02 PM, Ian Malone wrote:> Probably not the best time to ask this considering people are busy > for the next release, but we're looking at trac for a project > (apparently) and I remembered that there was a Xiph plan to move > away from it.When we switched, bugzilla had stagnated and trac was under heavy development. Those roles have mostly switched since then. As others have mentioned, trac has great integration with svn; the history browser is much better than viewcvs. It's also a great one- stop package for small projects. You can use the wiki to maintain project and documentation pages, and it's relatively easy to skin, so it's an instant website, except for blog support. On the other hand, it seems to get way more spam than bugzilla ever did/does elsewhere. It's also really only designed for single small projects; bugzilla handles multiple projects with multiple projects (like xiph.org has) much better. Bugzilla is messy perl+mysql, trac is only slightly cleaner python +sqlite, Trac uses an unpopular template engine, compared to bugzilla custom one. I think all this does add up to an essay, but there you go. :) -r