Re: [Bacula-devel] Developer coordination

[David B. <db...@si...>]

> I have to say i like it quite a bit. Very powerful search features and
> ways of customizing your view of the tickets in the system.

Another vote from here. It's a nice tool, if you add a few features
around it.=20

> Perl comes bundled with a tool called perlbug which knows how to write
> a bug report for perl that contains the necessary diagnostic and
> environmental information to track the bug down. It then sends an
> email to the bug list where RT automatically picks it up, replies and
> forwards a copy to the main dev list.

Glad you mentioned this; this would be an enormous help (or structure a
WWW-based front end to collect the info you want, and use that to
actually submit the bug report). You or someone else will probably have
to do a few months worth of "that's a bug, submit it via xxxx" on the
mailing lists to get people used to the idea, but it would make it
easier to work on stuff.=20

Given the out-of-control state of the spam industry, allowing people to
directly open tickets in RT via email is a good recipe for a lot of spam
noise. We had to do some fairly draconian whitelist processing to avoid
getting our support queues hammered by spammers. Disabling the automatic
registration function in RT is a good idea -- if you combine it with a
tool like perlbug, you at least make it a little bit daunting to annoy
lots of people. A perlbug-like interface that talked to a WWW
application that did some validation on the input could also manage the
whitelist, and then pass the posting on to RT.=20

Another comment: if you're going to use RT, then I'd put in a vote that
you decommission mantis and make the switch complete. Mantis works, but
you're not going to want to have two places to hunt for stuff, and
having the ability to link tickets and relate things within ticketing
systems is a really Good Thing that you won't be able to do if both
continue to be actively used.=20