Re: [Sugar-devel] Sync between GitHub and ASLO

[Jatin Dhankhar]

I agree with James, a lot of work is pending and lot needs to be done.

However aslo-v3 does support syncing activity when a release is  *explicitly
*published by the developer.
Is this something similar to what you are looking for?
Here is a demo of the same https://www.youtube.com/watch?v=XNount59G0Y.

We can try to pull info on each release but there is no event for Tags yet.
There are tags for push events and pull requests as well.
 https://developer.github.com/v3/activity/events/types/.

Let me know if you have any questions or concerns.


Thanks,
Jatin Dhankhar



On Fri, Jan 18, 2019 at 12:21 PM James Cameron  wrote:

> I disagree.  None of the automation proposed, or attempted in the
> past, has solved our _human_ problem of not testing and tagging an
> activity release.
>
> It is a human problem which needs a non-technical solution;
> attentiveness and willingness to act.
>
> It also won't be solved by GSoC or GCI, because it never has been the
> last few times we've tried that.  ;-)
>
> It hasn't been solved by improving documentation.
>
> It hasn't been solved by ASLOv3, as it is still under development, and
> the developers have told me they do not plan to replicate the
> functionality we have in ASLOv1, such as the Sugar version detection
> feature, so we're stuck with ASLOv1 for a good while longer.  It seems
> to keep working and is relatively easy to maintain.
>
> Also, those of us with a need for more than what ASLOv1 provides have
> deployed point solutions; Tony has his, and I have mine.  Mine are;
>
> - separate software update reference list maintained at laptop.org to
>   cover for when activities.sugarlabs.org is down,
>
> - redundant copy of bundles maintained at download.laptop.org to cover
>   for when download.sugarlabs.org is down,
>
> - tools for rapidly releasing bundles to ASLOv1, such as by using
>   'import requests'.
>
> Hope that helps.
>
> On Fri, Jan 18, 2019 at 08:15:22AM +0530, Rahul Bothra wrote:
> > *
> > A common issue across many activities is that changes are often not
> released to
> > ASLO. This must be automated to ensure that the work of developers is
> reaching
> > the users
> >
> > My suggestion is to have an automatic sync with GitHub and ASLO;
> > When a new release tag is set on GitHub,
> >  - the activity should be updated on ASLO with the latest changes.
> >  - Issues opened in the repository can go the into known bugs section
> >  - ReadMe can go into about the Activity section
> >  - git history or release tag description can go into the new changes
> section
> >
> > New changes to the repository will have to be tested before setting a new
> > release tag on GitHub
> >
> > I saw the ASLO bot is able to capture new tags from GitHub, but I'm not
> sure
> > how to fix it
>
> > ___
> > 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] Abandoned or orphaned activities

[James Cameron]

Once we had a list of abandoned activities, where the maintainer is
missing in action, not doing testing or releasing.

Now, I propose the inverse; a list of activities with a maintainer
testing and releasing.  It will be easier to maintain that list.

For myself, each of the Fructose activities, each of the activities we
ship on OLPC OS.  I know Walter is looking after Music Blocks.  Lionel
is looking after Sugarizer.  Are there any other developers who are
maintainers?

-- 
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] RPi Project for GSoC 2019

[James Cameron]

Thanks, but what's wrong with Fedora SoaS on RPi?  It seems to work
fine.  For GSoC 2017, we wanted an image because we didn't have one,
but the situation changed.  I don't think we should make something we
already have.

Adding a Raspberry Pi plugin to Turtle Blocks isn't a large enough
task to be a GSoC project.  Remember the size; three months work.

A simple Raspberry Pi GPIO exerciser activity could be a week's work.

If you think it is a good idea, get started now!

