Re: [Sugar-devel] [IAEP] [Announcement] Sugarizer v1.8 - 10th Anniversary edition - is available for your device

[Martin Abente Lahaye]

Congratulations !!

On Wed, Apr 10, 2024 at 4:11 PM Lionel Laské  wrote:

> Hi all,
>
> I'm proud to announce version 1.8 of Sugarizer (https://sugarizer.org),
> the leading learning platform for children. It's the 10th Anniversary
> edition: happy birthday Sugarizer!
>
> New in this version:
>
>- Chart Activity: Unleash your creativity and data prowess with the
>new Chart Activity. Organize your information in a visually appealing way.
>Choose the best chart for your data and make your presentation stand out.
>Try it now!
>
>
>- Word Puzzle in Exerciser:This new template in Exerciser activity
>empowers educators to create engaging word puzzles on the fly during
>lessons, providing a dynamic and interactive learning experience for
>students. With the ability to incorporate text, images, sounds,
>speech, or videos, the Word Puzzle template offers a new word experience
>for learners.
>
>
>- CSV file support: CSV format is now fully supported in Sugarizer.
>Open it from the Journal, easily export Measurements and Stopwatch
>activities data in CSV format. Plus, on Android and iOS, you can now
>copy any file from your device. Harness the flexibility and convenience of
>CSV today!
>
>
>- Rewrite of Chat activity:Experience a whole new level of interaction
>with our revamped Chat activity. It's simpler, more intuitive, and faster
>than ever before. Dive into seamless communication and enjoy the
>enhanced performance.
>
>
>- Improved stability: more than 30 fix and update on Sugarizer and
>activities.
>
>
>
> A short animation of these features is visible here:
> https://www.youtube.com/watch?v=m48JjH4EcPI
>
> A full description of Sugarizer activities with demo video, category and
> recommended age is available on https://sugarizer.org/activities.html
>
>
>
> We need your help to improve Sugarizer user experience and make it
> accessible to more users! Support Sugarizer on GitHub Sponsor [1] or
> Liberapay [2].
>
>
> Sugarizer 1.8  is available on your browser [3] but also for your
> Android, iOS, Linux, MacOS or Windows device. Download it from : Google
> Play [4], Amazon Store [5], Apple Store [6], F-droid [7], snapcraft [8]
> and if you don't like stores, you could also install it by yourself using
> instructions on the Sugarizer website [9].
>
> On Android, Sugarizer could also replace your launcher with Sugarizer OS
> [10].
>
> And if you want to deploy Sugarizer Server for your school, follow
> instructions here [11].
>
>
>
>Lionel Laské
>
>
> P.S.: Special thanks for their contribution on this version to Utkarsh
> Siddhpura and Vinayak Nayar. Many thanks also to all Google Summer of
> Code students and mentors who made this release possible.
>
>
>
>
>
> [1] https://github.com/sponsors/llaske
>
> [2] https://liberapay.com/llaske
>
> [3] http://try.sugarizer.org
>
> [4]
> https://play.google.com/store/apps/details?id=org.olpc_france.sugarizer
>
> [5] http://www.amazon.com/gp/product/B00NKK7PZA
>
> [6] https://itunes.apple.com/us/app/sugarizer/id978495303
>
> [7] https://f-droid.org/repository/browse/?fdid=org.olpc_france.sugarizer
>
> [8] https://snapcraft.io/sugarizer
>
> [9] https://sugarizer.org
>
> [10]
> https://play.google.com/store/apps/details?id=org.olpc_france.sugarizeros
>
> [11] https://github.com/llaske/sugarizer-server
>
>
> ___
> 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] Proposal for Flatpak port project

[Martin Abente]

Hi !

Thanks for sharing your proposal, I have read through it.

My recommendation is that you reconsider the activities you selected.
Especially those that require ports to Python 3 and GTK 3.

The reason is simple; porting these activities to Python 3 and GTK 3 is a
whole project in itself. Note that porting activities to Python 3 and GTK 3
requires more than just writing the code, e.g., testing, reviews, releases,
etc. That would take a significantly longer time (than a week, as per the
proposal) for a large activity such as TamTam.

Plus, you have to account for the time required to port these to Flatpak.

So, try to find activities that are already ported to Python 3 and GTK 3
and then analyze the project complexity to come up with a schedule that
would fit in the GSoC duration.

Regards,
Martín.

On Wed, Mar 27, 2024 at 5:26 PM Tech Shubham 
wrote:

> Hi everyone,
> I am attaching here my draft proposal for maintaining and porting Flatpak
> activities. Before finalizing it, I want to know your opinion on the
> selection of activities I've chosen to port. Please take a moment to review
> the proposal and share your thoughts.
> Thank you for your time and input.
> ___
> 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] Updating www-sugarlabs

[Martin Abente]

Hello everyone,

Can someone update sl.o ? I changed it months ago [1] to show our Flatpak
apps, but it seems these changes are not deployed yet.



Refs:
1.
https://github.com/sugarlabs/www-sugarlabs/commit/88bc4f1da48cd0eba2cc4072fdfc410629bdcc28
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [IAEP] Tom Gilliard

[Martin Abente Lahaye]

Very sad news. Just a few months ago, Tom was helping (and encouraging) me
with some projects I was working on.

We were very lucky to have him in our community, and he will be greatly
missed.



On Sun, Jul 26, 2020 at 4:48 PM Walter Bender 
wrote:

> I am saddened by the news that Tom Gilliard (satellit), long time Sugar
> contributor has passed away after a long illness.
>
> Tom was one of our most dedicated and diligent testers of Sugar builds (on
> a wide variety of GNU/Linux platforms) and a great advocate who will be
> missed.
>
> Tom's wife Virginia can be reached at sandykayak...@gmail.com
>
> -walter
>
> --
> Walter Bender
> Sugar Labs
> http://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

Re: [Sugar-devel] happy birthday Sugar Labs

[Martin Abente]

:D

On Fri, May 15, 2020 at 8:37 AM Walter Bender 
wrote:

> :)
>
> --
> 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] About Flatpak porting

[Martin Abente]

If you goal is to make Activities run as Flatpak (independently of Sugar
services) then you must do the port.

The port complexity varies depending on how many of these services are used
(and how big the dependency is). Best case scenario the port is just a 1
liner, worst case, it requires other adaptations.

On Tue, Mar 10, 2020 at 9:09 AM ayushman khurana <
khuranaayushman...@gmail.com> wrote:

> hi this is ayushman,
> i have been reading about flatpak porting using sugarapp.
> I want to ask if the porting is to be done for all the sugar apps or only
> those which needs to perform tasks like saving or retrieving data to and
> from journal .
>
> 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

Re: [Sugar-devel] Project: graphic design for resolution independence

[Martin Abente]

On Mon, Feb 24, 2020 at 8:50 PM James Cameron  wrote:

> Many older activities were designed for the 4:3 aspect ratio 1200x900
> pixel display of the original OLPC XO laptop, which had a button to rotate
> the screen by 90°.
>
> Now Sugar is being used on other laptops and computers with an aspect
> ratio of 16:9 and higher resolutions, and screen rotation may occur
> automatically.
>
> Display resolution may also change when an external display is plugged in.
>

It does, and since external displays don't necessary use the same
resolution as the primary one our current approach of
Gdk.Screen.width/height results in a very broken experience.

See
https://github.com/tchx84/sugarapp/blob/master/flatpak-guide-common-issues.md

The solution I am using for the Flatpak ports is to force activities to
display only on the primary monitor. I prepared a helper to make these
fixes a bit easier in sugarapp lib.

See https://github.com/tchx84/sugarapp/blob/master/sugarapp/helpers.py#L24

The project is to deploy a set of solutions specific to each activity;
>
> * for backgrounds; either redesign the background image for higher
> resolutions, or use tiling,
>
> * for game assets; either redesign the asset as a vector, or redesign for
> a higher resolution,
>
> * detect resolution changes and resize user interface elements,
>
> * test on all standard resolutions and 90° rotations.
>
> Technologies needed: PNG, SVG, Inkscape, git, Python, GTK, and Pygame.
>
> Skills needed: graphic design, software design, and software maintenance.
>
> --
> 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

Re: [Sugar-devel] Malicious code in dateutil

[Martin Abente]

*"The first is "python3-dateutil," which imitated the popular "dateutil"
library. The second is "jeIlyfish" (the first L is an I), which mimicked
the "jellyfish" library."*
If you read that carefully, it says these 2 libraries imitated the real
libraries. It does not say that the original libraries were compromised.

On Thu, Jan 23, 2020 at 7:50 PM Chihurumnaya Ibiam <
ibiamchihurumn...@gmail.com> wrote:

> Dateutil has been found to contain malicious code, a github search shows
> 10+ uses of dateutil in Sugar Labs repos.
>
> You can read more about it here
>
> https://www.zdnet.com/article/two-malicious-python-libraries-removed-from-pypi/
> ___
> 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] Mentors needed

[Martin Abente]

I just reviewed the port task with the longest wait time.

On Wed, Jan 15, 2020 at 6:48 PM James Cameron  wrote:

> Please help now.
>
> While I'm at linux.conf.au there is unmet need for mentors to respond to
> students on the Sugar tasks.
>
> Please check the task list for new tasks you are not mentors for, (turn
> off the "my tasks" slider button in the task list), and add yourself as
> mentor.
>
> Please check for pull requests on GitHub owned by the students you know
> of.  Some pull requests are not in the sugarlabs organisation; this is
> normal.
>
> Please check the GCI timeline; there's only a few days left.
>
> On the other hand, if your circumstances have changed and you can't
> provide the mentoring, let Walter and Ibiam know so you can be removed from
> the list.  Otherwise I'm sure Google's analysis after the event will
> classify you as inactive.
>
> --
>
>  @Quozl, sorry for this private message. I have a quite number of
> tasks for your review, but unfortunately, none of other mentors have been
> looking into my tasks, I have *-activity, *-activity, *-activity, and some
> other minor tasks left to be reviewed. As you are away right now, what
> would be your suggestion regarding this. Thanks :)
>
>  Urgently contact the other mentors; they are responsible for
> answering.  Do it by assigning to the task instance and writing a comment,
> once per six hours, until there is an answer.  I was afraid this would
> happen.  I had done too much work, set myself in front of everyone, and so
> everyone else has drawn back.  Sugar Labs is not very good at collective
> action.  You have to push them.  Ok?
>
>  Thanks for the reply @Quozl, Yes, In most of the task instances,
> you and chimosky are assigned as mentors, and other mentors keep telling
> there is too little time for them. I have started asssigning reviewers as
> Rahul Bothra, Martin, Walter and others. Idk if they would reply.  Ok, i
> will try doing as what you have said. thanks for your suggestion :)
>
> --
> 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

Re: [Sugar-devel] [IAEP] Oversight Board Elections 2019-21 has begun!

[Martin Abente]

Seems to work fine :)

In case someone has an unmanageable inbox like myself, just search for
"sugar labs election" and you should find it.

On Wed, Jan 15, 2020 at 7:24 PM Chihurumnaya Ibiam <
ibiamchihurumn...@gmail.com> wrote:

> Agreed, I didn't make the suggestion earlier as I'm part of the people who
> have access to the alias, kindly remove every one who's a candidate from
> the alias.
>
> On Wed, Jan 15, 2020, 10:53 PM James Cameron  wrote:
>
>> Thanks Vipul.
>>
>> It works, I voted.
>>
>> Please add memb...@sugarlabs.org and sl...@lists.sugarlabs.org to the
>> election results destination?  This will be more transparent.  We had
>> memb...@sugarlabs.org on the results destination in previous years.
>>
>> On Wed, Jan 15, 2020 at 11:21:13PM +0530, Vipul Gupta wrote:
>> > Hello folks,
>> > The Oversight Board election 2019-21 is upon us. In your inboxes, you
>> would
>> > have received a unique email from CIVS or [1]c...@cs.cornell.edu with
>> the
>> > options to poll for the candidates.
>> >
>> > The poll is open from 15th January 2020 to 31st January 2020. You can
>> find more
>> > information on the candidates here [2]https://wiki.sugarlabs.org/go/
>> > Oversight_Board/2019-2021-candidates.
>> >
>> > Please check your spam folders or promotions if you can't find it. Add
>> the
>> > email address to your contact list and mark as not spam when you find
>> it.
>> > As always, looking forward to hearing any questions you all would have.
>> Do cast
>> > your vote!
>> >
>> > Best,
>> > Vipul Gupta
>> > [3]Mixster | [4]Github
>> >
>> > References:
>> >
>> > [1] mailto:c...@cs.cornell.edu
>> > [2] https://wiki.sugarlabs.org/go/Oversight_Board/2019-2021-candidates
>> > [3] https://mixstersite.wordpress.com/
>> > [4] https://github.com/vipulgupta2048
>>
>> > ___
>> > IAEP -- It's An Education Project (not a laptop project!)
>> > i...@lists.sugarlabs.org
>> > http://lists.sugarlabs.org/listinfo/iaep
>>
>>
>> --
>> 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

Re: [Sugar-devel] why cannot most of sugar apps be packaged as flatpacks?

[Martin Abente]

Hello Thomas,

I am actually working on packaging sugar apps with flatpak, and publushing
them in Flathub. See
https://blogs.gnome.org/tchx84/2019/11/22/linux-app-summit-2019-and-sugar-learning-tools/

The work goes beyond just packaging, but also doing some porting so the
experience is properly integrated into the desktop paradigm.

I still just getting started, but I am getting ready to have some GCI tasks
as well.

On Mon, Nov 25, 2019 at 10:35 AM Thomas Gilliard 
wrote:

>  this is silverblue f32 1119 has Turtleblocks 220 etoys and
> labyrinth 0.6 as flatpacks
>  why cannot most of sugar apps be packaged as flatpacks?
> Google tasks? walterbender?
>  https://wiki.sugarlabs.org/go/Fedora_32#Silverblue
>  using system 76 laptop with it installed
>  #flatpack #silverblue
>
> ___
> 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] [RELEASE] Sugar Live Build 20191002 with Sugar 0.116 and Python 3

[Martin Abente]

Pretty amazing James!

On Wed, Oct 2, 2019 at 3:34 AM James Cameron  wrote:

> Announcing Sugar Live Build with Sugar 0.116 and the Fructose activity
> set, ported to Python 3.  It can be used for testing Sugar quickly and
> easily.
>
> 1.  boot from hard drive, flash drive, and optical media,
> automatically starting Sugar without persistence,
>
> 2.  or install as a virtual machine, with persistence and password
> protection,
>
> 3.  based on the Debian 10 Buster Live Build,
>
> 4.  for developers, contains all build dependencies, configured source
> trees (git clones in /usr/src), and binaries (make install) for the
> Sugar 0.116 Sucrose modules and the Fructose activity set,
>
> 5.  contains a backport of Metacity 3.34,
>
> 6.  does not contain Debian Sugar packages,
>
> Download from
> http://people.sugarlabs.org/~quozl/sugar-live-build-20191002/
>
> You must already know how to use an ISO9660 operating system
> installer.  For more details, see the Debian Live project.
>
> --
> 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

Re: [Sugar-devel] Sugar Labs 2017-2019 Oversight Board Election Results

[Martin Abente]

If it helps, the subject of the email I got was "Poll: Sugar Labs 2017
Oversight Board Election" and I got it from "c...@cs.cornell.edu".

On Tue, Oct 17, 2017 at 11:53 AM, Devin Ulibarri 
wrote:

> Samson Goddy:
> > c...@cs.cornell.edu and samsongo...@gmail.com. but it is more likely to
> be
> > the first email.
>
> Nothing from either of those emails on my end, BTW.
> ___
> 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] [Sugarlabs-vote] [Important / Importante] Plazo para votar termina mañana! / Deadline to vote ends tomorrow!

[Martin Abente]

Good reminder!

2017-10-14 12:37 GMT-03:00 Laura Vargas :

> [English]  [Español más abajo]
>
>
> Greetings, Sugar Labs members!
>
> This is a reminder that the deadline for voting on the 2017-2019
> <2017%202019> Oversight Board ends tomorrow *October 15, 2017*.
>
> If you have not yet voted please *locate your ballot in your inbox*: it
> was sent on October 3, 2017 with the following subject:
>
> Poll: Sugar Labs 2017 Oversight Board Election
>
> Sort the candidates according to your preference and send your vote.
>
> Remember that your participation is important because according to our
> current model of Governance, the Project Oversight Board is in charge of
> the Sugar Labs Project Management.
>
>
> *Membership and Elections Committee*
> Sugar Labs Project
>
>
> [Español]
>
> Saludos miembros de Sugar Labs!
>
> La presente para recordarles que el plazo para votar en las elecciones
> para la Junta de Supervisión para el periodo 2017-2019 <2017%202019>
> termina mañana *15 de Octubre de 2017.*
>
> Si aún no has votado por favor *ubica tu balota de votación en la bandeja
> de entrada de tu correo electrónico*: la balota fué enviada el dia 3 de
> Octubre de 2017 con el asunto:
> Poll: Sugar Labs 2017 Oversight Board Election
> Ordena los candidatos según tu preferencia y envia tu voto.
>
> Recuerda que tu participación es importante pues de acuerdo a nuestro
> actual modelo de Gobernancia, la Junta de Supervisión del Proyecto está a
> cargo de la Administración del Proyecto Sugar Labs.
>
>
> *Comité de Membresía y Elecciones*
> Proyecto Sugar Labs
>
>
> ___
> Sugarlabs-vote mailing list
> sugarlabs-v...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugarlabs-vote
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [RELEASE] Sugar-Artwork 0.111-libre unstable

[Martin Abente]

On Sat, Sep 16, 2017 at 8:52 AM, Sebastian Silva 
wrote:

>
> On 16/09/17 03:31, Chihurumnaya Ibiam wrote:
>
> Sebastian, do you mind me saying/assuming that you're bringing this up
> because James released 0.111 and you think it has something to do with
> OLPC?.
>
> *Ibiam Chihurumnaya*
>
>
> Hi Ibiam,
>
> Thanks for your interest! It inspires us to continue to make a stand for
> users such as yourself.
>
> Yes it is a reaction to an arbitrary release process by an employee of
> this laptop vendor.
>
> I would like to add that while I think it is likely that *every* current
> and former employee of it, is an *excellent person* individually, and we
> have sincere appreciation for their work, *as an organization*, they've
> been erratic at best.
>
> In fact it is not even clear who they are (Inc? Association? Foundation?)
> - yet we have remained branded with their logo.
>
> Sugar Labs has a duty to protect downstream users, developers and vendor
> freedom, and to remain *truly *neutral to hardware providers.
>
> Happy Software Freedom Day everyone!
>

So much freedom in a software where one developer tries to impose his views
because he is (admittedly) pissed off at another developer and because he
"thinks he is right". A tainted celebration for our community, at best.


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

Re: [Sugar-devel] [RELEASE] Sugar-Artwork 0.111-libre unstable

[Martin Abente]

Another unilateral action from Sebastian, and a unprecedented new low.

This "release" cannot be taken seriously.


On Fri, Sep 15, 2017 at 1:23 PM, Christian Stroetmann <
stroetm...@ontolab.com> wrote:

> Hello Walter
>
> I did not knew the history, so please dump my related points 1, 2, 3, and
> 4.
>
> What I am wondering now is the fact that OLPC licensed its trademark under
> the GPL, which from my point of view would mean that they have given up its
> trademark rights already respectively it makes no sense anymore to keep it
> in the trademark register because any other entity could demand its
> deleting from the trademark register by referring to this GPL licensing.
>
>
>
>
> Best regards
> Christian Stroetmann
>
>
> Thank you for your synopsis.  I think you make good points. However, I
> think the situation is further complicated by the fact that OLPC released
> Sugar Artwork under the GPL prior to the creation of Sugar Labs.  I defer
> to our lawyer at SFC, to sort through this on our behalf.
>
> Regards.
>
> Walter
>
> On Sep 15, 2017 12:39 PM, "Christian Stroetmann" 
> wrote:
>
>> Hello Everybody
>>
>> I followed the discussion about the OLPC logo with great interest. Sadly
>> to say, I was already running out of popcorn last month.
>>
>> First of all, someone in this threat said the right things about
>> trademarks. I would like to add the following points:
>> 1. The OLPC logo is a trademark and as long as Sugarlabs has no written
>> allowance to use it the alleged legal problem exists indeed. But ...
>> 3. OLPC has tolerated the use since 2006 and did not change its position
>> after OLPC and Sugarlabs departed. What is developing in this case is a
>> so-called customary right, which means that Sugarlabs might already have
>> the right to use the OLPC logo. I would recommend that OLPC and Sugarlabs
>> get together, pay the fee together, and care for the trademark against
>> misuse together.
>> 2. Furthermore, one of the most important points when handling an
>> infringement of a trademark right is how the broad public (e.g. 65% of a
>> representative group as accepted by a judge) interprets a
>> sign/logo/trademark and connects it to an entity (e.g. person,
>> organization, corporation) respectively is answering the question if a
>> confusion of the broad public between the trademark owner and the trademark
>> user does exist. The latter might be the case with every logo that is an
>> abstraction of the Vitruvian (see da Vinci) in the case of the OLPC logo
>> and an abstraction or clipart of a foot in the case of the Gnome logo.
>> 4. As far as I have noticed it, the OLPC logo is used as a functional
>> icon of the Graphical User Interface (GUI) and hence it is covered by the
>> GPL in an illegal way. Sugarlabs is not allowed to impose any other license
>> on signs/logos/trademarks that it does not own, is not allowed explicitly
>> to use in this way, or has no copyright for.
>> 5. I like the OX logo because it is a nice abstraction of the Vitruvian
>> and similar graphics. Nevertheless, an alternative logo or this function
>> that allows to select an individual logo by the users might be interesting
>> as well.
>> 6. As far as I noticed, there are children on this mailing list, too, and
>> everybody should be an ideal for them when discussing and solving problems.
>> Somehow, this does not always work as it should do. ;)
>>
>>
>>
>> Best regards
>> Christian Stroetmann
>>
>> Thank you Sebastian,
>>
>> This debug was long time due. Now Sugar can be called "Libre" :D
>>
>> I honestly didn't ever like the OLPC logo icon and the new feet are very
>> cute!
>>
>>
>> Regards
>>
>>
>> 2017-09-15 10:08 GMT-05:00 Sebastian Silva :
>>
>>> Hello Sugar friends,
>>>
>>> I am assuming the responsibility of making a new release of
>>> Sugar-Artwork package featuring the omission of a Trademarked logo.
>>>
>>> To avoid conflicts with incumbent parties, I have not increased the
>>> version number, instead I have tagged the release as 0.111-libre.
>>>
>>> https://download.sugarlabs.org/sources/sucrose/glucose/sugar
>>> -artwork/sugar-artwork-0.111-libre.tar.xz
>>>
>>> *This release comes with a stern warning to downstream distributors and
>>> users, that the XO computer icon is trademarked and, in the absence of a
>>> suitable (trademark) license, it constitutes a risk to downstream
>>> developers and deployments.*
>>> Regards,
>>>
>>> Sebastian
>>>
>>> ___
>>> Sugar-devel mailing list
>>> Sugar-devel@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>>
>>
>>
>> --
>> Laura V.
>> * I SomosAZUCAR.Org*
>>
>> “Solo la tecnología libre nos hará libres.”
>> ~ L. Victoria
>>
>> Happy Learning!
>> #LearningByDoing
>> #Projects4good
>> #IDesignATSugarLabs
>> #WeCanDoBetter
>>
>>
>>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> 

Re: [Sugar-devel] logo dicussion

[Martin Abente]

On Thu, Sep 14, 2017 at 10:27 AM, Laura Vargas 
wrote:

>
> 2017-09-14 8:52 GMT-05:00 Samuel Cantero :
>
>>
>> On Thu, Sep 14, 2017 at 8:32 AM Laura Vargas 
>> wrote:
>>
>>> 2017-09-14 7:23 GMT-05:00 Walter Bender :
>>>


 On Thu, Sep 14, 2017 at 8:09 AM, Laura Vargas 
 wrote:

>
>
> 2017-09-14 7:00 GMT-05:00 Samson Goddy :
>
>>
>>
>> On Sep 14, 2017 12:52 PM, "Laura Vargas" 
>> wrote:
>>
>>
>>
>> 2017-09-14 6:36 GMT-05:00 Samson Goddy :
>>
>>> I didn't wanted to reply earlier because i wanted to be sure what
>>> the discussion was all about. I perfectly understand Sebastian worries. 
>>> But
>>> as walter mention Sugar Labs was a spinoff of OLPC and that is why the 
>>> logo
>>> is still present. Now, what i think we should do is to ask SLOBS if we 
>>> want
>>> to make these changes, make a good logo, the present one from Sebastian 
>>> is
>>> good but it is similar to Gnome logo. So we should calm them design a 
>>> new
>>> one that if SLOBS approve the chnages.
>>>
>>> As for me, leaving the XO logo from Sugar is a smart move to
>>> marketing, our goal is to make Sugar available to all users not just 
>>> OLPC
>>> by doing that we should have Sugar OS logo to make things neutral.
>>>
>>> Sebastian, since you co-sign the agreement could you please take my
>>> suggestions and make things official by take it to SLOBS make design 
>>> open
>>> for members to agree on a design because the current one for me is not
>>> acceptable.
>>>
>>
>> Samson,
>>
>> Old trademarked OLPC logo is gone now.
>>
>> If you think the one proposed by Sebastian is "not acceptable" you
>> must explain your reasons. For me it is.
>>
>> Very similar to Gnome logo
>>
>
> I was chating here with my Gnome friends and we have come to a tag
> line:
>
> "To jump in one foot you must firts learn to stand up in two"
>
> She loved it!
>
>
>> As I have said earlier, am all for a Sugar Marathon Design. You in?
>>
>> Sugar Marathon Design??
>>
>> We don't we do an Open Logo competition online and share with members
>> for our users to design good logo, reflecting what sugar is. Like how 
>> Sugar
>> Labs logo came alive.
>>
>
> Am all for open dynamics still I prefer collaborative dynamics rather
> than competitive ones.
>
> A Sugar Design Marathon can be done if it is the Board will, by asking
> all community members to synchronize for ~15 intensive days with a design
> team from active volunteers and contributors.
>
> I look forward to see Community working together productively.
>
> What do you think?
>

 I think that (1) we should resolve the status of the XO icon before
 rushing into anything and (2) it would seem that the role of SLOB would be
 to ask the design team to do its job, not to do it for them.


>>> No offense Walter but I was asking Samson not you.
>>>
>>
>> What a childish and unpolite response.
>>
>
> ...
>
> Samuel,
>
> You are totally entitled your opinion.
>
>

If everyone would start acting like you and Sebastian are doing now, this
community would be severely damaged.

You are setting a terrible precedent, and this has to stop.


>
> Samson,
>
> *Now that the feet are Sugar interface main icon the legal thing is
> resolved.*
>

>
> If Community wants to support the Sugar Design Marathon to upgrade it I
> volunteer to help you lead the effort. I think we should start working on a
> formal proposal to present to SLOBs asap.
>
> Main objective proposed would be:
>
> - To define in a collaborative way the adoption of a new main icon for
> Sugar interface according to Sugar Labs acceptable License Policy
> .
>
> Specific tasks needed to do:
> - Debug all learning and marketing materials
> - Add yours here..
>
> Calendar proposed would be:
> Oct 1-15 2017
>
> Please confirm/unconfirm your interes and/or suggest changes to my
> proposal.
>
> Regards
>
> Laura
>
> --
> Laura V.
> * I SomosAZUCAR.Org*
>
> “Solo la tecnología libre nos hará libres.”
> ~ L. Victoria
>
> Happy Learning!
> #LearningByDoing
> #Projects4good
> #IDesignATSugarLabs
> #WeCanDoBetter
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SLOBS] [SLOB] xo-computer icon

[Martin Abente]

On Thu, Sep 14, 2017 at 7:40 AM, Laura Vargas  wrote:

> Walter,
>
> Nobody needs to be a lawyer to understand this.
>
> *We (sugar labs users) simply didn't have permission to do use therefore
> it was removed.*
>
>
> Any one else interested in Sugar UI in the Community is welcome to join
> forces and help me address this issue as an opportunity for the Community
> to work together engaging in a Collaborative Design Dynamic and if required
> define a more suitable substitute for Sebastian's commit.
>

How can you say "work together" and "engaging in a Collaborative design"
while Sebastian just pushed to master his own design unilaterally. Revert
it, and then someone might take this invitation seriously.


>
> I personally love the feet. They set a clear starting point for the Sugar
> experience and they look very cute. Try it changing the colors here, see
> how it looks:
>
> http://laboratoriosazucar.org/azucarizador/
>
> My young children really liked them, also several teachers in SM.
>
> I will test further among our programming students as well.
>
>
> Regards
>
> 2017-09-14 6:08 GMT-05:00 Walter Bender :
>
>>
>>
>> On Wed, Sep 13, 2017 at 10:18 PM, Laura Vargas 
>> wrote:
>>
>>> Legislation in Latinamerica is very restrictive regarding Trademark
>>> policies.
>>>
>>> If OLPC fans want to keep the old logo in their own version of Sugar
>>> that is OK, but not possible in the main branch.
>>>
>>
>> Laura,
>>
>> I would appreciate you stop you speculations and assertions about
>> trademark law and let Tony do his job. He asked some very specific
>> questions. I would appreciate that you try to address them.
>>
>> regards.
>>
>> -walter
>>
>>>
>>> Regards
>>>
>>> 2017-09-13 19:48 GMT-05:00 Walter Bender :
>>>
 As probably most of you are aware, yesterday one of our community
 members unilaterally changed the xo-computer icon in sugar-artwork. The
 ensuing discussion about the change is in the github pull request, "Urgent
 fix logos", [1]

 The gist of his concern is that OLPC has a trademark on the XO artwork
 [2] and there was concern that we were infringing and consequently
 downstream users would also be infringing.

 As Sean Daly points out, this is not the first time that the topic has
 come up [3, 4]. "In the past, OLPC was amenable to the use of the xo
 logo in Sugar, but asked we not use it in marketing materials without a
 formal co-branding licensing agreement."

 Personally, I think that OLPC was explicit in making the Sugar artwork
 available under a GPL licence and that this is hence moot. But I am not
 qualified to make that assessment. Consequently, I asked Adam Holt, our SFC
 liaison, to raise the issue with the legal team. Tony asked us to consider
 the following questions:

 1) Why is the XO logo included in the sugar-artwork repo now -- and
 does the SLOBs want to keep it there?
 2) Assuming the SLOBs want to keep the XO logo in sugar-artwork:  what
 outcome would the SLOBs *prefer* to see happen?  E.g.,
 - Does Sugar want downstream users to be able to redistribute and
 modify Sugar's codebase with or without the XO trademark file included in
 the program?
 - Does the SLOBs want downstream users to be able to modify and
 redistribute the XO trademark image itself, or is that less important to
 Sugar?

 The answer to the first part of Tony's first question is that the XO
 logo was part of Sugar from the very beginning -- before Sugar Labs was
 split from OLPC. We've never changed it.

 Regarding the second part: does the SLOBs want to keep it there?  is
 something we  need to discuss. Personally, I think it serves its purpose
 well -- a childcentric interface and it is "iconic" of Sugar. I see no
 reason to change it.

 Regarding Tony's second question, I would want downstream users to have
 as much freedom as possible: to use or not use the XO icon as they choose.
 However, I don't see the need to expand beyond the context of Sugar. If
 someone downstream wants to use the artwork for some other purpose, that is
 not our issue (although I that the GPL license would be the relevant
 determinant.)

 What do others think?

 Note, I think we should defer the discussion of what we would use as
 replacement artwork until we resolve the current issue.

 regards.

 -walter

 [1]  https://github.com/sugarlabs/sugar-artwork/pull/96
 [2]  http://www.trademarkia.com/xo-78880051.html
 [3]  http://lists.sugarlabs.org/archive/iaep/2008-December/003059.html
 [4] http://lists.sugarlabs.org/archive/iaep/2011-October/014245.html

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

 

Re: [Sugar-devel] logo dicussion

[Martin Abente]

On Thu, Sep 14, 2017 at 6:59 AM, Laura Vargas  wrote:

>
>
> 2017-09-14 5:40 GMT-05:00 Gonzalo Odiard :
>
>> Samuel,
>> You are right (Laura Vargas is Sebastian Silva wife).
>>
>
> You guys have to get over the fact that we are a married couple. We are 2
> happy long time Sugar Labs contributors.
>
> You cannot be discriminated us in any way for our marital status.
>
>
>
> *If you or anyone else want to support a Trademarked logo are welcome to
> do it not in Sugar main branch.*
>

You are wrong Laura (so is Sebastian), the process is just as important as
the issue you are supposedly trying to address. Making these decisions
unilaterally can damage the community and the project.


>
> Regards,
>
> --
> Laura V.
> * I SomosAZUCAR.Org*
>
> “Solo la tecnología libre nos hará libres.”
> ~ L. Victoria
>
> Happy Learning!
> #LearningByDoing
> #Projects4good
> #IDesignATSugarLabs
> #WeCanDoBetter
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] logo dicussion

[Martin Abente]

I noticed that my PR review and merged by Ignacio, but it later was
reverted by Sebastian again. Looks like if I send another PR, this will
keep happening, and i just want to point out that this is VERY scary,
having one person unilaterally making these decisions.

This is wrong.

On Wed, Sep 13, 2017 at 9:22 PM, Martin Abente <
martin.abente.lah...@gmail.com> wrote:

>
>
> On Wed, Sep 13, 2017 at 5:02 PM, Sean DALY <sdaly...@gmail.com> wrote:
>
>> In the past, OLPC was amenable to the use of the xo logo in Sugar, but
>> asked we not use it in marketing materials without a formal co-branding
>> licensing agreement. [1,2]
>>
>> The proposed feet logo is likely a violation of the GNOME Foundation
>> trademark, more info on their site [3].
>>
>
> If the feet logo could be a violation of the GNOME trademark, then lets
> revert it, until a proper replacement is found (and if its really needed,
> of course).
>
> https://github.com/sugarlabs/sugar-artwork/pull/97
>
>
>>
>> Sean.
>>
>> 1. http://lists.sugarlabs.org/archive/iaep/2008-December/003059.html
>> 2. http://lists.sugarlabs.org/archive/iaep/2011-October/014245.html
>> 3. https://wiki.gnome.org/action/show/FoundationBoard/Resources
>> /LicensingGuidelines?action=show=Foundation%2FLic
>> ensingGuidelines
>>
>>
>> On Wed, Sep 13, 2017 at 2:33 PM, Walter Bender <walter.ben...@gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Wed, Sep 13, 2017 at 2:25 PM, Laura Vargas <la...@somosazucar.org>
>>> wrote:
>>>
>>>> Am attaching the previous brand icon Trademark just for reference.
>>>>
>>>
>>> The question is more complex than whether or not OLPC received a
>>> trademark. Was it ever applicable to our use in Sugar? Is it still valid?
>>> Note that "a failure to enforce a trademark by monitoring the mark for
>>> misuses will result in a weakening of the mark and loss of distinctiveness,
>>> which can lead to a loss of the trademark." [1] Sugar Labs has been using
>>> xo-computer.svg and has never, as far as I know, received any notification
>>> that we are infringing. I don't know the answers to these questions, which
>>> is why I asked that our lawyer look into it.
>>>
>>> [1] https://www.justia.com/intellectual-property/trademarks/enforcement/
>>>
>>> regards.
>>>
>>> -walter
>>>
>>>>
>>>>
>>>>
>>>> 2017-09-13 13:16 GMT-05:00 Laura Vargas <la...@somosazucar.org>:
>>>>
>>>>> Hi Alex,
>>>>>
>>>>> Yes Sugar user interface needed to urgently get rid of any Trademark
>>>>> at all. We can breath now :D
>>>>>
>>>>> If you don't like the feet feel free to propose a new option or a
>>>>> dynamic for our Community to accomplish a new one collaboratively.  I
>>>>> really like the cute little finger color's.
>>>>>
>>>>> See how it looks here:
>>>>>
>>>>> http://laboratoriosazucar.org/azucarizador/
>>>>>
>>>>> There is still an urgent need for 111.1 Sugar release including this
>>>>> change.
>>>>>
>>>>> Am not sure whether or not Sugar Labs has currently a release Manager.
>>>>>
>>>>> Maybe if we propose a "Christmas Edition" for 111.1 I'll get to
>>>>> inspire some heroes to help us out.
>>>>>
>>>>> It would be ideal, if we can also add some other critical features
>>>>> required like the elimination of the male/female initial question.
>>>>>
>>>>>
>>>>> Regards
>>>>>
>>>>> Laura
>>>>>
>>>>> 2017-09-13 12:06 GMT-05:00 Alex Perez <ape...@alexperez.com>:
>>>>>
>>>>>> 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 <walter.ben...@gmail.com>
>>>>>> 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 

Re: [Sugar-devel] logo dicussion

[Martin Abente]

On Wed, Sep 13, 2017 at 5:02 PM, Sean DALY  wrote:

> In the past, OLPC was amenable to the use of the xo logo in Sugar, but
> asked we not use it in marketing materials without a formal co-branding
> licensing agreement. [1,2]
>
> The proposed feet logo is likely a violation of the GNOME Foundation
> trademark, more info on their site [3].
>

If the feet logo could be a violation of the GNOME trademark, then lets
revert it, until a proper replacement is found (and if its really needed,
of course).

https://github.com/sugarlabs/sugar-artwork/pull/97


>
> Sean.
>
> 1. http://lists.sugarlabs.org/archive/iaep/2008-December/003059.html
> 2. http://lists.sugarlabs.org/archive/iaep/2011-October/014245.html
> 3. https://wiki.gnome.org/action/show/FoundationBoard/
> Resources/LicensingGuidelines?action=show=Foundation%
> 2FLicensingGuidelines
>
>
> On Wed, Sep 13, 2017 at 2:33 PM, Walter Bender 
> wrote:
>
>>
>>
>> On Wed, Sep 13, 2017 at 2:25 PM, Laura Vargas 
>> wrote:
>>
>>> Am attaching the previous brand icon Trademark just for reference.
>>>
>>
>> The question is more complex than whether or not OLPC received a
>> trademark. Was it ever applicable to our use in Sugar? Is it still valid?
>> Note that "a failure to enforce a trademark by monitoring the mark for
>> misuses will result in a weakening of the mark and loss of distinctiveness,
>> which can lead to a loss of the trademark." [1] Sugar Labs has been using
>> xo-computer.svg and has never, as far as I know, received any notification
>> that we are infringing. I don't know the answers to these questions, which
>> is why I asked that our lawyer look into it.
>>
>> [1] https://www.justia.com/intellectual-property/trademarks/enforcement/
>>
>> regards.
>>
>> -walter
>>
>>>
>>>
>>>
>>> 2017-09-13 13:16 GMT-05:00 Laura Vargas :
>>>
 Hi Alex,

 Yes Sugar user interface needed to urgently get rid of any Trademark at
 all. We can breath now :D

 If you don't like the feet feel free to propose a new option or a
 dynamic for our Community to accomplish a new one collaboratively.  I
 really like the cute little finger color's.

 See how it looks here:

 http://laboratoriosazucar.org/azucarizador/

 There is still an urgent need for 111.1 Sugar release including this
 change.

 Am not sure whether or not Sugar Labs has currently a release Manager.

 Maybe if we propose a "Christmas Edition" for 111.1 I'll get to inspire
 some heroes to help us out.

 It would be ideal, if we can also add some other critical features
 required like the elimination of the male/female initial question.


 Regards

 Laura

 2017-09-13 12:06 GMT-05:00 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
>
>


 --
 Laura V.
 * I SomosAZUCAR.Org*

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

 Happy Learning!
 #LearningByDoing
 #Projects4good
 #IDesignATSugarLabs
 #WeCanDoBetter

>>>
>>>
>>>
>>> --
>>> Laura V.
>>> * I SomosAZUCAR.Org*
>>>
>>> “Solo la tecnología libre nos hará libres.”
>>> ~ L. Victoria
>>>
>>> Happy Learning!
>>> #LearningByDoing
>>> #Projects4good
>>> #IDesignATSugarLabs
>>> #WeCanDoBetter
>>>
>>> ___
>>> 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
>>
>>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>

Re: [Sugar-devel] logo dicussion

[Martin Abente]

Regardless of the separate trademark discussion, I still don't understand
why someone just decided to change the logo and merged it even though
several people asked him not to (without proper discussion, and not even
knowing if its really necessary).

On Wed, Sep 13, 2017 at 2:33 PM, Walter Bender 
wrote:

>
>
> On Wed, Sep 13, 2017 at 2:25 PM, Laura Vargas 
> wrote:
>
>> Am attaching the previous brand icon Trademark just for reference.
>>
>
> The question is more complex than whether or not OLPC received a
> trademark. Was it ever applicable to our use in Sugar? Is it still valid?
> Note that "a failure to enforce a trademark by monitoring the mark for
> misuses will result in a weakening of the mark and loss of distinctiveness,
> which can lead to a loss of the trademark." [1] Sugar Labs has been using
> xo-computer.svg and has never, as far as I know, received any notification
> that we are infringing. I don't know the answers to these questions, which
> is why I asked that our lawyer look into it.
>
> [1] https://www.justia.com/intellectual-property/trademarks/enforcement/
>
> regards.
>
> -walter
>
>>
>>
>>
>> 2017-09-13 13:16 GMT-05:00 Laura Vargas :
>>
>>> Hi Alex,
>>>
>>> Yes Sugar user interface needed to urgently get rid of any Trademark at
>>> all. We can breath now :D
>>>
>>> If you don't like the feet feel free to propose a new option or a
>>> dynamic for our Community to accomplish a new one collaboratively.  I
>>> really like the cute little finger color's.
>>>
>>> See how it looks here:
>>>
>>> http://laboratoriosazucar.org/azucarizador/
>>>
>>> There is still an urgent need for 111.1 Sugar release including this
>>> change.
>>>
>>> Am not sure whether or not Sugar Labs has currently a release Manager.
>>>
>>> Maybe if we propose a "Christmas Edition" for 111.1 I'll get to inspire
>>> some heroes to help us out.
>>>
>>> It would be ideal, if we can also add some other critical features
>>> required like the elimination of the male/female initial question.
>>>
>>>
>>> Regards
>>>
>>> Laura
>>>
>>> 2017-09-13 12:06 GMT-05:00 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


>>>
>>>
>>> --
>>> Laura V.
>>> * I SomosAZUCAR.Org*
>>>
>>> “Solo la tecnología libre nos hará libres.”
>>> ~ L. Victoria
>>>
>>> Happy Learning!
>>> #LearningByDoing
>>> #Projects4good
>>> #IDesignATSugarLabs
>>> #WeCanDoBetter
>>>
>>
>>
>>
>> --
>> Laura V.
>> * I SomosAZUCAR.Org*
>>
>> “Solo la tecnología libre nos hará libres.”
>> ~ L. Victoria
>>
>> Happy Learning!
>> #LearningByDoing
>> #Projects4good
>> #IDesignATSugarLabs
>> #WeCanDoBetter
>>
>> ___
>> 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
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [IAEP] Sugar Digest 2017-09-12

[Martin Abente Lahaye]

On Tue, Sep 12, 2017 at 12:59 PM, Walter Bender 
wrote:

> It has been a long time since I last wrote a Sugar Labs community new
> blog. I got tied up with my day jobs: starting a new design college from
> scratch and launching a new research center at MIT. (And, frankly, I was a
> bit depressed following the deaths of Marvin Minsky and Seymour Papert.) I
> have a breather on both fronts and given all of the Sugar activity of late,
> I am inspired to do some writing.
>
> 1. A footnote from Google Code-in 2015. Ezequiel Pereira, one of the
> grand-prize recipients from Sugar Labs was recently acknowledged by Google
> for discovering a security bug. He got some nice press, e.g., [1, 2]. In
> one article [3], he was quoted as saying: "Homework is boring. Looking for
> bugs is fun.” Ezequiel is one of a generation of children in Uruguay who
> grew up with Sugar. It is nice to hear the occasional word about their
> accomplishments.
>
> 2. We just wrapped up Google Code-in and Outreachy 2017. We had 9 interns
> supported by Google and 1 Outreachy intern. You can read about their
> accomplishments in their blogs [4] and in the meeting logs [5] (every
> Monday from May through August). Highlights from the summer include a new,
> easy-to-maintain activity portal and a new www.sugarlabs.org, both going
> live soon. Also of note: a new Sugar image for Raspberry Pi, some new apps,
> GTK3 ports, a Sugarizer dashboard, and a major overhaul of Music Blocks.
>
> Tip of the hat to our mentors: Abhijit Patel, Cristina Del Puerto, Devin
> Ulibarri, Hrishi Patel, Ignacio Rodriguez, José Argüello, Lionel Laské,
> Matias Baez, Michaël Ohayon, Samson Goddy, Samuel Cantero, and Tony
> Anderson. Lionel help me adminsister the program again this year. It is
> nice to note that many of the mentors are fomer GCI participants.
>
> Cristina, Michaël, and Samson will be representing Sugar Labs at the
> annual mentor summit at Google in October. (For those of you who have been
> following the saga of Samson's visa, I am happy to say that he was
> approved!)
>
>
:claps: :claps: :claps:


> 3. I was invited to represent Sugar Labs at the Plan Ceibal 10th
> anniversary in Montevideo a few months ago. It was great to see children
> still using Sugar 10  years after the first deployment in a small school in
> the Florida Department. It was also an opportunity to catch up with many
> old friends and Sugar contributors, including Ignacio, Andres, Alan, Jose
> Miguel, Guzman, etc. I am not sure if my talk is on line, but I wrote a
> paper based on the talk which is available for download [6].
>
> 4. Lionel just announced a new release of Sugarizer (v0.9). See [7] for
> all of the details.
>
> 5. James Cameron is working towards the release of Sugar 0.111, our first
> new release in nearly one year. It is mostly planned as a maintenance
> release.
>
> 6. There are only a few more days left (15 Sept.) to register as a
> candidate for the Sugar Labs oversight board. Please consider joining the
> board as we need some fresh voices and perspectives. See [8] for details.
> You also have until 27 Sept. to register as a member in order to be given a
> vote in the election. See [9] for details.
>
> 7. One of the first decisions the new board will be making is whether or
> not Sugar Labs should apply for GCI 2017. I am hopeful that the board will
> see the merits of the program and give a green light to apply again this
> year. If we do apply, I will be looking for mentors, project ideas, and a
> co-administrator. Please contact me if you are interested.
>
> regards.
>
-walter
>
> 
>
> [1] https://thenextweb.com/google/2017/08/10/highschool-
> security-research-google-data/#.tnw_5BETRGWT
> [2] https://www.theregister.co.uk/2017/08/10/schoolboy_google_
> bug_bounty_http_host/
> [3] http://abcnews.go.com/Lifestyle/google-awards-
> uruguay-high-school-student-10k-finding/story?id=49249604
> [4] https://wiki.sugarlabs.org/go/Summer_of_Code
> [5] http://meeting.sugarlabs.org/sugar-meeting/meetings
> [6] http://www.um.es/ead/red/54/bender.pdf
> [7] http://sugarizer.org
> [8] https://wiki.sugarlabs.org/go/Oversight_Board/2017-2019-candidates
> [9] https://wiki.sugarlabs.org/go/Sugar_Labs/Members
>
> --
> Walter Bender
> Sugar Labs
> http://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

Re: [Sugar-devel] Felicitaciones a Ezequiel !!

[Martin Abente]

wow!!

On Tue, Aug 15, 2017 at 4:49 PM, James Cameron  wrote:

> Indeed, well done Ezequiel.
>
> --
> 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] ASLO not working?

[Martin Abente]

Hey guys,

Is there something wrong with ASLO? The website is up but no activities are
displayed.

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

Re: [Sugar-devel] (no subject)

[Martin Abente]

Just ask what you need ! :)

On Wed, Jun 8, 2016 at 10:24 AM, samson goddy 
wrote:

> what type of help do you need?
>
> --
> From: rnezferrei...@gmail.com
> Date: Wed, 8 Jun 2016 10:23:09 -0400
> To: sugar-devel@lists.sugarlabs.org
> Subject: [Sugar-devel] (no subject)
>
> How can I get help here?
>
> ___ 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] Help us translating sugar

[Martin Abente]

Hello!

This is a reminder that we still have time to complete translations
until February
9th!

I take this opportunity to thank *Tymon Radzil*, *Edgar Quispe Chambi*
and *Robert
Antoni Buj Gelonch*, for completing the Polish, Aymara and Catalan
translations (respectively).

Regards,
Martin.

On Mon, Feb 1, 2016 at 2:09 PM, Tymon Radzik <dwg...@gmail.com> wrote:

> Hello Martin,
> I have translated entire sugar package to Polish language, so it is ready
> to be attached into release :)
> I'm gonna spread a word about this action to my friends, who also know
> other languages.
> Best regards,
> Tymon
>
> pon., 1.02.2016 o 03:10 użytkownik Martin Abente <
> martin.abente.lah...@gmail.com> napisał:
>
>> Hello everyone,
>>
>> I spent this weekend making sure that our translation platform [1] was
>> running fine and I updated the templates for sugar and sugar-toolkit-gtk3
>> projects. Compared to the last release, there are *only 97 new words *to
>> be translated in sugar [2].
>>
>> I also completed the Spanish translations [3], but the more we complete
>> the better, so *we need your help*! We have time until February 9th, so
>> I can merge the changes and do basic QA at least before the 0.108 release.
>>
>> *Spread the word!*
>>
>> Thanks,
>> Martin.
>>
>> Refs:
>> [1] http://translate.sugarlabs.org/
>> [2] http://translate.sugarlabs.org/projects/sugar/
>> [3]
>> https://github.com/sugarlabs/sugar/commit/8a08aa604df7434e9581bfaf021fa4305093cf9d
>>
> --
> Z poważaniem,
> Tymon Radzik
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Help us translating sugar

[Martin Abente]

Many thanks to those who contacted me offering for help, just a couple
recommendations:

1. Create your account in our platform [1].
2. Contact me to provide the name of your user and the languages are you
willing to translate.
3. Please use our platform to do the actual translation. The .po files in
the code are not up to date, only those in our platform.

Refs:
[1] http://translate.sugarlabs.org/


On Mon, Feb 1, 2016 at 4:07 AM, James Cameron  wrote:

> Create an account on http://translate.sugarlabs.org/ and let it guide
> you through work that is waiting.
>
> To assist with core Sugar translation, focus on
> http://translate.sugarlabs.org/projects/sugar/
>
> On Mon, Feb 01, 2016 at 12:20:52PM +0530, Utkarsh Tiwari wrote:
> > Hi,
> >  I would like to come forward. Could you please guide me how to
> proceed ?
>
> --
> James Cameron
> http://quozl.netrek.org/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Help us translating sugar

[Martin Abente]

Hello everyone,

I spent this weekend making sure that our translation platform [1] was
running fine and I updated the templates for sugar and sugar-toolkit-gtk3
projects. Compared to the last release, there are *only 97 new words *to be
translated in sugar [2].

I also completed the Spanish translations [3], but the more we complete the
better, so *we need your help*! We have time until February 9th, so I can
merge the changes and do basic QA at least before the 0.108 release.

*Spread the word!*

Thanks,
Martin.

Refs:
[1] http://translate.sugarlabs.org/
[2] http://translate.sugarlabs.org/projects/sugar/
[3]
https://github.com/sugarlabs/sugar/commit/8a08aa604df7434e9581bfaf021fa4305093cf9d
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Stable release deadline, translations and exceptional bug fixes

[Martin Abente]

February 13, will be.

On Sat, Jan 23, 2016 at 10:55 AM, Martin Abente <
martin.abente.lah...@gmail.com> wrote:

> Hello everyone,
>
> According to our roadmap [1] we are supposed to release our stable version
> on February 1st, which is basically in a week.
>
> Even though we are not far in terms of what we wanted to achieve for this
> release, I honestly think we are not quite ready yet. The main reasons are:
>
>- We definitely need more time than a week to QA translations, at
>least for the main languages that we (developers) usually support 
> ourselves.
>- There are still a couple patches I believe would be worth
>considering, specially [2] to give Sam and Walter more flexibility with the
>collaboration wrapper.
>
> Therefore, I am considering to move the release date to February 6th (or
> even another week later), but first let me know what you think.
>
>
>
> Martin.
>
> Refs:
> 1. https://wiki.sugarlabs.org/go/0.108/Roadmap
> 2. https://github.com/sugarlabs/sugar/pull/621
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Announcing] UNSTABLE 0.107.2 release (API, UI and Strings freeze)

[Martin Abente]

The search box allows the user to type e.g. "turtle" and then launch e.g.
Turtle Blocks activity, I think is very useful.

On Sun, Jan 24, 2016 at 11:35 AM, Tony Anderson <tony_ander...@usa.net>
wrote:

> Some confusion probably caused by not reading the proposals for this
> release. I was not aware there was a search box in the Home View. What is
> its
> function?
>
> Currently, the XO palette is open when the Home View appears. This is
> presumably a bug and not a feature which will be fixed by putting the focus
> on the search box. I hope this new search box has a sufficiently useful
> function for all XOs to justify this grab for attention.
>
> The problem with the palette is that it is modal and no action can be
> taken on the keyboard (e.g. switch to Journal or Neighborhood View or look
> at Frame) until the cursor is moved. This, of course, requires one more
> step in 'onboarding' to make users aware of the disabling nature of modal
> dialogs.
>
> Tony
>
>
> On 01/23/2016 05:27 PM, Martin Abente wrote:
>
> Hello everyone,
>
> I am pleased to announce the release of Sugar 0.107.2 (unstable). This
> release means that we have reached the API, UI and Strings freeze deadline
> [1] and that we should focus on making sure there are no missing
> translations or exceptional bugs left.
>
> This release comes with the following improvements:
>
>- Collaboration works on newer systems (e.g. Fedora 23) with
>activities that do not use Tubes (e.g. Chat).
>- The search box in home view grabs focus automatically.
>- More little steps on documenting our toolkit.
>
> The tarballs can be downloaded from:
>
>-
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.107.2.tar.xz
>-
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.107.2.tar.xz
>-
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.107.2.tar.xz
>-
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.107.2.tar.xz
>-
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.107.2.tar.xz
>
>
> Special thanks to Sam Parkinson, Nick DeFilippis and our Google Code-In
> students for his contributions, and to James Cameron and Gonzalo Odiard for
> the reviewing work.
>
>
> Regards,
> Martin.
>
> Refs:
> [1] https://wiki.sugarlabs.org/go/0.108/Roadmap
>
>
> ___
> Sugar-devel mailing 
> listSugar-devel@lists.sugarlabs.orghttp://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

[Sugar-devel] Stable release deadline, translations and exceptional bug fixes

[Martin Abente]

Hello everyone,

According to our roadmap [1] we are supposed to release our stable version
on February 1st, which is basically in a week.

Even though we are not far in terms of what we wanted to achieve for this
release, I honestly think we are not quite ready yet. The main reasons are:

   - We definitely need more time than a week to QA translations, at least
   for the main languages that we (developers) usually support ourselves.
   - There are still a couple patches I believe would be worth considering,
   specially [2] to give Sam and Walter more flexibility with the
   collaboration wrapper.

Therefore, I am considering to move the release date to February 6th (or
even another week later), but first let me know what you think.



Martin.

Refs:
1. https://wiki.sugarlabs.org/go/0.108/Roadmap
2. https://github.com/sugarlabs/sugar/pull/621
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] [Announcing] UNSTABLE 0.107.2 release (API, UI and Strings freeze)

[Martin Abente]

Hello everyone,

I am pleased to announce the release of Sugar 0.107.2 (unstable). This
release means that we have reached the API, UI and Strings freeze deadline
[1] and that we should focus on making sure there are no missing
translations or exceptional bugs left.

This release comes with the following improvements:

   - Collaboration works on newer systems (e.g. Fedora 23) with activities
   that do not use Tubes (e.g. Chat).
   - The search box in home view grabs focus automatically.
   - More little steps on documenting our toolkit.

The tarballs can be downloaded from:

   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.107.2.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.107.2.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.107.2.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.107.2.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.107.2.tar.xz


Special thanks to Sam Parkinson, Nick DeFilippis and our Google Code-In
students for his contributions, and to James Cameron and Gonzalo Odiard for
the reviewing work.


Regards,
Martin.

Refs:
[1] https://wiki.sugarlabs.org/go/0.108/Roadmap
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [IAEP] Default Collaboration Server

[Martin Abente]

It should be fine for 0.108, also, I think OLPC images had been doing the
same think for ages now.

On Mon, Jan 18, 2016 at 12:46 PM, Walter Bender 
wrote:

> +1  The privacy argument is a strong one.
>
> -walter
>
> On Mon, Jan 18, 2016 at 5:14 AM, Sam P.  wrote:
>
>> Hi All,
>>
>> Currently Sugar defaults to using "jabber.sugarlabs.org" as a
>> collaboration server in Sugar on a Stick and other GNU distros (fedora,
>> debian, etc.).  However, I propose that we change the default (this
>> release!) to use the local network (telepathy salut).  This is a feature is
>> that is already in sugar, and is used on XOs and normal computers.
>>
>> Why?
>>
>> * Better activity support.  Tubes are supported by salut, but not by
>> gabble (server based collab.).  This means that activities that haven't
>> been ported this cycle (most of them) will still work under salut (proposed
>> default), but will not work under gabble (current default)
>>
>> * More contextual neighbourhood view.  You only see people on your local
>> WiFi (or wired) network.  This is more helpful for finding your friends
>> than the trawling the crowded jabber.sugarlabs.org neighbourhood.
>>
>> * More features.  File transfers work via salut, but not via
>> jabber.sugarlabs.org
>>
>> * More speed and less lag.  Jabber.sugarlabs.org is hosted in the mit.
>> While that is good if you are a student at the mit, it is very laggy if you
>> are in say Australia.  I prefer near instant collaberation provided by my
>> local network.  Even if you are at the mit, your wifi router is still
>> closer than jabber.sugarlabs.org (hopefully)
>>
>> * Privacy.  Users (specifically kids) aren't by default sharing their
>> names and colours online and inviting others to send them things.
>>
>> Is this ok?  Will defaulting to use salut (local network) cause any
>> issues for anyone?  Is this ok for the 108 cycle?
>>
>> Thanks,
>> Sam
>>
>> ___
>> IAEP -- It's An Education Project (not a laptop project!)
>> i...@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/iaep
>>
>
>
>
> --
> 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

[Sugar-devel] Delaying the 107.2 release for a week

[Martin Abente]

Hello everyone,

We had planned to do our next 107.2 release today [1], but we are still
behind with some code reviews. Therefore, I think it would be good to delay
this release for a week, so we can catch up.

The 107.2 release is going to happen on 01/23.

Regards,
Martin.

Refs:
[1] http://wiki.sugarlabs.org/go/0.108/Roadmap
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Current status of collaboration work

[Martin Abente]

Hey Sam,

I checked your PR but I think I found a simpler way [1] to handle this. The
logic goes like this:

1. assume you have tubes.
2. if everything goes OK, then you do have tubes.
3. but, if tubes creation fails, and the reason is lack of support, then
you don't have tubes (sort of detection), and let process to continue.

This achieves the exact same thing, and does not require new config values.

What do you think?

Martin.

Refs
[1] https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/297

On Mon, Dec 28, 2015 at 6:05 PM, James Cameron <qu...@laptop.org> wrote:

> On Mon, Dec 28, 2015 at 02:37:20PM -0300, Martin Abente wrote:
> > @Sam:
> >
> >   • Using GSettings is definitely a decent workaround instead of going
> for
> > detection, I checked your PR and I will send some comments, but we
> will
> > have to push it for as a feature freeze exception / Bug Fix.
> >   • I don't agree we should add it to the toolkit yet, still too early
> to set
> > API on stones, but lets make a good use of that Wrapper of yours.
> Thanks
> > for making it available.
> >   • Collaboration should be transparent for Activities, and since Tubes
> is no
> > longer available in at least one scenario (jabber), we can't really
> > depending on it anymore.
> >
> > @Tony:
> >
> >   • As Sam explained, this is not something _we_ control. Telepathy
> dropped
> > Tubes years ago. There is no way to "workaround" the fact that Tubes
> in
> > gone and we gotta move to something else, but for now we will also
> keep
> > Tubes for those who can still use it and at least be able to do the
> > transition.
> >
> > @Gonzalo:
> >
> >   • Thanks for the feedback, you are right, collaboration is hard to
> test, so
> > we can't rush here.
> >
> > @James C.:
> >
> >   • Telepathy developers knew Sugar was using still it, I even heard they
> > warned us in a GUADEC conference years ago, I also heard they
> apologized in
> > advanced.
> >   • I am against introducing one deprecated piece of Telepathy code into
> Sugar
> > code, simply because we can barely catch up with our own code base
> and it
> > would be even worse if we adopt that code.
> >   • Aside from that, Walter and Sam tests show that there are many cases
> where
> > we can simply migrate other channels. It will take longer, but is
> the right
> > investment IMHO.
> >   • The Tubes issue is just as critical as any other "we can't catch up
> with
> > upstream" issue but, this time, we are trying not to ignore it.
> >   • Any comments regarding the use of a GSettings entry to re-enable
> Tubes
> > support (and leave it disabled by default)?
> >   • Funny picture.
>
> No worries, thanks for taking the decisions.
>
> >
> > @Walter:
> >
> >   • I agree, lets move forward.
> >
> > @Jonas:
> >
> >   • I hope so too.
> >
> > Martin.
>
> --
> James Cameron
> http://quozl.netrek.org/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Announcing] UNSTABLE 0.107.1 release (feature freeze)

[Martin Abente]

@peter: the plan is to disable tubes channel by default so collaboration
does not break in newer systems (with newer telepathy-gabble), but allow
older systems to re-enable it if they still use older telepathy-gabble.
Also, we plan to include this for the next release of 0.107 so we can test
it properly before the stable 0.108 release.

On Mon, Jan 4, 2016 at 8:04 AM, Sam P.  wrote:

> Hi Tony,
>
> This is serious.  If an activity wants to work in collaboration mode on a
> NEW version of telepathy gabble, it needs to be ported not to use tubes.
>
> However, your activity will still work on OLPC OS 13/14, Fedora 21 and
> before and on the current Debian (???).  Your activity will still work
> everywhere in single user mode.
>
> Thanks,
> Sam
>
> On Mon, Jan 4, 2016 at 9:40 PM, Tony Anderson 
> wrote:
>
>> Hi,
>>
>> Is this serious? No current activities will run on 0.107.
>>
>> Tony
>>
>> On 01/04/2016 04:55 AM, Peter Robinson wrote:
>>
>>> TL;DR  All activities need to be ported, and there will be a very small
>>> >toolkit change.  The toolkit change has not yet landed.
>>>
>>
>> ___
>> 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

[Sugar-devel] [Announcing] UNSTABLE 0.107.1 release (feature freeze)

[Martin Abente]

Hello everyone,

Moving forward with our current development cycle, I am pleased to announce
the release of Sugar 0.107.1 (unstable). This release means that we have
officially passed the time [1] for including new features and that we must
start focusing on stability and bug fixing.

This release comes with many improvements that are worth mentioning:

   - Changing the Frame settings in the control panel no longer requires to
   restart Sugar.
   - Added new keyboard controls to access and navigate the control panel.
   - The control panel can display the serial number for commodity
   hardware.
   - Multiple bundles can be installed at once using good old
   sugar-install-bundle script.
   - The shell now claims file transfer channels so Empathy won't interfere
   anymore.
   - Home views names can be changed now.
   - Neighborhood icons are no longer placed randomly.
   - Sugar can now start even when the disk is full.
   - More documentation for our gtk3 toolkit.
   - More fixes for the Sugar theme.
   - and even more [2].

Kudos to James Cameron, Sam Parkinson, Ezequiel Pereira, Batchu Venkat
Vishal and our Google Code-In students who are responsible for these
contributions, and to Gonzalo Odiard, Ignacio Rodriguez and Julio Reyes for
the reviewing work.

The tarballs for this release can be downloaded from:

   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.107.1.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.107.1.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.107.1.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.107.1.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.107.1.tar.xz


*Please help us testing it!*

Regards,
Martin.

Refs:
[1] http://wiki.sugarlabs.org/go/0.108/Roadmap
[2] http://wiki.sugarlabs.org/go/0.108/Feature_List
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Current status of collaboration work

[Martin Abente]

*@Sam:*

   - Using GSettings is definitely a decent workaround instead of going for
   detection, I checked your PR and I will send some comments, but we will
   have to push it for as a feature freeze exception / Bug Fix.
   - I don't agree we should add it to the toolkit yet, still too early to
   set API on stones, but lets make a good use of that Wrapper of yours.
   Thanks for making it available.
   - Collaboration should be transparent for Activities, and since Tubes is
   no longer available in at least one scenario (jabber), we can't really
   depending on it anymore.

*@Tony:*

   - As Sam explained, this is not something _we_ control. Telepathy
   dropped Tubes years ago. There is no way to "workaround" the fact that
   Tubes in gone and we gotta move to something else, but for now we will also
   keep Tubes for those who can still use it and at least be able to do the
   transition.

*@Gonzalo:*

   - Thanks for the feedback, you are right, collaboration is hard to test,
   so we can't rush here.

*@James C.:*

   - Telepathy developers knew Sugar was using still it, I even heard they
   warned us in a GUADEC conference years ago, I also heard they apologized in
   advanced.
   - I am against introducing one deprecated piece of Telepathy code into
   Sugar code, simply because we can barely catch up with our own code base
   and it would be even worse if we adopt that code.
   - Aside from that, Walter and Sam tests show that there are many cases
   where we can simply migrate other channels. It will take longer, but is the
   right investment IMHO.
   - The Tubes issue is just as critical as any other "we can't catch up
   with upstream" issue but, this time, we are *trying* not to ignore it.
   - Any comments regarding the use of a GSettings entry to re-enable Tubes
   support (and leave it disabled by default)?
   - Funny picture.


*@Walter:*

   - I agree, lets move forward.


*@Jonas:*

   - I hope so too.


Martin.

On Sat, Dec 26, 2015 at 11:05 PM, James Simmons  wrote:

> Tony,
>
> I have been lurking on these mailing lists for the past few years but
> haven't made any contribution to Sugar in that time. You may recall that I
> wrote a couple of FLOSS manuals for OLPC, and strangely enough that led me
> away from the project, because it convinced me I had a future as an author.
> I've written and published a few books since then, none of which have found
> as big an audience as the two FLOSS manuals did.
>
> After reading your recent emails, I see that one of my FLOSS manuals is on
> its way to being out of date, and my Sugar Activities are getting there
> too. I'd like to fix that. I don't know how much time I'll have to devote
> to this, but I want to do it.
>
> I'd like to know more about this Tubes wrapper to start with. Is there
> anything I can read to start learning about it?
>
> James Simmons
>
>
>
>
> ___
> 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] Current status of collaboration work

[Martin Abente]

Hello everyone,

I have been reviewing the current state of the collaboration proposals and
I am afraid it is still too early for merging it. We need to explore more
use cases, and this will only happens when we start porting more Activities
that actually use TUBES. Therefore, i want to share some thoughts on this.

*Opinions:*

   1. There haven't been enough changes in the Activities regarding Tubes
   deprecation.
   2. Dropping the Tubes support from Sugar without changing all the
   activities that depend on Tubes means that we will break collaboration for
   those activities anyway, and there wont be much gain by just doing that.
   3. Making changes in the Sugar API without proper testing with more
   activities (and scenarios) is simply not a good idea.
   4. But, making changes in the Activities can be easily handled since
   they are self contained.
   5. Most of our users still use Fedora 18 through OLPC deployments, where
   Tubes is available.

*Suggestions:*

   1. Lets make Sugar handle the Tubes deprecation better so it doesn't
   break, but lets not remove the support for TUBES yet.
   2. Instead, we can start changing the activities using the Wrapper that
   Walter and Sam prepared, but using it locally on each Activity for now.
   3. Once and if, we have most of our activities ported to the new
   telepathy API (which will be based on the Wrapper), then we can include the
   Wrapper into sugar-toolkit-gtk3, in a next release and remove it from
   Activities.

*Pros:*

   1. We avoid breaking collaboration for *(a)* Activities that use TUBES
   and run on older systems where TUBES is available, and *(b)* Activities
   that does not use TUBES on newer systems where TUBES is no longer
   available. This _is_ an improvement versus the current situation where is
   completely broken on newer systems.
   2. We do this whole re-work incrementally, without having to change the
   API (sort of) blindly.
   3. There will be more flexibility to explore ideas in Activities land.

*Cons:*

   1. There will be repeated code in Activities, but that can be changed
   easily later.


*What would be needed:*

   1. To detect if there is TUBES support, as Sam mentioned in his first PR
   [1]. *Can someone look into this?*
   2. Do not create TUBES channel when there is not support. This [2] is
   just a hack and the logic works fine, but it depends on whether or not we
   can detect support.
   3. Cleanup the Wrapper and make sure that it is possible to use it
   locally in activities.

*Other improvements that we could land now:*

   1. Give more flexibility to activities to use file transfer channels
   without having the shell messing with them. [3]

*Conclusions:*

If we don't do something about this, next Sugar releases will still be
broken for collaboration, for more scenarios than necessary.


Let me know what you guys think,
Martin.

*Refs:*
[1] https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/270
[2]
https://github.com/tchx84/sugar-toolkit-gtk3/commit/bed0ac5f4259ff1669323db26acb27f5d9c8ed1f
[3] https://github.com/sugarlabs/sugar/pull/621
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Feature Freeze deadline around the corner

[Martin Abente]

Hello everyone,

We are a week away from the Feature Freeze deadline [1] and we still got a
couple PRs queued [2,3]. I haven't been able to catch up with _all_ the
recent PRs, so if there anything you want me to prioritize please let me
know.

I would prefer to look at the collaboration bits but, except for Sam's and
Walter's contributions, there is still a lot activities that needs to be
corrected. I think we should at least try to merge the basics for handling
the deprecation of Tubes, gracefully.


Let me know what you think,

Martin.


Refs:
[1] http://wiki.sugarlabs.org/go/0.108/Roadmap
[2] https://github.com/sugarlabs/sugar-toolkit-gtk3/pulls
[3] https://github.com/sugarlabs/sugar/pulls
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar Activities not working on Ubuntu

[Martin Abente]

https://codein.withgoogle.com/dashboard/tasks/4659526686998528/

On Mon, Dec 14, 2015 at 1:51 PM, Martin Abente <
martin.abente.lah...@gmail.com> wrote:

> will do!
>
> On Sun, Dec 13, 2015 at 7:45 PM, Walter Bender <walter.ben...@gmail.com>
> wrote:
>
>> Sounds like a job for GCI :)  Martin: Can you write something up?
>>
>> On Sun, Dec 13, 2015 at 5:42 PM, James Cameron <qu...@laptop.org> wrote:
>>
>>> Agreed.
>>>
>>> Saw similar on Ubuntu 15.10 last week; this was failing;
>>>
>>> import locale
>>> locale.setlocale(locale.LC_ALL, '')
>>>
>>> Documentation says it can fail.  If an activity or toolkit doesn't
>>> handle failure, I think it needs to be fixed.
>>>
>>> On Sun, Dec 13, 2015 at 05:03:20PM -0500, Walter Bender wrote:
>>> > Hmm. Shouldn't locale revert to en_US if the locale is not found?
>>> Seems like a
>>> > Sugar/Sugar toolkit bug.
>>> >
>>> > On Sun, Dec 13, 2015 at 4:40 PM, James Cameron <[1]qu...@laptop.org>
>>> wrote:
>>> >
>>> > You are using sugar-build?  It seems so, because your screenshot
>>> has
>>> > an Ubuntu desktop view.
>>> >
>>> > In your logs, the following activities failed because of your en_NG
>>> > language choice: Calculate, Moon, Measure, Pippy, Record, Turtle
>>> > Blocks, and Speak.
>>> >
>>> > But many activities worked fine.
>>> >
>>> > An example from the Moon activity:
>>> >
>>> > Traceback (most recent call last):
>>> >   File "/usr/bin/sugar-activity", line 169, in 
>>> > main()
>>> >   File "/usr/bin/sugar-activity", line 164, in main
>>> > instance = create_activity_instance(activity_constructor,
>>> > activity_handle)
>>> >   File "/usr/bin/sugar-activity", line 42, in
>>> create_activity_instance
>>> > activity = constructor(handle)
>>> >   File "/usr/share/sugar/activities/Moon.activity/moon.py", line
>>> 90, in
>>> > __init__
>>> > activity_button = ActivityToolbarButton(self)
>>> >   File
>>> "/usr/lib/python2.7/dist-packages/sugar/activity/widgets.py", line
>>> > 75, in __init__
>>> > icon = _create_activity_icon(activity.metadata)
>>> >   File
>>> "/usr/lib/python2.7/dist-packages/sugar/activity/widgets.py", line
>>> > 45, in _create_activity_icon
>>> > bundle = ActivityBundle(get_bundle_path())
>>> >   File
>>> "/usr/lib/python2.7/dist-packages/sugar/bundle/activitybundle.py",
>>> > line 72, in __init__
>>> > linfo_file = self._get_linfo_file()
>>> >   File
>>> "/usr/lib/python2.7/dist-packages/sugar/bundle/activitybundle.py",
>>> > line 141, in _get_linfo_file
>>> > lang = locale.getdefaultlocale()[0]
>>> >   File "/usr/lib/python2.7/locale.py", line 543, in
>>> getdefaultlocale
>>> > return _parse_localename(localename)
>>> >   File "/usr/lib/python2.7/locale.py", line 475, in
>>> _parse_localename
>>> > raise ValueError, 'unknown locale: %s' % localename
>>> > ValueError: unknown locale: en_NG
>>> >
>>> > On Fri, Dec 11, 2015 at 05:29:42PM +0100, samson goddy wrote:
>>> > > here are the logs
>>> > >
>>> > >
>>> >
>>>  
>>> ━━━
>>> > > Date: Fri, 11 Dec 2015 12:57:01 -0300
>>> > > From: [2]martin.abente.lah...@gmail.com
>>> > > To: [3]samsongo...@hotmail.com
>>> > > CC: [4]sugar-devel@lists.sugarlabs.org
>>> > > Subject: Re: [Sugar-devel] Sugar Activities not working on Ubuntu
>>> > >
>>> > > Hey Samson,
>>> > >
>>> > > Are you using this [1]? Can you send the logs? Check in
>>> ~/.sugar/default/
>>> > logs/
>>> > >
>>> > > Regards,
>>> > > Martin.
>>> > >
>

Re: [Sugar-devel] Sugar Activities not working on Ubuntu

[Martin Abente]

will do!

On Sun, Dec 13, 2015 at 7:45 PM, Walter Bender 
wrote:

> Sounds like a job for GCI :)  Martin: Can you write something up?
>
> On Sun, Dec 13, 2015 at 5:42 PM, James Cameron  wrote:
>
>> Agreed.
>>
>> Saw similar on Ubuntu 15.10 last week; this was failing;
>>
>> import locale
>> locale.setlocale(locale.LC_ALL, '')
>>
>> Documentation says it can fail.  If an activity or toolkit doesn't
>> handle failure, I think it needs to be fixed.
>>
>> On Sun, Dec 13, 2015 at 05:03:20PM -0500, Walter Bender wrote:
>> > Hmm. Shouldn't locale revert to en_US if the locale is not found? Seems
>> like a
>> > Sugar/Sugar toolkit bug.
>> >
>> > On Sun, Dec 13, 2015 at 4:40 PM, James Cameron <[1]qu...@laptop.org>
>> wrote:
>> >
>> > You are using sugar-build?  It seems so, because your screenshot has
>> > an Ubuntu desktop view.
>> >
>> > In your logs, the following activities failed because of your en_NG
>> > language choice: Calculate, Moon, Measure, Pippy, Record, Turtle
>> > Blocks, and Speak.
>> >
>> > But many activities worked fine.
>> >
>> > An example from the Moon activity:
>> >
>> > Traceback (most recent call last):
>> >   File "/usr/bin/sugar-activity", line 169, in 
>> > main()
>> >   File "/usr/bin/sugar-activity", line 164, in main
>> > instance = create_activity_instance(activity_constructor,
>> > activity_handle)
>> >   File "/usr/bin/sugar-activity", line 42, in
>> create_activity_instance
>> > activity = constructor(handle)
>> >   File "/usr/share/sugar/activities/Moon.activity/moon.py", line
>> 90, in
>> > __init__
>> > activity_button = ActivityToolbarButton(self)
>> >   File
>> "/usr/lib/python2.7/dist-packages/sugar/activity/widgets.py", line
>> > 75, in __init__
>> > icon = _create_activity_icon(activity.metadata)
>> >   File
>> "/usr/lib/python2.7/dist-packages/sugar/activity/widgets.py", line
>> > 45, in _create_activity_icon
>> > bundle = ActivityBundle(get_bundle_path())
>> >   File
>> "/usr/lib/python2.7/dist-packages/sugar/bundle/activitybundle.py",
>> > line 72, in __init__
>> > linfo_file = self._get_linfo_file()
>> >   File
>> "/usr/lib/python2.7/dist-packages/sugar/bundle/activitybundle.py",
>> > line 141, in _get_linfo_file
>> > lang = locale.getdefaultlocale()[0]
>> >   File "/usr/lib/python2.7/locale.py", line 543, in getdefaultlocale
>> > return _parse_localename(localename)
>> >   File "/usr/lib/python2.7/locale.py", line 475, in
>> _parse_localename
>> > raise ValueError, 'unknown locale: %s' % localename
>> > ValueError: unknown locale: en_NG
>> >
>> > On Fri, Dec 11, 2015 at 05:29:42PM +0100, samson goddy wrote:
>> > > here are the logs
>> > >
>> > >
>> >
>>  
>> ━━━
>> > > Date: Fri, 11 Dec 2015 12:57:01 -0300
>> > > From: [2]martin.abente.lah...@gmail.com
>> > > To: [3]samsongo...@hotmail.com
>> > > CC: [4]sugar-devel@lists.sugarlabs.org
>> > > Subject: Re: [Sugar-devel] Sugar Activities not working on Ubuntu
>> > >
>> > > Hey Samson,
>> > >
>> > > Are you using this [1]? Can you send the logs? Check in
>> ~/.sugar/default/
>> > logs/
>> > >
>> > > Regards,
>> > > Martin.
>> > >
>> > > Refs:
>> > > 1. [1][5]https://wiki.sugarlabs.org/go/Ubuntu
>> > >
>> > > On Fri, Dec 11, 2015 at 12:14 PM, samson goddy <[2][6]
>> > samsongo...@hotmail.com>
>> > > wrote:
>> > >
>> > > Hello guys,
>> > >
>> > > Most of the activities in sugar running on Ubuntu is not
>> working.
>> > Prompting
>> > > failed  to start. here is a screenshot of the sugar activity
>> on
>> > Ubuntu.
>> > >
>> > > ___
>> > > Sugar-devel mailing list
>> > > [3][7]Sugar-devel@lists.sugarlabs.org
>> > > [4][8]http://lists.sugarlabs.org/listinfo/sugar-devel
>> > >
>> > > ___ Sugar-devel
>> mailing list
>> > > [9]Sugar-devel@lists.sugarlabs.org [10]
>> http://lists.sugarlabs.org/
>> > listinfo/sugar-devel
>> > >
>> > > References:
>> > >
>> > > [1] [11]https://wiki.sugarlabs.org/go/Ubuntu
>> > > [2] mailto:[12]samsongo...@hotmail.com
>> > > [3] mailto:[13]Sugar-devel@lists.sugarlabs.org
>> > > [4] [14]http://lists.sugarlabs.org/listinfo/sugar-devel
>> >
>> >
>> > > ___
>> > > Sugar-devel mailing list
>> > > [15]Sugar-devel@lists.sugarlabs.org
>> > > [16]http://lists.sugarlabs.org/listinfo/sugar-devel
>> >
>> > --
>> > James Cameron
>> > [17]http://quozl.netrek.org/
>> > ___
>> > 

Re: [Sugar-devel] Sugar Activities not working on Ubuntu

[Martin Abente]

Hey Samson,

Are you using this [1]? Can you send the logs? Check in
~/.sugar/default/logs/

Regards,
Martin.

Refs:
1. https://wiki.sugarlabs.org/go/Ubuntu

On Fri, Dec 11, 2015 at 12:14 PM, samson goddy 
wrote:

> Hello guys,
>
> Most of the activities in sugar running on Ubuntu is not working.
> Prompting failed  to start. here is a screenshot of the sugar activity on
> Ubuntu.
>
> ___
> 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-build on F23

[Martin Abente]

Hey Walter,

it took me a while to figure out what it was, but is should be fixed now
(with out having to create that file manually).

I just sent the PR with the fix [1].


Martin.

[1] https://github.com/sugarlabs/sugar-build/pull/35

On Mon, Dec 7, 2015 at 5:21 PM, Walter Bender <walter.ben...@gmail.com>
wrote:

> Yes. It is not broot. And yes,  adding the dir fixed the problem.
> On Dec 7, 2015 3:05 PM, "Sam P." <sam@sam.today> wrote:
>
>> Hi,
>>
>> Broot is disabled by default on fedora these days.
>>
>> Did adding the folder fix that?
>>
>> Thanks,
>> Sam
>>
>> On Tue, Dec 8, 2015, 2:24 AM Walter Bender <walter.ben...@gmail.com>
>> wrote:
>>
>>> Yes. I didn't disable broot. I'll test again and try to get you a log
>>> file.
>>>
>>> -walter
>>>
>>> On Mon, Dec 7, 2015 at 10:19 AM, Martin Abente <
>>> martin.abente.lah...@gmail.com> wrote:
>>>
>>>> Hi Walter,
>>>>
>>>> Are you using broot (default)? I only tested with broot disabled and I
>>>> didn't get that error...
>>>>
>>>> Can you paste the log here to see what exactly is asking for that file?
>>>>
>>>> Regards,
>>>> Martin.
>>>>
>>>> On Mon, Dec 7, 2015 at 12:30 AM, Walter Bender <walter.ben...@gmail.com
>>>> > wrote:
>>>>
>>>>> FYI, I finally upgraded to F23 and made a fresh sugar-build. Ran into
>>>>> one problem:
>>>>>
>>>>> /home/walter/sugar-build/build/out/install/etc/gconf was not created,
>>>>> so build failed. Adding the directory by hand and all was well.
>>>>>
>>>>> Also, I managed to break Turtle Blocks in v212. Patch coming ASAP.
>>>>>
>>>>> 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
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> 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] sugar-build on F23

[Martin Abente]

Hi Walter,

Are you using broot (default)? I only tested with broot disabled and I
didn't get that error...

Can you paste the log here to see what exactly is asking for that file?

Regards,
Martin.

On Mon, Dec 7, 2015 at 12:30 AM, Walter Bender 
wrote:

> FYI, I finally upgraded to F23 and made a fresh sugar-build. Ran into one
> problem:
>
> /home/walter/sugar-build/build/out/install/etc/gconf was not created, so
> build failed. Adding the directory by hand and all was well.
>
> Also, I managed to break Turtle Blocks in v212. Patch coming ASAP.
>
> 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] congrats James & All for imminent Release 13.2.6!

[Martin Abente]

On Sat, Nov 7, 2015 at 11:41 AM, Adam Holt <h...@laptop.org> wrote:

> Hopefully OLPC's download.laptop.org will come back to life later this
> wkd possibly?  So all can try this on the classic 4 XO laptops:
>
> http://wiki.laptop.org/go/Release_notes/13.2.6
>
> While OLPC Release 13.2.6 has technically been released today according to
> http://wiki.laptop.org/go/Releases, in anticipation of James Cameron's
> formal announcement in coming days, can Gonzalo and Martin Abente provide a
> bit of supportive context around the stability of "unstable" 0.107
> (included in 13.2.6) vs "stable" 0.108 expected Feb 1st 2016, to calm
> deployments' worst fears?
>

Sugar goes through a development process with different stages [1], 0.107.0
is a release during the stage where we haven't yet freeze features, API,
strings etc, and these could still change before the final 0.108 release.

Doesn't means it is "unstable" in terms of quality of software, but, of
course, the quality will be improved in each following release until the
final 0.108.0 release.

>From my POV, the more ways of testing these releases until the final 0.108
the better and at the same time each deployment has the freedom to decide
if that release is good enough for them.


Martin.

Refs:
[1] https://wiki.sugarlabs.org/go/0.108/Roadmap


>
>
> http://sugar-devel.sugarlabs.narkive.com/XR4185MI/announcing-unstable-0-107-0-release
> https://wiki.sugarlabs.org/go/0.108/Roadmap
>
> --
> Unsung Heroes of OLPC, interviewed live @ http://unleashkids.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] [Announcing] UNSTABLE 0.107.0 release

[Martin Abente]

GREAT!

On Wed, Nov 4, 2015 at 7:39 PM, James Cameron  wrote:

> Available now are packages for testing of Sugar 0.107.0
>
> http://wiki.sugarlabs.org/go/0.108/Testing
>
> These are 0.107.0 plus some cherry-picked patches;
>
> - in About my Computer show serial number for computers other than the
>   OLPC XO,
>
> - don't stop a shutdown, restart, or logout just because an activity
>   is not responding.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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 osbuild problem

[Martin Abente]

Please send a PR :)

On Tue, Oct 27, 2015 at 8:00 AM, Samuel Cantero  wrote:

> Hello guys,
>
> I was trying to setup the development environment but there was a problem
> with the command "./osbuild pull". It can not find the
> www.sugarlabs.org/~buildbot/broot/last-x86_64-master. This is because
> currently www.sugarlabs.org is pointing to freedom and no more to
> sunjammer. The solution is to change the line 146 in the root.json file.
> For example, "url": "http://sunjammer.sugarlabs.org/~buildbot/broot/;.
>
> Regards,
>
> ___
> 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] [Announcing] UNSTABLE 0.107.0 release

[Martin Abente]

Hello everyone,

As an official kick-off for the 0.108 development cycle [1], we have
released a new *UNSTABLE* version of Sugar. This first 0.107.x release
includes a fair amount of changes and fixes, so *please* help us testing it!

Tarballs:
http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.107.0.tar.xz
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.107.0.tar.xz
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.107.0.tar.xz
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.107.0.tar.xz
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.107.0.tar.xz

The major goal for the final 0.108 release is to get collaboration fixed,
but we just recently got some progress thanks to Sam and Walter, therefore
I have updated the roadmap [1] with new deadlines to make sure we have time
to work on this. Note that the work needed to reach this goal is not
trivial, therefore, I am willing to be flexible with our deadlines for this
cycle, depending on the progress.

Martin.

Refs:
[1] http://wiki.sugarlabs.org/go/0.108/Roadmap
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Fwd: [Test-Announce] Fedora 23 Beta Release Candidate 1 (RC1) Available Now!

[Martin Abente]

Great!!

On Wed, Sep 16, 2015 at 7:53 AM, Peter Robinson 
wrote:

> Hi All,
>
> Fedora 23 Beta RC1 with SoaS is out, the login issue is fixed, please
> test test test.
>
> Direct download links:
>
>
> https://alt.fedoraproject.org/pub/alt/stage/23_Beta_RC1/Live/i386/Fedora-Live-SoaS-i686-23_Beta-1.iso
>
> https://alt.fedoraproject.org/pub/alt/stage/23_Beta_RC1/Live/x86_64/Fedora-Live-SoaS-x86_64-23_Beta-1.iso
>
> https://alt.fedoraproject.org/pub/alt/stage/23_Beta_RC1/Images/armhfp/Fedora-SoaS-armhfp-23_Beta-1-sda.raw.xz
>
> Rest of the details:
>
>
> -- Forwarded message --
> From: Adam Williamson 
> Date: Wed, Sep 16, 2015 at 2:22 AM
> Subject: [Test-Announce] Fedora 23 Beta Release Candidate 1 (RC1)
> Available Now!
> To: test-annou...@lists.fedoraproject.org
>
>
> As scheduled [1], Fedora 23 Beta Release Candidate 1 (RC1) is now
> available for testing. Please help us complete all the validation
> testing!
>
> The 32-bit cloud base image is known to be missing from this compose.
> Otherwise there are no major known issues.
>
> Content information, including changes, can be found at
> https://fedorahosted.org/rel-eng/ticket/6237#comment:7 . Please see
> the following pages for download links and testing instructions.
> Normally dl.fedoraproject.org should provide the fastest download, but
> download-
> ib01.fedoraproject.org is available as a mirror (with an approximately
> 1 hour lag) in case of trouble. To use it, just replace "dl" with
> "download-ib01" in the download URL.
>
> Installation:
>
> https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
>
> Base:
>
> https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
>
> Workstation and Desktop:
>
> https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
>
> Server:
>
> https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
>
> Cloud:
>
> https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
>
> Summary:
>
> https://fedoraproject.org/wiki/Test_Results:Current_Summary
>
> All Alpha and Beta priority test cases for each of these test pages
> [2] must pass in order to meet the Beta Release Criteria [3]. We are
> also trying to run the Final tests at this time, to try and
> identify later release blocker bugs as early as possible.
>
> Help is available on #fedora-qa on irc.freenode.net [4], or on the
> test list [5].
>
> Create Fedora 23 Beta test compose (TC) and release candidate (RC)
> https://fedorahosted.org/rel-eng/ticket/6237
>
> Current Blocker and Freeze Exception bugs:
> http://qa.fedoraproject.org/blockerbugs/current
> [1] http://fedorapeople.org/groups/schedule/f-23/f-23-quality-tasks.html
> [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
> [3] https://fedoraproject.org/wiki/Fedora_23_Beta_Release_Criteria
> [4] irc://irc.freenode.net/fedora-qa
> [5] https://admin.fedoraproject.org/mailman/listinfo/test
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
>
>
> ___
> test-announce mailing list
> test-annou...@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/test-announce
> --
> devel mailing list
> de...@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> ___
> 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] Simple stuff I don't know

[Martin Abente]

Hey George,

You could:

1) modify the sugar shell to launch it... ie., doing something similar to
what was done for the welcome activity.  Or...
2) use the sugar services stuff to launch the activity without having to
modify sugar.

I would go for the second option, and simply write a _very_ small sugar
service that launches the activity. You can use this simple service as an
example [1]. The only thing you really need is to implement the account.py
[2] file, where the activity should be launched. You can pretty much ignore
the rest.

Regards,

Refs:
1. https://github.com/tchx84/sugar-gpaste
2.
https://github.com/tchx84/sugar-gpaste/blob/master/extensions/webservice/gpaste/account.py



On Wed, Sep 16, 2015 at 6:19 PM, James Cameron  wrote:

> .xsession can work, if your subshell will give Sugar time to start,
> then copy environment variables from the Sugar shell process, then run
> sugar-launch.
>
> Don't know a best awy.  Some deployments have used an automatic start
> activity.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> Devel mailing list
> de...@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [road to 0.108] follow up development team meeting

[Martin Abente]

Thanks everyone for coming, the logs are evailable here [1,2].

For those who could not come, Sam submitted a patch to webkit to gain
access to browse state API (if I got it right), James suggested we
seriously consider taking the working telepathy-gabble version into sugar
(assuming there is no resources to research and develop a full migration to
newer gabble) and Cerlyn pointed out that distros such as Fedora and Ubuntu
might provide a new mechanisms for having customized dependencies for each
DE.

Refs:
[1]
http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-09-16T22:15:39.html
[2] http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-09-16T22:15:39

On Mon, Sep 14, 2015 at 4:58 PM, James Cameron <qu...@laptop.org> wrote:

> On Mon, Sep 14, 2015 at 10:52:40AM -0400, Martin Abente wrote:
> > Would Wednesday 16th, 22:00 UTC work for you?
>
> Yes.
>
> --
> James Cameron
> http://quozl.linux.org.au/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] [road to 0.108] follow up development team meeting

[Martin Abente]

Hello everyone,

It's been a while since the last development meeting, would be good to
re-sync.

Would Wednesday 16th, 22:00 UTC work for you? As usual, on #sugar-meeting
at freenode.

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

Re: [Sugar-devel] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Martin Abente]

On Sat, Sep 5, 2015 at 3:29 PM, Jerry Vonau <m...@jvonau.ca> wrote:

>
>
> > On September 5, 2015 at 10:21 AM Martin Abente
> > <martin.abente.lah...@gmail.com> wrote:
> >
> >
> > On Fri, Sep 4, 2015 at 7:01 PM, James Cameron <qu...@laptop.org> wrote:
> >
> > > So to briefly restate.
> > >
> > > Problem: Sugar does not start on F23.
> > >
> > > Diagnosis: the shared library libsugarext.so.0 cannot be loaded,
> > > because of a missing symbol, yet the symbol can be found with
> > > strings(1).
> > >
> > > Workaround #1: use F22 packages.
> > >
> > > Workaround #2: use Martin's packages which were a rebuild of
> > > sugar-toolkit-gtk3 with .spec file change
> > >
> > > %undefine _hardened_build
> > >
> >
> > Yes, and both workarounds have in common that sugar-toolkit-gtk3 is built
> > without _hardened_build (by default on fc22 and explicitly on my modified
> > fc23 package).
> >
> >
> > >
> > > As this was a Fedora change, I think we need some advice on
> > > compatibility with Fedora build hardening.
>
> In any hardened builds build.log I can see
>
> libtool: link: gcc -o /builddir/build/BUILD/sugar-toolkit-gtk3-0.106.0
> -pthread
> 
> g-ir-scanner: SugarExt: warning: 2 warnings suppressed (use --warn-all to
> see them)
> /usr/bin/g-ir-compiler --includedir=../../src/sugar3/event-controller
> --includedir=. SugarExt-1.0.gir -o SugarExt-1.0.typelib
>
> Any idea on how to supply --warn-all to the g-ir-scanner call? This warning
> is absent from non-hardened builds.
>
>
I do see that warning in all builds, regardless if hardened or not [1].

Anyway, one way to do what you want is to "copy" the original CFLAGS, add
the flag, and re-export it before you build sugar-toolkit-gtk3 (e.g using
rpmbuild directly).

Refs:
[1]
https://kojipkgs.fedoraproject.org//packages/sugar-toolkit-gtk3/0.104.1/1.fc22/data/logs/x86_64/build.log


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

Re: [Sugar-devel] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Martin Abente]

On Fri, Sep 4, 2015 at 7:01 PM, James Cameron  wrote:

> So to briefly restate.
>
> Problem: Sugar does not start on F23.
>
> Diagnosis: the shared library libsugarext.so.0 cannot be loaded,
> because of a missing symbol, yet the symbol can be found with
> strings(1).
>
> Workaround #1: use F22 packages.
>
> Workaround #2: use Martin's packages which were a rebuild of
> sugar-toolkit-gtk3 with .spec file change
>
> %undefine _hardened_build
>

Yes, and both workarounds have in common that sugar-toolkit-gtk3 is built
without _hardened_build (by default on fc22 and explicitly on my modified
fc23 package).


>
> As this was a Fedora change, I think we need some advice on
> compatibility with Fedora build hardening.  We don't see the same
> thing with the build hardening on Debian or Ubuntu yet.
>

Agreed.


> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Martin Abente]

Hello Peter,

On Fri, Sep 4, 2015 at 5:50 AM, Peter Robinson <pbrobin...@gmail.com> wrote:

>
> On 4 Sep 2015 00:22, "Martin Abente" <martin.abente.lah...@gmail.com>
> wrote:
> >
> >
> >
> > On Thu, Sep 3, 2015 at 6:43 PM, James Cameron <qu...@laptop.org> wrote:
> >>
> >> The errors complain of missing symbols;
> >>
> >> - sugar_event_controller_get_state
> >>
> >> - acme_volume_alsa_new
> >>
> >> Which were both added after 0.98.
> >>
> >> On my F18 test systems, the package sugar-toolkit-0.98 brings in a
> >> _sugarext.so file in /usr/lib/python2.7/site-packages/sugar/ which
> >> does not have these symbols.
> >>
> >> If this file were being used instead, then the outcome may be as
> >> reported.
> >>
> >> Is the package present?
> >
> >
> > No, is not present. Also, that does not explain why the same 106
> packages work perfectly fine on fc23 when are built for fc22, while they
> fail when built for fc23.
> >
> > As you mentioned in a previous reply, the only difference in build time
> I also noticed, looking at the logs, is
> the -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' flag. which is passed to
> all gir-* (gobject introspection) calls.
> >
>
> Yes, it's a well advertised feature of F-23, but we're not the first
> distro to enable it and unless there's dodgy stuff going on in sugar it
> should cause no issues.
>

I rebuilt [1] the sugar-toolkit-gtk3 106 packages for fc23, adding "%undefine
_hardened_build" [2,3] to the .spec file, and now Sugar works fine on fc23.

I could not figure out why having _hardened_build enable breaks sugar, but
it looks like disabling could be an option for now.

Refs:
1. http://people.sugarlabs.org/~tch/tests/fedora23/
2. https://bugzilla.redhat.com/show_bug.cgi?id=1214506#c2
3.
https://fedoraproject.org/wiki/Changes/Harden_All_Packages#Troubleshooting_steps_for_package_maintainers


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

Re: [Sugar-devel] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Martin Abente]

Hey James,

I did these tests on a fc23 system with two different builds of the
sugar-toolkit-gtk3 106 package: (A) built for fc23, and (B) built for fc22.

On Fri, Sep 4, 2015 at 7:41 AM, James Cameron  wrote:

> [repost, no response seen]
>
> Martin showed a log of
>
> ** (main.py:1818): WARNING **: Failed to load shared library
>'libsugarext.so.0' referenced by the typelib:
>/lib64/libsugarext.so.0: undefined symbol:
>sugar_event_controller_get_state
>
> Compare with previous report
> http://paste.fedoraproject.org/260680/69152144/
>
> ** (main.py:2637): WARNING **: Failed to load shared library
>'libsugarext.so.0' referenced by the typelib:
>/lib/libsugarext.so.0: undefined symbol:
>sugar_event_controller_get_state
>
> The line number is different.
>
> @All, what is main.py and where are lines 1818 and 2637?
>
> src/jarabe/main.py is much smaller, only 425 lines.
>
> Some other diagnosis methods to suggest:
>
> a.  in a fresh python process, try the relevant imports, e.g.
>
> from jarabe.view import gesturehandler
> from jarabe.model.sound import sound
>

A) built for fc23: does NOT work, showing the same error as I the logs
previously posted.
B) built for fc22: does work, and sugar works too.


>
> b.  verify a symlink is present from /usr/lib/libsugarext.so.0 to
> libsugarext.so.0.0.0 (or equivalent functionality, as this is a
> guess from my experience with F18),
>

A) built for fc23: symlink IS present.
B) built for fc22: symlik IS present.


>
> c.  use strings to check libsugarext.so.0, see if
> sugar_event_controller_get_state is present,
>
> strings /usr/lib/libsugarext.so.0 | \
> grep sugar_event_controller_get_state
>

A) built for fc23: the string IS present ("acme_volume_alsa_new" is string).
B) built for fc22:  the string IS present ("acme_volume_alsa_new" is
string).


> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
On Fri, Sep 4, 2015 at 7:41 AM, James Cameron  wrote:

> [repost, no response seen]
>
> Martin showed a log of
>
> ** (main.py:1818): WARNING **: Failed to load shared library
>'libsugarext.so.0' referenced by the typelib:
>/lib64/libsugarext.so.0: undefined symbol:
>sugar_event_controller_get_state
>
> Compare with previous report
> http://paste.fedoraproject.org/260680/69152144/
>
> ** (main.py:2637): WARNING **: Failed to load shared library
>'libsugarext.so.0' referenced by the typelib:
>/lib/libsugarext.so.0: undefined symbol:
>sugar_event_controller_get_state
>
> The line number is different.
>
> @All, what is main.py and where are lines 1818 and 2637?
>
> src/jarabe/main.py is much smaller, only 425 lines.
>
> Some other diagnosis methods to suggest:
>
> a.  in a fresh python process, try the relevant imports, e.g.
>
> from jarabe.view import gesturehandler
> from jarabe.model.sound import sound
>
> b.  verify a symlink is present from /usr/lib/libsugarext.so.0 to
> libsugarext.so.0.0.0 (or equivalent functionality, as this is a
> guess from my experience with F18),
>
> c.  use strings to check libsugarext.so.0, see if
> sugar_event_controller_get_state is present,
>
> strings /usr/lib/libsugarext.so.0 | \
> grep sugar_event_controller_get_state
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Martin Abente]

On Thu, Sep 3, 2015 at 1:12 PM, Jerry Vonau <m...@jvonau.ca> wrote:

>
>
> > On September 3, 2015 at 11:38 AM Martin Abente
> > <martin.abente.lah...@gmail.com> wrote:
> >
> >
> > Hello everyone,
> >
> > I rebuilt 0.106.0 packages from fc23 source rpms, for fc22 x86_64.
>
> So did I using my copr account, what a great tool to build rpms with,
> perhaps SL should go back to using it.[1] Easy for testers to enable with
> dnf.
>
> > It works
> > fine, so it definitely not something with Sugar. It makes sense since
> > nothing changed in SugarExt.
> >
> > Now, this might be something with fc23, but is it on build time or run
> > time? Ideas? Maybe something related to gobject instrospection?
> >
>
> Runtime in F23, otherwise the F23 rpm would not been built.
>

Not necessarily, e.g. there could be something wrong happening while
generating the gobject introspection files. Something wrong in the sense
that the content is not generated "properly", and does not necessarily
triggers a "compilation error".

In fact, I think this might be the case: I installed the 0.106.0 packages I
built for fc22 on a fresh fc23 system and sugar works fine.

Ideas? I suspect on the gobject introspection bindings generation, but
can't think of what exactly it could be.

Refs:
[1] http://people.sugarlabs.org/~tch/tests/fedora22/


> Jerry
>
>
> 1. https://copr.fedoraproject.org/coprs/dnarvaez/sugar
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Martin Abente]

Hello everyone,

I rebuilt 0.106.0 packages from fc23 source rpms, for fc22 x86_64. It works
fine, so it definitely not something with Sugar. It makes sense since
nothing changed in SugarExt.

Now, this might be something with fc23, but is it on build time or run
time? Ideas? Maybe something related to gobject instrospection?

tch.

Refs:
[1] http://people.sugarlabs.org/~tch/tests/fedora22/


On Thu, Sep 3, 2015 at 3:45 AM, Jerry Vonau  wrote:

>
>
> > On September 3, 2015 at 1:34 AM James Cameron  wrote:
> >
> >
> > On Thu, Sep 03, 2015 at 01:21:19AM -0500, Jerry Vonau wrote:
> > >
> > >
> > > > On September 3, 2015 at 12:38 AM James Cameron 
> > > > wrote:
> > > >
> > > >
> > > > On Thu, Sep 03, 2015 at 12:11:38AM -0500, Jerry Vonau wrote:
> > > > > F22 upgrades clean to 106, feels pretty zippy in a VM. Back to
> > > > > figuring out what is now different in the dependencies given the
> > > > > logs[1] for the builds look more or less the same F21 <-> F23.
> > > > > There
> > > > > has to be a rpm package with a library that was split somewhere,
> > > > > sugar's toolkit wants to use something but is left unsatisfied.
> > > >
> > > > It might be interesting to see if the F23 build of 0.104.1 also has
> > > > the problem on F23.  As further proof that it isn't anything Sugar
> > > > did.
> > > >
> > > I can get to a cmdline via the bootprompt using the F23 iso, so I'll do
> > > the
> > > 104 on F23 test, just not tonight.
> > >
> > > It's not what sugar did, but didn't do yet, adapt to the new build
> > > environment for F23. Is the current recommended sugar development
> > > still sugar-build at EOL'd F20?
> >
> > Good question.  Don't know.  Hopefully someone from Sugar Labs can
> > tell us.
> >
> > Although sugar-build hides all these kinds of problems by building on
> > the target system instead of packaging.
> >
>
> I know I agree, that is why I'm looking at the devel packages that are
> installed there, make a change recompile and test, but a quick way to lose
> track of a dependence... in which package or is that the lib package or...
> You get the idea.
>
> > sugar-build is not used when deploying, so it seems unwise to use it
> > for development.  ;-)
> >
>
> Yea but some improvements got written while using it.
>
> > > > Comparing the logs of 0.104.1 build for x86_64 between F22 and F23,
> > > > the only interesting change that springs up is;
> > > >
> > > > -LDFLAGS='-Wl,-z,relro '
> > > > +LDFLAGS='-Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld'
> > > >
> > > > Doesn't seem related to the reported problem, however.
> > >
> > > I tend to agree, but I'm not sure of the full effect of the flag. I
> > > think there is a package that was split and a dependence needed by
> > > sugar/toolkit moved to a new sub-package and is not in what is
> > > declared as (Build)Requires anymore. If this is true then the new
> > > sub-package should now be used in the spec file somewhere, just
> > > finding the package.
> >
> > Hmm, doesn't seem related to the sugarext library missing from the
> > expected directory.  Maybe I've misunderstood the problem.
> >
>
> I wanted to poke around a bit because of Peter comment about s/b /usr/lib64
> in bugzilla for info. That why I booted to the cmdline, filesystem looks
> right /lib -> /usr/lib  /lib64 -> /usr/lib64 with libsugarext and
> libsugar-eventcontrollor present.
> ___
> 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] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Martin Abente]

On Thu, Sep 3, 2015 at 3:58 PM, Jerry Vonau <m...@jvonau.ca> wrote:

>
>
> > On September 3, 2015 at 12:58 PM Martin Abente
> > <martin.abente.lah...@gmail.com> wrote:
> >
> >
> > On Thu, Sep 3, 2015 at 1:12 PM, Jerry Vonau <m...@jvonau.ca> wrote:
> >
> > >
> > >
> > > > On September 3, 2015 at 11:38 AM Martin Abente
> > > > <martin.abente.lah...@gmail.com> wrote:
> > > >
> > > >
> > > > Hello everyone,
> > > >
> > > > I rebuilt 0.106.0 packages from fc23 source rpms, for fc22 x86_64.
> > >
> > > So did I using my copr account, what a great tool to build rpms with,
> > > perhaps SL should go back to using it.[1] Easy for testers to enable
> > > with
> > > dnf.
> > >
> > > > It works
> > > > fine, so it definitely not something with Sugar. It makes sense since
> > > > nothing changed in SugarExt.
> > > >
> > > > Now, this might be something with fc23, but is it on build time or
> > > > run
> > > > time? Ideas? Maybe something related to gobject instrospection?
> > > >
> > >
> > > Runtime in F23, otherwise the F23 rpm would not been built.
> > >
> >
> > Not necessarily, e.g. there could be something wrong happening while
> > generating the gobject introspection files. Something wrong in the sense
> > that the content is not generated "properly", and does not necessarily
> > triggers a "compilation error".
> >
>
> Agreed, looking for what changed is a pain.
>
> > In fact, I think this might be the case: I installed the 0.106.0 packages
> > I
> > built for fc22 on a fresh fc23 system and sugar works fine.
> >
>
> Interesting, what is the "fresh system"? Are you selecting sugar at the
> login manager or using sugar-runner?
>

a) fresh system == a new installation of fc23 Alpha-2 x86_64 on a VM.
b) I am selecting the Sugar option on the logging screen, but it also works
if you type "sugar" on a terminal in the gnome session.


> There could be dependencies that are already met by the installed system,
> that would mask an undeclared dependency in the sugar rpms. Kind of
> re-enforces what I'm thinking, some Build|Requires moved to a sub-package
> for a sugar dependency or there is a new unaccounted sugar dependency.
>
>
No, it doesn't seem to be a problem with the run-time environment.

I tried creating another VM with fc23, installed the fc23 sugar packages
and sugar fails to start [1].  Note that the error is slightly different,
but the is the same issue.

So, looking at all the tests I did, the only difference is the environment
in which the packages are built. If the packages are built for fc22 sugar
0.106 works even on fc23, but if its built for fc23 it doesn't work.

Refs:
[1] http://fpaste.org/263354/31582414/

> Ideas? I suspect on the gobject introspection bindings generation, but
> > can't think of what exactly it could be.
> >
> Wouldn't the recent addition of importing configparser require the
> python-configparser rpm to be declared as Required, not relying on to be
> already present? Might explain your observations with a different desktop.
>
> Jerry
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Martin Abente]

On Thu, Sep 3, 2015 at 6:43 PM, James Cameron <qu...@laptop.org> wrote:

> The errors complain of missing symbols;
>
> - sugar_event_controller_get_state
>
> - acme_volume_alsa_new
>
> Which were both added after 0.98.
>
> On my F18 test systems, the package sugar-toolkit-0.98 brings in a
> _sugarext.so file in /usr/lib/python2.7/site-packages/sugar/ which
> does not have these symbols.
>
> If this file were being used instead, then the outcome may be as
> reported.
>
> Is the package present?
>

No, is not present. Also, that does not explain why the same 106 packages
work perfectly fine on fc23 when are built for fc22, while they fail when
built for fc23.

As you mentioned in a previous reply, the only difference in build time I
also noticed, looking at the logs, is the
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld'
flag. which is passed to all gir-* (gobject introspection) calls.


>
> If so, does removing the .so file fix the problem?
>
> Use of the file could also be verified with strace -e open.
>
> On Thu, Sep 03, 2015 at 05:39:19PM -0400, Martin Abente wrote:
> > I tried creating another VM with fc23, installed the fc23 sugar
> > packages and sugar fails to start [1].  Note that the error is
> > slightly different, but the is the same issue.
> > [1] http://fpaste.org/263354/31582414/
>
> ** (main.py:1818): WARNING **: Failed to load shared library
>'libsugarext.so.0' referenced by the typelib:
>/lib64/libsugarext.so.0: undefined symbol:
>sugar_event_controller_get_state
>
> Compare with previous report
> http://paste.fedoraproject.org/260680/69152144/
>
> ** (main.py:2637): WARNING **: Failed to load shared library
>'libsugarext.so.0' referenced by the typelib:
>/lib/libsugarext.so.0: undefined symbol:
>sugar_event_controller_get_state
>
> The line number is different.
>
> @All, what is main.py and where are lines 1818 and 2637?
>
> src/jarabe/main.py is much smaller, only 425 lines.
>
> Some other diagnosis methods to suggest:
>
> a.  in a fresh python process, try the relevant imports, e.g.
>
> from jarabe.view import gesturehandler
> from jarabe.model.sound import sound
>
> b.  verify a symlink is present from /usr/lib/libsugarext.so.0 to
> libsugarext.so.0.0.0 (or equivalent functionality, as this is a
> guess from my experience with F18),
>
> c.  use strings to check libsugarext.so.0, see if
> sugar_event_controller_get_state is present,
>
> strings /usr/lib/libsugarext.so.0 | \
> grep sugar_event_controller_get_state
>
> --
> James Cameron
> http://quozl.linux.org.au/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Martin Abente]

On Wed, Sep 2, 2015 at 4:49 PM, James Cameron  wrote:

> On Wed, Sep 02, 2015 at 05:59:06AM -0500, Jerry Vonau wrote:
> >
> >
> > > On September 1, 2015 at 9:16 PM James Cameron 
> wrote:
> > >
> > >
> > > On Tue, Sep 01, 2015 at 09:03:28PM -0500, Jerry Vonau wrote:
> > > > That leads me to think if sugar is building against a library that
> > > > is only available in sugar's toolkit should the toolkit be declared
> > > > as a BuildRequires and be pulled into the BuildRoot for sugar?
> > >
> > > Possibly because nothing in the build of package "sugar" uses the
> > > library.
> > >
> > > I've looked through the Makefile.am files in "sugar" and none of them
> > > do linking, and the ones that execute Python code don't need that
> > > library.
> > >
> >
> > Ok got it, ldconfig keeps it all straight, so it's contained to the
> > call in the toolkit, bringing the login manager back in a loop, so I
> > see when booting the F23 iso in a vm.
>
> Couldn't parse that, sorry.


> > The only change I see from F22 with 104 to F23 with 106 around
> > SugarExt is the commit to "Add capture device support" in the
> > toolkit.
>
> That's strange, in my git repo that commit is just before the 0.101.4
> release back in 2014-03-22.



>
> It was the most recent change to SugarExt, but it should have been in
> F22 with 0.104 already.
>
>
Yes, all changes that impact on SugarExt were already present in 0.104,
being this [1] the last one.

Refs:
[1]
https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/7739336fb62afc05040559187ef2d47c89c32506


> I've not got the bandwidth for downloading SoaS, but the tests I
> suggest are:
>
> a.  use RPM to reinstall the Sugar 0.106 packages,


> b.  use RPM to reinstall the F22 Sugar 0.104 binary packages,


> c.  use RPM to rebuild the F22 Sugar 0.104 packages from src.rpm.


> That would help to divide the problem between Sugar and Fedora 23.,



> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> 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-install-bundle in 13.2.5 is slooow

[Martin Abente]

The problem caused by the race condition is that the activities were not
refreshed in Sugar activities list when updated or, not added to the list
when installed. By race condition I mean the situation where the
BundleRegistry detects changes (e.g. in ~/Activities) too early, when
activity.info is not available yet, so the bundle gets ignored. I
personally don't think is related to this issue.

Now, looking at Tony's report and Sam's confirmation that this issue is
related to the change in [1], my first guess would be that the problem is
caused by the overhead generated by initializing the BundleRegistry, and
any other sugar module imported by it, every time the sugar-install-bundle
script is executed. Note that the script runs in a different process than
the sugar shell, so the registry instance returned by get_registry() is not
the same one as the one in the shell. Having SUGAR_PROFILE set doesn't
necessarily mean the script is being executed in the same context as the
shell.

If my guess is confirmed, we should revise that change or revert it.

Refs:
1.
https://github.com/sugarlabs/sugar/commit/64b4b2fba1c37a9ad92ed30eb669b68552b62415

On Mon, Aug 31, 2015 at 9:02 AM, Gonzalo Odiard  wrote:

> I am wondering if this issue ca be related to the race condition detected
> by Martin when the file monitor detect the activity before the
> activity.info file
> is saved to disk.
>
> Martin, do you have a patch to test?
>
> Gonzalo
>
> On Mon, Aug 31, 2015 at 10:00 AM, Gonzalo Odiard 
> wrote:
>
>> Tony,
>> If you can enable logging (remove the comment in the line
>> SUGAR_LOGGER_LEVEL
>> in the file /home/olpc/.sugar/default/debug)
>> And install one of the activities without unset the SUGAR_PROFILE env
>> variable,
>> and send the log, maybe we can understand better what is happening.
>>
>> I am afraid the slowness will impact Browse even if you patch it, because
>> Browse process
>> run in a environment with the env variable set.
>>
>> One more question: the time is bigger in slower devices (XO-1) than in
>> XO-4,
>> or is independent of the hardware performance?
>>
>> Gonzalo
>>
>>
>> On Sun, Aug 30, 2015 at 7:34 PM, James Cameron  wrote:
>>
>>> G'day Sam,
>>>
>>> Adding a flag for a workaround seems like you've given up.  ;-)
>>>
>>> Wouldn't it be better to fix the problem?  As you can see from
>>> #4849 it occurs in Sugar, and only inside Terminal activity.
>>>
>>> Why is it happening?
>>>
>>> Why does it take up to 24 minutes to install Browse using Terminal?
>>>
>>> Why does it take up to 5 minutes to install in Sugar 0.98?
>>>
>>> And yet only half a second if the bundle registry is bypassed?
>>>
>>> The bundle registry can't be that slow.
>>>
>>> By understanding the problem we'll be able to say whether it is
>>> causing any other slowness of Sugar.
>>>
>>> --
>>> James Cameron
>>> http://quozl.linux.org.au/
>>> ___
>>> Sugar-devel mailing list
>>> Sugar-devel@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>
>>
>>
>> --
>> Gonzalo Odiard
>>
>>
>
>
> --
> Gonzalo Odiard
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] [Announcing] sugar and sugar-toolkit-gtk3 v0.106.1 (bug fixes release)

[Martin Abente]

Hello everyone,

It's been almost two months since the release of Sugar 0.106.0, and since
then we have been improving things. Many of these improvements are planned
for the next major release of Sugar, but there are bug fixes that will
certainly be useful for those using Sugar 0.106. Therefore, we have
released sugar [1] and sugar-toolkit-gtk3 [2] v0.106.1 which include these
bug fixes.

The tarballs can be downloaded from:

   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.106.1.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.106.1.tar.xz


I want to take this opportunity to thank our infrastructure team for their
hard work to keep things running smoothly in Sugar Labs, so thanks Sam
Parkinson, Samuel Cantero, Bernie Innocenti, Sebastian Silva and Roberto
Rodriguez Alcala!


Martin.

Refs:
[1] https://github.com/sugarlabs/sugar/commits/sucrose-0.106
[2] https://github.com/sugarlabs/sugar-toolkit-gtk3/commits/sucrose-0.106
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [road to 0.108] developing team meeting

[Martin Abente]

Thank you everyone for coming, I think that at least we have mentioned the
important topics and have opened the discussions regarding release times.

We should continue with these topics via mailing list and meet again ASAP
once we have a bit more details about what needs and can to be done.

Refs:
[1]
http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-07-20T21:02:59.html
[2] http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-07-20T21:02:59
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [road to 0.108] developing team meeting

[Martin Abente]

We didn't have enough people, so we are moving the meeting to Monday 20. We
discussed a few topics though:

1. We will be merging fixes on master, and if anything serious comes up we
will make a 0.106.1 release from the branch.
2. Gonzalo will review Sam's changes to palettes.
3. I will be reviewing Gonzalo's fixes.

See you on Monday,

Regards,
Martin.

On Tue, Jul 14, 2015 at 10:10 AM, Gonzalo Odiard godi...@sugarlabs.org
wrote:

 +1 from me


 On Tue, Jul 14, 2015 at 11:09 AM, Martin Abente 
 martin.abente.lah...@gmail.com wrote:

 @Sam: 21 UTC works for me!

 Does it work for everybody else?

 On Tue, Jul 14, 2015 at 7:56 AM, Sam P. sam@sam.today wrote:

 Hey Martin,

 I can't do 14 UTC.  Would 21/22 UTC be ok for you?

 Otherwise, I'm always happy to write emails :)

 Thanks,
 Sam



 On Tue, 14 Jul 2015 12:00 am Martin Abente 
 martin.abente.lah...@gmail.com wrote:

 Hello everyone,

 Now that Sugar 0.106 has been released, it is time to think about what
 has been done and what needs to be done for Sugar 0.108. Therefore, I
 proposed we meet on:

 Date: Friday July 17.
 Time: 14:00 UTC.
 Place: #sugar-meeting - freenode.

 Does that time work for you? If not, feel free to propose another time.

 Regards,
 Martin.




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




 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning

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

Re: [Sugar-devel] [road to 0.108] developing team meeting

[Martin Abente]

@Sam: 21 UTC works for me!

Does it work for everybody else?

On Tue, Jul 14, 2015 at 7:56 AM, Sam P. sam@sam.today wrote:

 Hey Martin,

 I can't do 14 UTC.  Would 21/22 UTC be ok for you?

 Otherwise, I'm always happy to write emails :)

 Thanks,
 Sam



 On Tue, 14 Jul 2015 12:00 am Martin Abente martin.abente.lah...@gmail.com
 wrote:

 Hello everyone,

 Now that Sugar 0.106 has been released, it is time to think about what
 has been done and what needs to be done for Sugar 0.108. Therefore, I
 proposed we meet on:

 Date: Friday July 17.
 Time: 14:00 UTC.
 Place: #sugar-meeting - freenode.

 Does that time work for you? If not, feel free to propose another time.

 Regards,
 Martin.



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

[Sugar-devel] [road to 0.108] developing team meeting

[Martin Abente]

Hello everyone,

Now that Sugar 0.106 has been released, it is time to think about what has
been done and what needs to be done for Sugar 0.108. Therefore, I proposed
we meet on:

Date: Friday July 17.
Time: 14:00 UTC.
Place: #sugar-meeting - freenode.

Does that time work for you? If not, feel free to propose another time.

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

Re: [Sugar-devel] About 0.106.1

[Martin Abente]

If nothing too serious comes up in the following weeks, there might be no
need for that release. Regardless of that, we should definitely meet before
start merging changes.

I have sent an invitation email for this Friday.

On Mon, Jul 13, 2015 at 8:37 AM, Gonzalo Odiard godi...@sugarlabs.org
wrote:

 In our schedule [1], we have a possible Sucrose 0.106.1
 with exceptional bugfixes tarballs  release planed.

 Can we start to merge changes on master, and later the release manager
 can cherry-pick the bugfixes needed for 0.106.1?

 I would like to have a development meeting to organize and do some
 planning.
 We already have a nice list of pull requests pending review/merging.

 [1] https://wiki.sugarlabs.org/go/0.106/Roadmap

 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning

 ___
 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 0.106 Video

[Martin Abente]

Excelente! Lo agregue al Release Notes [1].

Refs:
1. http://wiki.sugarlabs.org/go/0.106/Notes#Videos

On Mon, Jul 13, 2015 at 3:01 PM, Gonzalo Odiard godi...@sugarlabs.org
wrote:

 Muy bueno!

 On Mon, Jul 13, 2015 at 3:56 PM, Laura Vargas la...@somosazucar.org
 wrote:

 Thank you James!

 Here you'll find the Spanish version for the 106 release:

 https://www.youtube.com/watch?v=1SMzR8nI5A8

 Sam,

 One thing that is not clear is how to access the Social Help. I have
 tried 106 but didn't find my way in. Any help will be appreciated.

 Cheers and congrats to all for the new release.

 2015-07-08 17:58 GMT-05:00 James Cameron qu...@laptop.org:

 Sam shares my accent, so I'll transcribe it for you:

 We've got a brand new release, we can't wait to share it with you.

 Introducing: Sugar 106.

 This release introduces Social Help.

 Social Help lets you ask questions, report bugs, and discuss features,
 with developers and the community,

 Plus, we've put your display in the Frame.  It's now even easier to
 change a brightness or take a screenshot.

 Our bundle launcher makes activities work better together.  Activities
 can now open each other for a frictionless experience.

 As always, we've fixed masses of bugs, and regressions, thanks to hard
 work of community members.

 Visit our Wiki to start learning how to use 106 today.  And be
 involved in the Sugar Labs community.

 --
 James Cameron
 http://quozl.linux.org.au/




 --
 Laura V.
 ID SomosAZUCAR.Org

 Identi.ca/Skype acaire
 IRC kaametza

 Happy Learning!


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




 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning

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

Re: [Sugar-devel] Sugar 0.106 Video

[Martin Abente]

Great! Let me know if there are more versions of the video so I can add it
to the Notes page :)

On Tue, Jul 7, 2015 at 5:56 PM, Sam P. sam@sam.today wrote:

 Sounds like a very good way to do it!

 On Wed, Jul 8, 2015 at 7:55 AM James Cameron qu...@laptop.org wrote:

 I cannot speak for the tools that Sam may have, but a method for
 internationalisation is to:

 - write down what Sam said,

 - translate to Spanish,

 - play the video with sound muted,

 - record yourself speaking while watching the video,

 - repeat the recording until you think it is best,

 - send the recordings to Sam _or_ use tools to replace the audio track
   with your recording,

 What do you suggest, Sam?

 On Tue, Jul 07, 2015 at 12:01:11PM -0500, Laura Vargas wrote:
  Great video Sam!
 
  I would love to help with the Spanish version :D
 
  Let me kmow how to proceed.
 
  2015-07-05 18:40 GMT-05:00, James Cameron qu...@laptop.org:
   Reviewed, please merge.  ;-)
  
   --
   James Cameron
   http://quozl.linux.org.au/
   ___
   Sugar-devel mailing list
   Sugar-devel@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/sugar-devel
  
 
 
  --
  Laura V.
  ID SomosAZUCAR.Org
 
  Identi.ca/Skype acaire
  IRC kaametza
 
  Happy Learning!

 --
 James Cameron
 http://quozl.linux.org.au/
 ___
 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

[Sugar-devel] [Release] Announcing Sugar 0.106.0 (stable)

[Martin Abente]

Hello everyone,

I am pleased to announce the release of Sugar 0.106.0. In this new stable
release we added performance improvements, new ways of learning
collaboratively, new hardware controls, more translations, and of course, a
lot of bug fixes. Please visit the Release Notes page [1] for details.

This release of Sugar is dedicated to the memory of Marco Gritti Presenti.
Marco was a member of the original Sugar team and the lead Red Hat engineer
on the project over its first three years of development. Marco was also a
founding member of Sugar Labs and one of the original members of the Sugar
Labs oversight board. Beyond the code he contributed to the project -- he
was a gifted software engineer --Marco shared with us his vision that Sugar
ultimately belongs to its users: it is the clarity of this vision that is
still reflected in the Sugar code-base and the spirit of the Sugar Labs
community.

Martin.

[1] http://wiki.sugarlabs.org/go/0.106/Notes
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar 0.106 Video

[Martin Abente Lahaye]

Awesome! :)

On Sun, Jul 5, 2015 at 6:32 AM, Sam P. sam@sam.today wrote:

 Hi,

 So the 0.106 release is tomorrow, which is pretty awesome.

 I have made a video summarizing the features since we did that last
 release and it seems like a good idea:  https://youtu.be/PXFaXAGIw04

 Thanks,
 Sam

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

Re: [Sugar-devel] Change request: Fix open with API

[Martin Abente]

Considering that James, Sam and I have reviewed and tested these changes,
the consensus is to include them to fix the API. Therefore, Gonzalo has
green light for merge.

On Fri, Jul 3, 2015 at 5:41 AM, Tony Anderson tony_ander...@usa.net wrote:

  Thanks James and Sam for your replies.

 The references to Rainbow Security model are a bit confusing. The Rainbow
 model was dropped by the second G1G1 as I recollect. As far as I can tell,
 Browse launches child processes (pdfviewer). These typically are
 represented in the frame by a grey circle.

 I apologize on the argparse issue, I am still with 13.2. I was confused by
 the documentation:
 http://wiki.sugarlabs.org/go/Features/Start_activity_from_another_activity

 An activity can start other activity by:

- knowing the activity ID - starts that specific activity

 I assume that is a typo and bundle_id is meant.
  By having sugar-launch pass the -u (uri) and -o (object_id) options, it
 is possible now (and possibly since 0.82) to launch an activity by activity
 bundle_id either with a Journal object or a file from the Documents
 directory (visible in Journal) or a USB key (also visible in Journal).  I
 have been using the -o and -u options in sugar-launch for at least five
 years. This was discussed when this feature was first proposed.

 In effect, the api added to 106 is simply an alternate way to perform
 existing functions.

 Tony

 On 07/03/2015 09:29 AM, Sam P. wrote:

 Hi Tony,

 I think you have misunderstood the capabilities of the api.

 The api does not support launching with uris (which is something to look
 into for 108) or activity ids.

 The api supports bundle ids (open a new terminal activity) and object ids
 (open this memorize set).  This allows for many of the use cases you
 described although being very simple.

 Directly using sugar-launch from activity processes is suboptimal, as
 activities should not launch child processes (Rainbow security model).
 This was discussed when the feature was being implemented.

 I do not see why a feature that has some use cases and does not
 destabilise the rest of the system should be dropped so late in the cycle.

 Thanks,
 Sam



 ___
 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] adding gtk as a dependency on sugar-artwork

[Martin Abente]

Hello Sam, Gonzalo,

Now the new patch breaks it for Ubuntu 14.04, so I sent a new PR [1] which
doesn't break it (see my patch comment), please check it that works in
newer Fedora versions.

Regards,
Martin.

Refs:
1. https://github.com/sugarlabs/sugar-artwork/pull/68

On Thu, Jul 2, 2015 at 9:01 AM, Martin Abente 
martin.abente.lah...@gmail.com wrote:

 Will check today! Thanks Gonzalo and Sam!

 On Thu, Jul 2, 2015 at 7:29 AM, Gonzalo Odiard godi...@sugarlabs.org
 wrote:

 Martin,
 Are you ok with this new patch?

 Gonzalo

 On Thu, Jul 2, 2015 at 8:22 AM, Sam P. sam@sam.today wrote:

 Patch:  https://github.com/sugarlabs/sugar-artwork/pull/67

 On Thu, Jul 2, 2015 at 9:15 PM Gonzalo Odiard godi...@sugarlabs.org
 wrote:

 Great!

 On Thu, Jul 2, 2015 at 7:05 AM, Sam P. sam@sam.today wrote:

 Hi Gonzalo,

 Testing without your patch it appears that the journal background
 didn't get broken - so most of the breakage must have been fixed later in
 the Gtk+ 3.17 cycle!

 Using your patch (the 1st one), it fixes the log tree view and the
 journal still works fine.  I will send a patch.

 Next time I'll try to be more up to date with how the Gtk+ release
 cycle works so that I'm not submiting sugar patches for Gtk+ bugs!

 Thanks,
 Sam

 On Thu, Jul 2, 2015 at 5:02 AM Gonzalo Odiard godi...@sugarlabs.org
 wrote:

 If that don't work, should be good test:

 diff --git a/gtk3/theme/gtk-widgets.css.em
 b/gtk3/theme/gtk-widgets.css.em
 index 67e4e48..af87900 100644
 --- a/gtk3/theme/gtk-widgets.css.em
 +++ b/gtk3/theme/gtk-widgets.css.em
 @@ -221,9 +221,18 @@ column-header .button:hover:active {
  border-width: 0px;
  }

 +GtkTreeView row:even {
 +background-color: @row_even;
 +}
 +
  GtkTreeView row:nth-child(even) {
  background-color: @row_even;
  }
 +
 +GtkTreeView row:odd {
 +background-color: @row_odd;
 +}
 +
  GtkTreeView row:nth-child(odd) {
  background-color: @row_odd;
  }

 On Wed, Jul 1, 2015 at 3:15 PM, Gonzalo Odiard godi...@sugarlabs.org
  wrote:

 Sam,
 I don't have rawhide installed to test, can you try adding rules for
 the two new and old ways, like here:

 diff --git a/gtk3/theme/gtk-widgets.css.em
 b/gtk3/theme/gtk-widgets.css.em
 index 67e4e48..d14bbfb 100644
 --- a/gtk3/theme/gtk-widgets.css.em
 +++ b/gtk3/theme/gtk-widgets.css.em
 @@ -221,10 +221,11 @@ column-header .button:hover:active {
  border-width: 0px;
  }

 -GtkTreeView row:nth-child(even) {
 +GtkTreeView row:even, GtkTreeView row:nth-child(even) {
  background-color: @row_even;
  }
 -GtkTreeView row:nth-child(odd) {
 +
 +GtkTreeView row:odd, GtkTreeView row:nth-child(odd) {
  background-color: @row_odd;
  }

 Works on Gtk 3.16, we need check if works on Gtk 3.18

 Gonzalo

 On Wed, Jul 1, 2015 at 1:29 PM, Martin Abente 
 martin.abente.lah...@gmail.com wrote:

 From the tests I have done, I confirmed it is used in building
 time, therefore I have reverted the patch until we can determine a 
 better
 solution.

 On Wed, Jul 1, 2015 at 12:05 PM, Martin Abente 
 martin.abente.lah...@gmail.com wrote:

 Hello Sam,

 Different people reported an error while building sugar-artwork
 packages. The error is caused by this commit [1] which makes GTK a 
 building
 requirement for sugar-artwork, but:

 a) if GTK version version is really used on building time, then
 the approach used in [1] is wrong, because the css would depend on 
 the GTK
 version on the packager on something that is related to the final user
 runtime environment.

 b) if the GTK version is only used in running time, then we should
 make sure it does not become a building requirement.

 In either case, it does not seems to make sense to make it a
 dependency.

 Regards,
 Martin.


 Refs:
 1.
 https://github.com/sugarlabs/sugar-artwork/commit/813a2d77d83284b031a4f2bd5775b9f82b12846e





 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning




 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning




 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning




 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning



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

Re: [Sugar-devel] Change request: Fix open with API

[Martin Abente]

Hello Gonzalo,

To me this is basically a new feature, in terms of how it does impact sugar
(adding new method to the activity class and adding a new dbus endpoint to
the shell).

It breaks feature, API and code freezes. I believe the change is kind of
sensible considering what it does and specially since we are 3 days away
from the final release. Last week we landed a lot of trivial fixes, and
even then we needed an extra week to discover a serious issue with
sugar-artwork caused by one of these fixes, so certainly this could be more
dangerous.

Regarding the broken API, I see this differently, I don't think its about
adding an extra try catch. If the API is broken (because its use depends
on other method which shouldn't be allowed), then this feature should only
be used when both launch_bundle _and_ get_bundle are present (since
using the other method shouldn't be allowed anyway). Technically, this can
be seen as if this feature was not release yet (and we should not allow or
recommend its use until its really complete).

Now, if you still want to include it before Monday, then I think that you
should test it extensively in fc18 (and newer) and ubuntu 14.04, making
sure it works OK and that there are no other unwanted side effects (e.g, on
activities that does not this feature it or other services that consumes to
that dbus service).

Let me know what you want to do,
Martin.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Announcing] an extra UNSTABLE 0.105.3 release (code-frozen)

[Martin Abente]

Thanks German,

I also updated packages in [1] our custom archive of Ubuntu.

Refs:
[1]
https://wiki.sugarlabs.org/go/Ubuntu#OLPC_Ubuntu_Sugar_14.04.2_Trusty_LTS

On Wed, Jul 1, 2015 at 1:40 PM, German Ruiz - FundacionZT 
gr...@fundacionzt.org wrote:

 2015-06-30 16:16 GMT-06:00 Martin Abente martin.abente.lah...@gmail.com:
 
  Hello everyone,
 
  I just added one extra UNSTABLE release (0.105.3), basically to ease our
 testing before the final release on next Monday (July 6). If you are
 interested in helping out, the tarballs can be downloaded from:
 
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.105.3.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.105.3.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.105.3.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.105.3.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.105.3.tar.xz
 
  Consider the source code frozen [1]! We will only merge changes under
 exceptions now.
 
  Regards,
  Martin.
 
  Refs
  [1] http://wiki.sugarlabs.org/go/0.106/Roadmap

 Updated rpms are avaible for Fedora 18.

 http://wiki.sugarlabs.org/go/0.106/Testing#Fedora
 http://dev.laptop.org/~german/rpms-0105/

 Regards
 --
 German R S

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

[Sugar-devel] adding gtk as a dependency on sugar-artwork

[Martin Abente]

Hello Sam,

Different people reported an error while building sugar-artwork packages.
The error is caused by this commit [1] which makes GTK a building
requirement for sugar-artwork, but:

a) if GTK version version is really used on building time, then the
approach used in [1] is wrong, because the css would depend on the GTK
version on the packager on something that is related to the final user
runtime environment.

b) if the GTK version is only used in running time, then we should make
sure it does not become a building requirement.

In either case, it does not seems to make sense to make it a dependency.

Regards,
Martin.


Refs:
1.
https://github.com/sugarlabs/sugar-artwork/commit/813a2d77d83284b031a4f2bd5775b9f82b12846e
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] adding gtk as a dependency on sugar-artwork

[Martin Abente]

From the tests I have done, I confirmed it is used in building time,
therefore I have reverted the patch until we can determine a better
solution.

On Wed, Jul 1, 2015 at 12:05 PM, Martin Abente 
martin.abente.lah...@gmail.com wrote:

 Hello Sam,

 Different people reported an error while building sugar-artwork packages.
 The error is caused by this commit [1] which makes GTK a building
 requirement for sugar-artwork, but:

 a) if GTK version version is really used on building time, then the
 approach used in [1] is wrong, because the css would depend on the GTK
 version on the packager on something that is related to the final user
 runtime environment.

 b) if the GTK version is only used in running time, then we should make
 sure it does not become a building requirement.

 In either case, it does not seems to make sense to make it a dependency.

 Regards,
 Martin.


 Refs:
 1.
 https://github.com/sugarlabs/sugar-artwork/commit/813a2d77d83284b031a4f2bd5775b9f82b12846e

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

Re: [Sugar-devel] Delaying 0.106 for one week

[Martin Abente]

On Mon, Jun 29, 2015 at 11:03 AM, Martin Abente 
martin.abente.lah...@gmail.com wrote:

 Sure, I can do that tomorrow.

 Regarding the triage meeting, what about tomorrow (June 30) 13:00 UTC?


No quorum it seems, so I will be reviewing the remaining PRs and merging
them. We should freeze code after that,  and if nothing too unexpected
happens, we release 0.106 on Monday.



 On Mon, Jun 29, 2015 at 10:14 AM, Gonzalo Odiard godi...@sugarlabs.org
 wrote:

 Martin,
 Maybe you can release a new set of packages to try involve more people in
 the testing?

 Gonzalo

 On Fri, Jun 26, 2015 at 5:55 PM, Peter Robinson pbrobin...@gmail.com
 wrote:

 On Fri, Jun 26, 2015 at 9:40 PM, Martin Abente
 martin.abente.lah...@gmail.com wrote:
  Hello everyone,
 
  I am strongly considering to delay the 0.106 release by one week, from
 June
  29 to July 6 [1]. The reasons for this delay are:
 
  Aymara translations are very close to be fully completed, _very_ few
  translations are missing and it would be a shame to release 0.106 with
  incomplete translations for so few. I have already requested Edgar and
  Sebastian to work together to finish these last translations so the
 new .PO
  can be merged.
  Luckily for us, this week we had a burst of activity in github with
 many
  useful bug fixes, but at the same time I would like to have some extra
 time
  to make sure everything is in place before the final release.
 
  Thanks for your understanding,

 Fine by me, F-23 is well over a month prior to branching for alpha :-)
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




 --
 Gonzalo Odiard

 SugarLabs - Software for children learning



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

Re: [Sugar-devel] GCI 2014 Wrapup

[Martin Abente]

I knew it would be fun :) Thanks to you guys for all the code you send!


On Tue, Jun 30, 2015 at 2:58 PM, Gonzalo Odiard godi...@sugarlabs.org
wrote:

 Great news! Congratulations, is well deserved for both, Ignacio and you.
 Thanks for sharing!

 PS: I need change my signature :)

 On Fri, Jun 26, 2015 at 11:58 PM, Sam P. sam@sam.today wrote:


 Hi All,

 Ignacio and I recently went to San Fransisco as our GCI 2014 prize [1].
 San Francisco was a beautiful city and seeing Google (and a little Mozilla
 and Twitter) was a really amazing experience.

 But it wasn't just about San Fransisco.  Walter was also in San Fransisco
 which was amazing [2].  It was great to be chat sugar in real life with
 Walter and Ignacio.  Despite the very fun atmosphere of the trip, we even
 managed to hack together on some productive things :)  Walter and I hacked
 on the website a little (I'll smooth the edges of that soon so we can push
 it), while Ignacio and Walter jammed on turtlejs.

 The Google Code In was a great competition and opportunity for me (and
 probably many other participants) to become involved with open source.  Of
 course, thank you to Google for running it.

 But thank you very much to everyone who mentored us during the GCI.
 Thank you to Gonzalo, Tch and Walter who hugely increased their code review
 workloads to help teach us all how to participate in open source.  Thank
 you to everyone who made it possible that we didn't just make software for
 learning children but also a software by learning children, because you
 guys teach us so much.

 Thanks,
 Sam

 [1] http://people.sugarlabs.org/sam/gci2014-2.jpeg
 [2] http://people.sugarlabs.org/sam/gci2014-1.jpeg

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




 --
 Gonzalo Odiard

 SugarLabs - Software for children learning

 ___
 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] [Announcing] an extra UNSTABLE 0.105.3 release (code-frozen)

[Martin Abente]

Hello everyone,

I just added one extra UNSTABLE release (0.105.3), basically to ease our
testing before the final release on next Monday (July 6). If you are
interested in helping out, the tarballs can be downloaded from:

   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.105.3.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.105.3.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.105.3.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.105.3.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.105.3.tar.xz

Consider the source code *frozen [1]*! We will only merge changes under
exceptions now.

Regards,
Martin.

Refs
[1] http://wiki.sugarlabs.org/go/0.106/Roadmap
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Delaying 0.106 for one week

[Martin Abente]

Sure, I can do that tomorrow.

Regarding the triage meeting, what about tomorrow (June 30) 13:00 UTC?

On Mon, Jun 29, 2015 at 10:14 AM, Gonzalo Odiard godi...@sugarlabs.org
wrote:

 Martin,
 Maybe you can release a new set of packages to try involve more people in
 the testing?

 Gonzalo

 On Fri, Jun 26, 2015 at 5:55 PM, Peter Robinson pbrobin...@gmail.com
 wrote:

 On Fri, Jun 26, 2015 at 9:40 PM, Martin Abente
 martin.abente.lah...@gmail.com wrote:
  Hello everyone,
 
  I am strongly considering to delay the 0.106 release by one week, from
 June
  29 to July 6 [1]. The reasons for this delay are:
 
  Aymara translations are very close to be fully completed, _very_ few
  translations are missing and it would be a shame to release 0.106 with
  incomplete translations for so few. I have already requested Edgar and
  Sebastian to work together to finish these last translations so the new
 .PO
  can be merged.
  Luckily for us, this week we had a burst of activity in github with many
  useful bug fixes, but at the same time I would like to have some extra
 time
  to make sure everything is in place before the final release.
 
  Thanks for your understanding,

 Fine by me, F-23 is well over a month prior to branching for alpha :-)
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




 --
 Gonzalo Odiard

 SugarLabs - Software for children learning

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

Re: [Sugar-devel] Delaying 0.106 for one week

[Martin Abente]

Sure, but for this particular release, I honestly prefer to invest time
testing it the best we can, and only push fixes selectively if we find
regressions on the fixes we landed recently or if we find something new
something that we consider extremely critical.

If we push changes last minute, we won't be able to test it properly.


On Fri, Jun 26, 2015 at 4:42 PM, Gonzalo Odiard godi...@sugarlabs.org
wrote:

 No problem, but could we do a meeting next Monday and triage pending bugs
 to see what have higher priority?

 Gonzalo

 On Fri, Jun 26, 2015 at 5:40 PM, Martin Abente 
 martin.abente.lah...@gmail.com wrote:

 Hello everyone,

 I am strongly considering to delay the 0.106 release by one week, from
 June 29 to July 6 [1]. The reasons for this delay are:

- Aymara translations are very close to be fully completed, _very_
few translations are missing and it would be a shame to release 0.106 with
incomplete translations for so few. I have already requested Edgar and
Sebastian to work together to finish these last translations so the new 
 .PO
can be merged.
- Luckily for us, this week we had a burst of activity in github with
many useful bug fixes, but at the same time I would like to have some 
 extra
time to make sure everything is in place before the final release.

 Thanks for your understanding,
 Martin.

 Refs:
 [1] http://wiki.sugarlabs.org/go/0.106/Roadmap





 --
 Gonzalo Odiard

 SugarLabs - Software for children learning

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

Re: [Sugar-devel] Integrating the translations for sugar and sugar-toolkit-gtk3

[Martin Abente]

Hola de nuevo,

Aprovecho para tratar el siguiente problema:

La semana pasada, actualice todos los .PO de sugar y sugar-toolkit-gtk3 en
Pootle, de modo a que podamos actualizar los nuevos textos que se agregaron
para el inminente release 0.106. Ahora, he notado que los .PO de Aymara de
ambos proyectos [1,2] han sido sobre-escritos con una versión anterior
donde los textos nuevos no están disponibles.

@Edgar, @Sebatian: Les sería posible completar las traducciones de los
nuevos textos a Aymara? Son realmente pocos textos y no debería tomar mucho
tiempo. Lo mejor sería tener una traducción completa a Aymara en el release
0.106. Un vez completo e integrado, pueden volver a sobre-escribir en
Pootle cuantas veces necesiten.

He vuelto a actualizar dichos .PO, pero antes he subido copias de respaldo
[3] de la versión anterior.

Muchas gracias,
Martín.

[1] http://translate.sugarlabs.org/ayc/sugar/
[2] http://translate.sugarlabs.org/ayc/sugar-toolkit-gtk3/
[3] http://people.sugarlabs.org/~tch/aymara/


2015-06-25 13:17 GMT-04:00 Walter Bender walter.ben...@gmail.com:

 2015-06-25 12:18 GMT-04:00 Sebastian Silva sebast...@fuentelibre.org:
 
  On 25/06/15 09:06, Martin Abente wrote:
 
  Hola de nuevo,
 
  @Edgar: (...)
 
  @Sebastian: podrías ser más explicito en cuanto a que deberíamos
 permitir?
  No entiendo que exactamente estás solicitando. Como también eres
  administrador de translate.sugarlabs.org, y trabajas más de cerca con
 ellos,
  te pido que los asistas en lo que fuere necesario.
 
 
 
  El ministerio ha dispuesto a otra persona (Roger Gonzalo) para que sea
  responsable de las traducciones y es necesario permitirle a Roger
 completar
  su encargo.
 
  Explícitamente te estoy solicitando que NO pidan a Edgar que trabaje en
 las
  traducciones de Aymara - mas bien incluso que le pidan que NO lo haga.
 
  Edgar ha estado modificando el trabajo de Roger antes que el
 especialista en
  lenguas que supervisa su trabajo haya tenido tiempo de mirar. Esto está
  generando un conflicto que no permite concluir el trabajo.

 This is not how the community workflow has even been in the past.
 Edgar is the one who had been maintaining Aymara. To unilaterally
 decree that he should defer to someone with no track-record with the
 community seems a bit over the top. I presume we can come to some
 understanding, but asking the person who has done so much great work
 to stop seems a very bad precedent. Perhaps Roger can join the
 discussion and give us a sense of who he is and what he is doing
 directly.

 regards.

 -walter

 
  Siempre hemos apreciado la contribución de Edgar pero también es
 necesario
  colaborar con el Ministerio si el objetivo es que el trabajo llegue a los
  niños.
 
 
  Respecto a las traducciones de sugar y sugar-toolkit-gtk3
 (específicamente)
  a Quechua y Awajún, las veo muy incompletas aun. Alguna idea de cuando
 tiene
  el ministerio planeado terminarlas?
 
  Esperaría que finales de Julio.
  Estamos en un proceso coordinado y supervisado, que va a requerir un
 tiempo,
  y no estará concluído esta semana.
 
  Saludos,
  Martín.
 
  [1] http://translate.sugarlabs.org/ayc/sugar/
  [2] http://translate.sugarlabs.org/ayc/sugar-toolkit-gtk3/
 
 
  Una vez terminada la etapa formal, esperaríamos que con calma Edgar y
 Roger
  puedan resolver sus discrepancias estilísticas y esto concluya con
  traducciones de Aymara perfeccionadas y revisadas por varios ojos.
 
 
  --
  I+D SomosAzucar.Org
  icarito #somosazucar en Freenode IRC
  Nadie libera a nadie, nadie se libera solo. Los seres humanos se
 liberan en
  comunión - P. Freire



 --
 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] Delaying 0.106 for one week

[Martin Abente]

Hello everyone,

I am strongly considering to delay the 0.106 release by one week, from June
29 to July 6 [1]. The reasons for this delay are:

   - Aymara translations are very close to be fully completed, _very_ few
   translations are missing and it would be a shame to release 0.106 with
   incomplete translations for so few. I have already requested Edgar and
   Sebastian to work together to finish these last translations so the new .PO
   can be merged.
   - Luckily for us, this week we had a burst of activity in github with
   many useful bug fixes, but at the same time I would like to have some extra
   time to make sure everything is in place before the final release.

Thanks for your understanding,
Martin.

Refs:
[1] http://wiki.sugarlabs.org/go/0.106/Roadmap
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Integrating the translations for sugar and sugar-toolkit-gtk3

[Martin Abente]

Hola de nuevo,

@Edgar: si ingresas a las traducciones de sugar [1] y sugar-toolkit-gtk3
[2] a Aymara, verás que hay una opción que dice expand details (o
expandir detalles en español). Al hacer clic en esa opción, la plataforma
te va a mostrar algunos problemas con las traducciones de esos proyectos,
ej., espacios de mas, puntuaciones faltantes, entre otros detalles. Serial
ideal que pudieses resolver esos errores antes del lunes para que podamos
integrar los cambios en el mejor estado posible.

@Sebastian: podrías ser más explicito en cuanto a que deberíamos permitir?
No entiendo que exactamente estás solicitando. Como también eres
administrador de translate.sugarlabs.org, y trabajas más de cerca con
ellos, te pido que los asistas en lo que fuere necesario.

Respecto a las traducciones de sugar y sugar-toolkit-gtk3 (específicamente)
a Quechua y Awajún, las veo muy incompletas aun. Alguna idea de cuando
tiene el ministerio planeado terminarlas?

Saludos,
Martín.

[1] http://translate.sugarlabs.org/ayc/sugar/
[2] http://translate.sugarlabs.org/ayc/sugar-toolkit-gtk3/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Integrating the translations for sugar and sugar-toolkit-gtk3

[Martin Abente]

Hello everyone,

We are one week away [1] from the first stable release 0.106 and its time
to start integrating the new translations to sugar [2] and
sugar-toolkit-gtk3 [3], so we can spend this week doing some minimal QA.

Please reply to this email with the link to your Pootle language project
(e.g, [4]), and I will handle the merge. But first, make sure the
translation is 100% complete and revise any errors shown in the expand
details page.

Regards,
Martin.

Refs:
[1] http://wiki.sugarlabs.org/go/0.106/Roadmap
[2] http://translate.sugarlabs.org/projects/sugar/
[3] http://translate.sugarlabs.org/projects/sugar-toolkit-gtk3/
[4] http://translate.sugarlabs.org/gn/sugar/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Integrating the translations for sugar and sugar-toolkit-gtk3

[Martin Abente]

Hola Edgar,

Me fije que tienes las traducciones para Aymara (Aru) casi listas. El lunes
[1] vamos a liberar una nueva versión estable de Sugar, por lo tanto esta
semana debemos integrar al código las traducciones de sugar [2] y
sugar-toolkit-gtk3 [3].

Podrías agregar las traducciones faltantes y revisar las advertencias que
se muestran en la opción expandir detalles / expand details? Si crees que
ya están listas las integro.

Saludos,
Martín.

[1] http://wiki.sugarlabs.org/go/0.106/Roadmap
[2] http://translate.sugarlabs.org/ayc/sugar/
[3] http://translate.sugarlabs.org/ayc/sugar-toolkit-gtk3/

On Mon, Jun 22, 2015 at 8:29 PM, Walter Bender walter.ben...@gmail.com
wrote:

 Can you please make contact with Edgar to make sure his Aymara updates
 land? thx.

 -walter

 On Mon, Jun 22, 2015 at 4:38 PM, Martin Abente
 martin.abente.lah...@gmail.com wrote:
  Hello everyone,
 
  We are one week away [1] from the first stable release 0.106 and its
 time to
  start integrating the new translations to sugar [2] and
 sugar-toolkit-gtk3
  [3], so we can spend this week doing some minimal QA.
 
  Please reply to this email with the link to your Pootle language project
  (e.g, [4]), and I will handle the merge. But first, make sure the
  translation is 100% complete and revise any errors shown in the expand
  details page.
 
  Regards,
  Martin.
 
  Refs:
  [1] http://wiki.sugarlabs.org/go/0.106/Roadmap
  [2] http://translate.sugarlabs.org/projects/sugar/
  [3] http://translate.sugarlabs.org/projects/sugar-toolkit-gtk3/
  [4] http://translate.sugarlabs.org/gn/sugar/
 
  ___
  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

Re: [Sugar-devel] license of layout.py in Sugar Calculate activity

[Martin Abente]

Hello Jonas,

Thanks for taking the time to let us know. The new maintainer of Calculate
is Gonzalo (cc'ed).

For future reference, you can check this [1] list to see who is currently
maintaining an activity (we certainly need to improve our communication
channels).

Regards,
Martin.

[1]
http://wiki.sugarlabs.org/go/Translation_Team/Pootle_Projects/Repositories

On Thu, Jun 18, 2015 at 1:14 PM, Jonas Smedegaard d...@jones.dk wrote:

 Hi Aneesh,

 I maintain Sugar packaging of Sugar for Debian, and noticed that in the
 Calculate activity you've declared copyright for layout.py but not
 included a license.

 Please always include an explicit license statement where a copyright is
 stated, because a lack of license statement does not mean look in same
 folder for a COPYING file but instead in many jurisdictions imply All
 rights reserved which I suspect was not your intention :-)

 Kind regards,

  - Jonas

 --
  * Jonas Smedegaard - idealist  Internet-arkitekt
  * Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private

 ___
 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] This is just a test

[Martin Abente]

Apologies for the wasted inbox space!
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Making Record support external cameras

[Martin Abente]

On Wed, Jun 10, 2015 at 10:51 AM, Gonzalo Odiard godi...@sugarlabs.org
wrote:

 Tch, do yoou have any usb camera to test this?


Not at the moment, but I borrow one on the weekend.



 Gonzalo

 On Wed, Jun 10, 2015 at 12:57 AM, James Cameron qu...@laptop.org wrote:

 On Wed, Jun 10, 2015 at 12:03:11AM -0300, Gonzalo Odiard wrote:
  There are more drivers for different cameras? Any way to know what
  are the camera drivers?
  (or the usb camera drivers)

 Yes, there are many more drivers disabled.

 At OLPC we chose to enable the drivers that are needed, and leave
 deployments to enable other drivers.  This was to shrink filesystem;
 very important on XO-1 and early XO-1.5, but not important now for
 XO-1.75 and XO-4.

 No, there's no way to find out what drivers are needed, except by
 audit or survey of all users.

 You might compare /boot/config* between Fedora and OLPC kernel, and
 add whatever Fedora has enabled.

 --
 James Cameron
 http://quozl.linux.org.au/




 --
 Gonzalo Odiard

 SugarLabs - Software for children learning

 ___
 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] Update PO files in Pootle

[Martin Abente]

I have just updated sugar and sugar-toolkit-gtk3 POs.

@sebastian: I left a backup of POs and DB in a place where you can find it.

On Tue, Jun 2, 2015 at 11:46 AM, Sebastian Silva sebast...@somosazucar.org
wrote:


 On 01/06/15 15:38, Martin Abente wrote:
  If anyone is working in our Pootle instance and needs the current
  versions of these PO files, I can provide a backup of these files as
  they are before I update.
 Thanks for working on this. I would appreciate the backup for the
 current po files so that I can compare them and let translators know of
 any changes.


  There might be ways to address this more elegantly, but I _personally_
  don't the time to research and deploy (if somebody does, please step in).
 
 I don't think there are elegant ways to deal with string changes, except
 translating them again. Not sure what you mean, then.

 Thanks for working on this,
 Sebastian

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

Re: [Sugar-devel] [Announcing] UNSTABLE 0.105.2 (Strings, UI and API frozen)

[Martin Abente]

Thanks German!

For those interested in Ubuntu, I just updated the packages for [1].

Refs:
1. http://wiki.sugarlabs.org/go/Ubuntu

On Mon, Jun 1, 2015 at 11:30 AM, German Ruiz - FundacionZT 
gr...@fundacionzt.org wrote:

 2015-06-01 8:03 GMT-06:00 Martin Abente martin.abente.lah...@gmail.com:
  Hello everyone,
 
  I am pleased to announce another release in our road to 106 development
  cycle [1]. This time, the release marks the end of the period for
 Strings,
  UI and API changes. From now on, and until the stable release in a
 month, we
  will be focusing on fixing critical bugs and updating translations.
 
  The tarballs for this release:
 
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.105.2.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.105.2.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.105.2.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.105.2.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.105.2.tar.xz
 
  Many thanks to everyone who keeps contributing in this development cycle!
 
  Martin.
 
  Refs:
  1. http://wiki.sugarlabs.org/go/0.106/Roadmap

 For those who want to test it on XO hardware, updated rpms are avaible
 at this repo[0][1], clean images are on their way :)

 [0] http://dev.laptop.org/~german/rpms-0105/
 [1] http://wiki.sugarlabs.org/go/0.106/Testing#Testing_with_updates

 --
 German  R S

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

[Sugar-devel] [Announcing] UNSTABLE 0.105.2 (Strings, UI and API frozen)

[Martin Abente]

Hello everyone,

I am pleased to announce another release in our road to 106 development
cycle [1]. This time, the release marks the end of the period for Strings,
UI and API changes. From now on, and until the stable release in a month,
we will be focusing on fixing critical bugs and updating translations.

The tarballs for this release:

   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.105.2.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.105.2.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.105.2.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.105.2.tar.xz
   -
   
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.105.2.tar.xz

Many thanks to everyone who keeps contributing in this development cycle!

Martin.

Refs:
1. http://wiki.sugarlabs.org/go/0.106/Roadmap
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Update PO files in Pootle

[Martin Abente]

Hello everyone,

We are a month away from the release of Sugar 0.106 and we need to update
the sugar [1] and sugar-toolkit-gtk3 [2] PO files in Pootle. We don't have
branches as we used to do in the previous instance, this means that the
PO files will be adapted to what is currently in our projects upstream
sources. Existing translations will remain but there might be small
differences from the previous PO versions (ie., in case a string was
changed or removed).

If anyone is working in our Pootle instance and needs the current versions
of these PO files, I can provide a backup of these files as they are before
I update. There might be ways to address this more elegantly, but I
_personally_ don't the time to research and deploy (if somebody does,
please step in).

I will wait until this Wednesday (June 3), in case this mail gets delayed ;)

Regards,
Martin.

Refs:
1. http://translate.sugarlabs.org/projects/sugar/
2. http://translate.sugarlabs.org/projects/sugar-toolkit-gtk3/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Sugar-news] Sugar DIgest 2015-05-26

[Martin Abente]

I never had to chance to meet Marco but I can say that I only have heard
wonderful things about him, as a human being and as an engineer. My most
sincere condolences to his family and friends.

On Tue, May 26, 2015 at 5:07 PM, Christoph Derndorfer 
christ...@olpcnews.com wrote:

 On Tue, May 26, 2015 at 3:28 PM, Walter Bender walter.ben...@gmail.com
 wrote:

 1. It is with great sadness that write these words: Marco Presenti
 Gritti, the principal Sugar developer from Red Hat from 2006 to 2008 and
 one of the founders of Sugar Labs, passed away this past weekend after a
 long illness. Marco was a brilliant engineer whose work still reverberates
 throughout the Sugar stack and a warm, personable colleague, father, and
 husband. We will miss you Marco.


 Thank you for sharing this sad news which I - and I assume many others
 here - would have missed otherwise.

 Reading it made me go back through my e-mail and photo archives and I
 found this shot from FUDCon Brno in September 2008:

 [image: Inline image 1]

 I'll always remember mpg like that: A brilliant and cheerful software
 engineer amidst like-minded and equally friendly and dedicated software
 geniuses who built the foundations of Sugar.

 And +1 to Gonzalo's suggestions of dedicating 0.106 to Marco and his young
 family!

 If anyone has his physical address please let me know as I'd love send my
 condolences to his two Danielas in this time of sadness and mourning.

 Christoph



 == Sugar Digest ==

 2. For those of you who are interested, we hold our GSoC group meetings
 on Fridays, 11:00 EST (Boston), 14:00 UTC on irc.freenode.net
 #sugar-meeting.

 === Tech Talk ===

 3. Peter Robinson, Sam Parkinson, Sean Daly, and Iain Brown Douglas have
 done a great job of revamping the Sugar on a Stick spin site for Fedora.
 Please see [1].

 === Sugar Labs ===

 4. Please visit our planet [2].

 ---

 [1] http://spins.stg.fedoraproject.org/en/soas/
 [2] http://planet.sugarlabs.org

 -walter


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

 ___
 Community-news mailing list
 community-n...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/community-news




 --
 Christoph Derndorfer

 volunteer, OLPC (Austria) [www.olpc.at]
 editor, OLPC News [www.olpcnews.com]
 co-founder, TechnikBasteln® [www.technikbasteln.net]

 e-mail: christ...@derndorfer.eu

 ___
 Community-news mailing list
 community-n...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/community-news

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

[Sugar-devel] Bundlebuilder and mime-type related files

[Martin Abente]

Hello everyone,

Recently, when packaging activities for Debian/Ubuntu, I noticed that my
packaged activities contained many unexpected/unnecessary files under
/usr/share/mime. These files were clashing with other activities files I
packaged, because they were under the exact same path and name.

After investigating, I noticed that  our bundlebindler (ie., activity
installation script) makes a call to update-mime-database tool and also
creates some symlinks, and that Fedora and Debian packaging files uses
bundlebuilder (through /setup.py install) to populate the packages files
and dirs. The problem is not present in Fedora packages, my first guess is
it because /usr/share/mime directory is ignored from the final package
(doesn't seem to be the case for Debian/Ubuntu).

This is only happens when the activities provide a mimetypes.xml files in
the ./actvity/ directory.

The idea of this thread is to see if we can agree on a solution for this
problem. Here is an initial discussion that happened over IRC between Jonas
and me:

jo0nas tch__: sugar3/bundle/activitybundle symlink handling seems
 fundamentally wrong to me: It creates symlink from _build_ area to
 _install_ area - that only works when build area is same host as install,
 and is not purged
 jo0nas for Debian I will remove mimetype symlinks and properly _install_
 (not symlink) relevant files into install area
 tch__ jo0nas, thanks for the insight, what do you suggest we can do to
 improve that in upstream side?
 jo0nas simplest approach is to copy, not symlink
 jo0nas I suspect symlinking is done to save space - but it has the
 assumption that build (a.k.a. unpacking-source for most activitites) path
 will be sustained after (partly-pseudo-)install
 tch__ jo0nas, yes, and did you also notice the update-mime-database
 stuff? it _does_ creates database files and these _are_ included in the
 packages
 jo0nas to cover both user-pseudo-install and system-real-install
 sugar-toolkit-gtk3 needs to distinguish between those two
 tch__ jo0nas, (try with a package that has an actvity/mimetypes.xml file)
 tch__ s/package/activity/
 jo0nas no, I did not notice binary MIME database files getting included
 in packages
 tch__ jo0nas, it happened to me,
 tch__ jo0nas, let me see one example,
 * artista_ has quit (Ping timeout: 244 seconds)
 jo0nas at what path inside the .deb package did the binary MIME file(s)
 get installed?
 tch__ /usr/share/mime/
 jo0nas did you use CDBS python-sugar.mk snippet?
 tch__ yes, I follow pretty much your files
 jo0nas on Debian Sid, or...?  Which activity?
 tch__ jo0nas, I am currently testing in ubuntu trusty, but I remember
 double checking this on Jessie
 tch__ jo0nas, and with some of the new activities I packaged, ie.,
 stopwatch
 * k_yash has quit (Ping timeout: 246 seconds)
 jo0nas it would be nice for sugar-toolkit-gtk3 to grow a --system flag -
 I already now paper over its relying on user-specific XDG paths
 tch__ jo0nas, maybe we can sketch something together? there is still
 time to push it on this devel cycle
 jo0nas I really don't know the internals good enough
 tch__ jo0nas, I considered something like you mentioned earlier, to add
 an option to setup.py to completely avoid creating these symliks and update
 database, and leave that to packaging realm
 tch__ jo0nas, but it can become a burden to packaging too,
 jo0nas I just see that I currently prefix calls to install.py with this:
 LANG=C XDG_DATA_HOME=$(DEB_DESTDIR)/usr/share
 jo0nas ...in addition to setting --prefix=$(DEB_DESTDIR)/usr
 tch__ jo0nas, so, if we can find a decent solution for upstream, even if
 its copying the files it could work
 tch__ maybe copying the files + avoiding update step?
 tch__ then packaging realm only needs to run the update in something
 like postinst
 jo0nas this is essentially how I currently install: LANG=C
 XDG_DATA_HOME=$(DEB_DESTDIR)/usr/share python setup.py install
 --prefix=$(DEB_DESTDIR)/usr
 jo0nas makes sense to me that I instead would do this: python setup.py
 install --system --prefix=$(DEB_DESTDIR)/usr
 jo0nas ...which would then a) set paths based only on --prefix, not some
 parts based on XDG dirs, and b) really truly fully install (i.e. copy stuff
 not symlink)
 jo0nas ...and according to you it should then also c) avoid running
 update-mime-database, but I have not seen that go wrong myself yet
 jo0nas not sure if the option would be better named --shared
 tch__ jo0nas, neither I to be honest, but what about copying this
 conversation to the sugar-ml?
 jo0nas feel free to do so - but please keep me explicitly CCed, as I am
 not subscribed there
 tch__ jo0nas, if we can think and agree on something I could try to land
 it next week
 tch__ jo0nas, of course,


So basically, there are 2 problems.

1. symlinks creation during ./setup.py --install (for installing the
mimetypes.xml file .svg icons for mime types declared in activity.info)
 and,
2. the execution of update-mime-database (which generates the database

Re: [Sugar-devel] [Announcing] UNSTABLE 0.105.1 (feature frozen)

[Martin Abente]

Many thanks German!

On Tue, May 19, 2015 at 4:25 PM, German Ruiz - FundacionZT 
gr...@fundacionzt.org wrote:

 2015-05-18 7:45 GMT-06:00 Martin Abente martin.abente.lah...@gmail.com:
  Hello everyone,
 
  I am pleased to announce a new release of our road to 0.106 development
  cycle. This release marks the end of the period for including new
 features
  [1], from now on, we will focus on stability, translations and improving
  existing features. For those interested in testing and/or packaging I
  recommend to look at the new merged features [2].
 
  Tarballs:
 
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.105.1.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.105.1.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.105.1.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.105.1.tar.xz
 
 http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.105.1.tar.xz
 
 
  Many thanks to the developers who contributed this release!
 
  Martin.
 
  Refs:
  1. http://wiki.sugarlabs.org/go/0.106/Roadmap
  2. http://wiki.sugarlabs.org/go/0.106/Feature_List
 
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 

 Hello Sugar community

 For those who want to test this version on sugar on XO1 and 1.5, you
 can follow instructions detailed here
 http://wiki.sugarlabs.org/go/0.106/Testing

 Regards

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