<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I assume <a
href="https://wiki.sugarlabs.org/go/Development_Team/Release#Glucose_.28base.29_modules"><a class="moz-txt-link-freetext" href="https://wiki.sugarlabs.org/go/Development_Team/Release#Glucose_.28base.29_modules">https://wiki.sugarlabs.org/go/Development_Team/Release#Glucose_.28base.29_modules</a></a>
is a proposal (as shown at the top). Before acceptance, it needs
some work.<br>
<br>
It needs to reflect our move to github/sugarlabs.<br>
<br>
The terms glucose, fructose, and sucrose need clear definition and
explanation. For example, fructose appears to be used to point to
a list of demonstration activities, in other cases, it the list of
activities with translations on translate.sugarlabs.org, and in
other cases it is a core set of activities to be included in an
OLPC Os or other image including Sugar. Sucrose is sometimes used
to refer to sugar as in 'apt install sucrose'. I suspect Mate
would react to 'install partner' as I do to 'install sucrose'. <br>
<br>
The section 'new modules proposal' as it applies to activities is
inconsistent with Sugar Labs goals as reflected in the developer
hub on ASLO. Sugar from the beginning has encouraged contribution
of activities by individuals with vetting comparable to <br>
<pre>|TestCase|
Click on Browse, Read, Pippy icons in the homepage and make sure all of them starts correctly.</pre>
Contribution of activities is completely independent of the Sugar
release cycle.<br>
<br>
OLPC OS includes a selected set of activities with each release.
Selection of this set does not involve Sugar Labs.<br>
<br>
This process for proposing new activities for Sugar activities as
I see it is:<br>
<br>
A contributor develops the activity on his own computer with a
current version of Sugar installed. When ready, the contributor
requests someone with owner permissions to githubs/sugarlabs to
create a repository for the activity. The contributor then pushes
the local master to github. Alternatively, the contributor could
create a personal repository on github and push there. Then the
contributor could request it to be copied to github/sugarlabs. We
advise contributors not to wait for perfection but to submit as
soon as they have something which others can try (10+ lines of
code as I remember).<br>
<br>
As a subsequent step, the contributor/developer/maintainer of the
activity could commit an incremented version number in
activity.info and request that the activity be published to ASLO.
This process can be handled by the appropriate Sugar Labs reviewer
who creates the bundle with setup.py dist_xo and copies it to
download.sugarlabs.org. <br>
<br>
ASLO should display the highest numbered version of an activity
(but may display the latest for simplicity). <br>
<br>
ASLO shows information not now a part of the bundle (developer,
summary, description, chosen license). I would propose this
information be included in activity.info where it would be visible
in the github repository. Activity.info lines such as repository=,
homepage=,update=, workswith= could be used to provide this
information to ASLO. We could also include tags='fructose',"fang's
fun" to associate activities with collections in activity.info.<br>
<br>
The internal developer community may know exactly what the 'Goals
and Modules' document means and the extent to which applies to our
practice, but there are many interested parties who are not in
that community and need an explanation. For example, what are GSOC
candidates to make of sucrose, fructose, glucose and so on? <br>
<br>
Tony<br>
<br>
On 05/01/2017 07:53 AM, James Cameron wrote:<br>
</div>
<blockquote
cite="mid:sugarlabs%2Faslo%2Fissues%2F3%2F298265475@github.com"
type="cite">
<p><a moz-do-not-send="true"
href="https://wiki.sugarlabs.org/go/Development_Team/Release#Glucose_.28base.29_modules">https://wiki.sugarlabs.org/go/Development_Team/Release#Glucose_.28base.29_modules</a>
updated.</p>
<p
style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>
You are receiving this because you commented.<br>
Reply to this email directly, <a moz-do-not-send="true"
href="https://github.com/sugarlabs/aslo/issues/3#issuecomment-298265475">view
it on GitHub</a>, or <a moz-do-not-send="true"
href="https://github.com/notifications/unsubscribe-auth/AAULku3mrSgPc9n9X2rQwDS2bMGyLYqxks5r1R8XgaJpZM4Mtv6p">mute
the thread</a>.<img moz-do-not-send="true" alt=""
src="https://github.com/notifications/beacon/AAULktgCKEr7sSt_frgIUviKZ9o78uWKks5r1R8XgaJpZM4Mtv6p.gif"
height="1" width="1"></p>
<div itemscope="" itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope=""
itemtype="http://schema.org/ViewAction">
<link itemprop="url"
href="https://github.com/sugarlabs/aslo/issues/3#issuecomment-298265475">
<meta itemprop="name" content="View Issue">
</div>
<meta itemprop="description" content="View this Issue on GitHub">
</div>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/sugarlabs/aslo","title":"sugarlabs/aslo","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/sugarlabs/aslo"}},"updates":{"snippets":[{"icon":"PERSON","message":"@quozl in #3: https://wiki.sugarlabs.org/go/Development_Team/Release#Glucose_.28base.29_modules updated."}],"action":{"name":"View Issue","url":"https://github.com/sugarlabs/aslo/issues/3#issuecomment-298265475"}}}</script>
</blockquote>
<br>
</body>
</html>