Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[James Cameron]

On Sat, May 20, 2017 at 08:36:35AM +1000, Sam Parkinson wrote:
> Hi All,
> 
> Just thought I'd tune in with some thoughts about the ASLO.

Please continue to CC sugar-de...@lists.sugarlabs.org.

> Yeah.  One thing you need to be careful of is releases.  Not every
> commit should be packaged up and posted on the ASLO.
> 
> There are a few ways that you could do this.  You could search for the
> commits which the version number is changed.  Or you could use github
> releases.  Or you could have a "master" and "published" branch.  So
> many options.

Or git tags, which are perfect for this, as they can be moved, and can
be branch independent, leaving branches to be used for what we want.

Thanks for chiming in.

-- 
James Cameron
http://quozl.netrek.org/
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Sam Parkinson]

Hi All,

Just thought I'd tune in with some thoughts about the ASLO.

On Fri, 2017-05-19 at 15:21 +0530, Jatin Dhankhar wrote:
> Hello Chris,
> 
> > Welcome to the Sugar Labs community, When reworking ASLO (a very
> > valuable project), please do keep internationalization (i18n) and
> > localization (L10n) in mind.  You may or may not know that we do
> > host
> > PO files for L10n of NewASLO on our Pootle translation server:
> > https://translate.sugarlabs.org/projects/NewAslo/
> 
> Yes, Tony discussed the same points regarding i18n with me earlier on
> email.
> 
> > I think you are familiar with Pootle. The trick with Django is that
> > the display of strings is indirect.
> 
> Pootle is built upon Django, so it should be readily available and
> easy to plug.   
> 
> > Sam Cantaro mentioned using webhooks to notify ASLO when a new
> > activity version has been released. Perhaps such a hook could be
> > used to notify you of the need to review localization for the
> > activity and another hook to notify ASLO to update the bundle to
> > integrate the localization.
> 
> I think this is the right approach. 

Yeah.  One thing you need to be careful of is releases.  Not every
commit should be packaged up and posted on the ASLO.

There are a few ways that you could do this.  You could search for the
commits which the version number is changed.  Or you could use github
releases.  Or you could have a "master" and "published" branch.  So
many options.

Also I don't know if this has been discusses, but there is a build step
that you need to run.  You need to generate ".xo" files from the git
repos.  You might be intersted in the ASLO2 bot code, which handles
metadata-extraction (getting summary, title, screenshots, etc) and
bundle building:  https://github.com/samdroid-apps/aslo/blob/master/bot
/main.py  <-- that even handles extraction of translated names from a
po file

> 
> From the conversations so far and looking at the ASLO 3 Proposal, we
> are using webhooks to notify ASLO of any changes, whether it is
> adding a new activity, or updating an existing one. I have one
> question, how will an activity get approved prior to it's release on
> ASLO ?  Suppose a developer wants to create a new activity and upload
> it to ASLO. Of course, prior to release, the activity needs to be
> verified/moderated. Will be there an intermediate step? Since
> developer needs to be member of sugar-activites organization to
> publish an activity there or will there be another repository
> containing names of verified repo, which build server will check on
> each webhook ? 
> What I suggest is to use the Pull request reviews to moderate an
> activity and when an activity is signed off as okay but X number of
>  senior members then only it should be considered for ASLO.
> 
> My main query is, how we will accomplish moderation and publishing to
> ASLO using Github as a tool ? I might be wrong about the whole
> moderation thing but a healthy discussion will hopefully lead us in
> the right direction.

I think using GitHub as a base for the ASLO is a really simple idea. 
Right now we have the issue that we don't know where a lot of the code
for activities actually is.  If all activities on ALSO's offical
repository is on github.com/sugar-activities, that will really simplify
things.

From the perspective of adding a new activities; I think we don't need
to overthink it.  People can just send an email to the mailing list,
requesting to have a repository added to github.com/sugar-activities. 
Then that can be done manually if approved.


As for moderating updates, I'm not sure that it is the right idea to
moderate updates.  We already have the issue that the moderation queue
on ASLO grows very long.  So maybe we just trust the people who are
granted push access to sugar-activities repositories?  If we don't,
just make the sugar-activities repo be a fork of the original, which is
updated occasionally by a trusted person.

