<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I am sure this would be helpful. However, the situation seems a bit
more muddled.<br>
<br>
The Sugar activities, which represent 90% or more of the Sugar lines
of code, are being relocated to the github accounts of individual
developer/maintainers - not under a single Sugar account. At the
moment this information is recorded in the activity.info file of the
activity itself. This change has not yet been implemented across all
of the activities. <br>
<br>
I don't understand the process. However, it appears that OLPC makes
the release images. It decides which Sugar activities will be
included in a release. <br>
I gather that SugarLabs has no say in this.<br>
<br>
I don't know the technical details, but it would seem desirable to
separate issue tracking into separate Sugar and Sugar activity
branches. The issues for Sugar related to releases (e.g. 0.108) and
for Sugar activities to version numbers. Update to Sugar activities
are independent from Sugar releases.<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 04/03/2016 09:36 AM, Dave Crossland
wrote:<br>
</div>
<blockquote
cite="mid:CAEozd0zVtkOXUePfe8PjxUYKy_m614_egVM8xaFG8Mjw2hYQgw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
Hi
<div><br>
</div>
<div>When sugar git moved from <a moz-do-not-send="true"
href="http://git.sugarlabs.org/sugar-old">http://git.sugarlabs.org/sugar-old</a>
to <a moz-do-not-send="true"
href="https://github.com/sugarlabs/sugar">https://github.com/sugarlabs/sugar</a>
in 2013, why did issue tracking stay at <a
moz-do-not-send="true" href="http://bugs.sugarlabs.org">bugs.sugarlabs.org</a>
and not move to <a moz-do-not-send="true"
href="https://github.com/sugarlabs/sugar/issues">https://github.com/sugarlabs/sugar/issues</a>
?<br>
</div>
<div><br>
</div>
<div>I think it would be a good idea to move the issues, since
pull requests can then be linked to issues (and even close
them automatically by including "closes #issue_id" in the
commit/pr message :) and development is concentrated in 1
place, with 1 UX.</div>
<div>
<div><br>
</div>
</div>
<div>There are only 182 open issues on <a
moz-do-not-send="true" href="http://bugs.sugarlabs.org">bugs.sugarlabs.org</a>
(<a moz-do-not-send="true"
href="https://bugs.sugarlabs.org/query?status=new&status=assigned&status=accepted&status=reopened&component=Sugar&order=priority">https://bugs.sugarlabs.org/query?status=new&status=assigned&status=accepted&status=reopened&component=Sugar&order=priority</a>)
so moving them over would likely take one person 3-4 hours.
I'm happy to do this if it would be helpful. </div>
<div>
<div><br>
</div>
-- <br>
<div class="gmail_signature">Cheers<br>
Dave</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>