[Sugar-devel] [sugarlabs/aslo] does not show latest version of an activity (#3)

Tony Anderson tony_anderson at usa.net
Sun Apr 30 21:15:10 EDT 2017

I assume 
is a proposal (as shown at the top). Before acceptance, it needs some work.

It needs to reflect our move to github/sugarlabs.

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'.

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

Click on Browse, Read, Pippy icons in the homepage and make sure all of them starts correctly.

Contribution of activities is completely independent of the Sugar 
release cycle.

OLPC OS includes a selected set of activities with each release. 
Selection of this set does not involve Sugar Labs.

This process for proposing new activities for Sugar activities as I see 
it is:

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).

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.

ASLO should display the highest numbered version of an activity (but may 
display the latest for simplicity).

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.

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?


On 05/01/2017 07:53 AM, James Cameron wrote:
> https://wiki.sugarlabs.org/go/Development_Team/Release#Glucose_.28base.29_modules 
> updated.
>> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub 
> <https://github.com/sugarlabs/aslo/issues/3#issuecomment-298265475>, 
> or mute the thread 
> <https://github.com/notifications/unsubscribe-auth/AAULku3mrSgPc9n9X2rQwDS2bMGyLYqxks5r1R8XgaJpZM4Mtv6p>.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20170501/51de8762/attachment.html>

More information about the Sugar-devel mailing list