If we keep it all on github, github basically becomes our database! 
Writing less code & hosting less services === better IMHO.

---
Thanks,
Sam

https://learntemail.sam.today/

Latest blog post: Arithmetic with JavaScript Arrays - 
https://learntemail.sam.today/blog/arithmetic-with-javascript-arrays/
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Samuel Cantero]

Thanks all for the comments. Here are my replies:

On Thu, May 18, 2017 at 9:19 PM, Tony Anderson 
 wrote:
>Hi Sam,
>
>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?

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?

On Fri, May 19, 2017 at 3:04 AM, James Cameron  wrote:
>No.  I disagree with the conclusion.

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.

> The argument that ASLO is out of date because of there being two
> places to update information ... is specious.  Besides, "two" is
> wrong; there is a third place critical for downstream packaging;
> download.sugarlabs.org.

download.sugarlabs.org simply list the activities (xo files) stored at
files/ folder registered in ASLO. It's a must the sync between ASLO and
download.

>My prediction is that this new effort is just going to make things
>worse.  Few of you speaking in the debate are an activity maintainer
>or developer.  You risk making a tool that nobody will use.

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.

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.

>It is my job to review activities before they are built into an image;
>checking for malicious code, correct licensing, and correct function.

That's my point about removing the moderation queue. The image builders
will ALWAYS check the activities before they are built into an image.

>Nobody has asked me or added me to moderators queue.  Why not?  ;-)

I didn't know you were not a moderator. Can someone with admin rights add
to James?

> So just to clarify, you are removing from the activity maintainers the
> right and duty to run "python setup.py dist_xo", and "python setup.py
> dist_source", and you are _trusting_ the activity maintainers not to
> place anything in setup.py to subvert or take control of your server?

I was thinking to run this step inside a non privileged container but ideas
are welcome.

> There will be activities that cannot be processed in this way; such as
> the Wikipedia activity.

I'm aware that might be corner cases. That is the reason why it's a draft.

> There will be activities from maintainers who won't engage in this new
> process; how will those activities be welcomed?

They have now the chance to speak up.

> I've no issues with the remainder of the proposal.  Good design.

Thanks. But I don't understand how we should proceed. It looks like we all
are in different tracks.

> I don't think the user base is large enough for an image building web
> service.

Agree and image building need a lot of testing.

On Fri, May 19, 2017 at 5:51 AM, Jatin Dhankhar 
 wrote:
> My main query is, how we will accomplish moderation and publishing
> to ASLO using Github as a tool ? I might be wrong about the whole
> moderation thing but a healthy discussion will hopefully lead us in
> the right direction.

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.

On Fri, May 19, 2017 at 6:13 AM, Tony Anderson 
 wrote:
>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.

what you mean with a new implementation of the distribution function of
ASLO?

On Fri, May 19, 2017 at 6:31 AM, James Cameron  wrote:
> I agree.  Django apps are easily internationalised.
+1

> We already have patch review; much better moderation or approval than
> we had before.
+1

> Let's drop the moderation and approval requirement.  Leave it to the
> image builders if they want to go further.  Speaking as an image
> builder.
+1


On Fri, May 19, 2017 at 10:42 AM, Laura Vargas 
wrote:

> Thank you Samuel and Walter for share,
>
> I don't understand all the technicalities yet. I try to follow and learn
> :D
>
> I agree with Chris Leonard, we should *prioritize facilitation of the
> localization and internationalization (translations) process and tools*.
>
> There are few workflows that involve so much *international collective
> exchange* and efforts 

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Laura Vargas]

Thank you Samuel and Walter for share,

I don't understand all the technicalities yet. I try to follow and learn  :D

I agree with Chris Leonard, we should *prioritize facilitation of the
localization and internationalization (translations) process and tools*.

There are few workflows that involve so much *international collective
exchange* and efforts and this is therefore a cultural treasure and a vital
component of our relationships in the Sugar Labs Community.

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.

http://pe.sugarlabs.org/ir/Manual%20de%20Traducci%C3%B3n%20de%20Sugar

We'll continue to do our best effort to it updated if there are
modifications to the upstream process.

Tons of good energy for the team!

Regards,


 Laura V

