Hi, issues are per github project, so that would be the component. I think people use labels for priority and bug/enh, see for example
https://github.com/bower/bower/issues https://github.com/jshint/jshint/issues On Saturday, 19 April 2014, Gonzalo Odiard <[email protected]> wrote: > Looks more than comments than tickets, right? Or I am missing something? > > For our way of work, I think we need at least component and priority, > and if is a bug or a enhancement. > > Or there are another way to categorize them? > > I see labels here https://github.com/dnarvaez/test/issues > > Gonzalo > > > On Fri, Apr 18, 2014 at 6:07 PM, Daniel Narvaez > <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');> > > wrote: > >> >> By the way, if we decide to do it I think we should do it *before* the >> meeting, so that we triage using github already and we don't risk to lose >> information (or to have a really hard time fixing the script to preserve >> it). >> >> >> On 19 April 2014 02:03, Daniel Narvaez >> <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');> >> > wrote: >> >>> I tried to do a migration using trac2github. Here is what it looks like >>> >>> https://github.com/dnarvaez/test/issues/258 >>> >>> It's missing the reporter and it's not filtering by component but these >>> should be easy to add (it's php sigh, but still...). >>> >>> >>> On 19 April 2014 01:03, Daniel Narvaez >>> <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');> >>> > wrote: >>> >>>> Something is probably worth bringing up (it has been discussed a couple >>>> of times in irc) is the possibility to migrate to github issues. >>>> Maintaining trac is becoming a bit of a burden, especially because of spam >>>> prevention. Someone (Bernie?) suggested we could keep >>>> bugs.sugarlabs.org around for a while but in read-only mode, rather >>>> than migrating. Interested in people thoughts, I have not fully considered >>>> the migration issue to be honest. >>>> >>>> >>>> On 9 April 2014 14:10, Walter Bender >>>> <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');> >>>> > wrote: >>>> >>>>> We plan to hold a triage meeting to clean up bugs.sugarlabs.org on >>>>> Wednesday, 23 April, beginning at 9AM EST (14 UTC). We will be on >>>>> irc.freenode.net #sugar-meeting all day. Please join the fun. >>>>> >>>>> -- >>>>> >>>>> Tenemos la intención de celebrar una reunión de triage para limpiar >>>>> bugs.sugarlabs.org el miércoles 23 de abril a partir de las 9 a.m. EST >>>>> (14 UTC). Estaremos en irc.freenode.net #sugar-meeting todo el día. >>>>> Por favor, únase a la diversión. >>>>> >>>>> >>>>> regards. >>>>> >>>>> -walter >>>>> >>>>> -- >>>>> Walter Bender >>>>> Sugar Labs >>>>> http://www.sugarlabs.org >>>>> _______________________________________________ >>>>> Sugar-devel mailing list >>>>> [email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');> >>>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>>> >>>> >>>> >>>> >>>> -- >>>> Daniel Narvaez >>>> >>> >>> >>> >>> -- >>> Daniel Narvaez >>> >> >> >> >> -- >> Daniel Narvaez >> >> _______________________________________________ >> IAEP -- It's An Education Project (not a laptop project!) >> [email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');> >> http://lists.sugarlabs.org/listinfo/iaep >> > > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > -- Daniel Narvaez
_______________________________________________ Lista olpc-Sur [email protected] http://lists.laptop.org/listinfo/olpc-sur
