On Thu, Oct 13, 2011 at 2:35 PM, Will Coleda <[email protected]> wrote: > On Wed, Oct 12, 2011 at 6:28 PM, Jonathan "Duke" Leto <[email protected]> > wrote: >> Howdy, >> >> There is a new dashboard for organizations that shows all of their issues: >> >> https://github.com/organizations/parrot/dashboard/issues >> >> This is a great view into the Parrot organization and makes it easy to find >> stuff to hack on across all of our repos. >> >> I dislike Trac, so I will be using Github issues for new bugs+patches going >> forward. I hope others join in, but this isn't an "official" policy (whatever >> that is supposed to mean in the Parrot community). >> >> I am of the opinion that there is more noise than signal in our Trac TT's >> currently. We could programmatically convert our TT's to Github issues, but >> that is not a good solution either. We need to remove a lot of old and >> irrelevant tickets first. >> >> This is not a task for a new-comer, and everybody that is qualified to kill >> old >> tickets doesn't really seem to want to do it. Why not? >> >> Duke >> >> -- >> Jonathan "Duke" Leto <[email protected]> >> Leto Labs LLC >> 209.691.DUKE // http://labs.leto.net >> NOTE: Personal email is only checked twice a day at 10am/2pm PST, >> please call/text for time-sensitive matters. >> _______________________________________________ >> http://lists.parrot.org/mailman/listinfo/parrot-dev >> > > Speaking for myself, burnout. I've done the task too many times for > parrot so far. > > In the last day or so, I provided some advice in IRC on how to triage > these old tickets and start closing some again. Hope that helps. > > My recommendation on migrating tickets is to have a way to transfer > tickets over programmatically; even if you only use it on one triaged > ticket at a time, you will save yourself much madness. > (Recommendation: mention the URL for the ticket in each system in the > other system. Create a new status for "migrated" tickets, or add an > explicit comment to the closed trac ticket along with the URL "marking > resolved just to close the ticket, for update see...")
When I moved the pirc bugs out of trac and into parrot/pirc's github issues, I looked at App::SD, which in turn uses Net::Trac, and Net::Github. I found these two to be quite effective at migrating simple tickets. If we do implement some ticket auto-transfer tool, I'd recommend starting there. I have attached the script I used to do the transfer the pirc as an example for anyone eager to get started on this. > Regards. > > -- > Will "Coke" Coleda > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev >
t2g.pl
Description: Perl program
_______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
