<div dir="ltr">Hi, <div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">At one time there was a ASLO->Sugar Network synchronization script.</span><br style="font-size:12.8px"><br style="font-size:12.8px"><span style="font-size:12.8px">Information about the internals of Sugar Network are documented here:</span><br style="font-size:12.8px"><a class="gmail-m_6375654909049230124moz-txt-link-freetext" href="https://wiki.sugarlabs.org/go/Sugar_Network/API" target="_blank" style="font-size:12.8px">https://wiki.sugarlabs.org/go/<wbr>Sugar_Network/API</a><br style="font-size:12.8px"><br style="font-size:12.8px"><span style="font-size:12.8px">Sugar Network was meant to do what ASLO does and also provide a community support platform, and place to share creations and projects.</span><br style="font-size:12.8px"><span style="font-size:12.8px">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.</span></blockquote><div> </div><div>Original idea was to make ASLO easy to install (as easy pulling a docker image and running it) on a local network, so every organization can have a local way to distribute activities within the network. Now we are having much more active participation , which I think will clear any misunderstanding left and pave path on which ASLO development will move. </div><div><br></div><div>Thanks,</div><div><br></div><div>Jatin Dhankhar</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 17, 2017 at 8:17 AM, Sebastian Silva <span dir="ltr"><<a href="mailto:sebastian@fuentelibre.org" target="_blank">sebastian@fuentelibre.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="m_6375654909049230124moz-cite-prefix">On 16/05/17 20:53, Tony Anderson wrote:<br>
</div>
<blockquote type="cite">
<div class="m_6375654909049230124moz-cite-prefix">The Sugar Labs wiki page <a class="m_6375654909049230124moz-txt-link-freetext" href="http://wiki.sugarlabs.org/go/Sugar_Network" target="_blank">http://wiki.sugarlabs.org/go/<wbr>Sugar_Network</a>
states that Sugar Network has been renamed as School Network. <br>
</div>
</blockquote>
Not exactly. It says School Network <i>is a successor</i> of Sugar
Network.<br>
<blockquote type="cite">
<div class="m_6375654909049230124moz-cite-prefix"> <br>
The page links to <a class="m_6375654909049230124moz-txt-link-freetext" href="http://school-network.org/hub/" target="_blank">http://school-network.org/hub/</a><wbr>.
This screen offers activities, books, and groups but only the
activities appears to be populated. <br>
<br>
It offers a much simplified interface to the actiivities
consisting of widget with an enlarged icon and a download link.
<br>
</div>
</blockquote>
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.<br>
<br>
<blockquote type="cite">
<div class="m_6375654909049230124moz-cite-prefix"> <br>
<br>
<br>
On 05/17/2017 09:23 AM, Samuel Cantero wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>Samuel Cantero wrote:<br>
> we're going to try to build a new ASLO in GSoC
which must ease<br>
> activities management, for both image builders
and developers.<br>
<br>
</span>Please also consider Sugar Network, which
Sebastian knows about, and<br>
is used heavily, judging by the hit counts on the Sugar
Labs servers.<br>
</blockquote>
<div><br>
</div>
<div>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.<br>
</div>
</div>
</div>
</div>
</blockquote>
</blockquote>
<br>
<br>
At one time there was a ASLO->Sugar Network synchronization
script.<br>
<br>
Information about the internals of Sugar Network are documented
here:<br>
<a class="m_6375654909049230124moz-txt-link-freetext" href="https://wiki.sugarlabs.org/go/Sugar_Network/API" target="_blank">https://wiki.sugarlabs.org/go/<wbr>Sugar_Network/API</a><br>
<br>
Sugar Network was meant to do what ASLO does and also provide a
community support platform, and place to share creations and
projects.<br>
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.<br>
<br>
Regards,<br>
Sebastian<br>
<br>
<blockquote type="cite"> <br>
<fieldset class="m_6375654909049230124mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
Sugar-devel mailing list
<a class="m_6375654909049230124moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.<wbr>org</a>
<a class="m_6375654909049230124moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/<wbr>listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</div>
</blockquote></div><br></div>