On Thu, Jan 17, 2019 at 09:12:16PM +0530, Aman Sharma wrote:
> Hello
> 
> As a part of GSoC 2019 we are looking forward to increase the scope of our
> previous Sugar on RPi image which was initially developed during GSoC 2017. It
> is suggested by Mr.Walter Bender that we should include the following goals 
> for
> the project:
> 
> 1) Turtle Blocks access to RPi sensors / devices.
> 2) Long term support plan.
> 3) Methodical Testing Plan
> 
> Before adding this project to the idea list I am looking forward to have some
> more suggestions from the community regarding the activities that can leverage
> sensors or other devices that could be paired with the RPi to enhance user
> experience.
> Kindly provide your suggestions regarding the same.
> 
> Thank you
> Aman Sharma
> 

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

Re: [Sugar-devel] Sync between GitHub and ASLO

[James Cameron]

I disagree.  None of the automation proposed, or attempted in the
past, has solved our _human_ problem of not testing and tagging an
activity release.

It is a human problem which needs a non-technical solution;
attentiveness and willingness to act.

It also won't be solved by GSoC or GCI, because it never has been the
last few times we've tried that.  ;-)

It hasn't been solved by improving documentation.

It hasn't been solved by ASLOv3, as it is still under development, and
the developers have told me they do not plan to replicate the
functionality we have in ASLOv1, such as the Sugar version detection
feature, so we're stuck with ASLOv1 for a good while longer.  It seems
to keep working and is relatively easy to maintain.

Also, those of us with a need for more than what ASLOv1 provides have
deployed point solutions; Tony has his, and I have mine.  Mine are;

- separate software update reference list maintained at laptop.org to
  cover for when activities.sugarlabs.org is down,

- redundant copy of bundles maintained at download.laptop.org to cover
  for when download.sugarlabs.org is down,

- tools for rapidly releasing bundles to ASLOv1, such as by using
  'import requests'.

Hope that helps.

On Fri, Jan 18, 2019 at 08:15:22AM +0530, Rahul Bothra wrote:
> *
> A common issue across many activities is that changes are often not released 
> to
> ASLO. This must be automated to ensure that the work of developers is reaching
> the users
> 
> My suggestion is to have an automatic sync with GitHub and ASLO;
> When a new release tag is set on GitHub,
>  - the activity should be updated on ASLO with the latest changes.
>  - Issues opened in the repository can go the into known bugs section
>  - ReadMe can go into about the Activity section
>  - git history or release tag description can go into the new changes section
> 
> New changes to the repository will have to be tested before setting a new
> release tag on GitHub
> 
> I saw the ASLO bot is able to capture new tags from GitHub, but I'm not sure
> how to fix it

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

Re: [Sugar-devel] GSOC 2019 Student

[James Cameron]

Welcome,

As chair of the board; Sugar Labs has decided to apply for Google
Summer fo Code 2019, and once our application has been submitted we
will wait in hope for Google to select us.

As for myself;

You can get started however you like.  Don't wait for us to explain,
and don't expect us to set specific tasks to get started with.  If
someone does that to you, check that others think the task should be
done.

https://github.com/sugarlabs/GSoC has some ideas for projects we are
working to define better.  You are welcome to review and offer comments.

On Thu, Jan 17, 2019 at 05:39:46PM +0530, Shiv Pratap Singh wrote:
> Hi all,
>     I am undergraduate student in computer science.I find myself good with
> skills required to contribute in the projects in your organization.
>     I will be applying as GSOC student for the organization by developing
> features.
>     How can I get started ? Just to confirm if this organization is going to
> participate in upcoming GSOC.Please let me know where can I find all details 
> to
> get started.
> Thank You!

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

Re: [Sugar-devel] [SoaS] Errors from Soas 29

[James Cameron]

I've not recently tested the Sugar collaboration stack with Fedora, my
testing has been on Ubuntu.

But you're right on with the process to use; once they are able to
communicate over a common TCP/ip network that relays mDNS UDP
broadcast packets, an icon for each instance should appear in
Neighbourhood View.  Without that icon, the collaboration features
won't work.

When that icon does not appear, my checklist is;

- look for interesting log messages, especially in shell.log,

- make sure there are no alternate network paths, such as ethernet
  adapters,

- ping between two instance IP addresses to verify the network is
  working,

- tcpdump to look for mDNS and clique packets on two instances, making
  sure what is sent by one instance is also received by the other,

- use the Chat, Maze, or CollabWrapper test activities, as these have
  the most robust code for Telepathy use.

On Thu, Jan 17, 2019 at 09:51:28AM +0100, Samson Goddy wrote:
> Hello, 
> 
> Ibiam and I are currently working to install Sugar in the classroom, so we
> decided to download Soas 32-bit versions. After installing, we ran into some
> problems immediately after the desktop booted which can be found here[1]. I
> also noticed whenever I click on the speaker icon, the bottom of the frame
> becomes darker. I tested collaboration using Jabber service, Ibiam couldn't
> find the desktop on the neighborhood but the desktop can alongside.   
> 
>   Quick question? what are the best ways to make sugar to talk to each other?
> Those desktop are using mini USB wifi adaptors(working on windows) but not
> Soas. I will be testing on more systems by Wednesday.   
> 
> Logs[2]
> 
> [1][1]https://wiki.sugarlabs.org/go/Sugar_on_a_Stick#Known_bugs
> [2][2]https://paste.fedoraproject.org/paste/4QIR-XATy2wmnZb2VbNn3A
> 
> --
> 
>   Samson Goddy
> 
>   Twitter: [3]https://twitter.com/samson_goddy
>   Email: [4]samsongo...@sugarlabs.org
>               [5]samsongo...@gmail.com
> 
>   Website: [6]https://samsongoddy.me/ 
> 
> References:
> 
> [1] https://wiki.sugarlabs.org/go/Sugar_on_a_Stick#Known_bugs
> [2] https://paste.fedoraproject.org/paste/4QIR-XATy2wmnZb2VbNn3A
> [3] https://twitter.com/samson_goddy
> [4] mailto:samsongo...@sugarlabs.org
> [5] mailto:samsongo...@gmail.com
> [6] https://www.sugarlabs.org/

> ___
> SoaS mailing list
> s...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas


-- 
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] GSoC project ideas

[utkarsh Dhawan]

Hi James,

No the activity is not complete yet. We had managed to create beginner
levels but it still has lot of scope for further development. I am more
than wiling to complete it though :D

Thanking You,
Utkarsh Dhawan
(Developer/Student)

Note:Please Consider The environment before printing.


On Fri, Jan 18, 2019 at 11:10 AM James Cameron  wrote:

> G'day Utkarsh,
>
> Thanks, very interesting.  Would you like the activity to be hosted at
> Sugar Labs?  At the moment you have it in your own profile.  I'm not
> surprised I'd forgotten all about it, and perhaps others had too.
>
> I note there are no releases tagged and no bundle available from
> activities.sugarlabs.org; do you plan anything like that?  Is it ready?
>
> On Wed, Jan 16, 2019 at 05:29:06PM +0530, utkarsh Dhawan wrote:
> > Hi James,
> >
> > Web Confusion was an activity part of GSOC 2015. You can find the
> reference
> > here [1] the project was developed by me and Vibhor under the mentorship
> of
> > Tony. The activity basically revolves around interactive tasks divided
> into
> > various levels. You can find an example in the attachment below.
> >
> > [1] [1]https://github.com/crusher95/webconfusion
> >
> > Thanking You,
> > Utkarsh Dhawan
> > (Developer/Student)
> >
> > Note:Please Consider The environment before printing.
> >
> > On Wed, Jan 16, 2019 at 1:20 PM James Cameron <[2]qu...@laptop.org>
> wrote:
> >
> > G'day Utkarsh,
> >
> > What can you tell us about this Web Confusion project?  I've searched
> > and I can't it.
> >
> > We have in Sugarizer the activities Etoys, Jappy, Scratch, and Turtle
> > Blocks.  We have in Sugar also the activities Pippy, Develop, and
> > PyDebug.  All are offline capable.
> >
> > We also have Music Blocks, as a web app.  There are also many other
> > web apps for teaching children how to code.  All are online capable.
> >
> > Or do you mean adding the Turtle Confusion shape challenges to the
> > Turtle Blocks JavaScript activity?  I think they are already there,
> > no?
> >
> > On Wed, Jan 16, 2019 at 11:50:01AM +0530, utkarsh Dhawan wrote:
> > > Hi,
> > >
> > > Is the Web Confusion project still in the pipeline? Since I think
> it was
> > an
> > > amazing project to teach young kids about programming languages at
> an
> > early
> > > stage. Also I think the scope for the same can be increased to
> other
> > languages
> > > like python.
> > >
> > > Thanking You,
> > > Utkarsh Dhawan
> > > (Developer/Student)
> > >
> > > Note:Please Consider The environment before printing.
> > >
> > > On Sat, Jan 12, 2019 at 6:40 AM Walter Bender <[1][3]
> > walter.ben...@gmail.com>
> > > wrote:
> > >
> > > We have some ideas contributed by Rahul and myself. But
> nothing from
> > anyone
> > > else. Please add your ideas here [1] this week as organization
> > applications
> > > are due soon.
> > >
> > > regards.
> > >
> > > -walter
> > >
> > > [1] [2][4]
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md
> > > --
> > > Walter Bender
> > > Sugar Labs
> > > [3][5]http://www.sugarlabs.org
> > > [4]
> > > ___
> > > Sugar-devel mailing list
> > > [5][6]Sugar-devel@lists.sugarlabs.org
> > > [6][7]http://lists.sugarlabs.org/listinfo/sugar-devel
> > >
> > > References:
> > >
> > > [1] mailto:[8]walter.ben...@gmail.com
> > > [2] [9]https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md
> > > [3] [10]http://www.sugarlabs.org/
> > > [4] [11]http://www.sugarlabs.org/
> > > [5] mailto:[12]Sugar-devel@lists.sugarlabs.org
> > > [6] [13]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > > ___
> > > Sugar-devel mailing list
> > > [14]Sugar-devel@lists.sugarlabs.org
> > > [15]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > --
> > James Cameron
> > [16]http://quozl.netrek.org/
> > ___
> > Sugar-devel mailing list
> > [17]Sugar-devel@lists.sugarlabs.org
> > [18]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1] https://github.com/crusher95/webconfusion
> > [2] mailto:qu...@laptop.org
> > [3] mailto:walter.ben...@gmail.com
> > [4] https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md
> > [5] http://www.sugarlabs.org/
> > [6] mailto:Sugar-devel@lists.sugarlabs.org
> > [7] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [8] mailto:walter.ben...@gmail.com
> > [9] https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md
> > [10] http://www.sugarlabs.org/
> > [11] http://www.sugarlabs.org/
> > [12] mailto:Sugar-devel@lists.sugarlabs.org
> > [13] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [14] 

Re: [Sugar-devel] GSoC project ideas

[James Cameron]

G'day Utkarsh,

Thanks, very interesting.  Would you like the activity to be hosted at
Sugar Labs?  At the moment you have it in your own profile.  I'm not
surprised I'd forgotten all about it, and perhaps others had too.

I note there are no releases tagged and no bundle available from
activities.sugarlabs.org; do you plan anything like that?  Is it ready?

On Wed, Jan 16, 2019 at 05:29:06PM +0530, utkarsh Dhawan wrote:
> Hi James,
> 
> Web Confusion was an activity part of GSOC 2015. You can find the reference
> here [1] the project was developed by me and Vibhor under the mentorship of
> Tony. The activity basically revolves around interactive tasks divided into
> various levels. You can find an example in the attachment below. 
> 
> [1] [1]https://github.com/crusher95/webconfusion
> 
> Thanking You,
> Utkarsh Dhawan
> (Developer/Student)
> 
> Note:Please Consider The environment before printing.
> 
> On Wed, Jan 16, 2019 at 1:20 PM James Cameron <[2]qu...@laptop.org> wrote:
> 
> G'day Utkarsh,
> 
> What can you tell us about this Web Confusion project?  I've searched
> and I can't it.
> 
> We have in Sugarizer the activities Etoys, Jappy, Scratch, and Turtle
> Blocks.  We have in Sugar also the activities Pippy, Develop, and
> PyDebug.  All are offline capable.
> 
> We also have Music Blocks, as a web app.  There are also many other
> web apps for teaching children how to code.  All are online capable.
> 
> Or do you mean adding the Turtle Confusion shape challenges to the
> Turtle Blocks JavaScript activity?  I think they are already there,
> no?
> 
> On Wed, Jan 16, 2019 at 11:50:01AM +0530, utkarsh Dhawan wrote:
> > Hi,
> >
> > Is the Web Confusion project still in the pipeline? Since I think it was
> an
> > amazing project to teach young kids about programming languages at an
> early
> > stage. Also I think the scope for the same can be increased to other
> languages
> > like python.
> >
> > Thanking You,
> > Utkarsh Dhawan
> > (Developer/Student)
> >
> > Note:Please Consider The environment before printing.
> >
> > On Sat, Jan 12, 2019 at 6:40 AM Walter Bender <[1][3]
> walter.ben...@gmail.com>
> > wrote:
> >
> >     We have some ideas contributed by Rahul and myself. But nothing from
> anyone
> >     else. Please add your ideas here [1] this week as organization
> applications
> >     are due soon.
> >
> >     regards.
> >
> >     -walter
> >
> >     [1] 
> [2][4]https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md
> >     --
> >     Walter Bender
> >     Sugar Labs
> >     [3][5]http://www.sugarlabs.org
> >     [4]
> >     ___
> >     Sugar-devel mailing list
> >     [5][6]Sugar-devel@lists.sugarlabs.org
> >     [6][7]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1] mailto:[8]walter.ben...@gmail.com
> > [2] [9]https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md
> > [3] [10]http://www.sugarlabs.org/
> > [4] [11]http://www.sugarlabs.org/
> > [5] mailto:[12]Sugar-devel@lists.sugarlabs.org
> > [6] [13]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> > ___
> > Sugar-devel mailing list
> > [14]Sugar-devel@lists.sugarlabs.org
> > [15]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [16]http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> [17]Sugar-devel@lists.sugarlabs.org
> [18]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] https://github.com/crusher95/webconfusion
> [2] mailto:qu...@laptop.org
> [3] mailto:walter.ben...@gmail.com
> [4] https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md
> [5] http://www.sugarlabs.org/
> [6] mailto:Sugar-devel@lists.sugarlabs.org
> [7] http://lists.sugarlabs.org/listinfo/sugar-devel
> [8] mailto:walter.ben...@gmail.com
> [9] https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md
> [10] http://www.sugarlabs.org/
> [11] http://www.sugarlabs.org/
> [12] mailto:Sugar-devel@lists.sugarlabs.org
> [13] http://lists.sugarlabs.org/listinfo/sugar-devel
> [14] mailto:Sugar-devel@lists.sugarlabs.org
> [15] http://lists.sugarlabs.org/listinfo/sugar-devel
> [16] http://quozl.netrek.org/
> [17] mailto:Sugar-devel@lists.sugarlabs.org
> [18] 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] Sync between GitHub and ASLO

[Rahul Bothra]

A common issue across many activities is that changes are often not
released to ASLO. This must be automated to ensure that the work of
developers is reaching the users

My suggestion is to have an automatic sync with GitHub and ASLO;
When a new release tag is set on GitHub,
 - the activity should be updated on ASLO with the latest changes.
 - Issues opened in the repository can go the into known bugs section
 - ReadMe can go into about the Activity section
 - git history or release tag description can go into the new changes
section

New changes to the repository will have to be tested before setting a new
release tag on GitHub

I saw the ASLO bot is able to capture new tags from GitHub, but I'm not
sure how to fix it
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SoaS] Errors from Soas 29

[Iain Brown Douglas]

On Thu, 2019-01-17 at 10:28 +0100, Samson Goddy wrote:
> Yes, we did. Upgraded metacity and Sugar, also made changes to the
> ~/profile.py
> 
> On Thu, Jan 17, 2019, 10:26 AM Peter Robinson  wrote:
> > Have you applied all the latest updates to Fedora, a number of
> > issues have been fixed with Fedora 29 updates.
> > 
> > Peter
> > 
> > On Thu, Jan 17, 2019 at 8:52 AM Samson Goddy  > > wrote:

> > > Ibiam and I are currently working to install Sugar in the
> > > classroom, 

> > >   Quick question? what are the best ways to make sugar to talk to
> > > each other?

Persevere with WiFi.
Don't mix copper/Ethernet with WiFi.
Any machine connected with copper, disconnect copper, (for good measure
remove ~/.sugar), reboot with WiFi/USB WiFi stick plugged in.
Stick not recognised, follow: https://help.gnome.org/users/gnome-help/s
table/net-wireless-troubleshooting.html.en
Follow Help Activity to get each machine online.

Iain

> > > Those desktop are using mini USB wifi adaptors(working on
> > > windows) but not Soas. I will be testing on more systems by
> > > Wednesday.   
> > > 
> > > Logs[2]
> > > 
> > > 
> > > 
> > > 
> > > 
> > > [1]https://wiki.sugarlabs.org/go/Sugar_on_a_Stick#Known_bugs
> > > [2]https://paste.fedoraproject.org/paste/4QIR-XATy2wmnZb2VbNn3A
> > > 
> > > -- 
> > > 
> > > Samson Goddy
> > > Twitter: https://twitter.com/samson_goddy
> > > Email: samsongo...@sugarlabs.org
> > >             samsongoddy@gmail.comWebsite: https://samsongoddy.me/
> > >  
> > > 
> > > ___
> > > SoaS mailing list
> > > s...@lists.sugarlabs.org
> > > http://lists.sugarlabs.org/listinfo/soas
> > > 
> > 
> > ___
> > SoaS mailing list
> > s...@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/soas
> > 
> 
> ___
> SoaS mailing list
> s...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] RPi Project for GSoC 2019

[Rahul Bothra]

Thanks,

On Thu, Jan 17, 2019 at 9:12 PM Aman Sharma 
wrote:
> 1) Turtle Blocks access to RPi sensors / devices.
> 2) Long term support plan.
> 3) Methodical Testing Plan

Please elaborate on 2 and 3. My opinion is that 'plans' should be made by
regular
contributors and can be implemented during GSoC.

Will these goals be enough for a 3 month long GSoC Project?
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] RPi Project for GSoC 2019

[Aman Sharma]

Hello

As a part of GSoC 2019 we are looking forward to increase the scope of our
previous Sugar on RPi image which was initially developed during GSoC 2017.
It is suggested by Mr.Walter Bender that we should include the following
goals for the project:

1) Turtle Blocks access to RPi sensors / devices.
2) Long term support plan.
3) Methodical Testing Plan

Before adding this project to the idea list I am looking forward to have
some more suggestions from the community regarding the activities that can
leverage sensors or other devices that could be paired with the RPi to
enhance user experience.
Kindly provide your suggestions regarding the same.

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

[Sugar-devel] GSOC 2019 Student

[Shiv Pratap Singh]

Hi all,
I am undergraduate student in computer science.I find myself good with
skills required to contribute in the projects in your organization.
I will be applying as GSOC student for the organization by developing
features.
How can I get started ? Just to confirm if this organization is going
to participate in upcoming GSOC.Please let me know where can I find all
details to get started.
Thank You!
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SoaS] Errors from Soas 29

[Samson Goddy]

Yes, we did. Upgraded metacity and Sugar, also made changes to the
~/profile.py

On Thu, Jan 17, 2019, 10:26 AM Peter Robinson  Have you applied all the latest updates to Fedora, a number of issues have
> been fixed with Fedora 29 updates.
>
> Peter
>
> On Thu, Jan 17, 2019 at 8:52 AM Samson Goddy 
> wrote:
>
>> Hello,
>>
>> Ibiam and I are currently working to install Sugar in the classroom, so
>> we decided to download Soas 32-bit versions. After installing, we ran into
>> some problems immediately after the desktop booted which can be found
>> here[1]. I also noticed whenever I click on the speaker icon, the bottom of
>> the frame becomes darker. I tested collaboration using Jabber service,
>> Ibiam couldn't find the desktop on the neighborhood but the desktop can
>> alongside.
>>
>>   Quick question? what are the best ways to make sugar to talk to each
>> other? Those desktop are using mini USB wifi adaptors(working on windows)
>> but not Soas. I will be testing on more systems by Wednesday.
>>
>> Logs[2]
>>
>>
>>
>>
>>
>> [1]https://wiki.sugarlabs.org/go/Sugar_on_a_Stick#Known_bugs
>> [2]https://paste.fedoraproject.org/paste/4QIR-XATy2wmnZb2VbNn3A
>>
>> --
>>
>> Samson Goddy
>>
>> Twitter: https://twitter.com/samson_goddy
>> Email: samsongo...@sugarlabs.org
>> samsongo...@gmail.com
>>
>> Website: https://samsongoddy.me/  
>>
>> ___
>> SoaS mailing list
>> s...@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/soas
>>
> ___
> SoaS mailing list
> s...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SoaS] Errors from Soas 29

[Peter Robinson]

Have you applied all the latest updates to Fedora, a number of issues have
been fixed with Fedora 29 updates.

Peter

On Thu, Jan 17, 2019 at 8:52 AM Samson Goddy  wrote:

> Hello,
>
> Ibiam and I are currently working to install Sugar in the classroom, so we
> decided to download Soas 32-bit versions. After installing, we ran into
> some problems immediately after the desktop booted which can be found
> here[1]. I also noticed whenever I click on the speaker icon, the bottom of
> the frame becomes darker. I tested collaboration using Jabber service,
> Ibiam couldn't find the desktop on the neighborhood but the desktop can
> alongside.
>
>   Quick question? what are the best ways to make sugar to talk to each
> other? Those desktop are using mini USB wifi adaptors(working on windows)
> but not Soas. I will be testing on more systems by Wednesday.
>
> Logs[2]
>
>
>
>
>
> [1]https://wiki.sugarlabs.org/go/Sugar_on_a_Stick#Known_bugs
> [2]https://paste.fedoraproject.org/paste/4QIR-XATy2wmnZb2VbNn3A
>
> --
>
> Samson Goddy
>
> Twitter: https://twitter.com/samson_goddy
> Email: samsongo...@sugarlabs.org
> samsongo...@gmail.com
>
> Website: https://samsongoddy.me/  
>
> ___
> SoaS mailing list
> s...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Errors from Soas 29

[Samson Goddy]

Hello,

Ibiam and I are currently working to install Sugar in the classroom, so we
decided to download Soas 32-bit versions. After installing, we ran into
some problems immediately after the desktop booted which can be found
here[1]. I also noticed whenever I click on the speaker icon, the bottom of
the frame becomes darker. I tested collaboration using Jabber service,
Ibiam couldn't find the desktop on the neighborhood but the desktop can
alongside.

  Quick question? what are the best ways to make sugar to talk to each
other? Those desktop are using mini USB wifi adaptors(working on windows)
but not Soas. I will be testing on more systems by Wednesday.

Logs[2]





[1]https://wiki.sugarlabs.org/go/Sugar_on_a_Stick#Known_bugs
[2]https://paste.fedoraproject.org/paste/4QIR-XATy2wmnZb2VbNn3A

-- 

Samson Goddy

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

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