<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 17/05/17 00:47, James Cameron wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20170517054706.GK11893@us.netrek.org">
<blockquote type="cite" style="color: #000000;">
<pre wrap="">Can someone explain the relationship between ASLO and Sugar network?
</pre>
</blockquote>
<pre wrap="">Nobody has answered your question, so I'll have a go.
A derivative relationship; data flows from ASLO to Sugar Network.
Any changes you make in ASLO that affect how the data is presented may
have impact on Sugar Network.</pre>
</blockquote>
Sorry, I thought I had answered when I said:<br>
<br>
<i>" At one time there was a ASLO->Sugar Network synchronization
script. "<br>
<br>
</i>That is precisely the extent of the current relationship between
ASLO and Sugar Network, nothing more. <br>
There is no communication or dependency between them.<br>
<br>
> Developing a new ASLO has been tried before, by Sam Parkinson,
and it<br>
> did not get enough traction, and was shut down; we've only just<br>
> finished removed the changes from Sugar. It was also a git
based<br>
> backend. After that experience, I really don't think we need
another<br>
> ASLO.<br>
<br>
There is no reason we should not try again. <br>
<br>
> Activity release is not a complicated process; we lack
maintainers,<br>
> not tools.<br>
<br>
I disagree. Tooling is very important. We should not abandon the
vision of learners producing activities and sharing them. That is
what Sugar Labs is about, after all.<br>
<br>
I'd choose the datastore/framework with care, to try to accommodate
nano servers as well as large servers, and also that it is well
supported. <br>
<br>
But, keep it simple and maintainable.<br>
<br>
Sebastian<br>
<br>
<br>
<br>
<br>
</body>
</html>