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] do OLPC browsers support WebRTC microphone audio input?

[Sam Parkinson]

On Sun, 2017-03-12 at 12:16 -0400, Adam Holt wrote:
> Hi Jim,
> 
> On Sun, Mar 12, 2017 at 12:01 PM, Jim Salsman 
> wrote:
> > On Sat, Mar 11, 2017 at 11:55 PM, Sam P.  wrote:
> > > OLPC OS ships with an ancient (2011?) version of WebKitGtk+.  I
> > don't even
> > > think that the current version supports WebRTC.
> > >
> > > Maybe you could run a version of Firefox or chrome on it?
> > 
> > Does anyone out there have Chrome or Firefox compiling on OLPCs?
> 
> There was some solid research comparing Firefox 26 and Firefox 50 on
> XO laptops (particularly on Fedora 18) not so many weeks ago in
> December and January:
> 
>    http://lists.laptop.org/pipermail/devel/2017-January/thread.html
>    http://wiki.laptop.org/go/Browser_improvements
> 
> Rough conclusion seems to be that Firefox 26 is ready-to-go if you
> want that, but that it would take more work to get Firefox 50
> compiling cleanly here?

I'm quite amazed, but Firefox has supported WebRTC since version 22, so
it might work?!  http://caniuse.com/#search=webrtc (you have to click
the show all versions button)

> 
> Also if I recall Nathan Riddle also has a couple further details,
> that might not have made it into the thread above, so I can put you
> in contact with him directly if nec?
> 
> ___
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
-- 
Thanks,
Sam

https://www.sam.today/

Latest blog post: Testing GraphQL with Graphene Django - 
https://learntemail.sam.today/blog/testing-graphql-with-graphene-django/
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] Sugar Labs 2017 Budget

[Sam Parkinson]

On Sat, 2017-02-25 at 08:36 +0530, Dave Crossland wrote:
> Actually I am not convinced of this; I do not believe that the latest
> releases of the Python codebase reach classrooms, and the js codebase
> only reaches one. 
> 
> One of the projects listed is social help. It's a fine idea, but a
> cursory look at the site shows it has extremely low activity. I think
> it would be better to shut it down. 

Sugar tries to literally replace every part of the computer that a user
sees.  And believe it or not; that is a hard goal for a small free
software community.  3 people in their spare time can't replace the
years of work poured into every other desktop environment & their
software.

You're 100% spot on.  The future of SL is things like TurtleJS.

-- 
Thanks,
Sam

https://www.sam.today/

Latest blog post: Local Politicians Meet InfoSec - a Wordpress Disaster - 
https://learntemail.sam.today/blog/local-politicians-meet-infosec-a-wordpress-disaster/
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Systems] Services provided by Sugarlabs - Inventory - Maintainers

[Sam Parkinson]

On Sat, 2017-02-18 at 20:25 -0300, Samuel Cantero wrote:
> Hello everyone,
> 
> Currently we have two physical nodes - Justice and Freedom - which
> belongs to SugarLabs and one VM (Sunjammer) provided by the FSF.
> These nodes are running Ubuntu 16.04. Last upgrade was done by Bernie
> Innocenti and by me.
> 
> The main purpose of this email is to update our list of
> machine/services maintainers. We need to have a responsible for every
> service and update our wiki page according to the provided
> information. The Maintainer must be responsible for keeping service
> up, the OS updated and apply all the security patches. I can find
> that many of our services are just broken or forgotten. We need to
> some do cleaning/pruning.
> 
> Below are listed all the current machines/services we're hosting.
> Please, if you're responsible for the machine/service maintenance,
> identify yourself. If no one if responsible for the machine/service,
> we need to define what to do with those machines, whether to find a
> new maintainer or to decommission the machine/service.
> 
> Justice:
> 
> 1. OS: Ubuntu 16.04.1 LTS, 
> 2. Maintainers: Bernie Innocenti, Sebastian Silva and Samuel Cantero.
> 3. Services (VMs running inside this node):
> amnesia:
> OS: Fedora 18. This OS has reached End of Life.
> Maintainer: X.
> Services provided:
> Apparently it's used by Paraguay Educa. It's running an HTTP server,
> MySQL, etc.
> Are we still using this?
> aslo:
> OS: Ubuntu 14.04.5. EOL: April 2019.
> Maintainer: Samuel Cantero.
> Codebase maintainer: X. it would be nice to have someone behind it.
> Aleksey have been helping so far.
> Services provided:
> activities.sugarlabs.org
> zatoichi:
> OS: Ubuntu 12.04.5 LTS. EOL: April 2017.
> Maintainer: X.
> Services provided:
> *.paraguayeduca.org
> Can we keep all the services for PyEduca in one machine? Do we really
> need amnesia and zatoichi?
> lightwave:
> OS: Ubuntu 16.04.1 LTS.
> Maintainer: Bernie Innocenti / Samuel Cantero.
> Services provided:
> Primary DNS server.
> mothership:
> I can't get into the VM. I don't have information about maintainer
> nor the OS/services running inside.
> pootle:
> OS: Ubuntu 14.04.4 LTS.
> Maintainer: Chris Leonard.
> Services provided:
> translate.sugarlabs.org
> library:
> OS: Ubuntu 12.04.5 LTS.
> Maintainer: X.
> Services provided:
> library.sugarlabs.org (pathagar).
> Jita:
> OS: Ubuntu 12.04.5 LTS
> Maintainer: X.
> Services provided:
> cgit.sugarlabs.org. I guess we can decommission this.
> chat.sugarlabs.org.
> fedora.sugarlabs.org (service down, no one reported so no one is
> using it).
> git.sugarlabs.org (gitorious). Someone should move all repos inside
> git.sl.o to GitHub.
> meeting.sugarlabs.org,
> network.sugarlabs.org,
> node.sugarlabs.org (are we using this?)
> school-network.org
> Freedom
> 
> 1. OS: Ubuntu 16.04.1 LTS, 
> 2. Maintainers: Bernie Innocenti, Sebastian Silva, Sam Parkinson and
> Samuel Cantero.
> 3. Services:
> Main backup server.
> We have a bunch of VMs not used by SL. These are: ole, kuckuck,
> munin, owncloud, pirate, hammock, chat, hanginggarden, beacon. AFAIK,
> these VM belongs to Stephan Unterhauser (Dogi). I don't know about
> the terms defined between SugarLabs and Stephan. Hence, I must
> ask: Is Sugarlabs going to continue hosting these VMs?
> We also have the following containers:
> org.sugarlabs.www-rebuilder.
> Maintainer: Sam Parkinson.
> Services:
> used for update the SL www site after a new commit into GitHub repo
> (through Webhooks).
> related: www.sugarlabs.org
> org.sugarlabs.use-socialhelp:
> Maintainer: Sam Parkinson.
> Services:
> socialhelp.sugarlabs.org?
> org.sugarlabs.socialhelp_sso
> Maintainer: Sam Parkinson.
> Services:
> socialhelp.sugarlabs.org?
> local_discourse/app
> Maintainer: Sam Parkinson.
> Services:
> socialhelp.sugarlabs.org?
> org.turtleartday.www-rebuilder
> Maintainer: Samuel Cantero.
> Services:
> used for update the turtleartday.org site after a new commit into
> GitHub repo (through Webhooks).
> related: turtleartday.org
> org.sugarlabs.developer-rebuilder
> Maintainer: Sam Parkinson.
> Services:
> related: developer.sugarlabs.org
> org.sugarlabs.bundlebin
> Maintainer: Sam Parkinson.
> Services:
> bundlebin.sugarlabs.org
> org.sugarlabs.bugs
> Maintainer: Sam Parkinson / Samuel Cantero.

To the best of my knowledge, bundlebin is not/never was actively used. 
I will remove it from the server.

> Services:
> bugs.sugarlabs.org
> Sunjammer
> 
> 1. OS: Ubuntu 16.04.1 LTS, 
> 2. Maintainers: Bernie Innocenti, Sebastian Silva, and Samuel
> Cantero.
> 3. S

Re: [IAEP] Revision 50 of the Sugar Labs Fundraising Committe notes

[Sam Parkinson]

Well, Google is really one of the biggest non-free software vendors 
today, so saying yes to google and no to microsoft is very silly.


Also, organisations are big.  Google makes Google Classroom and Google 
Apps for Education ("GAFE"), yet still the OSPO gives SL funds.


Thanks,
Sam

On Sun, Jul 17, 2016 at 1:56 AM, Dave Crossland  wrote:


Hi Laura

I'd like to follow up on this thread :)

On 15 July 2016 at 23:39, Laura Vargas  wrote:
- Microsoft (laura -1: No private software funds shall get into our 
accounts!) (dave +1: money is money, and almost all the funding 
sources are private companies; the Nadella Microsoft is very 
different to the Gates/Ballmer era and is about as ethical as 
Google, Facebook, Intel, or IBM :) (Laura: don't apply, the 
requirement from grants providers to resonate SL values is not 
negotiable as it stands for the whole learning model we are 
proposing.) (Sean -1: No point adding Microsoft or Bill & Melinda 
Gates Foundation to this list.) (Dave: You assert your own values as 
"SL values", but the observable behaviour of SL and OLPC is not 
consistent with them. What do you see as the difference between 
Google and Microsoft? Why does SL take Google's money?)


How does Google resonate with SL values more than Microsoft?

Cheers
Dave
___
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 <d...@lab6.com> wrote:


On 14 July 2016 at 07:13, Sam Parkinson <sam.parkins...@gmail.com> 
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

[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] Voting on GPLv3 motion

[Sam Parkinson]

On Fri, Jul 1, 2016 at 3:32 PM, Tony Anderson  
wrote:

Hi, Dave

This is what I have been able to find regarding the GPLv3 motion.

At today's Sugar Labs oversight board meeting [1], we discussed the 
motion submitted by Sebastian Silva to finalize the transition from 
GPLv2 to GPLv3 for the Sugar core libraries (Sugar Activity 
developers are still free to choose whatever Libre license they 
prefer for their work.) See [2]. I second the motion and bring it to 
you in an email vote.


Didn't the motion pass?  I already merged the change of licence into 
the sugar repo, as per the approval.


Also, will we migrate sugar-toolkit-gtk3 to LGPLv3+?  What about 
sugar-datastore?





Approve.

Tony Anderson

Approve.

Sameer

Approve.


BTW I'm worried about the fact that the Sugar-Web part (and so 
Sugarizer too) use the Apache 2.0 Licence.

I'm not a specialist but what imply a Licence migration ?


These web people and their non copyleft liscenses.  I'm defiantly not a 
copyright holder for sugar-web, but aren't they worried about people 
stealing their work and rolling it into nonfree software?


Thanks,
Sam



  Lionel.

+1 para GPLv3 motion


___
Lic. José Miguel García
Montevideo - Uruguay

Approved!

Claudia

Today at 8:04PM (ET) would be the deadline for the GPLv3 motion. (May 
13 @ 8:04PM ET)


So this vote was 6 in favor and one abstention.

Tony

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

Re: [IAEP] Which cheap 2016 Laptop should be our reference?

[Sam Parkinson]

If we want a reference device, it needs to be as boring as possible.  
Let's not repeat the XO situation.


The issue with XOs now seems to be that they are all special snowflakes 
with their special kernel versions.  This is my understanding of why we 
can't update them to the new versions of upstream software.


Devices with mainline kernel are very good.  I'm sure everybody is 
familiar with this experience; having a random old laptop (XP era, 
older maybe) that can run all the latest distributions,  Supporting my 
software on that laptop is not hard - it is the same as the Fedora on 
every other laptop.


If we choose something with a special snowflake kernel, the support 
burden falls on us to keep the kernel up to date so that we can run new 
Systemd versions for the new Fedora versions.


Thanks,
Sam

On Wed, Jun 22, 2016 at 10:40 PM, Dave Crossland  wrote:


On Jun 21, 2016 10:41 AM, "Walter Bender"  
wrote:

>
> soliciting a small donation of hardware from Google as a reference 
platform.


Who do we know at google who could help with that?

Despite google fonts being a client, I don't know anyone there who 
could help with this :(


In any case, which laptop they might give us may not be the best to 
recommend.


There are 2 obvious candidates to me, the new "olpc laptop" available 
from olpc inc to USA resident individuals for us$200 plus us$100 
shipping from china, with other countries shipping fees varying; and 
the One Education "Infinity" which is us$350 plus shipping from 
Taiwan/ Australia.


The olpc unit ships with sugar and its cheaper so seems a better bet 
given both launched around now.
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] Which cheap 2016 Laptop should be our reference?

[Sam Parkinson]

On Thu, Jun 23, 2016 at 12:33 AM, Walter Bender 
 wrote:



On Wed, Jun 22, 2016 at 10:30 AM, Sean DALY  
wrote:


On Wed, Jun 22, 2016 at 4:25 PM, Sebastian Silva 
 wrote:
I wouldn't dismiss the Raspberry Pi 3 or similar single board 
computer



Around the time RPi hit the million unit mark I floated the idea of 
a Sugar-branded enclosure for it, distributed through the RPi 
partner network.


The problem at the time was that the Sugar experience on RPi was 
pretty terrible. I suspect it is pretty decent on the newer models. 
Do we know?


I think that the issue was mainly it was hard to install Sugar on the 
1st generation rpis.  The 1st gen was a special snowflake and it didn't 
run normal distros that could normally intall sugar.


I think the situation has changed?  Can't the rpi3 run mainline kernel?

There are actually a few funny tablets that run mainline kernel, like 
the 2013 nexus 7.  (not the 2012 nexus7, that's a tegra chip)  Maybe 
those are of interest to us.


Thanks,
Sam



-walter



Sean.





--
Walter Bender
Sugar Labs
http://www.sugarlabs.org

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

Re: [IAEP] 172 XO-1s for $24 each (+ freight) $4,000 total

[Sam Parkinson]

Dave, I don't frequent EBay listings, but it says:

>  Customer is responsible for arrangement of freight trucking pickup 
and insurance from our dock


Is that referring to the charging docks or the palette of laptops?

Obviously this is a small detail that doesn't effect the discussion, 
but it would probably change the figures a bit.


Thanks,
Sam

On Mon, Jun 13, 2016 at 3:07 PM, Dave Crossland  wrote:

Hi

http://www.ebay.com/itm/Qty-172-OLPC-One-Laptop-Per-Child-XO-1-w-7-5-TFT-256MB-RAM-1024KB-ROM-/262478690514

I propose that Sugar Labs buy these, image them with the 0.110
release, and sale them to raise funds; individual units regularly
clear $100 each, so this will raise around $13,000

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

Re: [IAEP] 172 XO-1s for $24 each (+ freight) $4,000 total

[Sam Parkinson]

Hi Dave,

They are XO1s... does Sugar run OK on the XO1?

$100 seems steep for an XO1.  In the USA, apparently less than $100 
yeilds you a "tablet" from "Walmart" (can't vouch for anything... just 
searched it on the net) [1].  Maybe sell it for less?  Or try $100 and 
see if we need to go lower?


But at $75 or $50, that's a nice thing to put on the frontpage of the 
site.  This will be amazing.  We can setup the infrastructure for 
selling devices, sending updates to people, etc.  We can empower 
deployment who need the hardware.


The "profit" can probably be invested in things we need.  Devel work?  
More capital for selling more devices (aka. things other than XO1)?  
Anyway, that is off topic... we can deal with that if the money 
actually eventuates.


But it is also great for our growth.  Not everybody installs OSes, but 
most people are familiar with the idea of buying a box of hardware.  Is 
$75 expensive?  In a school budget yes probably.  But there are 
defiantly some people who would be willing to spend it.


This is a very good use of the SL capital.

We obviously need to think about the risk.  If we spend $4000 on XOs, 
at the price of $75, we need to sell 50 (+more to cover postage costs) 
to make the money back.  Is that likely?  I would say yes... that is 
about 2 classes of students.


Of course, people will argue that it is not SL's job to get involved in 
selling hardware.  On the same token, nobody would say that is NOT SL's 
job to promote Sugar.  Selling a small batch of hardware is just a way 
of promoting our software.  This isn't OLPC scale, SL is not becoming 
an OEM... it is "Uncle Dave's Phone Repair Shop" scale.


Thanks,
Sam

[1]  
http://www.walmart.com/ip/RCA-Viking-Pro-10.1-2-in-1-Tablet-32GB-Quad-Core/45804384


On Mon, Jun 13, 2016 at 3:07 PM, Dave Crossland  wrote:

Hi

http://www.ebay.com/itm/Qty-172-OLPC-One-Laptop-Per-Child-XO-1-w-7-5-TFT-256MB-RAM-1024KB-ROM-/262478690514

I propose that Sugar Labs buy these, image them with the 0.110
release, and sale them to raise funds; individual units regularly
clear $100 each, so this will raise around $13,000

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

Re: [IAEP] [SLOBS] SL member list/joining criterion

[Sam Parkinson]

Didn't we all rebutt this proposal previously?  Do I need to state my 
objections again?


Basically; look at who doesn't requre membership donations:

   GNOME, Fedora, etc - Projects were most members contribute

Who even does membership donations?  I think somebody said the GNU 
Foundation, but it's a *Foundation*, and people probably just want to 
donate to RMS.  There are great people in the SL community, but I 
wouldn't say we have a person with an reputation like RMS.


Thanks,
Sam

On Tue, Jun 7, 2016 at 9:23 PM, Bert Freudenberg  
wrote:

On 16.05.2016, at 02:06, Dave Crossland  wrote:
  I suggest develop a 'super list' with as many possible members as 
possible, and then make persistent attempts to contact them until 
they pay a membership donation, ask for a membership bursary so they 
don't have to pay the fee personally, or tell us to go away :)


Where can I read more about the proposal to let only paying members 
vote? (I’m excited about the current energy in the community but 
can’t follow everything closely due to volume of emails)


- Bert -



___
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] "Windows Is Coming" (Dave Crossland)

[Sam Parkinson]

The idea of running Sugar on NaCl is a good idea in my opinion.

* The Chrome web store "apps" are downloaded in some form - which is 
good as even an NaCl sugar would probs be 500mb+
* It would make a good "gateway sugar" for people as it is easy to run 
on many platforms.
* I would think of it as a VM, but just super easy to install, and 
eaiser for us to maintain

* Can we actually just run it as a VM under NaCl?

Thanks,
Sam

On Sat, May 21, 2016 at 7:07 AM, Lionel Laské  
wrote:


2016-05-20 5:18 GMT+02:00 :


If we want to grow Sugar's userbase 10x, I think Sugar must run not 
only on

GNU but also Windows and Mac OS X.


Guess I don't need to say that it's exactly my though :-)
FYI, I've qualified Sugarizer on Windows 10.
I've tested it both on Windows 10 Desktop and on Windows 10 Mobile.

A preview video is available here [1].
If you're interested to test it, you could generate yourself the 
package from the Cordova command line using instructions here [2] 
(replace "android" by "windows").


It will be available on Windows Store in the next version.

   Lionel.

[1] 
https://www.facebook.com/lionel.olpcfrance/videos/1008345415887862/
[2] 
https://github.com/llaske/sugarizer#build-client-for-android-or-ios


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

Re: [IAEP] [Sugar-devel] [SLOBS] [SLOB] meeting reminder and some open issues to discuss

[Sam Parkinson]

I'm not a big fan of this idea.

The SLOBs already seem to have some capital.  But they seem to be 
scared to spend it.  How much arguing have we done over the translation 
co-ordinator position?  Something like a translation position would be 
great, but nobody has seemed to actually do anything to put in into 
action.


Meanwhile, Sugar continues to evolve.  Us volunteers write code, make 
releases, do user testing, etc.  This is not stuff that the SLOBs has 
helped with, not in a way that I am aware of at lest.


Is a membership fee for volunteers even something that any other Free 
Software orgs do?  GNOME doesn't seem to.


So my opinion is that the SLOBS should do something before seeking to 
raise additional funding, especially in this odd way.


Thanks,
Sam

On Thu, May 12, 2016 at 5:35 AM, Laura Vargas  
wrote:



2016-05-12 2:08 GMT+08:00 Dave Crossland :


On 11 May 2016 at 14:05, Laura Vargas  wrote:
there are ~US$65,000 available for planning/distributing among 
activities/teams/projects etc.


I think its essential that this be spent in ways that led directly 
to further income, to grow the project.


I agree that there is a need for income strategies as well. Still, 
the idea of annual budget is to plan the expenses so that the most 
areas of an organization can produce results in what they do.


It would be ideal to count with a somehow stable basic income, and 
therefore it would make sense to promote a motion for Lionel's idea 
of a yearly membership fee. Of course it would have to contemplate 
the exemptions of minors and members who actually don't have 
resources to pay.


Been more than 80 members, a yearly fee of US$100 with an estimated 
~50% of exemptions would put in SL general fund ~US$4.000 per year, 
probably enough for basic operations.



--
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] 2015 SocialHelp Survey?

[Sam Parkinson]

On Sun, Apr 24, 2016 at 5:17 AM, Dave Crossland <d...@lab6.com> wrote:

Hi Sam!

On 23 April 2016 at 00:45, Sam Parkinson <sam.parkins...@gmail.com> 
wrote:


I'm no longer afk.  I have collated the results into the attached 
spreedsheet.


Previously, I also wrote up an analysis of the results.  It is also 
attached.


Awesome!! I uploaded the files to the wiki and added them to the 
https://wiki.sugarlabs.org/go/Marketing_Team page


For me the Pain Points and Important Features sections were very 
interesting! Thanks for putting this together!! :D


You proposed 3 Major Takeaways:

Users do not understand the design patterns in Sugar. This was 
signalled through two methods. Firstly, users prioritised a tour or 
explanation as an important feature. Secondly, users expressed 
confusion with the interface and frame.


I agree, a tour would be a great activity. When I purchased a new 
XO-1 in 2007 and a new XO-4 this year, it came with a little printed 
leaflet with some basics; and I think there is an assumption that the 
UI is discoverable by kids if they have unrestricted free time to 
play and explore it. However I haven't seen any UX-study-style 
testing of this assumption.


You might be interested in this blog post that I wrote on the subject:  
https://www.sam.today/blog/sugar-onboard-user-testing.html


https://turtle.sugarlabs.org has a welcome tour. Can something like 
that be done with PyGTK3?


Developer and deployers have differing opinions compared to students 
and teachers; eg. reducing Journal clutter is significantly more 
popular with developers and deployers than with students and 
educators.


That's interesting! I wonder if students/educators work around 
journal clutter, or if they don't consider it to be cluttered at all. 
Which deployments can we ask about this?


The most important features to the Sugar community are Browse 
activity, the Journal and Turtle Blocks. These are closely followed 
by Write activity, Collaboration, the Terminal and the Sugar style 
design.


I see that none of these are in the top 20 on 
http://activities.sugarlabs.org/en-US/sugar/browse/type:1/cat:all?sort=popular


I can see how Browse is the most important activity for people who 
can be online to take the survey... for deployments without effective 
internet access, I wonder if that is still the case.


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

Re: [IAEP] Features wishlist from 2007

[Sam Parkinson]

I think that reducing the "interface prejudice" is an interesting 
question.  Changing the theme to use more gradients, transparency, 
shadows and stuff is very easy; we literally use the same toolkit that 
powers GNOME's interface.  The real question would be if we can test 
this feature; if anybody would be willing to do some usability testing 
in comparison of both.


I actually think that some features contribute to the interface issue.  
For example, we only allow 1 activity on the screen at the time.  Maybe 
if we add the ability to split the screen vertically, we could appear 
more mature.  It would also probably be useful for many users.  I might 
draw up a design, unless somebody beats me to it.


Thanks,
Sam

On Sat, Apr 23, 2016 at 9:49 AM, Dave Crossland  wrote:



On 22 April 2016 at 19:27, Sebastian Silva 
 wrote:


The UI described has some interesting features:

" Aqua sugar - the children's machine translated for adults"
Alex Van de Sande  - 2007

https://www.youtube.com/watch?v=RZnEtoYlRiE


Nice! Do you think any of these ideas should go on the sugar roadmap? 
:)
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep

Re: [IAEP] [Sugar-devel] triage meeting

[Sam Parkinson]

+1 to one less account
+1 to a nicer workflow
+1 to automatically keeping us updated by the github email bot
On Apr 19, 2014 10:03 AM, Daniel Narvaez dwnarv...@gmail.com wrote:

 Something is probably worth bringing up (it has been discussed a couple of
 times in irc)  is the possibility to migrate to github issues. Maintaining
 trac is becoming a bit of a burden, especially because of spam prevention.
 Someone (Bernie?) suggested we could keep bugs.sugarlabs.org around for a
 while but in read-only mode, rather than migrating. Interested in people
 thoughts, I have not fully considered the migration issue to be honest.


 On 9 April 2014 14:10, Walter Bender walter.ben...@gmail.com wrote:

 We plan to hold a triage meeting to clean up bugs.sugarlabs.org on
 Wednesday, 23 April, beginning at 9AM EST (14 UTC). We will be on
 irc.freenode.net #sugar-meeting all day. Please join the fun.

 --

 Tenemos la intención de celebrar una reunión de triage para limpiar
 bugs.sugarlabs.org el miércoles 23 de abril a partir de las 9 a.m. EST
 (14 UTC). Estaremos en irc.freenode.net #sugar-meeting todo el día.
 Por favor, únase a la diversión.


 regards.

 -walter

 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org
 ___
 Sugar-devel mailing list
 sugar-de...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




 --
 Daniel Narvaez

 ___
 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