Re: [IAEP] Priority languages to translate Sugar

I added Haitian Creole, even though it's already been partly translated, because the quality of the translations is weak and not finished. I know there was some talk in the past about hiring a firm - Educa Vision - to do the translations and contribute a Haitian Creole dictionary app, but I don't

Re: [IAEP] ASLO

ASLO isn't just a site for manual downloads. The build utilities for XO laptops hook into ASLO to download applications. Some sort of backward compatible API should be made for that. On Jul 14, 2016 12:43 PM, "Dave Crossland" wrote: > > On Jul 14, 2016 12:26 PM, "Tony Anderson"

Re: [IAEP] ASLO

On Jul 14, 2016 12:26 PM, "Tony Anderson" wrote: > > The problem is ASLO, our primary interface and support for our user community. > > If we are going the github route, we need to set up a means for updated versions of Activities to be made into bundles and installed on

Re: [IAEP] ASLO

The problem is ASLO, our primary interface and support for our user community. If we are going the github route, we need to set up a means for updated versions of Activities to be made into bundles and installed on the ASLO repository. Presumably documentation (but no code) would be required

Re: [IAEP] ASLO

On 14 July 2016 at 14:22, Tony Anderson wrote: > The obvious question is why? What functionality do we add for our users by > rewriting everything in Python 3? > The functionality of being able to run the software, because the underlying Python 2 packages are going away.

Re: [IAEP] ASLO

Hi, Dave The obvious question is why? What functionality do we add for our users by rewriting everything in Python 3? Tony On 07/14/2016 06:43 PM, Dave Crossland wrote: On Jul 14, 2016 12:26 PM, "Tony Anderson" > wrote: > > The

Re: [IAEP] ASLO

On 14 July 2016 at 13:13, Samuel Greenfeld wrote: > The build utilities for XO laptops hook into ASLO to download applications. > Cool! > Some sort of backward compatible API should be made for that. > Sure. Where is the API documented?

Re: [IAEP] ASLO

On Jul 14, 2016 8:15 AM, "Sam Parkinson" wrote: > > > > On Thu, Jul 14, 2016 at 10:01 PM, Dave Crossland wrote: >> >> >> On 14 July 2016 at 07:13, Sam Parkinson wrote: >>> >>> What do you mean? ASLO is based on very old

Re: [IAEP] ASLO

I don't know where this (as well as many of Sugar's APIs) are documented. It would be best to look at the original PHP code as well as the clients' intent: - http://git.sugarlabs.org/slo-activities/mainline/blobs/master/site/app/webroot/services/update-aslo.php -

Re: [IAEP] ASLO

On 14 July 2016 at 07:13, Sam Parkinson wrote: > What do you mean? ASLO is based on very old technology, which is going to > get broken. > > 10/10 would love to improve ASLO. I actually did an "ASLO2" effort a > while ago, although that failed for reasons that are

Re: [IAEP] ASLO

On Thu, Jul 14, 2016 at 10:01 PM, Dave Crossland wrote: On 14 July 2016 at 07:13, Sam Parkinson wrote: What do you mean? ASLO is based on very old technology, which is going to get broken. 10/10 would love to improve ASLO. I actually did an

Re: [IAEP] ASLO

On Thu, Jul 14, 2016 at 5:04 PM, Tony Anderson wrote: Apparently, it is another victim to 'deprecation'. Possibly the most important feature of Sugar today is that it is based on Python 2.7 which is not being 'enhanced'. What do you mean? ASLO is based on very old

Re: [IAEP] Priority languages to translate Sugar

Here is the first draft of the list for the Sugar translation pending projects. Hopefully, to be cosidered by the Sugar Projects Translation Fund: https://titanpad.com/SLLL I have tried to summarize to the best of my knowledge current initiatives from local Communities in America. If you have

Re: [IAEP] ASLO

ASLO, which is our most used service to our user-base, is back online, but is not operational. Yesterday, it reported a long list of error messages. Apparently, it is another victim to 'deprecation'. Possibly the most important feature of Sugar today is that it is based on Python 2.7 which is

Re: [IAEP] ASLO

El 14/07/16 a las 11:43, Dave Crossland escribió: > We need a plan to move off this php5 codebase. > > I am proposing a simple static site that hosts xo bundles, that is > functionally equivalent to the php5 codebase. > Aleksey had proposed this:

Re: [IAEP] Status of Samson's project

Hi Samson! 2016-06-28 13:45 GMT-05:00 samson goddy : > I don't know why i did not receive the confirmation code yet for the IAEP. > I didn't even receive this mail officially, it was forwarded to me by > ibiam. > > I have nothing to say because i am tired and sad,

Re: [IAEP] Priority languages to translate Sugar

Hi Folks… Although it may seem a nice idea to propose translations into many languages, at this time I feel translations should be restricted to those language groups that have the XO hardware to use Sugar, like those in Peru and Haiti. Trying to add some of the Native American languages, where

Re: [IAEP] Private emails (was Re: Save as)

2016-07-10 12:30 GMT-05:00 Sebastian Silva : > > El 10/07/16 a las 12:26, Tony Anderson escribió: > > Where is our list regarding the educational goals of Sugar? > > Yup, this is it. > > As a rule of thumb, if it mentions git or Python, use sugar-devel. > > ;-) > > +1