<div dir="ltr">Thanks all for the comments. Here are my replies:<div><br></div><div><font color="#741b47">On Thu, May 18, 2017 at 9:19 PM, Tony Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.<wbr>net</a>></span> wrote:</font></div><div><font color="#741b47">>Hi Sam,</font></div><div><font color="#741b47">></font></div><div><font color="#741b47">>Thanks for the proposal. Naturally this raises the question of the relationship >between your ASLOv3 and the GSOC project. Do you see two parallel >implementations or a merger of the two projects?</font><div><br></div><div>I don't understand your question. It's a proposal for the new ASLO implementation. One of the goals defined in Jatin's project. or is there another direction defined for this I am not aware of?</div></div><div><br></div><div><font color="#741b47">On Fri, May 19, 2017 at 3:04 AM, James Cameron <span dir="ltr"><<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>></span> wrote:</font></div><div><font color="#741b47">>No. I disagree with the conclusion.</font></div><div><br></div><div>I'm not saying I'm right. It's my point of view and I'm glad you have shared yours. Yes, lack of maintainers is a big issue and I don't expect the proposed design will fix all issues we have.</div><div><br></div><div><font color="#741b47">> The argument that ASLO is out of date because of there being two</font></div><font color="#741b47">> places to update information ... is specious. Besides, "two" is<br>> wrong; there is a third place critical for downstream packaging;<br>> <a href="http://download.sugarlabs.org/" rel="noreferrer" target="_blank">download.sugarlabs.org</a>.</font><div><br></div><div><a href="http://download.sugarlabs.org">download.sugarlabs.org</a> simply list the activities (xo files) stored at files/ folder registered in ASLO. It's a must the sync between ASLO and download.<br><div><br></div><div><font color="#741b47">>My prediction is that this new effort is just going to make things</font></div><font color="#741b47">>worse. Few of you speaking in the debate are an activity maintainer<br>>or developer. You risk making a tool that nobody will use.</font><div><br></div><div>I do not plan to rebuild "the same" ASLO just with a new language/framework. I'm not interested on that. I have had hard time finding someone to support or upgrade cakePHP (or other components) in current ASLO. I didn't see much people helping me last time when it got broken in server/OS update. So we also risk having a tool (current ASLO) that nobody will maintain.</div><div><br></div><div>We need to fix this issue. We have two options: build a new version but according to our reality or try to upgrade all components in current ASLO which does not seem too appealing to developers. It's hard to get contributors for this codebase.</div><div><br></div><div><font color="#741b47">>It is my job to review activities before they are built into an image;<br>>checking for malicious code, correct licensing, and correct function.</font></div><div><br></div><div>That's my point about removing the moderation queue. The image builders will ALWAYS check the activities before they are built into an image.<br><br><font color="#741b47">>Nobody has asked me or added me to moderators queue. Why not? ;-)<br></font></div><div><br></div><div>I didn't know you were not a moderator. Can someone with admin rights add to James?</div><div><br></div><div><font color="#741b47">> So just to clarify, you are removing from the activity maintainers the</font></div><font color="#741b47">> right and duty to run "python setup.py dist_xo", and "python setup.py<br>> dist_source", and you are _trusting_ the activity maintainers not to<br>> place anything in setup.py to subvert or take control of your server?</font><div><br></div><div>I was thinking to run this step inside a non privileged container but ideas are welcome.</div><div><br></div><div><font color="#741b47">> There will be activities that cannot be processed in this way; such as</font></div><font color="#741b47">> the Wikipedia activity.</font><div><br></div><div>I'm aware that might be corner cases. That is the reason why it's a draft.<br><div><br></div><div><font color="#741b47">> There will be activities from maintainers who won't engage in this new<br>> process; how will those activities be welcomed?</font></div><div><br></div><div>They have now the chance to speak up.</div><div><br></div><div><font color="#741b47">> I've no issues with the remainder of the proposal. Good design.</font></div><div><br></div><div>Thanks. But I don't understand how we should proceed. It looks like we all are in different tracks.</div><div><br></div><div><font color="#741b47">> I don't think the user base is large enough for an image building web</font></div><font color="#741b47">> service.</font></div><div><br></div><div>Agree and image building need a lot of testing.</div><div><br></div><div><font color="#741b47">On Fri, May 19, 2017 at 5:51 AM, Jatin Dhankhar <span dir="ltr"><<a href="mailto:dhankhar.jatin@gmail.com" target="_blank">dhankhar.jatin@gmail.com</a>></span> wrote:</font></div><div><div><font color="#741b47">> My main query is, how we will accomplish moderation and publishing</font></div><div><font color="#741b47">> to ASLO using Github as a tool ? I might be wrong about the whole</font></div><div><font color="#741b47">> moderation thing but a healthy discussion will hopefully lead us in</font></div><div><font color="#741b47">> the right direction.</font></div><div><br></div><div>I think we don't need moderation nor approval. We want to simplify. Please, you can test current workflow in ASLO to understand why I say simplify.</div><div><br></div><div><font color="#741b47">On Fri, May 19, 2017 at 6:13 AM, Tony Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span> wrote:</font></div><div><font color="#741b47">>So I see this three-month project as providing a new implementation of the >distribution function of ASLO, while support for activity developers and >maintainers moves to github. </font></div><div><br></div><div>what you mean with a new implementation of the distribution function of ASLO?</div><div><br></div><div><font color="#741b47">On Fri, May 19, 2017 at 6:31 AM, James Cameron <span dir="ltr"><<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>></span> wrote:<br></font></div><div><font color="#741b47">> I agree. Django apps are easily internationalised.</font></div><div>+1</div><div><br></div><div><font color="#741b47">> We already have patch review; much better moderation or approval than</font></div><font color="#741b47">> we had before.</font><br><div><div>+1</div><div><br></div><div><font color="#741b47">> Let's drop the moderation and approval requirement. Leave it to the</font></div><font color="#741b47">> image builders if they want to go further. Speaking as an image<br>> builder.</font><div>+1</div></div></div></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 19, 2017 at 10:42 AM, Laura Vargas <span dir="ltr"><<a href="mailto:laura@somosazucar.org" target="_blank">laura@somosazucar.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>Thank you Samuel and Walter for share,<br><br></div>I don't understand all the technicalities yet. I try to follow and learn :D<br><br>I agree with Chris Leonard, we should <b>prioritize facilitation
of the localization and internationalization (translations) process and
tools</b>.<br><br>There are few workflows that involve so much <b>international collective exchange</b>
and efforts and this is therefore a cultural treasure and a vital component of our relationships in the
Sugar Labs Community.<br><br>In Perú for example, we support the official translation manual to native
languages of Sugar published in a collaborative relationship with the community and the Deployment Administrators. <br><br><a href="http://pe.sugarlabs.org/ir/Manual%20de%20Traducci%C3%B3n%20de%20Sugar" target="_blank">http://pe.sugarlabs.org/ir/<wbr>Manual%20de%20Traducci%C3%B3n%<wbr>20de%20Sugar</a><br><br></div><div>We'll continue to do our best effort to it updated if there are modifications to the upstream process.<br></div><br></div></div></div>Tons of good energy for the team!<br><br></div>Regards,<br><br></div><br><div><div><div><div><div><div><div> Laura V<br></div></div></div></div></div></div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">2017-05-19 5:31 GMT-05:00 James Cameron <span dir="ltr"><<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, May 19, 2017 at 03:21:03PM +0530, Jatin Dhankhar wrote:<br>
> Hello Chris,<br>
<br>
Please continue to CC <a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.or<wbr>g</a> for developers.<br>
<span><br>
> Welcome to the Sugar Labs community, When reworking ASLO (a very<br>
> valuable project), please do keep internationalization (i18n) and<br>
> localization (L10n) in mind. You may or may not know that we do host<br>
> PO files for L10n of NewASLO on our Pootle translation server:<br>
</span>> [1]<a href="https://translate.sugarlabs.org/projects/NewAslo/" rel="noreferrer" target="_blank">https://translate.sugarlab<wbr>s.org/projects/NewAslo/</a><br>
<span>><br>
> Yes, Tony discussed the same points regarding i18n with me earlier on email.<br>
><br>
> I think you are familiar with Pootle. The trick with Django is that the<br>
> display of strings is indirect.<br>
><br>
> Pootle is built upon Django, so it should be readily available and easy to<br>
> plug.<br>
<br>
</span>I agree. Django apps are easily internationalised.<br>
<span><br>
> Sam Cantaro mentioned using webhooks to notify ASLO when a new activity<br>
> version has been released. Perhaps such a hook could be used to notify you<br>
> of the need to review localization for the activity and another hook to<br>
> notify ASLO to update the bundle to integrate the localization.<br>
><br>
> I think this is the right approach. <br>
><br>
</span>> From the conversations so far and looking at the [2]ASLO 3 Proposal, we are<br>
<span>> using webhooks to notify ASLO of any changes, whether it is adding a new<br>
> activity, or updating an existing one. I have one question, how will an<br>
> activity get approved prior to it's release on ASLO ?<br>
> Suppose a developer wants to create a new activity and upload it to<br>
> ASLO. Of course, prior to release, the activity needs to be<br>
> verified/moderated. Will be there an intermediate step? Since<br>
> developer needs to be member of sugar-activites organization to<br>
> publish an activity there or will there be another repository<br>
> containing names of verified repo, which build server will check on<br>
> each webhook ? <br>
> What I suggest is to use the Pull request reviews to moderate an<br>
> activity and when an activity is signed off as okay but X number of<br>
> senior members then only it should be considered for ASLO.<br>
<br>
</span>That would work, but it sounds difficult to communicate and implement;<br>
there are not enough senior members. ;-)<br>
<br>
We also can't trust GitHub to keep that UX stable.<br>
<span><br>
> My main query is, how we will accomplish moderation and publishing<br>
> to ASLO using Github as a tool ? I might be wrong about the whole<br>
> moderation thing but a healthy discussion will hopefully lead us in<br>
> the right direction.<br>
<br>
</span>What we have now is a moderation queue in a PHP application; perhaps<br>
we don't need a moderation or approval at all. That would simplify<br>
the activity release process by one step.<br>
<br>
We already have patch review; much better moderation or approval than<br>
we had before.<br>
<br>
Let's drop the moderation and approval requirement. Leave it to the<br>
image builders if they want to go further. Speaking as an image<br>
builder.<br>
<div class="m_-5220855858669314085HOEnZb"><div class="m_-5220855858669314085h5"><br>
--<br>
James Cameron<br>
<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div>-- <br><span class=""><div class="m_-5220855858669314085gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Laura V.<br><font color="#ff00ff"><b>
I&D SomosAZUCAR.Org</b></font></div><div><div style="color:rgb(136,136,136);font-size:12.8px"><font size="2"><span style="color:rgb(102,102,102);font-family:"helvetica neue",helvetica,arial,sans-serif"><br>“Solo la tecnología libre nos hará libres.” </span></font></div><div style="color:rgb(136,136,136);font-size:12.8px"><font size="2"><span style="color:rgb(102,102,102);font-family:"helvetica neue",helvetica,arial,sans-serif">~ Laura Victoria</span></font><br><br></div><div style="color:rgb(136,136,136);font-size:12.8px">Happy Learning!<br>#LearningByDoing</div><div style="color:rgb(136,136,136);font-size:12.8px">#Projects4good</div><div style="color:rgb(136,136,136);font-size:12.8px">#IDesignATSugarLabs<br></div><div style="color:rgb(136,136,136);font-size:12.8px">#WeCanDoBetter</div></div></div></div></div></div></div></div></div></div>
</span></div></div>
</blockquote></div><br></div>