2017-05-19 5:31 GMT-05:00 James Cameron :

> On Fri, May 19, 2017 at 03:21:03PM +0530, Jatin Dhankhar wrote:
> > Hello Chris,
>
> Please continue to CC sugar-de...@lists.sugarlabs.org for developers.
>
> > Welcome to the Sugar Labs community, When reworking ASLO (a very
> > valuable project), please do keep internationalization (i18n) and
> > localization (L10n) in mind.  You may or may not know that we do host
> > PO files for L10n of NewASLO on our Pootle translation server:
> > [1]https://translate.sugarlabs.org/projects/NewAslo/
> >
> > Yes, Tony discussed the same points regarding i18n with me earlier on
> email.
> >
> > I think you are familiar with Pootle. The trick with Django is that
> the
> > display of strings is indirect.
> >
> > Pootle is built upon Django, so it should be readily available and easy
> to
> > plug.
>
> I agree.  Django apps are easily internationalised.
>
> > Sam Cantaro mentioned using webhooks to notify ASLO when a new
> activity
> > version has been released. Perhaps such a hook could be used to
> notify you
> > of the need to review localization for the activity and another hook
> to
> > notify ASLO to update the bundle to integrate the localization.
> >
> > I think this is the right approach.
> >
> > From the conversations so far and looking at the [2]ASLO 3 Proposal, we
> are
> > using webhooks to notify ASLO of any changes, whether it is adding a new
> > activity, or updating an existing one. I have one question, how will an
> > activity get approved prior to it's release on ASLO ?
> > Suppose a developer wants to create a new activity and upload it to
> > ASLO. Of course, prior to release, the activity needs to be
> > verified/moderated. Will be there an intermediate step? Since
> > developer needs to be member of sugar-activites organization to
> > publish an activity there or will there be another repository
> > containing names of verified repo, which build server will check on
> > each webhook ?
> > What I suggest is to use the Pull request reviews to moderate an
> > activity and when an activity is signed off as okay but X number of
> >  senior members then only it should be considered for ASLO.
>
> That would work, but it sounds difficult to communicate and implement;
> there are not enough senior members.  ;-)
>
> We also can't trust GitHub to keep that UX stable.
>
> > My main query is, how we will accomplish moderation and publishing
> > to ASLO using Github as a tool ? I might be wrong about the whole
> > moderation thing but a healthy discussion will hopefully lead us in
> > the right direction.
>
> What we have now is a moderation queue in a PHP application; perhaps
> we don't need a moderation or approval at all.  That would simplify
> the activity release process by one step.
>
> We already have patch review; much better moderation or approval than
> we had before.
>
> Let's drop the moderation and approval requirement.  Leave it to the
> image builders if they want to go further.  Speaking as an image
> builder.
>
> --
> James Cameron
> http://quozl.netrek.org/
>



-- 
Laura V.
* I&D SomosAZUCAR.Org*

“Solo la tecnología libre nos hará libres.”
~ Laura Victoria

Happy Learning!
#LearningByDoing
#Projects4good
#IDesignATSugarLabs
#WeCanDoBetter
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[James Cameron]

On Fri, May 19, 2017 at 03:21:03PM +0530, Jatin Dhankhar wrote:
> Hello Chris,

Please continue to CC sugar-de...@lists.sugarlabs.org for developers.

> Welcome to the Sugar Labs community, When reworking ASLO (a very
> valuable project), please do keep internationalization (i18n) and
> localization (L10n) in mind.  You may or may not know that we do host
> PO files for L10n of NewASLO on our Pootle translation server:
> [1]https://translate.sugarlabs.org/projects/NewAslo/
> 
> Yes, Tony discussed the same points regarding i18n with me earlier on email.
> 
> I think you are familiar with Pootle. The trick with Django is that the
> display of strings is indirect.
> 
> Pootle is built upon Django, so it should be readily available and easy to
> plug.

I agree.  Django apps are easily internationalised.

