[Sugar-devel] New ASLO Project Definition

Tony Anderson tony_anderson at usa.net
Thu May 18 21:19:42 EDT 2017

Hi Sam,

Thanks for the proposal. Naturally this raises the question of the 
relationship between your ASLOv3 and the GSOC project. Do you see two 
parallel implementations or a merger of the two projects?

I agree with your proposal to install the activity repositories in 
https://github.com/sugar-activities/. Combining 600+ repositories in 
with the Sugar core repositories seems unmanageable. Someone would need 
to create this community on github. This needs to be decided quickly so 
the repostiroies are in place to support ASLO. We have to get past 
Walter saying this is what we are doing and James Cameron saying no 
decision has been made.

Some more detailed comments on the proposal:

*Actors and use cases*

I think there is a fourth, very important actor, the deployer. The 
deployer needs to configure a laptop installation but does not have the 
technical skills to build an image. A practical solution is to flash a 
prebuilt image (e.g. 13.2.8) and then update the activity configuration 
as needed. The best help we could provide for the developer is a network 
install capability from the institution's lan.

Since James Cameron (and possibly Jonas Smedegaard) are the only image 
builders I know of, it seems hard to justify automation. Perhaps the 
scope of the 'update url' should be shifted to providing a build system 
that creates a Sugar image for various target systems.


1. The other requirement is for an 'owner' to create the repository. 
This is analogous to the current procedure in ASLO.
2. I think the event should be 'new version released'. I am a git newbie 
(actually an old dog having trouble with new tricks) but I think git 
practice is to signal a release by creating a branch. This creation 
could generate the signal.
3. On the ASLO side, I think the information needs to be in 
activity.info. If this is done ASLO side, then the published bundle will 
not match the repository. If all of the information is in activity.info 
(or other file in the activity/ directory), the developer would have 
complete control over it.
3. I assume tar files are used in xol bundles. So far these are not 
published on ASLO. I think xol bundles should be handled independently 
of ASLO.


On 05/19/2017 05:14 AM, Samuel Cantero wrote:
> I just realized that proposal wasn't send to sugar-devel list. It was 
> removed from the thread at some point. So I just forward the link 
> again. Sorry for people subscribed to multiple lists.
> Best,
> Sam C.
> On Wed, May 17, 2017 at 4:06 PM, James Cameron <quozl at laptop.org 
> <mailto:quozl at laptop.org>> wrote:
>     Yes, please attach any files that developers should see.
>     The sugar-devel@ mailing list has a message size limit of 1024K.
>     Messages above the limit are held for approval by Sebastian and I.
>     My previous offer still stands; if people truly have no time to edit a
>     Wiki, set up public web hosting, or upload to github, send it as mail
>     to the list and I'll approve it.
>     http://lists.sugarlabs.org/archive/sugar-devel/2017-May/054193.html <http://lists.sugarlabs.org/archive/sugar-devel/2017-May/054193.html>
>     On the other hand, there have been Wiki edits in the last few
>     hours thanks to Walter;
>     http://wiki.sugarlabs.org/index.php?title=Summer_of_Code&curid=2570&diff=100299&oldid=100290
>     <http://wiki.sugarlabs.org/index.php?title=Summer_of_Code&curid=2570&diff=100299&oldid=100290>
>     Progress.  Yay.
>     --
>     James Cameron
>     http://quozl.netrek.org/
>     _______________________________________________
>     Sugar-devel mailing list
>     Sugar-devel at lists.sugarlabs.org
>     <mailto:Sugar-devel at lists.sugarlabs.org>
>     http://lists.sugarlabs.org/listinfo/sugar-devel
>     <http://lists.sugarlabs.org/listinfo/sugar-devel>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

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

More information about the Sugar-devel mailing list