Re: [IAEP] Status of Samson's project

[Laura Vargas]

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, because its over a month
>  after the motion passed. what is going on?
>
>
Was your contract issued OK?

Please share regurarly with the list how is your translation project coming
along.

Best of luck!

Many blessings and Thanks!

Samson Goddy
>
> --
> From: ibiamchihurumn...@gmail.com
> Date: Tue, 28 Jun 2016 11:39:34 -0700
> Subject: Fwd: [IAEP] Status of Samson's project
> To: samsongo...@hotmail.com
>
>
>
> -- Forwarded message --
> From: *Dave Crossland* 
> Date: Tue, Jun 28, 2016 at 9:52 AM
> Subject: [IAEP] Status of Samson's project
> To: iaep , SLOBs 
>
>
> Hi
>
> I'd like to request a brief update report on the status of Samson's
> project; its been about 6 weeks since the motion to fund the project
> was passed, but I haven't heard anything about it as I expected to
>
> --
> Cheers
> Dave
> ___
> 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
>



-- 
Laura V.
I SomosAZUCAR.Org

Identi.ca/Skype acaire
IRC kaametza

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

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

[Laura Vargas]

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 Great rule! Thanks icarito for your proactivity :D


> Tony
>
> On 07/10/2016 06:10 PM, Dave Crossland wrote:
>
>
> On Jul 10, 2016 11:54 AM, "Tony Anderson" < 
> tony_ander...@usa.net> wrote:
> >
> > However, since the various flaps concerning the Oversight Board, it is
> very
> > hard to find a discussion in IAEP that has any connection to education.
>
> My understanding is that this list is for threads not to do with software
> development technicalities but anything else to do with the project:
>
> "Its An Education _Project_"
>
>
>
>
> ___
> IAEP -- It's An Education Project (not a laptop 
> project!)IAEP@lists.sugarlabs.orghttp://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
>



-- 
Laura V.
I SomosAZUCAR.Org

Identi.ca/Skype acaire
IRC kaametza

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

Re: [IAEP] ASLO

[Sebastian Silva]

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:
http://school-network.org/hub/?view=Catalog=activity=featured



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

Re: [IAEP] Priority languages to translate Sugar

[Caryl Bigenho]

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 the hardware is not available 
is a futile exercise. 
At the same time, we need an increased effort to work on the porting of the top 
Sugar Activities to Sugarizer. That is where we can reach children and young 
people everywhere because the needed hardware is already in their hands.
A recent conversation I had with Samson Goddy in Nigeria went something like 
this:
C: What computers will you be using with the students?S: InfinityC: How many 
will you have?S: TwoC: But do most of them have smartphones?S: Yeah.
He agrees with me that we should be supporting Sugarizer so we can take 
advantage of the hardware the students already have.
So, along with these comments, I submit:  Simultaneous translation of Sugar 
Activities to their Sugarizer counter-parts is something that should be taken 
seriously.
How many of you folks can do JavaScript, HTML5, and CSS? Those are the skills 
needed to do this. You can get these skills online if you want to help. Please 
contact me and Lionel Laske if you are willing to help with this.
BTW… SOS (Sugar On A Stick) is not really a viable option.  I have tried it 
with teachers in a workshop and they found it too complicated to use and were 
afraid of infecting their computers with a virus. It was a great idea, 5 years 
ago. But, it is time to move on and Sugarizer is the direction of the future.
Caryl
From: s...@unleashkids.org
Date: Thu, 14 Jul 2016 10:02:19 -0400
To: la...@somosazucar.org
Subject: Re: [IAEP] Priority languages to translate Sugar
CC: iaep@lists.sugarlabs.org

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 know 
the status of any of that because I was not really involved in it.
On Thu, Jul 14, 2016 at 2:00 AM, Laura Vargas  wrote:
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 an idea or project to add please 
share the context/continent and relationship of the language with the SugarXO 
Community, and thanks in advance.

2016-07-09 11:25 GMT-05:00 Sebastian Silva :

  

  
  
El 09/07/16 a las 01:48, Laura Vargas escribió:




  

  

  Recalling Claudia's proposal to make a priority
languages list for Sugar translations, here in Perú I
did an informal survery with the team of the Dirección de 
Lenguas Indígenas del
Ministerio de Cultura, and noticing we already have
Quechua, Aymara and Awajún, they suggested (in no
specific order):



  
  - Ashaninka http://bdpi.cultura.gob.pe/pueblo/ashaninka


- Wampis http://bdpi.cultura.gob.pe/pueblo/wampis

  
  - Shipibo http://bdpi.cultura.gob.pe/pueblo/shipibo-konibo


  



Let's add Cherokee, possibly Navajo and Lakota?



To better word a phrase I wrote in another thread:

I do believe the mere possibility of attaining fluency in technology
and properly appropriable informatics holds the promise to empower
native cultures to better cope with modernity and even assume
leadership in it.


  



Is someone managing such list already?

  

  

  


  -- 

  Laura V.

I SomosAZUCAR.Org

IRC kaametza



Happy Learning!



  

  

  

  
  

  
  

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



  



-- 
Laura V.

I SomosAZUCAR.Org



Identi.ca/Skype acaire

IRC kaametza

Happy Learning!




___

IAEP -- It's An Education Project (not a laptop project!)

IAEP@lists.sugarlabs.org

http://lists.sugarlabs.org/listinfo/iaep



___
IAEP -- It's An 

Re: [IAEP] ASLO

[Samuel Greenfeld]

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
   -
   
http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/sugarlabs_activities/kspost.60.nochroot.aslo.sh
   -
   
https://github.com/sugarlabs/sugar/blob/master/src/jarabe/model/update/aslo.py

There are ways to build XO builds and update Sugar activities without ASLO
(although no automated one for apps installed to a user's home directory).
A bigger decision might be to eliminate getting Activities through this API.


On Thu, Jul 14, 2016 at 2:48 PM, Dave Crossland  wrote:

>
> 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?
>
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] ASLO

[Dave Crossland]

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?
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] ASLO

[Dave Crossland]

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.
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] ASLO

[Tony Anderson]

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 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.


It seems to me that the ALSO repository is dangerous unmaintained code 
and has been on its last legs for a while and those legs just broke. 
We can put them in a cast, but they are not going to heal.


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.


> Presumably documentation (but no code) would be required to document 
a procedure to submit or update activities.


Right.

> In the case of ASLO, the code base is PhP. At one time, it was 
proposed to implement in Python using Django - following the lead of 
Mozilla. This apparently didn't happen. Jekyll is clearly a much 
better framework, it's website promises that installing Jekyll is 
sufficient to create a website. :)


Is mozilla addons still a libre codebase?

> The 'crumbling to dust' applies to the code not Python. Any software 
needs support. Most of the original developers of the Sugar activities 
have moved on to greener pastures. We have activities that failed 
because they incorporated object code which was not recompiled for 
ARM. We have activities that failed because they were build with 
hulahop. We have activities that failed because they imported Abiword. 
I have not seen a single example of a Sugar activity that had to be 
updated because of Python 2.7.


Right :)

Python 2.7 packages themselves will be dropped and all python 2 code 
needs porting to 3 well in advance of that.


Eventually all i386 packages will be dropped too.

We need to plan for these eventualities :)



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

Re: [IAEP] ASLO

[Samuel Greenfeld]

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"  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 the ASLO
> repository.
>
> It seems to me that the ALSO repository is dangerous unmaintained code and
> has been on its last legs for a while and those legs just broke. We can put
> them in a cast, but they are not going to heal.
>
> 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.
>
> > Presumably documentation (but no code) would be required to document a
> procedure to submit or update activities.
>
> Right.
>
> > In the case of ASLO, the code base is PhP. At one time, it was proposed
> to implement in Python using Django - following the lead of Mozilla. This
> apparently didn't happen. Jekyll is clearly a much better framework, it's
> website promises that installing Jekyll is sufficient to create a website.
> :)
>
> Is mozilla addons still a libre codebase?
>
> > The 'crumbling to dust' applies to the code not Python. Any software
> needs support. Most of the original developers of the Sugar activities have
> moved on to greener pastures. We have activities that failed because they
> incorporated object code which was not recompiled for ARM. We have
> activities that failed because they were build with hulahop. We have
> activities that failed because they imported Abiword. I have not seen a
> single example of a Sugar activity that had to be updated because of Python
> 2.7.
>
> Right :)
>
> Python 2.7 packages themselves will be dropped and all python 2 code needs
> porting to 3 well in advance of that.
>
> Eventually all i386 packages will be dropped too.
>
> We need to plan for these eventualities :)
>
> ___
> 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] ASLO

[Dave Crossland]

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 the ASLO
repository.