> Sam Cantaro mentioned using webhooks to notify ASLO when a new activity
> version has been released. Perhaps such a hook could be used to notify you
> of the need to review localization for the activity and another hook to
> notify ASLO to update the bundle to integrate the localization.
> 
> I think this is the right approach. 
> 
> From the conversations so far and looking at the [2]ASLO 3 Proposal, we are
> using webhooks to notify ASLO of any changes, whether it is adding a new
> activity, or updating an existing one. I have one question, how will an
> activity get approved prior to it's release on ASLO ?
> Suppose a developer wants to create a new activity and upload it to
> ASLO. Of course, prior to release, the activity needs to be
> verified/moderated. Will be there an intermediate step? Since
> developer needs to be member of sugar-activites organization to
> publish an activity there or will there be another repository
> containing names of verified repo, which build server will check on
> each webhook ? 
> What I suggest is to use the Pull request reviews to moderate an
> activity and when an activity is signed off as okay but X number of
>  senior members then only it should be considered for ASLO.

That would work, but it sounds difficult to communicate and implement;
there are not enough senior members.  ;-)

We also can't trust GitHub to keep that UX stable.

> My main query is, how we will accomplish moderation and publishing
> to ASLO using Github as a tool ? I might be wrong about the whole
> moderation thing but a healthy discussion will hopefully lead us in
> the right direction.

What we have now is a moderation queue in a PHP application; perhaps
we don't need a moderation or approval at all.  That would simplify
the activity release process by one step.

We already have patch review; much better moderation or approval than
we had before.

Let's drop the moderation and approval requirement.  Leave it to the
image builders if they want to go further.  Speaking as an image
builder.

-- 
James Cameron
http://quozl.netrek.org/
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Jatin Dhankhar]

Hello Chris,

Welcome to the Sugar Labs community, When reworking ASLO (a very
> valuable project), please do keep internationalization (i18n) and
> localization (L10n) in mind.  You may or may not know that we do host
> PO files for L10n of NewASLO on our Pootle translation server:
> https://translate.sugarlabs.org/projects/NewAslo/


Yes, Tony discussed the same points regarding i18n with me earlier on email.

I think you are familiar with Pootle. The trick with Django is that the
> display of strings is indirect.

Pootle is built upon Django, so it should be readily available and easy to
plug.

Sam Cantaro mentioned using webhooks to notify ASLO when a new activity
> version has been released. Perhaps such a hook could be used to notify you
> of the need to review localization for the activity and another hook to
> notify ASLO to update the bundle to integrate the localization.

I think this is the right approach.

>From the conversations so far and looking at the ASLO 3 Proposal
,
we are using webhooks to notify ASLO of any changes, whether it is adding a
new activity, or updating an existing one. I have one question, how will an
activity get approved prior to it's release on ASLO ?  Suppose a developer
wants to create a new activity and upload it to ASLO. Of course, prior to
release, the activity needs to be verified/moderated. Will be there an
intermediate step? Since developer needs to be member of sugar-activites
organization to publish an activity there or will there be another
repository containing names of verified repo, which build server will check
on each webhook ?
What I suggest is to use the Pull request reviews
 to moderate an activity
and when an activity is signed off as okay but X number of  senior members
then only it should be considered for ASLO.

My main query is, how we will accomplish moderation and publishing to ASLO
using Github as a tool ? I might be wrong about the whole moderation thing
but a healthy discussion will hopefully lead us in the right direction.

Thanks,
Jatin Dhankhar

On Fri, May 19, 2017 at 6:54 AM, Chris Leonard 
wrote:

