<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">Hi, Sebastian. For once we agree completely. ;) The intent of this project is to separate development and maintenance from publishing and distribution. ASLO will be the library of published activities available for installation. Development and maintenance would be done using github proecedures. So a reviewer can bundle new versions of activities and add them to ASLO for distribution. In essence, ASLO is an example of a fusion application where the user's request returns a page built from a server-side store. This is the basic domain of Django. Tony On 05/17/2017 02:15 PM, Sebastian Silva wrote: </div> <blockquote cite="mid:d36509e6-ce34-8547-1143-96628666908e@fuentelibre.org" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <div class="moz-cite-prefix">On 17/05/17 00:47, James Cameron wrote: </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: " At one time there was a ASLO->Sugar Network synchronization script. " That is precisely the extent of the current relationship between ASLO and Sugar Network, nothing more. There is no communication or dependency between them. > Developing a new ASLO has been tried before, by Sam Parkinson, and it > did not get enough traction, and was shut down; we've only just > finished removed the changes from Sugar. It was also a git based > backend. After that experience, I really don't think we need another > ASLO. There is no reason we should not try again. > Activity release is not a complicated process; we lack maintainers, > not tools. 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. 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. But, keep it simple and maintainable. Sebastian <fieldset class="mimeAttachmentHeader"></fieldset> <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> </body> </html>