<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">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.<br>
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.<br>
<br>
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. <br>
<br>
Tony<br>
<br>
<br>
On 05/17/2017 10:47 AM, Sebastian Silva wrote:<br>
</div>
<blockquote
cite="mid:65159007-d344-9ff3-1005-e6aacfa59697@fuentelibre.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 16/05/17 20:53, Tony Anderson
wrote:<br>
</div>
<blockquote type="cite" cite="mid:591BAD34.3080909@usa.net">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
<div class="moz-cite-prefix">The Sugar Labs wiki page <a
class="moz-txt-link-freetext"
href="http://wiki.sugarlabs.org/go/Sugar_Network"
moz-do-not-send="true"><a class="moz-txt-link-freetext" href="http://wiki.sugarlabs.org/go/Sugar_Network">http://wiki.sugarlabs.org/go/Sugar_Network</a></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" cite="mid:591BAD34.3080909@usa.net">
<div class="moz-cite-prefix"> <br>
The page links to <a class="moz-txt-link-freetext"
href="http://school-network.org/hub/" moz-do-not-send="true">http://school-network.org/hub/</a>.
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" cite="mid:591BAD34.3080909@usa.net">
<div class="moz-cite-prefix"> <br>
<br>
<br>
On 05/17/2017 09:23 AM, Samuel Cantero wrote:<br>
</div>
<blockquote
cite="mid:CAGA8R4m2tf58sLSb_m23yH4MLTNScYErP_EB8RPgqhHHo3+4Vg@mail.gmail.com"
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
class="">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 moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://wiki.sugarlabs.org/go/Sugar_Network/API">https://wiki.sugarlabs.org/go/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" cite="mid:591BAD34.3080909@usa.net"> <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>