> Dear Jatin,
>
> Welcome to the Sugar Labs community, When reworking ASLO (a very
> valuable project), please do keep internationalization (i18n) and
> localization (L10n) in mind.  You may or may not know that we do host
> PO files for L10n of NewASLO on our Pootle translation server:
>
> https://translate.sugarlabs.org/projects/NewAslo/
>
> We currently have very complete coverage in the following languages:
> Swedish, Spanish, Russian, Guaraní (Paraguay), English (United
> Kingdom), English, Dutch, Danish, Catalan, Albanian, Igbo.  Obviously
> the fewer un-necessary UI string changes, the better we will be in
> terms of localizing the new product of your work,  The Translation
> Team will obviously take care of any strings that must be changed to
> produce a better ASLO, but changes for the sake of changes can
> hopefully be avoided if the existing strings serve the intended
> purpose.
>
> Having the Spanish translation complete in a production instance is
> probably more important than any other language given the number of
> Spanish-speaking users we typically want to reach, but as FOSS, if
> you're going to accommodate more than one language,  you might as well
> make it easy for all of them.  When you get ready to go-live with the
> new ASLO service, we'd obviously love to have the chance (a week or
> two of string freeze) to catch up with your work and make sure what
> gets deployed reaches our key audiences in their native language(s).
>
> Laura Vargas would be a fine guide to i18n/L10n practices in Sugar
> Labs, but if you have any questions, feel free to reach out to me and
> I'll try to help, I'll probably be the one to contact about grabbing a
> new POT template from your repository and uploading it to Pootle for
> the localizers to work on, as well as generating the pull request when
> they have completed their work on the specific language's PO file.
>
> Looking forward to seeing your work blossom.
>
> cjl
>
>
>
> On Thu, May 18, 2017 at 3:37 AM, Jatin Dhankhar
>  wrote:
> > Hi,
> > Thank you Laura for attaching the proposal.
> > I will be glad if you can point me in the right direction regarding my
> GSOC
> > project, suggest flaws and how it can be improved. If anyone has any
> > questions or speculations, feel free to ping me. I am also writing weekly
> > summary of GSOC here https://jatindhankhar.in/posts/.
> > If something is missing or incorrect, let me know.
> >
> > Thanks,
> > Jatin Dhakhar
> >
> > On Thu, May 18, 2017 at 9:10 AM, Laura Vargas 
> > wrote:
> >>
> >>
> >> Hi Jatin welcome to Sugar Labs Community!
> >>
> >> Hi Aleksey,
> >>
> >> I hope to find time to be able to follow Jatin's project proposed time
> >> line. I hope you can find some time too. See pdf attached for project's

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Tony Anderson]

Hi Chris

Currently there are two text fields per activity in ASLO: Summary and 
Description.
This gets a bit more complicated since these text fields edited by the 
developer in github.


Perhaps this might work. Have a po directory in the activities/ 
directory of the bundle. When the activity page is selected Django can 
select the summary string from the appropriate po and send it to the 
html template. This method would work for both summary and description. 
With the pootle default to display the POT string, no harm can be done.


Sam Cantaro mentioned using webhooks to notify ASLO when a new activity 
version has been released. Perhaps such a hook could be used to notify 
you of the need to review localization for the activity and another hook 
to notify ASLO to update the bundle to integrate the localization.


Tony

On 05/19/2017 10:08 AM, Chris Leonard wrote:

On Thu, May 18, 2017 at 9:57 PM, Tony Anderson  wrote:

On 05/19/2017 09:24 AM, Chris Leonard wrote:
The more difficult question is how to localize the summary and description
of the individual activities. At present, it appears we don't attempt to
localize this information.

The first thought that pops into my mind is the very brief Activity
description that is in the activity.info file and is frequently, but
not always captured in the PO file for localization.  With that as
background, making changes to activity,info format to include a richer
description seems feasible as does doing a better job of tooling the
i18n so that these activity.info fields are more consistently captured
in the PO files.  Having ASLO parse the activity.info file of the
hosted packages relevant PO file seems a reasonable approach that
would mean that ASLO doesn't have to have separately maintained
knowledge of the Activities being hosted, it justs picks it up from
the upload of the package itself.  . Just a thought.

cjl
.



___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Chris Leonard]

 I mis-phrased that slightly.  ASLO would parse the PO files for the
lines drawn from the activity,info file during POT generation (i18n),
not parse the activity.info file itself (which I think ASLO already
does for versuion  number, etc.).  The idea is that the activity,info
description in Engiish would be localized in the relevant PO files at
the time of L10n of the Activity's UI strings.

cjl

On Thu, May 18, 2017 at 10:08 PM, Chris Leonard
 wrote:
> On Thu, May 18, 2017 at 9:57 PM, Tony Anderson  wrote:
>> On 05/19/2017 09:24 AM, Chris Leonard wrote:
>>>
>> The more difficult question is how to localize the summary and description
>> of the individual activities. At present, it appears we don't attempt to
>> localize this information.
>
> The first thought that pops into my mind is the very brief Activity
> description that is in the activity.info file and is frequently, but
> not always captured in the PO file for localization.  With that as
> background, making changes to activity,info format to include a richer
> description seems feasible as does doing a better job of tooling the
> i18n so that these activity.info fields are more consistently captured
> in the PO files.  Having ASLO parse the activity.info file of the
> hosted packages relevant PO file seems a reasonable approach that
> would mean that ASLO doesn't have to have separately maintained
> knowledge of the Activities being hosted, it justs picks it up from
> the upload of the package itself.  . Just a thought.
>
> cjl
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Chris Leonard]

On Thu, May 18, 2017 at 9:57 PM, Tony Anderson  wrote:
> On 05/19/2017 09:24 AM, Chris Leonard wrote:
>>
> The more difficult question is how to localize the summary and description
> of the individual activities. At present, it appears we don't attempt to
> localize this information.

The first thought that pops into my mind is the very brief Activity
description that is in the activity.info file and is frequently, but
not always captured in the PO file for localization.  With that as
background, making changes to activity,info format to include a richer
description seems feasible as does doing a better job of tooling the
i18n so that these activity.info fields are more consistently captured
in the PO files.  Having ASLO parse the activity.info file of the
hosted packages relevant PO file seems a reasonable approach that
would mean that ASLO doesn't have to have separately maintained
knowledge of the Activities being hosted, it justs picks it up from
the upload of the package itself.  . Just a thought.

cjl
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Tony Anderson]

On 05/19/2017 09:24 AM, Chris Leonard wrote:

Welcome to the Sugar Labs community, When reworking ASLO (a very
valuable project), please do keep internationalization (i18n) and
localization (L10n) in mind.  You may or may not know that we do host
PO files for L10n of NewASLO on our Pootle translation server:

https://translate.sugarlabs.org/projects/NewAslo/

Hi, Chris

Thanks for this input. It is wonderful that the project is getting these 
inputs when there is still time to incorporate them in the design. I 
looked at the po - 81 works. The trick will be to adapt Django to pootle 
since the html definition is separate from the python code; however, it 
shouldn't be difficult. I envision a front page closer in design to 
School Network which should actually minimize text on the main page.


The more difficult question is how to localize the summary and 
description of the individual activities. At present, it appears we 
don't attempt to localize this information.


Tony
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Chris Leonard]

Dear Jatin,

Welcome to the Sugar Labs community, When reworking ASLO (a very
valuable project), please do keep internationalization (i18n) and
localization (L10n) in mind.  You may or may not know that we do host
PO files for L10n of NewASLO on our Pootle translation server:

https://translate.sugarlabs.org/projects/NewAslo/

We currently have very complete coverage in the following languages:
Swedish, Spanish, Russian, Guaraní (Paraguay), English (United
Kingdom), English, Dutch, Danish, Catalan, Albanian, Igbo.  Obviously
the fewer un-necessary UI string changes, the better we will be in
terms of localizing the new product of your work,  The Translation
Team will obviously take care of any strings that must be changed to
produce a better ASLO, but changes for the sake of changes can
hopefully be avoided if the existing strings serve the intended
purpose.

Having the Spanish translation complete in a production instance is
probably more important than any other language given the number of
Spanish-speaking users we typically want to reach, but as FOSS, if
you're going to accommodate more than one language,  you might as well
make it easy for all of them.  When you get ready to go-live with the
new ASLO service, we'd obviously love to have the chance (a week or
two of string freeze) to catch up with your work and make sure what
gets deployed reaches our key audiences in their native language(s).

Laura Vargas would be a fine guide to i18n/L10n practices in Sugar
Labs, but if you have any questions, feel free to reach out to me and
I'll try to help, I'll probably be the one to contact about grabbing a
new POT template from your repository and uploading it to Pootle for
the localizers to work on, as well as generating the pull request when
they have completed their work on the specific language's PO file.

Looking forward to seeing your work blossom.

cjl



On Thu, May 18, 2017 at 3:37 AM, Jatin Dhankhar
 wrote:
> Hi,
> Thank you Laura for attaching the proposal.
> I will be glad if you can point me in the right direction regarding my GSOC
> project, suggest flaws and how it can be improved. If anyone has any
> questions or speculations, feel free to ping me. I am also writing weekly
> summary of GSOC here https://jatindhankhar.in/posts/.
> If something is missing or incorrect, let me know.
>
> Thanks,
> Jatin Dhakhar
>
> On Thu, May 18, 2017 at 9:10 AM, Laura Vargas 
> wrote:
>>
>>
>> Hi Jatin welcome to Sugar Labs Community!
>>
>> Hi Aleksey,
>>
>> I hope to find time to be able to follow Jatin's project proposed time
>> line. I hope you can find some time too. See pdf attached for project's
>> details.
>>
>> Regards and blessings to all the team,
>>
>>
>> Laura Victoria
>>
>>
>>
>>
>> -- Forwarded message --
>> From: Tony Anderson 
>> Date: 2017-05-17 18:57 GMT-05:00
>> Subject: Re: [Sugar-devel] New ASLO Project Definition
>> To: Laura Vargas 
>>
>>
>> Hi, Laura
>>
>> Done.
>>
>> Tony
>>
>>
>> On 05/18/2017 12:56 AM, Laura Vargas wrote:
>>
>> Samuel and new ASLO team,
>>
>> Can you please attach the pdf with the project description?
>>
>> In my opinion, as ASLO is such a powerful resource used today by active
>> deployments, a successful successor will provide at least the same services.
>>
>> Regards
>>
>> Laura V.
>> I&D SomosAZUCAR.Org
>>
>> “Solo la tecnología libre nos hará libres.”
>> ~ Laura Victoria
>>
>> Happy Learning!
>> #LearningByDoing
>> #Projects4good
>> #IDesignATSugarLabs
>> #WeCanDoBetter
>>
>>
>> ___
>> Sugar-devel mailing list
>> sugar-de...@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>>
>
>
> ___
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Samuel Cantero]

s/These are my notes/These are some notes/g :)

Walter Bender has helped me to shape this first proposal.

On Thu, May 18, 2017 at 4:22 PM, Samuel Cantero  wrote:

> Hi all,
>
> These are my notes in order to augment current proposal: https://goo.gl/
> VEIzCr
>
> You can add comments/suggestions to the document.
>
> Best regards,
>
> Sam C.
>
> On Thu, May 18, 2017 at 3:37 AM, Jatin Dhankhar 
> wrote:
>
>> Hi,
>> Thank you Laura for attaching the proposal.
>> I will be glad if you can point me in the right direction regarding my
>> GSOC project, suggest flaws and how it can be improved. If anyone has any
>> questions or speculations, feel free to ping me. I am also writing weekly
>> summary of GSOC here https://jatindhankhar.in/posts/.
>> If something is missing or incorrect, let me know.
>>
>> Thanks,
>> Jatin Dhakhar
>>
>> On Thu, May 18, 2017 at 9:10 AM, Laura Vargas 
>> wrote:
>>
>>>
>>> Hi Jatin welcome to Sugar Labs Community!
>>>
>>> Hi Aleksey,
>>>
>>> I hope to find time to be able to follow Jatin's project proposed time
>>> line. I hope you can find some time too. See pdf attached for project's
>>> details.
>>>
>>> Regards and blessings to all the team,
>>>
>>>
>>> Laura Victoria
>>>
>>>
>>>
>>>
>>> -- Forwarded message --
>>> From: Tony Anderson 
>>> Date: 2017-05-17 18:57 GMT-05:00
>>> Subject: Re: [Sugar-devel] New ASLO Project Definition
>>> To: Laura Vargas 
>>>
>>>
>>> Hi, Laura
>>>
>>> Done.
>>>
>>> Tony
>>>
>>>
>>> On 05/18/2017 12:56 AM, Laura Vargas wrote:
>>>
>>> Samuel and new ASLO team,
>>>
>>> Can you please attach the pdf with the project description?
>>>
>>> In my opinion, as ASLO is such a powerful resource used today by active
>>> deployments, a successful successor will provide at least the same services.
>>>
>>> Regards
>>>
>>> Laura V.
>>> * I&D SomosAZUCAR.Org*
>>>
>>> “Solo la tecnología libre nos hará libres.”
>>> ~ Laura Victoria
>>>
>>> Happy Learning!
>>> #LearningByDoing
>>> #Projects4good
>>> #IDesignATSugarLabs
>>> #WeCanDoBetter
>>>
>>>
>>> ___
>>> Sugar-devel mailing 
>>> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>>
>>>
>>>
>>
>
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Samuel Cantero]

