Re: [Sugar-devel] [IAEP] FYI: GCI is discontinued

[Euan Ong]

This sounds great -- I'd be keen to help :)

On Thu, 11 Jun 2020 at 13:55, Samson Goddy  wrote:

> I am interested in helping to work on this idea too and I think it will be
> a good idea to get this going.
>
>
> Regards
>
> On Thu, Jun 11, 2020, 1:50 PM Walter Bender 
> wrote:
>
>> A few of us have been discussing how we might continue the concept
>> without formal Google support. Stay tuned.
>>
>> On Thu, Jun 11, 2020 at 2:58 AM Hrishi Patel 
>> wrote:
>>
>>> That is extremely sad. I read that email, I have so many good memories
>>> with GCI.
>>>
>>> On Thu, Jun 11, 2020, 2:25 AM Devin Ulibarri 
>>> wrote:
>>>
 Hi,

 Members of the GCI Mentors mailing list received this message today
 from Stephanie T. of Google.

 Some of you may not be on that list, but interested to know so I am
 copying it here.

 Thanks to everyone for all their efforts (and hacking) over the years
 for GCI with SL!

 > Hi GCI Mentors and Org Admins,
 >
 > Google Code-in concluded 10 amazing, productive, exhilarating years
 > in January. This program has been a success because of the amazing
 > energy and passion all of you have exhibited; volunteering dozens,
 > hundreds, and in some cases, thousands(!) of hours to help 14,700+
 > teenagers, from 115+ countries, complete a whopping 76,200+ open
 > source tasks, during the past 10 years!
 >
 > We wanted all of you to be among the first to know that Google Code-
 > in 2019 was our final Google Code-in contest. We've been looking hard
 > at our portfolio of programs and as open source evolves, our programs
 > need to evolve too. We've decided to focus our efforts on Google
 > Summer of Code and programs like Season of Docs that meet projects'
 > sustainability needs going into the next 10 years of open source.
 >
 > We want to thank you all for being inspiring role models to these
 > students. Many of you were GCI or GSoC students yourselves and have
 > been paying it forward for years by helping teenagers discover their
 > passion for open source software development. The extent of your
 > support was something many didn’t expect when they first started out
 > trying to complete a few tasks to earn a Google T-shirt.
 >
 > You have welcomed students into your communities and shown them how
 > open source is making the world a better place and how they can be a
 > part of that. You all have inspired, taught, listened, and made a
 > difference in the lives of thousands of students. THANK YOU! These
 > students have brought fresh new perspectives and ideas into your
 > communities, inspiring long-term committers with their enthusiasm,
 > curiosity and skills.
 >
 > Many of you have been mentors for all 10 years of GCI (plus GHOP!),
 > while others came into the GCI family just this past year. Regardless
 > of when you joined, thank you all for showing immense kindness,
 > patience, dedication, organization and guidance to the students, the
 > other mentors in our GCI community, and to me and the rest of our
 > team over the years.
 >
 > These past 10 years of Google Code-in have been an exciting,
 > adrenaline pumping adventure – thanks for coming along on the ride
 > with us!
 >
 > We will continue to be dedicated to helping open source communities
 > be sustainable and finding new contributors is an essential part of
 > those efforts. While Google Code-in is now officially retired, we
 > look forward to finding new ways to support your communities.
 >
 > Best,
 > Stephanie Taylor
 > GCI Program Lead
 --
 Follow me on GNU Social at https://loadaverage.org/pikurasa

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

>>> ___
>>> Sugar-devel mailing list
>>> Sugar-devel@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>> 
>> ___
>> IAEP -- It's An Education Project (not a laptop project!)
>> i...@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/iaep
>>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Debian Advocacy for Sugar - Update

[Chihurumnaya Ibiam]

 


On Thu, Jun 11, 2020 at 1:39 PM shaansubbaiah.c...@bmsce.ac.in <
shaansubbaiah.c...@bmsce.ac.in> wrote:

> Hello Ibiam,
>
> I am not sure if I got this right regarding the difference in line numbers
> but patch 1001
> 
> changes the schema indentation as discussed earlier. This patch has been
> numbered 1001, according to the README in the same commit, “1xxx:
> Possibly relevant for upstream adoption”. It has changes ahead of upstream.
>

Yes it was labeled "Possibly relevant for upstream adoption" because it's
only relevant for the official Debian release.

I believe this is a Debian patch and the diff is kept separate from
> browser.py( which is pulled from the upstream Github repository). Since
> the patch (located at /debian/patches/1001_un-embed_gsettings_schema.patch
> of the Salsa repository) is applied during installation, the line number
> changes (self.settings = _get_local_settings(activity)from L145 -> L147)
> is seen only in the installed Activity directory/Traceback. The Github and
> Salsa repositories have the above line in browser.py at L145 as they do
> not have the patch applied.
>

Yes this is what I've been trying to make you conclude, and you also could
have done this by viewing the source code of the activity in the debian
release.

I have to still find out why the issue occurs even with the patch. I was
> unable to reproduce the issue with libglib2.0-dev removed and the Web
> Activity log files deleted. I’ll restore a snapshot and try debugging.
>

Yes that's the next step to take.

Best,
> Shaan
>

Thanks for the update.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com



> On Wednesday, June 10, 2020, 11:14:19 PM GMT+5:30, Chihurumnaya Ibiam <
> ibiamchihurumn...@gmail.com> wrote:
>
>
> The commit #930e1c
> 
> applies patch
> 
> to the package, the commit message said
>
> Embedding the GSettings schema complicates generating during build. This 
> patch replicates the embedded schema as standalone file (partly reverting git 
> commit ffdacaa). . Additionally, this patch sprinkles some indentation 
> changes to the embedded schema, to ensure that if upstream changes the schema 
> then applying the patch will fail hard
>
> The commit message says the commit was reverting ffdacaa 
> 
>  while having the schema
> embedded with some indentation changes "to ensure that if the upstream 
> changes the schema
> then applying the patch will fail hard".
>
> The actual issue isn't the commit changing the indentation as that's not 
> what's been addressed.
> I've not been able to see any commit that change the lines, the error says 
> L192 of webactivity.py calls
> TabbedView in browser.py and this is where the lines get mixed up.
>
> Yes you'll have to investigate further why the schema can't be loaded but 
> also make sure the files in all 3 places correspond
> - sugar, salsa, github -.
>
>
>
> --
> Ibiam Chihurumnaya
> ibiamchihurumn...@gmail.com
>
>
>
> On Wed, Jun 10, 2020 at 5:26 PM shaansubbaiah.c...@bmsce.ac.in <
> shaansubbaiah.c...@bmsce.ac.in> wrote:
>
> Hello James and Ibiam,
>
> I should have been more clearer in my mail, the diff posted in the
> previous mail was generated by using Python with the difflib library.
>
> I have now gone through the commits in the Salsa repository and have found
> the commit that has caused the line changes. I’m not completely sure what
> the commit message means, it appears the difference in the indentation of
> the embedded schema was used to ensure that the patch in the commit would
> fail if upstream changed the schema. Linked here, #930e1c
> 
>
> Also, libglib2.0-bin had been added as a dependency in commit #c5717
> 
> and had been later replaced by a GSettings schema
> (org.laptop.WebActivity.gschema.xml) located at
> /usr/share/glib-2.0/schemas/ . Linked here, #0977a
> ,
> making Browse activity independent of libglib2.0-bin.
>
> I’ll have to investigate further as to why the Browse activity cannot
> detect the GSettings schema.
>
> Best,
> Shaan
> On Wednesday, June 10, 2020, 12:16:21 PM GMT+5:30, James Cameron <
> qu...@laptop.org> wrote:
>
>
> Shaan,
>
> * the sources are different, and this is not unusual, and not a problem
> worth reporting unless an explanation cannot be 

Re: [Sugar-devel] [IAEP] FYI: GCI is discontinued

[Samson Goddy]

I am interested in helping to work on this idea too and I think it will be
a good idea to get this going.


Regards

On Thu, Jun 11, 2020, 1:50 PM Walter Bender  wrote:

> A few of us have been discussing how we might continue the concept without
> formal Google support. Stay tuned.
>
> On Thu, Jun 11, 2020 at 2:58 AM Hrishi Patel 
> wrote:
>
>> That is extremely sad. I read that email, I have so many good memories
>> with GCI.
>>
>> On Thu, Jun 11, 2020, 2:25 AM Devin Ulibarri 
>> wrote:
>>
>>> Hi,
>>>
>>> Members of the GCI Mentors mailing list received this message today
>>> from Stephanie T. of Google.
>>>
>>> Some of you may not be on that list, but interested to know so I am
>>> copying it here.
>>>
>>> Thanks to everyone for all their efforts (and hacking) over the years
>>> for GCI with SL!
>>>
>>> > Hi GCI Mentors and Org Admins,
>>> >
>>> > Google Code-in concluded 10 amazing, productive, exhilarating years
>>> > in January. This program has been a success because of the amazing
>>> > energy and passion all of you have exhibited; volunteering dozens,
>>> > hundreds, and in some cases, thousands(!) of hours to help 14,700+
>>> > teenagers, from 115+ countries, complete a whopping 76,200+ open
>>> > source tasks, during the past 10 years!
>>> >
>>> > We wanted all of you to be among the first to know that Google Code-
>>> > in 2019 was our final Google Code-in contest. We've been looking hard
>>> > at our portfolio of programs and as open source evolves, our programs
>>> > need to evolve too. We've decided to focus our efforts on Google
>>> > Summer of Code and programs like Season of Docs that meet projects'
>>> > sustainability needs going into the next 10 years of open source.
>>> >
>>> > We want to thank you all for being inspiring role models to these
>>> > students. Many of you were GCI or GSoC students yourselves and have
>>> > been paying it forward for years by helping teenagers discover their
>>> > passion for open source software development. The extent of your
>>> > support was something many didn’t expect when they first started out
>>> > trying to complete a few tasks to earn a Google T-shirt.
>>> >
>>> > You have welcomed students into your communities and shown them how
>>> > open source is making the world a better place and how they can be a
>>> > part of that. You all have inspired, taught, listened, and made a
>>> > difference in the lives of thousands of students. THANK YOU! These
>>> > students have brought fresh new perspectives and ideas into your
>>> > communities, inspiring long-term committers with their enthusiasm,
>>> > curiosity and skills.
>>> >
>>> > Many of you have been mentors for all 10 years of GCI (plus GHOP!),
>>> > while others came into the GCI family just this past year. Regardless
>>> > of when you joined, thank you all for showing immense kindness,
>>> > patience, dedication, organization and guidance to the students, the
>>> > other mentors in our GCI community, and to me and the rest of our
>>> > team over the years.
>>> >
>>> > These past 10 years of Google Code-in have been an exciting,
>>> > adrenaline pumping adventure – thanks for coming along on the ride
>>> > with us!
>>> >
>>> > We will continue to be dedicated to helping open source communities
>>> > be sustainable and finding new contributors is an essential part of
>>> > those efforts. While Google Code-in is now officially retired, we
>>> > look forward to finding new ways to support your communities.
>>> >
>>> > Best,
>>> > Stephanie Taylor
>>> > GCI Program Lead
>>> --
>>> Follow me on GNU Social at https://loadaverage.org/pikurasa
>>>
>>> ___
>>> Sugar-devel mailing list
>>> Sugar-devel@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
> ___
> IAEP -- It's An Education Project (not a laptop project!)
> i...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] FYI: GCI is discontinued

[Walter Bender]

A few of us have been discussing how we might continue the concept without
formal Google support. Stay tuned.

On Thu, Jun 11, 2020 at 2:58 AM Hrishi Patel 
wrote:

> That is extremely sad. I read that email, I have so many good memories
> with GCI.
>
> On Thu, Jun 11, 2020, 2:25 AM Devin Ulibarri 
> wrote:
>
>> Hi,
>>
>> Members of the GCI Mentors mailing list received this message today
>> from Stephanie T. of Google.
>>
>> Some of you may not be on that list, but interested to know so I am
>> copying it here.
>>
>> Thanks to everyone for all their efforts (and hacking) over the years
>> for GCI with SL!
>>
>> > Hi GCI Mentors and Org Admins,
>> >
>> > Google Code-in concluded 10 amazing, productive, exhilarating years
>> > in January. This program has been a success because of the amazing
>> > energy and passion all of you have exhibited; volunteering dozens,
>> > hundreds, and in some cases, thousands(!) of hours to help 14,700+
>> > teenagers, from 115+ countries, complete a whopping 76,200+ open
>> > source tasks, during the past 10 years!
>> >
>> > We wanted all of you to be among the first to know that Google Code-
>> > in 2019 was our final Google Code-in contest. We've been looking hard
>> > at our portfolio of programs and as open source evolves, our programs
>> > need to evolve too. We've decided to focus our efforts on Google
>> > Summer of Code and programs like Season of Docs that meet projects'
>> > sustainability needs going into the next 10 years of open source.
>> >
>> > We want to thank you all for being inspiring role models to these
>> > students. Many of you were GCI or GSoC students yourselves and have
>> > been paying it forward for years by helping teenagers discover their
>> > passion for open source software development. The extent of your
>> > support was something many didn’t expect when they first started out
>> > trying to complete a few tasks to earn a Google T-shirt.
>> >
>> > You have welcomed students into your communities and shown them how
>> > open source is making the world a better place and how they can be a
>> > part of that. You all have inspired, taught, listened, and made a
>> > difference in the lives of thousands of students. THANK YOU! These
>> > students have brought fresh new perspectives and ideas into your
>> > communities, inspiring long-term committers with their enthusiasm,
>> > curiosity and skills.
>> >
>> > Many of you have been mentors for all 10 years of GCI (plus GHOP!),
>> > while others came into the GCI family just this past year. Regardless
>> > of when you joined, thank you all for showing immense kindness,
>> > patience, dedication, organization and guidance to the students, the
>> > other mentors in our GCI community, and to me and the rest of our
>> > team over the years.
>> >
>> > These past 10 years of Google Code-in have been an exciting,
>> > adrenaline pumping adventure – thanks for coming along on the ride
>> > with us!
>> >
>> > We will continue to be dedicated to helping open source communities
>> > be sustainable and finding new contributors is an essential part of
>> > those efforts. While Google Code-in is now officially retired, we
>> > look forward to finding new ways to support your communities.
>> >
>> > Best,
>> > Stephanie Taylor
>> > GCI Program Lead
>> --
>> Follow me on GNU Social at https://loadaverage.org/pikurasa
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


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

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

Re: [Sugar-devel] Debian Advocacy for Sugar - Update

[shaansubbaiah.c...@bmsce.ac.in]

Hello Ibiam,

 I am not sure if I got this right regarding the difference in line numbers but 
patch 1001 changes the schema indentation as discussed earlier. This patch has 
been numbered 1001, according to the README in the same commit, “1xxx: Possibly 
relevant for upstream adoption”. It has changes ahead of upstream.

I believe this is a Debian patch and the diff is kept separate from browser.py( 
which is pulled from the upstream Github repository). Since the patch (located 
at /debian/patches/1001_un-embed_gsettings_schema.patch of the Salsa 
repository) is applied during installation, the line number changes 
(self.settings = _get_local_settings(activity)from L145 -> L147) is seen only 
in the installed Activity directory/Traceback. The Github and Salsa 
repositories have the above line in browser.py at L145 as they do not have the 
patch applied.

I have to still find out why the issue occurs even with the patch. I was unable 
to reproduce the issue with libglib2.0-dev removed and the Web Activity log 
files deleted. I’ll restore a snapshot and try debugging.

Best,
Shaan
​   On Wednesday, June 10, 2020, 11:14:19 PM GMT+5:30, Chihurumnaya Ibiam 
 wrote:  
 
 The commit #930e1c applies patch to the package, the commit message said
Embedding the GSettings schema complicates generating during build.
 This patch replicates the embedded schema as standalone file
 (partly reverting git commit ffdacaa).
 .
 Additionally, this patch sprinkles some indentation changes
 to the embedded schema,
 to ensure that if upstream changes the schema
 then applying the patch will fail hard

The commit message says the commit was reverting ffdacaa while having the schema
embedded with some indentation changes "to ensure that if the upstream changes 
the schema
then applying the patch will fail hard".
The actual issue isn't the commit changing the indentation as that's not what's 
been addressed.
I've not been able to see any commit that change the lines, the error says L192 
of webactivity.py calls
TabbedView in browser.py and this is where the lines get mixed up.
Yes you'll have to investigate further why the schema can't be loaded but also 
make sure the files in all 3 places correspond 
- sugar, salsa, github -.

 
-- 
Ibiam Chihurumnaya 
ibiamchihurumn...@gmail.com


On Wed, Jun 10, 2020 at 5:26 PM shaansubbaiah.c...@bmsce.ac.in 
 wrote:


Hello James and Ibiam,

I should have been more clearer in my mail, the diff posted in the previous 
mail was generated by using Python with the difflib library.

I have now gone through the commits in the Salsa repository and have found the 
commit that has caused the line changes. I’m not completely sure what the 
commit message means, it appears the difference in the indentation of the 
embedded schema was used to ensure that the patch in the commit would fail if 
upstream changed the schema. Linked here, #930e1c

Also, libglib2.0-bin had been added as a dependency in commit #c5717 and had 
been later replaced by a GSettings schema (org.laptop.WebActivity.gschema.xml) 
located at /usr/share/glib-2.0/schemas/ . Linked here, #0977a, making Browse 
activity independent of libglib2.0-bin.

I’ll have to investigate further as to why the Browse activity cannot detect 
the GSettings schema.

Best,
Shaan
​   On Wednesday, June 10, 2020, 12:16:21 PM GMT+5:30, James Cameron 
 wrote:  
 
 Shaan,

* the sources are different, and this is not unusual, and not a problem worth 
reporting unless an explanation cannot be found,

* the commits in salsa explain the reason for every difference.

Now that you have detected a difference, please make sure you read the commits, 
in all aspects;

* the commit message,

* the commit diff,

* the context or ordering in which the diff occurs.

The diff format must be learned to the point you can be comfortable to make a 
change by hand.  Not that you have to; tools like patch(1) can do it for you, 
but sometimes a diff is malformed when it is sent by other means than git.

On Tue, Jun 09, 2020 at 06:29:10PM +0100, Chihurumnaya Ibiam wrote:
> Thanks for the update.
> 
> Both files in the Debian salsa repo and the github repo have matching lines 
> and
> I'm also guessing the file at
> the installed /usr/share/activities/browseactivity will also have matching -
> can you confirm if it does? - lines
> but the traceback prints the wrong lines.
> 
> --
> 
> Ibiam Chihurumnaya
> [1]ibiamchihurumn...@gmail.com
> 
> On Tue, Jun 9, 2020 at 6:02 PM [2]shaansubbaiah.c...@bmsce.ac.in <[3]
> shaansubbaiah.c...@bmsce.ac.in> wrote:
> 
>    Hello Ibiam,
> 
>    Comparing browse.py in:
> 
>      1. Github repository [4]https://github.com/sugarlabs/browse-activity/
>      2. Debian Salsa repository [5]https://salsa.debian.org/pkg-sugar-team/
>        sugar-browse-activity/-/blob/master/browser.py
>      3. The installed activity at /usr/share/activities/browseactivity
> 
>    The Github and Salsa versions have matching line numbers. Difference
>    between the Github and 

[Sugar-devel] Sugarizer Knowledge Activity Pack meeting (11 June)

[Dhruv Misra]

Hey there,

I had the weekly meeting with my mentor Lionel today i.e. 11 June at 9H UTC.

We reviewed tasks from last week and discussed the minor UI changes required to 
palettes. Then we discussed about localization of category/skill titles in 
Curriculum and decided to change the JSON accordingly. Finally, we then 
discussed addition of Trophies view and it’s presence implementations.


  *   Tasks from last week:
 *   Made the required UI changes to Curriculum, replaced flags with medals.
 *   Completed create/update/delete/sort for categories and skills.
 *   Created initial SugarDevice component
  *   Issues encountered last week: Adding Curriculum Activity tab to Journal 
Chooser, was fixed by making changes to `journalchooser.js`
  *   Tasks for this week:
 *   Fix the upload palette
 *   Add localization to CurriculumChooser and change JSON structure
 *   Work on the Trophies/Rewards view
 *   Start integration of presence
 *   Add features to SugarDevice

Thanks,
Dhruv Misra

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

Re: [Sugar-devel] FYI: GCI is discontinued

[Hrishi Patel]

That is extremely sad. I read that email, I have so many good memories with
GCI.

On Thu, Jun 11, 2020, 2:25 AM Devin Ulibarri  wrote:

> Hi,
>
> Members of the GCI Mentors mailing list received this message today
> from Stephanie T. of Google.
>
> Some of you may not be on that list, but interested to know so I am
> copying it here.
>
> Thanks to everyone for all their efforts (and hacking) over the years
> for GCI with SL!
>
> > Hi GCI Mentors and Org Admins,
> >
> > Google Code-in concluded 10 amazing, productive, exhilarating years
> > in January. This program has been a success because of the amazing
> > energy and passion all of you have exhibited; volunteering dozens,
> > hundreds, and in some cases, thousands(!) of hours to help 14,700+
> > teenagers, from 115+ countries, complete a whopping 76,200+ open
> > source tasks, during the past 10 years!
> >
> > We wanted all of you to be among the first to know that Google Code-
> > in 2019 was our final Google Code-in contest. We've been looking hard
> > at our portfolio of programs and as open source evolves, our programs
> > need to evolve too. We've decided to focus our efforts on Google
> > Summer of Code and programs like Season of Docs that meet projects'
> > sustainability needs going into the next 10 years of open source.
> >
> > We want to thank you all for being inspiring role models to these
> > students. Many of you were GCI or GSoC students yourselves and have
> > been paying it forward for years by helping teenagers discover their
> > passion for open source software development. The extent of your
> > support was something many didn’t expect when they first started out
> > trying to complete a few tasks to earn a Google T-shirt.
> >
> > You have welcomed students into your communities and shown them how
> > open source is making the world a better place and how they can be a
> > part of that. You all have inspired, taught, listened, and made a
> > difference in the lives of thousands of students. THANK YOU! These
> > students have brought fresh new perspectives and ideas into your
> > communities, inspiring long-term committers with their enthusiasm,
> > curiosity and skills.
> >
> > Many of you have been mentors for all 10 years of GCI (plus GHOP!),
> > while others came into the GCI family just this past year. Regardless
> > of when you joined, thank you all for showing immense kindness,
> > patience, dedication, organization and guidance to the students, the
> > other mentors in our GCI community, and to me and the rest of our
> > team over the years.
> >
> > These past 10 years of Google Code-in have been an exciting,
> > adrenaline pumping adventure – thanks for coming along on the ride
> > with us!
> >
> > We will continue to be dedicated to helping open source communities
> > be sustainable and finding new contributors is an essential part of
> > those efforts. While Google Code-in is now officially retired, we
> > look forward to finding new ways to support your communities.
> >
> > Best,
> > Stephanie Taylor
> > GCI Program Lead
> --
> Follow me on GNU Social at https://loadaverage.org/pikurasa
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel