On Sunday, 12 May 2013, William Orr wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Simon Schampijer <mailto:<a>simon@schampijer.de</a>> May 11, 2013 11:55 AM Am 11.05.2013 um 16:45 schrieb Daniel Drake<<a>dsd@laptop.org</a>>: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On Sat, May 11, 2013 at 4:15 AM, Daniel Narvaez<<a>dwnarvaez@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <a href="https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/27" target="_blank">https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/27</a> We should probably decide if we want to keep using trac instead and if so turn the issue tracker on github off. Last time we discussed it, the idea was to keep using trac to not depend too much on closed source github. What are people thoughts these days? </blockquote> I would prefer to stay with trac, to avoid a split/migration, to keep the info on the tickets directly under our control, and to keep with our open source ideals. Daniel </blockquote> I wanted to give it a try to see how it works at least, going through the process with this ticket. I am not opposed to stay with trac though. Simon <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> _______________________________________________ Sugar-devel mailing list <a>Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote> _______________________________________________ Sugar-devel mailing list <a>Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> Daniel Drake <mailto:<a>dsd@laptop.org</a>> May 11, 2013 10:45 AM I would prefer to stay with trac, to avoid a split/migration, to keep the info on the tickets directly under our control, and to keep with our open source ideals. Daniel _______________________________________________ Sugar-devel mailing list <a>Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> Daniel Narvaez <mailto:<a>dwnarvaez@gmail.com</a>> May 11, 2013 6:15 AM Hello, I noticed people have started to report issues on github. <a href="https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/27" target="_blank">https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/27</a> We should probably decide if we want to keep using trac instead and if so turn the issue tracker on github off. Last time we discussed it, the idea was to keep using trac to not depend too much on closed source github. What are people thoughts these days? Personally I like github issue tracking a lot, though I see the point about it being closed source and I imagine a migration would be a bit of a pain. -- Daniel Narvaez _______________________________________________ Sugar-devel mailing list <a>Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote> Hello, Sticking with a privately controlled bug tracker is probably a good idea. However, trac really needs to be cleaned up, as there are a ton of 3-5 year old bugs floating around that have long since been fixed. I've started closing the few I can't reproduce in scm. As a new contributor, I initially had gotten the impression that no one used trac, and I was discouraged from reporting/fixing bugs there. </blockquote><div> </div><div>Yes, I couldnt agree more! </div> -- Daniel Narvaez