Hi all,

These are my notes in order to augment current proposal:
https://goo.gl/VEIzCr

You can add comments/suggestions to the document.

Best regards,

Sam C.

On Thu, May 18, 2017 at 3:37 AM, Jatin Dhankhar 
wrote:

> Hi,
> Thank you Laura for attaching the proposal.
> I will be glad if you can point me in the right direction regarding my
> GSOC project, suggest flaws and how it can be improved. If anyone has any
> questions or speculations, feel free to ping me. I am also writing weekly
> summary of GSOC here https://jatindhankhar.in/posts/.
> If something is missing or incorrect, let me know.
>
> Thanks,
> Jatin Dhakhar
>
> On Thu, May 18, 2017 at 9:10 AM, Laura Vargas 
> wrote:
>
>>
>> Hi Jatin welcome to Sugar Labs Community!
>>
>> Hi Aleksey,
>>
>> I hope to find time to be able to follow Jatin's project proposed time
>> line. I hope you can find some time too. See pdf attached for project's
>> details.
>>
>> Regards and blessings to all the team,
>>
>>
>> Laura Victoria
>>
>>
>>
>>
>> -- Forwarded message --
>> From: Tony Anderson 
>> Date: 2017-05-17 18:57 GMT-05:00
>> Subject: Re: [Sugar-devel] New ASLO Project Definition
>> To: Laura Vargas 
>>
>>
>> Hi, Laura
>>
>> Done.
>>
>> Tony
>>
>>
>> On 05/18/2017 12:56 AM, Laura Vargas wrote:
>>
>> Samuel and new ASLO team,
>>
>> Can you please attach the pdf with the project description?
>>
>> In my opinion, as ASLO is such a powerful resource used today by active
>> deployments, a successful successor will provide at least the same services.
>>
>> Regards
>>
>> Laura V.
>> * I&D SomosAZUCAR.Org*
>>
>> “Solo la tecnología libre nos hará libres.”
>> ~ Laura Victoria
>>
>> Happy Learning!
>> #LearningByDoing
>> #Projects4good
>> #IDesignATSugarLabs
>> #WeCanDoBetter
>>
>>
>> ___
>> Sugar-devel mailing 
>> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>>
>>
>
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] New ASLO Project Definition

[Jatin Dhankhar]

Hi,
Thank you Laura for attaching the proposal.
I will be glad if you can point me in the right direction regarding my GSOC
project, suggest flaws and how it can be improved. If anyone has any
questions or speculations, feel free to ping me. I am also writing weekly
summary of GSOC here https://jatindhankhar.in/posts/.
If something is missing or incorrect, let me know.

Thanks,
Jatin Dhakhar

On Thu, May 18, 2017 at 9:10 AM, Laura Vargas 
wrote:

>
> Hi Jatin welcome to Sugar Labs Community!
>
> Hi Aleksey,
>
> I hope to find time to be able to follow Jatin's project proposed time
> line. I hope you can find some time too. See pdf attached for project's
> details.
>
> Regards and blessings to all the team,
>
>
> Laura Victoria
>
>
>
>
> -- Forwarded message --
> From: Tony Anderson 
> Date: 2017-05-17 18:57 GMT-05:00
> Subject: Re: [Sugar-devel] New ASLO Project Definition
> To: Laura Vargas 
>
>
> Hi, Laura
>
> Done.
>
> Tony
>
>
> On 05/18/2017 12:56 AM, Laura Vargas wrote:
>
> Samuel and new ASLO team,
>
> Can you please attach the pdf with the project description?
>
> In my opinion, as ASLO is such a powerful resource used today by active
> deployments, a successful successor will provide at least the same services.
>
> Regards
>
> Laura V.
> * I&D SomosAZUCAR.Org*
>
> “Solo la tecnología libre nos hará libres.”
> ~ Laura Victoria
>
> Happy Learning!
> #LearningByDoing
> #Projects4good
> #IDesignATSugarLabs
> #WeCanDoBetter
>
>
> ___
> Sugar-devel mailing 
> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
>
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep