introducing Trac_Assigner: a script to automatically assign tickets to their port maintainer

[Eric Le Lay]

Marko,

thanks for your feedback.

I was confident I could come up with a working script without too much
trouble, having done similar driving of websites in the past.
On the other hand, a plugin for trac required
that it would be installed in macports' infrastructure, tested on a
replica, what have you...
So I've preferred to cover the need first, with
maybe a bit too much traffic
- not so much I think, after a first overhaul of old/missed tickets.

I hope it could be set up as a cron job on some macports server, not run
by every maintainer (no need to: it assigns each and every ticket). This
way, having it run once per day, the resulting traffic would not be
too high.

Another way to curb traffic overflow (if it exists) would be to install
the trac XML-RPC plugin (or is it already installed ?) and let the
script talk to trac this way instead of parsing web pages/posting forms.

Cheer,
Eric

Le Sun, 22 Sep 2013 19:35:40 +0200,
MK-MacPorts at techno.ms a écrit :

> On Sep 22, 2013, at 6:48 AM, Joshua Root wrote:
> > On 2013-9-22 05:22 , MK-MacPorts at techno.ms wrote:
> >> Wouldn't it be much more efficient to have this already dealt with
> >> by trac itself during ticket creation?
> > Probably. You are certainly welcome to write such a trac plugin. :-)
> 
> Josh, I had brought this up quite a while ago already. Since then I
> am subscribed to the trac's ML, but so far - as you can see - I
> haven't yet come around to code anything. ;-( (Obviously the issue
> hasn't yet surpassed my suffering threshold…)
> 
> But I really think it would be best to integrate it at trac level,
> instead of letting every maintainer her/himself query trac's current
> database and run Eric's script. Too much redundant traffic. When I
> saw his post popping up in my inbox I cheered, because I thought it's
> the long-awaited trac-integrated feature... I wish Eric had known
> about this idea, perhaps he would have avoided to code that much perl
> and instead had dived into coding that trac-plugin. :-)
> 
> Marko


> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev