[Sugar-devel] Migration from bugs.sugarlabs.org to Github

Tony Anderson tony_anderson at usa.net
Thu Dec 14 08:52:22 EST 2017

Is our bug-fixing technique capable of fixing bugs present in 0.110? It 
the the XOs will be limited to 13.2.8 and 0.110 for the forseeable future.


On Thursday, 14 September, 2017 10:39 AM, James Cameron wrote:
> Thanks for the idea.  If someone is available to do it, great.
> A quick bulk insert of issues could be done using the GitHub API, or
> it could be done by hand by someone who knows nothing about Sugar.
> But it feels like unrewarding and wasted work, and there is more
> important work to do, such as fixing bugs or developing features.
> We have no plans to shut down the Trac instance bugs.sugarlabs.org and
> lose access to all those ideas.
> Also moving them to GitHub seems very unlikely to accelerate the rate
> at which tickets are resolved.  Firstly, because the very people who
> might resolve tickets are busy moving tickets.  Secondly, because
> those of us who are resolving tickets are able to do so with either
> bugs.sugarlabs.org or GitHub issues.  Where the issue is lodged has no
> relevance to fixing it.
> We also lack regular testing and reporting of new issues; either in
> bugs.sugarlabs.org or GitHub issues.  It has been nice to see GitHub
> used more, but mostly that is because of account approval delays on
> bugs.sugarlabs.org.
> There are some bugs.sugarlabs.org bugs that we may never fix,
> because the person who wanted them isn't interested any longer.
> Bringing those bugs into GitHub issues could be disruptive and
> unnecessary.
> On Thu, Sep 14, 2017 at 08:10:00AM +0000, Utkarsh Tiwari wrote:
>> Hi everyone,
>> While going through https://bugs.sugarlabs.org today, I came across
>> a lot of tickets that were raised quite a long time back ( > 2
>> years). I was wondering if we could do a GCI task of raising those
>> tickets into their respective Github respositories which can
>> accelerate the  rate at which our tickets get resolved.
>> This way newcomers while going through the SugarLabs repositories
>> will be able to easily spot the issues regarding the specific repo
>> they are watching. As not everyone is aware of our bugzilla, this
>> could be a nice alternative to catching contributor's attention to
>> raised tickets. What do you all think?
>> Regards,
>> Utkarsh Tiwari
>> References:
>> [1] https://bugs.sugarlabs.org/
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel

More information about the Sugar-devel mailing list