Trac Spam

[Zachary West]

On Sun, Nov 28, 2010 at 18:50, Evan Schoenberg, M.D. <evan.s at dreskin.net>wrote:

> Other than "then we don't have to run it on our server" is there any
> *advantage* to Google Code issue tracking over Trac? As far as I'm aware,
> today's spam attack is the first time in about a year we've done anything on
> an administrative/server management level to keep Trac running smoothly -
> this does not seem to be a significant burden.
>

Keeping Trac up to date, etc., is a bit of a pain in the ass. It would be
cool to not have to run this part of the project ourselves merely because
I'm the one who has to maintain it. :) It's not hard, though, no; it rarely
has any problems.


>
> The origin of the "move to Google Code" discussion appears to be that some
> folks want ticket creation to be something we control rather than letting
> users do it.
>

I don't care for this idea..


>
> I personally think that the convenience of users submitting their own
> tickets outweighs the problems with marking duplicates and closing bad
> tickets, but I'm not on the front lines of Adium support.  It seems to me
> that we should look into other mechanisms to reduce duplicate tickets rather
> than creating a personnel-dependent bottleneck.
>

I agree. However, which is more likely for our users to have: a Google
account, or an Adium Trac account? I think we could get reports if users
don't have to jump through hurdles to deal with us.


>
> In any case, we could easily set Trac not to let users create tickets;
> moving to a whole new system is not needed for such a change.
>

> Similarly, we could delete all existing tickets, if "starting fresh" were
> the goal, or we could create a new environment, keep the old one up for
> historical access, and migrate any tickets we wanted.  I don't think that's
> a very good idea, either, but my point is only that moving to a whole new
> system is not required to accomplish this.
>
> -Evan
>


I agree, but a new DB would be cool too.

Zac
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20101128/50013fbc/attachment-0002.html>