Looking for something to hack on?

[Will Coleda]

On Mon, Oct 17, 2011 at 8:07 PM, Andy Lester <andy at petdance.com> wrote:
>
> On Oct 17, 2011, at 2:14 PM, Moritz Lenz wrote:
>
> How about non-strawman arguments? What do you say to users who put a lot
> of effort into submitting good bug reports, and which will got lost by
> the non-migration?
>
> Maybe someone can do the migration.  Someone who is normally just doing scut
> work on C code, maybe?  Like me?
> xoxo
> Andy
> --
> Andy Lester => andy at petdance.com => www.petdance.com => AIM:petdance
>
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>
>

If the general consensus is to switch, that's fine, but my
recommendation would be to convert /everything/, and tag any tickets
that came over from trac with a label of some kind like "needs-triage"
or "from-trac" then we have a builtin list of tickets that we know
needs to be reviewed from the old system. Once a human has laid eyes
on the ticket and decided if it's worth keeping (some may be old
roadmap requests, some may be obsolete build reports from long ago,
patches that don't apply), remove the label.

Any new tickets should be triaged rather sooner than that, so we can
use the ticket status (new/open) to indicate if something needs triage
instead of the label.

If we can get more eyeballs on tickets in github, that's fine. I don't
think it matters if we close them before or after the migration, as
long as it's done.

-- 
Will "Coke" Coleda