Re: [Sugar-devel] critical vs pinned repositories, was New pull request reviewers; Rahul and Yash

[Tony Anderson]

This thread illustrates the crazy situation we have put ourselves in. 
Now we don't use github because we have too many repositories.


The simple solution is to separate repositories into a Sugar collection 
and an Activity collection. The use of fructose (and honey,...) should 
be deprecated. The terms have no meaning and are confusing. Can you 
imagine the user launching the chat-fructose.activity (not to mention 
translating 'fructose' to 100+ languages). Searching 300+ activities is 
not necessary if they are sorted alphabetically (abacus.activity, 
write.activity) and would be made easier if the activity names in ASLO 
matched the repostory names.


The repositories in Sugar should be ones required for a build. A build 
requires co-ordinated use of multiple repositories. Activities should be 
independent of each other and of Sugar builds. The maker of a build 
selects the activities to include in the build from those released.


Browse illustrates the problem with using common dependencies. Now it is 
critical to use the Browse version which works with the right build. 
This is contrary to the spirit of activities - that Sugar exists to 
provide the execution environment for activities. Meanwhile, the 
functionality of Browse becomes increasingly impaired. For example, 
Browse cannot download or resume html pages. It does not have 
configuration capabilities. A 404 error triggers a google search even 
when the connection is to a school server. It is not able to display 
console.log statements in javascript. It is not able to show the source 
code of a web page. It is not capable of saving a web page in the 
Journal (it saves urls of open tabs which is normally useless and 
consumes time discovering that the XO is not online).


Meanwhile, moving development support to github is making it more 
difficult for users to modify their own installation. First, we chose 
'view source' which suggests 'look but don't touch'. Then we wrapped 
Python programming in pippy where a user can create an activity by pippy 
magic. This, of course, hides the process from the user -- similar to 
the effect of using Dreamweaver to create html/css. Now we have taken 
development support away from the user who does not have ready internet 
access (i.e. more than half our users).


Tomorrow I am scheduled to give a class to secondary school students on 
programming. The students are already capable of using the Terminal 
activity to navigate and manage the XO file system. Generally I 
encourage them to use the Documents folder since it is visible in the 
Journal activity.


I plan to start with the Hello World activity. The repository for this 
activity is hello-world-fork-master - this for the activity intended to 
illustrate the simplest possible activity!!! To display 'Hello World!' 
on the screen takes 42 lines of python code. The hello-world-fork-master 
repository is a conversion of the original to gtk3 but continues to be 
version 6!


I have moved the toolbar related code to a separate file - toolbar.py. 
This file is imported into activity.py. This reduces the number of lines 
from 42 to 10. This is version 7.


More importantly, this activity is a useful template for user-developed 
activities. Al Sweigart has written three books on Python programming 
for children and has given them a Creative Commons license!  My plan for 
the class is to show the students how to make Al Sweigart's examples 
into Sugar activities by copying the hello-world.activity to 
guessing-game.activity and updating activity.info in the new activity. 
Then the students can copy and paste their code into activity.py.


None of the programs in the Al Sweigart's first two books use GTK (only 
print and raw_input). Naturally this is a problem for a Sugar activity 
which displays print statements in the log and requires gtk to display 
text on the screen. However, this is a learning opportunity for the 
students.


I truly wish some of this community effort and ingenuity were applied to 
making Sugar a better educational environment, giving our users the 
opportunity to explore and create rather than restricting it to elite 
developers.


Tony




On Wednesday, 28 February, 2018 08:34 AM, Walter Bender wrote:



On Tue, Feb 27, 2018 at 10:02 PM, James Cameron > wrote:


My list of critical repositories was on a thread focused on Sugar
desktop and Python activity code review.  It is less relevant for
Sugar Labs as a whole.

The mismatch at heart is GitHub's scalability of features for large
open source projects with many repositories.  We have 292 at the
moment.  Most are orphaned or abandoned.  Using search is critical.

Once a developer is familiar with our repository layout, the problem
disappears for them.  Does our ramp-up documentation explain well
enough?  I don't think I've heard many "where is X?" questions.

We could waste a lot of time moving 

Re: [Sugar-devel] critical vs pinned repositories, was New pull request reviewers; Rahul and Yash

[Walter Bender]

On Tue, Feb 27, 2018 at 10:02 PM, James Cameron  wrote:

> My list of critical repositories was on a thread focused on Sugar
> desktop and Python activity code review.  It is less relevant for
> Sugar Labs as a whole.
>
> The mismatch at heart is GitHub's scalability of features for large
> open source projects with many repositories.  We have 292 at the
> moment.  Most are orphaned or abandoned.  Using search is critical.
>
> Once a developer is familiar with our repository layout, the problem
> disappears for them.  Does our ramp-up documentation explain well
> enough?  I don't think I've heard many "where is X?" questions.
>
> We could waste a lot of time moving repositories around to meet
> consistent naming standards; I'd like to see reasoned benefit before
> doing that.
>
> I recently changed the pinned repositories.  I'd have pinned Sugarizer
> and Music Blocks, but they are both being developed outside Sugar Labs
> on GitHub personal accounts.  That's why I've got Browse and Turtle
> Art pinned.
>

The reason Turtle Blocks and Music Blocks are still hosted in my personal
repo is because we have had a backlog on sysadmin support, it has not been
practical to host projects on the Sugar Labs servers. Using github.io makes
things pretty painless. But because we have not yet set up a github,io
presence for Sugar Labs, so I haven't moved the repos. I'll try to finally
wrap my head around what sugarlabs.github.io might look like and make some
suggestions on this list.

>
> We could also waste a lot of time on dashboards or other
> meta-development.  If we have a volunteer to do that, great, but I'm
> not putting my hand up.
>
> Repositories containing submodules for a collection of activities
> might be interesting, but it brings a new problem; maintenance of the
> repository in the face of ongoing change in the submodules.  We've had
> to back away from submodules in Browse because of repeating bugs where
> a downstream used a GitHub release tag instead of our tarball.
>
> --
> James Cameron
> http://quozl.netrek.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

Re: [Sugar-devel] critical vs pinned repositories, was New pull request reviewers; Rahul and Yash

[James Cameron]

My list of critical repositories was on a thread focused on Sugar
desktop and Python activity code review.  It is less relevant for
Sugar Labs as a whole.

The mismatch at heart is GitHub's scalability of features for large
open source projects with many repositories.  We have 292 at the
moment.  Most are orphaned or abandoned.  Using search is critical.

Once a developer is familiar with our repository layout, the problem
disappears for them.  Does our ramp-up documentation explain well
enough?  I don't think I've heard many "where is X?" questions.

We could waste a lot of time moving repositories around to meet
consistent naming standards; I'd like to see reasoned benefit before
doing that.

I recently changed the pinned repositories.  I'd have pinned Sugarizer
and Music Blocks, but they are both being developed outside Sugar Labs
on GitHub personal accounts.  That's why I've got Browse and Turtle
Art pinned.

We could also waste a lot of time on dashboards or other
meta-development.  If we have a volunteer to do that, great, but I'm
not putting my hand up.

Repositories containing submodules for a collection of activities
might be interesting, but it brings a new problem; maintenance of the
repository in the face of ongoing change in the submodules.  We've had
to back away from submodules in Browse because of repeating bugs where
a downstream used a GitHub release tag instead of our tarball.

-- 
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] critical vs pinned repositories, was New pull request reviewers; Rahul and Yash

[Walter Bender]

One simple thing we might do is do something with the naming scheme of the
activities themselves.

turtle-art-fructose

bounce-honey

so a search for fructose would bring up all of the fructose activities.

We could also do this with "topics", but it would be a github-specific
solution.


As far as something a bit more comprehensive, and definitely github
specific, is something along the lines of
https://publiclab.github.io/community-toolbox/. The good news is that there
is a FOSS project with an active developer community behind this. But we'd
need to put resources into it.

-walter


On Tue, Feb 27, 2018 at 9:00 PM, D. Joe  wrote:

> On Fri, Feb 23, 2018 at 08:55:12AM +1100, James Cameron wrote:
>
> > Information below may be of help to guide you in this task.   [...]
>
> I find helpful this enumeration of critical repositories. This gives me a
> personal TODO list to make sure I'm following more of them than I do now.
>
> In checking against the sugarlabs organization page at
>
>   * https://github.com/sugarlabs
>
> I see something of a mismatch. I'm not sure to what extent it would be
> further helpful to refine what is pinned or not.  The set of pinned repos
> currently is
>
> sugar-docs
> browse-activity
> turtleart-activity
> sugar
> sugar-toolkit-gtk3
> sugar-artwork
>
> but ...
>
> > Critical repositories are;
> >
> > - sugar, sugar-toolkit, sugar-toolkit-gtk3, sugar-artwork,
> >   sugar-datastore, gst-plugins-espeak,
>
> So, from amongst this set those that aren't pinned are
>
> sugar-datastore
> sugar-toolkit
> gst-plugins-espeak
>
> > - each of the Fructose activity set repositories,
> >   https://wiki.sugarlabs.org/go/Development_Team/Release/
> Modules#Fructose
>
> From this much more extensive set, only two are pinned
>
> browse-activity
> turtleart-activity
>
> Overall, a GitHub profile is limited to six pinned repositories. In that
> light, the current set of pinned repositories is not bad as a
> representative
> draw from a set that is too large to pin in full, but it doesn't quite go
> far enough to support navigating to the full set of repositories enumerated
> by James.
>
> One possible improvement I'm wondering about is the creation of one or more
> meta repositories which then could be pinned, which in turn could hold
> READMEs pointing to the additional repositories, perhaps additionally with
> some documentation about important commonalities and differences amongst
> that subset of repositories.  This would be in addition to, and
> complementary to, and more directly discoverable than having these in
> sugar-docs.
>
> For instance, I do not find a 'fructose' repository, but there are so many
> and I think I'd need to gear up on the GitHub API to convince myself I have
> checked thoroughly.
>
> Perhaps sugarlabs/fructose or sugarlabs/fructose-meta or
> sugarlabs/fructose-collection could be created, and then pinned in place of
> both turtleart-activity or browse-activity.
>
> Naming is hard. I see "Glucose" and "Fructose" survive in the link James
> gives above, but only those two from all 6 carbohyrate-based names in
>
>   https://wiki.sugarlabs.org/go/Taxonomy
>
> seem to have been adopted. The full set of 6 terms feels overwrought and
> not
> super helpful to me.
>
> That said, it's at least *a* proposed solution to the problem brought up in
> the original version of that page:
>
>   https://wiki.sugarlabs.org/index.php?title=Taxonomy=419
>
> To be honest, using carbohydrate names seems like it is a better fit for
> hostnames or release names (cf mention of "Dextrose" in the current
> Taxonomy
> page).
>
> As I write this and think about it, I think I'd just as soon see meta repos
> 'sugar-core' and 'sugar-base-activities' in which the README for each would
> mention that they have also been known as 'Glucose' and 'Fructose'
> respectively.
>
> So, questions:
>
>   * Is the current way of documenting what packages are a priority
> sufficient or does some change make sense?
>   * Do we continue to try to make all the names there work, or just the
> few that have stuck?
>   * Do either or both of 'sugar-core' and 'sugar-base-activities' make
> sense as meta-repos as described above?
>   * Other comments, questions, concerns, objections, advice?
>
> If it doesn't seem at first glance to be a total waste of time I can work
> on draft versions of these meta repos in my own GitHub space for further
> review.
>
> > Comments?  Should the above be added to sugar-docs?
>
> ___
> 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] critical vs pinned repositories, was New pull request reviewers; Rahul and Yash

[D. Joe]

On Fri, Feb 23, 2018 at 08:55:12AM +1100, James Cameron wrote:

> Information below may be of help to guide you in this task.   [...]

I find helpful this enumeration of critical repositories. This gives me a
personal TODO list to make sure I'm following more of them than I do now.

In checking against the sugarlabs organization page at 

  * https://github.com/sugarlabs

I see something of a mismatch. I'm not sure to what extent it would be
further helpful to refine what is pinned or not.  The set of pinned repos
currently is

sugar-docs
browse-activity
turtleart-activity
sugar
sugar-toolkit-gtk3
sugar-artwork 

but ... 

> Critical repositories are;
> 
> - sugar, sugar-toolkit, sugar-toolkit-gtk3, sugar-artwork,
>   sugar-datastore, gst-plugins-espeak,
 
So, from amongst this set those that aren't pinned are 

sugar-datastore
sugar-toolkit
gst-plugins-espeak

> - each of the Fructose activity set repositories,
>   https://wiki.sugarlabs.org/go/Development_Team/Release/Modules#Fructose

From this much more extensive set, only two are pinned

browse-activity 
turtleart-activity

Overall, a GitHub profile is limited to six pinned repositories. In that
light, the current set of pinned repositories is not bad as a representative
draw from a set that is too large to pin in full, but it doesn't quite go
far enough to support navigating to the full set of repositories enumerated
by James.

One possible improvement I'm wondering about is the creation of one or more
meta repositories which then could be pinned, which in turn could hold
READMEs pointing to the additional repositories, perhaps additionally with
some documentation about important commonalities and differences amongst
that subset of repositories.  This would be in addition to, and
complementary to, and more directly discoverable than having these in
sugar-docs.

For instance, I do not find a 'fructose' repository, but there are so many and 
I think I'd need to gear up on the GitHub API to convince myself I have checked 
thoroughly.

Perhaps sugarlabs/fructose or sugarlabs/fructose-meta or
sugarlabs/fructose-collection could be created, and then pinned in place of
both turtleart-activity or browse-activity.

Naming is hard. I see "Glucose" and "Fructose" survive in the link James
gives above, but only those two from all 6 carbohyrate-based names in 

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

seem to have been adopted. The full set of 6 terms feels overwrought and not
super helpful to me.  

That said, it's at least *a* proposed solution to the problem brought up in
the original version of that page:

  https://wiki.sugarlabs.org/index.php?title=Taxonomy=419

To be honest, using carbohydrate names seems like it is a better fit for
hostnames or release names (cf mention of "Dextrose" in the current Taxonomy
page).

As I write this and think about it, I think I'd just as soon see meta repos
'sugar-core' and 'sugar-base-activities' in which the README for each would
mention that they have also been known as 'Glucose' and 'Fructose'
respectively.

So, questions:

  * Is the current way of documenting what packages are a priority sufficient 
or does some change make sense?
  * Do we continue to try to make all the names there work, or just the few 
that have stuck?
  * Do either or both of 'sugar-core' and 'sugar-base-activities' make sense as 
meta-repos as described above?
  * Other comments, questions, concerns, objections, advice?

If it doesn't seem at first glance to be a total waste of time I can work on 
draft versions of these meta repos in my own GitHub space for further review.

> Comments?  Should the above be added to sugar-docs?

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

Re: [Sugar-devel] Development Team Meeting, 27th February 10PM UTC

[James Cameron]

On Tue, Feb 27, 2018 at 09:42:14AM +1100, James Cameron wrote:
> Developers are invited to attend the next team meeting, on Tuesday
> 27th February, at 5PM US/Eastern (10PM UTC).

Attending were Walter, Devin (pikurasa), James (Quozl), Carlos
(unimaro), Ifeanyi, octamois, and dzho.

> Agenda to include
> 
> - what we have been working on,

Chasing bugs in Music Blocks, Speak, Memorize.  Porting activities to
GTK+ 3 and Sugargame 1.2.  Planning pinned repository changes.
and Six port.  Music Blocks class seminar at New England Conservatory.

> - port to Python 3 and Six, see GitHub issues below,
> 
> https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/382 (Port to Six)
> https://github.com/sugarlabs/sugar/issues/787 (Port to Python 3)
> https://github.com/sugarlabs/hello-world-fork/issues/2 (Port to Python 3)
> https://github.com/sugarlabs/sugar-datastore/issues/7 (Port to Python 3)
> https://github.com/sugarlabs/sugar-artwork/issues/102 (Port to Python 3)

Issues are cross-linked to indicate dependencies; the order in which
work needs to be done so that later work can build on earlier work.

Issues are for tracking, not for ownership.

Other GSoC project ideas might use tracking issues too.

Some porting work has begun; octamois on sugar-artwork.

Process isolation between Sugar shell and activities, with the D-Bus
API for communication, should make it easy to run both Python 2 and
Python 3 on the same system.  But only while the distribution of Linux
has Python 2 environment packages.

Critical is the GTK+ 3 toolkit.  It is to build and install both
Python 2 and Python 3.  Debian may package Python 2 and Python 3 for
as long as there is a Python 2 activity they package.  Fedora may only
package Python 3, we guess; nobody present with clear prediction.

Datastore is a special case; it has minimal toolkit needs and is well
isolated.

Implications for Python 2 GTK+ 2 activities;

- they may continue to work with the Python 2 GTK+ 2 toolkit,

- they may continue to work when started by a Python 3 Sugar shell,

- there is no Python 3 GTK+ 2 binding,

- way forward is to Python 2 GTK+ 3 then Python 3,

A test was added for these activities.

> #sugar-meeting irc.freenode.net
> 
> Visitors also welcome.

Two items of general business;

- Ifeany is concerned at lack of change to user interface and user
  experience of Sugar desktop since 2014, and wondered if it was
  caused by missing in action design team.  James confirmed design
  team has had few demands on their time.  Walter pointed out the full
  colour icon design issue is current and suggested engagement via
  SLOB.

- unimaro proposed the parental or teacher control feature as a
  project, and was asked to write it up in more detail and post to
  sugar-devel@.  Proposals like this for non-user control over Sugar
  features have come up in the past but have not gained traction.

-- 
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] Difficulty in setup of sugar environment

[James Cameron]

Sorry, your question makes no sense to me.

Your reply was to your thread where you were using Sugar 0.106; if you
are still using this version please upgrade first.

SUGAR_BUNDLE_PATH is automatically defined in Sugar 0.112.

However, running sugar-activity without arguments while in your
default home directory ... which is what you have demonstrated ... is
unsupported.  You're doing it wrong.

On Tue, Feb 27, 2018 at 10:30:25PM +0530, DIPANSH KHANDELWAL wrote:
> Hi,
> I wanted to know how can we - define SUGAR_BUNDLE_PATH in the environment ?
> 
> This is what I am getting -
> ```
> dipansh@dipansh-pc ~ $ sugar-activity
> SUGAR_BUNDLE_PATH is not defined in the environment.
> ```
> 
> Thanks
> Dipansh
> 
> On Tue, Feb 27, 2018 at 10:46 AM, James Cameron <[1]qu...@laptop.org> wrote:
> 
> Version 0.106 is very old.  Sugar is now at 0.112.  You can see latest
> Sugar packages in Ubuntu and Debian;
> 
> [2]https://packages.ubuntu.com/sucrose
> [3]https://packages.debian.org/sucrose
> 
> You can see both are at 0.112 now.
> 
> Debian bug #877812 affects 0.110, as the bug says.  Please refer to
> that bug for more information.  Since you have 0.106, the bug is
> probably not relevant.
> 
> Please continue to work with Linux Mint community on the problem, or
> upgrade to later release.
>
> Logs you will need are in ~profile/.sugar/default/logs/shell.log and
> will likely be a missing dependency.
> 
> On Tue, Feb 27, 2018 at 04:54:39AM +, DIPANSH KHANDELWAL wrote:
> > Sucrose version is 0.106.1-1
> > And about Debian bug #877812 is it still unsolved ?
> > And what issue shall I raise in the mint community? Problem in sucrose
> setup ?
> >
> > Thanks
> >
> > On Tue, 27 Feb 2018, 10:04 James Cameron, <[1][4]qu...@laptop.org> 
> wrote:
> >
> >     Please continue to copy sugar-devel@
> >
> >     Please stick to one problem at a time.
> >
> >     What version of sucrose package?
> >
> >     If version is not 0.112, please raise bug with Linux Mint.  Problem
> is
> >     that Sugar desktop does not show up.  Logs you will need are in
> >     ~profile/.sugar/default/logs/shell.log and will likely be a missing
> >     dependency.  See also Debian bug #877812.
> >
> >     While you wait for Linux Mint community to respond, post more detail
> >     in new thread about sugar-live-build.
> >
> >     Do not post about sugar-build; it is broken and unsupported.
> >
> >     Thanks!
> >
> >     On Tue, Feb 27, 2018 at 09:54:02AM +0530, DIPANSH KHANDELWAL wrote:
> >     > My system information - 
> [1][2][5]https://gist.github.com/anonymous/
> >     > a8bf08f81a08cd316cf74af221f3c42a
> >     >
> >     > I have first tried a sugar-live-build , sugar-build. But was not
> able to
> >     set it
> >     > up.
> >     > I also installed sucrose (I don't know if it was installed 
> properly
> or
> >     not).
> >     > It made one more profile in my pc.
> >     > So when I logged out out of my pc and tried to log in the sugar
> desktop,
> >     I
> >     > shows a blank screen with the typical sugar cursor pointer.
> >     > Then i have to hard shut down my pc to restart it.
> >     >
> >     > On Tue, Feb 27, 2018 at 9:23 AM, James Cameron <[2][3][6]
> qu...@laptop.org>
> >     wrote:
> >     >
> >     >     Java is not required.
> >     >
> >     >     Please describe your PC environment;
> >     >
> >     >     - operating system name, and release version,
> >     >
> >     >     Please describe what method you used to install.  Method
> depends on
> >     >     operating system and vendor.
> >     >
> >     >     On Tue, Feb 27, 2018 at 09:21:10AM +0530, DIPANSH KHANDELWAL
> wrote:
> >     >     > Hi,
> >     >     > I am facing difficulty in setting up the sugar environment 
> in
> my
> >     pc.
> >     >     > I tried to install sucrose but it is half completed because
> java-6
> >     is not
> >     >     > present.
> >     >     > But now oracle java-6 is not available.
> >     >     > What can I do now?
> >     >     >
> >     >     > Thanks
> >     >     > Dipansh
> >     >
> >     >     > ___
> >     >     > Sugar-devel mailing list
> >     >     > [3][4][7]Sugar-devel@lists.sugarlabs.org
> >     >     > [4][5][8]http://lists.sugarlabs.org/listinfo/sugar-devel
> >     >
> >     >
> >     >     --
> >     >     James Cameron
> >     >     [5][6][9]http://quozl.netrek.org/
> >     >
> >     > References:
> >     >
> >     > [1] [7][10]https://gist.github.com/anonymous/
> a8bf08f81a08cd316cf74af221f3c42a
> >     > [2] mailto:[8][11]qu...@laptop.org
> >     > 

Re: [Sugar-devel] Involving InGSoC 2018

[Carlos mauro]

Nice friend.

Welcome to SugarLabs.org please read the ideas in the wiki

https://wiki.sugarlabs.org/go/Summer_of_Code/2018

Try to install sugar from the git

https://github.com/sugarlabs/sugar-docs

And try to fix a litle bug :).


Best regards


El 27 feb. 2018 1:06 p. m., "Danishka Navin"  escribió:

> Hi there,
>
> I am planning to participate this year GSoC program.
> Since I have been working with Sugar/OLPC in terms of l10n, deployments in
> Sri Lanka using our own Fedora remix "Hanthana Linux' bundled both Gnome
> and Sugar desktop.
> Moreover I used to package Sugar activities for Fedora as well. [1]
>
> I would like to work on Sugar project for GSoC as well.
>
> I am interested in working on the task of "Sugarizer School Box".
> I choose this task as I am really interested in RPi based deployments as
> well as I am from DevOps background with AWS experience.
>
>
> [1] https://fedoraproject.org/wiki/User:Snavin
>
> Regards,
> --
> Danishka Navin
> http://danishkanavin.blogspot.com
> http://twitter.com/danishkanavin
>
>
>
>
>
> ___
> 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] Involving InGSoC 2018

[Danishka Navin]

Hi there,

I am planning to participate this year GSoC program.
Since I have been working with Sugar/OLPC in terms of l10n, deployments in
Sri Lanka using our own Fedora remix "Hanthana Linux' bundled both Gnome
and Sugar desktop.
Moreover I used to package Sugar activities for Fedora as well. [1]

I would like to work on Sugar project for GSoC as well.

I am interested in working on the task of "Sugarizer School Box".
I choose this task as I am really interested in RPi based deployments as
well as I am from DevOps background with AWS experience.


[1] https://fedoraproject.org/wiki/User:Snavin

Regards,
-- 
Danishka Navin
http://danishkanavin.blogspot.com
http://twitter.com/danishkanavin
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Difficulty in setup of sugar environment

[DIPANSH KHANDELWAL]

Hi,
I wanted to know how can we - define SUGAR_BUNDLE_PATH in the environment ?

This is what I am getting -
```
dipansh@dipansh-pc ~ $ sugar-activity
SUGAR_BUNDLE_PATH is not defined in the environment.
```

Thanks
Dipansh

On Tue, Feb 27, 2018 at 10:46 AM, James Cameron  wrote:

> Version 0.106 is very old.  Sugar is now at 0.112.  You can see latest
> Sugar packages in Ubuntu and Debian;
>
> https://packages.ubuntu.com/sucrose
> https://packages.debian.org/sucrose
>
> You can see both are at 0.112 now.
>
> Debian bug #877812 affects 0.110, as the bug says.  Please refer to
> that bug for more information.  Since you have 0.106, the bug is
> probably not relevant.
>
> Please continue to work with Linux Mint community on the problem, or
> upgrade to later release.
>
> Logs you will need are in ~profile/.sugar/default/logs/shell.log and
> will likely be a missing dependency.
>
> On Tue, Feb 27, 2018 at 04:54:39AM +, DIPANSH KHANDELWAL wrote:
> > Sucrose version is 0.106.1-1
> > And about Debian bug #877812 is it still unsolved ?
> > And what issue shall I raise in the mint community? Problem in sucrose
> setup ?
> >
> > Thanks
> >
> > On Tue, 27 Feb 2018, 10:04 James Cameron, <[1]qu...@laptop.org> wrote:
> >
> > Please continue to copy sugar-devel@
> >
> > Please stick to one problem at a time.
> >
> > What version of sucrose package?
> >
> > If version is not 0.112, please raise bug with Linux Mint.  Problem
> is
> > that Sugar desktop does not show up.  Logs you will need are in
> > ~profile/.sugar/default/logs/shell.log and will likely be a missing
> > dependency.  See also Debian bug #877812.
> >
> > While you wait for Linux Mint community to respond, post more detail
> > in new thread about sugar-live-build.
> >
> > Do not post about sugar-build; it is broken and unsupported.
> >
> > Thanks!
> >
> > On Tue, Feb 27, 2018 at 09:54:02AM +0530, DIPANSH KHANDELWAL wrote:
> > > My system information - [1][2]https://gist.github.com/anonymous/
> > > a8bf08f81a08cd316cf74af221f3c42a
> > >
> > > I have first tried a sugar-live-build , sugar-build. But was not
> able to
> > set it
> > > up.
> > > I also installed sucrose (I don't know if it was installed
> properly or
> > not).
> > > It made one more profile in my pc.
> > > So when I logged out out of my pc and tried to log in the sugar
> desktop,
> > I
> > > shows a blank screen with the typical sugar cursor pointer.
> > > Then i have to hard shut down my pc to restart it.
> > >
> > > On Tue, Feb 27, 2018 at 9:23 AM, James Cameron <[2][3]
> qu...@laptop.org>
> > wrote:
> > >
> > > Java is not required.
> > >
> > > Please describe your PC environment;
> > >
> > > - operating system name, and release version,
> > >
> > > Please describe what method you used to install.  Method
> depends on
> > > operating system and vendor.
> > >
> > > On Tue, Feb 27, 2018 at 09:21:10AM +0530, DIPANSH KHANDELWAL
> wrote:
> > > > Hi,
> > > > I am facing difficulty in setting up the sugar environment
> in my
> > pc.
> > > > I tried to install sucrose but it is half completed because
> java-6
> > is not
> > > > present.
> > > > But now oracle java-6 is not available.
> > > > What can I do now?
> > > >
> > > > Thanks
> > > > Dipansh
> > >
> > > > ___
> > > > Sugar-devel mailing list
> > > > [3][4]Sugar-devel@lists.sugarlabs.org
> > > > [4][5]http://lists.sugarlabs.org/listinfo/sugar-devel
> > >
> > >
> > > --
> > > James Cameron
> > > [5][6]http://quozl.netrek.org/
> > >
> > > References:
> > >
> > > [1] [7]https://gist.github.com/anonymous/
> a8bf08f81a08cd316cf74af221f3c42a
> > > [2] mailto:[8]qu...@laptop.org
> > > [3] mailto:[9]Sugar-devel@lists.sugarlabs.org
> > > [4] [10]http://lists.sugarlabs.org/listinfo/sugar-devel
> > > [5] [11]http://quozl.netrek.org/
> >
> > --
> > James Cameron
> > [12]http://quozl.netrek.org/
> >
> > References:
> >
> > [1] mailto:qu...@laptop.org
> > [2] https://gist.github.com/anonymous/
> > [3] mailto:qu...@laptop.org
> > [4] mailto:Sugar-devel@lists.sugarlabs.org
> > [5] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [6] http://quozl.netrek.org/
> > [7] https://gist.github.com/anonymous/a8bf08f81a08cd316cf74af221f3c42a
> > [8] mailto:qu...@laptop.org
> > [9] mailto:Sugar-devel@lists.sugarlabs.org
> > [10] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [11] http://quozl.netrek.org/
> > [12] http://quozl.netrek.org/
>
> --
> James Cameron
> http://quozl.netrek.org/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org

Re: [Sugar-devel] Development Team Meeting, 27th February 10PM UTC

[Carlos mauro]

I'll be there.

El 27 feb. 2018 3:26 a. m., "Ifeanyi Peter" 
escribió:

> OK Thanks
>
> Sent from Yahoo Mail on Android
>
> On Tue, Feb 27, 2018 at 9:19, James Cameron
>  wrote:
> No, sorry.
>
> I don't log in to Google and I block tracking cookies.  Siri on macOS
> Mail does recognise the text as a calendar entry; perhaps you need a
> mail client with deeper features.
>
> If anyone else wants to "add a Google calendar", and maintain it,
> please do so.
>
> On Tue, Feb 27, 2018 at 08:09:25AM +, Ifeanyi Peter wrote:
> > Nice.
> >
> > I'll love to be in the meeting. Please can you add a Google calendar
> next time?
> >
> > Thanks
> >
> > [1]Sent from Yahoo Mail on Android
> >
> >On Mon, Feb 26, 2018 at 23:42, James Cameron
> > wrote:
> >Developers are invited to attend the next team meeting, on Tuesday
> >27th February, at 5PM US/Eastern (10PM UTC).
> >
> >Agenda to include
> >
> >- what we have been working on,
> >
> >- port to Python 3 and Six, see GitHub issues below,
> >
> >#sugar-meeting irc.freenode.net
> >
> >Visitors also welcome.
> >
> >--
> >
> >References:
> >
> >[2]https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/382 (Port
> to Six)
> >[3]https://github.com/sugarlabs/sugar/issues/787 (Port to Python 3)
> >[4]https://github.com/sugarlabs/hello-world-fork/issues/2 (Port to
> Python
> >3)
> >[5]https://github.com/sugarlabs/sugar-datastore/issues/7 (Port to
> Python 3)
> >[6]https://github.com/sugarlabs/sugar-artwork/issues/102 (Port to
> Python 3)
> >
> >--
> >James Cameron
> >[7]http://quozl.netrek.org/
> >___
> >Sugar-devel mailing list
> >[8]Sugar-devel@lists.sugarlabs.org
> >[9]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1] https://overview.mail.yahoo.com/mobile/?.src=Android
> > [2] https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/382
> > [3] https://github.com/sugarlabs/sugar/issues/787
> > [4] https://github.com/sugarlabs/hello-world-fork/issues/2
> > [5] https://github.com/sugarlabs/sugar-datastore/issues/7
> > [6] https://github.com/sugarlabs/sugar-artwork/issues/102
> > [7] http://quozl.netrek.org/
> > [8] mailto:Sugar-devel@lists.sugarlabs.org
> > [9] http://lists.sugarlabs.org/listinfo/sugar-devel
>
> > Developers are invited to attend the next team meeting, on Tuesday
> > 27th February, at 5PM US/Eastern (10PM UTC).
> >
> > Agenda to include
> >
> > - what we have been working on,
> >
> > - port to Python 3 and Six, see GitHub issues below,
> >
> > #sugar-meeting irc.freenode.net
> >
> > Visitors also welcome.
> >
> > --
> >
> > References:
> >
> > https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/382 (Port to Six)
> > https://github.com/sugarlabs/sugar/issues/787 (Port to Python 3)
> > https://github.com/sugarlabs/hello-world-fork/issues/2 (Port to Python
> 3)
> > https://github.com/sugarlabs/sugar-datastore/issues/7 (Port to Python 3)
> > https://github.com/sugarlabs/sugar-artwork/issues/102 (Port to Python 3)
> >
> > --
> > James Cameron
> > http://quozl.netrek.org/
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Development Team Meeting, 27th February 10PM UTC

[James Cameron]

No, sorry.

I don't log in to Google and I block tracking cookies.  Siri on macOS
Mail does recognise the text as a calendar entry; perhaps you need a
mail client with deeper features.

If anyone else wants to "add a Google calendar", and maintain it,
please do so.

On Tue, Feb 27, 2018 at 08:09:25AM +, Ifeanyi Peter wrote:
> Nice.
> 
> I'll love to be in the meeting. Please can you add a Google calendar next 
> time?
> 
> Thanks
> 
> [1]Sent from Yahoo Mail on Android
> 
> On Mon, Feb 26, 2018 at 23:42, James Cameron
>  wrote:
> Developers are invited to attend the next team meeting, on Tuesday
> 27th February, at 5PM US/Eastern (10PM UTC).
> 
> Agenda to include
> 
> - what we have been working on,
> 
> - port to Python 3 and Six, see GitHub issues below,
> 
> #sugar-meeting irc.freenode.net
> 
> Visitors also welcome.
> 
> --
> 
> References:
> 
> [2]https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/382 (Port to 
> Six)
> [3]https://github.com/sugarlabs/sugar/issues/787 (Port to Python 3)
> [4]https://github.com/sugarlabs/hello-world-fork/issues/2 (Port to Python
> 3)
> [5]https://github.com/sugarlabs/sugar-datastore/issues/7 (Port to Python 
> 3)
> [6]https://github.com/sugarlabs/sugar-artwork/issues/102 (Port to Python 
> 3)
> 
> --
> James Cameron
> [7]http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> [8]Sugar-devel@lists.sugarlabs.org
> [9]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] https://overview.mail.yahoo.com/mobile/?.src=Android
> [2] https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/382
> [3] https://github.com/sugarlabs/sugar/issues/787
> [4] https://github.com/sugarlabs/hello-world-fork/issues/2
> [5] https://github.com/sugarlabs/sugar-datastore/issues/7
> [6] https://github.com/sugarlabs/sugar-artwork/issues/102
> [7] http://quozl.netrek.org/
> [8] mailto:Sugar-devel@lists.sugarlabs.org
> [9] http://lists.sugarlabs.org/listinfo/sugar-devel

> Developers are invited to attend the next team meeting, on Tuesday
> 27th February, at 5PM US/Eastern (10PM UTC).
> 
> Agenda to include
> 
> - what we have been working on,
> 
> - port to Python 3 and Six, see GitHub issues below,
> 
> #sugar-meeting irc.freenode.net
> 
> Visitors also welcome.
> 
> --
> 
> References:
> 
> https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/382 (Port to Six)
> https://github.com/sugarlabs/sugar/issues/787 (Port to Python 3)
> https://github.com/sugarlabs/hello-world-fork/issues/2 (Port to Python 3)
> https://github.com/sugarlabs/sugar-datastore/issues/7 (Port to Python 3)
> https://github.com/sugarlabs/sugar-artwork/issues/102 (Port to Python 3)
> 
> -- 
> James Cameron
> http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel


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