Re: [Sugar-devel] sugar-build on f25

[Alex Perez]

Walter,


> On Nov 28, 2016, at 10:00 AM, Walter Bender  wrote:
> 
> I have a clean F25 where I am trying to build sugar. osbuild pull keeps 
> failing, as it seems no package xorg-x11-drv-vmmouse is available. Anyone 
> else experiencing this problem?
> 
That package no longer exists in Fedora 25. I suspect strongly osbuild would 
succeed if you simply remove the dependency. Have you tried gripping 
recursively for xorg-x11-drv-vmmouse and removing any occurrences of it?
> -walter
> 
> -- 
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [XSCE] Sugar 0.110 (Build 20) shows unexplained stoppage of io on removable drives

[Alex Perez]

Tony,

> On Jan 3, 2017, at 11:30 AM, Tony Anderson  wrote:
> 
> I have spent hours in the past few days coping with io failures while 
> installing rpms and copying large files from usb sticks. The problem has also 
> affects sd cards.

Which XO hardware version? 1? Which OLPC OS/kernel version? These are critical 
pieces of information which have not been included. Also, when you say “Sugar 
0.110” do you actually mean OLPC OS 13.2.8?
> 
> The symptom is that during an extended io operation, the usb stick generates 
> io errors. An 'ls' on the folder shows it to be empty. After a cd ../ and a 
> cd back to the folder, the ls shows the contents. This failure has been seen 
> on an sd card as well. It does not occur during flash so the firmware appears 
> unaffected. Since the io recovers, it is not a simple 'umount'.
> 
> My theory is that the problem is related to the power settings. The 
> gsettings: org.sugarlabs.power automatic claims the default to be false.
> However, in 0.110 it is set to true. One basis for the theory is that when 
> the script appears stalled, hitting the enter key seems to move it forward 
> (awaking the system?).
> 
> After resetting the value to false, access to usb devices appears more 
> reliable but there has been at least one script failure that may be due to 
> this problem.
> 
> Since the problem seems to be related to extended io operations when there is 
> no interactive use of the keyboard or trackpad, this could have devastating 
> consequences for use of an XO as a server.
> 
> Tony
> 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Code In: Having trouble setting up Dev Environment

[Alex Perez]

Santi,

> On Dec 20, 2016, at 11:04 AM, Santi Acq  wrote:
> 
> Hello everyone,
> Yesterday I claimed the Beginner task "Install the Sugar development 
> environment" in which I am supposed to followed this instructions 
> "https://developer.sugarlabs.org/dev-environment.md.html 
> ".
> The part I am having trouble with is after cloning the sugar-build repository 
> in my home directory, when I run: ./osbuild pull. I get a lot of errors and 
> messages there.
> (The message I get is here: https://paste.fedoraproject.org/510169/ 
> )
> I tried to search for a solution to this problem, and some people said It 
> could be the firewall, however after opening the git port (9418) nothing 
> changed, I am using Ubuntu 16.04 if that helps.

It looks like you are missing a Python module, which is provided by pip. It 
does not appear to be a git-related problem. Since the full name of the pip 
module is truncated/obfuscated in the log you put on the pastebin, it’s 
difficult to know exactly what the problem is, but my guess is that this pip 
module it is expecting to find is missing. Perhaps someone else here who is 
more familiar with osbuild can delve into exactly what/why that is.

OSError: Command /home/santiacq/sugar...nstall/bin/python2.7 -c "import sys, 
pip; sys...d\"] + sys.argv[1:]))" setuptools pip failed with error code 1

> Does anybody experienced this problem or know a possible solution?
> Thanks in advance,
> Santiago
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

[Alex Perez]

Tony/Walter,

> On Mar 13, 2017, at 7:28 PM, Walter Bender  wrote:
> 
> Tony,
> 
> Not sure I agree about your asserts regarding github vs gitroious.

Count me in here..
> 
> (1) the were/are many activities that were not hosted in gitorious long 
> before we switched to github, so it wasn't obvious where to find the source 
> repo *before* the switch. This is one of the reasons I started add the repo 
> path to the activity.info  file.
> (2) ALSO needs work and maintenance regardless of where the repos are hosted.

And it is incumbent upon Sugar Labs and the board to ensure that this happens, 
even if it requires you to spend actual money to make it happen.
> 
> -walter
> 
> On Mon, Mar 13, 2017 at 10:02 PM, Tony Anderson  > wrote:
> Hi James,
> 
> Your book is a wonder and should be much more actively promoted. It is one of 
> the major contributions of Sugar to constructive learning.
> 
> I believe the use of git.sugarlabs.org  and github 
> are major steps backwards from the original conception of Sugar activities as 
> something which users could develop and make available to the community.

Why do you believe this? It’s simply a convention for version control, one 
which millions of people understand, and does not preclude the use of the 
latter mechanism you describe. They are not mutually exclusive. Additionally, 
anyone can download a tarball/zip file of source code, or of a tagged release, 
from github, even if they have zero clue about how git works. Git is a 
convenience for *developers*

> In the first place, the activity bundle contains the source code that is 
> actually being executed. Second, there is a simple version system in 
> activity.info . The Developer Hub at 
> activities.sugarlabs.org  supplies an 
> adequate means to control maintenance activities (in the PR sense of having 
> someone monitor changes before releasing them for general use). 

We do definitely need to expand upon the filtering abilities, to prevent, say, 
an x86-only activity from being installed on ARM, and vice versa.
> 
> If one wanted to update an activity, say TuxMath, now the first step would be 
> to clone the repository not install the activity itself. 

This is an incorrect assumption. 
> 
> The ASLO site needs some work. Currently, the latest version is not 
> necessarily exposed (see Browse or TuxMath, for example). In some cases, 
> activities do not support Arm or use Hulahop and there is no way to specify 
> which versions of Sugar or its platforms are supported. The availability of 
> maintainers who know the PhP implementation of ASLO is apparently dwindling. 
> Perhaps Sugar Labs could undertake to re-implement ASLO using Python (Django, 
> flask, ...) or javascript to broaden the base of potential maintainers. 

> 
> However, dependence on github creates a duplicate repository for the source 
> code. With 400+ activities, there is no mechanism in github to make the 
> activities visible. Currently it may require searching 7 screens to find if 
> an activity is there (unlike ASLO which has an effective search capability). 

ASLO is not a source code repository. It’s a convenience to end users. I know 
you think they should be one and the same, and in theory they could be, but I 
don’t necessarily see the benefit.
> 
> I am sympathetic to the desire to acquaint our users with git and the concept 
> of version control. However, this approach limits the opportunity to those 
> who have internet access (probably a minority of our users). 

I don’t see a reason why ASLO couldn’t simply be a front-end, pointing to .xo 
activity files which are mirrored elsewhere (even HTTP-accessible via 
Git/GitHub, or via a global CDN). That said, there is some value in hosting the 
activities directly on ASLO. There is also some risk, since, if ASLO goes 
offline, so does access to all activities.

> A more effective approach would be to determine how git could be installed in 
> Sugar ( a git activity?) so that it can be used. Your book could then be used 
> as a basis for helping our users learn to develop activities using 
> version-control. In this way version control can be used locally by the 
> developer prior to submitting an updated or new activity to ASLO (which may 
> well involve a visit to an internet cafe). 

Git can absolutely be used locally (with branches, tags, etc) without external 
access to the Internet. It was designed to be use this way. That said, I don’t 
see why Git needs to be a sugar activity. It just needs to be a dependency of 
the development-specific Sugar packages (RPM/deb/etc)
> 
> Tony
> 
> Tony
> 
> 
> On 03/14/2017 03:39 AM, James Simmons wrote:
>> All,
>> 
>> I have been neglecting the manual Make Your Own Sugar Activities! ever since 
>> I first wrote it. However, I did manage to make one 

Re: [Sugar-devel] logo dicussion

[Alex Perez]

On this subject, I may have missed this, but where did the (IMHO awful) 
"feet" icon come from, who approved its use, and was the board involved 
with the decision? It seems a fairly central branding decision.



Walter Bender 
Wednesday, September 13, 2017 5:49 AM
Regarding https://github.com/sugarlabs/sugar-artwork/pull/96 it would 
be helpful to get Tony's feedback. Can you please contact him as our 
liaison to the SFC?


regards.

-walter

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

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] licensing question

[Alex Perez]

Folks,

These attitudes are totally unhelpful, and I urge you to drop it, stop 
hurling insults. To be honest, I think both of you have valid points, 
and for the time being, I am not a fan of shutting down the legacy ASLO, 
until we have data that it's _really_ not being used. Removing the link 
from the landing page of the next version of sugar is a different thing 
entirely, so let's not conflate them. The deployed base on XO machines 
is largely running very old versions of Sugar, and many of those 
activities likely work fine with those old versions of Sugar. This is 
something I do not think James is considering, but perhaps I'm wrong.


We have access logs for ASLO. We can easily determine how often, and 
which, activities are downloaded. I do not personally know which server.


What we may lack, metric-wise, is what the version of Sugar on the 
client machine is. Is this encoded into the user agent of the custom 
browser, by chance? I assume not, but it's worth asking the question.



Tony Anderson 
May 23, 2018 at 11:27 PM
James Cameron's devotion to alternate facts is what is amusing 
(actually sad). The only way Sugar users can access activities not 
already installed is by ASLO (unless we have some really carefully 
hidden source).


Tony




___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
James Cameron 
May 23, 2018 at 5:54 PM
Copyright on the source code of these activities is held by their
original authors, and not by Sugar Labs.

The ASLO process is a distribution of software by Sugar Labs, and the
licenses are in the source code bundles.  It makes no real difference
what was entered into ASLO as metadata, what matters is the copyright
and license declaration in the source code.

Up until last year, ASLO did not require a license.  A pending change
to ASLO had not been put into production.  Since that change, each new
upload to ASLO has had to have a license field added if there wasn't
one.  But again, this license field is only a summary, and has little
bearing.  What matters is the copyright and license in the source.

Whether Sugar Labs has received a letter or not is immaterial; but as
a distributor Sugar Labs need only check that the license is
acceptable before distributing.

One of the issues at hand is bundling of TurtleBlocksJS inside
Sugarizer.  Sugarizer does not use ASLO, so what ASLO did or does is
immaterial.

TurtleBlocksJS is AGPLv3+ in js/activity.js, has bundled source of
various other licenses, and has no license metadata in activity.info.

I agree that one solution is for the authors of TurtleBlocksJS to
relicense their work to one more compatible with Sugarizer's Apache
2.0 license.  Another is for Sugarizer to relicense.  Best would be a
path from AGPLv3+ to Apache 2.0; I've not found one yet.

Perhaps the new availability of Scratch on Sugarizer reduces the demand
for TurtleBlocksJS.

I certainly don't agree with Tony's suggestion there has been
arbitrary choice of license in GitHub repositories, and have acted and
will act to change any incorrect choice.

The other issue of porting from Python to JavaScript is creating a
derivative work, so the original license does apply.

If the source license is GPLv2 then ask the original copyright owner
to relicense as GPLv2+ or GPLv3+.  If they cannot be contacted, stop.

If the source license is GPLv2+, then anyone can relicense as GPLv3+,
though it is convenient to ask the original copyright owners to
agree.

If the source license is GPLv3+, then anyone can relicense as Apache
2.0.

For the keeping of good records, these relicensing actions should be
commits with the intent clearly stated in commit messages.

Tony's insistence on ASLO continues to amuse me.  Most distribution of
activities now happens through bundles, tarballs, and GitHub.  ASLO is
rarely used by distributors or indeed useful for anything except
personal searches for broken activities.  Tony's numbers make it
plain.  My own plan is to remove the link to "activities" in Browse
default page; plenty of disk space these days to include all working
activities in a build.

On Thu, May 24, 2018 at 08:02:30AM +0800, Tony Anderson wrote:

The bulk of the Sugar Activities were contributed through the ASLO process.
This process assumes that the contributor is the copyright-holder. The
contributor was asked to specify a license. Unfortunately that selection is not
displayed on ASLO. Therefore, it is likely that the license clause in the
activities in Github were arbitrarily chosen.

If SugarLabs has not received a letter from a lawyer in 10 years probably means
that there is no objection or that the copyright holder sees our use as fair
use.

If gplv3 is ok, it would seem that turtleblocks.js needs to change license to
gpl3 - something that Walter is fully authorized to do.

Tony

On Thursday, 24 May, 2018 07:46 

[Sugar-devel] [IAEP] [sugar-devel] Wiki Page created for all Sugar Labs 2018 Goal Submissions

[Alex Perez]

Sameer,

I've taken a first stab at Wiki-fying the user submissions from the 
Google Form, which were collected between February 13th and March 27th 
of this year.


Please see https://wiki.sugarlabs.org/go/Goals/2018_Submissions and as 
always, feel free to add/expound on the initial ideas, using the links 
to add details to each specific sub-page.


Regards,
Alex Perez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Suggestion on moving from IRC to Gitter

[Alex Perez]

As an oversight board member, for all the same reasons cited below, I am 
100% _not_ in favor of this proposal. It's a crude attempt at 
re-implementing IRC, and despite being open-source, is effectively a 
proprietary service, which there is no guarantee of continued support 
for. If you want to offer to maintain a Gitter-to-IRC bridge, that's 
great, otherwise I think this highly negative move.


I guess the real question I have, which doesn't seem to have been 
answered anywhere yet, is, why Gitter, specifically? There are other, 
much more option options, such as Matrix, which have far more mature IRC 
integration options.


James Cameron wrote on 1/20/19 4:16 PM:

Thanks Rahul.  Please add to the plan;

- critical people; identify the critical code maintainers and note
   when they have engaged with Gitter.im on a continuous basis; in
   particular we are yet to hear from Lionel and Ibiam.

- licensing; as an open source project within the Software Freedom
   Conservancy, we should aim to promote tools that have a compatible
   license.  Devin said the web app is licensed MIT, but the service is
   All Rights Reserved.

- inclusiveness of prior contributors; we have several contributors
   who know how to use IRC, but are disinclined due to their age to
   use the modern systems; how do we continue to include them?

- further division; every time we start something new, we divide again
   the group of people talking, and the new group often forgets to keep
   the old group informed; how will the non-Gitter.im contributors be
   kept informed?  I'm not asking about the IRC contributors, but also
   people using GitHub, Wiki, Trac, Jabber, Pootle, and the mailing
   lists.

- Code of Conduct; how to make this more obvious in Gitter.im?
   Especially "If you come across a post that is in an incorrect forum,
   please respectfully redirect the poster to the appropriate" (as has
   happened already), and making sure to consult others.

I've briefly authorised and looked at Gitter.im, using Firefox on
Ubuntu, and have observations;

1.  a significant increase in mail contact attempts by other projects
on GitHub; i.e. you'll get more spam, because people have coded things
to get to you through Gitter,

2.  a daily mail message containing some of the notifications from
Gitter, but not all,

3.  the display does not scroll with page down, page up, or arrow
keys, unless you first click in the message area,

4.  it isn't clear how I can make a local log of the discussion,

5.  the network demand is substantially greater than IRC; this is not
something we can expect to scale up into schools with poor networks,

6.  the power and processing demand is higher.



--
Sent from Postbox 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Install sucrose

[Alex Perez]

Tony,

Thanks. I have updated it with the two additional commands required, the 
first of which activates the universe repo, and, if it's already 
installs is a no-op:


https://github.com/sugarlabs/sugar/blob/master/docs/ubuntu.md


Tony Anderson <mailto:tony_ander...@usa.net>
December 10, 2018 at 9:35 AM
Hi, Alex

