From shray.tyagi18 at vit.edu Fri Jan 1 03:46:37 2021 From: shray.tyagi18 at vit.edu (SHRAY TYAGI) Date: Fri, 1 Jan 2021 14:16:37 +0530 Subject: [Sugar-devel] Introduction Message-ID: Hello, My name is Shray Tyagi and I am a 3rd-year BTech student at Vishwakarma Institute of Technology Pune. My technical knowledge includes python, React JS, Html, CSS,django, Mysql,data structures and basics of java, Machine learning, c , c++. Some of my projects include a basic django todo app, car showroom database management system, digit detection using neural networks, basic chatbot, etc. I am very much interested in participating in GSoC 2021. The main reason for doing GSoC is to get exposure to the developer's world and to work with new people. I am looking forward to working under sugarlabs. Regards, Shray Tyagi -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Fri Jan 1 19:14:32 2021 From: quozl at laptop.org (James Cameron) Date: Sat, 2 Jan 2021 11:14:32 +1100 Subject: [Sugar-devel] Introduction In-Reply-To: References: Message-ID: <20210102001432.GB25533@laptop.org> Welcome. Your experience with Django is immediately useful; we have a Django app called Pootle on https://translate.sugarlabs.org/ that has not been maintained recently. We continue to have occasional translators, but I don't think we have an active translation manager. A few years ago, Bernie Innocenti wrote "Sysadmin documentation is in the usual place (the wiki). There are several pages written by the previous Pootle maintainers: http://wiki.sugarlabs.org/go/Service/translate http://wiki.sugarlabs.org/go/Service/Pootle http://wiki.sugarlabs.org/go/Service/Pootle2.5 http://wiki.sugarlabs.org/go/Machine/pootle " Is that something you're interested in? On Fri, Jan 01, 2021 at 02:16:37PM +0530, SHRAY TYAGI wrote: > Hello, My name is Shray Tyagi and I am a 3rd-year BTech student at Vishwakarma > Institute of Technology Pune. My technical knowledge includes python, React JS, > Html, CSS,django, Mysql,data structures and basics of java, Machine learning, c > , c++. Some of my projects include a basic django todo app, car showroom > database management system, digit detection using neural networks, basic > chatbot, etc. I am very much interested in participating in GSoC 2021. The main > reason for doing GSoC is to get exposure to the developer's world and to work > with new people. I am looking forward to working under sugarlabs. > > Regards, > Shray Tyagi > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From shray.tyagi18 at vit.edu Fri Jan 1 21:25:17 2021 From: shray.tyagi18 at vit.edu (SHRAY TYAGI) Date: Sat, 2 Jan 2021 07:55:17 +0530 Subject: [Sugar-devel] Introduction In-Reply-To: <20210102001432.GB25533@laptop.org> References: <20210102001432.GB25533@laptop.org> Message-ID: Yes, I would be interested. On Sat, 2 Jan 2021, 05:44 James Cameron, wrote: > Welcome. Your experience with Django is immediately useful; we have a > Django app called Pootle on https://translate.sugarlabs.org/ that has > not been maintained recently. We continue to have occasional > translators, but I don't think we have an active translation manager. > > A few years ago, Bernie Innocenti wrote "Sysadmin documentation is in > the usual place (the wiki). There are several pages written by the > previous Pootle maintainers: > > http://wiki.sugarlabs.org/go/Service/translate > http://wiki.sugarlabs.org/go/Service/Pootle > http://wiki.sugarlabs.org/go/Service/Pootle2.5 > http://wiki.sugarlabs.org/go/Machine/pootle > " > > Is that something you're interested in? > > On Fri, Jan 01, 2021 at 02:16:37PM +0530, SHRAY TYAGI wrote: > > Hello, My name is Shray Tyagi and I am a 3rd-year BTech student at > Vishwakarma > > Institute of Technology Pune. My technical knowledge includes python, > React JS, > > Html, CSS,django, Mysql,data structures and basics of java, Machine > learning, c > > , c++. Some of my projects include a basic django todo app, car showroom > > database management system, digit detection using neural networks, basic > > chatbot, etc. I am very much interested in participating in GSoC 2021. > The main > > reason for doing GSoC is to get exposure to the developer's world and to > work > > with new people. I am looking forward to working under sugarlabs. > > > > Regards, > > Shray Tyagi > > > _______________________________________________ > > Sugar-devel mailing list > > Sugar-devel at lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > -- > James Cameron > https://quozl.linux.org.au/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Fri Jan 1 21:32:35 2021 From: quozl at laptop.org (James Cameron) Date: Sat, 2 Jan 2021 13:32:35 +1100 Subject: [Sugar-devel] Introduction In-Reply-To: References: <20210102001432.GB25533@laptop.org> Message-ID: <20210102023235.GB1019@laptop.org> Good to hear, thanks. On Sat, Jan 02, 2021 at 07:55:17AM +0530, SHRAY TYAGI wrote: > Yes, I would be interested.? > > On Sat, 2 Jan 2021, 05:44 James Cameron, <[1]quozl at laptop.org> wrote: > > Welcome.? Your experience with Django is immediately useful; we have a > Django app called Pootle on [2]https://translate.sugarlabs.org/ that has > not been maintained recently.? We continue to have occasional > translators, but I don't think we have an active translation manager. > > A few years ago, Bernie Innocenti wrote "Sysadmin documentation is in > the usual place (the wiki). There are several pages written by the > previous Pootle maintainers: > > ? [3]http://wiki.sugarlabs.org/go/Service/translate > ? [4]http://wiki.sugarlabs.org/go/Service/Pootle > ? [5]http://wiki.sugarlabs.org/go/Service/Pootle2.5 > ? [6]http://wiki.sugarlabs.org/go/Machine/pootle > " > > Is that something you're interested in? > > On Fri, Jan 01, 2021 at 02:16:37PM +0530, SHRAY TYAGI wrote: > > Hello, My name is Shray Tyagi and I am a 3rd-year BTech student at > Vishwakarma > > Institute of Technology Pune. My technical knowledge includes python, > React JS, > > Html, CSS,django, Mysql,data structures and basics of java, Machine > learning, c > > , c++. Some of my projects include a basic django todo app, car showroom > > database management system, digit detection using neural networks, basic > > chatbot, etc. I am very much interested in participating in GSoC 2021. > The main > > reason for doing GSoC is to get exposure to the developer's world and to > work > > with new people. I am looking forward to working under sugarlabs. > > > > Regards, > > Shray Tyagi > > > _______________________________________________ > > Sugar-devel mailing list > > [7]Sugar-devel at lists.sugarlabs.org > > [8]http://lists.sugarlabs.org/listinfo/sugar-devel > > -- > James Cameron > [9]https://quozl.linux.org.au/ > > References: > > [1] mailto:quozl at laptop.org > [2] https://translate.sugarlabs.org/ > [3] http://wiki.sugarlabs.org/go/Service/translate > [4] http://wiki.sugarlabs.org/go/Service/Pootle > [5] http://wiki.sugarlabs.org/go/Service/Pootle2.5 > [6] http://wiki.sugarlabs.org/go/Machine/pootle > [7] mailto:Sugar-devel at lists.sugarlabs.org > [8] http://lists.sugarlabs.org/listinfo/sugar-devel > [9] https://quozl.linux.org.au/ -- James Cameron https://quozl.linux.org.au/ From jasbir.sb123 at gmail.com Sat Jan 2 13:39:23 2021 From: jasbir.sb123 at gmail.com (jasbir singh) Date: Sun, 3 Jan 2021 00:09:23 +0530 Subject: [Sugar-devel] Participation in GSOC 2021 Message-ID: Hii, My Name is Jasbir Singh, a 3rd year student at Army Institute of Technology, Pune. I am pretty confident in c++, python, HTML, CSS, Django, REST framework, MySQL, data structures, Algorithms and Machine learning. I have built some of the amazing projects using the mentioned technology stack. I am eagerly looking forward to participate in GSoC 2021 and contribute at Sugar Labs. I want to get gain experience and capitalize my technical and social skills by working in this vast open source community. Looking forward to work at Sugar Labs under your able guidance. Regards, Jasbir Singh -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Sun Jan 3 16:31:40 2021 From: quozl at laptop.org (James Cameron) Date: Mon, 4 Jan 2021 08:31:40 +1100 Subject: [Sugar-devel] Participation in GSOC 2021 In-Reply-To: References: Message-ID: <20210103213140.GB5951@laptop.org> Thanks for your interest in GSoC 2021 at Sugar Labs. We are yet to hear from the oversight board if Sugar Labs will participate this year. To participate, we need; (a) active projects, (b) active developers, (c) developers with a capacity and willingness to mentor, (d) developers to take on the administrator function, (e) ideas for student projects, (f) an application to, and acceptance by Google. Sugarizer and Music Blocks are active at the moment, but Sugar has been inactive since GSoC 2020. My guess is we have two or three developers per project with the capacity to mentor. You can see our preparations last year at https://github.com/sugarlabs/GSoC On Sun, Jan 03, 2021 at 12:09:23AM +0530, jasbir singh wrote: > Hii, My Name is Jasbir Singh, a 3rd year student at Army Institute of > Technology, Pune. > > I am pretty confident in c++, python, HTML, CSS, Django, REST framework, MySQL, > data structures, Algorithms and Machine learning. I have built some of the > amazing projects using the mentioned technology stack. > > I am eagerly looking forward to participate in GSoC 2021 and contribute?at > Sugar Labs. > I want to get gain experience and capitalize my technical and social skills by > working in this vast open source community. > > Looking forward to work at Sugar Labs under your able?guidance. > > Regards, > Jasbir Singh > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From shray.tyagi18 at vit.edu Mon Jan 4 21:54:37 2021 From: shray.tyagi18 at vit.edu (SHRAY TYAGI) Date: Tue, 5 Jan 2021 08:24:37 +0530 Subject: [Sugar-devel] work on pootle Message-ID: Hello james, Sorry I haven't started yet. But as soon as my college exams gets over which will be by the end of this week, I will start. Regards, Shray tyagi -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Mon Jan 4 22:00:49 2021 From: quozl at laptop.org (James Cameron) Date: Tue, 5 Jan 2021 14:00:49 +1100 Subject: [Sugar-devel] work on pootle In-Reply-To: References: Message-ID: <20210105030049.GG5457@laptop.org> No worries. Take as many exams as you like, the problem has been with us for years and is still be waiting for people to work it. Don't worry about missing out; if anybody else works the problem, it should be obvious, because they will say so. I've not worked the problem since. On Tue, Jan 05, 2021 at 08:24:37AM +0530, SHRAY TYAGI wrote: > Hello james,? > Sorry I haven't started yet. But as soon as my college exams gets over which > will be by the end of this week, I will start. > > Regards, > Shray tyagi? -- James Cameron https://quozl.linux.org.au/ From walter.bender at gmail.com Tue Jan 5 08:47:13 2021 From: walter.bender at gmail.com (Walter Bender) Date: Tue, 5 Jan 2021 08:47:13 -0500 Subject: [Sugar-devel] meeting reminder Message-ID: The next Sugar Labs oversight board meeting is Wednesday, 2021-01-06 at 19:30 UTC (2:30 PM on the US East Coast). There will be a finance report and we will be discussing Claudia's idea of monthly virtual workshops. Please join us on Jitsi [1]. regards. -walter [1] https://meet.jit.si/sugarlabs -- Walter Bender Sugar Labs http://www.sugarlabs.org From juipradhan2k at gmail.com Tue Jan 5 09:03:03 2021 From: juipradhan2k at gmail.com (Jui Pradhan) Date: Tue, 5 Jan 2021 19:33:03 +0530 Subject: [Sugar-devel] [SLOBS] meeting reminder In-Reply-To: References: Message-ID: Hi everyone, We might as well discuss Sugarlabs participation in GSoC 2021. The period to apply for mentoring organizations is January 29 - February 19, 2021 (GSoC 2021 Timeline ). Regards, Jui On Tue, Jan 5, 2021 at 7:17 PM Walter Bender wrote: > The next Sugar Labs oversight board meeting is Wednesday, 2021-01-06 > at 19:30 UTC (2:30 PM on the US East Coast). > > There will be a finance report and we will be discussing Claudia's > idea of monthly virtual workshops. > > Please join us on Jitsi [1]. > > regards. > > -walter > > [1] https://meet.jit.si/sugarlabs > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > _______________________________________________ > SLOBs mailing list > SLOBs at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/slobs > -- Jui Pradhan -------------- next part -------------- An HTML attachment was scrubbed... URL: From walter.bender at gmail.com Tue Jan 5 09:22:56 2021 From: walter.bender at gmail.com (Walter Bender) Date: Tue, 5 Jan 2021 09:22:56 -0500 Subject: [Sugar-devel] [SLOBS] meeting reminder In-Reply-To: References: Message-ID: Noted. thx On Tue, Jan 5, 2021 at 9:03 AM Jui Pradhan wrote: > > Hi everyone, > We might as well discuss Sugarlabs participation in GSoC 2021. The period to apply for mentoring organizations is January 29 - February 19, 2021 (GSoC 2021 Timeline). > > Regards, > Jui > > On Tue, Jan 5, 2021 at 7:17 PM Walter Bender wrote: >> >> The next Sugar Labs oversight board meeting is Wednesday, 2021-01-06 >> at 19:30 UTC (2:30 PM on the US East Coast). >> >> There will be a finance report and we will be discussing Claudia's >> idea of monthly virtual workshops. >> >> Please join us on Jitsi [1]. >> >> regards. >> >> -walter >> >> [1] https://meet.jit.si/sugarlabs >> -- >> Walter Bender >> Sugar Labs >> http://www.sugarlabs.org >> _______________________________________________ >> SLOBs mailing list >> SLOBs at lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/slobs > > > > -- > Jui Pradhan -- Walter Bender Sugar Labs http://www.sugarlabs.org From callaurrea at gmail.com Tue Jan 5 20:18:07 2021 From: callaurrea at gmail.com (Claudia Urrea) Date: Tue, 5 Jan 2021 20:18:07 -0500 Subject: [Sugar-devel] [Sur] [SLOBS] meeting reminder In-Reply-To: References: Message-ID: Walter and all, I just received confirmation about a meeting with the new minister of education in Belize. I am in the PI of a three year project with the government and I need to be there to present. The meeting is scheduled for 2:30 pm for 30 min. I will do my best to come back, but I can't miss this meeting. I apologize for the last minute change, but this is a significant 3 year long project with a team of over 15 people from MIT. I will keep you all posted. Claudia On Tue, Jan 5, 2021 at 9:23 AM Walter Bender wrote: > Noted. > > thx > > On Tue, Jan 5, 2021 at 9:03 AM Jui Pradhan wrote: > > > > Hi everyone, > > We might as well discuss Sugarlabs participation in GSoC 2021. The > period to apply for mentoring organizations is January 29 - February 19, > 2021 (GSoC 2021 Timeline). > > > > Regards, > > Jui > > > > On Tue, Jan 5, 2021 at 7:17 PM Walter Bender > wrote: > >> > >> The next Sugar Labs oversight board meeting is Wednesday, 2021-01-06 > >> at 19:30 UTC (2:30 PM on the US East Coast). > >> > >> There will be a finance report and we will be discussing Claudia's > >> idea of monthly virtual workshops. > >> > >> Please join us on Jitsi [1]. > >> > >> regards. > >> > >> -walter > >> > >> [1] https://meet.jit.si/sugarlabs > >> -- > >> Walter Bender > >> Sugar Labs > >> http://www.sugarlabs.org > >> _______________________________________________ > >> SLOBs mailing list > >> SLOBs at lists.sugarlabs.org > >> http://lists.sugarlabs.org/listinfo/slobs > > > > > > > > -- > > Jui Pradhan > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > _______________________________________________ > Lista olpc-Sur > olpc-Sur at lists.laptop.org > http://lists.laptop.org/listinfo/olpc-sur > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ibiamchihurumnaya at gmail.com Wed Jan 6 01:07:30 2021 From: ibiamchihurumnaya at gmail.com (Chihurumnaya Ibiam) Date: Wed, 6 Jan 2021 07:07:30 +0100 Subject: [Sugar-devel] [SLOBS] meeting reminder In-Reply-To: References: Message-ID: Hi Everyone, I'll try making it to the meeting but I doubt I'll make it as I'm currently in an area with bad internet access so I'll read the logs. Thanks. On Tue, Jan 5, 2021, 2:47 PM Walter Bender wrote: > The next Sugar Labs oversight board meeting is Wednesday, 2021-01-06 > at 19:30 UTC (2:30 PM on the US East Coast). > > There will be a finance report and we will be discussing Claudia's > idea of monthly virtual workshops. > > Please join us on Jitsi [1]. > > regards. > > -walter > > [1] https://meet.jit.si/sugarlabs > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > _______________________________________________ > SLOBs mailing list > SLOBs at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/slobs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tulsidasanikunal at gmail.com Thu Jan 7 06:42:46 2021 From: tulsidasanikunal at gmail.com (Kunal Tulsidasani) Date: Thu, 7 Jan 2021 17:12:46 +0530 Subject: [Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021 Message-ID: Hello, I hope you all are doing well. I am Kunal. I live in Jodhpur. I am a 2nd Year CSE B.Tech Student at IIITDM Jabalpur. I am good in Python and C++. I really want to contribute to Sugar Labs but I am a beginner to open-source. What should I do to begin? I could be a really great asset if I get proper guidance. Regards Kunal -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Thu Jan 7 18:53:37 2021 From: quozl at laptop.org (James Cameron) Date: Fri, 8 Jan 2021 10:53:37 +1100 Subject: [Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021 In-Reply-To: References: Message-ID: <20210107235337.GE26362@laptop.org> Welcom Kunal, As you know Python and C++, you may be interested in the unmet needs of the Sugar Toolkit, which has a lot of C code that has not been maintained for about ten years. The libraries used by the C code have changed slightly, and some libraries are also unmaintained. However, we have nobody who can give proper guidance; otherwise we'd do it ourselves as it would be more efficient than guiding anybody. You can find the Sugar Toolkit here; https://github.com/sugarlabs/sugar-toolkit-gtk3 Most of the C code is in src/sugar3 path, and is arranged as a Python extension so that Sugar and activities may call it. On Thu, Jan 07, 2021 at 05:12:46PM +0530, Kunal Tulsidasani wrote: > Hello, > > I hope you all are doing well. > > I am Kunal. I live in Jodhpur. I am a 2nd Year CSE B.Tech Student at IIITDM > Jabalpur. I am good in Python and C++. I really want to contribute to Sugar > Labs but I am a beginner to open-source. What should I do to begin? I could be > a really great asset if I get proper guidance. > > Regards > Kunal > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From tulsidasanikunal at gmail.com Fri Jan 8 03:10:53 2021 From: tulsidasanikunal at gmail.com (Kunal Tulsidasani) Date: Fri, 8 Jan 2021 13:40:53 +0530 Subject: [Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021 In-Reply-To: <20210107235337.GE26362@laptop.org> References: <20210107235337.GE26362@laptop.org> Message-ID: Thankyou for your reply! I will surely try to cope up with the needs of C code and do my best! I have taken a look at the code and I would be really obliged if you could help me to set up the development environment for sugar-toolkit-gtk3. Regards Kunal On Fri, Jan 8, 2021 at 5:23 AM James Cameron wrote: > Welcom Kunal, > > As you know Python and C++, you may be interested in the unmet needs > of the Sugar Toolkit, which has a lot of C code that has not been > maintained for about ten years. > > The libraries used by the C code have changed slightly, and some > libraries are also unmaintained. > > However, we have nobody who can give proper guidance; otherwise we'd > do it ourselves as it would be more efficient than guiding anybody. > > You can find the Sugar Toolkit here; > https://github.com/sugarlabs/sugar-toolkit-gtk3 > > Most of the C code is in src/sugar3 path, and is arranged as a Python > extension so that Sugar and activities may call it. > > On Thu, Jan 07, 2021 at 05:12:46PM +0530, Kunal Tulsidasani wrote: > > Hello, > > > > I hope you all are doing well. > > > > I am Kunal. I live in Jodhpur. I am a 2nd Year CSE B.Tech Student at > IIITDM > > Jabalpur. I am good in Python and C++. I really want to contribute to > Sugar > > Labs but I am a beginner to open-source. What should I do to begin? I > could be > > a really great asset if I get proper guidance. > > > > Regards > > Kunal > > > > > _______________________________________________ > > Sugar-devel mailing list > > Sugar-devel at lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > -- > James Cameron > https://quozl.linux.org.au/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From srevinsaju at sugarlabs.org Fri Jan 8 03:15:31 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Fri, 8 Jan 2021 11:15:31 +0300 Subject: [Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021 In-Reply-To: References: <20210107235337.GE26362@laptop.org> Message-ID: You might be interested in https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md for setting up a development environment. On 1/8/21 11:10 AM, Kunal Tulsidasani wrote: > Thankyou for your reply! > > I will surely try to cope up with the needs of C code and do my best! > > I have taken a look at the code and I would be really obliged if you > could help me to set up the development environment for > sugar-toolkit-gtk3. > > Regards > Kunal > > > On Fri, Jan 8, 2021 at 5:23 AM James Cameron > wrote: > > Welcom Kunal, > > As you know Python and C++, you may be interested in the unmet needs > of the Sugar Toolkit, which has a lot of C code that has not been > maintained for about ten years. > > The libraries used by the C code have changed slightly, and some > libraries are also unmaintained. > > However, we have nobody who can give proper guidance; otherwise we'd > do it ourselves as it would be more efficient than guiding anybody. > > You can find the Sugar Toolkit here; > https://github.com/sugarlabs/sugar-toolkit-gtk3 > > > Most of the C code is in src/sugar3 path, and is arranged as a Python > extension so that Sugar and activities may call it. > > On Thu, Jan 07, 2021 at 05:12:46PM +0530, Kunal Tulsidasani wrote: > > Hello, > > > > I hope you all are doing well. > > > > I am Kunal. I live in Jodhpur. I am a 2nd Year CSE B.Tech > Student at IIITDM > > Jabalpur. I am good in Python and C++. I really want to > contribute to Sugar > > Labs but I am a beginner to open-source. What should I do to > begin? I could be > > a really great asset if I get proper guidance. > > > > Regards > > Kunal > > > > > _______________________________________________ > > Sugar-devel mailing list > > Sugar-devel at lists.sugarlabs.org > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > -- > James Cameron > https://quozl.linux.org.au/ > > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From vishalbhatane123 at gmail.com Sat Jan 9 10:35:28 2021 From: vishalbhatane123 at gmail.com (Vishal Bhatane) Date: Sat, 9 Jan 2021 21:05:28 +0530 Subject: [Sugar-devel] GSoC 2021 Contribution Message-ID: Hi this is vishal, 3rd year student of college of engineering , pune. I'm looking forward to contributing to sugarlabs. While going through sugar devel archives I found that in one of the emails it is mentioned Sugar has been inactive since GSoC 2020. Does that mean In GSoC 2021 there will be no project selected from sugar ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From srevinsaju at sugarlabs.org Sat Jan 9 12:02:06 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Sat, 9 Jan 2021 20:02:06 +0300 Subject: [Sugar-devel] GSoC 2021 Contribution In-Reply-To: References: Message-ID: Sugar Labs will be participating in GSoC 2021 w.r.t 2021-01-06 motion, taken by the Oversight Board. The projects will be Sugar, Sugarizer and Musicblocks. Others: please correct me if I am wrong. On 1/9/21 6:35 PM, Vishal Bhatane wrote: > Hi this is vishal, 3rd year student of college of engineering , pune. > I'm looking forward to contributing to sugarlabs. While going through > sugar devel archives I found that in one of the emails it is mentioned > Sugar has been inactive since GSoC 2020. Does that mean In GSoC 2021 > there will be no project selected from sugar ? > > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x1007816766D390D7.asc Type: application/pgp-keys Size: 4849 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From quozl at laptop.org Sun Jan 10 18:19:16 2021 From: quozl at laptop.org (James Cameron) Date: Mon, 11 Jan 2021 10:19:16 +1100 Subject: [Sugar-devel] GSoC 2021 Contribution In-Reply-To: References: Message-ID: <20210110231916.GE2637@laptop.org> In addition to what Srevin said ... Thanks for reading archives. No, it doesn't mean that there will be no project selected from Sugar. Inactivity in the Sugar and activity repositories is an indicator of both source code stability and very few active developers. For the Sugar project, indications are that we still have two or three developers with the capacity to mentor. We will find out for sure after the application is accepted by Google and we must select capable mentors. You have time yet to demonstrate your capacity to mentor. Once GSoC 2021 gets underway, the next threshold is for us to receive student project proposals that have significant value. A lot of dominoes must be positioned in the right order and fall in the right way. https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-01-06 shows our GSoC organisation administrators this year will be Jui, Perrie, and Lionel. Last year was Walter and myself. On Sat, Jan 09, 2021 at 09:05:28PM +0530, Vishal Bhatane wrote: > Hi this is vishal, 3rd year student of college of engineering , pune. I'm > looking forward to contributing to sugarlabs. While going through sugar devel > archives I found that in one of the emails it is mentioned?Sugar has been > inactive since GSoC 2020. Does that mean In GSoC 2021 there will be no project > selected from sugar ?? > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From vishalbhatane123 at gmail.com Mon Jan 11 06:19:39 2021 From: vishalbhatane123 at gmail.com (Vishal Bhatane) Date: Mon, 11 Jan 2021 16:49:39 +0530 Subject: [Sugar-devel] GSoC 2021 Contribution In-Reply-To: <20210110231916.GE2637@laptop.org> References: <20210110231916.GE2637@laptop.org> Message-ID: Ok . Thank you for the clarification. On Mon, Jan 11, 2021 at 4:49 AM James Cameron wrote: > In addition to what Srevin said ... > > Thanks for reading archives. > > No, it doesn't mean that there will be no project selected from Sugar. > > Inactivity in the Sugar and activity repositories is an indicator of > both source code stability and very few active developers. > > For the Sugar project, indications are that we still have two or three > developers with the capacity to mentor. > > We will find out for sure after the application is accepted by Google > and we must select capable mentors. > > You have time yet to demonstrate your capacity to mentor. > > Once GSoC 2021 gets underway, the next threshold is for us to receive > student project proposals that have significant value. > > A lot of dominoes must be positioned in the right order and fall in > the right way. > > https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-01-06 > shows our GSoC organisation administrators this year will be Jui, > Perrie, and Lionel. Last year was Walter and myself. > > On Sat, Jan 09, 2021 at 09:05:28PM +0530, Vishal Bhatane wrote: > > Hi this is vishal, 3rd year student of college of engineering , pune. I'm > > looking forward to contributing to sugarlabs. While going through sugar > devel > > archives I found that in one of the emails it is mentioned Sugar has been > > inactive since GSoC 2020. Does that mean In GSoC 2021 there will be no > project > > selected from sugar ? > > > > > _______________________________________________ > > Sugar-devel mailing list > > Sugar-devel at lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > -- > James Cameron > https://quozl.linux.org.au/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ibiamchihurumnaya at gmail.com Mon Jan 11 11:56:09 2021 From: ibiamchihurumnaya at gmail.com (Chihurumnaya Ibiam) Date: Mon, 11 Jan 2021 17:56:09 +0100 Subject: [Sugar-devel] SOAS 33/34 Changes. Message-ID: Hi Everyone, SOAS was failing to build in F34 due to telepathy-salut being deprecated and needed as a dependency in sugar, F33 beta had an issue where startup goes straight to login. Both have been fixed after today's compose was released and can be tested. Download here . I don't think it's wise to change the download link in our wiki to reflect this - uploaded to sunjammer of course - as it's a compose image but Peter can tell if it's wise to. -- Ibiam Chihurumnaya ibiamchihurumnaya at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From pbrobinson at gmail.com Mon Jan 11 13:07:04 2021 From: pbrobinson at gmail.com (Peter Robinson) Date: Mon, 11 Jan 2021 18:07:04 +0000 Subject: [Sugar-devel] SOAS 33/34 Changes. In-Reply-To: References: Message-ID: On Mon, Jan 11, 2021 at 4:56 PM Chihurumnaya Ibiam wrote: > > Hi Everyone, > > SOAS was failing to build in F34 due to telepathy-salut being deprecated and needed as a dependency in sugar, F33 beta had an issue where startup goes straight to login. > > Both have been fixed after today's compose was released and can be tested. > Download here. > > I don't think it's wise to change the download link in our wiki to reflect this - uploaded to sunjammer of course - as it's a compose image but Peter can tell if it's wise to. The link is for rawhide which is the nightly development snapshots, it might be worthwhile putting a link for those interested in testing that to know the state of SoAS for the next release and be able to test issues with it and provide fixes, there's also an arm nightly image too. From tulsidasanikunal at gmail.com Tue Jan 12 11:52:35 2021 From: tulsidasanikunal at gmail.com (Kunal Tulsidasani) Date: Tue, 12 Jan 2021 22:22:35 +0530 Subject: [Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021 In-Reply-To: References: <20210107235337.GE26362@laptop.org> Message-ID: Hello! I hope you all are doing well! I have set up the development environment using packaged sugar with your help! For now I have forked and cloned and working on some issues. May I know how I should test my code (Procedure) after making commits before making any pull requests? I'll be really obliged if you could tell. Yours sincerely Kunal On Fri, Jan 8, 2021 at 1:45 PM Srevin Saju wrote: > You might be interested in > > https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md > for setting up a development environment. > > > On 1/8/21 11:10 AM, Kunal Tulsidasani wrote: > > Thankyou for your reply! > > > > I will surely try to cope up with the needs of C code and do my best! > > > > I have taken a look at the code and I would be really obliged if you > > could help me to set up the development environment for > > sugar-toolkit-gtk3. > > > > Regards > > Kunal > > > > > > On Fri, Jan 8, 2021 at 5:23 AM James Cameron > > wrote: > > > > Welcom Kunal, > > > > As you know Python and C++, you may be interested in the unmet needs > > of the Sugar Toolkit, which has a lot of C code that has not been > > maintained for about ten years. > > > > The libraries used by the C code have changed slightly, and some > > libraries are also unmaintained. > > > > However, we have nobody who can give proper guidance; otherwise we'd > > do it ourselves as it would be more efficient than guiding anybody. > > > > You can find the Sugar Toolkit here; > > https://github.com/sugarlabs/sugar-toolkit-gtk3 > > > > > > Most of the C code is in src/sugar3 path, and is arranged as a Python > > extension so that Sugar and activities may call it. > > > > On Thu, Jan 07, 2021 at 05:12:46PM +0530, Kunal Tulsidasani wrote: > > > Hello, > > > > > > I hope you all are doing well. > > > > > > I am Kunal. I live in Jodhpur. I am a 2nd Year CSE B.Tech > > Student at IIITDM > > > Jabalpur. I am good in Python and C++. I really want to > > contribute to Sugar > > > Labs but I am a beginner to open-source. What should I do to > > begin? I could be > > > a really great asset if I get proper guidance. > > > > > > Regards > > > Kunal > > > > > > > > _______________________________________________ > > > Sugar-devel mailing list > > > Sugar-devel at lists.sugarlabs.org > > > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > > > > -- > > James Cameron > > https://quozl.linux.org.au/ > > > > > > _______________________________________________ > > Sugar-devel mailing list > > Sugar-devel at lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- > Srevin Saju > https://srevinsaju.me > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From srevinsaju at sugarlabs.org Tue Jan 12 11:56:35 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Tue, 12 Jan 2021 19:56:35 +0300 Subject: [Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021 In-Reply-To: References: <20210107235337.GE26362@laptop.org> Message-ID: You might be interested in https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone . You may go through each step before submitting your Pull Request. On 1/12/21 7:52 PM, Kunal Tulsidasani wrote: > should test my code (Procedure) after making commits before making any > pull requests? > -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x1007816766D390D7.asc Type: application/pgp-keys Size: 4849 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From tulsidasanikunal at gmail.com Tue Jan 12 12:08:28 2021 From: tulsidasanikunal at gmail.com (Kunal Tulsidasani) Date: Tue, 12 Jan 2021 22:38:28 +0530 Subject: [Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021 In-Reply-To: References: <20210107235337.GE26362@laptop.org> Message-ID: Thankyou for your reply! I have read this file and this shows on what bases to check! I want to know how to check? Like what should I do? Regards Kunal On Tue, 12 Jan 2021, 22:26 Srevin Saju, wrote: > You might be interested in > > https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone > . You may go through each step before submitting your Pull Request. > > On 1/12/21 7:52 PM, Kunal Tulsidasani wrote: > > should test my code (Procedure) after making commits before making any > > pull requests? > > > -- > Srevin Saju > https://srevinsaju.me > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From srevinsaju at sugarlabs.org Tue Jan 12 12:19:51 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Tue, 12 Jan 2021 20:19:51 +0300 Subject: [Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021 In-Reply-To: References: <20210107235337.GE26362@laptop.org> Message-ID: <03210bea-dc1a-da05-d9fc-9826b730b5df@sugarlabs.org> It would be quite complicated to explain what to check. We would be able to explain better if you could send a draft Pull Request and ping me there. Some basic ways to test, common to all activities / sugar / any FOSS software would be to: 1. Clone the source, checkout master 2. Login to Sugar 3. Run the software / activity : (in sugar, it would be to run `python setup.py install` or `python setup.py dev`, click on the activity's icon on the Sugar Home view 4. Make your changes, GOTO STEP 2 and repeat those with your new changes. 5. Finally, push your changes when you are satisfied. 6. Have fun. On 1/12/21 8:08 PM, Kunal Tulsidasani wrote: > Thankyou for your?reply! > > I have read this file and this shows on what bases to check! > > I want to know how to check? Like what should I do? > > Regards > Kunal > > On Tue, 12 Jan 2021, 22:26 Srevin Saju, > wrote: > > You might be interested in > https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone > > > . You may go through each step before submitting your Pull Request. > > On 1/12/21 7:52 PM, Kunal Tulsidasani wrote: > > should test my code (Procedure) after making commits before > making any > > pull requests? > > > -- > Srevin Saju > https://srevinsaju.me > -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x1007816766D390D7.asc Type: application/pgp-keys Size: 4849 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From quozl at laptop.org Tue Jan 12 15:43:49 2021 From: quozl at laptop.org (James Cameron) Date: Wed, 13 Jan 2021 07:43:49 +1100 Subject: [Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021 In-Reply-To: <03210bea-dc1a-da05-d9fc-9826b730b5df@sugarlabs.org> References: <20210107235337.GE26362@laptop.org> <03210bea-dc1a-da05-d9fc-9826b730b5df@sugarlabs.org> Message-ID: <20210112204349.GD17204@laptop.org> I agree, there is no simple explanation for how to test code, as it depends exactly on where the change is made. However, I'm surprised if one would ever reach the point of having to test a change without knowing how to run the program that you are about to change. That would be very much going forward blindly. On Tue, Jan 12, 2021 at 08:19:51PM +0300, Srevin Saju wrote: > It would be quite complicated to explain what to check. We would be able to > explain better if you could send a draft Pull Request and ping me there. > > Some basic ways to test, common to all activities / sugar / any FOSS > software would be to: > > 1. Clone the source, checkout master > 2. Login to Sugar > 3. Run the software / activity : (in sugar, it would be to run `python > setup.py install` or `python setup.py dev`, click on the activity's > icon on the Sugar Home view > 4. Make your changes, GOTO STEP 2 and repeat those with your new changes. > 5. Finally, push your changes when you are satisfied. > 6. Have fun. > > On 1/12/21 8:08 PM, Kunal Tulsidasani wrote: > > Thankyou for your?reply! > > > > I have read this file and this shows on what bases to check! > > > > I want to know how to check? Like what should I do? > > > > Regards > > Kunal > > > > On Tue, 12 Jan 2021, 22:26 Srevin Saju, > > wrote: > > > > You might be interested in > > https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone > > > > > > . You may go through each step before submitting your Pull Request. > > > > On 1/12/21 7:52 PM, Kunal Tulsidasani wrote: > > > should test my code (Procedure) after making commits before > > making any > > > pull requests? > > > > > -- Srevin Saju > > https://srevinsaju.me > > > -- > Srevin Saju > https://srevinsaju.me > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > sub RSA 4096/14479587 2020-05-19 > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From ibiamchihurumnaya at gmail.com Wed Jan 13 05:38:48 2021 From: ibiamchihurumnaya at gmail.com (Chihurumnaya Ibiam) Date: Wed, 13 Jan 2021 11:38:48 +0100 Subject: [Sugar-devel] SOAS 33/34 Changes. In-Reply-To: References: Message-ID: Edit made, changes can be viewed in the SoaS download page . -- Ibiam Chihurumnaya ibiamchihurumnaya at gmail.com On Mon, Jan 11, 2021 at 7:07 PM Peter Robinson wrote: > On Mon, Jan 11, 2021 at 4:56 PM Chihurumnaya Ibiam > wrote: > > > > Hi Everyone, > > > > SOAS was failing to build in F34 due to telepathy-salut being deprecated > and needed as a dependency in sugar, F33 beta had an issue where startup > goes straight to login. > > > > Both have been fixed after today's compose was released and can be > tested. > > Download here. > > > > I don't think it's wise to change the download link in our wiki to > reflect this - uploaded to sunjammer of course - as it's a compose image > but Peter can tell if it's wise to. > > The link is for rawhide which is the nightly development snapshots, it > might be worthwhile putting a link for those interested in testing > that to know the state of SoAS for the next release and be able to > test issues with it and provide fixes, there's also an arm nightly > image too. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aperez at alexperez.com Wed Jan 13 21:17:42 2021 From: aperez at alexperez.com (Alex Perez) Date: Wed, 13 Jan 2021 18:17:42 -0800 Subject: [Sugar-devel] [SoaS] SOAS 33/34 Changes. In-Reply-To: References: Message-ID: I tested today's nightly rawhide of SoaS, and can confirm it behaves as expected/desired, with session auto-login. All activities start _except_ FotoToon. Downloaded from?https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210113.n.0/compose/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-Rawhide-20210113.n.0.iso SoaS raw-xz for armhfp (Raspberry Pi, etc) image at?https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210113.n.0/compose/Spins/armhfp/images/Fedora-SoaS-armhfp-Rawhide-20210113.n.0-sda.raw.xz On 1/13/2021 2:39:25 AM, Chihurumnaya Ibiam wrote: Edit made, changes can be viewed in the SoaS download page [https://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Downloads]. -- Ibiam Chihurumnaya ibiamchihurumnaya at gmail.com [mailto:ibiamchihurumnaya at gmail.com] On Mon, Jan 11, 2021 at 7:07 PM Peter Robinson wrote: On Mon, Jan 11, 2021 at 4:56 PM Chihurumnaya Ibiam wrote: > > Hi Everyone, > > SOAS was failing to build in F34 due to telepathy-salut being deprecated and needed as a dependency in sugar, F33 beta had an issue where startup goes straight to login. > > Both have been fixed after today's compose was released and can be tested. > Download here. > > I don't think it's wise to change the download link in our wiki to reflect this - uploaded to sunjammer of course - as it's a compose image but Peter can tell if it's wise to. The link is for rawhide which is the nightly development snapshots, it might be worthwhile putting a link for those interested in testing that to know the state of SoAS for the next release and be able to test issues with it and provide fixes, there's also an arm? nightly image too. _______________________________________________ SoaS mailing list SoaS at lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Wed Jan 13 21:28:32 2021 From: quozl at laptop.org (James Cameron) Date: Thu, 14 Jan 2021 13:28:32 +1100 Subject: [Sugar-devel] [SoaS] SOAS 33/34 Changes. In-Reply-To: References: Message-ID: <20210114022832.GA27652@laptop.org> Thanks for testing! On Wed, Jan 13, 2021 at 06:17:42PM -0800, Alex Perez wrote: > I tested today's nightly rawhide of SoaS, and can confirm it behaves as > expected/desired, with session auto-login. All activities start _except_ > FotoToon. > > Downloaded from https://kojipkgs.fedoraproject.org/compose/rawhide/ > Fedora-Rawhide-20210113.n.0/compose/Spins/x86_64/iso/ > Fedora-SoaS-Live-x86_64-Rawhide-20210113.n.0.iso > > SoaS raw-xz for armhfp (Raspberry Pi, etc) image at https:// > kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210113.n.0/compose/ > Spins/armhfp/images/Fedora-SoaS-armhfp-Rawhide-20210113.n.0-sda.raw.xz > > On 1/13/2021 2:39:25 AM, Chihurumnaya Ibiam > wrote: > > Edit made, changes can be viewed in the [1]SoaS download page. > > -- > > Ibiam Chihurumnaya > [2]ibiamchihurumnaya at gmail.com > > > > On Mon, Jan 11, 2021 at 7:07 PM Peter Robinson <[3]pbrobinson at gmail.com> > wrote: > > On Mon, Jan 11, 2021 at 4:56 PM Chihurumnaya Ibiam > <[4]ibiamchihurumnaya at gmail.com> wrote: > > > > Hi Everyone, > > > > SOAS was failing to build in F34 due to telepathy-salut being > deprecated and needed as a dependency in sugar, F33 beta had an issue > where startup goes straight to login. > > > > Both have been fixed after today's compose was released and can be > tested. > > Download here. > > > > I don't think it's wise to change the download link in our wiki to > reflect this - uploaded to sunjammer of course - as it's a compose > image but Peter can tell if it's wise to. > > The link is for rawhide which is the nightly development snapshots, it > might be worthwhile putting a link for those interested in testing > that to know the state of SoAS for the next release and be able to > test issues with it and provide fixes, there's also an arm nightly > image too. > > _______________________________________________ SoaS mailing list > SoaS at lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas > > References: > > [1] https://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Downloads > [2] mailto:ibiamchihurumnaya at gmail.com > [3] mailto:pbrobinson at gmail.com > [4] mailto:ibiamchihurumnaya at gmail.com > _______________________________________________ > SoaS mailing list > SoaS at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/soas -- James Cameron https://quozl.linux.org.au/ From ibiamchihurumnaya at gmail.com Thu Jan 14 07:03:24 2021 From: ibiamchihurumnaya at gmail.com (Chihurumnaya Ibiam) Date: Thu, 14 Jan 2021 13:03:24 +0100 Subject: [Sugar-devel] [SoaS] SOAS 33/34 Changes. In-Reply-To: References: Message-ID: Thanks for testing, can you share a log of the activity after it fails to start? -- Ibiam Chihurumnaya ibiamchihurumnaya at gmail.com On Thu, Jan 14, 2021 at 3:17 AM Alex Perez wrote: > I tested today's nightly rawhide of SoaS, and can confirm it behaves as > expected/desired, with session auto-login. All activities start _except_ > FotoToon. > > Downloaded from > https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210113.n.0/compose/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-Rawhide-20210113.n.0.iso > > SoaS raw-xz for armhfp (Raspberry Pi, etc) image at > https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210113.n.0/compose/Spins/armhfp/images/Fedora-SoaS-armhfp-Rawhide-20210113.n.0-sda.raw.xz > > On 1/13/2021 2:39:25 AM, Chihurumnaya Ibiam > wrote: > Edit made, changes can be viewed in the SoaS download page > . > > -- > > Ibiam Chihurumnaya > ibiamchihurumnaya at gmail.com > > > > On Mon, Jan 11, 2021 at 7:07 PM Peter Robinson > wrote: > >> On Mon, Jan 11, 2021 at 4:56 PM Chihurumnaya Ibiam >> wrote: >> > >> > Hi Everyone, >> > >> > SOAS was failing to build in F34 due to telepathy-salut being >> deprecated and needed as a dependency in sugar, F33 beta had an issue where >> startup goes straight to login. >> > >> > Both have been fixed after today's compose was released and can be >> tested. >> > Download here. >> > >> > I don't think it's wise to change the download link in our wiki to >> reflect this - uploaded to sunjammer of course - as it's a compose image >> but Peter can tell if it's wise to. >> >> The link is for rawhide which is the nightly development snapshots, it >> might be worthwhile putting a link for those interested in testing >> that to know the state of SoAS for the next release and be able to >> test issues with it and provide fixes, there's also an arm nightly >> image too. >> > _______________________________________________ SoaS mailing list > SoaS at lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas > > _______________________________________________ > SoaS mailing list > SoaS at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/soas > -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Fri Jan 15 02:50:55 2021 From: quozl at laptop.org (James Cameron) Date: Fri, 15 Jan 2021 18:50:55 +1100 Subject: [Sugar-devel] GSoC 2021 Ideas Message-ID: <20210115075055.GA17244@laptop.org> We need ideas for GSoC this year. Let's get started. Change from last year; projects are 175 hours rather than 350 hours. Use ideas from previous years, or make new ideas. Make a new Ideas-2021.md file in our repository https://github.com/sugarlabs/GSoC using a pull request. File README.md also needs a few changes. You can read the commit history of changes to the file to see what changed last year. Applications by organisations are from 29th January to 19th February. Organisation administrators this year are Jui, Perrie and Lionel. -- James Cameron https://quozl.linux.org.au/ From juipradhan2k at gmail.com Fri Jan 15 08:31:41 2021 From: juipradhan2k at gmail.com (Jui Pradhan) Date: Fri, 15 Jan 2021 19:01:41 +0530 Subject: [Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021 In-Reply-To: <20210112204349.GD17204@laptop.org> References: <20210107235337.GE26362@laptop.org> <03210bea-dc1a-da05-d9fc-9826b730b5df@sugarlabs.org> <20210112204349.GD17204@laptop.org> Message-ID: Hi, I will try to list the few ways I use to test. Also whichever way you use, I recommend mentioning it briefly in your commit messages. Check the log files after changes. Log files contain tracebacks.... - for activities see `~/.sugar/default/logs/activity_bundle_id.log` - for sugar refer to the logs `~/.sugar/default/logs/shell.log` - you may make changes to a source repository clone in /usr/src/sugar of Sugar Live Build and then run autogen, "make", and "make install". However, there are other things you need to take care of. Refer to: https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md Making changes to the Sugar Activities: Before you make any changes to the source code it is imperative to know how the activity works without these changes. While testing lookout for: - Your code does not make an unintentional change. By that I mean in the process of solving one issue, you do not create another. - Design tests and iterate until the tests have sufficient coverage for the code changes. As Srevin and James mentioned, there can be more to testing depending on what part of code you are working on. I hope our emails help. Regards, Jui On Wed, Jan 13, 2021 at 2:14 AM James Cameron wrote: > I agree, there is no simple explanation for how to test code, as it > depends exactly on where the change is made. > > However, I'm surprised if one would ever reach the point of having to > test a change without knowing how to run the program that you are > about to change. That would be very much going forward blindly. > > On Tue, Jan 12, 2021 at 08:19:51PM +0300, Srevin Saju wrote: > > It would be quite complicated to explain what to check. We would be able > to > > explain better if you could send a draft Pull Request and ping me there. > > > > Some basic ways to test, common to all activities / sugar / any FOSS > > software would be to: > > > > 1. Clone the source, checkout master > > 2. Login to Sugar > > 3. Run the software / activity : (in sugar, it would be to run `python > > setup.py install` or `python setup.py dev`, click on the activity's > > icon on the Sugar Home view > > 4. Make your changes, GOTO STEP 2 and repeat those with your new changes. > > 5. Finally, push your changes when you are satisfied. > > 6. Have fun. > > > > On 1/12/21 8:08 PM, Kunal Tulsidasani wrote: > > > Thankyou for your reply! > > > > > > I have read this file and this shows on what bases to check! > > > > > > I want to know how to check? Like what should I do? > > > > > > Regards > > > Kunal > > > > > > On Tue, 12 Jan 2021, 22:26 Srevin Saju, > > > wrote: > > > > > > You might be interested in > > > > https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone > > > < > https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone > > > > > > > > . You may go through each step before submitting your Pull Request. > > > > > > On 1/12/21 7:52 PM, Kunal Tulsidasani wrote: > > > > should test my code (Procedure) after making commits before > > > making any > > > > pull requests? > > > > > > > -- Srevin Saju > > > https://srevinsaju.me > > > > > -- > > Srevin Saju > > https://srevinsaju.me > > > > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) < > srevinsaju at sugarlabs.org> > > sub RSA 4096/14479587 2020-05-19 > > > > > > > > _______________________________________________ > > Sugar-devel mailing list > > Sugar-devel at lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > -- > James Cameron > https://quozl.linux.org.au/ > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Jui Pradhan -------------- next part -------------- An HTML attachment was scrubbed... URL: From aperez at alexperez.com Sun Jan 17 17:03:10 2021 From: aperez at alexperez.com (Alex Perez) Date: Sun, 17 Jan 2021 14:03:10 -0800 Subject: [Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware Message-ID: <6a3129ef-1bee-f2c5-e971-85319743a8a0@alexperez.com> James, I booted up the latest Sugar-live-build image, which I'd downloaded from http://people.sugarlabs.org/~quozl/sugar-live-build/ and written to a USB stick, and booted it up in an HP-branded terminal from ~2012, which works perfectly fine with the latest Fedora SoaS images. During early boot, the kernel printed a message which stated, "drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesetting for R600 or later requires firmware installed." followed by a line which said "See http://wiki.debian.org/Firmware for information about missing firmware" Furthermore, Xorg also fails to subsequently initialize in the fallback fbdev mode, with Xorg reporting "Cannot run in framebuffer omde. Please specify busIDs for all framebuffer devices", resulting in the machine sitting at a Linux console forever. Simply bundling the 'firmware-amd-graphics' package from the firmware-nonfree repo when you build the Live image would mean the image would work correctly on a vastly larger amount of hardware, out of the box. I would encourage you to take it one step further, and bundle the firmware-linux-nonfree metapackage, which will include firmware for things like Marvell wireless cards, Intel wireless cards, Atheros wireless cards (both USB and integrated/PCI/PCIe) Thanks, Alex Perez From quozl at laptop.org Sun Jan 17 17:13:47 2021 From: quozl at laptop.org (James Cameron) Date: Mon, 18 Jan 2021 09:13:47 +1100 Subject: [Sugar-devel] [SoaS] Sugar-starchart, flipsticks, labyrinth in Fedora Rawhide fails to install due to no python3 activity port In-Reply-To: <93b60437-ac68-a54a-073c-a6e418f8c642@alexperez.com> References: <93b60437-ac68-a54a-073c-a6e418f8c642@alexperez.com> Message-ID: <20210117221347.GC11162@laptop.org> Thanks for testing. For StarChart, the latest release is for Python 2. Work on a port to Python 3 was begun but not completed. https://github.com/sugarlabs/starchart/pull/8 For Flip Sticks, the latest release is for Python 3, but Fedora project is not yet packaging that release. I suggest upgrading to v14. For Labyrinth, the latest release is for GTK 2 and Python 2. The upstream project says nobody is maintaining it, but there has been recent work this year on a port to GTK 3. https://github.com/labyrinth-team/labyrinth/tree/gtk3 As this situation goes beyond SoaS, I've CC'd sugar-devel@ in case any developers there wish to get involved. I suggest you might like to do the same. On Sun, Jan 17, 2021 at 12:51:48PM -0800, Alex Perez wrote: > Ibiam, > > As of tonight's latest nightly build, sugar-starchart will not install, due > to the missing python2 toolkit dependency. Are you planning on fixing this > prior to the release of Fedora 34, which would need to be in the next week > or two? > > > All of the above activities fail to install for the same reason: the missing > python2 sugar toolkit dependency: > > * sugar-flipsticks > * sugar-labyrinth > * sugar-starchart > > DNF fails with: > > ?Problem: conflicting requests > ? - nothing provides sugar-toolkit needed by > sugar-starchart-16-12.fc31.noarch > (try to add '--skip-broken' to skip uninstallable packages) > > Additionally, sugar-distance and sugar-fototoon will install, but does not > execute properly. Given that sugar-distance doesn't actually work properly > with non-XO laptpos, I strongly recommend we retire the package, and remove > it entirely from Rawhide, so it will be properly gone in F34. The same goes > for the other activities above, if we don't expect to fix them in the next > week or two. > > Regards, > Alex Perez > _______________________________________________ > SoaS mailing list > SoaS at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/soas -- James Cameron https://quozl.linux.org.au/ From quozl at laptop.org Sun Jan 17 17:16:22 2021 From: quozl at laptop.org (James Cameron) Date: Mon, 18 Jan 2021 09:16:22 +1100 Subject: [Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware In-Reply-To: <6a3129ef-1bee-f2c5-e971-85319743a8a0@alexperez.com> References: <6a3129ef-1bee-f2c5-e971-85319743a8a0@alexperez.com> Message-ID: <20210117221622.GD11162@laptop.org> On Sun, Jan 17, 2021 at 02:03:10PM -0800, Alex Perez wrote: > James, > > I booted up the latest Sugar-live-build image, which I'd downloaded from > http://people.sugarlabs.org/~quozl/sugar-live-build/ and written to a USB > stick, and booted it up in an HP-branded terminal from ~2012, which works > perfectly fine with the latest Fedora SoaS images. Thanks for testing. > During early boot, the kernel printed a message which stated, > "drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesetting for R600 > or later requires firmware installed." followed by a line which said "See > http://wiki.debian.org/Firmware for information about missing firmware" > > Furthermore, Xorg also fails to subsequently initialize in the fallback > fbdev mode, with Xorg reporting "Cannot run in framebuffer omde. Please > specify busIDs for all framebuffer devices", resulting in the machine > sitting at a Linux console forever. > > Simply bundling the 'firmware-amd-graphics' package from the > firmware-nonfree repo when you build the Live image would mean the image > would work correctly on a vastly larger amount of hardware, out of the box. > > I would encourage you to take it one step further, and bundle the > firmware-linux-nonfree metapackage, which will include firmware for things > like Marvell wireless cards, Intel wireless cards, Atheros wireless cards > (both USB and integrated/PCI/PCIe) How will Sugar Labs comply with the licenses of these firmwares? -- James Cameron https://quozl.linux.org.au/ From aperez at alexperez.com Sun Jan 17 19:56:06 2021 From: aperez at alexperez.com (Alex Perez) Date: Sun, 17 Jan 2021 16:56:06 -0800 Subject: [Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware In-Reply-To: <20210117221622.GD11162@laptop.org> References: <6a3129ef-1bee-f2c5-e971-85319743a8a0@alexperez.com> <20210117221622.GD11162@laptop.org> Message-ID: <4e8bd410-1415-af5b-47a9-e468ff649b5c@alexperez.com> Answers inline James Cameron wrote on 1/17/2021 2:16 PM: > On Sun, Jan 17, 2021 at 02:03:10PM -0800, Alex Perez wrote: >> James, >> >> I booted up the latest Sugar-live-build image, which I'd downloaded from >> http://people.sugarlabs.org/~quozl/sugar-live-build/ and written to a USB >> stick, and booted it up in an HP-branded terminal from ~2012, which works >> perfectly fine with the latest Fedora SoaS images. > Thanks for testing. > >> Simply bundling the 'firmware-amd-graphics' package from the >> firmware-nonfree repo when you build the Live image would mean the image >> would work correctly on a vastly larger amount of hardware, out of the box. >> >> I would encourage you to take it one step further, and bundle the >> firmware-linux-nonfree metapackage, which will include firmware for things >> like Marvell wireless cards, Intel wireless cards, Atheros wireless cards >> (both USB and integrated/PCI/PCIe) > How will Sugar Labs comply with the licenses of these firmwares? > I'm afraid I don't understand what the concern is here. "Sugar" isn't subject to anything different from a licensing perspective, and therefore under no obligation to "comply" with anything: https://opensource.stackexchange.com/questions/8849/does-distributing-gpl-software-along-with-binary-image-force-the-binary-image-to All of the firmware images packaged by Debian in the non-free repo is freely redistributable, but not open-source. Fedora packages them, and includes them by default. Their LiveCDs/images work out of the box with them. Debian packages them, but does not install them by default, presumably out of ideological reticence. Since the goal of the Debian Sugar LiveCD should be to work, transparently, on as many computers out-of-the-box as is possible, this would seemingly be an obvious improvement. It's not possible to install from this LiveCD on a ton of "modern" hardware (the machine I'm using is from 2011) with the current state of bundled packages. If the goal is to only allow it to function fully on machines which are incapable of functioning fully without binary firmware blobs, I'd argue that this should be disclosed during the installation process. From walter.bender at gmail.com Sun Jan 17 20:54:33 2021 From: walter.bender at gmail.com (Walter Bender) Date: Sun, 17 Jan 2021 20:54:33 -0500 Subject: [Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware In-Reply-To: <4e8bd410-1415-af5b-47a9-e468ff649b5c@alexperez.com> References: <6a3129ef-1bee-f2c5-e971-85319743a8a0@alexperez.com> <20210117221622.GD11162@laptop.org> <4e8bd410-1415-af5b-47a9-e468ff649b5c@alexperez.com> Message-ID: Maybe we can distribute a free and a nonfree version? More work but not so much On Sun, Jan 17, 2021, 7:56 PM Alex Perez wrote: > Answers inline > > James Cameron wrote on 1/17/2021 2:16 PM: > > On Sun, Jan 17, 2021 at 02:03:10PM -0800, Alex Perez wrote: > >> James, > >> > >> I booted up the latest Sugar-live-build image, which I'd downloaded from > >> http://people.sugarlabs.org/~quozl/sugar-live-build/ and written to a > USB > >> stick, and booted it up in an HP-branded terminal from ~2012, which > works > >> perfectly fine with the latest Fedora SoaS images. > > Thanks for testing. > > > >> Simply bundling the 'firmware-amd-graphics' package from the > >> firmware-nonfree repo when you build the Live image would mean the image > >> would work correctly on a vastly larger amount of hardware, out of the > box. > >> > >> I would encourage you to take it one step further, and bundle the > >> firmware-linux-nonfree metapackage, which will include firmware for > things > >> like Marvell wireless cards, Intel wireless cards, Atheros wireless > cards > >> (both USB and integrated/PCI/PCIe) > > How will Sugar Labs comply with the licenses of these firmwares? > > > I'm afraid I don't understand what the concern is here. "Sugar" isn't > subject to anything different from a licensing perspective, and > therefore under no obligation to "comply" with anything: > > > https://opensource.stackexchange.com/questions/8849/does-distributing-gpl-software-along-with-binary-image-force-the-binary-image-to > > All of the firmware images packaged by Debian in the non-free repo is > freely redistributable, but not open-source. > > Fedora packages them, and includes them by default. Their LiveCDs/images > work out of the box with them. Debian packages them, but does not > install them by default, presumably out of ideological reticence. > > Since the goal of the Debian Sugar LiveCD should be to work, > transparently, on as many computers out-of-the-box as is possible, this > would seemingly be an obvious improvement. It's not possible to install > from this LiveCD on a ton of "modern" hardware (the machine I'm using is > from 2011) with the current state of bundled packages. If the goal is to > only allow it to function fully on machines which are incapable of > functioning fully without binary firmware blobs, I'd argue that this > should be disclosed during the installation process. > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Sun Jan 17 21:12:12 2021 From: quozl at laptop.org (James Cameron) Date: Mon, 18 Jan 2021 13:12:12 +1100 Subject: [Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware In-Reply-To: <4e8bd410-1415-af5b-47a9-e468ff649b5c@alexperez.com> References: <6a3129ef-1bee-f2c5-e971-85319743a8a0@alexperez.com> <20210117221622.GD11162@laptop.org> <4e8bd410-1415-af5b-47a9-e468ff649b5c@alexperez.com> Message-ID: <20210118021212.GJ11162@laptop.org> On Sun, Jan 17, 2021 at 04:56:06PM -0800, Alex Perez wrote: > Answers inline Thanks. Me too. > James Cameron wrote on 1/17/2021 2:16 PM: > > On Sun, Jan 17, 2021 at 02:03:10PM -0800, Alex Perez wrote: > > > James, > > > > > > I booted up the latest Sugar-live-build image, which I'd > > > downloaded from > > > http://people.sugarlabs.org/~quozl/sugar-live-build/ and written > > > to a USB stick, and booted it up in an HP-branded terminal from > > > ~2012, which works perfectly fine with the latest Fedora SoaS > > > images. > > Thanks for testing. > > > > > Simply bundling the 'firmware-amd-graphics' package from the > > > firmware-nonfree repo when you build the Live image would mean > > > the image would work correctly on a vastly larger amount of > > > hardware, out of the box. > > > > > > I would encourage you to take it one step further, and bundle > > > the firmware-linux-nonfree metapackage, which will include > > > firmware for things like Marvell wireless cards, Intel wireless > > > cards, Atheros wireless cards (both USB and integrated/PCI/PCIe) > > How will Sugar Labs comply with the licenses of these firmwares? > > > I'm afraid I don't understand what the concern is here. Okay, putting it differently; if a developer acting on behalf of Sugar Labs distributes this firmware via Sugar Labs infrastructure, is this action protected in any way? > "Sugar" isn't subject to anything different from a licensing > perspective, and therefore under no obligation to "comply" with > anything: > > https://opensource.stackexchange.com/questions/8849/does-distributing-gpl-software-along-with-binary-image-force-the-binary-image-to > > All of the firmware images packaged by Debian in the non-free repo > is freely redistributable, but not open-source. Actually, https://www.debian.org/doc/debian-policy/ch-archive#s-non-free says "not compliant with DFSG", "encumbered by patents or other legal issues that make their distirbution problematic". I don't think they are freely redistributable. A next step is to review all the licenses of the packages you asked for. > Fedora packages them, and includes them by default. Their > LiveCDs/images work out of the box with them. Debian packages them, > but does not install them by default, presumably out of ideological > reticence. > > Since the goal of the Debian Sugar LiveCD Okay, that's a new name. I've been calling it Sugar Live Build. > should be to work, transparently, on as many computers > out-of-the-box as is possible, this would seemingly be an obvious > improvement. It can be a goal, but it was not my goal to begin with. My goal was to provide an environment for student developers who lacked the capacity to install Sugar in the fashion we had required, while bypassing the downstream distribution processes because we couldn't rely on downstream to be timely. > It's not possible to install from this LiveCD on a ton of "modern" > hardware (the machine I'm using is from 2011) with the current state > of bundled packages. If the goal is to only allow it to function > fully on machines which are incapable of functioning fully without > binary firmware blobs, I'd argue that this should be disclosed > during the installation process. It sounds like you share some of the same intentions as Martin Guy, who needed i386 support. He found what he needed with Trisquel. Have you tried that? -- James Cameron https://quozl.linux.org.au/ From aperez at alexperez.com Sun Jan 17 21:18:14 2021 From: aperez at alexperez.com (Alex Perez) Date: Sun, 17 Jan 2021 18:18:14 -0800 Subject: [Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware In-Reply-To: <20210118021212.GJ11162@laptop.org> References: <6a3129ef-1bee-f2c5-e971-85319743a8a0@alexperez.com> <20210117221622.GD11162@laptop.org> <4e8bd410-1415-af5b-47a9-e468ff649b5c@alexperez.com> <20210118021212.GJ11162@laptop.org> Message-ID: <987e80da-adb9-da7e-2d03-f3872c079a1b@alexperez.com> James Cameron wrote on 1/17/2021 6:12 PM: > It sounds like you share some of the same intentions as Martin Guy, > who needed i386 support. He found what he needed with Trisquel. Have > you tried that? No, I'm interested in running on x86_64, EFI-compliant hardware.? I have no need or desire for Trisquel. From quozl at laptop.org Sun Jan 17 22:03:36 2021 From: quozl at laptop.org (James Cameron) Date: Mon, 18 Jan 2021 14:03:36 +1100 Subject: [Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware In-Reply-To: <987e80da-adb9-da7e-2d03-f3872c079a1b@alexperez.com> References: <6a3129ef-1bee-f2c5-e971-85319743a8a0@alexperez.com> <20210117221622.GD11162@laptop.org> <4e8bd410-1415-af5b-47a9-e468ff649b5c@alexperez.com> <20210118021212.GJ11162@laptop.org> <987e80da-adb9-da7e-2d03-f3872c079a1b@alexperez.com> Message-ID: <20210118030336.GK11162@laptop.org> On Sun, Jan 17, 2021 at 06:18:14PM -0800, Alex Perez wrote: > James Cameron wrote on 1/17/2021 6:12 PM: > > It sounds like you share some of the same intentions as Martin Guy, > > who needed i386 support. He found what he needed with Trisquel. Have > > you tried that? > No, I'm interested in running on x86_64, EFI-compliant hardware.? I > have no need or desire for Trisquel. Thanks. That's my problem too; I'm not interested in i386, I'm not interested in Trisquel, in Fedora, or SoaS. In turn, because of how I'm funded. The situation reminds me of Jussi Pakkanen's talk at linux.conf.au about this time last year, where he described several open source project interations (iLN6wL7ExHU from 8:47 to 17:50), eventually concluding that "What does it say about the OSS community, if cooperating with people using something other than your chosen tool is seen as an act of desperation?" https://lca2020.linux.org.au/schedule/presentation/87/ My perspective is that expanding to include i386 or non-free packages is effectively a request to expand my scope of software maintenance, and that I should instead reduce complexity to reduce cost of maintenance. A more correct solution within this perspective is for you to use Fedora. -- James Cameron https://quozl.linux.org.au/ From juipradhan2k at gmail.com Mon Jan 18 03:55:56 2021 From: juipradhan2k at gmail.com (Jui Pradhan) Date: Mon, 18 Jan 2021 14:25:56 +0530 Subject: [Sugar-devel] GSoC 2021 Ideas In-Reply-To: <20210115075055.GA17244@laptop.org> References: <20210115075055.GA17244@laptop.org> Message-ID: Hi, We are yet to add Ideas-2021.md file. - Given a change in the number of hours this year, any suggestions on changes to last year's projects are welcome. - It would be great if people who are familiar with recent work on Sugarizer and Music Blocks could speak about the relevance of last year's project ideas. - My opinion on last year's projects for Sugar (accepted projects for GSoC 2020) : `Improve and maintain Sugar Activities` is still relevant however the number of activities can be reduced to 15 (we can discuss the number) `Port Sugar and core activities to Python 3` I think this is still relevant and does not require changes to last year's project. `Debian advocacy for Sugar` we should definitely keep this as long as there is someone willing to mentor. Thanks On Fri, Jan 15, 2021 at 1:21 PM James Cameron wrote: > We need ideas for GSoC this year. Let's get started. > > Change from last year; projects are 175 hours rather than 350 hours. > > Use ideas from previous years, or make new ideas. > > Make a new Ideas-2021.md file in our repository > https://github.com/sugarlabs/GSoC using a pull request. > > File README.md also needs a few changes. You can read the commit > history of changes to the file to see what changed last year. > > Applications by organisations are from 29th January to 19th February. > > Organisation administrators this year are Jui, Perrie and Lionel. > > -- > James Cameron > https://quozl.linux.org.au/ > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > Regards, -- Jui Pradhan -------------- next part -------------- An HTML attachment was scrubbed... URL: From 2017230 at iiitdmj.ac.in Mon Jan 18 04:16:00 2021 From: 2017230 at iiitdmj.ac.in (Saumya Mishra) Date: Mon, 18 Jan 2021 14:46:00 +0530 Subject: [Sugar-devel] GSoC 2021 Ideas In-Reply-To: References: <20210115075055.GA17244@laptop.org> Message-ID: Hi, Regarding `Port Sugar and core activities to Python 3` I think this is still relevant and does not require changes to last year's project. I also agree with Jui. As the number of hours is reduced, we can try to reduce the number of items given in the 'Project Task checklist'. As Port to Telepathy (https://github.com/orgs/sugarlabs/projects/4) here it shows it is almost completed except for one activity remaining, it requires minimal concern this year. Port to the latest sugargame and collabwrapper, Port to Python 3 requires major importance this year according to me. "Reviewing the Sugar source code changes that were made for porting to Python 3" is also essential to include in the task list. Thanks Saumya On Mon, Jan 18, 2021 at 2:26 PM Jui Pradhan wrote: > Hi, > We are yet to add Ideas-2021.md file. > > - Given a change in the number of hours this year, any suggestions on > changes to last year's projects are welcome. > > - It would be great if people who are familiar with recent work on > Sugarizer and Music Blocks could speak about the relevance of last year's > project ideas. > > - My opinion on last year's projects for Sugar (accepted projects for GSoC > 2020) : > `Improve and maintain Sugar Activities` is still relevant however the > number of activities can be reduced to 15 (we can discuss the number) > `Port Sugar and core activities to Python 3` I think this is still > relevant and does not require changes to last year's project. > `Debian advocacy for Sugar` we should definitely keep this as long as > there is someone willing to mentor. > > Thanks > > On Fri, Jan 15, 2021 at 1:21 PM James Cameron wrote: > >> We need ideas for GSoC this year. Let's get started. >> >> Change from last year; projects are 175 hours rather than 350 hours. >> >> Use ideas from previous years, or make new ideas. >> >> Make a new Ideas-2021.md file in our repository >> https://github.com/sugarlabs/GSoC using a pull request. >> >> File README.md also needs a few changes. You can read the commit >> history of changes to the file to see what changed last year. >> >> Applications by organisations are from 29th January to 19th February. >> >> Organisation administrators this year are Jui, Perrie and Lionel. >> >> -- >> James Cameron >> https://quozl.linux.org.au/ >> _______________________________________________ >> Sugar-devel mailing list >> Sugar-devel at lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > > Regards, > -- > Jui Pradhan > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Mon Jan 18 16:25:06 2021 From: quozl at laptop.org (James Cameron) Date: Tue, 19 Jan 2021 08:25:06 +1100 Subject: [Sugar-devel] GSoC 2021 Ideas In-Reply-To: References: <20210115075055.GA17244@laptop.org> Message-ID: <20210118212506.GA11912@laptop.org> The project task checklist is not a good source of information. There are 138 search results for "exec = sugar-activity ", and 173 for "from sugar.activity". Not all of these can be worked, but there's plenty of opportunity without looking beyond GitHub for sources. However, if we run out of GitHub sources that need work, we have Gitorious at git.sugarlabs.org, and bundles at activities.sugarlabs.org. I've an idea for a blockchain learning app, using an intentionally weak hash so as to avoid children depleting laptop batteries with mining. On Mon, Jan 18, 2021 at 02:46:00PM +0530, Saumya Mishra wrote: > Hi, > > Regarding `Port Sugar and core activities to Python 3` I think this is still > relevant and does not require changes to last year's project. > I also agree with Jui. As the number of hours is reduced, we can try to reduce > the number of items given in the 'Project Task checklist'. As Port to Telepathy > ([1]https://github.com/orgs/sugarlabs/projects/4) here it shows it is almost > completed except for one activity remaining, it requires minimal concern this > year. > Port to the latest sugargame and collabwrapper, Port to Python 3 requires major > importance this year according to me. "Reviewing the Sugar source code changes > that were made for porting to Python 3" is also essential to include in the > task list. > > Thanks > Saumya > > On Mon, Jan 18, 2021 at 2:26 PM Jui Pradhan <[2]juipradhan2k at gmail.com> wrote: > > Hi, > We are yet to add Ideas-2021.md file. > > - Given a change in the number of hours this year, any suggestions on > changes to last year's projects are welcome. > > - It would be great if people who are familiar with recent work on > Sugarizer and Music Blocks could speak about the relevance of last year's > project ideas. > > - My opinion on last year's projects for Sugar (accepted projects for GSoC > 2020) : > `Improve and maintain Sugar Activities` is still relevant however the > number of activities can be reduced to 15 (we can discuss the number) > `Port Sugar and core activities to Python 3` I think this is still relevant > and does not require changes to last year's project. > `Debian advocacy for Sugar` we should definitely keep this as long as there > is someone willing to mentor. > > Thanks > > On Fri, Jan 15, 2021 at 1:21 PM James Cameron <[3]quozl at laptop.org> wrote: > > We need ideas for GSoC this year.? Let's get started. > > Change from last year; projects are 175 hours rather than 350 hours. > > Use ideas from previous years, or make new ideas. > > Make a new Ideas-2021.md file in our repository > [4]https://github.com/sugarlabs/GSoC using a pull request. > > File README.md also needs a few changes.? You can read the commit > history of changes to the file to see what changed last year. > > Applications by organisations are from 29th January to 19th February. > > Organisation administrators this year are Jui, Perrie and Lionel. > > -- > James Cameron > [5]https://quozl.linux.org.au/ > _______________________________________________ > Sugar-devel mailing list > [6]Sugar-devel at lists.sugarlabs.org > [7]http://lists.sugarlabs.org/listinfo/sugar-devel > > Regards, > -- > Jui Pradhan > _______________________________________________ > Sugar-devel mailing list > [8]Sugar-devel at lists.sugarlabs.org > [9]http://lists.sugarlabs.org/listinfo/sugar-devel > > * > > References: > > [1] https://github.com/orgs/sugarlabs/projects/4 > [2] mailto:juipradhan2k at gmail.com > [3] mailto:quozl at laptop.org > [4] https://github.com/sugarlabs/GSoC > [5] https://quozl.linux.org.au/ > [6] mailto:Sugar-devel at lists.sugarlabs.org > [7] http://lists.sugarlabs.org/listinfo/sugar-devel > [8] mailto:Sugar-devel at lists.sugarlabs.org > [9] http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From srevinsaju at sugarlabs.org Mon Jan 18 16:28:05 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Tue, 19 Jan 2021 00:28:05 +0300 Subject: [Sugar-devel] GSoC 2021 Ideas In-Reply-To: <20210118212506.GA11912@laptop.org> References: <20210115075055.GA17244@laptop.org> <20210118212506.GA11912@laptop.org> Message-ID: <5dd79a41-59e7-8ebb-5d41-8db875dcd2a2@sugarlabs.org> Another idea would be an email client for Sugar, I dunno if one exists. The last I could find was "sweetmail" iirc from git.sugarlabs.org On 1/19/21 12:25 AM, James Cameron wrote: > The project task checklist is not a good source of information. > > There are 138 search results for "exec = sugar-activity ", and 173 for > "from sugar.activity". Not all of these can be worked, but there's > plenty of opportunity without looking beyond GitHub for sources. > > However, if we run out of GitHub sources that need work, we have > Gitorious at git.sugarlabs.org, and bundles at > activities.sugarlabs.org. > > I've an idea for a blockchain learning app, using an intentionally > weak hash so as to avoid children depleting laptop batteries with > mining. > > On Mon, Jan 18, 2021 at 02:46:00PM +0530, Saumya Mishra wrote: >> Hi, >> >> Regarding `Port Sugar and core activities to Python 3` I think this is still >> relevant and does not require changes to last year's project. >> I also agree with Jui. As the number of hours is reduced, we can try to reduce >> the number of items given in the 'Project Task checklist'. As Port to Telepathy >> ([1]https://github.com/orgs/sugarlabs/projects/4) here it shows it is almost >> completed except for one activity remaining, it requires minimal concern this >> year. >> Port to the latest sugargame and collabwrapper, Port to Python 3 requires major >> importance this year according to me. "Reviewing the Sugar source code changes >> that were made for porting to Python 3" is also essential to include in the >> task list. >> >> Thanks >> Saumya >> >> On Mon, Jan 18, 2021 at 2:26 PM Jui Pradhan <[2]juipradhan2k at gmail.com> wrote: >> >> Hi, >> We are yet to add Ideas-2021.md file. >> >> - Given a change in the number of hours this year, any suggestions on >> changes to last year's projects are welcome. >> >> - It would be great if people who are familiar with recent work on >> Sugarizer and Music Blocks could speak about the relevance of last year's >> project ideas. >> >> - My opinion on last year's projects for Sugar (accepted projects for GSoC >> 2020) : >> `Improve and maintain Sugar Activities` is still relevant however the >> number of activities can be reduced to 15 (we can discuss the number) >> `Port Sugar and core activities to Python 3` I think this is still relevant >> and does not require changes to last year's project. >> `Debian advocacy for Sugar` we should definitely keep this as long as there >> is someone willing to mentor. >> >> Thanks >> >> On Fri, Jan 15, 2021 at 1:21 PM James Cameron <[3]quozl at laptop.org> wrote: >> >> We need ideas for GSoC this year.? Let's get started. >> >> Change from last year; projects are 175 hours rather than 350 hours. >> >> Use ideas from previous years, or make new ideas. >> >> Make a new Ideas-2021.md file in our repository >> [4]https://github.com/sugarlabs/GSoC using a pull request. >> >> File README.md also needs a few changes.? You can read the commit >> history of changes to the file to see what changed last year. >> >> Applications by organisations are from 29th January to 19th February. >> >> Organisation administrators this year are Jui, Perrie and Lionel. >> >> -- >> James Cameron >> [5]https://quozl.linux.org.au/ >> _______________________________________________ >> Sugar-devel mailing list >> [6]Sugar-devel at lists.sugarlabs.org >> [7]http://lists.sugarlabs.org/listinfo/sugar-devel >> >> Regards, >> -- >> Jui Pradhan >> _______________________________________________ >> Sugar-devel mailing list >> [8]Sugar-devel at lists.sugarlabs.org >> [9]http://lists.sugarlabs.org/listinfo/sugar-devel >> >> * >> >> References: >> >> [1] https://github.com/orgs/sugarlabs/projects/4 >> [2] mailto:juipradhan2k at gmail.com >> [3] mailto:quozl at laptop.org >> [4] https://github.com/sugarlabs/GSoC >> [5] https://quozl.linux.org.au/ >> [6] mailto:Sugar-devel at lists.sugarlabs.org >> [7] http://lists.sugarlabs.org/listinfo/sugar-devel >> [8] mailto:Sugar-devel at lists.sugarlabs.org >> [9] http://lists.sugarlabs.org/listinfo/sugar-devel -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x1007816766D390D7.asc Type: application/pgp-keys Size: 4849 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From ibiamchihurumnaya at gmail.com Tue Jan 19 20:23:18 2021 From: ibiamchihurumnaya at gmail.com (Chihurumnaya Ibiam) Date: Wed, 20 Jan 2021 02:23:18 +0100 Subject: [Sugar-devel] GSoC 2021 Ideas In-Reply-To: <20210118212506.GA11912@laptop.org> References: <20210115075055.GA17244@laptop.org> <20210118212506.GA11912@laptop.org> Message-ID: The blockchain learning app sounds like a good idea. -- Ibiam Chihurumnaya ibiamchihurumnaya at gmail.com On Mon, Jan 18, 2021 at 10:25 PM James Cameron wrote: > The project task checklist is not a good source of information. > > There are 138 search results for "exec = sugar-activity ", and 173 for > "from sugar.activity". Not all of these can be worked, but there's > plenty of opportunity without looking beyond GitHub for sources. > > However, if we run out of GitHub sources that need work, we have > Gitorious at git.sugarlabs.org, and bundles at > activities.sugarlabs.org. > > I've an idea for a blockchain learning app, using an intentionally > weak hash so as to avoid children depleting laptop batteries with > mining. > > On Mon, Jan 18, 2021 at 02:46:00PM +0530, Saumya Mishra wrote: > > Hi, > > > > Regarding `Port Sugar and core activities to Python 3` I think this is > still > > relevant and does not require changes to last year's project. > > I also agree with Jui. As the number of hours is reduced, we can try to > reduce > > the number of items given in the 'Project Task checklist'. As Port to > Telepathy > > ([1]https://github.com/orgs/sugarlabs/projects/4) here it shows it is > almost > > completed except for one activity remaining, it requires minimal concern > this > > year. > > Port to the latest sugargame and collabwrapper, Port to Python 3 > requires major > > importance this year according to me. "Reviewing the Sugar source code > changes > > that were made for porting to Python 3" is also essential to include in > the > > task list. > > > > Thanks > > Saumya > > > > On Mon, Jan 18, 2021 at 2:26 PM Jui Pradhan <[2]juipradhan2k at gmail.com> > wrote: > > > > Hi, > > We are yet to add Ideas-2021.md file. > > > > - Given a change in the number of hours this year, any suggestions on > > changes to last year's projects are welcome. > > > > - It would be great if people who are familiar with recent work on > > Sugarizer and Music Blocks could speak about the relevance of last > year's > > project ideas. > > > > - My opinion on last year's projects for Sugar (accepted projects > for GSoC > > 2020) : > > `Improve and maintain Sugar Activities` is still relevant however the > > number of activities can be reduced to 15 (we can discuss the number) > > `Port Sugar and core activities to Python 3` I think this is still > relevant > > and does not require changes to last year's project. > > `Debian advocacy for Sugar` we should definitely keep this as long > as there > > is someone willing to mentor. > > > > Thanks > > > > On Fri, Jan 15, 2021 at 1:21 PM James Cameron <[3]quozl at laptop.org> > wrote: > > > > We need ideas for GSoC this year. Let's get started. > > > > Change from last year; projects are 175 hours rather than 350 > hours. > > > > Use ideas from previous years, or make new ideas. > > > > Make a new Ideas-2021.md file in our repository > > [4]https://github.com/sugarlabs/GSoC using a pull request. > > > > File README.md also needs a few changes. You can read the commit > > history of changes to the file to see what changed last year. > > > > Applications by organisations are from 29th January to 19th > February. > > > > Organisation administrators this year are Jui, Perrie and Lionel. > > > > -- > > James Cameron > > [5]https://quozl.linux.org.au/ > > _______________________________________________ > > Sugar-devel mailing list > > [6]Sugar-devel at lists.sugarlabs.org > > [7]http://lists.sugarlabs.org/listinfo/sugar-devel > > > > Regards, > > -- > > Jui Pradhan > > _______________________________________________ > > Sugar-devel mailing list > > [8]Sugar-devel at lists.sugarlabs.org > > [9]http://lists.sugarlabs.org/listinfo/sugar-devel > > > > * > > > > References: > > > > [1] https://github.com/orgs/sugarlabs/projects/4 > > [2] mailto:juipradhan2k at gmail.com > > [3] mailto:quozl at laptop.org > > [4] https://github.com/sugarlabs/GSoC > > [5] https://quozl.linux.org.au/ > > [6] mailto:Sugar-devel at lists.sugarlabs.org > > [7] http://lists.sugarlabs.org/listinfo/sugar-devel > > [8] mailto:Sugar-devel at lists.sugarlabs.org > > [9] http://lists.sugarlabs.org/listinfo/sugar-devel > > -- > James Cameron > https://quozl.linux.org.au/ > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From srevinsaju at sugarlabs.org Thu Jan 21 01:16:47 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Thu, 21 Jan 2021 09:16:47 +0300 Subject: [Sugar-devel] v4.activities.sugarlabs.org (ASLO-v4) is up! Message-ID: <9677157c-12b8-d747-c041-fd9324701de7@sugarlabs.org> G'day! ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! ... with only a few more minor tidying up, ASLO-v4 will be ready for production. Activity maintainers can now push their bundles to ASLO-v4 by following the instructions on https://wiki.sugarlabs.org/go/Service/activities4 as well as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. Please feel free to reach out, so that I can improve the existing documentation, or anything you think is too complex. Next steps: * Connect services/update-aslo.php and deploy a flask server (I am trying to get a hold of some more good apache knowledge) * Sending "new version detected" emails to aslo at lists.sugarlabs.org, or should we create a new mailing list? -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x1007816766D390D7.asc Type: application/pgp-keys Size: 4849 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From quozl at laptop.org Thu Jan 21 02:00:41 2021 From: quozl at laptop.org (James Cameron) Date: Thu, 21 Jan 2021 18:00:41 +1100 Subject: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up! In-Reply-To: <9677157c-12b8-d747-c041-fd9324701de7@sugarlabs.org> References: <9677157c-12b8-d747-c041-fd9324701de7@sugarlabs.org> Message-ID: <20210121070041.GB2715@laptop.org> Thanks, great work. Merged 204. I've also updated Browse. https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac I would prefer new version notifications to go to sugar-devel at lists.sugarlabs.org, as that's one place we've seen them previously. aslo at lists.sugarlabs.org was for handling by library editors, but we don't have any active, and we don't have the same process with v4. On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: > G'day! > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! ... with only > a few more minor tidying up, ASLO-v4 will be ready for production. > > Activity maintainers can now push their bundles to ASLO-v4 by following the > instructions on https://wiki.sugarlabs.org/go/Service/activities4 as well > as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. > Please feel free to reach out, so that I can improve the existing > documentation, or anything you think is too complex. > > Next steps: > > * Connect services/update-aslo.php and deploy a flask server (I am > trying to get a hold of some more good apache knowledge) > * Sending "new version detected" emails to aslo at lists.sugarlabs.org, > or should we create a new mailing list? > > -- > Srevin Saju > https://srevinsaju.me > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > sub RSA 4096/14479587 2020-05-19 > > _______________________________________________ > Systems mailing list > Systems at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/systems -- James Cameron https://quozl.linux.org.au/ From srevinsaju at sugarlabs.org Thu Jan 21 02:03:02 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Thu, 21 Jan 2021 10:03:02 +0300 Subject: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up! In-Reply-To: <20210121070041.GB2715@laptop.org> References: <9677157c-12b8-d747-c041-fd9324701de7@sugarlabs.org> <20210121070041.GB2715@laptop.org> Message-ID: Right. I will configure ASLO-v4 to email sugar-devel@ with release notifications. Thanks to all developers, mentors who helped me out with this. Had a great experience working with it!!! On 1/21/21 10:00 AM, James Cameron wrote: > Thanks, great work. Merged 204. > > I've also updated Browse. > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac > > I would prefer new version notifications to go to > sugar-devel at lists.sugarlabs.org, as that's one place we've seen them > previously. aslo at lists.sugarlabs.org was for handling by library > editors, but we don't have any active, and we don't have the same > process with v4. > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: >> G'day! >> >> ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! ... with only >> a few more minor tidying up, ASLO-v4 will be ready for production. >> >> Activity maintainers can now push their bundles to ASLO-v4 by following the >> instructions on https://wiki.sugarlabs.org/go/Service/activities4 as well >> as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. >> Please feel free to reach out, so that I can improve the existing >> documentation, or anything you think is too complex. >> >> Next steps: >> >> * Connect services/update-aslo.php and deploy a flask server (I am >> trying to get a hold of some more good apache knowledge) >> * Sending "new version detected" emails to aslo at lists.sugarlabs.org, >> or should we create a new mailing list? >> >> -- >> Srevin Saju >> https://srevinsaju.me >> > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >> sub RSA 4096/14479587 2020-05-19 >> > > > >> _______________________________________________ >> Systems mailing list >> Systems at lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/systems > -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x1007816766D390D7.asc Type: application/pgp-keys Size: 4849 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From srevinsaju at sugarlabs.org Thu Jan 21 03:28:00 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Thu, 21 Jan 2021 11:28:00 +0300 Subject: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up! In-Reply-To: References: <9677157c-12b8-d747-c041-fd9324701de7@sugarlabs.org> <20210121070041.GB2715@laptop.org> Message-ID: And now, (Thanks bernie_!), we can use https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting sugar's microformat update system as mentioned below: > * support Sugar's microformat software upgrade feature in My > Settings, (Sugar 0.116 is configured > in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater > in|src/jarabe/model/update/aslo.py|which reaches out to a PHP > script|update-aslo.php|, and will instead be configured to > use|src/jarabe/model/update/microformat.py|), > On 1/21/21 10:03 AM, Srevin Saju wrote: > Right. I will configure ASLO-v4 to email sugar-devel@ with release > notifications. > Thanks to all developers, mentors who helped me out with this. Had a > great experience working with it!!! > > On 1/21/21 10:00 AM, James Cameron wrote: >> Thanks, great work.? Merged 204. >> >> I've also updated Browse. >> >> https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac >> >> >> I would prefer new version notifications to go to >> sugar-devel at lists.sugarlabs.org, as that's one place we've seen them >> previously.? aslo at lists.sugarlabs.org was for handling by library >> editors, but we don't have any active, and we don't have the same >> process with v4. >> >> On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: >>> G'day! >>> >>> ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! ... >>> with only >>> a few more minor tidying up, ASLO-v4 will be ready for production. >>> >>> Activity maintainers can now push their bundles to ASLO-v4 by >>> following the >>> instructions on https://wiki.sugarlabs.org/go/Service/activities4 as >>> well >>> as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. >>> Please feel free to reach out, so that I can improve the existing >>> documentation, or anything you think is too complex. >>> >>> Next steps: >>> >>> ? * Connect services/update-aslo.php and deploy a flask server (I am >>> ??? trying to get a hold of some more good apache knowledge) >>> ? * Sending "new version detected" emails to aslo at lists.sugarlabs.org, >>> ??? or should we create a new mailing list? >>> >>> -- >>> Srevin Saju >>> https://srevinsaju.me >>> >> pub?? RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >> >>> sub?? RSA 4096/14479587 2020-05-19 >>> >> >> >> >>> _______________________________________________ >>> Systems mailing list >>> Systems at lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/systems >> >> >> _______________________________________________ >> Sugar-devel mailing list >> Sugar-devel at lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x1007816766D390D7.asc Type: application/pgp-keys Size: 4849 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From activities-v4 at sugarlabs.org Thu Jan 21 04:12:57 2021 From: activities-v4 at sugarlabs.org (activities-v4 at sugarlabs.org) Date: Thu, 21 Jan 2021 04:12:57 -0500 (EST) Subject: [Sugar-devel] [ASLOv4][RELEASE] JupyterLabs - 6 Message-ID: <20210121091257.C107B1E163A@sunjammer.sugarlabs.org> JupyterLabs-6 has been released Version: 6 Bundle ID: io.srevinsaju.JupyterLabs Release time: Thu Jan 21 04:12:57 2021 You can download the latest release of this activity here: - Info: https:///app/io.srevinsaju.JupyterLabs - Download: https:///bundles/JupyterLabs-6.xo If you have questions about this review, please answer to this e-mail or join #sugar on chat.freenode.net. -- Sugar Activity Library https:// From activities-v4 at sugarlabs.org Thu Jan 21 04:12:57 2021 From: activities-v4 at sugarlabs.org (activities-v4 at sugarlabs.org) Date: Thu, 21 Jan 2021 04:12:57 -0500 (EST) Subject: [Sugar-devel] [ASLOv4][RELEASE] Browse - 206 Message-ID: <20210121091257.D53C31E163B@sunjammer.sugarlabs.org> Browse-206 has been released Version: 206 Bundle ID: org.laptop.WebActivity Release time: Thu Jan 21 04:12:57 2021 You can download the latest release of this activity here: - Info: https:///app/org.laptop.WebActivity - Download: https:///bundles/Browse-206.xo If you have questions about this review, please answer to this e-mail or join #sugar on chat.freenode.net. -- Sugar Activity Library https:// From activities-v4 at sugarlabs.org Thu Jan 21 04:12:57 2021 From: activities-v4 at sugarlabs.org (activities-v4 at sugarlabs.org) Date: Thu, 21 Jan 2021 04:12:57 -0500 (EST) Subject: [Sugar-devel] [ASLOv4][RELEASE] Implode - 20.1.1~quozl Message-ID: <20210121091257.E81431E163C@sunjammer.sugarlabs.org> Implode-20.1.1~quozl has been released Version: 20.1.1~quozl Bundle ID: com.jotaro.ImplodeActivity Release time: Thu Jan 21 04:12:57 2021 You can download the latest release of this activity here: - Info: https:///app/com.jotaro.ImplodeActivity - Download: https:///bundles/Implode-20.1.1~quozl.xo If you have questions about this review, please answer to this e-mail or join #sugar on chat.freenode.net. -- Sugar Activity Library https:// From sumitsrisumit at gmail.com Thu Jan 21 10:53:18 2021 From: sumitsrisumit at gmail.com (Sumit Srivastava) Date: Thu, 21 Jan 2021 21:23:18 +0530 Subject: [Sugar-devel] A show of excitement and source of motivation for everyone here Message-ID: Just came across this one-year-old comment of mine on a YouTube video titled "The Coolest Netbook You?ve Forgotten About: The OLPC XO-1" when someone commented on my comment about 2 hours ago. [Link to the video: https://youtu.be/UPP4ClRmVik] I thought that I'd share it all of you on the mailing list since it shows that people are still excited to hear about the cool stuff that the people here have built and the impact you're delivering each and every day. All of you are awesome! Sharing the whole YouTube comment transcript here, without any editing: Sumit Srivastava 1 year ago Hi, I'm from SugarLabs, the organisation that makes the software that OLPC laptops (and a lot more devices) run on. Happy to answer any questions. Please ask. Likes: 132 generic Josh number 96 generic Josh number 96 1 year ago Do you know if the display is switching modes with the greyscale thing? Very curious how the screen works Likes: 9 Alex Alex 1 year ago Have the laptops been upgraded over the years or have they stayed with the same exact hardware as initially? Eg bigger storage, Ram, a touchscreen, etc? Likes: 3 Sumit Srivastava Sumit Srivastava 1 year ago @generic Josh number 96 I have a better resource for you to read up on this display: http://wiki.laptop.org/go/Display It serves a good intro to the OLPC display. Likes: 11 Sumit Srivastava Sumit Srivastava 1 year ago @generic Josh number 96 Thanks for asking. A kernel configuration file is used to select colour or grayscale mode in the driver, and thus the display controller ASIC. This is in the kernel sources. The keyboard shim detects brightness control keys and manages the backlight power. When the backlight is turned off, the grayscale mode is enabled. When the backlight is turned on, the grayscale mode is disabled. This is in the keyboard shim sources. On the XO-1.75 and XO-4 models, a reverse biased red LED in the same SMT package as the green storage LED is used as an ambient light sensor. The power management daemon (powerd) detects high ambient light and turns off the backlight and turns on the grayscale mode. The backlight is turned off to save power, and increase running time on battery. This is in the powerd sources. However, without any change to backlight brightness or mode switching, full sunlight does appear as greyscale, because the human eye can't discern the small amount of colour emitted by the backlight compared to the large amount of white light reflected from the sun. Likes: 26 Sumit Srivastava Sumit Srivastava 1 year ago @Alex The hardware has been regularly updated with release of newer models. For example, XO-4 (the latest one) has a touchscreen variant and improved hardware. Likes: 10 Alex Alex 1 year ago What engine is the SugarXO browser based on? Likes: 1 Sumit Srivastava Sumit Srivastava 1 year ago @Alex The simple browser also called browse activity is implemented using HulaHop library and uses Gecko rendering engine(same as Firefox). Other browsers available for XO laptops are Opera and Firefox. :) Likes: 6 Alex Alex 1 year ago @Sumit Srivastava Really??? Opera and Firefox can run on these laptops??? I'm impressed! Likes: 1 Sumit Srivastava Sumit Srivastava 1 year ago @Alex these laptops are not underpowered, they're just aimed at children who want to learn, and appropriately capable to do so. :) Likes: 7 velleda velleda 1 year ago Exactly why do you need a developer key to boot things other than official OS builds, and why does it take 24 hours to get one? Likes: 3 Sumit Srivastava Sumit Srivastava 1 year ago @velleda because this was designed with security and antitheft in mind, and it's pretty secure, along with being fun to play with. Likes: 4 Sumit Srivastava Sumit Srivastava 1 year ago @velleda also, thank you for asking. Here's a link to your question, if you want to read a long explanation: http://wiki.laptop.org/go/Developer_key_philosophy Likes: 4 TheSola10 TheSola10 1 year ago Would it be interesting to switch OLPC to Silverblue/OSTree for increased reliability and less required maintenance? Sumit Srivastava Sumit Srivastava 1 year ago @TheSola10 Sugar OS is designed specifically with young children in mind. All our decisions, designs, usability considerations are made with that thing in mind. I don't think any other organisation would want to do that with OS. Likes: Likes: 5 James Livesey James Livesey 1 year ago @NiggaNig420 TOONZ They're giving their best efforts to help. They may or may not be part of Sugar Labs (and in their defence it's hard to verify), but they are providing people with helpful answers, so please don't be so rude! Likes: 13 Kintaro oe Kintaro oe 1 year ago any way to unlock the bios? me and my father tried to install xp countless times but the bios didnt allow us to, it would make my childhood dream finally complete Likes: 2 Sumit Srivastava Sumit Srivastava 1 year ago @Kintaro oe yes, you can install other operating systems using developer key. Instructions to request a developer key are at: http://wiki.laptop.org/go/Activation_and_developer_keys#Getting_a_developer_key Likes: 2 James Livesey James Livesey 1 year ago (edited) @NiggaNig420 TOONZ It appears to me that you are racist; however I do respect that people can have their own opinions in certain situations. Your 'evidence' that you have provided may be falsely representing the groups in question, and they may only be a minority. They may not be the representatives of their race, religion or nationality, and in fact it appears that there are so many Indians, Pakistanis and Asians that are brilliant, valued and talented individuals that we should be glad to have on Earth. Please don't prejudice, it's a bad quality to have! Life lesson over! ? Likes: 9 Kintaro oe Kintaro oe 1 year ago @Sumit Srivastava thanks Likes: Likes: 1 BitterJames BitterJames 1 year ago @James Livesey literally nobody cares. James Livesey James Livesey 1 year ago @BitterJames Except for the other 7 likers Hi another person called James Likes: 5 RiotOne RiotOne 1 year ago Sumit Im not sure that I know you... What is your IRC name and development branch? Peachy?s Here! Peachy?s Here! 1 year ago Sumit Srivastava! How do Transreflective Displays work? Sumit Srivastava Sumit Srivastava 1 year ago @RiotOne IRC: sum2it Development branch: SugarLabs- musicblocks Likes: 1 Sumit Srivastava Sumit Srivastava 1 year ago @Peachy?s Here! transreflective displays can be imagined as an e ink display with a backlight. Not really an accurate description but would be easier to grasp the concept. Likes: 1 anonfilly anonfilly 1 year ago Is the project still alive? Likes: 2 Sumit Srivastava Sumit Srivastava 1 year ago @anonfilly Yes, SugarLabs is still alive and growing. Impacts over 3 million kids in the world. KOTYAR0 KOTYAR0 1 year ago You do a great help to the world. How are you getting paid for your work, who makes your budget? Sumit Srivastava Sumit Srivastava 1 year ago @KOTYAR0 Thank you! We don't get paid. It's all volunteers who want to provide the best educational tools to children, for free. Likes: 1 Linuxuser95 Highlighted reply Linuxuser95 2 hours ago Id like to know how Windows XP or 7 Worked with the OLPC ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Thu Jan 21 14:45:38 2021 From: quozl at laptop.org (James Cameron) Date: Fri, 22 Jan 2021 06:45:38 +1100 Subject: [Sugar-devel] A show of excitement and source of motivation for everyone here In-Reply-To: References: Message-ID: <20210121194538.GA30976@laptop.org> On Thu, Jan 21, 2021 at 09:23:18PM +0530, Sumit Srivastava wrote: > Just came across this one-year-old comment of mine on a YouTube > video titled "The Coolest Netbook You?ve Forgotten About: The OLPC > XO-1" when someone commented on my comment about 2 hours ago. [Link > to the video: [1]https:// youtu.be/UPP4ClRmVik] > > I thought that I'd share it all of you on the mailing list since it > shows that people are still excited to hear about the cool stuff > that the people here have built and the impact you're delivering > each and every day. All of you are awesome! > > Sharing the whole YouTube comment transcript here, without any > editing: Thanks. Reviewed. Your answer about Browse is out of date. You probably used Wiki pages that have not been updated for over a decade. Browse uses WebKit now. When you copy text written by someone else, please do credit them appropriately. http://lists.sugarlabs.org/archive/sugar-devel/2019-June/056969.html https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md#be-considerate -- James Cameron https://quozl.linux.org.au/ From sumitsrisumit at gmail.com Thu Jan 21 15:00:45 2021 From: sumitsrisumit at gmail.com (Sumit Srivastava) Date: Fri, 22 Jan 2021 01:30:45 +0530 Subject: [Sugar-devel] A show of excitement and source of motivation for everyone here In-Reply-To: <20210121194538.GA30976@laptop.org> References: <20210121194538.GA30976@laptop.org> Message-ID: Hi, I agree that I should have credited you for that answer. Will credit you appropriately in the answer about Grayscale. Let me know if you've any updates that I could make in any other comments (like browse comment). I'll happily do so with credit. Thanks, Sumit On Fri, Jan 22, 2021, 1:15 AM James Cameron wrote: > On Thu, Jan 21, 2021 at 09:23:18PM +0530, Sumit Srivastava wrote: > > Just came across this one-year-old comment of mine on a YouTube > > video titled "The Coolest Netbook You?ve Forgotten About: The OLPC > > XO-1" when someone commented on my comment about 2 hours ago. [Link > > to the video: [1]https:// youtu.be/UPP4ClRmVik] > > > > I thought that I'd share it all of you on the mailing list since it > > shows that people are still excited to hear about the cool stuff > > that the people here have built and the impact you're delivering > > each and every day. All of you are awesome! > > > > Sharing the whole YouTube comment transcript here, without any > > editing: > > Thanks. Reviewed. > > Your answer about Browse is out of date. You probably used Wiki pages > that have not been updated for over a decade. Browse uses WebKit now. > > When you copy text written by someone else, please do credit them > appropriately. > > http://lists.sugarlabs.org/archive/sugar-devel/2019-June/056969.html > > https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md#be-considerate > > -- > James Cameron > https://quozl.linux.org.au/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From saurabhguptajpr at yahoo.in Sat Jan 23 09:30:57 2021 From: saurabhguptajpr at yahoo.in (Saurabh Gupta) Date: Sat, 23 Jan 2021 14:30:57 +0000 (UTC) Subject: [Sugar-devel] Participation in GSOC 2021 References: <1097962416.4536752.1611412257402.ref@mail.yahoo.com> Message-ID: <1097962416.4536752.1611412257402@mail.yahoo.com> Hi everyone,I hope you all are doing wellBy way of introduction, I am Saurabh, a 2nd-year student from IIT Roorkee. I am contributing to Sugarizer for the last few months and have fixed some issues. During this journey, I gained some knowledge about sugarizer activities and how sugarizer works.Here, I am just eager to know if sugarizer is planning to incorporate Hindi as a language in the coming future just like MusicBlocks has?Further, I am eagerly looking forward to participate in GSoC 2021 and make valuable contributions to Sugarlabs. Regards?Saurabh Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Sun Jan 24 18:29:21 2021 From: quozl at laptop.org (James Cameron) Date: Mon, 25 Jan 2021 10:29:21 +1100 Subject: [Sugar-devel] Participation in GSOC 2021 In-Reply-To: <1097962416.4536752.1611412257402@mail.yahoo.com> References: <1097962416.4536752.1611412257402.ref@mail.yahoo.com> <1097962416.4536752.1611412257402@mail.yahoo.com> Message-ID: <20210124232921.GD16602@laptop.org> Welcome Saurabh, We are a permissionless community. Why do you not add Hindi as a language immediately? There is no issue or pull request that mentions Hindi. There are closed pull requests that add other languages. I doubt Lionel has any reason to refuse a language, but if you think that may be the case, and you see no reply from him here, then ask him directly. On Sat, Jan 23, 2021 at 02:30:57PM +0000, Saurabh Gupta wrote: > Hi everyone, > I hope you all are doing well > By way of introduction, I am Saurabh, a 2nd-year student from IIT Roorkee. I am > contributing to Sugarizer for the last few months and have fixed some issues. > During this journey, I gained some knowledge about sugarizer activities and how > sugarizer works. > Here, I am just eager to know if sugarizer is planning to incorporate Hindi as > a language in the coming future just like MusicBlocks has? > Further, I am eagerly looking forward to participate in GSoC 2021 and make > valuable contributions to Sugarlabs. > > Regards > Saurabh Gupta > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From maulik.1822cs1079 at kiet.edu Mon Jan 25 13:21:39 2021 From: maulik.1822cs1079 at kiet.edu (MAULIK VARSHNEY) Date: Mon, 25 Jan 2021 23:51:39 +0530 Subject: [Sugar-devel] Information about Idea Page GSOC2021. Message-ID: Hey, Can anyone please help me with the Idea List page for GSOC 2021? What all technologies and prior codebase knowledge is generally being required/expected from the students participating in GSOC with Sage Math as parent Organisation? -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Mon Jan 25 19:03:31 2021 From: quozl at laptop.org (James Cameron) Date: Tue, 26 Jan 2021 11:03:31 +1100 Subject: [Sugar-devel] Information about Idea Page GSOC2021. In-Reply-To: References: Message-ID: <20210126000331.GB18815@laptop.org> You asked about SageMath. Please contact the SageMath organisation for all information about their involvement in GSoC. Sugar Labs has no relationship with SageMath. For Sugar Labs and GSoC, we have no ideas list yet. You can see last year's ideas list on our repository; https://github.com/sugarlabs/GSoC We do not select students based on technologies and codebase knowledge alone. To work towards a better proposal, read the list of points in our "Right fit" section; https://github.com/sugarlabs/GSoC#right-fit On Mon, Jan 25, 2021 at 11:51:39PM +0530, MAULIK VARSHNEY wrote: > Hey, > Can anyone please help me with the Idea List page for GSOC 2021? > What all technologies and prior codebase knowledge is generally being required/ > expected from the students participating in GSOC with Sage Math as parent > Organisation? > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From lionel.laske at gmail.com Tue Jan 26 04:06:57 2021 From: lionel.laske at gmail.com (=?UTF-8?Q?Lionel_Lask=C3=A9?=) Date: Tue, 26 Jan 2021 10:06:57 +0100 Subject: [Sugar-devel] Participation in GSOC 2021 In-Reply-To: References: Message-ID: Hi Saurabh, Thanks for your interest in Sugarizer and for your contributions. As James mentioned, there is no specific request today about integrating Hindi language in Sugarizer. I tend to prefer adding features asked by the field and there is no today deployment asking for Hindi. But of course anyone can propose new features, so I will certainly accept new languages for Sugarizer. BTW localization in Sugarizer is not a programming task, it's handled using a dedicated website - more friendly for translators - on https://translate.sugarizer.org Regards. Lionel Date: Mon, 25 Jan 2021 10:29:21 +1100 > From: James Cameron > To: Saurabh Gupta > Cc: "sugar-devel at lists.sugarlabs.org" > > Subject: Re: [Sugar-devel] Participation in GSOC 2021 > Message-ID: <20210124232921.GD16602 at laptop.org> > Content-Type: text/plain; charset=us-ascii > > Welcome Saurabh, > > We are a permissionless community. Why do you not add Hindi as a > language immediately? There is no issue or pull request that mentions > Hindi. There are closed pull requests that add other languages. I > doubt Lionel has any reason to refuse a language, but if you think > that may be the case, and you see no reply from him here, then ask him > directly. > > On Sat, Jan 23, 2021 at 02:30:57PM +0000, Saurabh Gupta wrote: > > Hi everyone, > > I hope you all are doing well > > By way of introduction, I am Saurabh, a 2nd-year student from IIT > Roorkee. I am > > contributing to Sugarizer for the last few months and have fixed some > issues. > > During this journey, I gained some knowledge about sugarizer activities > and how > > sugarizer works. > > Here, I am just eager to know if sugarizer is planning to incorporate > Hindi as > > a language in the coming future just like MusicBlocks has? > > Further, I am eagerly looking forward to participate in GSoC 2021 and > make > > valuable contributions to Sugarlabs. > > > > Regards > > Saurabh Gupta > > > _______________________________________________ > > Sugar-devel mailing list > > Sugar-devel at lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > -- > James Cameron > https://quozl.linux.org.au/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Tue Jan 26 18:49:01 2021 From: quozl at laptop.org (James Cameron) Date: Wed, 27 Jan 2021 10:49:01 +1100 Subject: [Sugar-devel] Spectrum Message-ID: <20210126234901.GC13962@laptop.org> I was introduced to https://spectrum.chat/ while at https://linux.conf.au/ for working with the open hardware miniconference track. Spectrum is open source. https://github.com/withspectrum -- James Cameron https://quozl.linux.org.au/ From quozl at laptop.org Tue Jan 26 19:08:05 2021 From: quozl at laptop.org (James Cameron) Date: Wed, 27 Jan 2021 11:08:05 +1100 Subject: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up! In-Reply-To: References: <9677157c-12b8-d747-c041-fd9324701de7@sugarlabs.org> <20210121070041.GB2715@laptop.org> Message-ID: <20210127000805.GD13962@laptop.org> On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote: > And now, (Thanks bernie_!), we can use > https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting > sugar's microformat update system as mentioned below: > > > * support Sugar's microformat software upgrade feature in My > > Settings, (Sugar 0.116 is configured > > in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater > > in|src/jarabe/model/update/aslo.py|which reaches out to a PHP > > script|update-aslo.php|, and will instead be configured to > > use|src/jarabe/model/update/microformat.py|), https://github.com/sugarlabs/sugar/pull/939 Needs testing. I've used tcpdump and saw no evidence of connection to port 443, so I'm yet to dig into how to reconfigure my Sugar install. > > > On 1/21/21 10:03 AM, Srevin Saju wrote: > > Right. I will configure ASLO-v4 to email sugar-devel@ with release > > notifications. > > Thanks to all developers, mentors who helped me out with this. Had a > > great experience working with it!!! > > > > On 1/21/21 10:00 AM, James Cameron wrote: > > > Thanks, great work.? Merged 204. > > > > > > I've also updated Browse. > > > > > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac > > > > > > > > > I would prefer new version notifications to go to > > > sugar-devel at lists.sugarlabs.org, as that's one place we've seen them > > > previously.? aslo at lists.sugarlabs.org was for handling by library > > > editors, but we don't have any active, and we don't have the same > > > process with v4. > > > > > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: > > > > G'day! > > > > > > > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! > > > > ... with only > > > > a few more minor tidying up, ASLO-v4 will be ready for production. > > > > > > > > Activity maintainers can now push their bundles to ASLO-v4 by > > > > following the > > > > instructions on > > > > https://wiki.sugarlabs.org/go/Service/activities4 as well > > > > as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. > > > > Please feel free to reach out, so that I can improve the existing > > > > documentation, or anything you think is too complex. > > > > > > > > Next steps: > > > > > > > > ? * Connect services/update-aslo.php and deploy a flask server (I am > > > > ??? trying to get a hold of some more good apache knowledge) > > > > ? * Sending "new version detected" emails to aslo at lists.sugarlabs.org, > > > > ??? or should we create a new mailing list? > > > > > > > > -- > > > > Srevin Saju > > > > https://srevinsaju.me > > > > > > > pub?? RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > > > > > > > sub?? RSA 4096/14479587 2020-05-19 > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Systems mailing list > > > > Systems at lists.sugarlabs.org > > > > http://lists.sugarlabs.org/listinfo/systems > > > > > > > > > _______________________________________________ > > > Sugar-devel mailing list > > > Sugar-devel at lists.sugarlabs.org > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- > Srevin Saju > https://srevinsaju.me > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > sub RSA 4096/14479587 2020-05-19 > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From quozl at laptop.org Tue Jan 26 19:09:41 2021 From: quozl at laptop.org (James Cameron) Date: Wed, 27 Jan 2021 11:09:41 +1100 Subject: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up! In-Reply-To: References: <9677157c-12b8-d747-c041-fd9324701de7@sugarlabs.org> <20210121070041.GB2715@laptop.org> Message-ID: <20210127000941.GE13962@laptop.org> On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote: > And now, (Thanks bernie_!), we can use > https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting > sugar's microformat update system as mentioned below: > > > * support Sugar's microformat software upgrade feature in My > > Settings, (Sugar 0.116 is configured > > in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater > > in|src/jarabe/model/update/aslo.py|which reaches out to a PHP > > script|update-aslo.php|, and will instead be configured to > > use|src/jarabe/model/update/microformat.py|), I've reviewed the output of update-aslo.php briefly. For Implode it gives a minVersion of 0.116 and a maxVersion of 0.117. How does an activity author specify these values? 20.1.1~quozl {9e5ecf85-6bb9-4403-bae8-d6865f19677b} 0.116 0.117 https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo 198 https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe > > > On 1/21/21 10:03 AM, Srevin Saju wrote: > > Right. I will configure ASLO-v4 to email sugar-devel@ with release > > notifications. > > Thanks to all developers, mentors who helped me out with this. Had a > > great experience working with it!!! > > > > On 1/21/21 10:00 AM, James Cameron wrote: > > > Thanks, great work.? Merged 204. > > > > > > I've also updated Browse. > > > > > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac > > > > > > > > > I would prefer new version notifications to go to > > > sugar-devel at lists.sugarlabs.org, as that's one place we've seen them > > > previously.? aslo at lists.sugarlabs.org was for handling by library > > > editors, but we don't have any active, and we don't have the same > > > process with v4. > > > > > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: > > > > G'day! > > > > > > > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! > > > > ... with only > > > > a few more minor tidying up, ASLO-v4 will be ready for production. > > > > > > > > Activity maintainers can now push their bundles to ASLO-v4 by > > > > following the > > > > instructions on > > > > https://wiki.sugarlabs.org/go/Service/activities4 as well > > > > as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. > > > > Please feel free to reach out, so that I can improve the existing > > > > documentation, or anything you think is too complex. > > > > > > > > Next steps: > > > > > > > > ? * Connect services/update-aslo.php and deploy a flask server (I am > > > > ??? trying to get a hold of some more good apache knowledge) > > > > ? * Sending "new version detected" emails to aslo at lists.sugarlabs.org, > > > > ??? or should we create a new mailing list? > > > > > > > > -- > > > > Srevin Saju > > > > https://srevinsaju.me > > > > > > > pub?? RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > > > > > > > sub?? RSA 4096/14479587 2020-05-19 > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Systems mailing list > > > > Systems at lists.sugarlabs.org > > > > http://lists.sugarlabs.org/listinfo/systems > > > > > > > > > _______________________________________________ > > > Sugar-devel mailing list > > > Sugar-devel at lists.sugarlabs.org > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- > Srevin Saju > https://srevinsaju.me > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > sub RSA 4096/14479587 2020-05-19 > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From srevinsaju at sugarlabs.org Tue Jan 26 23:58:27 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Wed, 27 Jan 2021 07:58:27 +0300 Subject: [Sugar-devel] Spectrum In-Reply-To: <20210126234901.GC13962@laptop.org> References: <20210126234901.GC13962@laptop.org> Message-ID: <20b0ec9c-f242-ce90-b1aa-f26a085fff5e@sugarlabs.org> yes, its a nice software. Another one is https://rocket.chat/ On 1/27/21 2:49 AM, James Cameron wrote: > I was introduced to https://spectrum.chat/ while at > https://linux.conf.au/ for working with the open hardware > miniconference track. > > Spectrum is open source. https://github.com/withspectrum > -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x1007816766D390D7.asc Type: application/pgp-keys Size: 4849 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From srevinsaju at sugarlabs.org Wed Jan 27 00:04:41 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Wed, 27 Jan 2021 08:04:41 +0300 Subject: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up! In-Reply-To: <20210127000941.GE13962@laptop.org> References: <9677157c-12b8-d747-c041-fd9324701de7@sugarlabs.org> <20210121070041.GB2715@laptop.org> <20210127000941.GE13962@laptop.org> Message-ID: <4cf4c8d3-c8ad-f5ba-2664-130ce10d9452@sugarlabs.org> reply inline. On 1/27/21 3:09 AM, James Cameron wrote: > On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote: >> And now, (Thanks bernie_!), we can use >> https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting >> sugar's microformat update system as mentioned below: >> >>> * support Sugar's microformat software upgrade feature in My >>> Settings, (Sugar 0.116 is configured >>> in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater >>> in|src/jarabe/model/update/aslo.py|which reaches out to a PHP >>> script|update-aslo.php|, and will instead be configured to >>> use|src/jarabe/model/update/microformat.py|), > I've reviewed the output of update-aslo.php briefly. For Implode it > gives a minVersion of 0.116 and a maxVersion of 0.117. How does an > activity author specify these values? Right now, its hardcoded into https://github.com/sugarlabs/aslo-v4/blob/a1ac5dac02030f38dca863eea3c70b978ebd8ad1/aslo4/rdf/rdf.py#L55. Let me know what would be the best implementation. > > > > > > > > > > > 20.1.1~quozl > > > {9e5ecf85-6bb9-4403-bae8-d6865f19677b} > 0.116 > 0.117 > https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo > 198 > https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html > sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe > > > > > > >> On 1/21/21 10:03 AM, Srevin Saju wrote: >>> Right. I will configure ASLO-v4 to email sugar-devel@ with release >>> notifications. >>> Thanks to all developers, mentors who helped me out with this. Had a >>> great experience working with it!!! >>> >>> On 1/21/21 10:00 AM, James Cameron wrote: >>>> Thanks, great work.? Merged 204. >>>> >>>> I've also updated Browse. >>>> >>>> https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac >>>> >>>> >>>> I would prefer new version notifications to go to >>>> sugar-devel at lists.sugarlabs.org, as that's one place we've seen them >>>> previously.? aslo at lists.sugarlabs.org was for handling by library >>>> editors, but we don't have any active, and we don't have the same >>>> process with v4. >>>> >>>> On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: >>>>> G'day! >>>>> >>>>> ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! >>>>> ... with only >>>>> a few more minor tidying up, ASLO-v4 will be ready for production. >>>>> >>>>> Activity maintainers can now push their bundles to ASLO-v4 by >>>>> following the >>>>> instructions on >>>>> https://wiki.sugarlabs.org/go/Service/activities4 as well >>>>> as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. >>>>> Please feel free to reach out, so that I can improve the existing >>>>> documentation, or anything you think is too complex. >>>>> >>>>> Next steps: >>>>> >>>>> ? * Connect services/update-aslo.php and deploy a flask server (I am >>>>> ??? trying to get a hold of some more good apache knowledge) >>>>> ? * Sending "new version detected" emails to aslo at lists.sugarlabs.org, >>>>> ??? or should we create a new mailing list? >>>>> >>>>> -- >>>>> Srevin Saju >>>>> https://srevinsaju.me >>>>> >>>> pub?? RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >>>> >>>>> sub?? RSA 4096/14479587 2020-05-19 >>>>> >>>> >>>>> _______________________________________________ >>>>> Systems mailing list >>>>> Systems at lists.sugarlabs.org >>>>> http://lists.sugarlabs.org/listinfo/systems >>>> _______________________________________________ >>>> Sugar-devel mailing list >>>> Sugar-devel at lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >> -- >> Srevin Saju >> https://srevinsaju.me >> > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >> sub RSA 4096/14479587 2020-05-19 >> > > >> _______________________________________________ >> Sugar-devel mailing list >> Sugar-devel at lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel -- Srevin Saju https://srevinsaju.me On 1/27/21 3:09 AM, James Cameron wrote: > On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote: >> And now, (Thanks bernie_!), we can use >> https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting >> sugar's microformat update system as mentioned below: >> >>> * support Sugar's microformat software upgrade feature in My >>> Settings, (Sugar 0.116 is configured >>> in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater >>> in|src/jarabe/model/update/aslo.py|which reaches out to a PHP >>> script|update-aslo.php|, and will instead be configured to >>> use|src/jarabe/model/update/microformat.py|), > I've reviewed the output of update-aslo.php briefly. For Implode it > gives a minVersion of 0.116 and a maxVersion of 0.117. How does an > activity author specify these values? > > > > > > > > > > > > 20.1.1~quozl > > > {9e5ecf85-6bb9-4403-bae8-d6865f19677b} > 0.116 > 0.117 > https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo > 198 > https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html > sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe > > > > > > >> On 1/21/21 10:03 AM, Srevin Saju wrote: >>> Right. I will configure ASLO-v4 to email sugar-devel@ with release >>> notifications. >>> Thanks to all developers, mentors who helped me out with this. Had a >>> great experience working with it!!! >>> >>> On 1/21/21 10:00 AM, James Cameron wrote: >>>> Thanks, great work.? Merged 204. >>>> >>>> I've also updated Browse. >>>> >>>> https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac >>>> >>>> >>>> I would prefer new version notifications to go to >>>> sugar-devel at lists.sugarlabs.org, as that's one place we've seen them >>>> previously.? aslo at lists.sugarlabs.org was for handling by library >>>> editors, but we don't have any active, and we don't have the same >>>> process with v4. >>>> >>>> On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: >>>>> G'day! >>>>> >>>>> ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! >>>>> ... with only >>>>> a few more minor tidying up, ASLO-v4 will be ready for production. >>>>> >>>>> Activity maintainers can now push their bundles to ASLO-v4 by >>>>> following the >>>>> instructions on >>>>> https://wiki.sugarlabs.org/go/Service/activities4 as well >>>>> as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. >>>>> Please feel free to reach out, so that I can improve the existing >>>>> documentation, or anything you think is too complex. >>>>> >>>>> Next steps: >>>>> >>>>> ? * Connect services/update-aslo.php and deploy a flask server (I am >>>>> ??? trying to get a hold of some more good apache knowledge) >>>>> ? * Sending "new version detected" emails to aslo at lists.sugarlabs.org, >>>>> ??? or should we create a new mailing list? >>>>> >>>>> -- >>>>> Srevin Saju >>>>> https://srevinsaju.me >>>>> >>>> pub?? RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >>>> >>>>> sub?? RSA 4096/14479587 2020-05-19 >>>>> >>>> >>>> >>>>> _______________________________________________ >>>>> Systems mailing list >>>>> Systems at lists.sugarlabs.org >>>>> http://lists.sugarlabs.org/listinfo/systems >>>> >>>> _______________________________________________ >>>> Sugar-devel mailing list >>>> Sugar-devel at lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >> -- >> Srevin Saju >> https://srevinsaju.me >> > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >> sub RSA 4096/14479587 2020-05-19 >> > > > >> _______________________________________________ >> Sugar-devel mailing list >> Sugar-devel at lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel > -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x1007816766D390D7.asc Type: application/pgp-keys Size: 4849 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From quozl at laptop.org Wed Jan 27 00:30:35 2021 From: quozl at laptop.org (James Cameron) Date: Wed, 27 Jan 2021 16:30:35 +1100 Subject: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up! In-Reply-To: <4cf4c8d3-c8ad-f5ba-2664-130ce10d9452@sugarlabs.org> References: <9677157c-12b8-d747-c041-fd9324701de7@sugarlabs.org> <20210121070041.GB2715@laptop.org> <20210127000941.GE13962@laptop.org> <4cf4c8d3-c8ad-f5ba-2664-130ce10d9452@sugarlabs.org> Message-ID: <20210127053035.GM13962@laptop.org> On Wed, Jan 27, 2021 at 08:04:41AM +0300, Srevin Saju wrote: > reply inline. me too. > > On 1/27/21 3:09 AM, James Cameron wrote: > > On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote: > > > And now, (Thanks bernie_!), we can use > > > https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting > > > sugar's microformat update system as mentioned below: > > > > > > > * support Sugar's microformat software upgrade feature in My > > > > Settings, (Sugar 0.116 is configured > > > > in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater > > > > in|src/jarabe/model/update/aslo.py|which reaches out to a PHP > > > > script|update-aslo.php|, and will instead be configured to > > > > use|src/jarabe/model/update/microformat.py|), > > I've reviewed the output of update-aslo.php briefly. For Implode it > > gives a minVersion of 0.116 and a maxVersion of 0.117. How does an > > activity author specify these values? > > Right now, its hardcoded into https://github.com/sugarlabs/aslo-v4/blob/a1ac5dac02030f38dca863eea3c70b978ebd8ad1/aslo4/rdf/rdf.py#L55. > Let me know what would be the best implementation. I'm in doubt. I had previously asked that we not be required to change activity metadata, yet activity metadata is a great place to put this. What do you think? Perhaps each new release should be interpreted as being for the current version, if such metadata is missing. https://developer.sugarlabs.org/sugar3/sugar3.bundle.html is our activity metadata documentation. https://wiki.sugarlabs.org/go/Development_Team/Almanac/Activity_Bundles is also documentation. In the history of edits to the Wiki, we had a host_version metadata item to specify the version of Sugar, but it was not implemented. So perhaps min_sugar_version and max_sugar_version are needed. On the other hand, aslo.py does _not check_ the minVersion and maxVersion values. For the time being, you can set them both to 0.118. With aslo.py not checking the value, it doesn't yet matter. > > > > > > > > > > > > > > > > > > > > > > > 20.1.1~quozl > > > > > > {9e5ecf85-6bb9-4403-bae8-d6865f19677b} > > 0.116 > > 0.117 > > https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo > > 198 > > https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html > > sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe > > > > > > > > > > > > > > > On 1/21/21 10:03 AM, Srevin Saju wrote: > > > > Right. I will configure ASLO-v4 to email sugar-devel@ with release > > > > notifications. > > > > Thanks to all developers, mentors who helped me out with this. Had a > > > > great experience working with it!!! > > > > > > > > On 1/21/21 10:00 AM, James Cameron wrote: > > > > > Thanks, great work.? Merged 204. > > > > > > > > > > I've also updated Browse. > > > > > > > > > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac > > > > > > > > > > > > > > > I would prefer new version notifications to go to > > > > > sugar-devel at lists.sugarlabs.org, as that's one place we've seen them > > > > > previously.? aslo at lists.sugarlabs.org was for handling by library > > > > > editors, but we don't have any active, and we don't have the same > > > > > process with v4. > > > > > > > > > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: > > > > > > G'day! > > > > > > > > > > > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! > > > > > > ... with only > > > > > > a few more minor tidying up, ASLO-v4 will be ready for production. > > > > > > > > > > > > Activity maintainers can now push their bundles to ASLO-v4 by > > > > > > following the > > > > > > instructions on > > > > > > https://wiki.sugarlabs.org/go/Service/activities4 as well > > > > > > as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. > > > > > > Please feel free to reach out, so that I can improve the existing > > > > > > documentation, or anything you think is too complex. > > > > > > > > > > > > Next steps: > > > > > > > > > > > > ? * Connect services/update-aslo.php and deploy a flask server (I am > > > > > > ??? trying to get a hold of some more good apache knowledge) > > > > > > ? * Sending "new version detected" emails to aslo at lists.sugarlabs.org, > > > > > > ??? or should we create a new mailing list? > > > > > > > > > > > > -- > > > > > > Srevin Saju > > > > > > https://srevinsaju.me > > > > > > > > > > > pub?? RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > > > > > > > > > > > sub?? RSA 4096/14479587 2020-05-19 > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Systems mailing list > > > > > > Systems at lists.sugarlabs.org > > > > > > http://lists.sugarlabs.org/listinfo/systems > > > > > _______________________________________________ > > > > > Sugar-devel mailing list > > > > > Sugar-devel at lists.sugarlabs.org > > > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > -- > > > Srevin Saju > > > https://srevinsaju.me > > > > > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > > > sub RSA 4096/14479587 2020-05-19 > > > > > > > > > > _______________________________________________ > > > Sugar-devel mailing list > > > Sugar-devel at lists.sugarlabs.org > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- > Srevin Saju > https://srevinsaju.me > > On 1/27/21 3:09 AM, James Cameron wrote: > > On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote: > > > And now, (Thanks bernie_!), we can use > > > https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting > > > sugar's microformat update system as mentioned below: > > > > > > > * support Sugar's microformat software upgrade feature in My > > > > Settings, (Sugar 0.116 is configured > > > > in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater > > > > in|src/jarabe/model/update/aslo.py|which reaches out to a PHP > > > > script|update-aslo.php|, and will instead be configured to > > > > use|src/jarabe/model/update/microformat.py|), > > I've reviewed the output of update-aslo.php briefly. For Implode it > > gives a minVersion of 0.116 and a maxVersion of 0.117. How does an > > activity author specify these values? > > > > > > > > > > > > > > > > > > > > > > > > 20.1.1~quozl > > > > > > {9e5ecf85-6bb9-4403-bae8-d6865f19677b} > > 0.116 > > 0.117 > > https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo > > 198 > > https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html > > sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe > > > > > > > > > > > > > > > On 1/21/21 10:03 AM, Srevin Saju wrote: > > > > Right. I will configure ASLO-v4 to email sugar-devel@ with release > > > > notifications. > > > > Thanks to all developers, mentors who helped me out with this. Had a > > > > great experience working with it!!! > > > > > > > > On 1/21/21 10:00 AM, James Cameron wrote: > > > > > Thanks, great work.? Merged 204. > > > > > > > > > > I've also updated Browse. > > > > > > > > > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac > > > > > > > > > > > > > > > I would prefer new version notifications to go to > > > > > sugar-devel at lists.sugarlabs.org, as that's one place we've seen them > > > > > previously.? aslo at lists.sugarlabs.org was for handling by library > > > > > editors, but we don't have any active, and we don't have the same > > > > > process with v4. > > > > > > > > > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: > > > > > > G'day! > > > > > > > > > > > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! > > > > > > ... with only > > > > > > a few more minor tidying up, ASLO-v4 will be ready for production. > > > > > > > > > > > > Activity maintainers can now push their bundles to ASLO-v4 by > > > > > > following the > > > > > > instructions on > > > > > > https://wiki.sugarlabs.org/go/Service/activities4 as well > > > > > > as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. > > > > > > Please feel free to reach out, so that I can improve the existing > > > > > > documentation, or anything you think is too complex. > > > > > > > > > > > > Next steps: > > > > > > > > > > > > ? * Connect services/update-aslo.php and deploy a flask server (I am > > > > > > ??? trying to get a hold of some more good apache knowledge) > > > > > > ? * Sending "new version detected" emails to aslo at lists.sugarlabs.org, > > > > > > ??? or should we create a new mailing list? > > > > > > > > > > > > -- > > > > > > Srevin Saju > > > > > > https://srevinsaju.me > > > > > > > > > > > pub?? RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > > > > > > > > > > > sub?? RSA 4096/14479587 2020-05-19 > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Systems mailing list > > > > > > Systems at lists.sugarlabs.org > > > > > > http://lists.sugarlabs.org/listinfo/systems > > > > > > > > > > _______________________________________________ > > > > > Sugar-devel mailing list > > > > > Sugar-devel at lists.sugarlabs.org > > > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > -- > > > Srevin Saju > > > https://srevinsaju.me > > > > > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > > > sub RSA 4096/14479587 2020-05-19 > > > > > > > > > > > > _______________________________________________ > > > Sugar-devel mailing list > > > Sugar-devel at lists.sugarlabs.org > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > -- > Srevin Saju > https://srevinsaju.me > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > sub RSA 4096/14479587 2020-05-19 > -- James Cameron https://quozl.linux.org.au/ From srevinsaju at sugarlabs.org Wed Jan 27 00:36:21 2021 From: srevinsaju at sugarlabs.org (Srevin Saju) Date: Wed, 27 Jan 2021 08:36:21 +0300 Subject: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up! In-Reply-To: <20210127053035.GM13962@laptop.org> References: <9677157c-12b8-d747-c041-fd9324701de7@sugarlabs.org> <20210121070041.GB2715@laptop.org> <20210127000941.GE13962@laptop.org> <4cf4c8d3-c8ad-f5ba-2664-130ce10d9452@sugarlabs.org> <20210127053035.GM13962@laptop.org> Message-ID: On 1/27/21 8:30 AM, James Cameron wrote: > On Wed, Jan 27, 2021 at 08:04:41AM +0300, Srevin Saju wrote: >> reply inline. > me too. > >> On 1/27/21 3:09 AM, James Cameron wrote: >>> On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote: >>>> And now, (Thanks bernie_!), we can use >>>> https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting >>>> sugar's microformat update system as mentioned below: >>>> >>>>> * support Sugar's microformat software upgrade feature in My >>>>> Settings, (Sugar 0.116 is configured >>>>> in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater >>>>> in|src/jarabe/model/update/aslo.py|which reaches out to a PHP >>>>> script|update-aslo.php|, and will instead be configured to >>>>> use|src/jarabe/model/update/microformat.py|), >>> I've reviewed the output of update-aslo.php briefly. For Implode it >>> gives a minVersion of 0.116 and a maxVersion of 0.117. How does an >>> activity author specify these values? >> Right now, its hardcoded into https://github.com/sugarlabs/aslo-v4/blob/a1ac5dac02030f38dca863eea3c70b978ebd8ad1/aslo4/rdf/rdf.py#L55. >> Let me know what would be the best implementation. > I'm in doubt. I had previously asked that we not be required to > change activity metadata, yet activity metadata is a great place to > put this. What do you think? Agreed. That would reduce a lot of complexities. Its ideal to extract every information from the bundle itself. Also, it would be nice to keep an `activityInfoVersion` which would define the specification of the activity.info, so that, we can run a migrate function to update old activity.info to new activity.info and vice-versa. > Perhaps each new release should be interpreted as being for the > current version, if such metadata is missing. Agreed, that would do. > > https://developer.sugarlabs.org/sugar3/sugar3.bundle.html is our > activity metadata documentation. > > https://wiki.sugarlabs.org/go/Development_Team/Almanac/Activity_Bundles > is also documentation. > > In the history of edits to the Wiki, we had a host_version metadata > item to specify the version of Sugar, but it was not implemented. > > So perhaps min_sugar_version and max_sugar_version are needed. Yes. > > On the other hand, aslo.py does _not check_ the minVersion and > maxVersion values. > > For the time being, you can set them both to 0.118. > > With aslo.py not checking the value, it doesn't yet matter. Updated, as of e071af059cdbac9bb903b9543beec89033f35cd6 commit on sugarlabs/aslo-v4 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> 20.1.1~quozl >>> >>> >>> {9e5ecf85-6bb9-4403-bae8-d6865f19677b} >>> 0.116 >>> 0.117 >>> https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo >>> 198 >>> https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html >>> sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe >>> >>> >>> >>> >>> >>> >>>> On 1/21/21 10:03 AM, Srevin Saju wrote: >>>>> Right. I will configure ASLO-v4 to email sugar-devel@ with release >>>>> notifications. >>>>> Thanks to all developers, mentors who helped me out with this. Had a >>>>> great experience working with it!!! >>>>> >>>>> On 1/21/21 10:00 AM, James Cameron wrote: >>>>>> Thanks, great work.? Merged 204. >>>>>> >>>>>> I've also updated Browse. >>>>>> >>>>>> https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac >>>>>> >>>>>> >>>>>> I would prefer new version notifications to go to >>>>>> sugar-devel at lists.sugarlabs.org, as that's one place we've seen them >>>>>> previously.? aslo at lists.sugarlabs.org was for handling by library >>>>>> editors, but we don't have any active, and we don't have the same >>>>>> process with v4. >>>>>> >>>>>> On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: >>>>>>> G'day! >>>>>>> >>>>>>> ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! >>>>>>> ... with only >>>>>>> a few more minor tidying up, ASLO-v4 will be ready for production. >>>>>>> >>>>>>> Activity maintainers can now push their bundles to ASLO-v4 by >>>>>>> following the >>>>>>> instructions on >>>>>>> https://wiki.sugarlabs.org/go/Service/activities4 as well >>>>>>> as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. >>>>>>> Please feel free to reach out, so that I can improve the existing >>>>>>> documentation, or anything you think is too complex. >>>>>>> >>>>>>> Next steps: >>>>>>> >>>>>>> ? * Connect services/update-aslo.php and deploy a flask server (I am >>>>>>> ??? trying to get a hold of some more good apache knowledge) >>>>>>> ? * Sending "new version detected" emails to aslo at lists.sugarlabs.org, >>>>>>> ??? or should we create a new mailing list? >>>>>>> >>>>>>> -- >>>>>>> Srevin Saju >>>>>>> https://srevinsaju.me >>>>>>> >>>>>> pub?? RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >>>>>> >>>>>>> sub?? RSA 4096/14479587 2020-05-19 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Systems mailing list >>>>>>> Systems at lists.sugarlabs.org >>>>>>> http://lists.sugarlabs.org/listinfo/systems >>>>>> _______________________________________________ >>>>>> Sugar-devel mailing list >>>>>> Sugar-devel at lists.sugarlabs.org >>>>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> -- >>>> Srevin Saju >>>> https://srevinsaju.me >>>> >>> pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >>>> sub RSA 4096/14479587 2020-05-19 >>>> >>> >>>> _______________________________________________ >>>> Sugar-devel mailing list >>>> Sugar-devel at lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >> -- >> Srevin Saju >> https://srevinsaju.me >> >> On 1/27/21 3:09 AM, James Cameron wrote: >>> On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote: >>>> And now, (Thanks bernie_!), we can use >>>> https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting >>>> sugar's microformat update system as mentioned below: >>>> >>>>> * support Sugar's microformat software upgrade feature in My >>>>> Settings, (Sugar 0.116 is configured >>>>> in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater >>>>> in|src/jarabe/model/update/aslo.py|which reaches out to a PHP >>>>> script|update-aslo.php|, and will instead be configured to >>>>> use|src/jarabe/model/update/microformat.py|), >>> I've reviewed the output of update-aslo.php briefly. For Implode it >>> gives a minVersion of 0.116 and a maxVersion of 0.117. How does an >>> activity author specify these values? >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> 20.1.1~quozl >>> >>> >>> {9e5ecf85-6bb9-4403-bae8-d6865f19677b} >>> 0.116 >>> 0.117 >>> https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo >>> 198 >>> https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html >>> sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe >>> >>> >>> >>> >>> >>> >>>> On 1/21/21 10:03 AM, Srevin Saju wrote: >>>>> Right. I will configure ASLO-v4 to email sugar-devel@ with release >>>>> notifications. >>>>> Thanks to all developers, mentors who helped me out with this. Had a >>>>> great experience working with it!!! >>>>> >>>>> On 1/21/21 10:00 AM, James Cameron wrote: >>>>>> Thanks, great work.? Merged 204. >>>>>> >>>>>> I've also updated Browse. >>>>>> >>>>>> https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac >>>>>> >>>>>> >>>>>> I would prefer new version notifications to go to >>>>>> sugar-devel at lists.sugarlabs.org, as that's one place we've seen them >>>>>> previously.? aslo at lists.sugarlabs.org was for handling by library >>>>>> editors, but we don't have any active, and we don't have the same >>>>>> process with v4. >>>>>> >>>>>> On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: >>>>>>> G'day! >>>>>>> >>>>>>> ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! >>>>>>> ... with only >>>>>>> a few more minor tidying up, ASLO-v4 will be ready for production. >>>>>>> >>>>>>> Activity maintainers can now push their bundles to ASLO-v4 by >>>>>>> following the >>>>>>> instructions on >>>>>>> https://wiki.sugarlabs.org/go/Service/activities4 as well >>>>>>> as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. >>>>>>> Please feel free to reach out, so that I can improve the existing >>>>>>> documentation, or anything you think is too complex. >>>>>>> >>>>>>> Next steps: >>>>>>> >>>>>>> ? * Connect services/update-aslo.php and deploy a flask server (I am >>>>>>> ??? trying to get a hold of some more good apache knowledge) >>>>>>> ? * Sending "new version detected" emails to aslo at lists.sugarlabs.org, >>>>>>> ??? or should we create a new mailing list? >>>>>>> >>>>>>> -- >>>>>>> Srevin Saju >>>>>>> https://srevinsaju.me >>>>>>> >>>>>> pub?? RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >>>>>> >>>>>>> sub?? RSA 4096/14479587 2020-05-19 >>>>>>> >>>>>> >>>>>>> _______________________________________________ >>>>>>> Systems mailing list >>>>>>> Systems at lists.sugarlabs.org >>>>>>> http://lists.sugarlabs.org/listinfo/systems >>>>>> _______________________________________________ >>>>>> Sugar-devel mailing list >>>>>> Sugar-devel at lists.sugarlabs.org >>>>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> -- >>>> Srevin Saju >>>> https://srevinsaju.me >>>> >>> pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >>>> sub RSA 4096/14479587 2020-05-19 >>>> >>> >>> >>>> _______________________________________________ >>>> Sugar-devel mailing list >>>> Sugar-devel at lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >> -- >> Srevin Saju >> https://srevinsaju.me >> > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) >> sub RSA 4096/14479587 2020-05-19 >> > > > -- Srevin Saju https://srevinsaju.me -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x1007816766D390D7.asc Type: application/pgp-keys Size: 4849 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From saurabhguptajpr at yahoo.in Wed Jan 27 03:54:58 2021 From: saurabhguptajpr at yahoo.in (Saurabh Gupta) Date: Wed, 27 Jan 2021 08:54:58 +0000 (UTC) Subject: [Sugar-devel] Participation in GSOC 2021 In-Reply-To: <20210124232921.GD16602@laptop.org> References: <1097962416.4536752.1611412257402.ref@mail.yahoo.com> <1097962416.4536752.1611412257402@mail.yahoo.com> <20210124232921.GD16602@laptop.org> Message-ID: <155975473.484755.1611737698449@mail.yahoo.com> Hi James,Sure, I will be glad to add Hindi as a language to Sugarizer and add some value to Sugarizer.Once I discuss it with Lionel regarding the changes I need to make, I will act accordingly and immediately.Regards??Saurabh Gupta On Monday, 25 January, 2021, 04:59:31 am IST, James Cameron wrote: Welcome Saurabh, We are a permissionless community.? Why do you not add Hindi as a language immediately?? There is no issue or pull request that mentions Hindi.? There are closed pull requests that add other languages.? I doubt Lionel has any reason to refuse a language, but if you think that may be the case, and you see no reply from him here, then ask him directly. On Sat, Jan 23, 2021 at 02:30:57PM +0000, Saurabh Gupta wrote: > Hi everyone, > I hope you all are doing well > By way of introduction, I am Saurabh, a 2nd-year student from IIT Roorkee. I am > contributing to Sugarizer for the last few months and have fixed some issues. > During this journey, I gained some knowledge about sugarizer activities and how > sugarizer works. > Here, I am just eager to know if sugarizer is planning to incorporate Hindi as > a language in the coming future just like MusicBlocks has? > Further, I am eagerly looking forward to participate in GSoC 2021 and make > valuable contributions to Sugarlabs. > > Regards > Saurabh Gupta > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From saurabhguptajpr at yahoo.in Wed Jan 27 04:06:37 2021 From: saurabhguptajpr at yahoo.in (Saurabh Gupta) Date: Wed, 27 Jan 2021 09:06:37 +0000 (UTC) Subject: [Sugar-devel] Participation in GSOC 2021 In-Reply-To: References: Message-ID: <1947941716.217452.1611738397450@mail.yahoo.com> Hi Lionel,Thanks for sharing the insights about adding features to Sugarizer.If adding Hindi as a language looks good to you, we can add it in the language option in Sugarizer and also on?Weblate?so that people with Hindi as a native language can start doing the localization in Hindi also.RegardsSaurabh Gupta On Tuesday, 26 January, 2021, 02:37:10 pm IST, Lionel Lask? wrote: Hi Saurabh, Thanks for your interest in Sugarizer and for your contributions. As James mentioned, there is no specific request today about integrating Hindi language in Sugarizer.I tend to prefer adding features asked by the field and there is no today deployment asking for Hindi. But of course anyone can propose new features, so I will certainly accept new languages for Sugarizer. BTW localization in Sugarizer is not a programming task, it's handled using a dedicated website - more friendly for translators - on https://translate.sugarizer.org Regards. ?????? Lionel Date: Mon, 25 Jan 2021 10:29:21 +1100 From: James Cameron To: Saurabh Gupta Cc: "sugar-devel at lists.sugarlabs.org" ? ? ? ? Subject: Re: [Sugar-devel] Participation in GSOC 2021 Message-ID: <20210124232921.GD16602 at laptop.org> Content-Type: text/plain; charset=us-ascii Welcome Saurabh, We are a permissionless community.? Why do you not add Hindi as a language immediately?? There is no issue or pull request that mentions Hindi.? There are closed pull requests that add other languages.? I doubt Lionel has any reason to refuse a language, but if you think that may be the case, and you see no reply from him here, then ask him directly. On Sat, Jan 23, 2021 at 02:30:57PM +0000, Saurabh Gupta wrote: > Hi everyone, > I hope you all are doing well > By way of introduction, I am Saurabh, a 2nd-year student from IIT Roorkee. I am > contributing to Sugarizer for the last few months and have fixed some issues. > During this journey, I gained some knowledge about sugarizer activities and how > sugarizer works. > Here, I am just eager to know if sugarizer is planning to incorporate Hindi as > a language in the coming future just like MusicBlocks has? > Further, I am eagerly looking forward to participate in GSoC 2021 and make > valuable contributions to Sugarlabs. > > Regards > Saurabh Gupta > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Fri Jan 29 15:27:20 2021 From: quozl at laptop.org (James Cameron) Date: Sat, 30 Jan 2021 07:27:20 +1100 Subject: [Sugar-devel] GSoC 2021 Ideas In-Reply-To: <20210115075055.GA17244@laptop.org> References: <20210115075055.GA17244@laptop.org> Message-ID: <20210129202720.GA10485@laptop.org> GSoC 2021 is now accepting applications from mentoring organisations. Sugar Labs has until 19th February to apply. We still need ideas. On Fri, Jan 15, 2021 at 06:50:55PM +1100, James Cameron wrote: > We need ideas for GSoC this year. Let's get started. > > Change from last year; projects are 175 hours rather than 350 hours. > > Use ideas from previous years, or make new ideas. > > Make a new Ideas-2021.md file in our repository > https://github.com/sugarlabs/GSoC using a pull request. > > File README.md also needs a few changes. You can read the commit > history of changes to the file to see what changed last year. > > Applications by organisations are from 29th January to 19th February. > > Organisation administrators this year are Jui, Perrie and Lionel. > > -- > James Cameron > https://quozl.linux.org.au/ -- James Cameron https://quozl.linux.org.au/ From adityapratapsingh51 at gmail.com Sun Jan 31 11:05:30 2021 From: adityapratapsingh51 at gmail.com (Aditya Pratap Singh) Date: Sun, 31 Jan 2021 21:35:30 +0530 Subject: [Sugar-devel] Entry to GSoC 2021 Message-ID: Hello, My name is Aditya Pratap Singh, and I am a BTech fresher at Indraprastha Institute of Information Technology, Delhi. I have a decent experience in C++ and Python. I've been using Arch for over a year now. I am very much interested in participating in GSoC 2021. The main reason for doing GSoC is to get exposure to the developer's world and work with new people. I hope that, despite me being a fresher, the SugarLabs community welcomes me. This is my current contribution to SugarLabs: 1) Resolved this issue . 2) Made a SugarLabs extension . I am looking forward to working with SugarLabs. Regards Aditya Pratap Singh -------------- next part -------------- An HTML attachment was scrubbed... URL: From quozl at laptop.org Sun Jan 31 21:12:05 2021 From: quozl at laptop.org (James Cameron) Date: Mon, 1 Feb 2021 13:12:05 +1100 Subject: [Sugar-devel] Entry to GSoC 2021 In-Reply-To: References: Message-ID: <20210201021205.GC5766@laptop.org> Thanks for your contribution. I've forked your tictactoe into the Sugar Labs organisation. On Sun, Jan 31, 2021 at 09:35:30PM +0530, Aditya Pratap Singh wrote: > Hello, My name is Aditya Pratap Singh, and I am a BTech fresher at Indraprastha > Institute of Information Technology, Delhi. > > I have a decent experience in C++ and Python. I've been using Arch for over a > year now. > > I am very much interested in participating in GSoC 2021. The main reason for > doing GSoC is to get exposure to the developer's world and work with new > people. I hope that, despite me being a fresher, the SugarLabs community > welcomes me. > > This is my current contribution to SugarLabs: > 1) Resolved [1]this issue. > 2) Made a [2]SugarLabs extension. > I am looking forward to working with SugarLabs. > > Regards > Aditya Pratap Singh > > References: > > [1] https://github.com/sugarlabs/iknowmyabcs/issues/15 > [2] https://github.com/devmrfitz/tictactoe > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ From quozl at laptop.org Sun Jan 31 22:11:58 2021 From: quozl at laptop.org (James Cameron) Date: Mon, 1 Feb 2021 14:11:58 +1100 Subject: [Sugar-devel] linux.conf.au 2021 Message-ID: <20210201031158.GJ5766@laptop.org> Talks and keynotes from linux.conf.au 2021 are being uploaded. https://yewtu.be/channel/UCciKHCG06rnq31toLTfAiyw I attended the conference remote along with everyone else. What I've seen so far that I can recommend for Sugar Labs members; * keynotes by Cory Doctorow, Limor Fried (Adafruit) and Omoju Miller (GitHub). * a talk by Neil McGovern, director of the GNOME Foundation, on a patent suit, * a talk by Sumana Harihareswara, on how to get a project unstuck and fixing the skill gaps that got us here, * by Katie Bell, "What even is code? Building a non-code coding interface" * by Robin Willison, a tour of the Adelaide Makerspace, an adult learning environment, * by Mars Buttfield-Addison, "Radio Astronomy for Programmers", dealing with unusual graphics coordinate systems, * by Jeremy Kerr, "Server platforms: experiment with your expensive hardware too!", * by Paul Gardner-Stephen, "Digital Sovereignty: We need devices we truly own more than ever", * by Sanchayan Maity, "What's next for Bluetooth in PulseAudio?" -- James Cameron https://quozl.linux.org.au/ From adityapratapsingh51 at gmail.com Sun Jan 31 22:43:13 2021 From: adityapratapsingh51 at gmail.com (Aditya Pratap Singh) Date: Mon, 1 Feb 2021 09:13:13 +0530 Subject: [Sugar-devel] Entry to GSoC 2021 In-Reply-To: <20210201031541.GK5766@laptop.org> References: <20210201021205.GC5766@laptop.org> <20210201031541.GK5766@laptop.org> Message-ID: Thank you for your response For future communication, if I want *person A* specifically to see the mail, I should mention Sugar Mailing List in "To:" field and him/her in "Cc:" or vice versa? On Mon, 1 Feb 2021, 8:45 am James Cameron, wrote: > Hello, > > We do not like to give private replies because this can advantage you > over others; which is unfair treatment. > > Yes, you have a chance. But we have not seen how others have performed. > > We do not select students based on technologies and codebase knowledge > alone. To work towards a better proposal, read the list of points in > our "Right fit" section; > > https://github.com/sugarlabs/GSoC#right-fit > > Jui, Perrie, and Lionel are the organisation administrators this year. > > > https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-01-06 > > Please read the mailing list archives for anything you may have missed > before you subscribed. > > http://lists.sugarlabs.org/archive/sugar-devel/ > > On Mon, Feb 01, 2021 at 08:26:01AM +0530, Aditya Pratap Singh wrote: > > Sir > > Are there any chances of me, as a fresher, getting selected by SugarLabs > for > > GSoC? If yes, what should I do for now to improve my chances and show > that I'm > > willing to spend time working on Sugar? > > > > Regards > > Aditya Pratap Singh > > > > On Mon, 1 Feb 2021, 7:42 am James Cameron, <[1]quozl at laptop.org> wrote: > > > > Thanks for your contribution. I've forked your tictactoe into the > > Sugar Labs organisation. > > > > On Sun, Jan 31, 2021 at 09:35:30PM +0530, Aditya Pratap Singh wrote: > > > Hello, My name is Aditya Pratap Singh, and I am a BTech fresher at > > Indraprastha > > > Institute of Information Technology, Delhi. > > > > > > I have a decent experience in C++ and Python. I've been using Arch > for > > over a > > > year now. > > > > > > I am very much interested in participating in GSoC 2021. The main > reason > > for > > > doing GSoC is to get exposure to the developer's world and work > with new > > > people. I hope that, despite me being a fresher, the SugarLabs > community > > > welcomes me. > > > > > > This is my current contribution to SugarLabs: > > > 1) Resolved [1]this issue. > > > 2) Made a [2]SugarLabs extension. > > > I am looking forward to working with SugarLabs. > > > > > > Regards > > > Aditya Pratap Singh > > > > > > References: > > > > > > [1] [2]https://github.com/sugarlabs/iknowmyabcs/issues/15 > > > [2] [3]https://github.com/devmrfitz/tictactoe > > > > > _______________________________________________ > > > Sugar-devel mailing list > > > [4]Sugar-devel at lists.sugarlabs.org > > > [5]http://lists.sugarlabs.org/listinfo/sugar-devel > > > > -- > > James Cameron > > [6]https://quozl.linux.org.au/ > > > > References: > > > > [1] mailto:quozl at laptop.org > > [2] https://github.com/sugarlabs/iknowmyabcs/issues/15 > > [3] https://github.com/devmrfitz/tictactoe > > [4] mailto:Sugar-devel at lists.sugarlabs.org > > [5] http://lists.sugarlabs.org/listinfo/sugar-devel > > [6] https://quozl.linux.org.au/ > > -- > James Cameron > https://quozl.linux.org.au/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: