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

2019-01-17 Thread 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

[Sugar-devel] Abandoned or orphaned activities

2019-01-17 Thread 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,

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

2019-01-17 Thread 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

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

2019-01-17 Thread 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

Re: [Sugar-devel] GSOC 2019 Student

2019-01-17 Thread 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

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

2019-01-17 Thread 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

Re: [Sugar-devel] GSoC project ideas

2019-01-17 Thread 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.

Re: [Sugar-devel] GSoC project ideas

2019-01-17 Thread 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

[Sugar-devel] Sync between GitHub and ASLO

2019-01-17 Thread 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

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

2019-01-17 Thread 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

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

2019-01-17 Thread 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

[Sugar-devel] RPi Project for GSoC 2019

2019-01-17 Thread 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 /

[Sugar-devel] GSOC 2019 Student

2019-01-17 Thread 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

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

2019-01-17 Thread 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

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

2019-01-17 Thread 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

[Sugar-devel] Errors from Soas 29

2019-01-17 Thread 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