I used https://github.com/sugarlabs/sugar/blob/master/docs/ubuntu.md.

Tony


On 12/10/18 5:12 PM, Alex Perez wrote:


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Alex Perez <mailto:ape...@alexperez.com>
December 10, 2018 at 9:12 AM
Tony,

Can you cite the documentation you were using? Nowhere in this process 
is that cited, and without it, this one line command can't be added. 
Do you have a wiki account? If so, please feel free to add it to the 
appropriate page yourself, but it would also be helpful for you to 
actually cite the content you are referencing here.


Regards,
Alex Perez


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Tony Anderson <mailto:tony_ander...@usa.net>
December 10, 2018 at 8:48 AM
Hi, James

Alex Perez identified the problem correctly. I needed to run:

sudo apt-get update

before

sudo apt install sucrose

For me, the real concern is that someone attracted to try Sugar may be 
turned away be incomplete installation instructions.


Tony



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
James Cameron <mailto:qu...@laptop.org>
December 9, 2018 at 7:16 PM
Just now, tested Ubuntu 18.04 and 18.04.1 installation media by
installing Sugar.  The universe repository was already enabled, and
"sudo apt install sucrose" completed normally.  After restart, and
Sugar selected from login, everything worked fine.

There's no error "package not found".  When you try to install a
package that is not listed, you get "E: Unable to locate package
sucrose".

One scenario where "sudo apt install sucrose" may say "E: Unable to
locate package sucrose" is where the system does not have internet
access, or where access was not available during a critical period
after boot when the Ubuntu system automatically updates the package
list.  Missing network drivers is a common cause.  Nothing to do with
Sugar though, and we won't document all the foibles of Ubuntu.

Please do update the Debian Wiki if it is in error.  Not really our
responsibility here at Sugar Labs, so we rely on interested people to
do it.

On Mon, Dec 03, 2018 at 10:10:54AM +, Tony Anderson wrote:

Sadly, this is not the problem. The Universe repository was enabled.

wiki.debian.org/sugar/#Running the Sugar interface says Upcoming Debian 9
"Stretch" will include 0.110. (We are on 0.112).
Packages overiview for Debian Sugar Team says sugar: 0.110.0-3 as stable and
0.112.6 with 7 bugs and unstable. Naturally I don't know whether any of this
refers to 'sucrose' in Ubuntu 18.04 LTS.

Tony

On 12/1/18 6:12 PM, Alex Perez wrote:

 Tony,

 It sounds like you do not have the 'universe' apt repository enabled, since
 this is where the sucrose package lives, according to [1]https://
 packages.ubuntu.com/bionic/sucrose

 With Ubuntu 18.04, you should just be able to run "sudo add-apt-repository
 universe" and enable it.

 [2]Tony Anderson
 Friday, November 30, 2018 9:34 PM
 I am trying to install sugar on a Windows laptop.

 I was able to get 50gb unallocated space and installed ubuntu 18.04
 LTS.

 The command 'sudo apt install sucrose' returned package not found.

 Tony

 ___
 Sugar-devel mailing list
 [3]Sugar-devel@lists.sugarlabs.org
 [4]http://lists.sugarlabs.org/listinfo/sugar-devel

 ___
 Sugar-devel mailing list
 [5]Sugar-devel@lists.sugarlabs.org
 [6]http://lists.sugarlabs.org/listinfo/sugar-devel

References:

[1] https://packages.ubuntu.com/bionic/sucrose
[2] mailto:tony_ander...@usa.net
[3] mailto:Sugar-devel@lists.sugarlabs.org
[4] http://lists.sugarlabs.org/listinfo/sugar-devel
[5] mailto:Sugar-devel@lists.sugarlabs.org
[6] http://lists.sugarlabs.org/listinfo/sugar-devel



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel



Tony Anderson <mailto:tony_ander...@usa.net>
December 3, 2018 at 2:10 AM
Sadly, this is not the problem. The Universe repository was enabled.

wiki.debian.org/sugar/#Running the Sugar interface says Upcoming 
Debian 9 "Stretch" will include 0.110. (We ar

Re: [Sugar-devel] Install sucrose

[Alex Perez]

Tony,

Can you cite the documentation you were using? Nowhere in this process 
is that cited, and without it, this one line command can't be added. Do 
you have a wiki account? If so, please feel free to add it to the 
appropriate page yourself, but it would also be helpful for you to 
actually cite the content you are referencing here.


Regards,
Alex Perez


Tony Anderson <mailto:tony_ander...@usa.net>
December 10, 2018 at 8:48 AM
Hi, James

Alex Perez identified the problem correctly. I needed to run:

sudo apt-get update

before

sudo apt install sucrose

For me, the real concern is that someone attracted to try Sugar may be 
turned away be incomplete installation instructions.


Tony



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
James Cameron <mailto:qu...@laptop.org>
December 9, 2018 at 7:16 PM
Just now, tested Ubuntu 18.04 and 18.04.1 installation media by
installing Sugar.  The universe repository was already enabled, and
"sudo apt install sucrose" completed normally.  After restart, and
Sugar selected from login, everything worked fine.

There's no error "package not found".  When you try to install a
package that is not listed, you get "E: Unable to locate package
sucrose".

One scenario where "sudo apt install sucrose" may say "E: Unable to
locate package sucrose" is where the system does not have internet
access, or where access was not available during a critical period
after boot when the Ubuntu system automatically updates the package
list.  Missing network drivers is a common cause.  Nothing to do with
Sugar though, and we won't document all the foibles of Ubuntu.

Please do update the Debian Wiki if it is in error.  Not really our
responsibility here at Sugar Labs, so we rely on interested people to
do it.

On Mon, Dec 03, 2018 at 10:10:54AM +, Tony Anderson wrote:

Sadly, this is not the problem. The Universe repository was enabled.

wiki.debian.org/sugar/#Running the Sugar interface says Upcoming Debian 9
"Stretch" will include 0.110. (We are on 0.112).
Packages overiview for Debian Sugar Team says sugar: 0.110.0-3 as stable and
0.112.6 with 7 bugs and unstable. Naturally I don't know whether any of this
refers to 'sucrose' in Ubuntu 18.04 LTS.

Tony

On 12/1/18 6:12 PM, Alex Perez wrote:

 Tony,

 It sounds like you do not have the 'universe' apt repository enabled, since
 this is where the sucrose package lives, according to [1]https://
 packages.ubuntu.com/bionic/sucrose

 With Ubuntu 18.04, you should just be able to run "sudo add-apt-repository
 universe" and enable it.

 [2]Tony Anderson
 Friday, November 30, 2018 9:34 PM
 I am trying to install sugar on a Windows laptop.

 I was able to get 50gb unallocated space and installed ubuntu 18.04
 LTS.

 The command 'sudo apt install sucrose' returned package not found.

 Tony

 ___
 Sugar-devel mailing list
 [3]Sugar-devel@lists.sugarlabs.org
 [4]http://lists.sugarlabs.org/listinfo/sugar-devel

 ___
 Sugar-devel mailing list
 [5]Sugar-devel@lists.sugarlabs.org
 [6]http://lists.sugarlabs.org/listinfo/sugar-devel

References:

[1] https://packages.ubuntu.com/bionic/sucrose
[2] mailto:tony_ander...@usa.net
[3] mailto:Sugar-devel@lists.sugarlabs.org
[4] http://lists.sugarlabs.org/listinfo/sugar-devel
[5] mailto:Sugar-devel@lists.sugarlabs.org
[6] http://lists.sugarlabs.org/listinfo/sugar-devel



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel



Tony Anderson <mailto:tony_ander...@usa.net>
December 3, 2018 at 2:10 AM
Sadly, this is not the problem. The Universe repository was enabled.

wiki.debian.org/sugar/#Running the Sugar interface says Upcoming 
Debian 9 "Stretch" will include 0.110. (We are on 0.112).
Packages overiview for Debian Sugar Team says sugar: 0.110.0-3 as 
stable and 0.112.6 with 7 bugs and unstable. Naturally I don't know 
whether any of this refers to 'sucrose' in Ubuntu 18.04 LTS.


Tony

On 12/1/18 6:12 PM, Alex Perez wrote:


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Alex Perez <mailto:ape...@alexperez.com>
December 1, 2018 at 10:12 AM
Tony,

It sounds like you do not have the 'universe' apt repository enabled, 
since this is where the sucrose package lives, according to 
https://packages.ubuntu.com/bionic/sucrose


With Ubuntu 18.04, you should just be able to run "sudo 
add-apt-repository universe" and enable it.


___

Re: [Sugar-devel] Sugar Labs 2018-2020 Oversight Board Election Results

[Alex Perez]

Agreed, the voter turnout of just under 26% is highly unfortunate, and I 
personally think it would be worth sending a questionnaire to the 124 
members we know did not submit a vote, but were "registered" to do so, 
asking a question or two about why they chose not to vote. Was it a 
matter of not knowing about the candidates, or no longer caring about 
Sugar, etc?




Ifeanyi Peter <mailto:ifeanyipete...@yahoo.com>
December 17, 2018 at 5:29 AM
Congratulations to the new Oversight Board Members.


The ballot is kinda poor, not even up to 50% members voted.

Thanks to the electoral committee for an awesome job

- Ifeanyi Ekperi
Designer, WP Expert

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Samson Goddy <mailto:samsongo...@gmail.com>
December 15, 2018 at 3:01 AM
Hello,

43 out of 167 Sugar Labs member voted during the Sugar Labs 2018-2020 
Election.


Congratulations to the winners who have been selected for the 
2018-2020 period:


1. *Walter Bender*
2. *James Cameron*
3. *Lionel Laské*
*4. Alex Perez *
*5. Devin Ulibarri*
*
*
Results are available at the following URL:

https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_7e20f77cd6595bfe=dd2850a107103a39 
<https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_7e20f77cd6595bfe=dd2850a107103a39>


For more information about the Condorcet Internet Voting Service, see
http://civs.cs.cornell.edu <http://civs.cs.cornell.edu/>

Many thanks to Ibiam Chihurumnaya, Rahul Bothra,Jaskirat Singh, Anmol 
Mishra, and Amaan Iqbal for their candidacies submissions and for 
their interest to be part of the Sugar Labs Oversight Board.


Many thanks to everyone in the Membership and Elections Committee, for 
all their efforts and time dedicated to maintaining the Sugar Labs 
member's list.


Many thanks to the Wiki and Systems teams for their ongoing support.



*Membership and Elections Committee*
Project Sugar Labs


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


--
Sent from Postbox 
<https://www.postbox-inc.com/?utm_source=email_medium=siglink_campaign=reach>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Install sucrose

[Alex Perez]

This is the kind of thing that's really easy to overlook, especially if 
you already have the universe repo enabled on the machine, when whomever 
wrote the documentation wrote it. Chances are, the original author did 
test it, but only within their environment.



Tony Anderson <mailto:tony_ander...@usa.net>
December 1, 2018 at 9:00 PM
Hi Alex,

Thanks, I'll give that a try.

I had suspected that the instructions on the Sugar wiki were not 
complete. We spent time changing the markup to gitHub but apparently 
not time testing the instructions.


Tony


On 12/1/18 6:12 PM, Alex Perez wrote:


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Alex Perez <mailto:ape...@alexperez.com>
December 1, 2018 at 10:12 AM
Tony,

It sounds like you do not have the 'universe' apt repository enabled, 
since this is where the sucrose package lives, according to 
https://packages.ubuntu.com/bionic/sucrose


With Ubuntu 18.04, you should just be able to run "sudo 
add-apt-repository universe" and enable it.


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


--
Sent from Postbox 
<https://www.postbox-inc.com/?utm_source=email_medium=siglink_campaign=reach>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Systems] Tidying up; images from 2010 to 2012

[Alex Perez]

Assuming there _was_ a resistance factor is probably not a good idea :) 
I'm not really sure why it matters, even if there was one, either.



Anmol Mishra 
December 8, 2018 at 6:15 AM
I would like to ask If these images are from 2010-2012, why weren't 
they deleted earlier?
I'm asking this to get the resistance factors that were imposed 
earlier on deletion in maybe 2016-current.


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
James Cameron 
December 7, 2018 at 9:02 PM
Yes.

Harms are misdirection of users and filesystem size.

Further subdividing;

- on the misdirection, the images have bugs that have been fixed, such
as since mitigated zero-day vulnerabilities.

- on the size, they increased time cost of backups or filesystem
maintenance on the servers.

What are the gains in keeping these files?

Dave Crossland 
December 7, 2018 at 6:53 PM
I don't see the harm in leaving old stuff lying around if the disk has 
plenty of room. Surely there's more important things to do  :)

___
Systems mailing list
syst...@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/systems
James Cameron 
December 7, 2018 at 6:51 PM
61%

Dave Crossland 
December 7, 2018 at 6:39 PM
What % of the server disk space is used?
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


--
Sent from Postbox 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Install sucrose

[Alex Perez]

Tony,

It sounds like you do not have the 'universe' apt repository enabled, 
since this is where the sucrose package lives, according to 
https://packages.ubuntu.com/bionic/sucrose


With Ubuntu 18.04, you should just be able to run "sudo 
add-apt-repository universe" and enable it.

Tony Anderson 
Friday, November 30, 2018 9:34 PM
I am trying to install sugar on a Windows laptop.

I was able to get 50gb unallocated space and installed ubuntu 18.04 LTS.

The command 'sudo apt install sucrose' returned package not found.

Tony

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [IAEP] Announcement of the candidacy of Alex Perez (was: Stage II November: Election)

[Alex Perez]

I hereby announce my candidacy. Please ask any questions you may have, 
and read more at 
https://wiki.sugarlabs.org/go/Oversight_Board/2018-2020-candidates/Alex_Perez



Samson Goddy 
November 19, 2018 at 7:24 AM
Greetings,

Sugar Lab's Elections and Membership Committee announces t**he 
upcoming *2018-2020 Sugar Labs Oversight Board Election 
. **


F***our (4) Oversight Board members shall be elected for the Sugar 
Labs Oversight Board project for the 2018-2020 period*.*



**

*This is the first _call for candidates_: **

*The mission of the oversight board is to ensure that the Sugar Labs 
community has clarity of purpose and the means to collaborate in 
achieving its goals.

***
Members  can run for 
election to the Oversight Board 
 and vote in the 
elections for the Oversight Board.


Once e*lected, board members are expected to participate actively on 
Sugar Labs decision making processes and join Sugar-meeting IRC 
channel for SLOB's monthly meetings.



*
Stage II November 19, Reminder of the election date and second call 
for candidates. (Today)

*

--

Samson Goddy

Twitter: https://twitter.com/samson_goddy
Email: samsongo...@sugarlabs.org 
samsongo...@gmail.com 

Website: https://samsongoddy.me/ 


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


--
Sent from Postbox 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [IAEP] Announcement of the candicacy of Lionel Laské for SLOB

[Alex Perez]

Lionel,

Thank you for stepping forward. I encourage others to ask questions of 
you as well. I have a few:


Are you willing to state that you will make your best effort to attend 
all SLOB meetings? There is no statement to this effect on your 
candidacy page, and as you are no doubt aware, I have called out a 
number of current SLOB members out regarding their extremely poor 
attendance.


Also, on your candidacy page, you state "We are an open source 
community. It should be asserted on our webpage and we must choose tools 
compatible with that philosophy. It's not acceptable for example that 
today the SugarLabs webpage include multiple tracking tools."


Can you be more specific about what sort of tracking tools you believe 
are problematic? I personally agree that the Sugar Labs website needs to 
do a better job explaining what the project is, and that it is an open 
source project (these words to not appear anywhere on the Sugar Labs 
landing page).


Regards,
Alex Perez


Lionel Laské <mailto:lionel.la...@gmail.com>
November 27, 2018 at 9:02 AM
Hi all,

I'm proud to be candidate for the SugarLabs Oversight Board election.

Find more about my candidacy here: 
https://wiki.sugarlabs.org/go/Oversight_Board/2018-2020-candidates/Lionel_Lask%C3%A9


Best regards from France.

Lionel.


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


--
Sent from Postbox 
<https://www.postbox-inc.com/?utm_source=email_medium=siglink_campaign=reach>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sl.org Down?

[Alex Perez]

Not just you. It is down, and we are having a problem with this 
particular host. I am working on resolving it today.


Samson Goddy wrote on 1/26/19 2:47 AM:

Hello,

Is it just me or is https://www.sugarlabs.org down?


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


--
Sent from Postbox 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] SpellCheck for write activity project

[Alex Perez]

Jake,

I would personally like to encourage you to not re-implement the wheel. 
Aspell has been around for a long time, quite possibly longer than 
you've been alive, and has python bindings, and a C API:


See
https://pypi.org/project/aspell-python-py3/
and
https://github.com/WojciechMula/aspell-python


Jake Scarlet wrote on 4/4/19 7:36 AM:
Would it be preferable if I used  an existing library for the 
spellcheck feature or if I created one by myself

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [IAEP] What's the long term vision of Sugar Labs?

[Alex Perez]

Sumit,

Great questions, and they're particularly relevant at this phase/age of 
the existence of Sugar Labs. They certainly can't be answered in a 
single e-mail, however I think this is a perfect conversation to have, 
particularly on our IAEP mailing list, which is our general purpose 
mailing list.


Sumit Srivastava wrote on 3/28/19 5:00 PM:
Do we aim to be like Red Hat? Canonical? No match? Who are we closest 
to? Who do we aim to be?


Speaking as an Oversight Board member, I do not believe it is in the 
interest of Sugar Labs to attempt to emulate a company like Red Hat and 
Canonical. These companies have hundreds/thousands of paid employees, 
and their organizational structure is a product of the needs of their 
corporate customers.


Right now, we have a few existential problems on the horizon, one of 
which is a long term problem, but which we now need to address in the 
short-term: Maintainability. Sugar has a lot of "technical debt", and 
unless we can complete our goal of 100% Python 3 compatibility of all 
core Sugar libraries and the toolkit, we risk the loss of being able to 
be run as a desktop environment on current versions of Linux, due to our 
reliance on Python 2. Since Python 2 has been on life support for many, 
many years, and is only nine months from being officially retired, it 
will no longer be maintained by the Python Foundation, nor included by 
default in the next versions of Fedora and Ubuntu. You can read further 
details about the sunsetting of Python 2 at https://pythonclock.org 






I understand that these are a lot of questions. You can also share 
relevant mail archive links if they're available.


I also understand that we're a non profit and the organisations I 
mentioned might not be a close match.
I personally do not think the core entity of Sugar Labs should be a 
commercial entity, but non-profit organizations are completely entitled 
to be profitable, and many are quite  for the profitable. Personally, I 
would like to see the development of a federated model, where we have 
country/regionally-centered "chapters" of Sugar Labs, with Sugar Labs 
itself taking the in-the-field feedback from our distributed user base, 
and incorporating and triaging suggestions/feedback,


Essense of my question: If we could achieve anything, what would we want?
I would love to see a world where Sugar was used extensively, worldwide, 
by children in the primary school age range, with a wide range of 
actively-maintained activities, relevant to the current curricula of a 
variety of countries, and of interest to elementary school teachers, 
across all socioeconomic groups. How we get there is the real question, 
assuming we want to, and have the organizational will to do so.


As for what our "long term vision" is, I honestly don't think we have 
one at this point, and we should fix that, which is one of the reasons 
why I chose to run for the Sugar Labs Oversight Board. Our next meeting 
is next Friday, on 2019-04-05 at 20:00 UTC, on IRC, in the 
#sugar-meeting channel on FreeNode. Feel free to join us and observe, as 
well as ask questions before and after the official meeting commences.


https://wiki.sugarlabs.org/go/Oversight_Board


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


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] How to add activities to Sugarizer on Android

[Alex Perez]

Evert,

Evert Groenewald wrote on 3/3/19 11:06 PM:

Hallo List

I have installed Sugarizer from F-Droid to my phone and would like to
know how to go about adding additional activities. I would like to add a
chess activity for instance. On the OLPC it is easy to add activities.
Actually, it's not just on the OLPC side...it's just as easy to do this 
with The Fedora-based Sugar on a Stick installations of Sugar, which is 
available for armhfp (Pi3+), i386 and x86_64. Of course, it's not 
Android, but the OLPC is far from the only way to make use of the Sugar 
environment.

Here it is not that obvious. I have read some of the informantion in the
wiki and searched in the archives of the mailing lists, but I am still
not clear on whats steps to take to accomplish adding additional
activities on android.

Thanks in advance.

Evert


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Fwd: [GSoC Mentors] Announcing Season of Docs 2019

[Alex Perez]

Which, by the way, says "Sugar 0.106 documentation 
<https://help.sugarlabs.org/en/#>" at the top of the page. How do we fix 
that?


James Cameron wrote on 3/11/19 6:45 PM:

We have https://help.sugarlabs.org/

Please raise issues here;
https://github.com/godiard/help-activity

On Mon, Mar 11, 2019 at 04:01:07PM -0700, Alex Perez wrote:

I saw this as well, and thought the same thing. We should definitely try to
develop some better user-facing documentation, for those _new_ to Sugar.

Walter Bender wrote on 3/11/19 3:43 PM:

 Could be quite useful.

 -- Forwarded message -
 From: 'sttaylor' via Google Summer of Code Mentors List <[1]
 google-summer-of-code-mentors-l...@googlegroups.com>
 Date: Mon, Mar 11, 2019 at 6:32 PM
 Subject: [GSoC Mentors] Announcing Season of Docs 2019
 To: Google Summer of Code Mentors List <[2]
 google-summer-of-code-mentors-l...@googlegroups.com>

 We’re delighted to announce the inaugural year of Season of Docs, a Google
 program that fosters collaboration between open source projects and
 technical writers. Season of Docs is similar to Summer of Code, but with a
 focus on open source documentation and technical writers. Details are on
 our website: [3]g.co/seasonofdocs.

 Would you like to take part as an open source mentor in the inaugural year
 of Season of Docs? Open source organizations can start thinking now about
 the projects you’d like a technical writer to work on. Take a look at the
 [4]examples of project ideas. Reach out to your community members to see
 who’d like to be a mentor for Season of Docs. As a mentor, you don’t need
 technical writing skills. Instead, you're a member of the open source
 organization who knows the value of good documentation and who is
 experienced in open source processes and tools. See the guidelines on [5]
 working with a technical writer. Organization applications open on April 2,
 2019. See the full [6]timeline on the Season of Docs website.

 From April 30, Technical writers can explore the list of participating open
 source organizations and their project ideas. Technical writers bring their
 skills in designing and developing documentation to the open source
 organization. Technical writer applications open on April 30. The list of
 accepted technical writing projects is announced on July 30.

 Please do tweet and blog about Season of Docs if you’d like to share the
 news. We want as many people to know about it as possible. We’ve provided
 logos that you can download and some example content on the [7]press page.

 We’re looking forward to an exciting pilot of the Season of Docs program!

 If you have any questions about the program, please email us at [8]
 season-of-docs-supp...@googlegroups.com.

 Best regards

 Sarah Maddox, Andrew Chen and the Season of Docs team

 --
 You received this message because you are subscribed to the Google Groups
 "Google Summer of Code Mentors List" group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to [9]google-summer-of-code-mentors-list+unsubscr...@googlegroups.com
 .
 To post to this group, send email to [10]
 google-summer-of-code-mentors-l...@googlegroups.com.
 Visit this group at [11]https://groups.google.com/group/
 google-summer-of-code-mentors-list.
 To view this discussion on the web visit [12]https://groups.google.com/d/
 msgid/google-summer-of-code-mentors-list/
 563595bc-e36d-411e-9868-71a5f75742a4%40googlegroups.com.
 For more options, visit [13]https://groups.google.com/d/optout.

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

 ___
 Sugar-devel mailing list
 [15]Sugar-devel@lists.sugarlabs.org
 [16]http://lists.sugarlabs.org/listinfo/sugar-devel

--
Sent from [17]Postbox

References:

[1] mailto:google-summer-of-code-mentors-l...@googlegroups.com
[2] mailto:google-summer-of-code-mentors-l...@googlegroups.com
[3] https://developers.google.com/season-of-docs/
[4] https://developers.google.com/season-of-docs/docs/project-ideas
[5] https://developers.google.com/season-of-docs/docs/tech-writer-collaboration
[6] https://developers.google.com/season-of-docs/docs/timeline
[7] https://developers.google.com/season-of-docs/docs/press
[8] mailto:season-of-docs-supp...@googlegroups.com
[9] mailto:google-summer-of-code-mentors-list+unsubscr...@googlegroups.com
[10] mailto:google-summer-of-code-mentors-l...@googlegroups.com
[11] https://groups.google.com/group/google-summer-of-code-mentors-list
[12] 
https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/563595bc-e36d-411e-9868-71a5f75742a4%40googlegroups.com?utm_medium=email_source=footer
[13] https://groups.google.com/d/optout
[14] http://www.

Re: [Sugar-devel] Collaboration Between Activities Fail with Fedora 29 SoaS

[Alex Perez]

Samson,

Based on my previous conversations with you, you had indicated you were 
using Fedora 29 32-bit SoaS. Please confirm that this is still the case. 
I have changed the subject line to reflect this.


I believe you are encountering the issue which we thought we had fixed 
with a previous patch (see https://github.com/sugarlabs/sugar/issues/814 
). This patch is now upstream in F29, but _only_ if you use the updated 
32-bit SoaS image, which is not yet generally available. Even with the 
fix in place, collaboration still fails with the same message.


After starting Sugar, open the Terminal, and type 'grep key 
~/.sugar/default/logs/shell.log' If you see a message which says "ERROR 
root: Error parsing public key" then you are running into a bug that has 
been present in the last several versions of Fedora, and completely 
breaks collaboration. The underlying problem is still not fully 
understood, however we know it's related to SSH keys.


Additionally, for collaboration to function, you must also make sure 
that your Ethernet interfaces have IP addresses (self-assigned is fine), 
and that there is a default route set on each computer that is 
attempting to collaborate. You can check this from the terminal with "ip 
route", and if there is no line that starts with "default" or no output 
at all, then there is no default route set, and collaboration will not work.


Here is an example of the output of shell.log which shows the error: 
http://alexperez.com/xo1/VirtualBox_Fedora29-soas-shell.log.png



Samson Goddy wrote on 3/13/19 7:09 AM:

Hi Everyone,

We've been working on installing SOAS on some computers in a school 
and we were testing collaboration using CAT5 cables connected to a router
and also connected to the two computers running the SOAS instances, 
the both instances are seen on the two computers but after joining an 
activity

the "Joining activity" alert and collaboration doesn't happen.

Logs here .

--

Samson Goddy

Twitter: https://twitter.com/samson_goddy
Email: samsongo...@sugarlabs.org 
samsongo...@gmail.com 

Website: https://samsongoddy.me/ 


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


--
Sent from Postbox 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] IRC Channel

[Alex Perez]

Ahmed,

Generally speaking, there is no fixed time. While I would encourage 
anyone who wanted to to "idle" on IRC (keep it in the background logged 
in, assuming you have reliable and inexpensive enough connectivity), we 
see _so many_ people log in for five, ten, or fifteen minutes, ask a 
single question, and then disappear. This is not helpful behavior, nor 
is it conducive to getting responses.


Remember, we are all globally distributed. IRC is not a replacement for 
e-mail lists. Please do not treat it as such.


Regards,
Alex Perez
Sugar Labs Oversight Board Member

Sumit Srivastava wrote on 3/11/19 5:12 AM:
If it's a question, mostly you'll get a reply within minutes on sugar 
devel.


Welcome to Sugar Labs! :)

On Mon, 11 Mar 2019, 5:36 pm Ahmed Khaled, <mailto:akhah...@outlook.com>> wrote:


Hey dudes and girls, I was wondering if there's a fixed time where
you guys are online on the IRC channel since I've been lurking for
a week now and haven't found any activity!

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
<mailto:Sugar-devel@lists.sugarlabs.org>
http://lists.sugarlabs.org/listinfo/sugar-devel

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


--
Sent from Postbox 
<https://www.postbox-inc.com/?utm_source=email_medium=siglink_campaign=reach>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [RELEASE] Sugar 0.113 unstable

[Alex Perez]

James,

Apologies for the thread hijacking, but I feel it's appropriate...

FYI, I have just discovered that collaboration in Sugar under 0.112 + 
Ubuntu 19.04 is also broken. We must get this fixed before we can 
release the stable 0.114.


See https://termbin.com/qtkh

James Cameron wrote on 3/15/2019 7:51 PM:

Sorry, I don't know.  I've not done that.  So many things would go
wrong.  You ought to wait for Fedora project to package Sugar 0.113.

I'm testing on Ubuntu18.04  at the moment, and it seems okay after
fixing those two errata in my previous post to this thread.


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SLOBS] GCI'18 Report

[Alex Perez]

Yes, thank you sincerely for this report...my thoughts/responses are 
inline...


Chihurumnaya Ibiam wrote on 1/31/19 6:38 AM:

Hi Everyone,

This is a report about last year's GCI.

674 students participated. Of those, 245 completed at least one task.
This works out to just over 36% of the "participants" actually 
participating in a substantive way.
The most popular task completed by students was our beginner task: 
"Make a Pull Request", which was completed by 100 students.

Or, approximately 15% of 674.

60 students completed the "Install the Sugar Environment" task.

Under 9%


• Briefly what was merged; that is, the work that has become part of
  the Sugar Labs software.

We have about 91 PRs that were merged,
Is there a list of the Pull Requests listed below? I'd like to 
personally examine how many of them are substantive.


Sugar/Activities = 20
Sugarizer = 20
MusicBlocks = 38
TurtleBlocks = 2
Sugar Social = 6
Sugar Website = 5


The event was fun and I enjoyed every bit of it.

• How we might improve next year.

It may seem like conventional wisdom that some of our mentors lacked 
knowledge about some tasks or weren't contributors to Sugar Labs but 
every mentor had previously contributed to Sugar Labs in one way or 
another.


It'll be great if the tasks we want are agreed upon as an org, as this 
gives a definite direction and narrows down the type of tasks we have.


Although it seems as if we got little if any help from the  community 
in generating task ideas. It was all on the shoulders of just a few of 
us. That needs to improve.

What would be the ideal way to improve this, from your perspective?
And I think we had too many open-ended design tasks -- we should pare 
back that somewhat next year, but not eliminate them. (They are 
required by Google, for one thing.) Maybe structure them such that a 
student can only do 1 or 2 simple design tasks by marking them as 
beginner tasks (although I think that was the case for the most part 
this year too.)


--
Ibiam Chihurumnaya
ibiamchihurumn...@sugarlabs.org 


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Sugar Labs presence at PyCon (was: Re: Sugar-devel Digest, Vol 126, Issue 52)

[Alex Perez]

Sugar Labs already has plans to have a presence at this years PyCon, 
which is April 30th through May 10th in Cleveland, Ohio, USA.


I will be there personally, in my capacity as Oversight Board member, as 
will Samson Goddy. Ibiam had hoped to attend but had difficulty with his 
visa application, and eventually decided to cease pursuing the matter 
further.


Suggesting we be present there seems to indicate that some of the member 
base is simply unaware of ongoing plans and activities.


I would encourage members to read the minutes of previous meetings at 
https://wiki.sugarlabs.org/go/Oversight_Board/Minutes


and specifically 
http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-03-01


Information on when and where (via IRC) the meetings are held are 
available at https://wiki.sugarlabs.org/go/Oversight_Board


Any member of the community is welcome to join and observe the meeting, 
as well as ask questions before and after.


Regards,
Alex Perez

paul hunter wrote on 4/13/19 11:20 AM:

In my opinion, representing Sugar at PyCon would be a great idea.
I really would like to get my hands on any archive if available


On Sat, Apr 13, 2019 at 9:30 PM 
<mailto:sugar-devel-requ...@lists.sugarlabs.org>> wrote:


Send Sugar-devel mailing list submissions to
sugar-devel@lists.sugarlabs.org
<mailto:sugar-devel@lists.sugarlabs.org>

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

You can reach the person managing the list at
sugar-devel-ow...@lists.sugarlabs.org
<mailto:sugar-devel-ow...@lists.sugarlabs.org>

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


Today's Topics:

   1. Sugar Outreach Plans 2019 - PyCon Cleveland (Vipul Gupta)
   2. Re: Sugar Outreach Plans 2019 - PyCon Cleveland (Jaskirat Singh)
   3. Re: Sugar Outreach Plans 2019 - PyCon Cleveland (Vipul Gupta)


--

Message: 1
Date: Sat, 13 Apr 2019 10:30:35 +0530
From: Vipul Gupta mailto:vipulgupta2...@gmail.com>>
To: sugar-devel mailto:sugar-devel@lists.sugarlabs.org>>
Subject: [Sugar-devel] Sugar Outreach Plans 2019 - PyCon Cleveland
Message-ID:
       
mailto:mx2kokva_v3dauo...@mail.gmail.com>>
Content-Type: text/plain; charset="utf-8"

Hello folks,
At the end of 2018, we started the Outreach works for Sugar Labs.
At first,
we thought of sharing several accomplishments throughout Google
Code-In to
keep the people in the loop on various social media platforms, as
well as
sharing experiences of Google Summer of Code students and their
projects
held in 2018 for a positive impact.

We thought we can go bigger and with that thought in mind
represent Sugar
Labs on larger platforms in front of communities. I proposed PyCon
to be a
great choice for the same. Considering OLPC represented XO laptops
being
part of PyCon 2008 (An article by Tony
<http://www.olpcnews.com/use_cases/technology/pycon_2008_and_olpc.html>)
Hence, we submitted a proposal for talks about Sugar Labs in the
Education
Summit of PyCon Cleveland 2019, and I am very happy to inform that
we have
in fact been selected. It's a great accomplishment for us all.

Samson would be representing our community at PyCon Cleveland. I,
unfortunately, due to my university exams won't be able to go. As
much as I
loved drafting the proposal with Samson and be would like to meet
and talk
about Sugar Labs, I am happy that Samson has a chance to be at
PyCon and
will do great. We are still raw in your efforts and have lots to
improve.
Would love to have more suggestions on things we should be doing,
and also
planning to hold workshops regarding Sugar in many countries in
the near
future.

Thanks,

Cordially,
Vipul Gupta
Mixster <https://mixstersite.wordpress.com/> | Github
<https://github.com/vipulgupta2048>
-- next part --
An HTML attachment was scrubbed...
URL:

<http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190413/f2a200cc/attachment-0001.html>

--

Message: 2
Date: Sat, 13 Apr 2019 10:46:31 +0530
From: Jaskirat Singh mailto:juskirat2...@gmail.com>>
To: Vipul Gupta mailto:vipulgupta2...@gmail.com>>
Cc: sugar-devel mailto:sugar-devel@lists.sugarlabs.org>>
Subject: Re: [Sugar-devel] Sugar Outreach Plans 2019 - PyCon Cleveland
Message-ID:
       
mailto:cao3su

Re: [Sugar-devel] Fwd: [GSoC Mentors] Announcing Season of Docs 2019

[Alex Perez]

I saw this as well, and thought the same thing. We should definitely try 
to develop some better user-facing documentation, for those _new_ to Sugar.


Walter Bender wrote on 3/11/19 3:43 PM:

Could be quite useful.

-- Forwarded message -
From: *'sttaylor' via Google Summer of Code Mentors List* 
>

Date: Mon, Mar 11, 2019 at 6:32 PM
Subject: [GSoC Mentors] Announcing Season of Docs 2019
To: Google Summer of Code Mentors List 
>



We’re delighted to announce the inaugural year of Season of Docs, a 
Google program that fosters collaboration between open source projects 
and technical writers. Season of Docs is similar to Summer of Code, 
but with a focus on open source documentation and technical writers. 
Details are on our website: g.co/seasonofdocs 
.



Would you like to take part as an open source mentor in the inaugural 
year of Season of Docs? Open source organizations can start thinking 
now about the projects you’d like a technical writer to work on. Take 
a look at the examples of project ideas 
. 
Reach out to your community members to see who’d like to be a mentor 
for Season of Docs. As a mentor, you don’t need technical writing 
skills. Instead, you're a member of the open source organization who 
knows the value of good documentation and who is experienced in open 
source processes and tools. See the guidelines on working with a 
technical writer 
. 
Organization applications open on April 2, 2019. See the full timeline 
on the 
Season of Docs website.



From April 30, Technical writers can explore the list of participating 
open source organizations and their project ideas. Technical writers 
bring their skills in designing and developing documentation to the 
open source organization. Technical writer applications open on April 
30. The list of accepted technical writing projects is announced on 
July 30.



Please do tweet and blog about Season of Docs if you’d like to share 
the news. We want as many people to know about it as possible. We’ve 
provided logos that you can download and some example content on the 
press page .



We’re looking forward to an exciting pilot of the Season of Docs program!


If you have any questions about the program, please email us at 
season-of-docs-supp...@googlegroups.com 
.



Best regards

Sarah Maddox, Andrew Chen and the Season of Docs team

--
You received this message because you are subscribed to the Google 
Groups "Google Summer of Code Mentors List" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to 
google-summer-of-code-mentors-list+unsubscr...@googlegroups.com 
.
To post to this group, send email to 
google-summer-of-code-mentors-l...@googlegroups.com 
.
Visit this group at 
https://groups.google.com/group/google-summer-of-code-mentors-list.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/563595bc-e36d-411e-9868-71a5f75742a4%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


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

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


--
Sent from Postbox 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar on Debian 10 (Buster)?

[Alex Perez]

Jeff,

Most, if not all, of the Sugar-specific bugs that are present in Debian 
should be fixed if you use the "0.112-3" (the 3 is critically important) 
Debian packages from the _unstable_ Debian repo. They have not yet been 
promoted to testing, and will likely not be included in Debian 10 when 
it is released, as it is late in the package freeze process.


So, you have a few options here...the easiest thing to do would be to 
run an entire "unstable" install of Debian, since you will get these 
packages by default, but otherwise, you have to configure Apt with the 
unstable repo, and then use package pinning. This is documented at 
https://serverfault.com/questions/371383/install-whitelist-of-packages-using-unstable-in-debian.


See https://packages.debian.org/buster/sucrose for a list of these 
packages, and https://wiki.debian.org/DebianUnstable#Installation can 
explain how to enable the unstable apt repo on a stable or testing install.


This may also be of use 
https://serverfault.com/questions/22414/how-can-i-run-debian-stable-but-install-some-packages-from-testing



Jeff Elkner wrote on 5/15/19 9:54 AM:

Great to meet you (virtually), Alex and James.  I'm a high school /
community college teacher in Arlington, Virginia who was an early
member of the OLPC community here in the DC area.  I run Debian in my
classroom and would very much be interested in using the Sugar desktop
to work on that platform.  It doesn't currently seem to work.  I don't
have the capacity to fix it myself, but I can provide reliable testing
and feedback in an educational setting should that be of use to you.
I'm hoping to rejoin the Sugar community once it is in a state where
it can be used both in my classroom and on Raspberry Pi's.

Thanks!
Jeff Elkner
Arlington Career Center
Arlington, VA

On Wed, May 15, 2019 at 12:39 PM Samson Goddy  wrote:

Hello Alex and James,

I guess you both miss this thread. Can you please guide Jeff on how to get 
started?



On Fri, May 10, 2019, 8:14 AM Jeff Elkner  wrote:

Dear Sugar Labs Devs,

I am a high school / community college computer science teacher in
Arlington Virginia who was an active member of the OLPC project for
years and who would like to rejoin the community.

I am convinced being able to run the Sugar desktop on the same
underlying OS (Debian) as Raspbian uses is the key to that working for
me.

I tried creating a basic buster install and then running:

$ sudo apt install sugar sucrose lightdm

The result is not a usable Sugar installation.  I am most eager to
participate as a tester, power user, and curriculum developer, but I
need to start with a working system.

Thanks!

Jeff Elkner


Let's work together to create a just and sustainable world!


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar on Debian 10 (Buster)?

[Alex Perez]

Jeff,

Jeff Elkner wrote on 5/17/19 8:00 AM:

...vreveals that the latest Sugar update for my XO's will be running
Ubuntu18.04,  but also that it has the same issues I'm seeing in the
Debian Sid VM with Metacity, I guess?


No, OLPC OS 18.04 will not flash to Any original XO (XO-1, XO-1.5, 
XO-1.75, or XO-4) machines. At the URL you cited, the supported 
platforms are stated as "The target platforms are NL3 and ED20" which is 
exclusive of any of the original XO laptops. Furthermore, this 
(official) version does not suffer from the Metacity bug.


OLPC OS 13.2.10 <http://wiki.laptop.org/go/13.2.10> is the latest 
official version from OLPC for all XO laptops.


OLPC OS 18.04 is likely to work on unsupported hardware, however you 
will not be able to get any help from OLPC, nor from Sugar Labs, if you 
choose to go that route, as we have no control over the composition of 
this customized distribution.

James, I can't agree with you from personal experience that "Rasbian
has a very high barrier to entry unless the microSD card is
purchased already loaded (e.g. NOOBS)."  On the contrary, the website
instructions for creating your own microSD card are super easy using
etcher (https://www.balena.io/etcher/).  When you first boot from the
resulting microSD, it automatically runs a script that expands the
file system to fill the card, so the steps are really just:


Agreed, this is not hard for most people to do, even if it may be 
unfamiliar territory, especially the first time. Using something like 
Etcher, Fedora Image Writer (for Fedora, obviously) takes away most of 
the uncertainty for first time users.


Regards,
Alex Perez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar on Debian 10 (Buster)?

[Alex Perez]

There are two errors in this log file:

sh: 1: glib-compile-schemas: not found
and
gi.repository.GLib.Error: g-file-error-quark: Failed to open file 
“/home/jelkner/.sugar/default/org.laptop.WebActivity/data/schemas/gschemas.compiled”: 
open() failed: No such file or directory (4)



|Try sudo apt-get install libglib2.0-dev and see if it sorts this out, 
although I'm not sure it will.|

||

||


Jeff Elkner wrote on 5/17/19 9:01 AM:


When you say the browse activity didn't work, I'm assuming you started 
the activity and it showed a "Failed to start" message,
can you show us the activity log, it can be found in 
`/home/user/.sugar/default/logs/org.laptop.WebActivity-1.log`.


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SLOBS] GCI summit travel

[Alex Perez]

+1 from me, we should arrange to meet up while you are here. Is the 
summit in Mountain View?


Walter Bender wrote on 5/28/19 7:07 PM:
I've been selected by the GCI winners to represent SL at the summit 
next month. Google has provided US $1500 for travel (all other 
expenses are directly covered by Google.) I anticipate that the total 
cost of my trip will be < US $1000. I'd like approval from SLOB before 
booking my flight.


regards.

-walter

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



___
SLOBs mailing list
sl...@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/slobs


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar Outreach Plans 2019 - PyCon Cleveland (Tony Anderson)

[Alex Perez]

Lionel,

Lionel Laské wrote on 4/15/19 2:37 AM:


Hi Tony,

+1 on this.

BTW Sugar/Python is not the only way to grow user base.
For your information, we're currently deploying Sugarizer in 3 schools 
in the Saint-Ouen city near Paris. It means about 150 Android tablets 
with Sugarizer OS installed on it, used by few hundred children.


That's great, but it really needs to be documented. Has there been any 
media coverage, or other articles written about your efforts? if not, 
would you be willing to write an article about it, with some depth? I'd 
be genuinely interested to learn more about the project.


Regards.

Lionel.


Le lun. 15 avr. 2019 à 11:03, > a écrit :



Date: Mon, 15 Apr 2019 15:42:52 +0800
From: Tony Anderson mailto:tony_ander...@usa.net>>
To: sugar-devel@lists.sugarlabs.org

Subject: Re: [Sugar-devel] Sugar Outreach Plans 2019 - PyCon Cleveland
Message-ID: mailto:a42719ae-037d-9224-c420-fb98df7a6...@usa.net>>
Content-Type: text/plain; charset=utf-8; format=flowed

What Sugar Labs needs to survive is users. If our count of active
users
reaches zero, there will be no need for developers (or Sugar Labs).

A Conference like PyCon is an opportunity to show that Sugar is a
viable
educational platform. So marketing does not need to be concerned
about
$, it needs to be concerned about the characteristics of Sugar
that make
it an attractive option for educators. At such a conference it is
possible to make presentations - ofen there is an educational track.
More importantly there is an opportunity to have an exhibit (booth).
This booth can provide many examples of Sugar running on platforms
other
than the XO (make sure there some XO pictures visible since this
attracts interest to a booth.) Sugarizer can demonstrate that
Sugar is
available for smartphones, tablets and other devices. Sugar can
show its
capabilities on Ubuntu, Raspbian. Windows is a special case since
Miccrosoft has been able to lock educators into Windows. Showing that
Sugar is viable in a Windows-based deployment may be beyond our
current
cabability.

Our goal should be to attract new contributors and to find new
deployment opportunities.

Tony

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Meeting reminder: Sugar Dashboard (GSoC)

[Alex Perez]

Hrishi,

Can you respond here with your github username, and where you intend 
your blog posts to live? I would like to add this information to the 
wiki page of accepted GSoC 2019 projects at 
https://wiki.sugarlabs.org/index.php?title=GSoC/2019/Accepted_Proposals



Hrishi Patel wrote on 5/10/19 8:57 PM:

Thanks, I will keep these points in mind.

On Sat, May 11, 2019, 3:53 AM James Cameron > wrote:


Log of the meeting is
http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-05-10T14:34:13

My comments;

1.  please do write to sugar-devel@ for any small doubt,

2.  read the source code for the frame icons to see how they are
shown,

3.  read the source code for the Icon classes and look at how a
"badge" is applied,

4.  read the source code for the neighbourhood view and look at how
the wireless icons are filled in based on signal strength,

5.  because Sugar is designed to run native on a laptop, and only then
will certain features be visible to you, please learn to run it native
without a VM, otherwise you won't have the same user experience as a
VM,

6.  read help.sugarlabs.org  as a quick
way to see the user experience,

7.  rather than change the icon image, use GTK and Cairo to draw the
icon, so that the icon can be whatever you want,

8.  virtualisation software may hide your battery from the virtual
machine, or your computer might have no battery; you can emulate a
battery by editing the source code that discovers the battery and
extracts the state of charge,

-- 
James Cameron

http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org

http://lists.sugarlabs.org/listinfo/sugar-devel



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Unable to locate source package for sugar-toolkit (Native Installation of sugar v0.114)

[Alex Perez]

James Cameron wrote on 5/22/19 7:01 PM:

Thanks for reporting this.

Whether it works or not depends on the version of Debian or Ubuntu you
are using.  The sugar-toolkit module is for GTK 2, and was last packaged;

* for Debian 9 (Stretch),
* for Ubuntu 16.04 (Xenial).

It was dropped because Rsvg was dropped, in turn because Rsvg was not
maintained.
librsvg itself is not un-maintained, and in fact the most recent release 
was mere days ago:


https://github.com/GNOME/librsvg/releases

...so, presumably, it should be possible to build sugar-toolkit with 
this version of librsvg?


You will need sugar-toolkit module to run any Sugar activities that
depend on GTK 2.  You will also need sugar-toolkit as part of porting
any of these activities to GTK 3; because you must verify the user
experience is unchanged.  We saw recently with the Bichos activity how
important this is.

For OLPC OS my package archive has sugar-toolkit for Ubuntu 18.04, and
an unmaintained Rsvg package.

What changes do you propose for development-environment.md?

On Wed, May 22, 2019 at 04:16:24PM +0530, Swarup N wrote:

Hello,

I am trying to setup the sugar development environment via the native build
method as described [1]here.
I am able to clone the respective repositories, however when I run sudo apt
build-dep sugar-toolkit , I get the following error:
E: Unable to find a source package for sugar-toolkit

I am however able to run the same build-dep command for the other repositories
such as sugar-datastore, sugar-artwork and so on.

I did uncomment all the deb-src lines from /etc/apt/sources.list.

Can anyone guide me on how to proceed from here?

Thanks and Regards,
Swarup N

References:

[1] 
https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel




___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Request for Comments: What's missing for a Sugar 1.0 release?

[Alex Perez]

Folks,

Six years and ~two months ago, way back in March of 2013, the 
then-current SLOBs decided to make "the next release" version 1.0. This 
didn't happen, and instead, 0.99.0 was released on 2013-06-27 instead.


Seehttps://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2013-03-21

I'd like to request that the community at-large share their opinions 
with regards to what they feel are _must-have_ (not "nice to have") 
items for a "Sugar 1.0" release. Please reply to this thread with your 
thoughts.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Help] Connect two french students with OLPC deployments in various countries?

[Alex Perez]

Bastien,

Thanks for reaching out. Do you know which specific version of XO 
laptops these students were/will be given?


Is the e-mail address you CC'ed when you e-mailed sugar-devel the 
address of one of the students you mention? Joining and e-mailing 
i...@lists.sugarlabs.org may yield more useful information, since that 
is our general purpose list, and sugar-devel is (supposed to be) focused 
on actual development :)


Bastien wrote on 5/21/19 9:26 AM:

Hi Sugar,

OLPC France has been in touch with two students who will organize
IT workshops for children in various countries in Asia (India,
Bangladesh, Myanmar, Laos, Vietnam, Cambodia, Thailand) and South
America (Brazil, Paraguay, Argentina, Chile, Bolivia, Peru).

OLPC France will give them two XO laptops.

What is the best way to let them know people who are still active
on OLPC deployments in these countries?

I CC them -- don't forget to keep them in the loop or to send them
OLPC contacts thay you may have in these countries.

Below is their message.

Thanks a lot in advance for your help.



We are two students in IT school in France with the following project:
In one year, we will go to Asia (India, Bangladesh, Myanmar, Laos,
Vietnam, Cambodia, Thailand) and South America (Brazil, Paraguay,
Argentina, Chile, Bolivia, Peru) to meet local children and student to
share our IT knowledge.

Following our studies, we are convinced of the opportunities, but also
the dangers of IT for anyone. That’s why we want to awaken people to
IT. But instead of creating a global workshop, we want to respond to a
real need in local countries.

To achieve that, we want to create our workshops based on OLPC
initiative. OLPC France will lend us 2 XO computers. But to make our
initiative more relevant, we want to respond to a real need in each
country. For that reason, we want to exchange and discuss with
experienced people to obtain a better understanding of the situation
to build relevant workshops.

Based on your experience , do you know some person with this kind of
experience or knowledge? Your help will be very appreciated in any
subject (kind of population in need, contact of local IT school,
problems about IT, IT domain in need of qualified people, etc…)

Thank you in advance !





___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[Alex Perez]

Aniket,

You have hit a known bug for 0.113. Please see 
https://github.com/sugarlabs/sugar/issues/822


I should also point out that this was an easily search-able issue, and 
would encourage you to use Google or your preferred search engine, when 
you encounter issues like this in the future.


This bug will be fixed in 0.114, whenever that is released, which I have 
no direct control over. For now, you can download 
https://github.com/sugarlabs/sugar/commit/a83257bcf791e237afb55ed37f04d776f0fd927b.patch/ 
and patch Sugar manually, using the 'patch' command.


ANIKET MATHUR wrote on 5/14/19 4:12 AM:

Greetings everyone,

I was installing Sugar v0.113 using the Native Sugar build method here 
. 
I was using Ubuntu 18.10. After installation, on running Sugar I 
received the error message "ImportError: No module named sugar3". Need 
help with a couple of questions
1) Is there a need to have a build of the older version for v0.113 to 
work properly?

(never paid attention to that before).
 2) What is the correct procedure for installing v0.113?
Thanks!


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] F30 ARM (Raspberry Pi) SoaS not working, but a fix exists..

[Alex Perez]

James Cameron wrote on 5/19/19 3:50 PM:

That's unfortunate.

Agreed, but it was due to a lack of testing.


Were the Fedora 30 ARM builds being tested before release?
They were, but only in QEMU, it would seem. The temporary workaround is 
to fetch the initramfs referenced below, and then, after imaging the 
image to an SD card using $preferredImagingMethod (Fedora Image Writer, 
for most folks, would be their best bet), just copy the downloaded 
initrd over to the boot partition on the SD card.


Are the Fedora 31 ARM builds being tested?
I am informed by pwhalen that, as of today, the image is still broken in 
rawhide (which will become F31) but that it will be fixed in the coming 
days/weeks, now that there's a bug for the issue:


https://bugzilla.redhat.com/show_bug.cgi?id=1711475



On Sun, May 19, 2019 at 09:01:25AM -0700, Thomas Gilliard wrote:

Current f30 soas release for a Rpi3B+ (arm) do not boot [1]

There is a solution:

  "if you replace the initramfs with this one - [1]https://fedorapeople.org/
~pwhalen/soas/initramfs-5.0.9-301.fc30.armv7hl.img ...it will boot." 
on #fedora-arm

Hopefully this can be fixed in a rebuild for f30 arm

Tom Gilliard

satellit on freenode #fedora-qa

[1] [2]https://wiki.sugarlabs.org/go/Fedora_30#not_working

References:

[1] https://fedorapeople.org/~pwhalen/soas/initramfs-5.0.9-301.fc30.armv7hl.img
[2] https://wiki.sugarlabs.org/go/Fedora_30#not_working
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel




___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Fedora 30 (Release Candidate 1) SoaS images ready for testing

[Alex Perez]

Folks,


Just under the wire, we have managed to get some critical Sugar on a 
Stick issues fixed, which are now included in Fedora 30 SoaS images. I 
would like to extend a very special thanks to Peter Robinson, who took 
time out of his busy schedule to assist in getting the Fedora packages 
updated with the necessary fixes and patches. Thank you, Peter. This 
will be the first Fedora SoaS in several releases to have functional 
collaboration within Sugar, and it is thanks to your work, as well as 
community testers who take the time to test these new packages, and 
report back with the results.


For those who would like to test ot use Fedora 30 Sugar on a Stick, 
Release Candidate 1, you can download these ISO images, and use DD, 
win32diskimager, or your preferred raw image writing utility to stick 
the contents on a USB drive. Alternatively, these ISOs can be booted as 
a Virtual Machine, using VirtualBox, Parallels, Hyper-V, and other 
virtualization software.


Here are your download links:

For 32-bit machines: http://bit.ly/Fedora-30-RC1-SoaS-32-bit (891 
megabyte ISO)
For 64-bit machines: http://bit.ly/Fedora-30-RC1-SoaS-64-bit 
<https://dl.fedoraproject.org/pub/alt/stage/30_RC-1.1/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-30-1.1.iso> 
(942 megabytes)



Here is what's been fixed:

* Sugar 0.113 is included by default
* Collaboration works out of the box
* Able to connect to jabber.sugarlabs.org when configured (this is 
related to the fix for collaboration, thanks to James Cameron for this)
* A patch/hotfix to 0.113 
<https://github.com/sugarlabs/sugar/commit/a83257bcf791e237afb55ed37f04d776f0fd927b>, 
which resolves Sugar 0.113 starting up. Special thanks to Rahul 
"Pro-Panda" Bothra for this contribution.




The final release of Fedora 30 is expected to be made between April 30th 
and May 7th, depending on a number of factors. The F30 release schedule 
is documented at https://fedoraproject.org/wiki/Releases/30/Schedule


Regards,
Alex Perez
Sugar Labs Oversight Board Member
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Continued packet loss to MIT Media Lab-hosted Sugar Labs web servers may be resolved

[Alex Perez]

Folks,

 or the past ~48 hours, we've had fairly severe, but sporadic, packet 
loss (from 30% to 70%) to the Sugar Labs infrastructure and servers 
(freedom, justice, jita) that host our public-facing websites such as:


* translate.sugarlabs.org
* www.sugarlabs.org
* activities.sugarlabs.org
* all Sugar Labs mailing lists

..as well as the ability to ssh to the servers themselves, plus the 
management BMC/IPMI hosts for the servers. None of the servers 
themselves are actually in a degraded state at the OS level, only the 
network is.


Yesterday afternoon, after rooting around for help on who to contact, I 
opened a support ticket with MIT, and I got a response from them an hour 
or so later, stating: "I'm aware of the issue and am working to 
determine the cause. It is either something failing on the switch or 
something in the optical path. I'm in the process of replacing 
components in the pathway to rule that out."


External monitoring has shown that there have not been any further 
problems with the infrastructure for the past hour and a half, so it may 
be that they have resolved the problem as of this AM. It's just after 
noon where MIT is.


If anybody has any questions, please feel free to e-mail me directly.

Regards,
Alex Perez

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Fwd: Motion re GSoC Mentor Summit 2019

[Alex Perez]

+1

Walter Bender wrote on 7/16/19 1:06 PM:
As per Rahul's request below, we need to decide on whether or not to 
support the GSoC 2019 mentor summit travel for Rahul, Ibiam, and 
Tarun. (We can send up to 3 mentors to the summit (including a GCI 
representative). Google provides US $1100 stipend per person we send 
and covers all of local expenses.


As per protocol, the GSoC admins (James, Rahul, and I) selected the 
mentors to represent SL. Our criteria was based in part on having 
broad coverage -- core Sugar, Sugarizer, and GCI -- and ensuring that 
the people we select are active within the community.


If/when the motion below passes, I will write letters on behalf of SL 
for Rahul, Ibiam, and Tarun, so that they can get their visa 
applications started.


Motion: Sugar Labs will send Rahul Bothra, Ibiam Chihurumnaya, and 
Tarun Singhal to represent us at the Google Summer of Code 2019 Mentor 
Summit in Munich, Germany. Google is providing a stipend of US $1100 
per representative, which is expected to cover the bulk of the expense 
and the travelers will abide by the travel policy regarding any and 
all expenses.


regards.


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] translate.sugarlabs.org is back up and running

[Alex Perez]

I fixed translate.sugarlabs.org this morning.

Deepak Kumar wrote on 11/12/19 4:29 AM:

Thanks a lot James for the details.
 I will check it out on wiki and inform if I found something related 
to it.


On Tue, 12 Nov 2019, 4:38 pm James Cameron, > wrote:


Yes, I said it is not working.  It was working, but stopped working in
the past month or so; can't remember exactly when.  I think it
happened when the IP address range changed at MIT.  Losing it has
stopped me releasing activities with new translation changes.

Deepak, I don't know of a repository for it.  It isn't in
sugarlabs-infra on github either.  Apart from in the production
instance, I don't know where the source code is kept.  Our old
gitorious instance at http://git.sugarlabs.org/ has "pootle"
repositories.  The Wiki may have something on it.  Search there.

But if it was the IP address change, then the next step is for
sysadmins to fix it.

On Tue, Nov 12, 2019 at 08:37:45AM +0100, Samson Goddy wrote:
> Yes, it is down. I tested it and someone also reported
similar issue.
>
> On Tue, Nov 12, 2019, 8:23 AM Deepak Kumar
<[1]deepakdk2...@gmail.com > wrote:
>
>     Hi James,
>     I think that this link is broken
>     [2]http://translate.sugarlabs.org/
>     Could you please add the link to the repository of this
project as I
>     couldn't find it on sugarlabs repo. As I have good knowledge
of Python and
>     done some projects using Django as a backend too so I think
that I can help
>     with this project.
>
>     Thanks!
>
>     On Tue, 12 Nov 2019, 11:45 am James Cameron,
<[3]qu...@laptop.org > wrote:
>
>         Welcome Rahul.  You can find in the mailing list
archives my "How to
>         get started as a Sugar Labs developer [v7]",
>
>       
 [4]http://lists.sugarlabs.org/archive/sugar-devel/2019-September/
>         057182.html
>
>         Music Blocks and Sugarizer are web apps written in
JavaScript.
>
>         [5]activities.sugarlabs.org
 is a web app written in PHP.
>
>         [6]translate.sugarlabs.org
 is a web app written in Python
with Django.
>
>         (but is not working).
>
>         You can work on whatever you want to work on, and if
what you make is
>         good, we may keep it.
>
>         On Tue, Nov 12, 2019 at 11:23:01AM +0530, Rahul kohli wrote:
>         > Please help me as I am a new here I want to know about
sugarlabs and
>         how can i
>         > get started and also I want to work on web app of
sugar labs so how
>         can i work
>         > on that too..
>
>         > __



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Issues in building sugar

[Alex Perez]

You probably need to install autoconf-dev or autoconf-devel. Googling 
the error would likely have led you to this conclusion.



Garvit Gupta 
December 15, 2019 at 9:11 AM
As given in the document for building sugar, while running the 
autogen.sh file the below error comes up (screenshot for the error is 
attached below).


Also, I am not able to found these required directories:
source code for fructose activities - use/src/sugar-activities/*
sugar,sugar-toolkit-gtk3, sugar-datastore and sugar-artwork - 
/usr/src/sugar*.



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Regarding IRC channels

[Alex Perez]

Garvit,

There are hundreds of free IRC clients out there, for every operating 
system under the sun. mIRC is not necessarily the best option. Here's 
one I know is pretty decent: https://www.adiirc.com/




Garvit Gupta 
December 15, 2019 at 8:59 AM
Can you suggest some web-based application through which we can 
communicate on IRC. I am currently using mirc but it is free only for 
30 days.




___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [ASLO] Release Browse-157.5

[Alex Perez]

James,


Is the " For Fedora 18 systems only," item correct? If so, which version 
of Browse should we be using with 0.116 on non-F18 platforms?

Sugar Labs Activities 
November 28, 2019 at 7:46 PM
Activity Homepage:
http://activities.sugarlabs.org/addon/4024

Sugar Platform:
0.98 - 0.116

Download Now:
http://activities.sugarlabs.org/downloads/file/29361/browse-157.5.xo

Release notes:
* For Fedora 18 systems only,
* Hide browser tabs in fullscreen mode,
* Reset title after a download starts,
* Ignore leading spaces in a URL,
* Add feature - dark mode for PDFs,
* New translations,
* Test collaboration.



Sugar Labs Activities
http://activities.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [IAEP] From OLPC XO To Positivo: Rwanda Sets The Bar Higher

[Alex Perez]

It would be good and helpful to attempt to make contact with anyone 
within Rwanda that is using Sugar on Positivos, official or otherwise, 
but also anyone who is involved with the official distribution of 
Positivos within Rwanda. Can you help us on this front, Samson?



Walter Bender 
November 25, 2019 at 6:57 AM


On Mon, Nov 25, 2019 at 4:38 AM Tony Anderson > wrote:


The current school year in Rwanda is just ending and the new year
starts
January 6. The Positivos have been distributed to GS (Groupe
Scolaire)
schools which are public with grades from entry to S3 (9th grade).

The ICT Curriculum is based on Windows - with some planned
expansion to
include mobile techniques. The Positivos are distributed with
Windows 10
installed.  Neither the Positivos or XOs currently include touch
screen
technology.

Note: as far as I know, Rwanda is the largest still active XO
deployment. The need is to find a bridge between the student's three
years of primary school XO experience and their further ICT
instruction.The Positivo hard drive is large enough to support an
Ubuntu/Sugar install alongside.. Some teachers are making this
install
on their own initiative. The article hints that Rwanda may take
official
advantage of this opportunity.


Please let us know if there is anything we can do to support this effort.


I am currently in Rwanda working with Care 4 Kids, a German
philanthropy
supporting the use of the XO. Care 4 Kids provides interns - local A
Level graduates in ICT to selected schools. In 2019 these interns
supported five GS schools in Kigali province (XO ICT enrollment in
the
thousands). In 2020, there will be five two-person teams of interns.
Four teams supporting  a school in one of the provinces and
working with
teachers from five surrounding schools. The Kigali team will
continue to
support the five 2019 schools. Their support provided in the native
language has proven effective and popular.


Is there a translation team we could tap into?

As far as bridging the two worlds, some of our apps could be gateways, 
such as Music Blocks, which run just as well in Windows as Sugar.



Tony

On 25/11/2019 01:56, James Cameron wrote:
> Thanks Samson.
>
> For Sugar Labs, the most important part is "the machines will
have the
> same modules (interface) for children lesson," so there's an
> opportunity for Sugar Labs to remain involved.
>
> I don't know what operating system REB are using, but OLPC OS
18.04.0
> based on Ubuntu 18.04.2 and Sugar will likely work straight away on
> PC-compatible laptops, and can be customised and rebuilt.  Our OLPC
> servers do see update requests from countries were we have not
> distributed our PC-compatible laptops, which is cool.
>
> On Sun, Nov 24, 2019 at 12:17:21PM +0100, Samson Goddy wrote:
>> Hello everyone,
>>
>> I saw this article online, and I thought it should be an
interesting read[1].
>>
>> [1][1]https://ktpress.rw/2019/11/
>> from-olpc-xo-to-positivo-rwanda-sets-the-bar-higher/
>>
>> Regards
>>
>> --
>>
>>    Samson Goddy
>>
>>    Twitter: [2]https://twitter.com/samson_goddy
>>    Email: [3]samsongo...@sugarlabs.org

>>                [4]samsongo...@gmail.com

>>
>>    Website: [5]https://samsongoddy.me/
>>
>> References:
>>
>> [1]

https://ktpress.rw/2019/11/from-olpc-xo-to-positivo-rwanda-sets-the-bar-higher/
>> [2] https://twitter.com/samson_goddy
>> [3] mailto:samsongo...@sugarlabs.org

>> [4] mailto:samsongo...@gmail.com 
>> [5] https://www.sugarlabs.org/
>> ___
>> IAEP -- It's An Education Project (not a laptop project!)
>> i...@lists.sugarlabs.org 
>> http://lists.sugarlabs.org/listinfo/iaep
>

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org

http://lists.sugarlabs.org/listinfo/sugar-devel



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



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Tony Anderson 
November 25, 2019 at 12:40 AM
The current school year in Rwanda is just ending and the new year 
starts January 6. The Positivos have been distributed to GS (Groupe 
Scolaire) schools which are public with grades from entry to S3 (9th 
grade).


The ICT Curriculum is based on Windows - with some 

Re: [Sugar-devel] Fwd: [Bug 1737929] sugar depends on Python 2

[Alex Perez]

Right, and the goal for Fedora 32 is to eliminate all of those 
activities. They either get patched/ported, or dropped as a packaged 
activity within Fedora, so we don't need any dependency on Python 2, 
which is going away. Any activity that depends on something as simple as 
python2-simplejson, for instance, is already broken in Fedora 32 (not 
released, in development)



James Cameron 
November 27, 2019 at 1:16 PM
Some of the activities packaged by Fedora depend on sugar-toolkit
because those packages haven't had a Port to Python 3.  That's what's
bringing sugar-toolkit into the light.

On Wed, Nov 27, 2019 at 10:03:46PM +0100, Chihurumnaya Ibiam wrote:

Sugar-toolkit isn't being used by sugar anymore, sugar-toolkit-gtk3 is being
used and that has been ported to python3.  Sugar-toolkit should be retired.

On Wed, Nov 27, 2019, 7:51 PM Thomas Gilliard <[1]satelli...@gmail.com> wrote:

  Forwarded Message 
 Subject: [Bug 1737929] sugar depends on Python 2
Date: Wed, 27 Nov 2019 18:08:45 +
From: [2]bugzi...@redhat.com
  To: [3]satelli...@gmail.com

 [4]https://bugzilla.redhat.com/show_bug.cgi?id=1737929

 Adam Williamson [5] changed:

 What |Removed |Added
 

 CC| |[6]awill...@redhat.com

 --- Comment #15 from Adam Williamson [7] ---
 sugar-toolkit depends on python2-simplejson and that went away already.
 This is
 prevent SoaS images building in Rawhide, e.g.
 [8]https://koji.fedoraproject.org/koji/taskinfo?taskID=39373467 .

 --
 You are receiving this mail because:
 You are on the CC list for the bug.

 ___
 Sugar-devel mailing list
 [9]Sugar-devel@lists.sugarlabs.org
 [10]http://lists.sugarlabs.org/listinfo/sugar-devel

References:

[1] mailto:satelli...@gmail.com
[2] mailto:bugzi...@redhat.com
[3] mailto:satelli...@gmail.com
[4] https://bugzilla.redhat.com/show_bug.cgi?id=1737929
[5] mailto:awill...@redhat.com
[6] mailto:awill...@redhat.com
[7] mailto:awill...@redhat.com
[8] https://koji.fedoraproject.org/koji/taskinfo?taskID=39373467
[9] mailto:Sugar-devel@lists.sugarlabs.org
[10] http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Chihurumnaya Ibiam 
November 27, 2019 at 1:03 PM
Sugar-toolkit isn't being used by sugar anymore, sugar-toolkit-gtk3 is 
being used and that has been ported to python3. Sugar-toolkit should 
be retired.




___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Thomas Gilliard 
November 27, 2019 at 10:51 AM




 Forwarded Message 
Subject:[Bug 1737929] sugar depends on Python 2
Date:   Wed, 27 Nov 2019 18:08:45 +
From:   bugzi...@redhat.com
To: satelli...@gmail.com



https://bugzilla.redhat.com/show_bug.cgi?id=1737929

Adam Williamson  changed:

What |Removed |Added

CC| |awill...@redhat.com



--- Comment #15 from Adam Williamson  ---
sugar-toolkit depends on python2-simplejson and that went away 
already. This is

prevent SoaS images building in Rawhide, e.g.
https://koji.fedoraproject.org/koji/taskinfo?taskID=39373467 .

--
You are receiving this mail because:
You are on the CC list for the bug.


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Running Sugar Activities

[Alex Perez]

Soham,

Two details we'll need which are missing from your report are: which version of 
Sugar do you have installed, and how are you installing the activities?

On 3/1/2020 2:35:34 AM, soham bhattacharya <116cs0...@nitrkl.ac.in> wrote:
Hi,
I am Soham. I am running Sugar on Ubuntu 18.04.3 LTS. I also have the Sugar 
toolkit installed. The problem is after installing any sugar activity I am not 
being able to run it.

for example if I run Calculate.activity I get:

Traceback (most recent call last):
  File "calculate.py", line 37, in 
    from shareable_activity import ShareableActivity
  File "/usr/share/sugar/activities/Calculate.activity/shareable_activity.py", 
line 5, in 
    from sugar3.activity import activity
  File "/usr/local/lib/python2.7/dist-packages/sugar3/activity/activity.py", 
line 175, in 
    gi.require_version('TelepathyGLib', '0.12')
  File "/home/soham/.local/lib/python2.7/site-packages/gi/__init__.py", line 
129, in require_version
    raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace TelepathyGLib not available

Or if I try to run TurtleBlocks.activity:

  File "TurtleArtActivity.py", line 43, in 
    from sugar3.activity import activity
  File "/usr/local/lib/python2.7/dist-packages/sugar3/activity/activity.py", 
line 175, in 
    gi.require_version('TelepathyGLib', '0.12')
  File "/home/soham/.local/lib/python2.7/site-packages/gi/__init__.py", line 
129, in require_version
    raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace TelepathyGLib not available

It looks like TelepathyGLib is missing from gi. What should I do. Help will be 
appreciated.

Thanks,
Soham
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[Alex Perez]

Prashant,

We also offer our own Sugar Labs specific IRC chat gateway, at 
http://chat.sugarlabs.org:9090/


I'd like to understand more fully why you believe IRC is hard for you to 
use. Is it hard because you've never used it before? Is it hard because 
you have no familiarity with it? IRC can absolutely be used on mobile 
devices, and this basic misunderstanding shows me that you're not 
particularly familiar with some basic IRC facts, nor have you bothered 
to open your mobile phone up, go to the app store, and type "IRC" in to 
the search field. Which mobile platform are you using? Android? iOS? If 
you tell us, we can recommend some clients for you.


The issue of loss-of-state when you're disconnected from IRC is a known 
problem for 25+ years, and many ways to address it have been developed 
over that period of time.  There are IRC bouncers, web-based IRC 
clients, and all sorts of other solutions to these problems, if you can 
be bothered to search for them, instead of assuming that no solution 
exists, which is sorta what seems to have happened here.


There are several reasons why we don't use Slack, Discord, or other 
proprietary messaging systems, which I'm not going to get into the 
details of here, but since they are corporate owned-and-operated pieces 
of infrastructure, they may or may not exist in the future.


The primary problem with using Gitter is that it requires you to have a 
GitHub account, and has no other authentication mechanism. Developers 
are not the only people we care about, and IRC is accessible to all, and 
is fundamentally democratic.



Prashant Sengar 
March 4, 2020 at 6:33 AM
Hi,

I am sure this request must have been raised earlier as well. I wanted 
to ask if Sugar could create a communication channel on another 
platform such as a discord server, Slack or Telegram instead of IRC to 
make communication easier.


The reason why others will be a better option:
1. The chats will be accessible even if I am offline for a while, 
unlike IRC where I cannot see any earlier data.
2. IRC cannot be used on mobile devices, so it creates a barrier in 
communication. On the other hand, the other chat applications are 
available on all platforms for everyone to use.


I would like to request the team to please consider this request. If 
such request has been made earlier and denied due to some reasons, 
then I would like to know them so that I can understand the reasons 
and work accordingly.


Regards.
Prashant Sengar


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[Alex Perez]

Srevin,

Srevin Saju 
March 4, 2020 at 10:07 AM
I agree to Prashant. To me Slack seems to be a viable option, and 
indeed popular too. But unfortunately due to historical reasons, we 
might not move to another platform. Nevertheless, it might be of 
interest to other developers in the community
We will not be moving our real-time communication mechanism to Slack, or 
any other proprietary chat platform. See my other e-mail for a bit more 
of an explanation as to why, or, if you've got 20 minutes, please read 
this article: 
https://sneak.berlin/20200220/discord-is-not-an-acceptable-choice-for-free-software-projects/


I use slack daily for communications with work colleagues, and don't 
hate it, though I wish their stand-alone clients didn't use a shitload 
of RAM (they're Electron-based browser apps)
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Greetings from Sugar Labs DC!

[Alex Perez]

Christian,

Welcome. If you happened to be with Jeff when he and a group of his 
students were at PyCon last year, we may have met then. I believe James 
Cameron has some current Sugar packages for Debian he may be 
able/willing to share with you. We are actually in need of someone to 
take over packaging of the Sugar packages in Debian. Is that something 
you might be interested in helping us with?


Regards,
Alex Perez


Christian Faris <mailto:christian.lee.fa...@gmail.com>
March 5, 2020 at 3:42 PM

Dear Sugar Labs Devel Community,


My name is Christian “Chip” Faris and I am active with Sugar Labs DC. 
I am a former student of Jeff Elkner and have good connections with 
Kevin Cole. I am helping out a student who has a capstone project of 
helping Sugar Labs DC to use Sugar on Debian Buster. The GitHub for 
installing Sugar on Debian Buster has not updated in quite sometime. 
Since most of the hardware we have (mainly raspberry pi 3B+ and 4) run 
Debian Buster, I wonder if there is a way to install Sugar on Debian 
Buster as this will be a huge help with labs and events for our 
elementary and early childhood education students.



Thank you for reading and any help is greatly appreciated!

Sincerely yours,


Christian “Chip” Faris


christian.lee.fa...@gmail.com <mailto:christian.lee.fa...@gmail.com>


https://cfaris459.github.io/




___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Joining Sugar Labs

[Alex Perez]

Abhay,

Permission to "Join" Sugar Labs is not needed. Your contributions are 
all that matters, in whatever form that takes. What are your abilities? 
How would you like to contribute? Those are the questions that matter :)


That said, if you would like to become a member, here is the forma 
process. There is no requirement that contributors be members, though we 
encourage all who contribute and care about the future of the project to 
consider membership.


See https://wiki.sugarlabs.org/go/Sugar_Labs/Members for the details.


Abhay Malik 
February 27, 2020 at 4:48 AM
Hey,
Mr. Walter can I join sugar labs.

Thanks,
Abhay

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar Advocacy for Arch Linux

[Alex Perez]

Srevin,

I'm personally a fan of Arch Linux, but It's a bit of a chicken-and-egg 
problem, when we already don't have sufficient resources. While I 
welcome testing of Sugar on Arch, I don't think it makes sense for us to 
direct existing resources there, unless there's a demonstrable reason 
why it's necessary, or even directly beneficial. I would personally 
rather see Sugar Labs direct more focus on maintaining tested and good 
packages for Debian/Ubuntu, and Fedora, given that we know we have users 
there.


All distributions can be relatively easily customized, so I'm not 
particularly swayed by the argument that Arch serves customization any 
better than any other distribution, frankly. I also suspect that most 
schools that choose to use Linux are likely using one of the more 
popular, mainstream distros, such as Ubuntu or Debian, possibly Fedora. 
Regardless, anyone is free to contribute as they choose, but asking us 
to focus efforts to $favoritePreferredDistro doesn't necessarily serve 
to benefit the community as a whole.


Regards,
Alex Perez

Srevin Saju <mailto:srevi...@gmail.com>
February 4, 2020 at 8:17 AM
I have noticed the GSoC projects for Ubuntu and Fedora, however, it 
would be nice to have Sugar tested on Arch Linux also, as part of 
GSoC. Currently we have only 1 tester for Arch, viz, Markimus, on the 
AUR. Testing on Arch Linux or Mankato, would help to also include 
Manjaro with Sugar DE distributions, moreover, Arch serves 
customisation, which a bigger organization can use, if they would like 
to use Sugar for students. This is only a suggestion. thanks.


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Fwd: Fedora 32 Sugar on a Stick is available now!

[Alex Perez]

Fedora 32 has been released, and the Fedora 32 Sugar on a Stick spin is 
available for download from https://bit.ly/F32-SoAS-x86_64-ISO. It is 
950 megabytes in size.


The 32-bit Fedora SoaS ARM image, suitable for use on Raspberry Pi 
1/2/3, is also available at https://bit.ly/F32-SoAS-armhfp-raw and is 
730 megabytes in size. Also worthy of note, the armhfp kernel supplied 
in this image has been verified to boot from USB on an unlocked OLPC 
XO-1.75, although it's very, very slow.


This is a purely Python 3 based Sugar environment, and Python 2 
activities will not run here at all. This is the first version of Sugar 
on a Stick to drop Python 2 completely, and a few of the bundled 
activities which have yet to be ported to Python 3 were removed from 
this release, and will re-appear at which point the porting and testing 
of them is complete.

*From:* Matthew Miller 
*Date:* April 28, 2020 at 6:55 AM
*To:* annou...@lists.fedoraproject.org
*CC:* devel-annou...@lists.fedoraproject.org
*Subject:* Fedora 32 is available now!
It’s here! We’re proud to announce the release of Fedora 32.
Thanks to the hard work of thousands of Fedora community
members and contributors, we’re celebrating yet another
on-time release!

Read the official announcement at:

* https://fedoramagazine.org/announcing-fedora-32/

or just go ahead and grab it from:

* https://getfedora.org/



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SoaS] SoaS 32 is silent?

[Alex Perez]

Correct, this is a function of multiple audio outputs, and how they are 
enumerated. I have verified that SoaS boots and runs, with sound and no 
changes required, on an old iMac5,2, form 2007. As an aside, this is one 
of those weird Apple-manufactured 32-bit EFI machines (but 64-bit CPUs).



James Cameron <mailto:qu...@laptop.org>
April 28, 2020 at 6:28 PM
Good, that makes it not-Sugar.  Get it fixed on Workstation is your
best bet.

I've seen this kind of thing happen with laptops that have HDMI output
capability.  Audio is being clocked out a disconnected port.

Sugar predates PulseAudio.  Sugar has no support for anything other
than ALSA.  An opportunity.  GStreamer as used by Speak will use
PulseAudio if available.

On Tue, Apr 28, 2020 at 08:31:57PM -0400, Frederick Grose wrote:

So I found that SoaS and Fedora Workstation, at least, have the audio output
sink default on card/port index 1 instead of the convention of index 0.
Where and how this goes this way, I don't know.  But it happens on more than
one system.

I've updated the bug report, [1]https://bugs.sugarlabs.org/ticket/4998.

A workaround is to use the PulseAudio command,
$ pacmd set-default-sink 0

On Tue, Apr 28, 2020 at 4:36 AM Peter Robinson <[2]pbrobin...@gmail.com> wrote:

 > With Fedora-SoaS-Live-x86_64-32-1.6.iso I'm hearing no sound.
 > And see no log messages.
 >
 > Is this a common problem?

 Ultimately in this cycle in particular an awful lot changed, we moved
 completely from python2 -> python3 among a lot of other changes.

 For me the Speak activity works for me on a VM and that's my usual
 go-to sound tester as I don't need to find any media to play.

 Things like sound are very complex, multiple output, defaults,
 different hardware. Some level of detail of the hardware and the setup
 is useful to even begin to know what the issue may be, is there any
 errors in dmesg etc.

 Peter

 > --
 > From: James Cameron <[3]qu...@laptop.org>
 > Date: Mon, Apr 27, 2020 at 8:04 PM
 > To: Frederick Grose <[4]fgr...@gmail.com>
 > Cc: Development of live Sugar distributions <[5]s...@lists.sugarlabs.org
 >, Sugar-dev Devel <[6]sugar-devel@lists.sugarlabs.org>
 >
 >
 > I've no idea about your sound problem.  It doesn't happen for me on
 > Debian or Ubuntu.  I get sound from Speak and Music Keyboard.  I get
 > sound into Measure.
 >
 > For not seeing any log messages; Python 3 holds messages in process
 > memory and does not flush logs.  Another layer of buffering.
 >
 > Log files in .sugar/default/logs should be read after stopping the
 > program that writes to them.
 >
 > For activity logs, you have to stop the activity and confirm with
 > Frame F6 that it is stopped.
 >
 > For shell.log you have to log out and log in again.
 >
 > For datastore.log you have to log out for a couple of minutes and then
 > log in again.  Otherwise the same datastore process may be reused.
 >
 > James Cameron
 > [7]http://quozl.netrek.org/
 >
 >
 > --
 > From: Alex Perez <[8]ape...@alexperez.com>
 > Date: Mon, Apr 27, 2020 at 8:11 PM
 > To: Frederick Grose <[9]fgr...@gmail.com>
 > Cc: Development of live Sugar distributions <[10]s...@lists.sugarlabs.org
 >, Sugar-dev Devel <[11]sugar-devel@lists.sugarlabs.org>
 >
 >
 > Frederick,
 >
 > Chances are, with the sound problem, that this is a system/Fedora
 specific problem, and has nothing to do with Sugar. You can test this
 hypothesis by downloading a different spin of RC1.6, for example the LXDE
 Live ISO, and test sound there. [12]https://dl.fedoraproject.org/pub/alt/
 stage/32_RC-1.6/Spins/x86_64/iso/Fedora-LXDE-Live-x86_64-32-1.6.iso
 >
 > &&&&&&&&&&&&&&&&&&&&&&&&&
 >
 > Thanks for the hints.
 >
 > I tested a live USB installation of LXDE 32-1.6 and got sound for the
 music player sample.
 >
 > So probably not Fedora in general, nor Sugar, but something in the SoaS
 build.
 >
 > I've opened [13]https://bugs.sugarlabs.org/ticket/4998 and attached the
 zipped logs from some test sessions.
 >
 >
 > ___
 > SoaS mailing list
 > [14]s...@lists.sugarlabs.org
 > [15]http://lists.sugarlabs.org/listinfo/soas
 ___
 SoaS mailing list
 [16]s...@lists.sugarlabs.org
 [17]http://lists.sugarlabs.org/listinfo/soas

References:

[1] https://bugs.sugarlabs.org/ticket/4998

Re: [Sugar-devel] [SoaS] Fedora 32 Final is GO, SoaS Release Candidate ISO available immediately

[Alex Perez]

Frederick,

Chances are, with the sound problem, that this is a system/Fedora 
specific problem, and has nothing to do with Sugar. You can test this 
hypothesis by downloading a different spin of RC1.6, for example the 
LXDE Live ISO, and test sound there. 
https://dl.fedoraproject.org/pub/alt/stage/32_RC-1.6/Spins/x86_64/iso/Fedora-LXDE-Live-x86_64-32-1.6.iso



Frederick Grose <mailto:fgr...@gmail.com>
April 27, 2020 at 11:50 AM
With Fedora-SoaS-Live-x86_64-32-1.6.iso I'm hearing no sound.
And see no log messages.

Is this a common problem?



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Alex Perez <mailto:ape...@alexperez.com>
April 23, 2020 at 11:21 AM
The Fedora release team met today and approved the release of Fedora 
32, which is scheduled for this coming Tuesday, April 28th.


The 1.6 Release Candidate ISO for the Fedora 32 SoaS (Sugar on a 
Stick) LiveCD/ISO is downloadable from 
https://bit.ly/Fedora-32-RC-SoaS-LiveISO-x86_64

It is one gigabyte in size.

This is a purely Python 3 based Sugar environment, and Python 2 
activities will not run here at all. This is the first version of 
Sugar on a Stick to drop Python 2 completely, and a few of the bundled 
activities which have yet to be ported to Python 3 were removed from 
this release, and will re-appear at which point the porting and 
testing of them is complete.


Special thanks to Peter Robinson and Ibiam Chihurumnaya for making the 
Sugar-specific bits of this spin possible.



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Status of Python 3 port of Sugar Training Activity?

[Alex Perez]

James,

I saw your commit from seven days ago to 
https://github.com/sugarlabs/training-activity, and was wondering if 
it's considered "py3 complete". Can you provide a high level update on 
the state of the activity, as time allows?


Thanks,
Alex Perez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Fedora 32 Final is GO, SoaS Release Candidate ISO available immediately

[Alex Perez]

The Fedora release team met today and approved the release of Fedora 32, 
which is scheduled for this coming Tuesday, April 28th.


The 1.6 Release Candidate ISO for the Fedora 32 SoaS (Sugar on a Stick) 
LiveCD/ISO is downloadable from 
https://bit.ly/Fedora-32-RC-SoaS-LiveISO-x86_64

It is one gigabyte in size.

This is a purely Python 3 based Sugar environment, and Python 2 
activities will not run here at all. This is the first version of Sugar 
on a Stick to drop Python 2 completely, and a few of the bundled 
activities which have yet to be ported to Python 3 were removed from 
this release, and will re-appear at which point the porting and testing 
of them is complete.


Special thanks to Peter Robinson and Ibiam Chihurumnaya for making the 
Sugar-specific bits of this spin possible.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugarizer knowledge activity pack

[Alex Perez]

The sugar-devel list archives are available at 
http://lists.sugarlabs.org/archive/sugar-devel/


That said, I'm not sure what you're looking for exists there.


Hemansh Khaneja 
March 19, 2020 at 9:05 AM
I have joined this mailing list just now, could someone share any 
previous conversation regarding Sugarizer Knowledge Activity Pack GSoC 
Project



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Fedora 32 Sugar on a Stick beta ISO ready for testing

[Alex Perez]

Fedora 32 has entered beta state, and the Sugar on a Stick beta ISO 
(size is 1 gigabyte) can be downloaded from http://bit.ly/SoaS-F32-Beta-ISO


One known issue is that the IRC activity fails to start, and can not be 
used, as it's not yet been ported to Python 3.


The current target final release date for Fedora 32 is Tuesday, April 
21st, though this may change if need be.


Please test on real hardware if possible, and send/provide reports to 
s...@lists.sugarlabs.org as necessary.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Today's Minutes and Next Meeting Time

[Alex Perez]

James Cameron wrote on 12/9/20 9:09 PM:
> On Thu, Dec 10, 2020 at 07:13:49AM +0300, Srevin Saju wrote:
>> G'day!
>>
>> I have a topic, which perhaps needs discussion,
> It is about time this came up again.

Pretty much :)
>
>> We have been using IRC for many years. Recently, some of our
>> communication moved to Slack, and some to Jitsi. What is Sugar
>> Labs's idea of a best, unified communication platform which it
>> should recommend to new developers.  Right now, all the guides point
>> directly to IRC,
> Yes, even my "How to get started as a Sugar Labs developer" points to
> IRC.
>
>> most new developers, who are interested to contributing to Sugar
>> drop a message to an IRC channel, and almost never get a reply. This
>> is possibly because the communication has diversified, or because of
>> a community split on the basis of communication medium.
> It is easier to explain the lack of reply as being caused by a lack of
> contributing members, and a focus by the remaining members on their
> specific projects in a way that does not require collaborating in
> real-time.  The GitHub commit pattern over time confirms this.
>
>> Recently, many new developers told us of the difficulties of using
>> IRC clients, the need for Bouncers, etc.
> (a) my preference is not to call them developers until they have
> contributed,

Agreed. Until you've contributed something, you're just an interested
party. Simply aspiring to be a developer does not make you one.
>
> (b) these barriers to using IRC do not seem difficult; above all, why
> are we doing FreeNode's job for them?
In what way do you feel we're doing FreeNode's job for them? I don't get it.
>
>> We (some of us) suggested them to use a Matrix client to connect to
>> #sugar, and indeed they are quite satisfied with new mode of
>> communication.. The Matrix protocol.
> Most recent discussion on #sugar was just you talking to cyksager, and
> we couldn't see anything from them until they did something to fix it.
>
>> The Matrix protocol is interesting. Sugar had a matrix channel for
>> many years. Recently we set up a bridge between the matrix channel
>> (#sugar:matrix.org) and the IRC irc.freenode.net channel, i.e
>> (#sugar), which helped a few developers to keep connected to the IRC
>> channel without a bouncer and also make use of newer clients for
>> mobile, for example Element Android (available  on F-droid, Google
>> Play), and Element iOS. Element / Matrix has a intuitive web client
>> which supports reactions and better formatting as compared to IRC,
>> and is the best place for a developer to start contributing. The
>> most interesting and useful feature is the IRC bridge, which helps
>> to make use of the best of Matrix and maintain the connection
>> between the IRC channel and the Matrix channel. The bridge is a tool
>> which helps to convert the IRC protocol to the matrix protocol and
>> vice versa.
>>
>> Topic of discussion, we a Sugar Gitter channel, Sugarizer Matrix
>> channel, etc. Matrix has the support to integrate everything to a
>> single channel.  What is your opinion?

While it may be a factually accurate statement that "we have had this
channel for years", that doesn't mean it's been trafficked/visited much
at all. For instance, I had no knowledge of its existence before several
months ago, when the IRC bridge was set up. The IRC channel has existed
since the inception of the Sugar Labs project. You may see IRC as an
antiquated protocol, and I have no problem with Sugar Matrix channel,
bridged to the IRC channel. But to show up and suggest that we eliminate
the primary real-time collaboration tool that the project has used since
its inception shows, frankly, somewhat of a lack of understanding of how
open source projects work. You need to learn to build consensus. If you
show up and, shortly thereafter, say "I don't like the way we
communicate", let's change it completely, you're inevitably going to
experience resistance. To expect anything else is nuts. We have mailing
lists for non-realtime communications. If you're e-mail averse, you will
not last long in any open source community.
> My opinion is that you've got the cart before the horse.  First thing
> that is needed is for potential contributors to become developers, and
> to collaborate on something.
Agreed. And honestly, if you can't follow basic directions on how to use
and connect to an IRC channel, I find it very, very unlikely that
newcomers will have the patience necessary to become meaningful
contributors.
>
> Where you have potential contributors using IRC to ask questions that
> are answered by documentation or source code; that's just a help line
> or chat bot.  It is often a waste of time to invest in that.  Better
> is to fix the problem they are reporting.
Agreed. It's not as though we have paid customer support/engagement
people to do anything with such complaints, anyways.
>
>> Interesting points of discussion and helpful material:
>>
>> * Pull request to add Matrix 

[Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware

[Alex Perez]

James,

I booted up the latest Sugar-live-build image, which I'd downloaded from 
http://people.sugarlabs.org/~quozl/sugar-live-build/ and written to a 
USB stick, and booted it up in an HP-branded terminal from ~2012, which 
works perfectly fine with the latest Fedora SoaS images.


During early boot, the kernel printed a message which stated, 
"drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesetting for 
R600 or later requires firmware installed." followed by a line which 
said "See http://wiki.debian.org/Firmware for information about missing 
firmware"


Furthermore, Xorg also fails to subsequently initialize in the fallback 
fbdev mode, with Xorg reporting "Cannot run in framebuffer omde. Please 
specify busIDs for all framebuffer devices", resulting in the machine 
sitting at a Linux console forever.


Simply bundling the 'firmware-amd-graphics' package from the 
firmware-nonfree repo when you build the Live image would mean the image 
would work correctly on a vastly larger amount of hardware, out of the box.


I would encourage you to take it one step further, and bundle the 
firmware-linux-nonfree metapackage, which will include firmware for 
things like Marvell wireless cards, Intel wireless cards, Atheros 
wireless cards (both USB and integrated/PCI/PCIe)


Thanks,
Alex Perez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware

[Alex Perez]

James Cameron wrote on 1/17/2021 6:12 PM:

It sounds like you share some of the same intentions as Martin Guy,
who needed i386 support.  He found what he needed with Trisquel.  Have
you tried that?
No, I'm interested in running on x86_64, EFI-compliant hardware.  I have 
no need or desire for Trisquel.

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware

[Alex Perez]

Answers inline

James Cameron wrote on 1/17/2021 2:16 PM:

On Sun, Jan 17, 2021 at 02:03:10PM -0800, Alex Perez wrote:

James,

I booted up the latest Sugar-live-build image, which I'd downloaded from
http://people.sugarlabs.org/~quozl/sugar-live-build/ and written to a USB
stick, and booted it up in an HP-branded terminal from ~2012, which works
perfectly fine with the latest Fedora SoaS images.

Thanks for testing.


Simply bundling the 'firmware-amd-graphics' package from the
firmware-nonfree repo when you build the Live image would mean the image
would work correctly on a vastly larger amount of hardware, out of the box.

I would encourage you to take it one step further, and bundle the
firmware-linux-nonfree metapackage, which will include firmware for things
like Marvell wireless cards, Intel wireless cards, Atheros wireless cards
(both USB and integrated/PCI/PCIe)

How will Sugar Labs comply with the licenses of these firmwares?

I'm afraid I don't understand what the concern is here. "Sugar" isn't 
subject to anything different from a licensing perspective, and 
therefore under no obligation to "comply" with anything:


https://opensource.stackexchange.com/questions/8849/does-distributing-gpl-software-along-with-binary-image-force-the-binary-image-to

All of the firmware images packaged by Debian in the non-free repo is 
freely redistributable, but not open-source.


Fedora packages them, and includes them by default. Their LiveCDs/images 
work out of the box with them. Debian packages them, but does not 
install them by default, presumably out of ideological reticence.


Since the goal of the Debian Sugar LiveCD should be to work, 
transparently, on as many computers out-of-the-box as is possible, this 
would seemingly be an obvious improvement. It's not possible to install 
from this LiveCD on a ton of "modern" hardware (the machine I'm using is 
from 2011) with the current state of bundled packages. If the goal is to 
only allow it to function fully on machines which are incapable of 
functioning fully without binary firmware blobs, I'd argue that this 
should be disclosed during the installation process.

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SoaS] SOAS 33/34 Changes.

[Alex Perez]

I tested today's nightly rawhide of SoaS, and can confirm it behaves as 
expected/desired, with session auto-login. All activities start _except_ 
FotoToon.

Downloaded from 
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210113.n.0/compose/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-Rawhide-20210113.n.0.iso

SoaS raw-xz for armhfp (Raspberry Pi, etc) image at 
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210113.n.0/compose/Spins/armhfp/images/Fedora-SoaS-armhfp-Rawhide-20210113.n.0-sda.raw.xz

On 1/13/2021 2:39:25 AM, Chihurumnaya Ibiam  wrote:
Edit made, changes can be viewed in the SoaS download page 
[https://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Downloads].

--

Ibiam Chihurumnaya

ibiamchihurumn...@gmail.com [mailto:ibiamchihurumn...@gmail.com]



On Mon, Jan 11, 2021 at 7:07 PM Peter Robinson mailto:pbrobin...@gmail.com]> wrote:

On Mon, Jan 11, 2021 at 4:56 PM Chihurumnaya Ibiam
mailto:ibiamchihurumn...@gmail.com]> wrote:
>
> Hi Everyone,
>
> SOAS was failing to build in F34 due to telepathy-salut being deprecated and 
> needed as a dependency in sugar, F33 beta had an issue where startup goes 
> straight to login.
>
> Both have been fixed after today's compose was released and can be tested.
> Download here.
>
> I don't think it's wise to change the download link in our wiki to reflect 
> this - uploaded to sunjammer of course - as it's a compose image but Peter 
> can tell if it's wise to.

The link is for rawhide which is the nightly development snapshots, it
might be worthwhile putting a link for those interested in testing
that to know the state of SoAS for the next release and be able to
test issues with it and provide fixes, there's also an arm  nightly
image too.

___ SoaS mailing list 
s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Fwd: [Telepathy] ANNOUNCE: telepathy-glib 0.24.2

[Alex Perez]

FYI.



 Forwarded Message 
Subject:[Telepathy] ANNOUNCE: telepathy-glib 0.24.2
Date:   Thu, 4 Feb 2021 01:54:04 +0300
From:   Alexander Akulich 
To: telepathy 



The "Ages Later" release.

tarball: 
https://telepathy.freedesktop.org/releases/telepathy-glib/telepathy-glib-0.24.2.tar.gz
signature: 
https://telepathy.freedesktop.org/releases/telepathy-glib/telepathy-glib-0.24.2.tar.gz.asc
git: https://cgit.freedesktop.org/telepathy/telepathy-glib

Enhancements:

• Port build tools to Python 3 (Alexey Andreyev)
• Update and fix tests for Python 3 (Jakub Kulík)

Fixes:

• stop hardcoding python's path in .py scripts (fd.o #76495, Guillaume)
• fixed some code issues discovered by compiling with clang
 (fd.o #79006, Guillaume)
• replaced tp_verify_* with G_STATIC_ASSERTs, fixing the build with
 more recent gtk-doc (Simon)
• autogen.sh: run gtkdocize from $srcdir in out-of-source builds
 (fd.o #94391, Philip Withnall)
• tests: fix build failure with glib >= 2.46 due to duplicate test paths
 (fd.o #92245, George Kiagiadakis)
• tests: Fix a service file path to fix the build with installed tests
 (fd.o #90991, Philip Withnall)
• call-channel: fix a memory leak (Fabrice Bellet)
• debug-sender: fix messages queue locking (Fabrice Bellet)
• TpBasePasswordChannel: fix gtk-doc comment for finished signal
 (Ting-Wei Lan)
• protocol: fix a memory leak (Ivaylo Dimitrov)
• Fix a crash when creating a conference call (Martin Jones)
___
telepathy mailing list
telepa...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SLOBS] Belated meeting reminder

[Alex Perez]

Apologies for missing the meeting. It was my birthday, and my wife and I were 
out on the coast for the day.
On 6/9/2021 5:19:51 AM, Walter Bender  wrote:
We have a Sugar Labs oversight meeting today at 19:30 UTC (3:30 on the
US East Coast). We'll meet in the Matrix #sugar room. (Note that there
is a gateway from Liberachat's #sugar room.)

See you there.

-walter

--
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
SLOBs mailing list
sl...@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/slobs

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Announcement: Sugar on a Stick (SoaS) 34 released today

[Alex Perez]

Folks,

Fedora 34 was released today, which means that we've got a new release
of Sugar on a Stick 34, which includes Sugar 0.118, and can be
downloaded from:

https://dl.fedoraproject.org/pub/fedora/linux/releases/34/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-34-1.2.iso
 

It's one gigabyte in size.

..and written to any USB stick using BalenaEtcher, Fedora Imager Writer,
or whatever your favorite/preferred image writing tool is.


an installation image (non-live environment) for 32-bit ARM devices,
such as the Raspberry Pi 2-3, is also available at:

https://dl.fedoraproject.org/pub/fedora/linux/releases/34/Spins/armhfp/images/Fedora-SoaS-34-1.2.armhfp.raw.xz
The above image is 1.8 gigabytes.

Special thanks to Sugar Labs member and contributor Ibiam Chihurumnaya,
AKA 'chimosky', for co-maintaining many/most of these Fedora activities,
as well as the core Sugar Fedora packages, which, as a whole, make up
Sugar on a Stick.

Regards,
Alex Perez
Sugar Labs Contributor & Fedora Package Wrangler

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SoaS] Fedora has been branched, SoaS LiveUSB environment is up for testing

[Alex Perez]

James,

James Cameron wrote on 2/10/21 1:45 PM:
> On Wed, Feb 10, 2021 at 12:48:30PM -0800, Alex Perez wrote:
>> Folks,
>>
>> The Fedora 34 branch has happened, and there's a nightly build of SoaS,
>> based on Fedora 0.118, which I'd like to call on folks to test. There's
>> one known big bug, which will be fixed in the next couple of days, which
>> is that the Language control panel doesn't open/crashes, preventing you
>> from changing languages from the default English.
>>
>> All activities except FotoToon should start and work properly.
> So my release of v26 didn't help?
It just hasn't been updated on the Fedora package side, yet. That will
happen in a day or two.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Call for testing of Fedora 34 beta Sugar On A Stick

[Alex Perez]

Folks,

This is a call for testing of the upcoming Fedora 34 based Sugar on a Stick, 
which is now ready for testing on the following platforms:

For 64-bit PCs, the ISO can be downloaded from:

https://dl.fedoraproject.org/pub/alt/stage/34_Beta-1.3/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-34_Beta-1.3.iso
 
[https://dl.fedoraproject.org/pub/alt/stage/34_Beta-1.3/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-34_Beta-1.3.iso]


The installer based version of SoaS for 32-bit ARM can be downloaded from 
https://dl.fedoraproject.org/pub/alt/stage/34_Beta-1.3/Spins/armhfp/images/Fedora-SoaS-34_Beta-1.3.armhfp.raw.xz
 
[https://dl.fedoraproject.org/pub/alt/stage/34_Beta-1.3/Spins/armhfp/images/Fedora-SoaS-34_Beta-1.3.armhfp.raw.xz]

...and finally, we have a new variant of SoaS for 64-bit ARM devices, which is 
also installer-based, and available for download at 
https://dl.fedoraproject.org/pub/alt/stage/34_Beta-1.3/Spins/aarch64/images/Fedora-SoaS-34_Beta-1.3.aarch64.raw.xz
 
[https://dl.fedoraproject.org/pub/alt/stage/34_Beta-1.3/Spins/aarch64/images/Fedora-SoaS-34_Beta-1.3.aarch64.raw.xz]

Please test on real hardware if possible. All you need to do is download and 
write the image to a USB stick, with Fedora Media Writer, which can be 
downloaded from https://github.com/FedoraQt/MediaWriter/releases/tag/4.2.0 
[https://github.com/FedoraQt/MediaWriter/releases/tag/4.2.0]
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSoC 2021 aspirant

[Alex Perez]

Sourabha,

James Cameron wrote on 3/15/21 12:41 PM:
> Latest is Sugar 0.118.
>
> Etoys activity has not been ported to new shell or Python 3, so not
> surprising that it does not work yet.
We would welcome a port of eToys to GTK3+Python3, if you are willing to
pursue this. We'd be greatly appreciative.

Regards,
Alex Perez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] The future of Starchart and other "abandoned" GTK2/python2 activities

[Alex Perez]

Folks,

I'd like to start a conversation about the future of some activities, 
such as Starchart, which have unfinished/incomplete/un-tested ports to 
GTK3 and Python 3. The code for Starchart, for instance, is at 
https://github.com/sugarlabs/starchart and hasn't been given much love 
recently. There are three pending pull requests, one of which appears to 
be largely complete, from July of 2020: 
https://github.com/sugarlabs/starchart/pull/8


If someone would be willing to get this across the finish line by 
completing the port to GTK3, that would be a very good thing indeed. 
This activity was previously packaged in Sugar on a Stick Fedora spin, 
but has not built for several releases of Fedora, due to the above 
reasons.


If anyone else here has any activities they feel should be priorities 
for porting to GTK3 and/or Python 3, please feel free to pipe up and 
either volunteer to fix them, or just voice your opinion on which have 
value.


Thanks,
Alex Perez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Donations to SugarLabs

[Alex Perez]

Devin,

We can now accept donations via both Zelle (US only) and PayPal, by sending to 
donati...@sugarlabs.org

On 12/31/2021 6:25:40 AM, devin@ulibarri.website  wrote:
Hi,

I have been receiving many year-end fundraising emails from other orgs,
and this made me think of SugarLabs which is now an official non-profit
in the U.S.

I see this page for donations:
https://wiki.sugarlabs.org/go/Sugar_Labs/Donate

Is check the only method to receive donations?

(I send this email for the broader, long-term benefit, and general
awareness.)

Best,
Devin
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Sugar on a Stick (Fedora 35 spin) released

[Alex Perez]

Today, Fedora 35 has been released, and is available for download from 
https://download.fedoraproject.org/pub/fedora/linux/releases/35/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-35-1.2.iso

The above ISO is 946 megabytes, and can be written to a USB stick using Fedora 
Media Writer.


It's also available as a 32-bit ARM image, at 
https://mirrors.rit.edu/fedora/fedora/linux//releases/35/Spins/armhfp/images/Fedora-SoaS-35-1.2.armhfp.raw.xz
 91.9GB)



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SoaS] Fix Startup issue with F35 SOAS

[Alex Perez]

There's a fixed Fedora 35 SoaS ISO at 
http://download.sugarlabs.org/soas/Fedora-SoaS-Live-x86_64-F35-20220211.iso 
which I have confirmed is working as expected.


The above ISO is 1.2 gigabytes in size.

Chihurumnaya Ibiam wrote on 2/9/2022 12:37 PM:

Hi Everyone,

A fix for the fail to start issue on F35 SOAS has been fixed and 
deployed to F35, so an update on an F35 would get the fix, you can 
view the current stable versions for sugar-toolkit-gtk3 
.

--
Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com 



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Fedora 36 SoaS ISO spin beta ready for testing

[Alex Perez]

Hi folks,

The Fedora 36 beta was released earlier this week, and the SoaS spin is
ready for testing. This 860 megabyte ISO can be downloaded from:

https://download.fedoraproject.org/pub/fedora/linux/releases/test/36_Beta/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-36_Beta-1.4.iso

Any testing reports are appreciated. Please test on both bare metal and
in Virtual Machines, if possible.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Eager to work in fixing the UI of sugarizer.

[Alex Perez]

Anuj,

I appreciate your enthusiasm, and welcome. Before any UI re-design would
be considered, we would require detailed written analysis of what the
goals are for such a re-design, what's "wrong" with the current design,
and what your qualifications are for making what are largely subjective
changes. While everyone has opinions on UI design, engineers are often
infamous for designing awful user interfaces. Please share with us what
sorts qualifications you possess that would qualify you to make UI
design changes to Sugar/Sugarizer.

Have you ever used Sugar for more than a few hours, or a day? If so,
which elements do you feel should be changed? If you have not used Sugar
extensively, I would argue that you likely lack sufficient experience to
propose such changes.

The Sugar/Sugarizer UI was primarily designed for children of a specific
age range. Almost all design decisions stem from that basic premise.
Have you considered this?

Regards,
Alex Perez

MR. OPTIMIST wrote on 3/10/23 10:24 AM:
> Hello everyone !
>                  I am Anuj Verma from Maharashtra, India majoring in
> computer science and engineering.  I have worked in multiple projects
> and web applications including AI projects.
> I have checked the sugarizer, it's pretty good but I believe it's UI
> can be improved. Like we 
> can add links to words as well as icons, we can improve icons as well
> which is less user friendly(in my opinion).I have experience of
> working with many projects but have not worked on open source yet. I'm
> writing to seek further comments and be open to constructive feedback
> and criticism. Your response to this mail will be highly appreciated.
>

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel