[Sugar-devel] New-ASLO and Sugar Network

Tony Anderson tony_anderson at usa.net
Tue May 16 23:19:34 EDT 2017

The choice of architecture is not odd - it is quite reasonable. The 
question is what information needs to be available to the user browsing 
the collection.
The question is what information from ASLO needs to be available to the 
user browsing activities. In addition to the activity name and icon 
shown by School Network, ASLO provides information about the developer, 
a summary, a description, links to the git repository, and so on. A 
question in the GSOC project will be what of this information is needed.

The main push relevant to ASLO at the moment is make github/sugarlabs 
the repository for maintenance and support of the activities. So it 
appear we will need two 'centers' for ASLO. Github/sugarlabs for 
development and support. ASLO for users to select and download 
activities. So it would appear that what is needed is to use setup.py to 
make bundles of new versions of an activity and that these bundles be 
'published' to ASLO.


On 05/17/2017 10:47 AM, Sebastian Silva wrote:
> On 16/05/17 20:53, Tony Anderson wrote:
>> The Sugar Labs wiki page http://wiki.sugarlabs.org/go/Sugar_Network 
>> states that Sugar Network has been renamed as School Network.
> Not exactly. It says School Network /is a successor/ of Sugar Network.
>> The page links to http://school-network.org/hub/. This screen offers 
>> activities, books, and groups but only the activities appears to be 
>> populated.
>> It offers a much simplified interface to the actiivities consisting 
>> of widget with an enlarged icon and a download link.
> It is important to note that Sugar Network was intended to eventually 
> replace ASLO. The odd choice for an architecture is because it was 
> intended to function de-centralized.
>> On 05/17/2017 09:23 AM, Samuel Cantero wrote:
>>>     Samuel Cantero wrote:
>>>     > we're going to try to build a new ASLO in GSoC which must ease
>>>     > activities management, for both image builders and developers.
>>>     Please also consider Sugar Network, which Sebastian knows about, and
>>>     is used heavily, judging by the hit counts on the Sugar Labs
>>>     servers.
>>> Can someone explain the relationship between ASLO and Sugar network? 
>>> Pitifully we can't work in ASLO and Sugar network at the same time, 
>>> but we can take into account what is needed for interaction with 
>>> Sugar network. At least in design in the first stage.
> At one time there was a ASLO->Sugar Network synchronization script.
> Information about the internals of Sugar Network are documented here:
> https://wiki.sugarlabs.org/go/Sugar_Network/API
> Sugar Network was meant to do what ASLO does and also provide a 
> community support platform, and place to share creations and projects.
> It would be interesting at least to draw inspiration from. Laura, 
> Aleksey and me were original designers and implementers, always 
> looking for ways to make the vision a reality, and hoping to collaborate.
> Regards,
> Sebastian
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> 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/20170517/3819bc44/attachment.html>

More information about the Sugar-devel mailing list