<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">http://pe.sugarlabs.org/ir/Manual%20de%20Traducci%C3%B3n%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"><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">sugar-devel@lists.sugarlabs.<wbr>org</a> for developers.<br> <span class=""><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.<wbr>sugarlabs.org/projects/<wbr>NewAslo/</a><br> <span class="">><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 class=""><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 class="">> 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 class=""><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="HOEnZb"><div class="h5"><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>-- <br><div class="gmail_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> </div></div>