<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"><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote">
<div class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Second, I see you are investing a ton of work on this. </div><div>
<div>I don't know if there are some wiki page with the plan about </div>
</div><div>what features would need a hypothetical ASLO2.. </div><div>if is not, can you prepare one with the points we already discussed?</div></div></blockquote><div><br></div></div><div>Here you go: <a href="http://wiki.sugarlabs.org/go/ASLO2" target="_blank">http://wiki.sugarlabs.org/go/ASLO2</a><br>
<br></div><div>Have I missed any?<br></div><div class=""><div> </div></div></div></div></div></div></blockquote><div><br></div><div>Would be good separate the features from the implementation.</div><div>"Search by activity name or description" is a feature, "websockets" or "json database"</div>
<div>is a implementation detail. Is important have clear _what_ we need,</div><div>and later define _how_ achieve that.</div><div><br></div><div>Then we need start with the features the actual ASLO have:</div><div><br></div>
<div>* Stores every version of a activity (.xo, release notes, screenshots).</div><div>* Can search by text or activity description (English only)</div><div>* UI localized</div><div>* Activities have categories</div><div>
* Users can add comments and stars</div><div>* Offer the last activity version available based on the user Sugar version (if use Browse activity) </div><div>etc</div><div><br></div><div>you can add the new features we need:</div>
<div><br></div><div>* support i18n (search in languages different than English)</div><div>* make easier publish a new version</div><div>* automatic publish of development versions with github hooks</div><div>* bugs reports? (will create bus in <a href="http://bugs.sugarlabs.org">bugs.sugarlabs.org</a>?)</div>
<div>* improve communication with the developers?</div><div><br></div><div>I don't know if I am missing something, have all this clear will be good</div><div>in a big project like this.</div></div><div><br></div>-- <br>
<div dir="ltr">Gonzalo Odiard<br><br><div>SugarLabs - Software for children learning <br></div></div>
</div></div>