It seems to me that the ALSO repository is dangerous unmaintained code and
has been on its last legs for a while and those legs just broke. We can put
them in a cast, but they are not going to heal.

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.

> Presumably documentation (but no code) would be required to document a
procedure to submit or update activities.

Right.

> In the case of ASLO, the code base is PhP. At one time, it was proposed
to implement in Python using Django - following the lead of Mozilla. This
apparently didn't happen. Jekyll is clearly a much better framework, it's
website promises that installing Jekyll is sufficient to create a website.
:)

Is mozilla addons still a libre codebase?

> The 'crumbling to dust' applies to the code not Python. Any software
needs support. Most of the original developers of the Sugar activities have
moved on to greener pastures. We have activities that failed because they
incorporated object code which was not recompiled for ARM. We have
activities that failed because they were build with hulahop. We have
activities that failed because they imported Abiword. I have not seen a
single example of a Sugar activity that had to be updated because of Python
2.7.

Right :)

Python 2.7 packages themselves will be dropped and all python 2 code needs
porting to 3 well in advance of that.

Eventually all i386 packages will be dropped too.

We need to plan for these eventualities :)
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] ASLO

[Tony Anderson]

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 to 
document a procedure to submit or update activities.


In the case of ASLO, the code base is PhP. At one time, it was proposed 
to implement in Python using Django - following the lead of Mozilla. 
This apparently didn't happen. Jekyll is clearly a much better 
framework, it's website promises that installing Jekyll is sufficient to 
create a website. :)


The 'crumbling to dust' applies to the code not Python. Any software 
needs support. Most of the original developers of the Sugar activities 
have moved on to greener pastures. We have activities that failed 
because they incorporated object code which was not recompiled for ARM. 
We have activities that failed because they were build with hulahop. We 
have activities that failed because they imported Abiword. I have not 
seen a single example of a Sugar activity that had to be updated because 
of Python 2.7.


Tony


On 07/14/2016 02:47 PM, Dave Crossland wrote:



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 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 
documented on my blog.  I would be up for using a AppStream and 
PackageKit based stack to reinvent the activity store experience though.

>>
>>
>> I think if ASLO can't be resuscitated, something VERY simple - a 
set of XO files and a Jekyll-like simple HTML site that links to them 
- would best replace it.

>
>
> Nice idea.  That is very simple!  But remember that you also needs 
search,


As a single page the browser search provides that. Site wide Google 
Search  provides that.


> i18n,

Its static content. i18n can be done inline.

> provide an api for Sugar to get list of bundles to update.

What is the current api URL schema and do we have examples of sample 
data or do we need to bring aslo back up?


Jekyll can provide structured data in html, XML, json, etc.

> The current ASLO also has other features, like a developer interface 
(how do devs submit updates to the static site)


Github pull request.

> and only showing the user activities that are compatible with the 
version of Sugar they are running.


They click the version and a <10 line JavaScript script hides the 
irrelevant information.


