<div dir="auto">One of the pre-summer tasks is to answer that question. <div dir="auto"> </div></div><div class="gmail_extra"> <div class="gmail_quote">On May 19, 2017 5:51 PM, "James Cameron" <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Samuel & Jatin, Rather than make a new Django app to replace a PHP app, please consider the previous New ASLO written by Sam Parkinson with help from many of us here. <a href="https://github.com/samdroid-apps/aslo" rel="noreferrer" target="_blank">https://github.com/samdroid-apps/aslo</a> This work started around 16th April 2014, and the last commit was on 18th July 2015. It is written in Python, uses Flask, Docker, git, and has a workflow that is very close to what Samuel has defined. Instead of a separate GitHub organisation, Sam designed a registry repository; <a href="https://github.com/samdroid-apps/sugar-activities" rel="noreferrer" target="_blank">https://github.com/samdroid-apps/sugar-activities</a> This uses JSON metadata derived in part from the .info files. An aslo-bot was responsible for detecting releases in activity repositories and adjusting the registry. The New ASLO is already integrated with the Social Help discourse forum. Chris has reminded us, the New ASLO already has translations; <a href="https://translate.sugarlabs.org/projects/NewAslo/" rel="noreferrer" target="_blank">https://translate.sugarlabs.org/projects/NewAslo/</a> So please explain why Sam's work cannot be used? -- James Cameron <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div></div>