Trac Spam

[Peter Hosey]

On Nov 27, 2010, at 21:18:42, John Bailey wrote:
>> 2. We still lock out user submission of Issues, but allow voting (star system). We encourage the use of the forums for users to submit their bugs, following which we confirm or dismiss them. If confirmed, then a dev creates an issue in the Google Code tracker to represent the bug. Users who report well described bugs on the forums gain access to the Google Code issue tracker.
> 
> This is an inordinate amount of overhead.  Requiring a developer to open a ticket for an issue is a waste of the developer's already severely limited time.

Currently, that time (of helpers as well as developers) is wasted on closing duplicate tickets. On Growl, we do exactly what Jordan has suggested—use Google Code, file tickets ourselves—and we have nearly eliminated duplicate tickets*. I can't predict how well such a system would scale to Adium, but it's been working very well for Growl.

*I think the last duplicate ticket we had was filed by me, because I forgot we already had a ticket for the issue.

> Additionally, how… do you achieve integration between the mercurial repository and Google Code so that you can close tickets with a commit message?

I'm pretty sure GCH doesn't support this. At any rate, we're not using it on Growl, since we primarily host our repositories ourselves (our GCH default repo is a mirror of our development repo).

Not directly in reply to anything anybody's said so far: GCH tickets are pretty dumb, intentionally so. Tickets are plain text; comments on them are plain text. Categories, milestones, etc. are all plain-text labels. The system works, but it's a significant change from Trac's customizable separate pop-up menus.

I certainly would not recommend exposing GCH's new-ticket form to Adium users.