>>> Re Sugar using python2; a port to python3 was previously 
investigated as part of last years GSoC. We can port it baring our 
telepathy-python dependency.  (FYI there has not been a commit for 
telepathy salut or gabble in the past 2 years.  Dead upstream?


Salut could just be stable. The spec is at least a decade old. 
Telepathy and Gabble might be lost causes.


> Still, there are so many bugs that affect sugar.  10/10 would love 
to port collab to using something like Matrix.Org - the spec is *way* 
is more easy to understand than telepathy.


Yes matrix is very nice. However I don't know if it supports 
collaboration otself, I think we need a crdt library or something 
similar on top? Or was that the case with telepathy anyway?


> Telepathy seems much more complex than Sugar needs - we don't need 
abstract multi-backend support.


What are examples of Activities that deeply integrated collaboration? 
Write?


>> I think we should not upgrade to python3 but javascript.
>
>
> Py2 -> Py3 is a small change.  Py2 -> JS is massive.

The return on investment is the same, though.

> And moving to JS means you have to replace telepathy, for Py3, we 
can easily port the python-telepathy library ourselves (it is very 
small library)


Lionel already has real time collaboration working on Sugarizer, this 
is no biggie.


> What do you mean by javascript?  It is javascript and HTML?  Or 
javascript on top of GJS, using the same amazing Gtk+ technology stack?


I am proposing sunsetting the python codebase because it is crumbling 
to dust before our eyes. The Sugar Python codebase could go back to 
being maintained by OLPC Inc and Sugar Labs become a web shop. It 
seems the new "OLPC Laptop" will be running vanilla Ubuntu.


> One idea that had been in my mind recently is moving parts of 
sugar-toolkit-gtk3 to Vala or C.  In Vala/C, you can expose the 
objects via Gobject Introspection - meaning that they are accessible 
from Python{2,3}, Javascript, Vala, Perl, and probably more.  Don't 
know if it would be worth the barrier that it adds to 

Re: [IAEP] Priority languages to translate Sugar

[Sora Edwards-Thro]

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 know the status of any of that because I was not really involved in
it.

On Thu, Jul 14, 2016 at 2:00 AM, Laura Vargas  wrote:

> 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 an idea or project to add
> please share the context/continent and relationship of the language with
> the SugarXO Community, and thanks in advance.
>
>
> 2016-07-09 11:25 GMT-05:00 Sebastian Silva :
>
>> El 09/07/16 a las 01:48, Laura Vargas escribió:
>>
>> Recalling Claudia's proposal to make a priority languages list for Sugar
>> translations, here in Perú I did an informal survery with the team of the 
>> Dirección
>> de Lenguas Indígenas del Ministerio de Cultura, and noticing we already
>> have Quechua, Aymara and Awajún, they suggested (in no specific order):
>>
>> - Ashaninka http://bdpi.cultura.gob.pe/pueblo/ashaninka
>> - Wampis http://bdpi.cultura.gob.pe/pueblo/wampis
>> - Shipibo http://bdpi.cultura.gob.pe/pueblo/shipibo-konibo
>>
>>
>> Let's add Cherokee, possibly Navajo and Lakota?
>>
>> To better word a phrase I wrote in another thread:
>> I do believe the mere possibility of attaining fluency in technology and
>> properly appropriable informatics holds the promise to empower native
>> cultures to better cope with modernity and even assume leadership in it.
>>
>>
>> Is someone managing such list already?
>>
>> --
>> Laura V.
>> I SomosAZUCAR.Org
>> IRC kaametza
>>
>> Happy Learning!
>>
>>
>>
>> ___
>> IAEP -- It's An Education Project (not a laptop 
>> project!)IAEP@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/iaep
>>
>>
>>
>
>
> --
> Laura V.
> I SomosAZUCAR.Org
>
> Identi.ca/Skype acaire
> IRC kaametza
>
> Happy Learning!
>
>
> ___
> 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] ASLO

[Dave Crossland]

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 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 documented on my
blog.  I would be up for using a AppStream and PackageKit based stack to
reinvent the activity store experience though.
>>
>>
>> I think if ASLO can't be resuscitated, something VERY simple - a set of
XO files and a Jekyll-like simple HTML site that links to them - would best
replace it.
>
>
> Nice idea.  That is very simple!  But remember that you also needs
search,

As a single page the browser search provides that. Site wide Google Search
provides that.

> i18n,

Its static content. i18n can be done inline.

> provide an api for Sugar to get list of bundles to update.

What is the current api URL schema and do we have examples of sample data
or do we need to bring aslo back up?

Jekyll can provide structured data in html, XML, json, etc.

> The current ASLO also has other features, like a developer interface (how
do devs submit updates to the static site)

Github pull request.

> and only showing the user activities that are compatible with the version
of Sugar they are running.

They click the version and a <10 line JavaScript script hides the
irrelevant information.

>>> Re Sugar using python2; a port to python3 was previously investigated
as part of last years GSoC.  We can port it baring our telepathy-python
dependency.  (FYI there has not been a commit for telepathy salut or gabble
in the past 2 years.  Dead upstream?

Salut could just be stable. The spec is at least a decade old. Telepathy
and Gabble might be lost causes.

> Still, there are so many bugs that affect sugar.  10/10 would love to
port collab to using something like Matrix.Org - the spec is *way* is more
easy to understand than telepathy.

Yes matrix is very nice. However I don't know if it supports collaboration
otself, I think we need a crdt library or something similar on top? Or was
that the case with telepathy anyway?

> Telepathy seems much more complex than Sugar needs - we don't need
abstract multi-backend support.

What are examples of Activities that deeply integrated collaboration? Write?

>> I think we should not upgrade to python3 but javascript.
>
>
> Py2 -> Py3 is a small change.  Py2 -> JS is massive.

The return on investment is the same, though.

> And moving to JS means you have to replace telepathy, for Py3, we can
easily port the python-telepathy library ourselves (it is very small
library)

Lionel already has real time collaboration working on Sugarizer, this is no
biggie.

> What do you mean by javascript?  It is javascript and HTML?  Or
javascript on top of GJS, using the same amazing Gtk+ technology stack?

I am proposing sunsetting the python codebase because it is crumbling to
dust before our eyes. The Sugar Python codebase could go back to being
maintained by OLPC Inc and Sugar Labs become a web shop. It seems the new
"OLPC Laptop" will be running vanilla Ubuntu.

> One idea that had been in my mind recently is moving parts of
sugar-toolkit-gtk3 to Vala or C.  In Vala/C, you can expose the objects via
Gobject Introspection - meaning that they are accessible from Python{2,3},
Javascript, Vala, Perl, and probably more.  Don't know if it would be worth
the barrier that it adds to development though.

If we want to provide software for all the world's children we must develop
software that runs on all platforms.
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] ASLO

