<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Welcome to the Sugar community (and its growing entropy)!<br>
<br>
You are proposing, appropriately, a new way to handle version
control for Sugar.<br>
<br>
There is documented procedure to add new activities or to update
activities on ASLO. This procedure is working with update
notifications in the ASLO mailing list. This process is independent
(and ignorant of) github. So your proposal is a change to current
practice.<br>
<br>
The separate tracking would be a byproduct of changing to a github
based procedure from our current practice
(<a class="moz-txt-link-freetext" href="https://bugs.sugarlabs.org/">https://bugs.sugarlabs.org/</a>) In my experience all bugs/issues are
reported here whether against a specific Sugar activity (say Etoys)
or against a component of Sugar.<br>
<br>
I am not sure whether Sugar is supported as a desktop by all GNU
machines. In particular, 32-bit Ubuntu is not supported. Debian
dropped the Record activity because it does not use gstreamer1.0 or
gtk3. This is one of the eight protected activities which are
considered essential to a running Sugar. As far as I know, SOAS does
not offer an 'install' option.<br>
<br>
You are right about the issue of which activity versions support
which Sugar releases. This is complicated by the factor that some
ASLO entries have more recent versions stored as 'earlier versions'.
Someone needs to grab the handle and set up an ASLO system that can
identify which activities work with which versions and make
potentially multiple versions visible in ASLO as necessary.<br>
<br>
During the recent GCI, Walter Bender and some of the participants
came up with a scheme which allows an activity with a binary blob to
identify the XO model and configure with the appropriate blob at
run-time. I suspect there are activities which need this fix.<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 04/03/2016 12:38 PM, Dave Crossland
wrote:<br>
</div>
<blockquote
cite="mid:CAEozd0wb6fo8B_hxPHKVtqX=pgndroeX=a7PUCXEBhMm3La=pA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On 2 April 2016 at 22:18, Tony
Anderson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">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. </div>
</blockquote>
<div><br>
</div>
<div>I think that is fine :) If they would like to make
their activity 'official' then they can ask to be invited
to the <a moz-do-not-send="true"
href="http://github.com/sugarlabs">github.com/sugarlabs</a>
organization, and then after they accept the invitation,
they can go to <a moz-do-not-send="true"
href="http://github.com/username/repo/settings">github.com/username/repo/settings</a>
and at the bottom move the repo to the org. </div>
<div><br>
</div>
<div>(Or, someone who has joined the org with appropriate
permissions can fork their repo into the org, to maintain
an 'official' copy of it, and the initial developer or
anyone else can then make pull requests to it. However, I
think the first way is better since then Github will show
that as the 'upstream' repo on network graph pages, eg <a
moz-do-not-send="true"
href="https://github.com/sugarlabs/sugar/network"><a class="moz-txt-link-freetext" href="https://github.com/sugarlabs/sugar/network">https://github.com/sugarlabs/sugar/network</a></a>) </div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">At the moment this
information is recorded in the <a
moz-do-not-send="true" href="http://activity.info"
target="_blank">activity.info</a> file of the activity
itself. This change has not yet been implemented across
all of the activities. <br>
</div>
</blockquote>
<div><br>
</div>
<div>Cool - that seems like a good milestone for Sugar Labs
this year. I added it to <a moz-do-not-send="true"
href="https://wiki.sugarlabs.org/go/Vision_proposal_2016">https://wiki.sugarlabs.org/go/Vision_proposal_2016</a> </div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> 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. I gather that SugarLabs has no
say in this.<br>
</div>
</blockquote>
<div><br>
</div>
<div>That sounds great to me :) </div>
<div><br>
</div>
<div>As I understand it, Sugar is a desktop environment for
all computers that can run GNU, while OLPC makes "OLPC
OS," which is a GNU distribution tailored to XO laptops
that packages Sugar and GNOME desktops.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> I don't know the
technical details, but it would seem desirable to
separate issue tracking into separate Sugar and Sugar
activity branches. </div>
</blockquote>
<div><br>
</div>
<div>That is unavoidable with the way Github is designed.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">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>
</div>
</blockquote>
</div>
<br>
However, surely some Sugar releases are requirements for some
activity versions? Eg, Chat 78 (<a moz-do-not-send="true"
href="http://activities.sugarlabs.org/en-US/sugar/addon/4069">http://activities.sugarlabs.org/en-US/sugar/addon/4069</a>)
says it requires a Sugar release of 0.86 or higher (and may
not work with 0.108, according to the metadata on that page) <br
clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">Cheers<br>
Dave</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>