[Sam Parkinson]

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 "ASLO2" effort 
a while ago, although that failed for reasons that are documented on 
my blog.  I would be up for using a AppStream and PackageKit based 
stack to reinvent the activity store experience though.


I think if ASLO can't be resuscitated, something VERY simple - a set 
of XO files and a Jekyll-like simple HTML site that links to them - 
would best replace it.


Nice idea.  That is very simple!  But remember that you also needs 
search, i18n, provide an api for Sugar to get list of bundles to 
update.  The current ASLO also has other features, like a developer 
interface (how do devs submit updates to the static site) and only 
showing the user activities that are compatible with the version of 
Sugar they are running.




Re Sugar using python2; a port to python3 was previously 
investigated as part of last years GSoC.  We can port it baring our 
telepathy-python dependency.  (FYI there has not been a commit for 
telepathy salut or gabble in the past 2 years.  Dead upstream?  
Still, there are so many bugs that affect sugar.  10/10 would love 
to port collab to using something like Matrix.Org - the spec is 
*way* is more easy to understand than telepathy.  Telepathy seems 
much more complex than Sugar needs - we don't need abstract 
multi-backend support.


I think we should not upgrade to python3 but javascript.


Py2 -> Py3 is a small change.  Py2 -> JS is massive.  And moving to JS 
means you have to replace telepathy, for Py3, we can easily port the 
python-telepathy library ourselves (it is very small library)


What do you mean by javascript?  It is javascript and HTML?  Or 
javascript on top of GJS, using the same amazing Gtk+ technology stack?


One idea that had been in my mind recently is moving parts of 
sugar-toolkit-gtk3 to Vala or C.  In Vala/C, you can expose the objects 
via Gobject Introspection - meaning that they are accessible from 
Python{2,3}, Javascript, Vala, Perl, and probably more.  Don't know if 
it would be worth the barrier that it adds to development though.


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

Re: [IAEP] ASLO

[Dave Crossland]

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 documented on my
> blog.  I would be up for using a AppStream and PackageKit based stack to
> reinvent the activity store experience though.
>

I think if ASLO can't be resuscitated, something VERY simple - a set of XO
files and a Jekyll-like simple HTML site that links to them - would best
replace it.


> Re Sugar using python2; a port to python3 was previously investigated as
> part of last years GSoC.  We can port it baring our telepathy-python
> dependency.  (FYI there has not been a commit for telepathy salut or gabble
> in the past 2 years.  Dead upstream?  Still, there are so many bugs that
> affect sugar.  10/10 would love to port collab to using something like
> Matrix.Org - the spec is *way* is more easy to understand than telepathy.
> Telepathy seems much more complex than Sugar needs - we don't need abstract
> multi-backend support.
>

I think we should not upgrade to python3 but javascript.
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] ASLO

[Sam Parkinson]

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 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 documented on my 
blog.  I would be up for using a AppStream and PackageKit based stack 
to reinvent the activity store experience though.


Re Sugar using python2; a port to python3 was previously investigated 
as part of last years GSoC.  We can port it baring our telepathy-python 
dependency.  (FYI there has not been a commit for telepathy salut or 
gabble in the past 2 years.  Dead upstream?  Still, there are so many 
bugs that affect sugar.  10/10 would love to port collab to using 
something like Matrix.Org - the spec is *way* is more easy to 
understand than telepathy.  Telepathy seems much more complex than 
Sugar needs - we don't need abstract multi-backend support.


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

Re: [IAEP] ASLO

[Tony Anderson]

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

not being 'enhanced'.

At the next Board Meeting, we need to consider ,  how to restore this 
service and to see that it is properly supported going forward.


Certainly the developer hub needs to be re-considered in light of the 
decision to move the activities to github.


Tony

On 07/11/2016 06:00 PM, iaep-requ...@lists.sugarlabs.org wrote:

Send IAEP mailing list submissions to
iaep@lists.sugarlabs.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.sugarlabs.org/listinfo/iaep
or, via email, send a message with subject or body 'help' to
iaep-requ...@lists.sugarlabs.org

You can reach the person managing the list at
iaep-ow...@lists.sugarlabs.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of IAEP digest..."


Today's Topics:

1. Re: [Systems] Maintenance downtime today for OS upgrades
   (Sebastian Silva)


--

Message: 1
Date: Mon, 11 Jul 2016 09:26:43 -0500
From: Sebastian Silva 
To: Laura Vargas , Bernie Innocenti

Cc: "Lim, Aleksey" , systems
, Sugar Devel
, IAEP 
Subject: Re: [IAEP] [Systems] Maintenance downtime today for OS
upgrades
Message-ID: 
Content-Type: text/plain; charset="utf-8"

Hi,

I restarted the wiki service for the pe.sugarlabs.org domain.

I run it in `screen` but I will make it a proper service or maybe apache
can launch it.


El 11/07/16 a las 09:17, Laura Vargas escribió:

Hi Bernie,

Thanks for the maintenance. This is tI report you our wiki is also down!

http://pe.sugarlabs.org/ir/

Thanks in advance.

2016-07-10 12:44 GMT-05:00 Bernie Innocenti >:

 On 10/07/16 12:57, Bernie Innocenti wrote:
 > On 09/07/16 19:15, Bernie Innocenti wrote:
 >
 >> Most notably, activities.sugarlabs.org
  is still down. It probably
 >> doesn't like PHP 7... The wiki is also very slow because I had to
 >> disable APC until I understand how to make Mediawiki use the
 new APCu.
 >
 > I'm still working to restore ASLO. It's an old codebase that was
 still
 > using PHP features that were deprecated in PHP 5.5 and removed
 in PHP 7...

 I finally got ASLO to display its front page, but activities are not
 being listed. I had to switch the DB backend to mysqli because the
 mysql
 extension has been removed in PHP7.

 Aleksey, since you're familiar with ASLO's codebase, would you be able
 to look into the outstanding issues?

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




--
Laura V.
I SomosAZUCAR.Org

Identi.ca/Skype acaire
IRC kaametza

Happy Learning!



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

-- next part --
An HTML attachment was scrubbed...
URL: 


--

Subject: Digest Footer

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

--

End of IAEP Digest, Vol 100, Issue 30
*


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

Re: [IAEP] Priority languages to translate Sugar

[Laura Vargas]

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 an idea or project to add
please share the context/continent and relationship of the language with
the SugarXO Community, and thanks in advance.


2016-07-09 11:25 GMT-05:00 Sebastian Silva :

> El 09/07/16 a las 01:48, Laura Vargas escribió:
>
> Recalling Claudia's proposal to make a priority languages list for Sugar
> translations, here in Perú I did an informal survery with the team of the 
> Dirección
> de Lenguas Indígenas del Ministerio de Cultura, and noticing we already
> have Quechua, Aymara and Awajún, they suggested (in no specific order):
>
> - Ashaninka http://bdpi.cultura.gob.pe/pueblo/ashaninka
> - Wampis http://bdpi.cultura.gob.pe/pueblo/wampis
> - Shipibo http://bdpi.cultura.gob.pe/pueblo/shipibo-konibo
>
>
> Let's add Cherokee, possibly Navajo and Lakota?
>
> To better word a phrase I wrote in another thread:
> I do believe the mere possibility of attaining fluency in technology and
> properly appropriable informatics holds the promise to empower native
> cultures to better cope with modernity and even assume leadership in it.
>
>
> Is someone managing such list already?
>
> --
> Laura V.
> I SomosAZUCAR.Org
> IRC kaametza
>
> Happy Learning!
>
>
>
> ___
> IAEP -- It's An Education Project (not a laptop 
> project!)IAEP@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/iaep
>
>
>


-- 
Laura V.
I SomosAZUCAR.Org

Identi.ca/Skype acaire
IRC kaametza

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