Sugar Labs - User contributions [en]

Sugarizer Saint-Ouen deployment

2021-11-07T09:42:49Z

Llaske: Update Saint-Ouen deployment status

== Location ==

The city of [https://fr.wikipedia.org/wiki/Saint-Ouen-sur-Seine Saint-Ouen] is located in the northern suburbs of Paris.

The population is about 50,000 people.

There is about 5,400 children in schools: 2,200 in kindergarten, 3,200 in primary schools.
There is about 200 teachers in 23 school.

== History ==

The Saint-Ouen deployment started in 2014 with the deployment of 25 XO-4 at the Mendela school by [http://olpc-france.org OLPC France/Eduvelopers].

In 2017, the 25 XO-4 have been replaced by 25 tablets Lenovo Tab 2 A10-30 on Sugarizer OS, bought with the help of the L'Oreal Fondation.

[[File:Sugarizer stouen childs.jpg|thumb|Children playing with Sugarizer in Mendela school at Saint-Ouen]]

Considering the positive feedbacks of teachers on field and its wish to deploy Android tablets in schools, the Saint-Ouen city decided in 2018 to launch a large deployment of Sugarizer in schools.

A partnership was set between Saint-Ouen city, the Inspection Academique (depending of French minister of education) and OLPC France/Eduvelopers.

== First phase of deployment ==

The first phase of deployment has started in 2019 with a deployment in 3 schools: Mendela, PEF and Petit-Prince. It means about 50 class and 1000 children.

Three training sessions animated by IT team from Saint-Ouen city and OLPC France/Eduvelopers was planned between March and May with teachers of each school.

[[File:Sugarizer stouen training.jpg|thumb|Teacher training workshop in March 2019]]

== Devices and software ==

Tablets deployed are Samsung Galaxy Tab A 2018. Each schools received 2 chariots with 27 tablets in each and a WiFi . Each school is connected to a broadband internet connection.

[[File:Sugarizer stouen devices.png|thumb|Devices deployed at Saint-Ouen]]

Sugarizer OS is deployed on each tablets with about 20 android application launchable from Sugarizer OS.

Sugarizer Server is deployed on the city infrastructure using Docker.

[[File:Sugarizerserver stouen architecture.png|thumb|Sugarizer Server architecture at Saint-Ouen deployment]]

== Second phase of deployment ==

The second phase of deployment has started in september 2019 witch is a deployment in 5 new schools: Frédéric Joliot Curie, Irène Joliot Curie, Jules Michelet, Victor Hugo and La Fontaine. It means about 50 new class and about 1100 new children.

About 480 Sugarizer OS tablets was deployed between phase 1 and phase 2.

During the second phase, two training sessions for teachers was planned into each school. The first training session was planned at the beginning of school year and is intended to explain usage of tablets and Sugarizer. Training sessions are conducted by IT team from Saint-Ouen city, OLPC France/Eduvelopers and the mentor on digital technology for teachers (eRun) from Inspection Academique.

The second session was planned during Q2 2020 and was dedicated to listen teacher feedbacks but has been cancelled due to the pandemic.

== Third phase of deployment ==

The third phase of deployment was planned in 2nd semester 2020 but due to the pandemic was postponed to 2nd semester 2021. The objective is to deploy the 5 leaving schools in the city: Alexandre Bachelet, Anatole France, Emile Zola, Jules Valles and Paul Langevin. It means about 1500 new children and 300 new tablets.

For these new schools it was decided to use Sugarizer Server hosted on [https://sugarizer.site Sugarizer School Portal] instead of servers deployed on the city infrastructure.

== More information ==

Deployment updates are posted on [https://twitter.com/sugarizerapp Sugarizer twitter account].

Contact [[User:Llaske|Lionel Laské]] for more information.

Oversight Board/Minutes

2021-02-17T21:36:13Z

Llaske:

<noinclude>{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude>
__NOTOC__
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Oversight board holds regular monthly meetings.
</div>

=== Past meetings ===

Logs of meetings on the #sugar-meeting channel are available [http://meeting.sugarlabs.org/sugar-meeting/ here].

{|
| width="20%" valign="top" |
'''2021'''

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-01-06

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-01-20

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-02-03

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-02-17

{|
| width="20%" valign="top" |
'''2020'''

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-05-13

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-05-27

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-06-10

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-06-24

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-07-08

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-12-23

{|
| width="20%" valign="top" |
'''2019'''

04 Jan

[[Oversight_Board/Meeting_Minutes-2019-01-04|minutes]]
[[Oversight_Board/2019/meeting-log-2019-01-04|log]] 
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-01-04T20:00:43.html minutes]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-01-04T20:00:43 log]


01 Feb

[[Oversight_Board/Meeting_Minutes-2019-02-01|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-02-01T20:01:00.html minutes]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-02-01 log]


01 Mar

[[Oversight_Board/Meeting_Minutes-2019-03-01|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-03-01 log]


05 Apr

[[Oversight_Board/Meeting_Minutes-2019-04-05|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-04-05 log]


03 May

[[Oversight_Board/Meeting_Minutes-2019-05-03|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-05-03 log]


| width="20%" valign="top" |
'''2018'''

07 Dec
 [[Oversight_Board/2018/meeting-log-2018-12-07|log]]

03 Nov
 [[Oversight_Board/2018/meeting-log-2018-11-03|log]]

05 Oct
 [[Oversight_Board/2010/Meeting-log-2018-10-05|log]]

07 Sept
 [[Oversight_Board/2010/Meeting-log-2018-09-07|log]]

03 Aug
 [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-08-03T20:00:00 log]

06 July
 [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-07-06T20:11:29 log]

01 Jun
 [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-06-01T20:07:40 log]

04 May
 [[Oversight Board/Meeting Minutes-2018-05-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-05-04T20:00:12 log]

06 Apr
 [[Oversight Board/Meeting Minutes-2018-04-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-04-06 log]

02 Mar
 [[Oversight Board/Meeting Minutes-2018-03-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-02 log]

02 Feb
 [[Oversight Board/Meeting Minutes-2018-02-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-02-02 log]

05 Jan
 [[Oversight Board/Meeting Minutes-2018-01-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-05 log]

| width="20%" valign="top" |
'''2017'''

01 Dec
 [[Oversight Board/Meeting Minutes-2017-12-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-12-01 log]

03 Nov
 [[Oversight Board/Meeting Minutes-2017-11-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-11-03 log]

06 Oct
 [[Oversight Board/Meeting Minutes-2017-10-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-10-06T19:00:31 log]

01 Sep
 [[Oversight Board/Meeting Minutes-2017-09-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01T19:10:08 log]

04 Aug
 [[Oversight Board/Meeting Minutes-2017-08-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24 log]

07 Jul
 [[Oversight Board/Meeting Minutes-2017-07-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-07-07 log]

02 Jun
 [[Oversight Board/Meeting Minutes-2017-06-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-06-02 log]

05 May
 [[Oversight Board/Meeting Minutes-2017-05-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-05-05 log]

07 Apr
 [[Oversight Board/Meeting Minutes-2017-04-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-04-07T19:03:42 log]

03 Mar
 [[Oversight Board/Meeting Minutes-2017-03-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-03-03 log]

03 Feb
 [[Oversight Board/Meeting Minutes-2017-02-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-02-03 log]

06 Jan
 [[Oversight Board/Meeting Minutes-2017-01-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-01-06T19:07:40 log]

|}

{|
| width="20%" valign="top" |
'''2016'''

04 Nov
 [[Oversight Board/Meeting Minutes-2016-11-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-11-04T19:03:35 log]

07 Oct
 [[Oversight Board/Meeting Minutes-2016-10-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-10-07 log]

02 Sep
 [[Oversight Board/Meeting Minutes-2016-09-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-09-02T19:03:42 log] 

05 Aug
 [[Oversight Board/Meeting Minutes-2016-08-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-08-05 log] 

01 Jul
 [[Oversight Board/Meeting Minutes-2016-07-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-07-01T19:00:23 log] 

03 Jun
 [[Oversight Board/Meeting Minutes-2016-06-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-06-03T19:01:08 log] 

06 May
 [[Oversight Board/Meeting Minutes-2016-05-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-05-06T16:02:18 log] 

01 Apr
 [[Oversight Board/Meeting Minutes-2016-04-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-04-01 log] 

04 Mar
 [[Oversight Board/Meeting Minutes-2016-03-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-03-04 log] 

12 Feb
 [[Oversight Board/Meeting Minutes-2016-02-12|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-02-12T16:06:14 log] 

| width="20%" valign="top" |
'''2015'''

17 Dec
 [[Oversight Board/Meeting Minutes-2015-12-17|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-12-17T23:25:46 log] 

3 Nov
 [[Oversight Board/Meeting Minutes-2015-11-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-11-02T23:06:41 log] 

12 Oct
 [[Oversight Board/Meeting Minutes-2015-10-12|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-10-12T23:03:08 log] 

14 Sept
 [[Oversight Board/Meeting Minutes-2015-09-14|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-09-14T23:17:25 log] 

11 Aug
 [[Oversight Board/Meeting Minutes-2015-08-11|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-08-11T00:04:07 log] 

10 July
 [[Oversight Board/Meeting Minutes-2015-07-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-07-06T23:06:56 log] 

01 June
[[Oversight Board/Meeting Minutes-2015-06-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-06-01T23:06:01 log] 

04 May
[[Oversight Board/Meeting Minutes-2015-05-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-05-04T23:07:10 log] 

06 Apr
[[Oversight Board/Meeting Minutes-2015-04-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-04-06T23:10:04 log] 

02 Mar
[[Oversight Board/Meeting Minutes-2015-03-02 |minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-03-02T23:04:27 log] 

09 Feb
[[Oversight Board/Meeting Minutes-2015-02-09|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-02-09 log] 

14 Jan
[[Oversight Board/Meeting Minutes-2015-01-14|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-01-14 log] 

| width="20%" valign="top" |
'''2014'''

02 Dec
[[Oversight Board/Meeting Minutes-2014-12-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-12-02 log] 

04 Nov
[[Oversight Board/Meeting Minutes-2014-11-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-11-04 log] 

06 Oct
[[Oversight Board/Meeting Minutes-2014-10-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-10-07 log] 

11 Aug
[[Oversight Board/Meeting Minutes-2014-08-11|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-08-12T00:12:11 log]


8 Jul
[[Oversight Board/Meeting Minutes-2014-07-8|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-09T00:04:25 log]

17 Apr
[[Oversight Board/Meeting Minutes-2014-04-17|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-04-17T23:12:23 log]

03 Mar
[[Oversight Board/Meeting Minutes-2014-03-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-03-03 log]

05 Feb
[[Oversight Board/Meeting Minutes-2014-02-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-02-05T14:02:12 log]

06 Jan
[[Oversight Board/Meeting Minutes-2014-01-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-01-06T13:59:33 log]
|width="20%" valign="top"|
'''2013'''

02 Dec
[[Oversight Board/Meeting Minutes-2013-12-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-12-02T14:08:14 log]

04 Nov
[[Oversight Board/Meeting Minutes-2013-11-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-11-04T14:07:29 log]

18 Oct
[[Oversight Board/Meeting Minutes-2013-10-18|minutes]]

21 Mar
[[Oversight Board/Meeting Minutes-2013-03-21|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-03-21T22:08:55 log]

25 Feb
[[Oversight Board/Meeting Minutes-2013-02-25|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-02-25T23:15:58 log]

04 Feb
[[Oversight Board/Meeting Minutes-2013-02-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-02-04 log]

28 Jan
[[Oversight Board/Meeting Minutes-2013-01-28|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-01-28T23:00:42 log]

14 Jan
[[Oversight Board/Meeting Minutes-2013-01-14|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-01-14 log]

07 Jan
[[Oversight Board/Meeting Minutes-2013-01-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-01-07T23:06:56 log]

|width="20%" valign="top"|
'''2012'''

30 May
[[Oversight Board/Meeting Minutes-2012-05-30|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-30T21:08:10 log]

17 May
[[Oversight Board/Meeting Minutes-2012-05-17|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-17 log]

10 May
[[Oversight Board/Meeting Minutes-2012-05-10|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-10 log]

03 May
[[Oversight Board/Meeting Minutes-2012-05-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-03 log]

28 Feb
[[Oversight Board/Meeting Minutes-2012-02-28|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-02-28T22:30:53 log]

03 Jan
[[Oversight Board/Meeting Minutes-2012-01-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-01-03T21:12:16 log]
|}

{|
|width="20%" valign="top"|
'''2011'''

20 Dec
[[Oversight Board/Meeting Minutes-2011-12-20|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-12-20T21:03:04 log]

02 Dec
[[Oversight Board/Meeting Minutes-2011-12-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-12-02T15:01:02 log] [[Oversight Board/Meeting log Addendum-2011-12-02|+]]

10 Nov
(no quorum) [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-11-10 log]

20 Oct
([[Oversight Board/2011/Meeting Minutes-2011-10-20|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-10-23T15:03:50 log])

23 Sep
([[Oversight Board/2011/Meeting Minutes-2011-09-23|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-10-20T15:01:17 log])

16 Sep
([[Oversight Board/2011/Meeting Minutes-2011-09-16|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-09-16T15:03:05 log])

05 Aug
([[Oversight Board/2011/Meeting Minutes-2011-08-05|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-08-05T15:00:58 log])

09 Jun
([[Oversight Board/2011/Meeting Minutes-2011-06-09|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/2011-06-09#i_2671836 log])

08 May
([[Oversight Board/2011/Meeting Minutes-2011-05-08|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/2011-05-08#i_2665675 log])

21 Apr
([[Oversight Board/Meeting Minutes-2011-04-21|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-04-21T19:00:15 log (1)][http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-04-21T20:05:05 log (2)])

4 Mar
([[Oversight Board/2011/Meeting Minutes-2011-03-04|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-04T23:00:51 log])

17 Feb
([[Oversight Board/2011/Meeting Minutes-2011-02-17|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-17 log])

10 Feb
([[Oversight Board/2011/Meeting Minutes-2011-02-10|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-10 log])

13 Jan
([[Oversight Board/2011/Meeting Minutes-2011-01-13|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-01-13T20:03:31 log])

|width="20%" valign="top"|
'''2010'''

23 Dec
([[Oversight Board/2010/Meeting-log-2010-12-23|log]])

16 Dec
([[Oversight Board/2010/Meeting-log-2010-12-16|log]])

13 Dec
([[Oversight Board/2010/Meeting Minutes-2010-12-13|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-12-13T22:03:08 log])

01 Dec
([[Oversight Board/2010/Meeting Minutes-2010-12-01|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-12-01T17:03:11 log])


26 Oct
([[Oversight Board/2010/Meeting Minutes-2010-10-26|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-10-26T15:24:49 log])


28 Sep
([[Oversight Board/2010/Meeting Minutes-2010-09-28|minutes]], [[Oversight Board/Meeting log-2010-09-28|log]])


14 Sep
([[Oversight Board/2010/Meeting Minutes-2010-09-14|minutes]], [http://jita.sugarlabs.org/sugar-meeting/meetings/2010-09-14T15:16:44 log])


24 Aug
([[Oversight Board/2010/Meeting Minutes-2010-08-24|minutes]], [[Oversight Board/Meeting log-2010-08-24|log]])


11 Jul
[http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100711_0446.html discussion]


25 Jun
[http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100625_1103.html discussion]

04 Jun
([[Oversight Board/2010/Meeting Minutes-2010-06-04|minutes]], [[Oversight Board/2010/Meeting log-2010-06-04|log]])

14 May
([[Oversight Board/2010/Meeting Minutes-2010-05-14|minutes]], [[Oversight Board/2010/Meeting log-2010-05-14|log]])

07 May
([[Oversight Board/2010/Meeting Minutes-2010-05-07|minutes]], [[Oversight Board/2010/Meeting log-2010-05-07|log]])

26 Mar
([[Oversight Board/2010/Meeting Minutes-2010-03-26|minutes]], [[Oversight Board/2010/Meeting log-2010-03-26|log]])

12 Mar
([[Oversight Board/2010/Meeting Minutes-2010-03-12|minutes]], [[Oversight Board/2010/Meeting log-2010-03-12|log]])

05 Mar
([[Oversight Board/2010/Meeting Minutes-2010-03-05|minutes]], [[Oversight Board/2010/Meeting log-2010-03-05|log]])

26 Feb
([[Oversight Board/2010/Meeting Minutes-2010-02-26|minutes]], [[Oversight Board/2010/Meeting log-2010-02.26|log]])

05 Feb
([[Oversight Board/2010/Meeting Minutes-2010-02-05|minutes]], [[Oversight Board/2010/Meeting log-2010-02-05|log]])

29 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-29|minutes]], [[Oversight Board/2010/Meeting log-2010-01-29|log]])

22 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-22|minutes]], [[Oversight Board/2010/Meeting log-2010-01-22|log]])

15 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-15|minutes]], [[Oversight Board/2010/Meeting log-2010-01-15|log]])

08 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-08|minutes]], [[Oversight Board/2010/Meeting log-2010-01-08|log]])

|width="20%" valign="top"|
'''2009'''

30 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-30|minutes]], [[Oversight Board/2009/Meeting log-2009-12-30|log]])

23 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-23|minutes]], [[Oversight Board/2009/Meeting log-2009-12-23|log]])

18 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-18|minutes]], [[Oversight Board/2009/Meeting log-2009-12-18|log]])

11 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-11|minutes]], [[Oversight Board/2009/Meeting log-2009-12-11|log]])

04 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-04|minutes]], [[Oversight Board/2009/Meeting log-2009-12-04|log]])

20 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-20|minutes]], [[Oversight_Board/2009/Meeting_log-2009-11-20|log]])

13 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-13|minutes]], [[Oversight_Board/2009/Meeting_log-2009-11-13|log]])

06 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-06|minutes]], [[Oversight_Board/2009/Meeting_log-2009-11-06|log]])

30 Oct
([[Oversight Board/2009/Meeting Minutes-2009-10-30|minutes]], [[Oversight_Board/2009/Meeting_log-2009-10-30|log]])

25 Sep
([[Oversight Board/2009/Meeting Minutes-2009-09-25|minutes]], [[Oversight Board/2009/Meeting log-2009-09-25|log]])


28 Aug
([[Oversight Board/2009/Meeting Minutes-2009-08-28|minutes]], [[Oversight Board/Log-2009-08-28|log]])


10 Jul
([http://meeting.sugarlabs.org/sugar-meeting.minutes.20090710_0905.html minutes],
[http://meeting.sugarlabs.org/sugar-meeting.log.20090710_0905.html log])


06 Mar
([[Oversight Board/2009/Meeting Minutes-2009-03-06|minutes]])


13 Feb
([[Oversight Board/2009/Meeting Minutes-2009-02-13|minutes]], [[Oversight Board/2009/Log-2009-02-13|log]])


02 Feb
([[Oversight Board/2009/Meeting Minutes-2009-02-02|minutes]], [[Oversight Board/2009/Log-2009-02-02|log]])


|width="20%" valign="top"|
'''2008'''

12 Dec

([[Oversight Board/2008/Meeting Minutes-2008-12-12|minutes]], [[Oversight Board/2008/Log-2008-12-12|log]])


31 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-31|minutes]], [[Oversight Board/2008/Log-2008-10-31|log]])


17 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-17|minutes]], [[Oversight Board/2008/Log-2008-10-17|log]])


03 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-03|minutes]], [[Oversight Board/2008/Log-2008-10-03|log]])


19 Sep

([[Oversight Board/2008/Meeting Minutes-2008-09-19|minutes]], [[Oversight Board/2008/Log-2008-09-19|log]])


05 Sep

([[Oversight Board/2008/Meeting Minutes-2008-09-05|minutes]], [[Oversight Board/2008/Log-2008-09-05|log]])


01 Aug

([[Oversight Board/2008/Meeting Minutes-2008-08-01|minutes]], [[Oversight Board/2008/Log-2008-08-01|log]])


18 Jul

([[Oversight Board/2008/Meeting Minutes-2008-07-18|minutes]], [[Oversight Board/2008/Log-2008-07-18|log]])


30 Jun

([[Oversight Board/2008/Meeting_Minutes-2008-06-30|minutes]], [[Oversight Board/2008/Log-2008-06-30|log]])


|}

[[Category:Oversight board]]
[[Category:Meetings]]
[[Category:Meeting minutes]]
[[Category:Governance]]

User:Llaske

2021-02-17T21:33:04Z

Llaske:

My name is Lionel Laské. I'm member of SugarLabs Oversight Board since 2015. My github account is [https://github.com/llaske llaske].

I'm also board member and co-founder in 2008 of the [http://olpc-france.org OLPC France grassroot].

OLPC France launch and maintain from 2009 to 2018 a deployment of 200 XO-1/1.5 laptops in Madagascar on the [http://wiki.laptop.org/go/OLPC_Madagascar/Nosy_Komba Nosy Komba Island].

OLPC France launched also a small deployment of 50 XO-1.5 laptops in Saint-Denis (Paris suburb) between 2012 and 2014 and a deployment of 25 XO-4 laptops in Saint-Ouen (Paris suburb) in 2015-2016. Currently we hold a [http://sugarizer.org Sugarizer] deployment of 480 Android tablets in [[Sugarizer Saint-Ouen deployment|Saint-Ouen]].

OLPC France promote One Laptop Per Child philosophy, Sugar and open source software and is also a reproducible association based on [http://movecommons.org Move Commons philosophy] so all our way of working is fully transparent and documented [http://olpc-france.org/wiki/index.php/Association].

OLPC France organized three SugarCamp in Paris in 2009, 2011 and 2014.

OLPC France was closed in 2018 and reborn in 2019 with the name of Eduvelopers.

I'm the author of 8 Sugar activities [http://activities.sugarlabs.org/en/sugar/user/1454]. I'm also the author and the lead developer of [http://sugarizer.org Sugarizer], a port of Sugar on any device.

Finally I was mentor for SugarLabs during Google Summer of Code 2013 to 2020 and I was mentor for Google Code-In in 2015 to 2019.

Oversight Board/Minutes

2021-02-03T20:26:41Z

Llaske: /* Past meetings */

<noinclude>{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude>
__NOTOC__
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Oversight board holds regular monthly meetings.
</div>

=== Past meetings ===

Logs of meetings on the #sugar-meeting channel are available [http://meeting.sugarlabs.org/sugar-meeting/ here].

{|
| width="20%" valign="top" |
'''2021'''

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-01-06

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-01-20

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-02-03

{|
| width="20%" valign="top" |
'''2020'''

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-05-13

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-05-27

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-06-10

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-06-24

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-07-08

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-12-23

{|
| width="20%" valign="top" |
'''2019'''

04 Jan

[[Oversight_Board/Meeting_Minutes-2019-01-04|minutes]]
[[Oversight_Board/2019/meeting-log-2019-01-04|log]] 
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-01-04T20:00:43.html minutes]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-01-04T20:00:43 log]


01 Feb

[[Oversight_Board/Meeting_Minutes-2019-02-01|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-02-01T20:01:00.html minutes]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-02-01 log]


01 Mar

[[Oversight_Board/Meeting_Minutes-2019-03-01|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-03-01 log]


05 Apr

[[Oversight_Board/Meeting_Minutes-2019-04-05|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-04-05 log]


03 May

[[Oversight_Board/Meeting_Minutes-2019-05-03|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-05-03 log]


| width="20%" valign="top" |
'''2018'''

07 Dec
 [[Oversight_Board/2018/meeting-log-2018-12-07|log]]

03 Nov
 [[Oversight_Board/2018/meeting-log-2018-11-03|log]]

05 Oct
 [[Oversight_Board/2010/Meeting-log-2018-10-05|log]]

07 Sept
 [[Oversight_Board/2010/Meeting-log-2018-09-07|log]]

03 Aug
 [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-08-03T20:00:00 log]

06 July
 [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-07-06T20:11:29 log]

01 Jun
 [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-06-01T20:07:40 log]

04 May
 [[Oversight Board/Meeting Minutes-2018-05-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-05-04T20:00:12 log]

06 Apr
 [[Oversight Board/Meeting Minutes-2018-04-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-04-06 log]

02 Mar
 [[Oversight Board/Meeting Minutes-2018-03-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-02 log]

02 Feb
 [[Oversight Board/Meeting Minutes-2018-02-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-02-02 log]

05 Jan
 [[Oversight Board/Meeting Minutes-2018-01-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-05 log]

| width="20%" valign="top" |
'''2017'''

01 Dec
 [[Oversight Board/Meeting Minutes-2017-12-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-12-01 log]

03 Nov
 [[Oversight Board/Meeting Minutes-2017-11-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-11-03 log]

06 Oct
 [[Oversight Board/Meeting Minutes-2017-10-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-10-06T19:00:31 log]

01 Sep
 [[Oversight Board/Meeting Minutes-2017-09-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01T19:10:08 log]

04 Aug
 [[Oversight Board/Meeting Minutes-2017-08-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24 log]

07 Jul
 [[Oversight Board/Meeting Minutes-2017-07-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-07-07 log]

02 Jun
 [[Oversight Board/Meeting Minutes-2017-06-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-06-02 log]

05 May
 [[Oversight Board/Meeting Minutes-2017-05-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-05-05 log]

07 Apr
 [[Oversight Board/Meeting Minutes-2017-04-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-04-07T19:03:42 log]

03 Mar
 [[Oversight Board/Meeting Minutes-2017-03-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-03-03 log]

03 Feb
 [[Oversight Board/Meeting Minutes-2017-02-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-02-03 log]

06 Jan
 [[Oversight Board/Meeting Minutes-2017-01-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-01-06T19:07:40 log]

|}

{|
| width="20%" valign="top" |
'''2016'''

04 Nov
 [[Oversight Board/Meeting Minutes-2016-11-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-11-04T19:03:35 log]

07 Oct
 [[Oversight Board/Meeting Minutes-2016-10-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-10-07 log]

02 Sep
 [[Oversight Board/Meeting Minutes-2016-09-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-09-02T19:03:42 log] 

05 Aug
 [[Oversight Board/Meeting Minutes-2016-08-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-08-05 log] 

01 Jul
 [[Oversight Board/Meeting Minutes-2016-07-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-07-01T19:00:23 log] 

03 Jun
 [[Oversight Board/Meeting Minutes-2016-06-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-06-03T19:01:08 log] 

06 May
 [[Oversight Board/Meeting Minutes-2016-05-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-05-06T16:02:18 log] 

01 Apr
 [[Oversight Board/Meeting Minutes-2016-04-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-04-01 log] 

04 Mar
 [[Oversight Board/Meeting Minutes-2016-03-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-03-04 log] 

12 Feb
 [[Oversight Board/Meeting Minutes-2016-02-12|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-02-12T16:06:14 log] 

| width="20%" valign="top" |
'''2015'''

17 Dec
 [[Oversight Board/Meeting Minutes-2015-12-17|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-12-17T23:25:46 log] 

3 Nov
 [[Oversight Board/Meeting Minutes-2015-11-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-11-02T23:06:41 log] 

12 Oct
 [[Oversight Board/Meeting Minutes-2015-10-12|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-10-12T23:03:08 log] 

14 Sept
 [[Oversight Board/Meeting Minutes-2015-09-14|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-09-14T23:17:25 log] 

11 Aug
 [[Oversight Board/Meeting Minutes-2015-08-11|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-08-11T00:04:07 log] 

10 July
 [[Oversight Board/Meeting Minutes-2015-07-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-07-06T23:06:56 log] 

01 June
[[Oversight Board/Meeting Minutes-2015-06-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-06-01T23:06:01 log] 

04 May
[[Oversight Board/Meeting Minutes-2015-05-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-05-04T23:07:10 log] 

06 Apr
[[Oversight Board/Meeting Minutes-2015-04-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-04-06T23:10:04 log] 

02 Mar
[[Oversight Board/Meeting Minutes-2015-03-02 |minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-03-02T23:04:27 log] 

09 Feb
[[Oversight Board/Meeting Minutes-2015-02-09|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-02-09 log] 

14 Jan
[[Oversight Board/Meeting Minutes-2015-01-14|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-01-14 log] 

| width="20%" valign="top" |
'''2014'''

02 Dec
[[Oversight Board/Meeting Minutes-2014-12-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-12-02 log] 

04 Nov
[[Oversight Board/Meeting Minutes-2014-11-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-11-04 log] 

06 Oct
[[Oversight Board/Meeting Minutes-2014-10-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-10-07 log] 

11 Aug
[[Oversight Board/Meeting Minutes-2014-08-11|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-08-12T00:12:11 log]


8 Jul
[[Oversight Board/Meeting Minutes-2014-07-8|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-09T00:04:25 log]

17 Apr
[[Oversight Board/Meeting Minutes-2014-04-17|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-04-17T23:12:23 log]

03 Mar
[[Oversight Board/Meeting Minutes-2014-03-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-03-03 log]

05 Feb
[[Oversight Board/Meeting Minutes-2014-02-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-02-05T14:02:12 log]

06 Jan
[[Oversight Board/Meeting Minutes-2014-01-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-01-06T13:59:33 log]
|width="20%" valign="top"|
'''2013'''

02 Dec
[[Oversight Board/Meeting Minutes-2013-12-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-12-02T14:08:14 log]

04 Nov
[[Oversight Board/Meeting Minutes-2013-11-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-11-04T14:07:29 log]

18 Oct
[[Oversight Board/Meeting Minutes-2013-10-18|minutes]]

21 Mar
[[Oversight Board/Meeting Minutes-2013-03-21|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-03-21T22:08:55 log]

25 Feb
[[Oversight Board/Meeting Minutes-2013-02-25|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-02-25T23:15:58 log]

04 Feb
[[Oversight Board/Meeting Minutes-2013-02-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-02-04 log]

28 Jan
[[Oversight Board/Meeting Minutes-2013-01-28|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-01-28T23:00:42 log]

14 Jan
[[Oversight Board/Meeting Minutes-2013-01-14|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-01-14 log]

07 Jan
[[Oversight Board/Meeting Minutes-2013-01-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-01-07T23:06:56 log]

|width="20%" valign="top"|
'''2012'''

30 May
[[Oversight Board/Meeting Minutes-2012-05-30|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-30T21:08:10 log]

17 May
[[Oversight Board/Meeting Minutes-2012-05-17|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-17 log]

10 May
[[Oversight Board/Meeting Minutes-2012-05-10|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-10 log]

03 May
[[Oversight Board/Meeting Minutes-2012-05-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-03 log]

28 Feb
[[Oversight Board/Meeting Minutes-2012-02-28|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-02-28T22:30:53 log]

03 Jan
[[Oversight Board/Meeting Minutes-2012-01-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-01-03T21:12:16 log]
|}

{|
|width="20%" valign="top"|
'''2011'''

20 Dec
[[Oversight Board/Meeting Minutes-2011-12-20|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-12-20T21:03:04 log]

02 Dec
[[Oversight Board/Meeting Minutes-2011-12-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-12-02T15:01:02 log] [[Oversight Board/Meeting log Addendum-2011-12-02|+]]

10 Nov
(no quorum) [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-11-10 log]

20 Oct
([[Oversight Board/2011/Meeting Minutes-2011-10-20|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-10-23T15:03:50 log])

23 Sep
([[Oversight Board/2011/Meeting Minutes-2011-09-23|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-10-20T15:01:17 log])

16 Sep
([[Oversight Board/2011/Meeting Minutes-2011-09-16|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-09-16T15:03:05 log])

05 Aug
([[Oversight Board/2011/Meeting Minutes-2011-08-05|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-08-05T15:00:58 log])

09 Jun
([[Oversight Board/2011/Meeting Minutes-2011-06-09|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/2011-06-09#i_2671836 log])

08 May
([[Oversight Board/2011/Meeting Minutes-2011-05-08|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/2011-05-08#i_2665675 log])

21 Apr
([[Oversight Board/Meeting Minutes-2011-04-21|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-04-21T19:00:15 log (1)][http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-04-21T20:05:05 log (2)])

4 Mar
([[Oversight Board/2011/Meeting Minutes-2011-03-04|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-04T23:00:51 log])

17 Feb
([[Oversight Board/2011/Meeting Minutes-2011-02-17|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-17 log])

10 Feb
([[Oversight Board/2011/Meeting Minutes-2011-02-10|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-10 log])

13 Jan
([[Oversight Board/2011/Meeting Minutes-2011-01-13|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-01-13T20:03:31 log])

|width="20%" valign="top"|
'''2010'''

23 Dec
([[Oversight Board/2010/Meeting-log-2010-12-23|log]])

16 Dec
([[Oversight Board/2010/Meeting-log-2010-12-16|log]])

13 Dec
([[Oversight Board/2010/Meeting Minutes-2010-12-13|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-12-13T22:03:08 log])

01 Dec
([[Oversight Board/2010/Meeting Minutes-2010-12-01|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-12-01T17:03:11 log])


26 Oct
([[Oversight Board/2010/Meeting Minutes-2010-10-26|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-10-26T15:24:49 log])


28 Sep
([[Oversight Board/2010/Meeting Minutes-2010-09-28|minutes]], [[Oversight Board/Meeting log-2010-09-28|log]])


14 Sep
([[Oversight Board/2010/Meeting Minutes-2010-09-14|minutes]], [http://jita.sugarlabs.org/sugar-meeting/meetings/2010-09-14T15:16:44 log])


24 Aug
([[Oversight Board/2010/Meeting Minutes-2010-08-24|minutes]], [[Oversight Board/Meeting log-2010-08-24|log]])


11 Jul
[http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100711_0446.html discussion]


25 Jun
[http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100625_1103.html discussion]

04 Jun
([[Oversight Board/2010/Meeting Minutes-2010-06-04|minutes]], [[Oversight Board/2010/Meeting log-2010-06-04|log]])

14 May
([[Oversight Board/2010/Meeting Minutes-2010-05-14|minutes]], [[Oversight Board/2010/Meeting log-2010-05-14|log]])

07 May
([[Oversight Board/2010/Meeting Minutes-2010-05-07|minutes]], [[Oversight Board/2010/Meeting log-2010-05-07|log]])

26 Mar
([[Oversight Board/2010/Meeting Minutes-2010-03-26|minutes]], [[Oversight Board/2010/Meeting log-2010-03-26|log]])

12 Mar
([[Oversight Board/2010/Meeting Minutes-2010-03-12|minutes]], [[Oversight Board/2010/Meeting log-2010-03-12|log]])

05 Mar
([[Oversight Board/2010/Meeting Minutes-2010-03-05|minutes]], [[Oversight Board/2010/Meeting log-2010-03-05|log]])

26 Feb
([[Oversight Board/2010/Meeting Minutes-2010-02-26|minutes]], [[Oversight Board/2010/Meeting log-2010-02.26|log]])

05 Feb
([[Oversight Board/2010/Meeting Minutes-2010-02-05|minutes]], [[Oversight Board/2010/Meeting log-2010-02-05|log]])

29 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-29|minutes]], [[Oversight Board/2010/Meeting log-2010-01-29|log]])

22 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-22|minutes]], [[Oversight Board/2010/Meeting log-2010-01-22|log]])

15 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-15|minutes]], [[Oversight Board/2010/Meeting log-2010-01-15|log]])

08 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-08|minutes]], [[Oversight Board/2010/Meeting log-2010-01-08|log]])

|width="20%" valign="top"|
'''2009'''

30 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-30|minutes]], [[Oversight Board/2009/Meeting log-2009-12-30|log]])

23 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-23|minutes]], [[Oversight Board/2009/Meeting log-2009-12-23|log]])

18 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-18|minutes]], [[Oversight Board/2009/Meeting log-2009-12-18|log]])

11 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-11|minutes]], [[Oversight Board/2009/Meeting log-2009-12-11|log]])

04 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-04|minutes]], [[Oversight Board/2009/Meeting log-2009-12-04|log]])

20 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-20|minutes]], [[Oversight_Board/2009/Meeting_log-2009-11-20|log]])

13 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-13|minutes]], [[Oversight_Board/2009/Meeting_log-2009-11-13|log]])

06 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-06|minutes]], [[Oversight_Board/2009/Meeting_log-2009-11-06|log]])

30 Oct
([[Oversight Board/2009/Meeting Minutes-2009-10-30|minutes]], [[Oversight_Board/2009/Meeting_log-2009-10-30|log]])

25 Sep
([[Oversight Board/2009/Meeting Minutes-2009-09-25|minutes]], [[Oversight Board/2009/Meeting log-2009-09-25|log]])


28 Aug
([[Oversight Board/2009/Meeting Minutes-2009-08-28|minutes]], [[Oversight Board/Log-2009-08-28|log]])


10 Jul
([http://meeting.sugarlabs.org/sugar-meeting.minutes.20090710_0905.html minutes],
[http://meeting.sugarlabs.org/sugar-meeting.log.20090710_0905.html log])


06 Mar
([[Oversight Board/2009/Meeting Minutes-2009-03-06|minutes]])


13 Feb
([[Oversight Board/2009/Meeting Minutes-2009-02-13|minutes]], [[Oversight Board/2009/Log-2009-02-13|log]])


02 Feb
([[Oversight Board/2009/Meeting Minutes-2009-02-02|minutes]], [[Oversight Board/2009/Log-2009-02-02|log]])


|width="20%" valign="top"|
'''2008'''

12 Dec

([[Oversight Board/2008/Meeting Minutes-2008-12-12|minutes]], [[Oversight Board/2008/Log-2008-12-12|log]])


31 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-31|minutes]], [[Oversight Board/2008/Log-2008-10-31|log]])


17 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-17|minutes]], [[Oversight Board/2008/Log-2008-10-17|log]])


03 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-03|minutes]], [[Oversight Board/2008/Log-2008-10-03|log]])


19 Sep

([[Oversight Board/2008/Meeting Minutes-2008-09-19|minutes]], [[Oversight Board/2008/Log-2008-09-19|log]])


05 Sep

([[Oversight Board/2008/Meeting Minutes-2008-09-05|minutes]], [[Oversight Board/2008/Log-2008-09-05|log]])


01 Aug

([[Oversight Board/2008/Meeting Minutes-2008-08-01|minutes]], [[Oversight Board/2008/Log-2008-08-01|log]])


18 Jul

([[Oversight Board/2008/Meeting Minutes-2008-07-18|minutes]], [[Oversight Board/2008/Log-2008-07-18|log]])


30 Jun

([[Oversight Board/2008/Meeting_Minutes-2008-06-30|minutes]], [[Oversight Board/2008/Log-2008-06-30|log]])


|}

[[Category:Oversight board]]
[[Category:Meetings]]
[[Category:Meeting minutes]]
[[Category:Governance]]

Oversight Board/Next meeting

2021-02-03T17:19:40Z

Llaske: /* Next meeting */

=== Next meeting===

* Wednesday, 2021-02-03 at 19:30 UTC, (per agreed motion 2020-06, "meet every two weeks"),
* on Jitsi

==== Agenda items ====

Current draft is published at https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-02-03 (which will later become the minutes for the meeting).

Our agenda is typically negotiated as first item of business in the meeting. Add topics by either;

* write to sugar-devel and slobs at lists dot sugarlabs dot org (the most transparent method), or;
* write to slobs at lists dot sugarlabs dot org (a transparent method), or;
* write to a member of the oversight board (a non-transparent method).
* editing the wiki page for the agenda yourself (before the meeting).

Standing agenda items;

* pending motions from e-mail,
* reports from project representative (Conservancy liaison),
* reports from Ombudsman,
* reports from project teams, e.g. administrators of Google Code-in or Google Summer of Code,
* discussion of goals,

Oversight Board/Minutes

2021-02-03T17:17:34Z

Llaske: Add 2021 meetings

<noinclude>{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude>
__NOTOC__
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Oversight board holds regular monthly meetings.
</div>

=== Past meetings ===

Logs of meetings on the #sugar-meeting channel are available [http://meeting.sugarlabs.org/sugar-meeting/ here].

{|
| width="20%" valign="top" |
'''2021'''

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-01-06

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-01-20

{|
| width="20%" valign="top" |
'''2020'''

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-05-13

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-05-27

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-06-10

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-06-24

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-07-08

https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-12-23

{|
| width="20%" valign="top" |
'''2019'''

04 Jan

[[Oversight_Board/Meeting_Minutes-2019-01-04|minutes]]
[[Oversight_Board/2019/meeting-log-2019-01-04|log]] 
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-01-04T20:00:43.html minutes]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-01-04T20:00:43 log]


01 Feb

[[Oversight_Board/Meeting_Minutes-2019-02-01|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-02-01T20:01:00.html minutes]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-02-01 log]


01 Mar

[[Oversight_Board/Meeting_Minutes-2019-03-01|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-03-01 log]


05 Apr

[[Oversight_Board/Meeting_Minutes-2019-04-05|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-04-05 log]


03 May

[[Oversight_Board/Meeting_Minutes-2019-05-03|minutes]]
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2019-05-03 log]


| width="20%" valign="top" |
'''2018'''

07 Dec
 [[Oversight_Board/2018/meeting-log-2018-12-07|log]]

03 Nov
 [[Oversight_Board/2018/meeting-log-2018-11-03|log]]

05 Oct
 [[Oversight_Board/2010/Meeting-log-2018-10-05|log]]

07 Sept
 [[Oversight_Board/2010/Meeting-log-2018-09-07|log]]

03 Aug
 [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-08-03T20:00:00 log]

06 July
 [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-07-06T20:11:29 log]

01 Jun
 [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-06-01T20:07:40 log]

04 May
 [[Oversight Board/Meeting Minutes-2018-05-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-05-04T20:00:12 log]

06 Apr
 [[Oversight Board/Meeting Minutes-2018-04-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-04-06 log]

02 Mar
 [[Oversight Board/Meeting Minutes-2018-03-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-02 log]

02 Feb
 [[Oversight Board/Meeting Minutes-2018-02-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-02-02 log]

05 Jan
 [[Oversight Board/Meeting Minutes-2018-01-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-05 log]

| width="20%" valign="top" |
'''2017'''

01 Dec
 [[Oversight Board/Meeting Minutes-2017-12-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-12-01 log]

03 Nov
 [[Oversight Board/Meeting Minutes-2017-11-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-11-03 log]

06 Oct
 [[Oversight Board/Meeting Minutes-2017-10-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-10-06T19:00:31 log]

01 Sep
 [[Oversight Board/Meeting Minutes-2017-09-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01T19:10:08 log]

04 Aug
 [[Oversight Board/Meeting Minutes-2017-08-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24 log]

07 Jul
 [[Oversight Board/Meeting Minutes-2017-07-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-07-07 log]

02 Jun
 [[Oversight Board/Meeting Minutes-2017-06-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-06-02 log]

05 May
 [[Oversight Board/Meeting Minutes-2017-05-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-05-05 log]

07 Apr
 [[Oversight Board/Meeting Minutes-2017-04-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-04-07T19:03:42 log]

03 Mar
 [[Oversight Board/Meeting Minutes-2017-03-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-03-03 log]

03 Feb
 [[Oversight Board/Meeting Minutes-2017-02-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-02-03 log]

06 Jan
 [[Oversight Board/Meeting Minutes-2017-01-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-01-06T19:07:40 log]

|}

{|
| width="20%" valign="top" |
'''2016'''

04 Nov
 [[Oversight Board/Meeting Minutes-2016-11-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-11-04T19:03:35 log]

07 Oct
 [[Oversight Board/Meeting Minutes-2016-10-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-10-07 log]

02 Sep
 [[Oversight Board/Meeting Minutes-2016-09-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-09-02T19:03:42 log] 

05 Aug
 [[Oversight Board/Meeting Minutes-2016-08-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-08-05 log] 

01 Jul
 [[Oversight Board/Meeting Minutes-2016-07-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-07-01T19:00:23 log] 

03 Jun
 [[Oversight Board/Meeting Minutes-2016-06-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-06-03T19:01:08 log] 

06 May
 [[Oversight Board/Meeting Minutes-2016-05-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-05-06T16:02:18 log] 

01 Apr
 [[Oversight Board/Meeting Minutes-2016-04-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-04-01 log] 

04 Mar
 [[Oversight Board/Meeting Minutes-2016-03-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-03-04 log] 

12 Feb
 [[Oversight Board/Meeting Minutes-2016-02-12|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-02-12T16:06:14 log] 

| width="20%" valign="top" |
'''2015'''

17 Dec
 [[Oversight Board/Meeting Minutes-2015-12-17|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-12-17T23:25:46 log] 

3 Nov
 [[Oversight Board/Meeting Minutes-2015-11-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-11-02T23:06:41 log] 

12 Oct
 [[Oversight Board/Meeting Minutes-2015-10-12|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-10-12T23:03:08 log] 

14 Sept
 [[Oversight Board/Meeting Minutes-2015-09-14|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-09-14T23:17:25 log] 

11 Aug
 [[Oversight Board/Meeting Minutes-2015-08-11|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-08-11T00:04:07 log] 

10 July
 [[Oversight Board/Meeting Minutes-2015-07-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-07-06T23:06:56 log] 

01 June
[[Oversight Board/Meeting Minutes-2015-06-01|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-06-01T23:06:01 log] 

04 May
[[Oversight Board/Meeting Minutes-2015-05-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-05-04T23:07:10 log] 

06 Apr
[[Oversight Board/Meeting Minutes-2015-04-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-04-06T23:10:04 log] 

02 Mar
[[Oversight Board/Meeting Minutes-2015-03-02 |minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-03-02T23:04:27 log] 

09 Feb
[[Oversight Board/Meeting Minutes-2015-02-09|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-02-09 log] 

14 Jan
[[Oversight Board/Meeting Minutes-2015-01-14|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2015-01-14 log] 

| width="20%" valign="top" |
'''2014'''

02 Dec
[[Oversight Board/Meeting Minutes-2014-12-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-12-02 log] 

04 Nov
[[Oversight Board/Meeting Minutes-2014-11-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-11-04 log] 

06 Oct
[[Oversight Board/Meeting Minutes-2014-10-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-10-07 log] 

11 Aug
[[Oversight Board/Meeting Minutes-2014-08-11|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-08-12T00:12:11 log]


8 Jul
[[Oversight Board/Meeting Minutes-2014-07-8|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-09T00:04:25 log]

17 Apr
[[Oversight Board/Meeting Minutes-2014-04-17|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-04-17T23:12:23 log]

03 Mar
[[Oversight Board/Meeting Minutes-2014-03-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-03-03 log]

05 Feb
[[Oversight Board/Meeting Minutes-2014-02-05|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-02-05T14:02:12 log]

06 Jan
[[Oversight Board/Meeting Minutes-2014-01-06|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-01-06T13:59:33 log]
|width="20%" valign="top"|
'''2013'''

02 Dec
[[Oversight Board/Meeting Minutes-2013-12-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-12-02T14:08:14 log]

04 Nov
[[Oversight Board/Meeting Minutes-2013-11-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-11-04T14:07:29 log]

18 Oct
[[Oversight Board/Meeting Minutes-2013-10-18|minutes]]

21 Mar
[[Oversight Board/Meeting Minutes-2013-03-21|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-03-21T22:08:55 log]

25 Feb
[[Oversight Board/Meeting Minutes-2013-02-25|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-02-25T23:15:58 log]

04 Feb
[[Oversight Board/Meeting Minutes-2013-02-04|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-02-04 log]

28 Jan
[[Oversight Board/Meeting Minutes-2013-01-28|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-01-28T23:00:42 log]

14 Jan
[[Oversight Board/Meeting Minutes-2013-01-14|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-01-14 log]

07 Jan
[[Oversight Board/Meeting Minutes-2013-01-07|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2013-01-07T23:06:56 log]

|width="20%" valign="top"|
'''2012'''

30 May
[[Oversight Board/Meeting Minutes-2012-05-30|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-30T21:08:10 log]

17 May
[[Oversight Board/Meeting Minutes-2012-05-17|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-17 log]

10 May
[[Oversight Board/Meeting Minutes-2012-05-10|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-10 log]

03 May
[[Oversight Board/Meeting Minutes-2012-05-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-03 log]

28 Feb
[[Oversight Board/Meeting Minutes-2012-02-28|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-02-28T22:30:53 log]

03 Jan
[[Oversight Board/Meeting Minutes-2012-01-03|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-01-03T21:12:16 log]
|}

{|
|width="20%" valign="top"|
'''2011'''

20 Dec
[[Oversight Board/Meeting Minutes-2011-12-20|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-12-20T21:03:04 log]

02 Dec
[[Oversight Board/Meeting Minutes-2011-12-02|minutes]] [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-12-02T15:01:02 log] [[Oversight Board/Meeting log Addendum-2011-12-02|+]]

10 Nov
(no quorum) [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-11-10 log]

20 Oct
([[Oversight Board/2011/Meeting Minutes-2011-10-20|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-10-23T15:03:50 log])

23 Sep
([[Oversight Board/2011/Meeting Minutes-2011-09-23|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-10-20T15:01:17 log])

16 Sep
([[Oversight Board/2011/Meeting Minutes-2011-09-16|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-09-16T15:03:05 log])

05 Aug
([[Oversight Board/2011/Meeting Minutes-2011-08-05|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-08-05T15:00:58 log])

09 Jun
([[Oversight Board/2011/Meeting Minutes-2011-06-09|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/2011-06-09#i_2671836 log])

08 May
([[Oversight Board/2011/Meeting Minutes-2011-05-08|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/2011-05-08#i_2665675 log])

21 Apr
([[Oversight Board/Meeting Minutes-2011-04-21|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-04-21T19:00:15 log (1)][http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-04-21T20:05:05 log (2)])

4 Mar
([[Oversight Board/2011/Meeting Minutes-2011-03-04|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-04T23:00:51 log])

17 Feb
([[Oversight Board/2011/Meeting Minutes-2011-02-17|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-17 log])

10 Feb
([[Oversight Board/2011/Meeting Minutes-2011-02-10|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-10 log])

13 Jan
([[Oversight Board/2011/Meeting Minutes-2011-01-13|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-01-13T20:03:31 log])

|width="20%" valign="top"|
'''2010'''

23 Dec
([[Oversight Board/2010/Meeting-log-2010-12-23|log]])

16 Dec
([[Oversight Board/2010/Meeting-log-2010-12-16|log]])

13 Dec
([[Oversight Board/2010/Meeting Minutes-2010-12-13|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-12-13T22:03:08 log])

01 Dec
([[Oversight Board/2010/Meeting Minutes-2010-12-01|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-12-01T17:03:11 log])


26 Oct
([[Oversight Board/2010/Meeting Minutes-2010-10-26|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-10-26T15:24:49 log])


28 Sep
([[Oversight Board/2010/Meeting Minutes-2010-09-28|minutes]], [[Oversight Board/Meeting log-2010-09-28|log]])


14 Sep
([[Oversight Board/2010/Meeting Minutes-2010-09-14|minutes]], [http://jita.sugarlabs.org/sugar-meeting/meetings/2010-09-14T15:16:44 log])


24 Aug
([[Oversight Board/2010/Meeting Minutes-2010-08-24|minutes]], [[Oversight Board/Meeting log-2010-08-24|log]])


11 Jul
[http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100711_0446.html discussion]


25 Jun
[http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100625_1103.html discussion]

04 Jun
([[Oversight Board/2010/Meeting Minutes-2010-06-04|minutes]], [[Oversight Board/2010/Meeting log-2010-06-04|log]])

14 May
([[Oversight Board/2010/Meeting Minutes-2010-05-14|minutes]], [[Oversight Board/2010/Meeting log-2010-05-14|log]])

07 May
([[Oversight Board/2010/Meeting Minutes-2010-05-07|minutes]], [[Oversight Board/2010/Meeting log-2010-05-07|log]])

26 Mar
([[Oversight Board/2010/Meeting Minutes-2010-03-26|minutes]], [[Oversight Board/2010/Meeting log-2010-03-26|log]])

12 Mar
([[Oversight Board/2010/Meeting Minutes-2010-03-12|minutes]], [[Oversight Board/2010/Meeting log-2010-03-12|log]])

05 Mar
([[Oversight Board/2010/Meeting Minutes-2010-03-05|minutes]], [[Oversight Board/2010/Meeting log-2010-03-05|log]])

26 Feb
([[Oversight Board/2010/Meeting Minutes-2010-02-26|minutes]], [[Oversight Board/2010/Meeting log-2010-02.26|log]])

05 Feb
([[Oversight Board/2010/Meeting Minutes-2010-02-05|minutes]], [[Oversight Board/2010/Meeting log-2010-02-05|log]])

29 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-29|minutes]], [[Oversight Board/2010/Meeting log-2010-01-29|log]])

22 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-22|minutes]], [[Oversight Board/2010/Meeting log-2010-01-22|log]])

15 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-15|minutes]], [[Oversight Board/2010/Meeting log-2010-01-15|log]])

08 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-08|minutes]], [[Oversight Board/2010/Meeting log-2010-01-08|log]])

|width="20%" valign="top"|
'''2009'''

30 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-30|minutes]], [[Oversight Board/2009/Meeting log-2009-12-30|log]])

23 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-23|minutes]], [[Oversight Board/2009/Meeting log-2009-12-23|log]])

18 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-18|minutes]], [[Oversight Board/2009/Meeting log-2009-12-18|log]])

11 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-11|minutes]], [[Oversight Board/2009/Meeting log-2009-12-11|log]])

04 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-04|minutes]], [[Oversight Board/2009/Meeting log-2009-12-04|log]])

20 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-20|minutes]], [[Oversight_Board/2009/Meeting_log-2009-11-20|log]])

13 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-13|minutes]], [[Oversight_Board/2009/Meeting_log-2009-11-13|log]])

06 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-06|minutes]], [[Oversight_Board/2009/Meeting_log-2009-11-06|log]])

30 Oct
([[Oversight Board/2009/Meeting Minutes-2009-10-30|minutes]], [[Oversight_Board/2009/Meeting_log-2009-10-30|log]])

25 Sep
([[Oversight Board/2009/Meeting Minutes-2009-09-25|minutes]], [[Oversight Board/2009/Meeting log-2009-09-25|log]])


28 Aug
([[Oversight Board/2009/Meeting Minutes-2009-08-28|minutes]], [[Oversight Board/Log-2009-08-28|log]])


10 Jul
([http://meeting.sugarlabs.org/sugar-meeting.minutes.20090710_0905.html minutes],
[http://meeting.sugarlabs.org/sugar-meeting.log.20090710_0905.html log])


06 Mar
([[Oversight Board/2009/Meeting Minutes-2009-03-06|minutes]])


13 Feb
([[Oversight Board/2009/Meeting Minutes-2009-02-13|minutes]], [[Oversight Board/2009/Log-2009-02-13|log]])


02 Feb
([[Oversight Board/2009/Meeting Minutes-2009-02-02|minutes]], [[Oversight Board/2009/Log-2009-02-02|log]])


|width="20%" valign="top"|
'''2008'''

12 Dec

([[Oversight Board/2008/Meeting Minutes-2008-12-12|minutes]], [[Oversight Board/2008/Log-2008-12-12|log]])


31 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-31|minutes]], [[Oversight Board/2008/Log-2008-10-31|log]])


17 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-17|minutes]], [[Oversight Board/2008/Log-2008-10-17|log]])


03 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-03|minutes]], [[Oversight Board/2008/Log-2008-10-03|log]])


19 Sep

([[Oversight Board/2008/Meeting Minutes-2008-09-19|minutes]], [[Oversight Board/2008/Log-2008-09-19|log]])


05 Sep

([[Oversight Board/2008/Meeting Minutes-2008-09-05|minutes]], [[Oversight Board/2008/Log-2008-09-05|log]])


01 Aug

([[Oversight Board/2008/Meeting Minutes-2008-08-01|minutes]], [[Oversight Board/2008/Log-2008-08-01|log]])


18 Jul

([[Oversight Board/2008/Meeting Minutes-2008-07-18|minutes]], [[Oversight Board/2008/Log-2008-07-18|log]])


30 Jun

([[Oversight Board/2008/Meeting_Minutes-2008-06-30|minutes]], [[Oversight Board/2008/Log-2008-06-30|log]])


|}

[[Category:Oversight board]]
[[Category:Meetings]]
[[Category:Meeting minutes]]
[[Category:Governance]]

Oversight Board/Meeting Minutes-2021-01-20

2021-01-21T16:38:13Z

Llaske: /* Sugar Labs Monthly Events Discussion */

== Meeting Minutes ==

Date: 2021-01-20

=== Participants ===
Jui
Perrie
Lionel
Walter
Claudia

Samson

=== Role ===
Alex will continue to participate in the board. We need confirmation from Alex on whether or not he will continue to be executive director.
Martin Guy has agreed to manage finances.

=== Report from project representative (Conservancy liaison) ===
Claudia is in communication with Alex to complete the W9 form requested by Conservancy.

=== Google Code-in Replacement Report ===
The following document was created during the Jan 13 meeting. More information will be added in the following few days: https://docs.google.com/document/d/1AZE9xL7AWnwHjQLE8zb6L-hgtdENjLPefKtuEYxhz7U/edit

We spoke about including this topic during regular meeting times to facilitate participation. Sansom will look into the possibility.
(Samson)

=== Sugar Labs Monthly Events Discussion ===
We will aim to share monthly learning packages to support learners around the world, in particular those who are affected by COVID pandemic. We will curate and create learning packages for a diverse groups of learners that includes learners of different ages, interests and access to technologies.

We looked at the different ideas:
* More than 20 things to do with Turtle Art (paper by Walter, Cynthia and Claudia): https://www.academia.edu/9509368/_More_than_Twenty_Things_to_Do_in_Turtle_Blocks
* Full STEAM Ahead from MIT: https://fullsteam.mit.edu/week-5-package-the-world-around-us/

We will invite others to contribute and activate the community:
* Sdenka (Peru) http://wiki.laptop.org/go/Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom
* Guzman (Uruguay) http://smarterphysics.blogspot.com/p/olpc-xo.html
* Walter/Claudia (US) https://wiki.sugarlabs.org/go/Math4Team/Florida

Topics for the monthly packages:
* Music (Activities: MusicBlocks)
* Storytelling (Activities: Fototoons, Story, Turtle Block)
* Physics ?
* Computation/Math (Abacus)

Where do we store/display pictures or projects shared by the learners?

We are aiming to begin on Feb 15, 2021.

(Claudia)

=== Communication Channels: Discord Discussion ===
Samson was not able to get in touch with Alex.
Walter talked to Alex and reported that Discord is not an open source platform. He will do additional research on alternative tools.

=== Time and Place of Next Meeting ===
3 Feb in JITSI

=== Closing ===

Oversight Board/Meeting Minutes-2020-12-09

2020-12-09T20:56:34Z

Llaske:

== Agenda for SLOBs Meeting ==
2020-12-09 at 19:30 UTC on Jitsi

=== Role Call ===

SLOBs Present: Devin, Walter, Claudia, Lionel

SL Inc. Present: Devin, Walter, Claudia, Samson, Lionel

=== Advising with Aaron Williamson ===

Any liabilities that we should know about?
* Director's and Officer's Insurance
D&O ~$103

Any insurance that we should know about with regard to working with minors?
* General Liability

CORI ? (Perhaps only for workshops)

What should we know about the (...)?

Outgoing board members (Delaware) will resign, and the remaining members of the Delaware org will vote to appoint those members.

"Board of Directors can fill any vacancy"

Ok for international members.

Travel Policy: What are the minimum requirements?

IRS accountable plan
1. All of the expenses must be related to the business.
2. Substantiated. (60 days)
3. If employee was paid out, then they need to return any money that they cannot provide documentation.

Put a limit on the cost of a given flight (international or national)

Submit a budget in advance of a trip, the budget needs to be approved, and the expenses must be documented.

How to move members to the new org?

Either:
* Automatically move them over; or
* Another reaffirmation of membership into the new org

"Make a significant and sustained contribution" -- if you cannot identify contributions, you could drop those members.

What would be required in order to hire someone to do the backoffice work?
* It is difficult to keep on top of tax obligations without a point person who takes these responsibilities for themselves.
* This person can do fundraising.
** Things to consider for hiring:
*** Board needs to fulfill its duty of care to find the right person.
*** Sometimes boards have someone in mind, but recommended to go through an application process.
*** Data for NPO's is published, so this can be easily compared. This can be used in setting the salary for anyone we might hire.
*** Payroll obligations. Recommended to go with a payroll company.

Listed on 1023 the "Number of volunteers; number of countries". What should we know about this?
* There are some countries on the anti-terrorist list. (Through treasury dept.)
* Iran, North Korea, (I think) Sudan, and Libya -- these are countries where you need to be careful not to do business with.
* Avoid "terrorist" orgs and criminals

Would not be a bad policy when you have non-US nationals, check the "special designated nationals" list. (Especially when sending money.)

Closed meeting of the board?

Built into the bylaws 7 day notice before inviting non-board members. This is contrary to the way we have operated in the past.
* Sometimes there needs to be clear and frank discussions about certain things (like when people break the code of conduct).

Why are they all not open? Why have they not been open in the past?

We can always vote to change this.

Are we still on SFC? Can we operate as our own org?

We are still on SFC, but we are also our own org.
It could take 8 to 12 months to have an official answer to the 1023.

=== Report from project representative (Conservancy liaison) ===

Devin sent our "1023 FYI" to Karen. No response yet.

=== Reports from Ombudsman ===

Nothing Reported. (Reminder: This is Walter's role now.)

=== Strategic Planning, etc. ===

Bring 2 ideas next week.

Layout ideas, and prioritize them.

HR meets ideas.

* Business Plan
* Marketing and PR
* Strategic Planning

=== SugarLabs Code-in ===

(Postponing this until 12/23)

=== SugarLabs Vision ===

(Postponing this until the meeting after 12/23)

=== Time and Place of Next Meeting ===

2020-12-23 at 19:30 UTC on Jitsi

=== Closing ===

20:30 UTC

Oversight Board/2020-2022-candidates/Lionel Laské

2020-11-04T08:41:21Z

Llaske:

Hi all,

My name is Lionel Laské, you could learn more about me [[User:Llaske|here]].

I'm SLOB member since 2015 and I'm author and lead developer of [https://sugarizer.org Sugarizer], a rewrite of Sugar to run on any device.
Sugarizer has already thousands of users all over the world, specifically in [[Sugarizer_Saint-Ouen_deployment|France]], [https://www.lewa.org/impact/education-2/curriculum-development/ Kenya] and [https://www.gob.pe/institucion/pronatel/noticias/300600-mtc-entrega-mas-de-28-mil-tabletas-a-la-region-ayacucho-para-fortalecer-el-acceso-a-la-educacion Peru].
I'm proud that there is now more than 100 Sugarizer contributors today and this community is still growing. In the latest Google Summer of Code, 2 mentors was previously students of the program for SugarLabs and one student was already here last year.

Sugarizer keep alive the spirit of SugarLabs. With Sugarizer, with the nice Music Blocks project and with the legacy code base of Sugar -that we need to maintain for existing users- we've got a promise for a nice future for SugarLabs.

For 2020-2022, I would like to contribute to write this future and to help the transition from SFC to SugarLabs Inc.

Oversight Board/2020-2022-candidates/Lionel Laské

2020-11-04T08:19:44Z

Llaske: Lionel Laské proposal for 2020-2022.

Hi all,

My name is Lionel Laské, you could learn more about me [[User:Llaske|here]].

I'm SLOB member since 2015 and I'm author and lead developer of [https://sugarizer.org Sugarizer], a rewrite of Sugar to run on any device.
Sugarizer has already thousands of users all over the world, specifically in [[Sugarizer_Saint-Ouen_deployment|France]], [https://www.lewa.org/impact/education-2/curriculum-development/ Kenya] and [https://www.gob.pe/institucion/pronatel/noticias/300600-mtc-entrega-mas-de-28-mil-tabletas-a-la-region-ayacucho-para-fortalecer-el-acceso-a-la-educacion Peru].
I'm proud that there is now more than Sugarizer 100 contributors today and this community is still growing. In the latest Google Summer of Code, 2 mentors was previously students of the program and one student was already here last year.

Sugarizer keep alive the spirit of SugarLabs. With Sugarizer, with the nice Music Blocks project and with the legacy code base of Sugar -that we need to maintain for existing users- we've got a promise for a nice future for SugarLabs.

For 2020-2022, I would like to contribute to write this future and to help the transition from SFC to SugarLabs Inc.

Oversight Board/Meeting Minutes-2020-09-02

2020-09-03T19:25:46Z

Llaske: /* Sugarizer */

== Agenda for SLOBs Meeting ==
2020-09-02 at 20:00 UTC on Jitsi

=== Role Call ===

Present SLOBs: Ibiam, Lionel, Devin

Present Guests: Walter

=== Report from project representative (Conservancy liaison) ===

Nothing to Report.

=== Reports from Ombudsman ===

(James is not present, so no report.)

=== Any reports from project teams, Google Summer of Code ===

Walter asks mentors to submit the evaluations if not done already.

NOTE: Students did a wonderful job this summer.

TODO: All students must archive final reports [https://github.com/sugarlabs/GSoC/tree/master/archives/2020/student-reports here].

=== 1023 Status Report and Action Items ===

Action Items:
1. Rework Bios (everyone)
2. Rework Beginning (Devin)
3. Rework History (5 paragraphs)
4. Rework Future (5 paragraphs)

=== James and Ibiam Sugar Activity Job Report ===

Received a detailed sheet of packages from Ibiam with which show what needs to be updated.

=== Board Composition and Election (Cont.) ===

Walter and Ibiam will be meeting to work on this.

* Sugar Labs Oversight Board members may run and be voted on, under SFC.

* Sugar Labs Advisory Board members may move into new org without legal implications. Minors may run and be voted on.

* Sugar Labs Inc. board cannot be changed without considering legal implications.

=== Time and Place of Next Meeting ===

Sep 16th 20:00UTC on Jitsi

=== Closing ===

Finished 4:58

=== Final 2020 GSoC Feature Share ===

==== Music Blocks ====

Oscilloscope

==== Sugarizer ====

Vote activity

Oversight Board/Meeting Minutes-2020-09-02

2020-09-03T19:25:26Z

Llaske: /* Any reports from project teams, Google Summer of Code */

Oversight Board/Meeting Minutes-2020-07-22

2020-07-23T20:39:38Z

Llaske: /* Sugarizer */

== Minutes for SLOBs Meeting ==
2020-07-22 at 20:00 UTC

Attendance: Devin, Lionel, Ibiam, James, Walter, Samson (Alex excused himself beforehand.)

=== Vote on Prior Meeting Minutes ===

See https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-07-08

Minutes Approved unanimously after some final edits.

=== Report from project representative (Conservancy liaison) ===

No Report

=== Reports from Ombudsman ===

No Report

=== Any reports from project teams, Google Summer of Code ===

James says everyone is doing well. Groups are not cross-pollinating.

Every student passed their first evaluation.

=== Devin and Caryl 1023 Job Report ===

* 1023 Status
* Finding a new lawyer -- how is that going? (Kyle says he cannot do it because of time constraints.)

Two problematic areas in our "Brief History of SL" related to language.

Walter and Devin will work on the "Brief History of Sugar Labs" after this meeting.

=== James and Ibiam Sugar Activity Job Report ===

Met for 30 minutes. Not yet agreed on a plan.

Ibiam has been feeling sick and has just started feeling better.

=== Each One Teach One ===

Similar to Google Code-in. Not a contest, but involves kids of a similar age.

See www.eachoneteachone.is for more information.

=== GSoC Feature Share ===

==== Sugarizer ====

Lionel shows "Mind Math" activity. Can be tested at https://dev.sugarizer.org

Students can compete with other users.

==== Music Blocks ====

Devin demonstrates Aviral's work on movable do for when students are inputting their code.

==== Python ====

Bug fixes. Tests. Translations and other clerical work.

=== Vote on Today's Meeting Minutes ===

See this page https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-07-22

Minutes unanimously Approved by all SLOBS present

=== Time and Place of Next Meeting ===

Meeting on 2020-08-05 at 20:00 UTC on IRC.

Agenda to be published at https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-08-05 (then overwritten with the minutes at meeting)

=== Closing ===

Motion to adjourn the meeting has been approved.

Oversight Board/Meeting Minutes-2020-07-08

2020-07-22T16:22:40Z

Llaske:

== SLOBs Meeting ==
2020-07-08 at 20:00 UTC

Attendance: Devin, Claudia, James, Walter, and Ibiam

=== Report from project representative (Conservancy liaison) ===

No Report

=== Reports from Ombudsman ===

No Report (James has not heard from Ombudsman)

=== any reports from project teams, Google Summer of Code ===

All the evaluations have been completed.

Some students treat GSoC like a job, and do not try new things.

Music Blocks code is getting much cleaner and easier to read.

=== Acknowledge Recycle USB ===

Report by Walter Bender

From email:
> I was asked by Recycle USB (https://www.recycleusb.com/), the
> organization that periodically sends us USB keys in bulk to
> distribute, if we could put some sort of ACK on our website. Would
> like to discuss this with the board at the next meeting.
>
> FWIW, I just got a batch of 5000 8gig USB keys, suitable for
> distributing SOAS et al. from Recycle USB.

Discussion:
It would be best if we could have a method for distributing these USB keys.

It may be nice to partner with an org, such as FSF for small scale distribution. (Walter and Devin to reach out to FSF contacts.)

=== Music Blocks in Peru ===

Report by Walter Bender

From email:
> Not sure it merits discussion at the SLOB meeting, but I wanted to
> give everyone a heads up that the ministry of education in Peru will
> be distributing on the order of 800000 Android tablets to children in
> the coming months. They will be including Music Blocks (translated
> into Aymara and Quechua). I've been discussing the possibility of
> including Sugarizer in future releases as well.

Discussion:
Update from Walter: They need an Android app. Lionel will help Walter with this.

Link from Lionel on the Sugarizer Cordova Packager: www.github.com/llaske/sugarizer-apkbuilder

=== James and Ibiam Sugar Activity Job ===

Going to meet soon now that James is feeling better.

=== Methods for Engaging to Board ===

Discussion:

Walter mentions that others may want to attend the board meeting.

James suggested that it helps our productivity when the board meets privately.

Claudia suggests that every other meeting could be available to the public via open invitation.

Devin suggests that the agenda be published on the wiki before the meeting.

Devin also says that we need to be careful, when using Jitsi, that no unwanted intruders come to the meeting (i.e. Zoom bombing)

James says that not very many members have responded to request for who would like to attend the board meetings.

Ibiam suggests that maybe we use IRC for the open-invitation meetings.

=== GSoC Feature Share ===

==== Lionel | Sugarizer ====

Deployment of new servers via easy code

==== Walter | Music Blocks ====

* Input via MIDI keyboard
* Musical staff as a graph (like cartesian)
* Export JS

==== James ====

* Students are "chugging along".
* Students working on engagement with Debian -- needs to reach out to Debian again.
* Students are amazing. Observation that some students do not have opportunity to innovate.

=== time of next meeting ===

Meeting on 2020-07-22

Agenda to be published at https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2020-07-22 (then overwritten with the minutes at meeting)

=== closing ===

Oversight Board/Meeting Minutes-2020-07-08

2020-07-08T21:00:49Z

Llaske: /* Music Blocks in Peru */

== SLOBs Meeting ==
2020-07-08 at 20:00 UTC

=== Report from project representative (Conservancy liaison) ===

No Report

=== Reports from Ombudsman ===

No Report (James has not heard from Ombudsman)

=== any reports from project teams, Google Summer of Code ===

All the evaluations have been completed.

Some students treat GSoC like a job, and do not try new things.

Music Blocks code is getting much cleaner and easier to read.

=== Acknowledge Recycle USB ===

Report by Walter Bender

From email:
> I was asked by Recycle USB (https://www.recycleusb.com/), the
> organization that periodically sends us USB keys in bulk to
> distribute, if we could put some sort of ACK on our website. Would
> like to discuss this with the board at the next meeting.
>
> FWIW, I just got a batch of 5000 8gig USB keys, suitable for
> distributing SOAS et al. from Recycle USB.

Discussion:
It would be best if we could have a method for distributing these USB keys.

It may be nice to partner with an org, such as FSF for small scale distribution. (Walter and Devin to reach out to FSF contacts.)

=== Music Blocks in Peru ===

Report by Walter Bender

From email:
> Not sure it merits discussion at the SLOB meeting, but I wanted to
> give everyone a heads up that the ministry of education in Peru will
> be distributing on the order of 800000 Android tablets to children in
> the coming months. They will be including Music Blocks (translated
> into Aymara and Quechua). I've been discussing the possibility of
> including Sugarizer in future releases as well.

Discussion:
Update from Walter: They need an Android app. Lionel will help Walter with this.

Link from Lionel on the Sugarizer Cordova Packager: www.github.com/llaske/sugarizer-apkbuilder

=== James and Lionel Sugar Activity Job ===

Going to meet soon now that James is feeling better.

=== Methods for Engaging to Board ===

Discussion:

Walter mentions that others may want to attend the board meeting.

James suggested that it helps our productivity when the board meets privately.

Claudia suggests that every other meeting could be available to the public via open invitation.

Devin suggests that the agenda be published on the wiki before the meeting.

Devin also says that we need to be careful, when using Jitsi, that no unwanted intruders come to the meeting (i.e. Zoom bombing)

Ibiam suggests that maybe we use IRC for the open-invitation meetings.

=== GSoC Feature Share ===

=== any discussion of goals ===

=== time of next meeting ===

=== closing ===

Sugarizer Saint-Ouen deployment

2020-01-14T14:57:59Z

Llaske: /* Next deployment step */

== Location ==

The city of [https://fr.wikipedia.org/wiki/Saint-Ouen-sur-Seine Saint-Ouen] is located in the northern suburbs of Paris.

The population is about 50,000 people.

There is about 5,400 children in schools: 2,200 in kindergarten, 3,200 in primary schools.
There is about 200 teachers in 23 school.

== History ==

The Saint-Ouen deployment started in 2014 with the deployment of 25 XO-4 at the Mendela school by [http://olpc-france.org OLPC France/Eduvelopers].

In 2017, the 25 XO-4 have been replaced by 25 tablets Lenovo Tab 2 A10-30 on Sugarizer OS, bought with the help of the L'Oreal Fondation.

[[File:Sugarizer stouen childs.jpg|thumb|Children playing with Sugarizer in Mendela school at Saint-Ouen]]

Considering the positive feedbacks of teachers on field and its wish to deploy Android tablets in schools, the Saint-Ouen city decided in 2018 to launch a large deployment of Sugarizer in schools.

A partnership was set between Saint-Ouen city, the Inspection Academique (depending of French minister of education) and OLPC France/Eduvelopers.

== First phase of deployment ==

The first phase of deployment has started in 2019 with a deployment in 3 schools: Mendela, PEF and Petit-Prince. It means about 50 class and 1000 children.

Three training sessions animated by IT team from Saint-Ouen city and OLPC France/Eduvelopers was planned between March and May with teachers of each school.

[[File:Sugarizer stouen training.jpg|thumb|Teacher training workshop in March 2019]]

== Devices and software ==

Tablets deployed are Samsung Galaxy Tab A 2018. Each schools received 2 chariots with 27 tablets in each and a WiFi . Each school is connected to a broadband internet connection.

[[File:Sugarizer stouen devices.png|thumb|Devices deployed at Saint-Ouen]]

Sugarizer OS is deployed on each tablets with about 20 android application launchable from Sugarizer OS.

Sugarizer Server is deployed on the infrastructure of city using Docker.

[[File:Sugarizerserver stouen architecture.png|thumb|Sugarizer Server architecture at Saint-Ouen deployment]]

== Second phase of deployment ==

The second phase of deployment has started in september 2019 witch is a deployment in 5 new schools: Frédéric Joliot Curie, Irène Joliot Curie, Jules Michelet, Victor Hugo and La Fontaine. It means about 50 new class and about 1100 new children.

About 480 Sugarizer OS tablets was deployed between phase 1 and phase 2.

During the second phase, two training sessions for teachers was planned into each school. The first training session was planned at the beginning of school year and is intended to explain usage of tablets and Sugarizer. Training sessions are conducted by IT team from Saint-Ouen city, OLPC France/Eduvelopers and the mentor on digital technology for teachers (eRun) from Inspection Academique.

The second session is planned during Q2 2020 and will be dedicated to listen teacher feedbacks.

== Next deployment step ==

The third phase of deployment is planned in 2nd semester 2020. The objective is to deploy the 5 leaving schools in the city: means about 1500 new children and 300 new tablets.

All schools in the city should be deployed at the end of 2020.

== More information ==

Deployment updates are posted on [https://twitter.com/sugarizerapp Sugarizer twitter account].

Contact [[User:Llaske|Lionel Laské]] for more information.

User:Llaske

2019-12-17T13:45:29Z

Llaske:

My name is Lionel Laské. I'm member of SugarLabs Oversight Board since 2015. My github account is [https://github.com/llaske llaske].

I'm also board member and co-founder in 2008 of the [http://olpc-france.org OLPC France grassroot].

OLPC France launch and maintain from 2009 to 2018 a deployment of 200 XO-1/1.5 laptops in Madagascar on the [http://wiki.laptop.org/go/OLPC_Madagascar/Nosy_Komba Nosy Komba Island].

OLPC France launched also a small deployment of 50 XO-1.5 laptops in Saint-Denis (Paris suburb) between 2012 and 2014 and a deployment of 25 XO-4 laptops in Saint-Ouen (Paris suburb) in 2015-2016. Currently we hold a [http://sugarizer.org Sugarizer] deployment of 480 Android tablets in [[Sugarizer Saint-Ouen deployment|Saint-Ouen]].

OLPC France promote One Laptop Per Child philosophy, Sugar and open source software and is also a reproducible association based on [http://movecommons.org Move Commons philosophy] so all our way of working is fully transparent and documented [http://olpc-france.org/wiki/index.php/Association].

OLPC France organized three SugarCamp in Paris in 2009, 2011 and 2014.

OLPC France was closed in 2018 and reborn in 2019 with the name of Eduvelopers.

I'm the author of 8 Sugar activities [http://activities.sugarlabs.org/en/sugar/user/1454]. I'm also the author and the lead developer of [http://sugarizer.org Sugarizer], a port of Sugar on any device.

Finally I was mentor for SugarLabs during Google Summer of Code 2013 to 2019 and I was mentor for Google Code-In in 2015 to 2019.

Sugarizer Saint-Ouen deployment

2019-12-13T15:16:49Z

Llaske: /* Location */

== Location ==

The city of [https://fr.wikipedia.org/wiki/Saint-Ouen-sur-Seine Saint-Ouen] is located in the northern suburbs of Paris.

The population is about 50,000 people.

There is about 5,400 children in schools: 2,200 in kindergarten, 3,200 in primary schools.
There is about 200 teachers in 23 school.

== History ==

The Saint-Ouen deployment started in 2014 with the deployment of 25 XO-4 at the Mendela school by [http://olpc-france.org OLPC France/Eduvelopers].

In 2017, the 25 XO-4 have been replaced by 25 tablets Lenovo Tab 2 A10-30 on Sugarizer OS, bought with the help of the L'Oreal Fondation.

[[File:Sugarizer stouen childs.jpg|thumb|Children playing with Sugarizer in Mendela school at Saint-Ouen]]

Considering the positive feedbacks of teachers on field and its wish to deploy Android tablets in schools, the Saint-Ouen city decided in 2018 to launch a large deployment of Sugarizer in schools.

A partnership was set between Saint-Ouen city, the Inspection Academique (depending of French minister of education) and OLPC France/Eduvelopers.

== First phase of deployment ==

The first phase of deployment has started in 2019 with a deployment in 3 schools: Mendela, PEF and Petit-Prince. It means about 50 class and 1000 children.

Three training sessions animated by IT team from Saint-Ouen city and OLPC France/Eduvelopers was planned between March and May with teachers of each school.

[[File:Sugarizer stouen training.jpg|thumb|Teacher training workshop in March 2019]]

== Devices and software ==

Tablets deployed are Samsung Galaxy Tab A 2018. Each schools received 2 chariots with 27 tablets in each and a WiFi . Each school is connected to a broadband internet connection.

[[File:Sugarizer stouen devices.png|thumb|Devices deployed at Saint-Ouen]]

Sugarizer OS is deployed on each tablets with about 20 android application launchable from Sugarizer OS.

Sugarizer Server is deployed on the infrastructure of city using Docker.

[[File:Sugarizerserver stouen architecture.png|thumb|Sugarizer Server architecture at Saint-Ouen deployment]]

== Second phase of deployment ==

The second phase of deployment has started in september 2019 witch is a deployment in 5 new schools: Frédéric Joliot Curie, Irène Joliot Curie, Jules Michelet, Victor Hugo and La Fontaine. It means about 50 new class and about 1100 new children.

About 480 Sugarizer OS tablets was deployed between phase 1 and phase 2.

During the second phase, two training sessions for teachers was planned into each school. The first training session was planned at the beginning of school year and is intended to explain usage of tablets and Sugarizer. Training sessions are conducted by IT team from Saint-Ouen city, OLPC France/Eduvelopers and the mentor on digital technology for teachers (eRun) from Inspection Academique.

The second session is planned during Q2 2020 and will be dedicated to listen teacher feedbacks.

== Next deployment step ==

The third phase of deployment is planned in 2nd semester 2020. The objective is to deploy the 5 leaving schools in the city: means about 1500 new children et 300 new tablets.

All schools in the city should be deployed at the end of 2020.

== More information ==

Deployment updates are posted on [https://twitter.com/sugarizerapp Sugarizer twitter account].

Contact [[User:Llaske|Lionel Laské]] for more information.

Sugarizer Saint-Ouen deployment

2019-12-12T22:14:22Z

Llaske: Update deployment information

== Location ==

The city of [https://fr.wikipedia.org/wiki/Saint-Ouen-sur-Seine Saint-Ouen] is located is located in the northern suburbs of Paris.

The population is about 50,000 people.

There is about 5,400 children in schools: 2,200 in kindergarten, 3,200 in primary schools.
It's 23 schools and about 200 teachers.

== History ==

The Saint-Ouen deployment started in 2014 with the deployment of 25 XO-4 at the Mendela school by [http://olpc-france.org OLPC France/Eduvelopers].

In 2017, the 25 XO-4 have been replaced by 25 tablets Lenovo Tab 2 A10-30 on Sugarizer OS, bought with the help of the L'Oreal Fondation.

[[File:Sugarizer stouen childs.jpg|thumb|Children playing with Sugarizer in Mendela school at Saint-Ouen]]

Considering the positive feedbacks of teachers on field and its wish to deploy Android tablets in schools, the Saint-Ouen city decided in 2018 to launch a large deployment of Sugarizer in schools.

A partnership was set between Saint-Ouen city, the Inspection Academique (depending of French minister of education) and OLPC France/Eduvelopers.

== First phase of deployment ==

The first phase of deployment has started in 2019 with a deployment in 3 schools: Mendela, PEF and Petit-Prince. It means about 50 class and 1000 children.

Three training sessions animated by IT team from Saint-Ouen city and OLPC France/Eduvelopers was planned between March and May with teachers of each school.

[[File:Sugarizer stouen training.jpg|thumb|Teacher training workshop in March 2019]]

== Devices and software ==

Tablets deployed are Samsung Galaxy Tab A 2018. Each schools received 2 chariots with 27 tablets in each and a WiFi . Each school is connected to a broadband internet connection.

[[File:Sugarizer stouen devices.png|thumb|Devices deployed at Saint-Ouen]]

Sugarizer OS is deployed on each tablets with about 20 android application launchable from Sugarizer OS.

Sugarizer Server is deployed on the infrastructure of city using Docker.

[[File:Sugarizerserver stouen architecture.png|thumb|Sugarizer Server architecture at Saint-Ouen deployment]]

== Second phase of deployment ==

The second phase of deployment has started in september 2019 witch is a deployment in 5 new schools: Frédéric Joliot Curie, Irène Joliot Curie, Jules Michelet, Victor Hugo and La Fontaine. It means about 50 new class and about 1100 new children.

About 480 Sugarizer OS tablets was deployed between phase 1 and phase 2.

During the second phase, two training sessions for teachers was planned into each school. The first training session was planned at the beginning of school year and is intended to explain usage of tablets and Sugarizer. Training sessions are conducted by IT team from Saint-Ouen city, OLPC France/Eduvelopers and the mentor on digital technology for teachers (eRun) from Inspection Academique.

The second session is planned during Q2 2020 and will be dedicated to listen teacher feedbacks.

== Next deployment step ==

The third phase of deployment is planned in 2nd semester 2020. The objective is to deploy the 5 leaving schools in the city: means about 1500 new children et 300 new tablets.

All schools in the city should be deployed at the end of 2020.

== More information ==

Deployment updates are posted on [https://twitter.com/sugarizerapp Sugarizer twitter account].

Contact [[User:Llaske|Lionel Laské]] for more information.

Sugarizer Saint-Ouen deployment

2019-12-04T21:25:13Z

Llaske: Update deployment information

== History ==

The [https://fr.wikipedia.org/wiki/Saint-Ouen-sur-Seine Saint-Ouen] deployment started in 2014 with the deployment of 25 XO-4 at the Mendela school by [http://olpc-france.org OLPC France/Eduvelopers].

In 2017, the 25 XO-4 have been replaced by 25 tablets Lenovo Tab 2 A10-30 on Sugarizer OS, bought with the help of the L'Oreal Fondation.

[[File:Sugarizer stouen childs.jpg|thumb|Children playing with Sugarizer in Mendela school at Saint-Ouen]]

Considering the positive feedbacks of teachers on field and its wish to deploy Android tablets in schools, the Saint-Ouen city decided in 2018 to launch a large deployment of Sugarizer in schools.

A partnership was set between Saint-Ouen city, the Inspection Academique (depending of French minister of education) and OLPC France/Eduvelopers.

== First phase of deployment ==

The first phase of deployment has started in 2019 with a deployment in 3 schools: Mendela, PEF and Petit-Prince. It means about 50 class and 1000 children.

Three training sessions animated by IT team from Saint-Ouen city and OLPC France/Eduvelopers was planned between March and May with teachers of each school.

[[File:Sugarizer stouen training.jpg|thumb|Teacher training workshop in March 2019]]

== Devices and software ==

Tablets deployed are Samsung Galaxy Tab A 2018. Each schools received 2 chariots with 27 tablets in each and a WiFi . Each school is connected to a broadband internet connection.

[[File:Sugarizer stouen devices.png|thumb|Devices deployed at Saint-Ouen]]

Sugarizer OS is deployed on each tablets with about 20 android application launchable from Sugarizer OS.

Sugarizer Server is deployed on the infrastructure of city using Docker.

[[File:Sugarizerserver stouen architecture.png|thumb|Sugarizer Server architecture at Saint-Ouen deployment]]

== Second phase of deployment ==

The second phase of deployment has started in september 2019 witch is a deployment in 5 new schools: Frédéric Joliot Curie, Irène Joliot Curie, Jules Michelet, Victor Hugo and La Fontaine. It means about 50 new class and about 1000 new children.

During the second phase, two training sessions for teachers was planned into each school. The first training session was planned at the beginning of school year and is intended to explain usage of tablets and Sugarizer. Training sessions are conducted by IT team from Saint-Ouen city, OLPC France/Eduvelopers and the mentor on digital technology for teachers (eRun) from Inspection Academique.

The second session is planned during Q2 2020 and will be dedicated to listen teacher feedbacks.

== Next deployment step ==

The third phase of deployment is planned in 2nd semester 2020. The objective is to deploy the 5 leaving schools in the city. So all city schools should be deployed at the end of 2020.

== More information ==

Deployment updates are posted on [https://twitter.com/sugarizerapp Sugarizer twitter account].

Contact [[User:Llaske|Lionel Laské]] for more information.

Google Code In 2018/background

2019-10-18T15:29:57Z

Llaske: /* Getting started with Sugarizer */

=== Getting set up on IRC ===

We use IRC for much of our communication. Unfortunate, Freenode, our IRC server, has been under attack by trolls of late, so we have had to lock down our channels. Therefore, you'll need to create a "registered account" to login. (You can use an IRC client or open https://webchat.freenode.net in a browser.)

To register on Freenode:

/msg NickServ REGISTER password youremail@example.com

(Filling in your email and password)

Leave the window open if possible.

You will get an email that includes a command you'll need to type in to complete your registration. (It may take a while for the email to arrive.)

Go back to the open IRC window and paste in the verification line from the email you received in the bottom space.

If you have closed the IRC window, you will need to reopen it.

Once you are registered, you may join the #sugar channel:

/join #sugar

When you reconnect at a later date, you may have to:

/msg NickServ identify your-password

Please contact walter @ sugarlabs . org if you have any questions.

=== Basics: Attribution and Licensing ===

Read [[Attribution and Licensing]], as both are important for all submissions.

=== Setting up a Sugar desktop environment ===

There are several options for setting up the Sugar desktop environment for development, depending on what equipment you have;

{| class="wikitable"
|-
! Your Equipment !! Your Operating System !! Our Recommendation
|-
| rowspan="2" | You have only one computer and don't want to erase it
| Linux, Windows, macOS, or iOS
| Install virtualisation software, make a new virtual machine and install [[Live Build|Sugar Live Build]], [[SoaS|Sugar on a Stick]], [[Ubuntu]], [[Fedora]], or [[Debian]].
|-
| Linux
| Install Sugar packages from your distribution, see [[Ubuntu]], [[Fedora]] or [[Debian]]. For other distributions, contact your distribution community.
|-
| You have another computer that can be erased
| Doesn't matter
| Install [[Live Build|Sugar Live Build]], [[SoaS|Sugar on a Stick]], [[Ubuntu]], [[Fedora]], or [[Debian]].
|}

What's the difference between Live Build, Sugar on a Stick and the various Linux options?

{| class="wikitable"
|-
! !! Live Build (based on Debian) !! Sugar on a Stick (based on Fedora) !! Ubuntu, Debian or Fedora
|-
! Sugar desktop user experience on startup
| yes, 0.116 || yes, 0.114 || no, must install packages
|-
! Good for Sugar activity development
| yes || no, must install packages || no, must install packages
|-
! Good for Sugar desktop module development
| yes, source code included || no, must install git and use rpmbuild || no, must install packages
|-
! Works on a spare computer
| yes || yes || yes
|-
! Works as a Virtual Machine
| yes || yes || yes
|}

See also [https://developer.sugarlabs.org/dev-environment.md.html Setup a development environment].

=== Getting started with coding in Sugar ===

Sugar development is in either Python or JavaScript languages.

* For the JavaScript language, you will need knowledge of;
** JavaScript;
** HTML5;
** web browsers;
** web design; and,
** web deployment.
* For the Python language, you will need knowledge of;
** [https://www.python.org/ Python];
** the [https://pygobject.readthedocs.io/en/latest/ PyGObject] package;
** the [https://python-gtk-3-tutorial.readthedocs.org/en/latest/ Python bindings] for [https://www.gtk.org/ GTK+ 3]; and
** the [https://lazka.github.io/pgi-docs/#Gtk-3.0 Gtk-3.0 section of the PyGObject API Reference].
* For both, you will need knowledge of Sugar activity development, see the book [http://www.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities!]

Python programmers, you should run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and flake8 on your changes ''before'' submitting your patches.

=== Getting started with GIT ===

Some knowledge of git is important as your work will be submitted to our [https://github.com/sugarlabs git repositories]. The basic mechanism is a pull-request (PR), which is explained in [https://developer.sugarlabs.org/contributing.md.html Contributing].

''It is required that you follow the steps outlined on the [https://developer.sugarlabs.org/contributing.md.html Contributing] page when doing coding and documentation tasks in GCI.''

GitHub provides a [https://try.github.io/levels/1/challenges/1 tutorial]. There are many other guides to GIT as well.

Our old bug tracker is https://bugs.sugarlabs.org, but these days, we mostly report bugs using the ''issues'' feature of GitHub. (See https://guides.github.com/features/issues/ for details on GitHub Issues.)

=== Making a Pull Request ===

We detail the Pull Request process in [https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md here] in our [https://github.com/sugarlabs/sugar-docs docs] on Git Hub.

A few things to keep in mind:
* Do not link commits or pull requests to a GCI task, as these are transient and not public,
* Link commits and pull requests to any relevant GitHub issue, and if there is no such issue, say so,
* Explain the problem and how it was solved in your commit message, not in your pull request.

=== Setting up a Sugarizer environment ===

{| class="wikitable"
|-
! Your Equipment !! Your Operating System !! Our Recommendation
|-
| You have a computer
| Linux, Windows or macOS
| Install the [https://sugarizer.org/#apps Sugarizer package] for your operating system.
|-
| You have a tablet or phone
| Android
| Install the [https://sugarizer.org/#apps Sugarizer app] from Google Play.
|-
| You have a tablet or phone
| iOS
| Install the [https://sugarizer.org/#apps Sugarizer app] from the App Store.
|-
| You have just a browser
| Any
| Test Sugarizer on the [https://try.sugarizer.org/ Sugarizer web site].
|}
See also [[#Getting started with coding in Sugarizer]].

=== Getting started with coding in Sugarizer ===

A good way to start coding in Sugarizer is to complete the [https://github.com/llaske/sugarizer/blob/dev/docs/tutorial.md Sugarizer activity development tutorial].
To learn more about Sugarizer architecture, see the dedicated page [https://github.com/llaske/sugarizer/blob/dev/docs/architecture.md here].

=== Getting a wiki account ===

Some tasks require that you make edits to this wiki for which you'll need an account. Please email walter @ sugarlabs . org to request an account.

=== Editing SVG ===

Some tasks will require that you edit SVG. You are welcome to use any SVG editor you like, but we recommend [https://inkscape.org/en/ Inkscape]. That said, when saving from Inkscape, please be sure to "save as plain SVG." The default "save" puts extra data into the files which is not needed by Sugar and makes the file size quite large.

=== Getting help ===

Got a problem? Ask your mentors, ask other students, or ask the Sugar Labs community.

The Sugar Labs community is large, and there are people who are not mentors in the contest. Mentors are [[Google_Code_In_2017#Mentors|listed]]. Everyone else you talk with may be a non-mentor.

As part of Sugar Labs community, non-mentors are to treat students in accord with the [[Sugar_Labs/Legal/Code_of_Conduct|Code of Conduct]], and as if they are new to Sugar Labs.

Students should keep in mind that some people are non-mentors, and cannot see the contest tasks, contest progress, dates, or information about students. When communicating widely, be sure to;

* introduce yourself, the first time;
* tell us what your task is, without relying on a link to the task (because we probably can't see it);
* talk about the task as if you want to do it yourself, not because of the contest; and,
* defend your technical decisions without using the contest as a defence.

Non-mentors may give good guidance on technical decisions, but bad guidance on how they think a task is judged. Always consult with your mentors as well.

Google Code In 2018/background

2019-10-18T15:24:27Z

Llaske: /* Setting up a Sugarizer environment */

=== Getting set up on IRC ===

We use IRC for much of our communication. Unfortunate, Freenode, our IRC server, has been under attack by trolls of late, so we have had to lock down our channels. Therefore, you'll need to create a "registered account" to login. (You can use an IRC client or open https://webchat.freenode.net in a browser.)

To register on Freenode:

/msg NickServ REGISTER password youremail@example.com

(Filling in your email and password)

Leave the window open if possible.

You will get an email that includes a command you'll need to type in to complete your registration. (It may take a while for the email to arrive.)

Go back to the open IRC window and paste in the verification line from the email you received in the bottom space.

If you have closed the IRC window, you will need to reopen it.

Once you are registered, you may join the #sugar channel:

/join #sugar

When you reconnect at a later date, you may have to:

/msg NickServ identify your-password

Please contact walter @ sugarlabs . org if you have any questions.

=== Basics: Attribution and Licensing ===

Read [[Attribution and Licensing]], as both are important for all submissions.

=== Setting up a Sugar desktop environment ===

There are several options for setting up the Sugar desktop environment for development, depending on what equipment you have;

{| class="wikitable"
|-
! Your Equipment !! Your Operating System !! Our Recommendation
|-
| rowspan="2" | You have only one computer and don't want to erase it
| Linux, Windows, macOS, or iOS
| Install virtualisation software, make a new virtual machine and install [[Live Build|Sugar Live Build]], [[SoaS|Sugar on a Stick]], [[Ubuntu]], [[Fedora]], or [[Debian]].
|-
| Linux
| Install Sugar packages from your distribution, see [[Ubuntu]], [[Fedora]] or [[Debian]]. For other distributions, contact your distribution community.
|-
| You have another computer that can be erased
| Doesn't matter
| Install [[Live Build|Sugar Live Build]], [[SoaS|Sugar on a Stick]], [[Ubuntu]], [[Fedora]], or [[Debian]].
|}

What's the difference between Live Build, Sugar on a Stick and the various Linux options?

{| class="wikitable"
|-
! !! Live Build (based on Debian) !! Sugar on a Stick (based on Fedora) !! Ubuntu, Debian or Fedora
|-
! Sugar desktop user experience on startup
| yes, 0.116 || yes, 0.114 || no, must install packages
|-
! Good for Sugar activity development
| yes || no, must install packages || no, must install packages
|-
! Good for Sugar desktop module development
| yes, source code included || no, must install git and use rpmbuild || no, must install packages
|-
! Works on a spare computer
| yes || yes || yes
|-
! Works as a Virtual Machine
| yes || yes || yes
|}

See also [https://developer.sugarlabs.org/dev-environment.md.html Setup a development environment].

=== Getting started with coding in Sugar ===

Sugar development is in either Python or JavaScript languages.

* For the JavaScript language, you will need knowledge of;
** JavaScript;
** HTML5;
** web browsers;
** web design; and,
** web deployment.
* For the Python language, you will need knowledge of;
** [https://www.python.org/ Python];
** the [https://pygobject.readthedocs.io/en/latest/ PyGObject] package;
** the [https://python-gtk-3-tutorial.readthedocs.org/en/latest/ Python bindings] for [https://www.gtk.org/ GTK+ 3]; and
** the [https://lazka.github.io/pgi-docs/#Gtk-3.0 Gtk-3.0 section of the PyGObject API Reference].
* For both, you will need knowledge of Sugar activity development, see the book [http://www.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities!]

Python programmers, you should run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and flake8 on your changes ''before'' submitting your patches.

=== Getting started with GIT ===

Some knowledge of git is important as your work will be submitted to our [https://github.com/sugarlabs git repositories]. The basic mechanism is a pull-request (PR), which is explained in [https://developer.sugarlabs.org/contributing.md.html Contributing].

''It is required that you follow the steps outlined on the [https://developer.sugarlabs.org/contributing.md.html Contributing] page when doing coding and documentation tasks in GCI.''

GitHub provides a [https://try.github.io/levels/1/challenges/1 tutorial]. There are many other guides to GIT as well.

Our old bug tracker is https://bugs.sugarlabs.org, but these days, we mostly report bugs using the ''issues'' feature of GitHub. (See https://guides.github.com/features/issues/ for details on GitHub Issues.)

=== Making a Pull Request ===

We detail the Pull Request process in [https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md here] in our [https://github.com/sugarlabs/sugar-docs docs] on Git Hub.

A few things to keep in mind:
* Do not link commits or pull requests to a GCI task, as these are transient and not public,
* Link commits and pull requests to any relevant GitHub issue, and if there is no such issue, say so,
* Explain the problem and how it was solved in your commit message, not in your pull request.

=== Setting up a Sugarizer environment ===

{| class="wikitable"
|-
! Your Equipment !! Your Operating System !! Our Recommendation
|-
| You have a computer
| Linux, Windows or macOS
| Install the [https://sugarizer.org/#apps Sugarizer package] for your operating system.
|-
| You have a tablet or phone
| Android
| Install the [https://sugarizer.org/#apps Sugarizer app] from Google Play.
|-
| You have a tablet or phone
| iOS
| Install the [https://sugarizer.org/#apps Sugarizer app] from the App Store.
|-
| You have just a browser
| Any
| Test Sugarizer on the [https://try.sugarizer.org/ Sugarizer web site].
|}
See also [[#Getting started with coding in Sugarizer]].

=== Getting started with Sugarizer ===

Sugar Web Framework is the [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md JavaScript Framework for Sugar]. [http://sugarizer.org Sugarizer] is a subset of Sugar that allow running activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.

=== Getting a wiki account ===

Some tasks require that you make edits to this wiki for which you'll need an account. Please email walter @ sugarlabs . org to request an account.

=== Editing SVG ===

Some tasks will require that you edit SVG. You are welcome to use any SVG editor you like, but we recommend [https://inkscape.org/en/ Inkscape]. That said, when saving from Inkscape, please be sure to "save as plain SVG." The default "save" puts extra data into the files which is not needed by Sugar and makes the file size quite large.

=== Getting help ===

Got a problem? Ask your mentors, ask other students, or ask the Sugar Labs community.

The Sugar Labs community is large, and there are people who are not mentors in the contest. Mentors are [[Google_Code_In_2017#Mentors|listed]]. Everyone else you talk with may be a non-mentor.

As part of Sugar Labs community, non-mentors are to treat students in accord with the [[Sugar_Labs/Legal/Code_of_Conduct|Code of Conduct]], and as if they are new to Sugar Labs.

Students should keep in mind that some people are non-mentors, and cannot see the contest tasks, contest progress, dates, or information about students. When communicating widely, be sure to;

* introduce yourself, the first time;
* tell us what your task is, without relying on a link to the task (because we probably can't see it);
* talk about the task as if you want to do it yourself, not because of the contest; and,
* defend your technical decisions without using the contest as a defence.

Non-mentors may give good guidance on technical decisions, but bad guidance on how they think a task is judged. Always consult with your mentors as well.

Google Code In 2019

2019-10-18T15:12:12Z

Llaske: Fix link on how to help

<noinclude>[[Category:Trac Reference]][[Category:Idea]]
[[Category: GCI2019]]</noinclude>

Sugar Labs community members: please feel free to add tasks below.

== Message to potential participants ==

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

Please see the Contest Rules for Eligibility and Registration process.

https://codein.withgoogle.com/student-terms/

Also, you will likely need to set up the Sugar development environment. To do that and to further information about contributing to the project go to: https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md

Please don't hesitate to ask questions on our IRC channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org
(See [[Google_Code_In_2019#Getting_set_up_on_IRC|below]] for details regarding setting up an IRC account.)

== Why Sugar Labs is participating ==

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

== Some background from GCI ==

[See https://developers.google.com/open-source/gci/resources/getting-started]

===Open Source Fundamentals ===

You can contribute without being a coder!
You do not have to be a coder to contribute to open source. There are many different skill sets needed to help an open source community thrive:
;Documentation: If you are a good writer and enjoy attention to detail then you might want to contribute by writing or editing documentation. Documentation is a huge part of a successful open source project. Organizations need documentation to help attract new contributors as it helps them see what the codebase looks like and where things are and what the plan is for the project.
;Research: An organization may need help crunching numbers or sorting through pages of documents to better understand what the users want or need. There are many different types of tasks that students could work on that are very important to the health of the project.
;Outreach: If you have an outgoing personality and like being around and talking to people, take a look at the outreach tasks. Outreach tasks often include hosting meetups in your local community or creating a plan on how people around the globe can host a meetup about the project in their local communities.
;Training: You could create a YouTube video discussing a new feature of the project or maybe some basics on what the project does so people who haven’t heard about it can understand the project and get involved.
;User Interface: User interface can include many types of tasks including designing new aspects of a web page or creating a new logo for the project. It may also include various accessibility opportunities to help make the project easier for people who are blind.
;Other: If you have an idea that may help an organization, reach out to them and let them know! Sometimes the best task is one that the organization hasn’t even considered yet.
=== Collaboration===
Open source is not just about coding but working with other people to find the best solution. Being a part of the community is an essential part of success in Google Code-in. Mentors tell us every year that their best students were the ones who worked hard on their projects but also participated on IRC and helped answer questions other students had. Collaborate with the community and mentors on the #sugar channel in the irc.freenode.net network.

=== Quality over Quantity ===

It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.

== Some basics about Sugar Labs and Sugar development ==

For some basics about the project, see [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

{{:Google Code In 2018/background}}

== This is a stub for 25+ example tasks new for GCI 2019. ==

Note, more detailed task descriptions will be available once the contest begins.

=== Beginner tasks ===
# Install the Sugar development environment by following the instruction at [http://developer.sugarlabs.org/dev-environment.md.html].
# Install Sugar in a virtual machine.
# Install Sugar packages on Ubuntu, Debian, or Fedora.
# Install Sugarizer on a Raspberry Pi for use by nearby computers, tablets, or phones.
# Create an example program in Turtle Blocks (See [https://www.pinterest.com/walterbender/turtle-art/] for some ideas).
# Create an example program in Music Blocks.
# Create a simple machine in Physics.

=== General tasks ===
# Organize a Turtle Art Day (or Music Blocks Day) in your community (Outreach)
# Create a 60 second promotional video on Sugar and its community (Outreach)
# Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. (Outreach)
# DIY Sugar on a Stick||Organize and host a Sugar on a Stick party where you show people how to make their own Sugar on a Stick. (Outreach)
# Find an educator who is using open-source educational software to teach. Interview the educator about their experience as an educator and why they are using open-source software to teach. (Outreach)
# Write a blog post about your experience as a GCI participant for Sugar Labs. (Outreach)
# Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. (Research/Outreach)
# Gather information on who could benefit from using or knowing about Sugar. (Research)
# Find the resources that people are using throughout the world to learn about or teach Sugar Activities. (Research)
# Find the missing repo: we've lost track of the source repository of some Sugar activities: help us find them (Research)
# Wiki cleanup (Documentation)
# Music Blocks examples (Documentation/Training)
# Write a review about an Activity in Sugar. (Documentation)
# Create a unit tests for a JavaScript activity (Quality assurance)
# Test old Sugar activities and report any really obvious problems (Quality assurance)
# Refactor Turtle graphics to adopt look of Javascript version (Code: Python)
# write a Python/GTK version of Music Blocks
# Investigate CSound/Python version of Music Blocks (Code: Python)
# Resolve an open issue from https://github.com/sugarlabs/ (Code: Python)
# Plugin manager for Turtle JS (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Write a Turtle plugin (Code: Javascript)
# Write a extruder in JavaScript to convert from SVG to STL for 3D printing. (Code: JavaScript)
# Write a slicer in JavaScript to convert between SL and GCODE for 3D printing. (Code: JavaScript)
# Resolve an open issue from https://github.com/walterbender/musicblocks/ (Code: JavaScript)
# Port a Sugarizer activity to Sugar (Code: Javascript)
# Port an old Sugar activity to the most recent Sugar (Code: Python)

Mentors: please feel free to add more tasks and/or add yourself as a potential mentor to an existing task.

Tasks must fall within one of these five categories: [[#Documentation/Training]]; [[#Outreach/Research]]; [[#User Interface]]; [[#Quality Assurance]]; and [[#Code]].

== Mentors ==
;NOTES TO MENTORS:
:Please note that not all tasks are coding tasks so please consider participating even if you are not a coder (there are research, outreach, design, and documentation tasks as well).
:But also note that prior participation in the Sugar Labs community is a requirement for mentoring.

Send an email to one of the Org Admins (this year they are Walter and TBD). You will then receive an invitation by email.
Follow the instructions in the email to sign up as a Sugar Labs mentor.
:Please add yourself to the list below.
:Feel free to add new tasks to the table above.

Depending on the task, we will assign multiple mentors from our various development and support teams.

* Walter Bender - co-administrator
* James Cameron - release manager
* Sumit Srivastava - Mentor for Coding, Design, and QA tasks.
* Jaskirat Singh - Mentor for Research, Documentation, Design and Testing tasks
* Vaibhav Aren - Mentor for Coding, Research, Documentation, Design and Testing tasks.
* Hrishi Patel - Mentor for Coding, Research, Documentation, Design and QA tasks.
* Amaan Iqbal - Mentor for Coding, Research, Documentation, Design, and Testing Tasks
* Pratul Kumar - Mentor for Coding, Beginner First Issues, Git and Github, Documentation.
* Vipul Gupta - Mentor for Research, Coding, Git and GitHub, Documentation, Design tasks.
* Rishabh Thaney - Mentor for Coding, Research, Documentation, Design and Testing tasks.
* Ashish Aggarwal - Mentor for Coding, Research, Documentation, Design, and Testing Tasks
* Favour Kelvin - Mentor for Coding, Research, Documentation and Testing Tasks
* Freddie Nicholson - Mentor for Coding (Sugarizer/Music Blocks), Research, Design, Documentation and Outreach Tasks

Sugarizer Saint-Ouen deployment

2019-05-13T10:15:28Z

Llaske: /* History */

== History ==

The [https://fr.wikipedia.org/wiki/Saint-Ouen-sur-Seine Saint-Ouen] deployment started in 2014 with the deployment of 25 XO-4 at the Mendela school by [http://olpc-france.org OLPC France].

In 2017, the 25 XO-4 have been replaced by 25 tablets Lenovo Tab 2 A10-30 on Sugarizer OS, bought with the help of the L'Oreal Fondation.

[[File:Sugarizer stouen childs.jpg|thumb|Children playing with Sugarizer in Mendela school at Saint-Ouen]]

Considering the positive feedbacks of teachers on field and its wish to deploy Android tablets in schools, the Saint-Ouen city decided in 2018 to launch a large deployment of Sugarizer in schools.

A partnership was set between Saint-Ouen city, the Inspection Academique (depending of French minister of education) and OLPC France.

== First phase of deployment ==

The first phase of deployment has started in 2019 witch is a deployment in 3 schools: Mendela, PEF and Petit-Prince. It means about 50 class and 1000 children.

Three training session animated by OLPC France are planned between March and May with teachers of each school.

[[File:Sugarizer stouen training.jpg|thumb|Teacher training workshop in March 2019]]

== Devices and software ==

Tablets deployed are Samsung Galaxy Tab A 2018. Each schools received 2 chariots with 27 tablets in each and a WiFi . Each school is connected to a broadband internet connection.

[[File:Sugarizer stouen devices.png|thumb|Devices deployed at Saint-Ouen]]

Sugarizer OS is deployed on each tablets with about 20 android application launchable from Sugarizer OS.

Sugarizer Server is deployed on the infrastructure of city using Docker.

[[File:Sugarizerserver stouen architecture.png|thumb|Sugarizer Server architecture at Saint-Ouen deployment]]

== Next deployment step ==

The second phase of deployment is planned in Q4 2019 with 3 new schools. The objective is to deploy all city schools (13) by the end of 2020.

== More information ==

Deployment updates are posted on [https://twitter.com/sugarizerapp Sugarizer twitter account].

Contact [[User:Llaske|Lionel Laské]] for more information.

Sugarizer Saint-Ouen deployment

2019-05-12T14:20:04Z

Llaske: Link on Saint-Ouen city

== History ==

The [https://fr.wikipedia.org/wiki/Saint-Ouen-sur-Seine Saint-Ouen] deployment started in 2014 with the deployment of 25 XO-4 at the Mendela school by [http://olpc-france.org OLPC France].

In 2017 with replaced the 25 XO-4 by 25 tablets Lenovo Tab 2 A10-30 on Sugarizer OS bought with the help of the L'Oreal Fondation.

[[File:Sugarizer stouen childs.jpg|thumb|Children playing with Sugarizer in Mendela school at Saint-Ouen]]

Considering the positive feedbacks of teachers on field and its wish to deploy Android tablets in schools, the Saint-Ouen city decided in 2018 to launch a large deployment of Sugarizer in schools.

A partnership was set between Saint-Ouen city, the Inspection Academique (depending of French minister of education) and OLPC France.

== First phase of deployment ==

The first phase of deployment has started in 2019 witch is a deployment in 3 schools: Mendela, PEF and Petit-Prince. It means about 50 class and 1000 children.

Three training session animated by OLPC France are planned between March and May with teachers of each school.

[[File:Sugarizer stouen training.jpg|thumb|Teacher training workshop in March 2019]]

== Devices and software ==

Tablets deployed are Samsung Galaxy Tab A 2018. Each schools received 2 chariots with 27 tablets in each and a WiFi . Each school is connected to a broadband internet connection.

[[File:Sugarizer stouen devices.png|thumb|Devices deployed at Saint-Ouen]]

Sugarizer OS is deployed on each tablets with about 20 android application launchable from Sugarizer OS.

Sugarizer Server is deployed on the infrastructure of city using Docker.

[[File:Sugarizerserver stouen architecture.png|thumb|Sugarizer Server architecture at Saint-Ouen deployment]]

== Next deployment step ==

The second phase of deployment is planned in Q4 2019 with 3 new schools. The objective is to deploy all city schools (13) by the end of 2020.

== More information ==

Deployment updates are posted on [https://twitter.com/sugarizerapp Sugarizer twitter account].

Contact [[User:Llaske|Lionel Laské]] for more information.

Sugarizer Saint-Ouen deployment

2019-05-11T20:49:21Z

Llaske: Description of Sugarizer Deployment in Saint-Ouen

== History ==

The Saint-Ouen deployment started in 2014 with the deployment of 25 XO-4 at the Mendela school by [http://olpc-france.org OLPC France].

In 2017 with replaced the 25 XO-4 by 25 tablets Lenovo Tab 2 A10-30 on Sugarizer OS bought with the help of the L'Oreal Fondation.

[[File:Sugarizer stouen childs.jpg|thumb|Children playing with Sugarizer in Mendela school at Saint-Ouen]]

Considering the positive feedbacks of teachers on field and its wish to deploy Android tablets in schools, the Saint-Ouen city decided in 2018 to launch a large deployment of Sugarizer in schools.

A partnership was set between Saint-Ouen city, the Inspection Academique (depending of French minister of education) and OLPC France.

== First phase of deployment ==

The first phase of deployment has started in 2019 witch is a deployment in 3 schools: Mendela, PEF and Petit-Prince. It means about 50 class and 1000 children.

Three training session animated by OLPC France are planned between March and May with teachers of each school.

[[File:Sugarizer stouen training.jpg|thumb|Teacher training workshop in March 2019]]

== Devices and software ==

Tablets deployed are Samsung Galaxy Tab A 2018. Each schools received 2 chariots with 27 tablets in each and a WiFi . Each school is connected to a broadband internet connection.

[[File:Sugarizer stouen devices.png|thumb|Devices deployed at Saint-Ouen]]

Sugarizer OS is deployed on each tablets with about 20 android application launchable from Sugarizer OS.

Sugarizer Server is deployed on the infrastructure of city using Docker.

[[File:Sugarizerserver stouen architecture.png|thumb|Sugarizer Server architecture at Saint-Ouen deployment]]

== Next deployment step ==

The second phase of deployment is planned in Q4 2019 with 3 new schools. The objective is to deploy all city schools (13) by the end of 2020.

== More information ==

Deployment updates are posted on [https://twitter.com/sugarizerapp Sugarizer twitter account].

Contact [[User:Llaske|Lionel Laské]] for more information.

File:Sugarizer stouen training.jpg

2019-05-11T20:38:03Z

Llaske:

Sugarizer teacher training in Saint-Ouen in March 2019

File:Sugarizerserver stouen architecture.png

2019-05-11T20:37:04Z

Llaske:

Sugarizer Server architecture in Saint-Ouen

File:Sugarizer stouen devices.png

2019-05-11T20:33:04Z

Llaske:

Devices selected in Saint-Ouen schools

File:Sugarizer stouen childs.jpg

2019-05-11T20:30:32Z

Llaske:

Children using Sugarizer in Mendela Saint-Ouen school

User:Llaske

2019-04-05T21:01:47Z

Llaske:

My name is Lionel Laské. I'm member of SugarLabs Oversight Board since 2015. My github account is [https://github.com/llaske llaske].

I'm also board member and co-founder in 2008 of the [http://olpc-france.org OLPC France grassroot].

OLPC France launch and maintain since 2009 a deployment of 200 XO-1/1.5 laptops in Madagascar on the [http://wiki.laptop.org/go/OLPC_Madagascar/Nosy_Komba Nosy Komba Island].

OLPC France launched also a small deployment of 50 XO-1.5 laptops in Saint-Denis (Paris suburb) between 2012 and 2014 and a deployment of 25 XO-4 laptops in Saint-Ouen (Paris suburb) in 2015-2016. Currently we hold a [http://sugarizer.org Sugarizer] deployment on 25 Android tablets in Saint-Ouen.

OLPC France promote One Laptop Per Child philosophy, Sugar and open source software and is also a reproducible association based on [http://movecommons.org Move Commons philosophy] so all our way of working is fully transparent and documented [http://olpc-france.org/wiki/index.php/Association].

OLPC France organized three SugarCamp in Paris in 2009, 2011 and 2014.

I'm the author of 8 Sugar activities [http://activities.sugarlabs.org/en/sugar/user/1454]. I'm also the author and the main contributor of [http://sugarizer.org Sugarizer], a way to deploy Sugar on any device.

OLPC France launched in 2017 two deployments of Sugarizer on Android tablets in Saint-Ouen (25 Lenovo Tablets) and in Stains (10 Lenovo Tablets).

Finally I was mentor for SugarLabs during Google Summer of Code 2013 to 2018 and I was mentor for Google Code-In in 2015 to 2018.

Oversight Board/2018-2020-candidates/Lionel Laské

2018-11-27T17:04:40Z

Llaske:

Hi all,

My name is Lionel Laské, you could learn more about me [[User:Llaske|here]].

As you probably know I'm author and main contributor of [https://sugarizer.org Sugarizer], a rewrite of Sugar to run on any device.

When I launched this project 5 years ago, my only objective was to maintain alive the spirit of Sugar and SugarLabs. Today I'm happy to see that in OLPC France we'll very soon reach the point where we deployed more Sugarizer devices than XO laptops: about 300.

I think the Sugarizer initiative is a success and could really be a nice future for Sugar and SugarLabs.

But I'm disappointed by the current situation of SugarLabs:

* We want to give the better learning experience to learner on their devices. But our marketing is not clear: our users doesn't want know what is Sugar and Sugarizer. They want the better learning platform, whatever technical stuff inside. We need to be more clear on it and guide our users with easy steps, not with complex and outdated wiki pages.
* Sugarizer contents grow regularly and we could expect that it allow us to expand our user base. But SugarLabs lack of maintainer for Sugar core and for Sugar activities. We need to be clear about which platforms we want to maintain and allow resources on it, including funds if need. But we need to be clear also about platforms and activities we are unable to maintain and mark it deprecated.
* We've done a good job with Google partnership with GSoC and GCI. But too much source code are just throw away at the end of GSoC and too much mentors are useless or are just unable to do the task they mentor. We need a real process to qualify projects and mentors for future GSoC and GCI: writing an idea in a wiki page should not be a way to qualify a project, attending a meeting should not be a way to qualify a good mentor.
* We are an open source community. It should be asserted on our webpage and we must choose tools compatible with that philosophy. It's not acceptable for example that today the SugarLabs webpage include multiple tracking tools.

With the help of other SLOB members, my wish is to try to solve these issues in next 2 years and to be sure that all of us could be proud to work on the leading learning platform.

Thanks for your attention and thanks in advance for your support.

Oversight Board/2018-2020-candidates/Lionel Laské

2018-11-27T17:01:27Z

Llaske:

Hi all,

My name is Lionel Laské, you could learn more about me [[User:Llaske|here]].

As you probably know I'm author and main contributor of [https://sugarizer.org Sugarizer], a rewrite of Sugar to run on any device.

When I launched this project 5 years ago, my only objective was to maintain alive the spirit of Sugar and SugarLabs. Today I'm happy to see that in OLPC France we'll very soon reach the point where we deployed more Sugarizer devices than XO laptops: about 300.

I think the Sugarizer initiative is a success and could really be a nice future for Sugar and SugarLabs.

But I'm disappointed by the current situation of SugarLabs:

* We want to give the better learning experience to learner on their devices. But our marketing is not clear: our users doesn't want know what is Sugar and Sugarizer. They want the better learning platform, whatever technical stuff inside. We need to be more clear on it and guide our users with easy steps, not with complex and outdated wiki pages.
* Sugarizer contents grow regularly and we could expect that it allow us to expand our user base. But SugarLabs lack of maintainer for Sugar core and for Sugar activities. We need to be clear about which platforms we want to maintain and allow resources on it, including funds if need. But we need to be clear also about platforms and activities we are unable to maintain and mark it deprecated.
* We've done a good job with Google partnership with GSoC and GCI. But too much source code are just throw away at the end of GSoC and too much mentors are useless or are just unable to do the task they mentor. We need a real process to qualify projects and mentors for future GSoC and GCI: writing an idea in a wiki page should not be a way to qualify a project, attending a meeting should not be a way to qualify a good mentor.
* We are an open source community. It should be asserted on our webpage and we must choose tools compatible with that philosophy. It's not acceptable than today the SugarLabs webpage include multiple tracking tools.

With the help of other SLOB members, my wish is to try to solve these issues in next 2 years and to be sure that all of us could be proud to work on the leading learning platform.

Thanks for your attention and thanks in advance for your support.

Oversight Board/2018-2020-candidates/Lionel Laské

2018-11-27T16:55:10Z

Llaske: Created page with "Hi all, You could learn more about me here. As you probably know I'm author and main contributor of [https://sugarizer.org Sugarizer], a rewrite of Sugar to..."

Hi all,

You could learn more about me [[User:Llaske|here]].

As you probably know I'm author and main contributor of [https://sugarizer.org Sugarizer], a rewrite of Sugar to run on any device.

When I launched this project 5 years ago, my only objective was to maintain alive the spirit of Sugar and SugarLabs. Today I'm happy to see that in OLPC France we'll very soon reach the point where we deployed more Sugarizer devices than XO laptops: about 300.

I think the Sugarizer initiative is a success and could really be a nice future for Sugar and SugarLabs.

But I'm disappointed by the current situation of SugarLabs:

* We want to give the better learning experience to learner on their devices. But our marketing is not clear: our users doesn't want know what is Sugar and Sugarizer. They want the better learning platform, whatever technical stuff inside. We need to be more clear on it and guide our users with easy steps, not with complex and outdated wiki pages.
* Sugarizer contents grow regularly and we could expect that it allow us to expand our user base. But SugarLabs lack of maintainer for Sugar core and for Sugar activities. We need to be clear about which platforms we want to maintain and allow resources on it, including funds if need. But we need to be clear also about platforms and activities we are unable to maintain and mark it deprecated.
* We've done a good job with Google partnership with GSoC and GCI. But too much source code are just throw away at the end of GSoC and too much mentors are useless or are just unable to do the task they mentor. We need a real process to qualify projects and mentors for future GSoC and GCI: writing an idea in a wiki page should not be a way to qualify a project, attending a meeting should not be a way to qualify a good mentor.
* We are an open source community. It should be asserted on our webpage and we must choose tools compatible with that philosophy. It's not acceptable than today the SugarLabs webpage include multiple tracking tools.

With the help of other SLOB members, my wish is to try to solve these issues in next 2 years and to be sure that all of us could be proud to work on the leading learning platform.

Thanks for your attention and thanks in advance for your support.

User:Llaske

2018-11-27T16:42:47Z

Llaske:

My name is Lionel Laské. I'm member of SugarLabs Oversight Board since 2015.

I'm also board member and co-founder in 2008 of the [http://olpc-france.org OLPC France grassroot].

OLPC France launch and maintain since 2009 a deployment of 200 XO-1/1.5 laptops in Madagascar on the [http://wiki.laptop.org/go/OLPC_Madagascar/Nosy_Komba Nosy Komba Island].

OLPC France launched also a small deployment of 50 XO-1.5 laptops in Saint-Denis (Paris suburb) between 2012 and 2014 and a deployment of 25 XO-4 laptops in Saint-Ouen (Paris suburb) in 2015-2016. Currently we hold a [http://sugarizer.org Sugarizer] deployment on 25 Android tablets in Saint-Ouen.

OLPC France promote One Laptop Per Child philosophy, Sugar and open source software and is also a reproducible association based on [http://movecommons.org Move Commons philosophy] so all our way of working is fully transparent and documented [http://olpc-france.org/wiki/index.php/Association].

OLPC France organized three SugarCamp in Paris in 2009, 2011 and 2014.

I'm the author of 8 Sugar activities [http://activities.sugarlabs.org/en/sugar/user/1454]. I'm also the author and the main contributor of [http://sugarizer.org Sugarizer], a way to deploy Sugar on any device.

OLPC France launched in 2017 two deployments of Sugarizer on Android tablets in Saint-Ouen (25 Lenovo Tablets) and in Stains (10 Lenovo Tablets).

Finally I was mentor for SugarLabs during Google Summer of Code 2013 to 2018 and I was mentor for Google Code-In in 2015 to 2018.

Summer of Code/2018/Sugarizer Exerciser Activity

2018-04-30T16:09:50Z

Llaske:

== About The Project: ==
The aim of the project is to create a Sugarizer Activity that can be used by the educators to create exercises for their students based on their curriculum. The educators will be able to enter the questions and answers into the activity and share that activity on the server for students to use. After the activity is shared the students on the server will be able to do the assignment and get a final score at the end.

=== Community Bonding Period: ===

===== First Meeting (30/4/18): =====
The meeting was centered around communication, due dates and structure/ time of future meetings.
During the bouding period we'll do 2 things:
* Use the Sprint Math activity developed by Mankirat as a sandbox to learn development of a Sugarizer activity
* Detail UI and features of the Exerciser activity

In the first meeting the following tasks were asked:
* Build a wiki page for the project
* Update the UI of sprint math activity
* Refactor code of sprint math activity so that presence can be added later
* Update the SVG icon of sprint math activity
* Integrate Palette in sprint math activity
* Design mockups of exercise activity (GSoC project)

Summer of Code/2018

2018-01-27T10:49:25Z

Llaske: Add Sugarizer project

== Sponsored Projects ==

[https://summerofcode.withgoogle.com/organizations/5544862897143808/ Sugar Labs at GSoC]

== Project Ideas ==

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title
!Mentor
!Project

|-
| valign=top width="15%" style="background:#e3e4e5;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
| align=left valign=top |
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details. See [[Translation Team]] for framework description.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |Full-color icons
| valign=top width="15%" |Design team
| align=left valign=top |
;Brief explanation: We have been discussing the implications of removing the duo-tone restriction on Sugar icons, allowing for full-color icons. We can likely use badges to compensate for any functionality we'd lose. (See [https://medium.com/@sidhant/designing-interfaces-for-education-systems-with-sugar-labs-rethinking-icons-on-sugar-614120e7ec6f] as one example of how we might proceed.)
;Expected results: A patch to Sugar that uses badges to manage the icon notifications such as activity and sharing
;Knowledge prerequisites: Knowledge of GTK; Python.

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks optimizations [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Music Blocks has never been optimized in any way. It would be helpful to review the tone.js optimization recommendations, as well as build some unit tests to measure and improve the program itself.
;Expected results: A more robust and responsive Music Blocks.
;Knowledge prerequisites: Knowledge of JavaScript, unit testing

|-
| valign=top width="15%" style="background:#e3e4e5;" |Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/labels/temperament MB issues for temperament], [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF Articles about temperament, scales, and tuning] and [https://owncloud.libretools.com/index.php/s/PmPfZ1yMhimQomG various materials related to temperament (.tb files that achieve temperament with existing MB features, videos of those files being performed, notes)]
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory

|-
| valign=top width="15%" style="background:#e3e4e5;" |Maintenance of activities.sugarlabs.org (ASLO)
| valign=top width="15%" | Sam CG
| align=left valign=top |
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded. During GSoC 2017 we built ASLO v3 to address a number of deficiencies. But we have a few odds and ends that need to be addressed to bring the new site on line.
;Expected results: Update missing license and repository info on the activities found in the Sugar Labs github repository. Popular the database for the new ASLO. Do extensive testing (including creating some test suites.) Document future maintenance on the Wiki.
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git. See [https://github.com/sugarlabs/aslo-v3].

|-
| valign=top width="15%" style="background:#e3e4e5;" |Lesson Plans for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima
Hrishi Patel
| align=left valign=top |
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need some more scaffolding in the form of lesson plans.
;Expected results: A website and PDF document that can be bound.
;Knowledge prerequisites: Knowledge of music theory, writing skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Just say no to GTK2
| valign=top width="15%" | Ignacio Rodriguez Cristian Garcia
Abhijit Patel Ibiam Chihurumnaya
| align=left valign=top |
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.
;Expected results: New versions of at least 25 existing Sugar activities.
;Knowledge prerequisites: Knowledge of GTK, GST, and Python

|-
| valign=top width="15%" style="background:#e3e4e5;" |Updating a new design of Sugarlabs wiki
| valign=top width="15%" | Jaskirat Singh Walter bender
| align=left valign=top |
;Brief explanation: we are lacking in look of wiki.sugarlabs.org page. It looks ugly and unfriendly and need to be updated with a good design
;Expected results: New design of Wiki page of Sugarlabs
;Knowledge prerequisites: Knowledge of mediawiki and use of some basic languages

|-
|valign=top width="15%" style="background:#e3e4e5;" |Outreach
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: We don't have a very friendly approach to outreach to new contributors. It would be great to make it easier to get involved and to navigate the path towards contributing to Sugar Labs. The goal of this project is to revamp our approach to outreach.
;Expected results: A set of pages similar to [https://publiclab.github.io/community-toolbox/] and [https://publiclab.org/wiki/software-outreach]
;Knowledge prerequisites: community outreach experience; some coding experience (to create requisite artifacts)

|-
|valign=top width="15%" style="background:#e3e4e5;" |Making a Beginner Guide
| valign=top width="15%" | Jaskirat Singh Walter Bender
| align=left valign=top |
;Brief explanation: We don't have a beginner guide for the newcomers to the Sugar labs Community. It would be great to guide them by guiding them how to contribute through making these "form where to start? , What to start? , How to start? , Where to submit? " . [http://api.coala.io/en/latest/Developers/Newcomers_Guide.html Example] The goal of this project is to Help newcomers to get introduce in easy way to the world of Sugar Labs
;Expected results: A set of website pages and also documentation in Pdf form with this the problems of newcomers about their contribution will be solved and they can work easily
;Knowledge prerequisites: community research , GitHub , coding experience ( HTML, CSS )

|-
| valign=top width="15%" style="background:#e3e4e5;" |New Social Sugarlabs website [[File:Social Site.jpg|90px|thumb|center]]
| valign=top width="15%" | Jaskirat Singh Samson Goddy
| align=left valign=top |
;Brief explanation: Its a social website that can be used to attract maximum users and everything ( Blogs, New projects, Softwares, Activities, etc) can be uploaded on it which will attract more user and create their interest
;Expected results: It should be over viewed by people around the world
;Knowledge prerequisites: Good Layout designing and coding experience

|-
| valign=top width="15%" style="background:#e3e4e5;" |Making a marketing animated website page of sugarlabs
| valign=top width="15%" | Jaskirat Singh Samson Goddy
| align=left valign=top |
;Brief explanation:We need to develop a link that is website-page that will include a page with animations explaining all the things we have in Sugarlabs (as a marketing) like these examples [http://meta-liquid.com/ See[1] ], [http://education.iceandsky.com/ See [2] ]
;Expected results: A UI/UX layout and a main page that can be used to market the things in an animated way
;Knowledge prerequisites: Knowledge of marketing and use of some basic languages ( HTML, CSS styling, PHP)

|-
| valign=top width="15%" style="background:#e3e4e5;" |Lilypond Methodical Improvements to how Music Blocks generates Lilypond output [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: Music Blocks is capable of exporting [https://www.lilypond.org Lilypond] code of which general instructions can be found [https://github.com/walterbender/musicblocks/tree/master/guide#BEYOND-MUSIC-BLOCKS here in the Music Blocks guide] and its [https://github.com/walterbender/musicblocks/ source code can be found here]. We would like to improve existing code where needed and implement needed features in a methodical way, which means we must 1) document how the Music Blocks source code works for current and future developers to learn and benefit from and 2) project manage this portion of Music Blocks development (e.g. "what works" and "what needs to be done". [https://owncloud.libretools.com/index.php/s/tgJAX5yMEzQsENf An example of a draft of a simple type of this analysis exists for you to start from.]), as well as 3) implement and improve features.
;Expected results: Implement and improve lilypond export features; Detailed documentation created for developer audience that details how Music Blocks exports to Lilypond; documentation to help manage what needs to be completed.
;Knowledge prerequisites: Literacy in reading music; functional knowledge of Lilypond code (some of your own scores would be nice); Organizational and Project Management Skills; JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |Migrating Planet Sugar to Medium
| valign=top width="15%" | Jaskirat Singh Samson Goddy
| align=left valign=top |
;Brief explanation:We need to change the look of [http://planet.sugarlabs.org/ Planet Sugar] by embedding [https://medium.com/ Medium] ( a blogger )into it by using Medium API but design should be changed> Better and interactive layout
;Expected results: A UI/UX layout and an interactive design which can be easy to use and outreach more.
;Knowledge prerequisites: Knowledge of web designing and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)

|-
| valign=top width="15%" style="background:#e3e4e5;" |Making Testimonials page on Sugar Labs website
| valign=top width="15%" | Jaskirat Singh Walter Bender
| align=left valign=top |
;Brief explanation:Well, Develop a testimonal webpage on Sugarlabs website by making a good research about the users who have experienced the world of Sugar. That should include videos, blog posts and many more things. For such type of layout example visit ( https://www.chownow.com/testimonials-reviews ) and ( https://www.codecademy.com/stories )
;Expected results: A good layout with more views about sugar Users
;Knowledge prerequisites: Make a research about people using Sugar ...get interaction with them ; know about Sugarlabs and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks' First Steps for Robotics [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: What is needed to integrate Music Blocks with Robotics? This project is 1) to experiment with existing technologies to see what is already possible, 2) develop features (e.g. plugins, hardware modifications) needed to make interfacing possible, and 3) document the entire process and next steps
;Expected results: A working method for interfacing with a simple robot; additional features within MB to ease interfacing; and full documentation of how to recreate successful projects (that a classroom could use); communication (we do not want to guess what experiments you are doing by yourself--do not be shy to send emails, videos, pictures DAILY!!!)
;Knowledge prerequisites: Understanding of Javascript (Music Blocks source code) and robotics (no particular method requested, just make sure it is free/libre); demonstratable documentation and self-management skills; NOTE: we value quality, clear ideas over expensive or pretty robots

|-
| valign=top width="15%" style="background:#e3e4e5;" |Create Examples, Compositions, and New Experiments Every Day! [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top |
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has some examples already, but it would be nice to have one ambitious student really work for the summer to make new creative, thoughtful code everyday. Secondary, but important goals, are bug reports when bugs are found, feature suggestions, and overall good and frequent communication with the Music Blocks team.
;Expected results: Quality examples sent daily; variety of styles; runs entire gamut in terms of blocks used (we want a number of great examples for each and every block feature); organized documentation of all examples created, which can be finalized in the final weeks of GSoC
;Knowledge prerequisites: Understanding of Music Blocks program; A good proposal is one that has a well-thought out and detailed list of music projects for each day of GSoC (timeframes, blocks used, musical styles, name of music to be transcribed); experience with music and composition/theory is a definate plus.

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks UI Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has a good enough UI, but there are open issues remaining and it would be nice if a person with a high level of understanding of graphics and style were to proposal and implement changes that unify the entire look and feel of Music Blocks.
;Expected results: Visually unified, beautiful and intuitive Music Blocks interface. Documentation to benefit future contributors to understand "what Music Blocks style is" (obviously this may change in the future, but a thoughtful rationale for the new style is expected).
;Knowledge prerequisites: Understanding of CSS, Javascript, and HTML. Published work on UI (links to code, websites, etc)

|-
| valign=top width="15%" style="background:#e3e4e5;" |Scales/Modes/Keys Design Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser Sachiko Nakajima
| align=left valign=top |
;Brief explanation: There are features in [https://github.com/walterbender/musicblocks/tree/master/guide#3213-setting-voice-and-keys MB for exploring modes/scales/keys which can are referenced in the guide]. However, we suspect that there are better ways to organize keys. This project would be to reimagine how MB organizes pitches. We recommend that you read the discussions that have taken place already on GitHub as well as research how keys work as well as [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF scholarly articles about temperament, scales, and tuning]. Keep in mind that we would like to prepare for the possibility of chromatic pitch spaces that are not 12--for example, a chroma of 5 or 7 or 13, etc. What features and widgets are needed?
;Expected results: Detailed documentation created for developer audience that specifies 1) proposed features and overall design, 2) purpose of design choices, 3) audit of code (e.g. What changes to our current approach may be necessary? Are there libraries that may be useful?) 4) widget design proposal as well as MB code design proposal.
;Knowledge prerequisites: Understanding of Music Theory and/or group (or set) theory. Please read the articles at https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF We are looking for candidates that can make a simple and effective design that a future (or current) developer could read and implement.

|-
| valign=top width="15%" style="background:#e3e4e5;" |Create UI features for music analysis and visualization [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top |
;Brief explanation: Music Blocks does not yet have a robust set of tools to help the user analyze their music (e.g. highest pitch, lowest pitch, pitches used, keys, musical form, intervals etc.). Additionally, users would very much benefit from features to help them visualize the way their music is constructed. Perhaps we could even create some features to help the user choose a style of music and the analysis highlights movements that violate that style's particular rules.
;Expected results: New Features.
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; javascript knowledge

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks Musical Ornaments Features [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: The neighbor block feature is the first of a series of musical ornament features. There are many more possibilities, some of which are described [https://github.com/walterbender/musicblocks/issues/909 in issue 909]. The project would be to implement and document these features as well as to create example programs.
;Expected results: New Features, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; javascript knowledge; knowledge of Music Blocks and tone.js internals (please research)

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks Widget Improvements [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: Music Blocks has a number of features to help users conceptualize musical concepts, which also help to create code. Please see [https://github.com/walterbender/musicblocks/tree/master/guide#widgets the guide for more]. There are a number of widgets that have not been integrated at all as well. This project would be to 1) fix widget bugs, 2) implement unfinished features ([https://github.com/walterbender/musicblocks/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+widgets+ see issues]), and 3) document and fully integrate these new features and improve existing features. [https://github.com/walterbender/musicblocks/issues/663 is also a related feature]
;Expected results: New Features, fixes, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; javascript knowledge; knowledge of Music Blocks and tone.js internals (please research)
|-
|valign=top width="15%" style="background:#e3e4e5;" |Sugarizer School Box [[File:Sugarizerschoolbox.jpg|90px|thumb|center]]
|valign=top width="15%" |Michaël Ohayon

Lionel Laské
|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the javascript version of Sugar, making education available of many platforms from web to mobile.:The app is composed by both a client side and a server side.
:The idea of this project is to develop a package to simplify deployment of Sugarizer in schools.
: This package will take two forms:
: 1 - An image for Raspberry Pi that could be flashed on a sd card that could automatically start a sugarizer server at boot and displays sugarizer client on the Pi. The server will be accessible by other devices from the local network. So the teacher has just to plug the RaspberryPI to expose a WiFi and the Sugarizer Server API/WebApp. So any computer connected to this WiFi could use Sugarizer Server WebApp and any tablet with Sugarizer App connected to this WiFi could benefit to collaboration, presence and backup its content on the server.
: 2 - Create one click to deploy scripts, to deploy a full Sugarizer stack on popular providers such as Amazon AWS or Heroku. So anyone could deploy a new Sugarizer Server instance on one of popular cloud platform without the need to dig into a complex setup process.
;Expected results:Raspberry Pi image files. Deployment scripts.
;Knowledge prerequisites:[https://github.com/llaske/sugarizer-server Sugarizer Server] knowledge, Linux system administration knowledge, bash scripting capabilities, Docker enthusiasm. (This project may require to download many system files)
|-
|valign=top width="15%" style="background:#e3e4e5;" |Sugarizer Exerciser activity [[File:Sugarizerexerciser.jpg|90px|thumb|center]]
|valign=top width="15%" |Lionel Laské

Michaël Ohayon

|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the javascript version of Sugar, making education available of many platforms from web to mobile.
:The idea of this project is to create a new Sugarizer activity to allow users to create exercise and let other users play to this exercise.
:The activity will propose different templates for exercises. Typical exercises could be multiple-choice question, reordering a list of items, cloze text, group assignment, ...
:Once created, the exercise could be played locally or shared on the network using Sugarizer presence. At the end of the exercise a graph will give results for each participants.
:The activity should allow to integrate multimedia element (images, sounds, videos) coming from the Journal. The activity should as simple as possible so even a child should be able to create an exercise and share it.
:Like all Sugarizer activity, the activity should: adopt the Sugar UI, be responsive (work on any screen size), work with the keyboard and with the mouse (to support touch screen), use journal and use localization.
:Features inspiration could be found on [https://learningapps.org LearningApps], [https://www.google.com/forms/ Google Forms], [https://www.limesurvey.org LimeSurvey], ...
;Expected results:A Sugarizer activity.
;Knowledge prerequisites: HTML/JavaScript, UI Design, [https://github.com/llaske/sugarizer/blob/dev/docs/tutorial.md Sugarizer Development Tutorial]
|}

File:Sugarizerexerciser.jpg

2018-01-27T10:29:18Z

Llaske:

File:Sugarizerschoolbox.jpg

2018-01-27T10:28:49Z

Llaske:

Google Code In 2017/background

2017-12-01T21:10:25Z

Llaske: Specify Sugarizer pre-requisite

=== Basics: Attribution and Licensing ===

Read [[Attribution and Licensing]], as both are important for all submissions.

=== Setting up the Sugar environment ===

There are several options for setting up the Sugar environment for development, depending on what equipment you have;

{| class="wikitable"
|-
! Your Equipment !! Your Operating System !! Our Recommendation
|-
| rowspan="2" | You have only one computer and don't want to erase it
| Linux, Windows, macOS, or iOS
| Install virtualisation software, make a new virtual machine and install [[Live Build|Sugar Live Build]], [[SoaS|Sugar on a Stick]], [[Ubuntu]], [[Fedora]], or [[Debian]].
For Sugarizer, your could use your computer.
|-
| Linux
| Install Sugar packages from your distribution, see [[Ubuntu]], [[Fedora]] or [[Debian]]. For other distributions, contact your distribution community.
|-
| You have another computer that can be erased
| Doesn't matter
| Install [[Live Build|Sugar Live Build]], [[SoaS|Sugar on a Stick]], [[Ubuntu]], [[Fedora]], or [[Debian]].
|}

What's the difference between Live Build, Sugar on a Stick and the various Linux options?

{| class="wikitable"
|-
! !! Live Build (based on Debian) !! Sugar on a Stick (based on Fedora) !! Ubuntu, Debian or Fedora
|-
! Sugar desktop user experience on startup
| yes, 0.112 || yes, 0.110 || no, must install packages
|-
! Good for Sugar activity development
| yes || no, must install packages || no, must install packages
|-
! Good for Sugar desktop module development
| yes, source code included || no, must install git and use rpmbuild || no, must install packages
|-
! Works on a spare computer
| yes || yes || yes
|-
! Works as a Virtual Machine
| yes || yes || yes
|-
! Good for Sugarizer development
| colspan="3" | no, use your normal computer
|}

See also [https://developer.sugarlabs.org/dev-environment.md.html Setup a development environment].

=== Getting started with coding in Sugar ===

Sugar development is in either Python or JavaScript languages.

* For the JavaScript language, you will need knowledge of;
** JavaScript;
** HTML5;
** web browsers;
** web design; and,
** web deployment.
* For the Python language, you will need knowledge of;
** [https://www.python.org/ Python];
** the [https://pygobject.readthedocs.io/en/latest/ PyGObject] package;
** the [https://python-gtk-3-tutorial.readthedocs.org/en/latest/ Python bindings] for [https://www.gtk.org/ GTK+ 3]; and
** the [https://lazka.github.io/pgi-docs/#Gtk-3.0 Gtk-3.0 section of the PyGObject API Reference].
* For both, you will need knowledge of Sugar activity development, see the book [http://www.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities!]

Python programmers, you must run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and pyflakes on your code ''before'' submitting your patches.

=== Getting started with GIT ===

Some knowledge of git is important as your work will be submitted to our [https://github.com/sugarlabs git repositories]. The basic mechanism is a pull-request (PR), which is explained in [https://developer.sugarlabs.org/contributing.md.html Contributing].

''It is required that you follow the steps outlined on the [https://developer.sugarlabs.org/contributing.md.html Contributing] page when doing coding and documentation tasks in GCI.''

GitHub provides a [https://try.github.io/levels/1/challenges/1 tutorial]. There are many other guides to GIT as well.

Our old bug tracker is https://bugs.sugarlabs.org, but these days, we mostly report bugs using the ''issues'' feature of GitHub. (See https://guides.github.com/features/issues/ for details on GitHub Issues.)

=== Getting started with Sugarizer ===

Sugar Web Framework is the [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md JavaScript Framework for Sugar]. [http://sugarizer.org Sugarizer] is a subset of Sugar that allow running activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.

=== Getting a wiki account ===

Some tasks require that you make edits to this wiki for which you'll need an account. Please email walter @ sugarlabs . org to request an account.

=== Getting help ===

Got a problem? Ask your mentors, ask other students, or ask the Sugar Labs community.

The Sugar Labs community is large, and there are people who are not mentors in the contest. Mentors are [[Google_Code_In_2017#Mentors|listed]]. Everyone else you talk with may be a non-mentor.

As part of Sugar Labs community, non-mentors are to treat students in accord with the [[Sugar_Labs/Legal/Code_of_Conduct|Code of Conduct]], and as if they are new to Sugar Labs.

Students should keep in mind that some people are non-mentors, and cannot see the contest tasks, contest progress, dates, or information about students. When communicating widely, be sure to;

* introduce yourself, the first time;
* tell us what your task is, without relying on a link to the task (because we probably can't see it);
* talk about the task as if you want to do it yourself, not because of the contest; and,
* defend your technical decisions without using the contest as a defence.

Non-mentors may give good guidance on technical decisions, but bad guidance on how they think a task is judged. Always consult with your mentors as well.

Oversight Board/2017-2019-candidates

2017-09-02T09:13:55Z

Llaske: /* [Lionel Laské] */

==Election==

There are to be four (4) [[Oversight Board]] slots to be elected for the 2017-2019 period, currently held by Walter, Adam, Lionel and Sameer.

==Calendar==

{| class="wikitable"
|Stage I
|August 15
|Announcement of election date and first call for candidates.
|-
|Stage II
|August 30
|Reminder of election date and second call for candidates.
|-
|Stage III
|September 15
|[[#Candidates|Candidates' Wiki submissions]] deadline.
|-
|Stage IV
|October 1-15
|Election.
|}

==Candidates==

Candidates should create a Wiki entry at [[#Candidates|Candidates' Wiki submissions]], one entry per candidate, 1500 characters maximum length, sharing their vision and motivation.

Candidates should read and understand the terms of the [[Sugar_Labs/SFC_Fiscal_Agreement|Software Freedom Conservancy Fiscal Agreement]], because such terms bind our behavior as Sugar Labs Oversight Board and all our internal policies and procedures as a Project and as an organization.

Among other terms, please note the Project Management, Communications and Activities terms in the agreement provide that:

2.1. The Oversight Board Will Manage the Project.

2.2. The Project Will Be Free Software.

6. Representation of the Project in Conservancy: The Representative will have the authority to instruct Conservancy on the Project’s behalf on all matters.

The terms contemplate that the Oversight Board elects a single individual to communicate with Conservancy (the “Representative”) and shall notify Conservancy promptly following the election of a new Representative.

By publishing your candidacy below, you imply that in case you are elected a Sugar Labs Oversight board member you will honor the agreement terms.

=Devin Ulibarri=
Devin Ulibarri is a musician and an educator who became interested in free/libre software in 2014 during research for the Center for Music-in-Education (Boston). Devin pursued research into the implications for "software libre in education" which led him to believe that free/libre software is best for teaching and learning. He was soon introduced to SugarLabs, which both empowers teachers/learners with software freedom as well as offers tools to exercise those freedoms in a community setting.

Since his introduction to the SugarLabs community, Devin has participated heavily in the development of Music Blocks, a programming language for music. Within the SugarLabs community, Devin offers conceptual recommendations, design ideas, mockups, testing, minor patches, and community involvement on GitHub and Sugar's IRC. In his local community, Devin has represented Music Blocks software as a workshop lecturer (Constructionism Conference in Thailand, Canopy of Somerville) as well as a class instructor (YMCA Malden).

As an oversight board member, Devin would bring his insight as an experienced classroom teacher, an artist, and a free/libre software advocate. Devin has been described as "a very patient person", which he hopes would be a contribution to the oversight board if elected.

=Walter Bender=
After a decade of working on Sugar, I am reflecting on how we engage learners. We provide programming environments (e.g., Turtle and Music Blocks) and mechanism for debugging, collaboration, expression, and reflection. Our adherence to the principles of Free/Libre Software provides scaffolding for personal expression through programming and for surfacing personal responsibility, a sense of community, and unbounded expectations of Sugar users turned Sugar developers.

Where have we fallen short? Edtech is become big business: selling Apps and content is more lucrative and facile than the hard work of engaging teacher and learners in authentic problem-solving. There is a strong temptation to make things as simple as possible so as to reach the broadest possible audience. But some things are inherently complex. Apps might be fun, but the hard part of “hard fun” is in reaching towards complexity.

We are going where the learners are: Sugar as a Web app, on Android, or on iOS, (Sugarizer) and, tracking the growth of the Maker Movement, we now support Sugar on Raspbian.
“It is said that the best way to learn something is to teach it—and perhaps writing a teaching program is better still in its insistence on forcing one to consider all possible misunderstandings and mistakes.” — Seymour Papert

I have made mistakes, but as part of a learning community we will do better.

“Homework is boring. Looking for bugs is fun.” —Ezequiel Pereira

Let's continue to provide the basis for some fun.

=Sebastian Silva=

The mission of the Sugar Labs Oversight Board is to ensure the community has clarity of purpose and the means to attain its goals.

Sugar Labs needs to recognize that our community is '''diverse'''. Therefore, there are diverse purposes that may be clear and at the same time opposed.

We should provide a '''safe and neutral space''' for dialogue on the technology and education that underlies our projects. We need to approve and enforce a ''code of conduct''.

Finally, the reason for Sugar Labs to exist under the SFC is to '''facilitate the flow of resources''' to volunteers with valuable projects. We should strive to open and fund open calls with funds for development, infrastructure and end user products.

=== About Sebastian ===
Sebastian is father to two precious children that are being homeschooled in collaboration with his dear wife and co-creator Laura Vargas.

As a child, Sebastian learned to program with Logo and soon outgrew it to be charmed with Python and raise the flag of Free/Libre Software. He loves writing Sugar Activities; His latest is a collaborative [http://educa.juegos/#sugarlabs_platform_2017 Python IDE] that he hopes you'll love too.

Currently he lives with his family in a cabin in the Amazon rainforest and teaches Karate and videogame programming to the kids in the vicinity, sustaining a lifestyle seeking harmony with nature and providing services of software artisanship and systems gardening remotely.

=Lionel Laské=
Learn more about my background [[User:Llaske|here]].

Like lot of you I've joined SugarLabs at the beginning of the OLPC project. As cofounder of [http://olpc-france.org OLPC France grassroot], I've worked hard to deploy it on the field and contribute to expand it both in term of activities and in term of French content.
Because the OLPC project and the XO laptop was declining year after year, I've decided 5 years ago to launch the [http://sugarizer.org Sugarizer] initiative. My objective was to write a new page of Sugar history by expanding its compatibility to any device, specifically the favorite education device of today: tablets. I'm very proud that today, two deployments already start to use Sugarizer on Android tablets.

Deployed on more than 2 millions of devices and supported by millions of users, Sugar is the #1 learning platform in the world. But we need to convince this large community that a future exist out of the XO laptop. It's my ambition as candidate to the SugarLabs Oversight Board. As I've done in past month as SLOB member, I will support projects where the goal is to expand the community and give a vision to SugarLabs. Even if it could hurt sometime, I will also refuse to spend our limited resources on ways that not fit into its vision. We're all volunteers and our time is precious, let's continue to invest it where it will be the most useful: give to learners the better free libre education platform.

=[Candidate Name]=
Entry

=[Candidate Name]=
Entry

...

==References==

This election is being run by the [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]] which was [[Oversight_Board/Decisions#2017-01-06|appointed in January]], along with Dave Crossland
as an impartial election oversight party.

An update from the Membership and Elections Committee was [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900181 received] during the Oversight Board meeting of August 4. Also listed were the [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900205 expiring slots].

Oversight Board/2017-2019-candidates

2017-09-02T09:13:17Z

Llaske: /* [Candidate Name] */

==Election==

There are to be four (4) [[Oversight Board]] slots to be elected for the 2017-2019 period, currently held by Walter, Adam, Lionel and Sameer.

==Calendar==

{| class="wikitable"
|Stage I
|August 15
|Announcement of election date and first call for candidates.
|-
|Stage II
|August 30
|Reminder of election date and second call for candidates.
|-
|Stage III
|September 15
|[[#Candidates|Candidates' Wiki submissions]] deadline.
|-
|Stage IV
|October 1-15
|Election.
|}

==Candidates==

Candidates should create a Wiki entry at [[#Candidates|Candidates' Wiki submissions]], one entry per candidate, 1500 characters maximum length, sharing their vision and motivation.

Candidates should read and understand the terms of the [[Sugar_Labs/SFC_Fiscal_Agreement|Software Freedom Conservancy Fiscal Agreement]], because such terms bind our behavior as Sugar Labs Oversight Board and all our internal policies and procedures as a Project and as an organization.

Among other terms, please note the Project Management, Communications and Activities terms in the agreement provide that:

2.1. The Oversight Board Will Manage the Project.

2.2. The Project Will Be Free Software.

6. Representation of the Project in Conservancy: The Representative will have the authority to instruct Conservancy on the Project’s behalf on all matters.

The terms contemplate that the Oversight Board elects a single individual to communicate with Conservancy (the “Representative”) and shall notify Conservancy promptly following the election of a new Representative.

By publishing your candidacy below, you imply that in case you are elected a Sugar Labs Oversight board member you will honor the agreement terms.

=Devin Ulibarri=
Devin Ulibarri is a musician and an educator who became interested in free/libre software in 2014 during research for the Center for Music-in-Education (Boston). Devin pursued research into the implications for "software libre in education" which led him to believe that free/libre software is best for teaching and learning. He was soon introduced to SugarLabs, which both empowers teachers/learners with software freedom as well as offers tools to exercise those freedoms in a community setting.

Since his introduction to the SugarLabs community, Devin has participated heavily in the development of Music Blocks, a programming language for music. Within the SugarLabs community, Devin offers conceptual recommendations, design ideas, mockups, testing, minor patches, and community involvement on GitHub and Sugar's IRC. In his local community, Devin has represented Music Blocks software as a workshop lecturer (Constructionism Conference in Thailand, Canopy of Somerville) as well as a class instructor (YMCA Malden).

As an oversight board member, Devin would bring his insight as an experienced classroom teacher, an artist, and a free/libre software advocate. Devin has been described as "a very patient person", which he hopes would be a contribution to the oversight board if elected.

=Walter Bender=
After a decade of working on Sugar, I am reflecting on how we engage learners. We provide programming environments (e.g., Turtle and Music Blocks) and mechanism for debugging, collaboration, expression, and reflection. Our adherence to the principles of Free/Libre Software provides scaffolding for personal expression through programming and for surfacing personal responsibility, a sense of community, and unbounded expectations of Sugar users turned Sugar developers.

Where have we fallen short? Edtech is become big business: selling Apps and content is more lucrative and facile than the hard work of engaging teacher and learners in authentic problem-solving. There is a strong temptation to make things as simple as possible so as to reach the broadest possible audience. But some things are inherently complex. Apps might be fun, but the hard part of “hard fun” is in reaching towards complexity.

We are going where the learners are: Sugar as a Web app, on Android, or on iOS, (Sugarizer) and, tracking the growth of the Maker Movement, we now support Sugar on Raspbian.
“It is said that the best way to learn something is to teach it—and perhaps writing a teaching program is better still in its insistence on forcing one to consider all possible misunderstandings and mistakes.” — Seymour Papert

I have made mistakes, but as part of a learning community we will do better.

“Homework is boring. Looking for bugs is fun.” —Ezequiel Pereira

Let's continue to provide the basis for some fun.

=Sebastian Silva=

The mission of the Sugar Labs Oversight Board is to ensure the community has clarity of purpose and the means to attain its goals.

Sugar Labs needs to recognize that our community is '''diverse'''. Therefore, there are diverse purposes that may be clear and at the same time opposed.

We should provide a '''safe and neutral space''' for dialogue on the technology and education that underlies our projects. We need to approve and enforce a ''code of conduct''.

Finally, the reason for Sugar Labs to exist under the SFC is to '''facilitate the flow of resources''' to volunteers with valuable projects. We should strive to open and fund open calls with funds for development, infrastructure and end user products.

=== About Sebastian ===
Sebastian is father to two precious children that are being homeschooled in collaboration with his dear wife and co-creator Laura Vargas.

As a child, Sebastian learned to program with Logo and soon outgrew it to be charmed with Python and raise the flag of Free/Libre Software. He loves writing Sugar Activities; His latest is a collaborative [http://educa.juegos/#sugarlabs_platform_2017 Python IDE] that he hopes you'll love too.

Currently he lives with his family in a cabin in the Amazon rainforest and teaches Karate and videogame programming to the kids in the vicinity, sustaining a lifestyle seeking harmony with nature and providing services of software artisanship and systems gardening remotely.

=[Lionel Laské]=
Learn more about my background [[User:Llaske|here]].

Like lot of you I've joined SugarLabs at the beginning of the OLPC project. As cofounder of [http://olpc-france.org OLPC France grassroot], I've worked hard to deploy it on the field and contribute to expand it both in term of activities and in term of French content.
Because the OLPC project and the XO laptop was declining year after year, I've decided 5 years ago to launch the [http://sugarizer.org Sugarizer] initiative. My objective was to write a new page of Sugar history by expanding its compatibility to any device, specifically the favorite education device of today: tablets. I'm very proud that today, two deployments already start to use Sugarizer on Android tablets.

Deployed on more than 2 millions of devices and supported by millions of users, Sugar is the #1 learning platform in the world. But we need to convince this large community that a future exist out of the XO laptop. It's my ambition as candidate to the SugarLabs Oversight Board. As I've done in past month as SLOB member, I will support projects where the goal is to expand the community and give a vision to SugarLabs. Even if it could hurt sometime, I will also refuse to spend our limited resources on ways that not fit into its vision. We're all volunteers and our time is precious, let's continue to invest it where it will be the most useful: give to learners the better free libre education platform.

=[Candidate Name]=
Entry

=[Candidate Name]=
Entry

...

==References==

This election is being run by the [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]] which was [[Oversight_Board/Decisions#2017-01-06|appointed in January]], along with Dave Crossland
as an impartial election oversight party.

An update from the Membership and Elections Committee was [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900181 received] during the Oversight Board meeting of August 4. Also listed were the [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900205 expiring slots].

User:Llaske

2017-08-27T19:54:57Z

Llaske:

My name is Lionel Laské. I'm member of SugarLabs Oversight Board since 2015.

I'm also board member and co-founder in 2008 of the [http://olpc-france.org OLPC France grassroot].

OLPC France launch and maintain since 2009 a deployment of 200 XO-1/1.5 laptops in Madagascar on the [http://wiki.laptop.org/go/OLPC_Madagascar/Nosy_Komba Nosy Komba Island].

OLPC France launched also a small deployment of 50 XO-1.5 laptops in Saint-Denis (Paris suburb) between 2012 and 2014 and a deployment of 25 XO-4 laptops in Saint-Ouen (Paris suburb) in 2015-2016. Currently we hold a [http://sugarizer.org Sugarizer] deployment on 25 Android tablets in Saint-Ouen.

OLPC France promote One Laptop Per Child philosophy, Sugar and open source software and is also a reproducible association based on [http://movecommons.org Move Commons philosophy] so all our way of working is fully transparent and documented [http://olpc-france.org/wiki/index.php/Association].

OLPC France organized three SugarCamp in Paris in 2009, 2011 and 2014.

I'm the author of 8 Sugar activities [http://activities.sugarlabs.org/en/sugar/user/1454]. I'm also the author and the main contributor of [http://sugarizer.org Sugarizer], a way to deploy Sugar on any device.

OLPC France launched in 2017 two deployments of Sugarizer on Android tablets in Saint-Ouen (25 Lenovo Tablets) and in Stains (10 Lenovo Tablets).

Finally I was mentor for SugarLabs during Google Summer of Code 2013 to 2017 and I was mentor for Google Code-In in 2015 and 2016.

Oversight Board

2017-08-27T19:53:47Z

Llaske:

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude>
{{TOCright}}

== Mission ==

{{:Oversight_Board/Mission}}

== The Oversight Board ==

The current oversight board members are:

* [[User:Walter|Walter Bender]] (slot expiring in [[Oversight_Board/2017-2019-candidates|2017]])
* [[User:Llaske|Lionel Laské]] (slot expiring in [[Oversight_Board/2017-2019-candidates|2017]])
* [[User:Sverma|Sameer Verma]] (slot expiring in [[Oversight_Board/2017-2019-candidates|2017]])
* [[User:Holt|Adam Holt]] (slot expiring in [[Oversight_Board/2017-2019-candidates|2017]])
* [[Samson Goddy]]
* [[User:Ignacio|Ignacio Rodríguez]]
* [[User:Laura_Vargas|Laura Vargas]]

===Contacts===

* slobs AT lists.sugarlabs.org - A private list for the Oversight Board members; all emails that do not ask to be private (or are not obviously intended to be private) will be forwarded to the publicly archived IAEP list.
* ombudsman AT sugarlabs.org - A neutral party with whom anyone (member or non-member) may consult privately. The ombudsman will report to the Oversight Board and the community each month that a consultation occurs. [[User:Bert|Bert Freudenberg]] is Ombudsman.

[[Category:Oversight board]]
[[Category:Contact]]

== Meetings ==

We meet on IRC at 19:00 UTC on the first Friday of each month (irc.freenode.net #sugar-meeting).

{{:Oversight_Board/Next_meeting}}

=== Previous Meetings ===

Minutes from previous meeting can be found at [[Oversight Board/Minutes]].
Logs can be found at [http://meeting.sugarlabs.org/sugar-meeting/meetings].

== Decisions ==

Board actions and decisions are found at [[Oversight Board/Decisions]].

== Additional roles within Sugar Labs==

The [[Oversight Board]] is responsible for appointing delegates with executive functions.
Any Sugar Labs [[Sugar Labs/Members|member]] can be appointed by the board. Existing
delegates include:

* <strike>[[Sugar Labs/Executive_Director|Executive Director]] (ED)</strike>
* [[Sugar Labs/Treasurer|Treasurer]]
* [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]]
* [[Sugar Labs/Ombudsman|Ombudsman]]

Coordinators are appointed independently by each SIG.

* [[Sugar Labs/Teams|Team Coordinators]]
* [[Sugar Labs/Projects|Project Managers]]
* [[Local Labs|Coordinators of Local Labs]]

The [[Oversight Board]] appoints one of its members as a liaison to each SIG.

== Former Board Members ==

We'd like to thank the follow former board members for their contributions:

* [[User:Marcopg|Marco Pesenti Gritti]] (2008–2009)
* [[User:Gdk|Greg Dekoenigsberg]] (2008–2009)
* [[User:Dfarning|David Farning]] (2008–2009)
* [[User:Tomeu|Tomeu Vizoso]] (2008-2010)
* [[User:Bernie|Bernie Innocenti]] (2008-2011)
* [[User:Alsroot|Aleksey Lim]] (2008-2012)
* [[User:Cjb|Chris Ball]] (2008-2012)
* [[User:SeanDaly|Sean Daly]] (2009–2010)
* [[User:Mchua|Mel Chua]] (2009-2011)
* [[User:Sebastian|Sebastian Silva]] (2010-2012)
* [[User:Gardito|Gerald Ardito]] (2013–2014)
* [[User:Francis|Daniel Francis]] (-2015)
* [[User:Cjl|Chris Leonard]] (-2015)
* [[User:Godiard|Gonzalo Odiard]] (-2015)
* [[Claudia Urrea]]
* [[User: Jmgarcia|José Miguel García]]
* Tony Anderson

== Subpages ==
{{Special:PrefixIndex/{{PAGENAME}}/}}

[[Category:Oversight board]]
[[Category:Governance]]

[[Category:Team]]

User:Llaske

2017-08-27T19:52:47Z

Llaske:

My name is Lionel Laské. I'm member of SugarLabs Oversight Board since 2015.

I'm also board member and co-founder in 2008 of the [http://olpc-france.org OLPC France grassroot].

OLPC France launch and maintain since 2009 a deployment of 200 XO-1/1.5 laptops in Madagascar on the [http://wiki.laptop.org/go/OLPC_Madagascar/Nosy_Komba Nosy Komba Island].

OLPC France launched also a small deployment of 50 XO-1.5 laptops in Saint-Denis (Paris suburb) between 2012 and 2014 and a deployment of 25 XO-4 laptops in Saint-Ouen (Paris suburb) in 2015-2016. Currently we hold a [http://sugarizer.org Sugarizer] deployment on 25 Android tablets in Saint-Ouen.

OLPC France promote One Laptop Per Child philosophy, Sugar and open source software and is also a reproducible association based on [http://movecommons.org Move Commons philosophy] so all our way of working is fully transparent and documented [http://olpc-france.org/wiki/index.php/Association].

OLPC France organized three SugarCamp in Paris in 2009, 2011 and 2014.

I'm the author of 8 Sugar activities [http://activities.sugarlabs.org/en/sugar/user/1454]. I'm also the author and the main contributor of [http://sugarizer.org Sugarizer], a way to deploy Sugar on any device.

OLPC France launched in 2017 two deployments of Sugarizer on Android tablets in Saint-Ouen (25 Lenovo Tablets) and in Stains (10 Lenovo Tablets).

Finally I was mentor for SugarLabs during Google Summer of Code 2013 to 2017 and I was mentor for Google Code-In in 2015 and 2016.

Summer of Code

2017-05-08T19:32:19Z

Llaske:

<noinclude>{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}</noinclude>

[http://google-opensource.blogspot.com/2016 '''Google Summer of Code'''] Sugar years: | [[Summer of Code/2009|2009]] | [[Summer of Code/2010|2010]] | [[Summer of Code/2011|2011]] | [[Summer of Code/2012|2012]] | [[Summer of Code/2013|2013]] | [[Summer of Code/2014|2014]] | [[Summer of Code/2015|2015]] | [[Summer of Code/2016|2016]] | [[Summer of Code/2017|2017]]

Sugar Labs has been accepted for '''Google Summer of Code (GSoC)''' 2017.

<center>
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Student !! Mentors !! Proposal Link !! Blog Link
|-
| width=25%; valign=top | Raphael Teyssandier
| width=25%; valign=top | Michaël Ohayon and Lionel Laské
| width=25%; valign=top | [https://summerofcode.withgoogle.com/dashboard/project/4957188710727680/overview/ Sugarizer Deployment Tool]
| width=25%; valign=top |
|-
| width=25%; valign=top | Tarun Kumar Singhal
| width=25%; valign=top | Lionel Laské and Michaël Ohayon
| width=25%; valign=top | [https://summerofcode.withgoogle.com/dashboard/project/6698013379526656/overview/ Sugarizer Server Dashboard]
| width=25%; valign=top | [https://github.com/tarunsinghal92/sugarizer-backend/wiki blog]
|-
| width=25%; valign=top | Jatin Dhankhar
| width=25%; valign=top | Sam Cantero and Tony Anderson
| width=25%; valign=top | [https://summerofcode.withgoogle.com/dashboard/project/4987332267606016/overview/ Maintaining ASLO]
| width=25%; valign=top | [https://jatindhankhar.in/blog blog]
|-
| width=25%; valign=top | Sanjay Kumar
| width=25%; valign=top | Tony Anderson and Ignacio Rodriguez
| width=25%; valign=top | [https://summerofcode.withgoogle.com/dashboard/project/5716653544308736/overview/ Mind Math Activity]
| width=25%; valign=top |
|-
| width=25%; valign=top | P. Seetarama Raju
| width=25%; valign=top | Samson Goddy and Walter Bender
| width=25%; valign=top | [https://summerofcode.withgoogle.com/dashboard/project/6106673893605376/overview/ Giving Sugar Labs Website a New Look]
| width=25%; valign=top |
|-
| width=25%; valign=top | Zeeshan Khan
| width=25%; valign=top | Ignacio Rodriguez and Walter Bender
| width=25%; valign=top | [https://summerofcode.withgoogle.com/dashboard/project/5325121714651136/overview/ Say no to Gtk2]
| width=25%; valign=top |
|-
| width=25%; valign=top | Rishabh Thaney
| width=25%; valign=top | Abhijit Patel and Walter Bender
| width=25%; valign=top | [https://summerofcode.withgoogle.com/dashboard/project/4860989563469824/overview/ Sugar on Raspberry Pi]
| width=25%; valign=top |
|-
| width=25%; valign=top | Tayba Wasim
| width=25%; valign=top | Devin Ulibarri, Cristina Del Puerto, Hrishi Patel
| width=25%; valign=top | [https://summerofcode.withgoogle.com/dashboard/project/4549541150851072/overview/ Timbre Widget for Music Blocks]
| width=25%; valign=top | [https://tabs16blog.wordpress.com/ blog]
|-
| width=25%; valign=top | Dinuka Tharangi
| width=25%; valign=top | Devin Ulibarri, Cristina Del Puerto, Hrishi Patel
| width=25%; valign=top | [https://summerofcode.withgoogle.com/dashboard/project/5761551930753024/overview/ User Manual for Music Blocks]
| width=25%; valign=top | [http://dinukaasblog.blogspot.com/ blog]
|-
| width=25%; valign=top | Prachi Agrawal
| width=25%; valign=top | Devin Ulibarri, Cristina Del Puerto, Hrishi Patel
| width=25%; valign=top | [https://outreachy.gnome.org/?q=view_projects&prg=8&p=1588 Music Blocks Improvements]
| width=25%; valign=top |
|}

</center>

'''Upcoming deadlines'''

Important GSoC 2017 Dates and Deadlines

;February 9, 2017: Organization Application Deadline
;February 27, 2017: Organizations Announced
;April 3, 2017: Student Application Deadline
;May 4, 2017: Student Projects Announced
;May 30, 2017: Coding Begins

See [https://summerofcode.withgoogle.com/how-it-works/#timeline GSoC Timeline] for more details from Google.

==Useful Links==

*'''[https://summerofcode.withgoogle.com/ Website]'''

*'''[https://developers.google.com/open-source/gsoc/faq FAQs]'''

We look forward to accepting your contributions to support the use of technology in education. Google Summer of Code (GSoC) is "a global program that offers student developers stipends to write code for various open source projects."[http://socghop.appspot.com/ 1]

== How to Participate ==

<center>
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! As a student !! As a mentor !! By contributing ideas
|-
| width=34%; valign=top | The most important job of all! Sugar Labs is looking forward to your contribution. To begin, we strongly recommend orienting yourself with the Sugar Labs code base. Be sure to visit http://bugs.sugarlabs.org/.

Please add a summary of your proposal to the wiki on a page called:

Summer_of_Code/2017/'''Proposal_name'''

where Proposal_name is the name of your proposal.

You can use this [[Summer_of_Code/Template|proposal template]]. (If you are applying to Outreachy, you may use your Outreachy proposal.) Be sure to explain what you want to do, why it is important, and evidence that you can do the work proposed.

Also, be sure to discuss the details of your proposal with members of the Sugar Labs community.

You also need to apply on the Google Summer of Code website.
| width=33%; valign=top| You can directly benefit a new software developer's coding competency and confidence levels while contributing to Sugar Labs and developing your own first-line management skills.
| width=33%; valign=top| Here you can look for more development ideas –
* [[Summer_of_Code/2017|Summer of Code 2017]] and
* [[Summer_of_Code/Resources#Project_Ideas|Resources]]
|}

</center>

== Sugar Labs GSoC Contact ==

Need help? Contact [[User:Walter| Walter Bender]]. He's responsible for,

* Maintaining this wiki page for the summer 2017 GSoC season (Feb 2017 - Sep 2017),
* Coordinating SL's application to the GSoC program as a mentorship organization,
* Recruiting mentors,
* Recruiting applicants,
* Selecting applicants,
* Supervising mentors, which largely entails making sure mid-term and end-of-summer reports are handed in on time,
* Interfacing with the Sugar Labs Oversight Board members to deal with collection and distribution of funds from Google

== Wiki Account ==

To request a Sugar Labs wiki account, please submit a preferred user name and an email address to:
systems at lists dot sugarlabs dot org.

<noinclude>

==Subpages==
[[Category:GSoC]]
</noinclude>

2017 Goals

2017-04-13T13:49:49Z

Llaske: Sugarizer update

Sugar Labs goals for 2017.

''[This is a draft based on proposals made on the [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17778.html IAEP email thread] started on April 9th.]''

''[See [https://docs.google.com/document/d/1fvR8Qr3CVI_n8ccho0dEW81hvAhgoWmJJl6ACgDvBNY/edit Sugar Labs Goals] for another shared editing document started in that thread.]''

==Mission==

''[Our Mission is the responsibility of the Board; any changes to the Mission must be passed by the Board.]''

Sugar Labs® is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.



==Vision==

''[To be defined. See also [[Vision proposal 2016]].]''

{{TOCright|show=0}}

==Template: Goals, Objectives & Actions==

''[A template to copy and paste when adding a new goal.]''

'''Goal: X''' '': [a broad statement about what the program or initiative intends to accomplish. It is also the intended long-term outcome.]''
* Objective: ''[expected achievements that are well-defined, specific, measurable, and derived from the goal(s).]''
* Action: ''[efforts conducted to achieve the objectives.]''
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}

==Goals, Objectives & Actions==

''[Can someone take what is listed on [[2016 Goals]] and plug them into the goals, objectives and actions on this page for the year?]''

'''Goal: Continue to develop, distribute, and maintain Sugar as a free/libre learning platform on GNU/Linux platforms and to work with the distributors of those platforms to promote Sugar for education.'''

* Objective:
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Work with Trisquel||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education
||??|| Needs a volunteer|| ??|| ??
|-
|Workshop with Raspberry Pi Foundation||Initiate contact with Raspberry Pi Education Coordinator to cohost workshops showcasing free/libre tools for education||??|| Needs a volunteer|| ??|| ??
|-
|Port Sugar to Raspian||Port Sugar to Raspian||??|| Needs a volunteer|| ??|| ??
|-
|Write an article for the Free Software Foundation||Write a guest blog post about the Sugar desktop pointing to ways volunteers can help with development||??|| Needs a volunteer|| ??|| ??
|-
|Participate in Mini-Maker Faires||Host a booth andor workshop at several Mini-Maker Faires||??|| Needs a volunteer|| ??|| ??
|-
|}
* Objective:
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}

'''Goal: Develop, distribute, and maintain a variety of Sugarizer Apps and installations for as many devices as possible.'''

* Objective: Enhance user experience for Sugarizer Apps
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Login experience ||Add a full login experience for Sugarizer users connected to a Server || ?|| ?|| ?|| ?
|-
|Add Fototoon activity||Port Fototoon activity to Sugarizer || ?|| ?|| ?|| ?
|-
|Package as Flatpak||Make Sugarizer available for GNU/Linux operating systems as a Flatpak download|| Downloads|| ?|| [https://github.com/manuq/sugarizer-electron 12th April 2017]||Example
|-
|Package as MacOS||Make Sugarizer available on MacOS App Store||Store|| ?|| ?|| ?
|-
|}
* Objective: Create a full package to deploy easily Sugarizer in schools
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Create a dashboard tool|| Create a Dashboard tools to allow teachers/admin to administrate a deployment. See [https://wiki.sugarlabs.org/go/Summer_of_Code/2017#sugdash] || GSoC student || GSoC student || ?|| ?
|-
|Create a deployment tool|| Create a deployment tools for Sugarizer OS to easily deploy/manage devices. See [https://wiki.sugarlabs.org/go/Summer_of_Code/2017#sugmdm] || GSoC student || GSoC student || ?|| ?
|-
|}
* Objective: Actively recruit and maintain developers for Sugarizer
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Make the platform easier for developers to contribute||Example|| Examples|| Example|| Example||Example
|-
|}

'''Goal: Maintain and promote various related stand-alone projects that supports free/libre and Constructionist Learning'''

* Objective: Increase awareness of learners and learning communities for Music Blocks and Turtle Art
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}
* Objective: Maintain development and documentation of Music Blocks and Turtle Art
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Quarterly updates/pruning on the documentation for Music Blocks and Turtle Art ||Example|| Examples|| Example|| Example||Example
|-
|}

'''Goal: Develop, distribute and maintain a series of school server versions for use where reliable internet service is not possible.'''

* Objective:
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}
* Objective:
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}

'''Goal: To sponsor any motivated, active individuals in need to continue doing the best they can to support our mission.'''

* Objective: Support individuals at the high school and college level with financial incentives, more importantly mentorship.
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Participate as an organization in Google Summer of Code||Example|| Examples|| Example|| Example||Example
|-
|Participate as an organization in Google Code-in||Example|| Examples|| Example|| Example||Example
|-
|}
* Objective: Provide funding to individuals to create and/or maintain ongoing projects in their given communities.
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}

'''Goal: Sugar and related software must be developed with “internationalization” (i18n) capabilities built in from the onset, thereby allowing translation of the user interface into many languages by our diverse “localization” (L10n) community. Lack of i18n means an inability to share.'''

* Objective:
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}
* Objective:
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}

'''Goal: Secure and distribute our servers and systems.'''

* Objective:
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}
* Objective:
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}

'''Goal: To maintain domains and trademarks.'''

* Objective:
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}
* Objective:
::::{| class="wikitable"
|-
!Action Item!! Description !! Resources !! Committee/Volunteer !! Date Started !! Date Completed
|-
|Examples||Example|| Examples|| Example|| Example||Example
|-
|}

==Context==

''[A current and historical context to guide the goals, objectives and actions listed above. This text is modified from what Walter Bender posted on sugar-devel@ in response to request.]''

===What is Sugar Labs?===

Sugar Labs creates, distributes, and maintains learning software for children. Our approach to learning is grounded in Constructionism, a pedagogy developed by Seymour Papert and his colleagues in the 1960s and 70s at MIT. Papert pioneered the use of the computer by children to help engage them in the “construction of knowledge.” His long-time colleague Cynthia Solomon expanded up his ideas by introducing the concept of engaging children in debugging as a pathway into problem-solving. Their 1971 paper, “Twenty things to do with a computer”, is arguably the genesis of contemporary movements such as the Maker Movement and Hour of Code.

At the core of Constructionism is “learning through doing.” If you want more learning, you want more doing. At Sugar Labs we provide tools to promote doing. (We focus almost exclusively on tools, not instructional materials.) However, we go beyond “doing” by incorporating critical dialog and reflection into the Sugar learning environment, through mechanisms for collaboration, journaling, and portfolio.

Sugar Labs is a spinoff of the One Laptop per Child (OLPC) project and consequently it has inherited many of its goals from that project. The goal of OLPC is to bring the ideas of Constructionism to scale in order to reach more children. A particular focus is on children in the developing world. In order to meet that goal, Sugar, which was originally developed for OLPC, was by necessity a small-footprint solution that required few resources in terms of CPU, memory, storage, or network connectivity. The major change on focus from the OLPC project is that Sugar Labs strives to make the Sugar desktop available to multiple platforms, not just the OLPC hardware.

===Who develops Sugar?===

Sugar Labs is a 100% volunteer effort (although we do occasionally raise money for paid student internships). Sugar development and maintenance is incumbent upon volunteers and hence we strive to provide as much control as possible to our community members, including our end-users. (In fact, one of our assertions is that by enabling our users to participate in the development of the tools that they use will lead to deeper engagement in their own learning.) Towards these ends, we chose the GPL as our primary license. It has been said of the GPL that it “restricts my right [as a developer] to restrict yours [as a user and potential developer]”, which seems ideal for a project that wants to engage a broad and diverse set of learners. But at Sugar Labs we go beyond the usual goals of FOSS: a license to make changes to the code is not enough to ensure that users make changes. We also strive to provide the means to make changes. Our success in this goal is best reflected in the number of patches we receive from our community. (We achieve this goal through providing access to source code and development tools within Sugar itself. We also actively participate in workshops and internship programs such as Google Summer of Code, Outreaching, and Google Code-In.)

===Who uses Sugar?===

Ultimately, our goal is to reach learners (and educators) with powerful tools and engage them in Constructionist learning. Currently we reach them in many ways: the majority of our users get the Sugar desktop preinstalled on OLPC hardware. We have a more modest set of users who get Sugar packaged in Fedora, Trisquel, Debian, Ubuntu, or other GNU/Linux platforms. Some users get Sugar on Live Media (i.e., Sugar on a Stick). Recently Sugarizer, a repackaging of some of the core Sugar ideas for the browser, has been finding its way to some users. There are also a number of Sugar activities that are popular outside of the context Sugar itself, for example, Turtle Blocks, which has wide-spread use in India. Harder to measure is the extent to which Sugar has influenced other providers of “educational” software. If the Sugar pedagogy is incorporated by others, that advances our goal.

===Who supports Sugar?===

When we first created Sugar Labs, we envisioned “Local Labs”—hence the name “Sugar Labs”, plural—that would provide local support in terms of local-language support, training, curriculum development, and customizations. This model has not ever gained the scale and depth envisioned (we can debate the reasons why), although there are still some active local communities (e.g., Educa Paraguay) that continue to work closely with the broader community. There are also individual volunteers, such as Tony Anderson and T.K. Kang, who help support individual schools in Rwanda, Malaysia, et al. An open question is how do we support our users over the long term?

===What is next for Sugar?===

We face several challenges at Sugar Labs. With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we attract more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment and that our users, potential users, and imitators are learning about and learning from Sugar. Some of this is a matter of marketing; some of this is a matter of staying focused on our core pedagogy; some of this a matter of finding strategic partners with whom we can work.

We have several near-term opportunities that we should leverage:
* Raspian: The Raspberry Pi 3 is more than adequate to run Sugar—the experience rivals or exceeds that of the OLPC XO-4 hardware, though not the OLPC NL3 hardware. While Raspberry Pi is not the only platform we should be targeting, it does have broad penetration into the Maker community, which shares a synergy with our emphasis on “doing”. It is low-hanging fruit. With a little polish we could have an image available for download from the Raspberry Pi website.
* Trisquel: We have the potential for better leveraging the Free Software Foundation as a vehicle for promoting Sugar. Their distro of choice is Trisquel and the maintainer does a great job of keep the Sugar packages up to date.
* Sugarizer: The advantage of Sugarizer is that it has the potential of reaching orders of magnitude more users since it is web-based and runs in Android and iOS. There is some work to be done to make the experience palatable on small screens and the current development environment is—at least my opinion—not scalable or maintainable. The former is a formidable problem. The latter quite easy to address.
* Stand-alone projects such as Music Blocks have merit as long as they maintain both a degree of connection with Sugar and promote the values of the community. It is not certain that these projects will lead users towards Sugar, but they do promote FOSS and Constructionist principles. And they have attracted new developers to the Sugar community.
* School-server: The combination of the School Server and Sugar desktop is a technical solution to problems facing small and remote communities. We should continue to support and promote this combination.

===Specific actions===
After last year’s Libre Planet conference, several community members discussed a marketing strategy for Sugar. We thought that if we could reach influencers, we might be able to greatly amplify our efforts. There are several prominent bloggers and pundits in the education arena who are widely read and who might be receptive to what we are doing. One significant challenge is that GNU/Linux remains on the far periphery of the Ed Tech world. Although the “love affair” with all things Apple seems to be over, the new elephant in the room—Chromebooks and Google Docs—is equally difficult to co-exist with. Personally, I see the most potential synergy with the Maker movement, which is building up momentum in extra-curricular programs, where FOSS and GNU-Linux are welcome (hence my earlier focus on RPi). (There are even some schools that are building their entire curriculum around PBL.) We can and should develop and run some workshops that can introduce Sugar within the context of the Maker movement. (Toward that end, I have been working with some teachers on how to leverage, for example, Turtle Blocks for 3D printing.) It is very much a tool-oriented community with little overall discussion of architectural frameworks, so we have some work to do. But there is lots of low-hanging fruit there.

Summer of Code/2017

2017-03-18T10:35:27Z

Llaske: /* Project Ideas */

== Project Ideas ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title
!Mentor
!Project

|-
| valign=top width="15%" style="background:#e3e4e5;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
| align=left valign=top |
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details. See [[Translation Team]] for framework description.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |New Back-end Server for Turtle Blocks and Music Blocks [[File:Git logo.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Vikram Ahuja Ignacio Rodriguez
| align=left valign=top |
;Brief explanation: Last year we sponsored [http://vikramahujagsoc.blogspot.com/ an exploration] of using a git-like back end for projects so that they could be cloned, forked, etc. This summer we would like to implement and deploy this new approach.
;Expected results: Deployment of "git" back end.
;Knowledge prerequisites: Knowledge of Git, JavaScript, server-side skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/issues Music Blocks issues].
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory

|-
| valign=top width="15%" style="background:#e3e4e5;" |Giving Sugar Labs Website a New Look
| valign=top width="15%" | Ignacio Rodriguez Samson Goddy Dave Crossland Tymon Radzik
| align=left valign=top |
;Brief explanation: Sugar Labs would like a new look for its [https://github.com/sugarlabs/www-sugarlabs homepage], with the goals of making it more attractive and easier to explore (See link to get more information concerning the [https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md proposed homepage]).
;Expected results: Deployment of a new website for Sugar Labs
;Knowledge prerequisites: JavaScript, HTML, CSS, Ruby, JQuery, jeckyl, and/or django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Maintenance of activities.sugarlabs.org (ASLO)
| valign=top width="15%" | (volunteers?)
| align=left valign=top |
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded. Some maintenance tasks are needed. Sugar uses activities.sugarlabs.org in Software Update in My Settings, and has a link to it in the Browse default page.
;Expected results: Fix downloads by non-Sugar browsers; old versions are offered. Fix downloads by new versions of Sugar; old versions are offered. Make activity maintainer take-over easier; not easy at the moment. Adopt the new look from the new [http://www.sugarlabs.org/ sugarlabs.org] site; theme now is quite old. Show new activity.info metadata such as source repository. Other problems listed in [http://bugs.sugarlabs.org bugs.sugarlabs.org] against component [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=activities.sugarlabs.org&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&order=priority activities.sugarlabs.org]. Semi-automate common maintenance tasks; like adding a new Sugar version. Document future maintenance on the Wiki.
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git. See [https://github.com/sugarlabs/aslo source code].

|-
| valign=top width="15%" style="background:#e3e4e5;" |School Management Backend
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Sugar is a desktop and a collection of apps. It has great internal features for collaboration and journaling. But it doesn't have any mechanism for managing courses/curriculum/administrative functions commonly found in "school management systems". It could be possible to overlay on top of Sugar web-services such a toolkit.
;Expected results: a framework, a core implementation, and documentation for expanding the implementation.
;Knowledge prerequisites: Python, django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Timbre Widget for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Ayush Kumar designed a widget for designing voices for Music Blocks (See [http://kuckuck.treehouse.su:5000/task/5948636577923072/instance/5685003230904320/]). This project would be to implement the design.
;Expected results: a working widget for Music Blocks for manipulating Timbre.
;Knowledge prerequisites: JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |{{anchor|sugdash}}Sugarizer Server Dashboard [[File:Dashboard server.png|90px|thumb|center]]
| valign=top width="15%" | Lionel Laské Michaël Ohayon
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on Sugar Web library, which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates activities written for Sugar in Sugar Web. The goal of this specific project is to create the "Sugarizer Server Dashboard". This feature will require an enhancement of the existing Sugarizer Server API specifically to integrate a real authentication mechanism.

;Expected results: Sugarizer Server Dashboard is a web admin console for Sugarizer Server. The Dashboard will allow to manage and analyze all activity on a Sugarizer Server. Dashboard features will include:
* Users: how many users has been registered on the server, how many users currently connected, top users on the server, last users connection, create/edit/remove an user.
* Journal: how many Journals and how many entries in Journal on the server, last Journal and last entries, size of Journals, top Journals, edit a journal (see/update/remove) entries.
* Application: how many applications are available on the server, change application visibility from Client, update order and way to appear in favorite view.
* Graphic and request: display graphics and report on previous data.

;Knowledge prerequisites: HTML5/JavaScript, bootstrap, node.js, MongoDB
;How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then install Sugarizer server using instructions [https://github.com/llaske/sugarizer/blob/master/README.md#server here], finally explore the [http://sugarizer.org/apidoc/ Sugarizer Server API] and think about way to implement dashboard features with existing API.

|-
| valign=top width="15%" style="background:#e3e4e5;" |{{anchor|sugmdm}}Sugarizer Deployement and Management Tool for Android [[File:Sugarizermdmtool.png|90px|thumb|center]]
| valign=top width="15%" | Michaël Ohayon Lionel Laské
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies. Sugarizer can be deployed on many devices including Android phones and tablets. The goal of this specific project is to create the "Sugarizer Deployment and Management Tool for Android".

;Expected results: Sugarizer Server Deployment and Management Tool is a GUI Tool working on GNU/Linux, Mac and Windows to deploy and configure Android devices using ADB (Android Debug Bridge).
* Inventory : Collect and store devices data like serial number, os version, device name, installed applications, current Android launcher and Sugarizer availability.
* Application Manager : Install or remove applications using APK files.
* File Manager : Add / Remove files
* Input Manager : Click / Touch coordinates on the screen, launch applications to perform automations.
* Scenario Writer : Allow '''non developpers''' to create sequences to perform all the steps previously defined.

;Knowledge prerequisites: Java and JavaFX / Kotlin and TornadoFX
;How to start: Create a Java or Kotlin project using Intellij and display a window using JavaFX or TornadoFX. Then add https://github.com/vidstige/jadb and display connected android devices in the window.

|-
| valign=top width="15%" style="background:#e3e4e5;" |User Manual for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need something a bit more polished as a user manual.
;Expected results: A website and PDF document that can be bound.
;Knowledge prerequisites: Knowledge of music theory, writing skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Just say no to GTK2
| valign=top width="15%" | Ignacio Rodriguez Sam Parkinson
Abhijit Patel
| align=left valign=top |
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.
;Expected results: New versions of Turtle, Speak, Chat, Record, and a dozen others
;Knowledge prerequisites: Knowledge of GTK, GST, and Python
|-
| valign=top width="15%" style="background:#e3e4e5;" |Develop Activity AKA Pippy JS, Taller del Artesano 2
| valign=top width="15%" |Sebastian Silva
| align=left valign=top |
;Brief explanation: We don't have a Javascript IDE for writing activities. This is a proposal to collaborate in making one. It would have templates for writing Javascript and Python.
;Expected results: New activity capable of making new activities, runnable in Web and Sugarizer
;Knowledge prerequisites: Python, Javascript, HTML5, CSS

|-
| valign=top width="15%" style="background:#e3e4e5;" |Debian SugarBlend
A.K.A: Harmonic Distribution, Deployment Platform
| valign=top width="15%" |Sebastian Silva Jonas Smedegaard
| align=left valign=top |
;Brief explanation: Debian is a base for many educational derivative distribution. We would like to make a SugarBlend that is a good base for local integrators.
;Expected results: Debian SugarBlend of upcoming Debian 9 (Stretch)
;Knowledge prerequisites: Debian packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Sugar on Raspberry Pi
| valign=top width="15%" |Walter Bender
| align=left valign=top |
;Brief explanation: Raspberry Pi is a popular tool with the Maker Movement. Sugar runs quite well on RPi3, but it is in need of some love.
;Expected results: Packaged Sugar for RPi suitable for inclusion on the [https://www.raspberrypi.org/downloads/ RPi download page].
;Knowledge prerequisites: Debian and/or Fedora packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks for Mobile [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Music Blocks was written for a browser, not mobile. It would be great to have a version native to mobile.
;Expected results: Working version on Android/and/or iOS. Some UI adjustments will be necessary.
;Knowledge prerequisites: Knowledge of JavaScript/Codrova/React and/or Swift.

|

|-
| valign=top width="15%" style="background:#e3e4e5;" |Collab Rethink 
| valign=top width="15%" | Abhijit Patel Walter Bender
| align=left valign=top |
;Brief explanation: Sugar collaboration uses a deprecated library, python-telepathy, which we no longer wish to maintain. We need to upgrade Sugar collab using something better
;Expected results: Working version of revised collab system.
* Refactored presenceservice
* Common Collabwrapper module for all sugar activities.

;Knowledge prerequisites: python, prior knowledge of networking. knowledge of telepathy might be useful.
|
}

Summer of Code/2017

2017-03-18T10:33:38Z

Llaske: /* Project Ideas */

== Project Ideas ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title
!Mentor
!Project

|-
| valign=top width="15%" style="background:#e3e4e5;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
| align=left valign=top |
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details. See [[Translation Team]] for framework description.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |New Back-end Server for Turtle Blocks and Music Blocks [[File:Git logo.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Vikram Ahuja Ignacio Rodriguez
| align=left valign=top |
;Brief explanation: Last year we sponsored [http://vikramahujagsoc.blogspot.com/ an exploration] of using a git-like back end for projects so that they could be cloned, forked, etc. This summer we would like to implement and deploy this new approach.
;Expected results: Deployment of "git" back end.
;Knowledge prerequisites: Knowledge of Git, JavaScript, server-side skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/issues Music Blocks issues].
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory

|-
| valign=top width="15%" style="background:#e3e4e5;" |Giving Sugar Labs Website a New Look
| valign=top width="15%" | Ignacio Rodriguez Samson Goddy Dave Crossland Tymon Radzik
| align=left valign=top |
;Brief explanation: Sugar Labs would like a new look for its [https://github.com/sugarlabs/www-sugarlabs homepage], with the goals of making it more attractive and easier to explore (See link to get more information concerning the [https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md proposed homepage]).
;Expected results: Deployment of a new website for Sugar Labs
;Knowledge prerequisites: JavaScript, HTML, CSS, Ruby, JQuery, jeckyl, and/or django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Maintenance of activities.sugarlabs.org (ASLO)
| valign=top width="15%" | (volunteers?)
| align=left valign=top |
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded. Some maintenance tasks are needed. Sugar uses activities.sugarlabs.org in Software Update in My Settings, and has a link to it in the Browse default page.
;Expected results: Fix downloads by non-Sugar browsers; old versions are offered. Fix downloads by new versions of Sugar; old versions are offered. Make activity maintainer take-over easier; not easy at the moment. Adopt the new look from the new [http://www.sugarlabs.org/ sugarlabs.org] site; theme now is quite old. Show new activity.info metadata such as source repository. Other problems listed in [http://bugs.sugarlabs.org bugs.sugarlabs.org] against component [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=activities.sugarlabs.org&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&order=priority activities.sugarlabs.org]. Semi-automate common maintenance tasks; like adding a new Sugar version. Document future maintenance on the Wiki.
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git. See [https://github.com/sugarlabs/aslo source code].

|-
| valign=top width="15%" style="background:#e3e4e5;" |School Management Backend
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Sugar is a desktop and a collection of apps. It has great internal features for collaboration and journaling. But it doesn't have any mechanism for managing courses/curriculum/administrative functions commonly found in "school management systems". It could be possible to overlay on top of Sugar web-services such a toolkit.
;Expected results: a framework, a core implementation, and documentation for expanding the implementation.
;Knowledge prerequisites: Python, django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Timbre Widget for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Ayush Kumar designed a widget for designing voices for Music Blocks (See [http://kuckuck.treehouse.su:5000/task/5948636577923072/instance/5685003230904320/]). This project would be to implement the design.
;Expected results: a working widget for Music Blocks for manipulating Timbre.
;Knowledge prerequisites: JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |Sugarizer Server Dashboard [[File:Dashboard server.png|90px|thumb|center]]
| valign=top width="15%" | Lionel Laské Michaël Ohayon
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on Sugar Web library, which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates activities written for Sugar in Sugar Web. The goal of this specific project is to create the "Sugarizer Server Dashboard". This feature will require an enhancement of the existing Sugarizer Server API specifically to integrate a real authentication mechanism.

;Expected results: Sugarizer Server Dashboard is a web admin console for Sugarizer Server. The Dashboard will allow to manage and analyze all activity on a Sugarizer Server. Dashboard features will include:
* Users: how many users has been registered on the server, how many users currently connected, top users on the server, last users connection, create/edit/remove an user.
* Journal: how many Journals and how many entries in Journal on the server, last Journal and last entries, size of Journals, top Journals, edit a journal (see/update/remove) entries.
* Application: how many applications are available on the server, change application visibility from Client, update order and way to appear in favorite view.
* Graphic and request: display graphics and report on previous data.

;Knowledge prerequisites: HTML5/JavaScript, bootstrap, node.js, MongoDB
;How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then install Sugarizer server using instructions [https://github.com/llaske/sugarizer/blob/master/README.md#server here], finally explore the [http://sugarizer.org/apidoc/ Sugarizer Server API] and think about way to implement dashboard features with existing API.

|-
| valign=top width="15%" style="background:#e3e4e5;" |{{anchor|sugmdm}}Sugarizer Deployement and Management Tool for Android [[File:Sugarizermdmtool.png|90px|thumb|center]]
| valign=top width="15%" | Michaël Ohayon Lionel Laské
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies. Sugarizer can be deployed on many devices including Android phones and tablets. The goal of this specific project is to create the "Sugarizer Deployment and Management Tool for Android".

;Expected results: Sugarizer Server Deployment and Management Tool is a GUI Tool working on GNU/Linux, Mac and Windows to deploy and configure Android devices using ADB (Android Debug Bridge).
* Inventory : Collect and store devices data like serial number, os version, device name, installed applications, current Android launcher and Sugarizer availability.
* Application Manager : Install or remove applications using APK files.
* File Manager : Add / Remove files
* Input Manager : Click / Touch coordinates on the screen, launch applications to perform automations.
* Scenario Writer : Allow '''non developpers''' to create sequences to perform all the steps previously defined.

;Knowledge prerequisites: Java and JavaFX / Kotlin and TornadoFX
;How to start: Create a Java or Kotlin project using Intellij and display a window using JavaFX or TornadoFX. Then add https://github.com/vidstige/jadb and display connected android devices in the window.

|-
| valign=top width="15%" style="background:#e3e4e5;" |User Manual for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need something a bit more polished as a user manual.
;Expected results: A website and PDF document that can be bound.
;Knowledge prerequisites: Knowledge of music theory, writing skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Just say no to GTK2
| valign=top width="15%" | Ignacio Rodriguez Sam Parkinson
Abhijit Patel
| align=left valign=top |
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.
;Expected results: New versions of Turtle, Speak, Chat, Record, and a dozen others
;Knowledge prerequisites: Knowledge of GTK, GST, and Python
|-
| valign=top width="15%" style="background:#e3e4e5;" |Develop Activity AKA Pippy JS, Taller del Artesano 2
| valign=top width="15%" |Sebastian Silva
| align=left valign=top |
;Brief explanation: We don't have a Javascript IDE for writing activities. This is a proposal to collaborate in making one. It would have templates for writing Javascript and Python.
;Expected results: New activity capable of making new activities, runnable in Web and Sugarizer
;Knowledge prerequisites: Python, Javascript, HTML5, CSS

|-
| valign=top width="15%" style="background:#e3e4e5;" |Debian SugarBlend
A.K.A: Harmonic Distribution, Deployment Platform
| valign=top width="15%" |Sebastian Silva Jonas Smedegaard
| align=left valign=top |
;Brief explanation: Debian is a base for many educational derivative distribution. We would like to make a SugarBlend that is a good base for local integrators.
;Expected results: Debian SugarBlend of upcoming Debian 9 (Stretch)
;Knowledge prerequisites: Debian packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Sugar on Raspberry Pi
| valign=top width="15%" |Walter Bender
| align=left valign=top |
;Brief explanation: Raspberry Pi is a popular tool with the Maker Movement. Sugar runs quite well on RPi3, but it is in need of some love.
;Expected results: Packaged Sugar for RPi suitable for inclusion on the [https://www.raspberrypi.org/downloads/ RPi download page].
;Knowledge prerequisites: Debian and/or Fedora packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks for Mobile [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Music Blocks was written for a browser, not mobile. It would be great to have a version native to mobile.
;Expected results: Working version on Android/and/or iOS. Some UI adjustments will be necessary.
;Knowledge prerequisites: Knowledge of JavaScript/Codrova/React and/or Swift.

|

|-
| valign=top width="15%" style="background:#e3e4e5;" |Collab Rethink 
| valign=top width="15%" | Abhijit Patel Walter Bender
| align=left valign=top |
;Brief explanation: Sugar collaboration uses a deprecated library, python-telepathy, which we no longer wish to maintain. We need to upgrade Sugar collab using something better
;Expected results: Working version of revised collab system.
* Refactored presenceservice
* Common Collabwrapper module for all sugar activities.

;Knowledge prerequisites: python, prior knowledge of networking. knowledge of telepathy might be useful.
|
}

Summer of Code/2017

2017-03-18T10:29:18Z

Llaske: /* Project Ideas */

== Project Ideas ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title
!Mentor
!Project

|-
| valign=top width="15%" style="background:#e3e4e5;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
| align=left valign=top |
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details. See [[Translation Team]] for framework description.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |New Back-end Server for Turtle Blocks and Music Blocks [[File:Git logo.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Vikram Ahuja Ignacio Rodriguez
| align=left valign=top |
;Brief explanation: Last year we sponsored [http://vikramahujagsoc.blogspot.com/ an exploration] of using a git-like back end for projects so that they could be cloned, forked, etc. This summer we would like to implement and deploy this new approach.
;Expected results: Deployment of "git" back end.
;Knowledge prerequisites: Knowledge of Git, JavaScript, server-side skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/issues Music Blocks issues].
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory

|-
| valign=top width="15%" style="background:#e3e4e5;" |Giving Sugar Labs Website a New Look
| valign=top width="15%" | Ignacio Rodriguez Samson Goddy Dave Crossland Tymon Radzik
| align=left valign=top |
;Brief explanation: Sugar Labs would like a new look for its [https://github.com/sugarlabs/www-sugarlabs homepage], with the goals of making it more attractive and easier to explore (See link to get more information concerning the [https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md proposed homepage]).
;Expected results: Deployment of a new website for Sugar Labs
;Knowledge prerequisites: JavaScript, HTML, CSS, Ruby, JQuery, jeckyl, and/or django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Maintenance of activities.sugarlabs.org (ASLO)
| valign=top width="15%" | (volunteers?)
| align=left valign=top |
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded. Some maintenance tasks are needed. Sugar uses activities.sugarlabs.org in Software Update in My Settings, and has a link to it in the Browse default page.
;Expected results: Fix downloads by non-Sugar browsers; old versions are offered. Fix downloads by new versions of Sugar; old versions are offered. Make activity maintainer take-over easier; not easy at the moment. Adopt the new look from the new [http://www.sugarlabs.org/ sugarlabs.org] site; theme now is quite old. Show new activity.info metadata such as source repository. Other problems listed in [http://bugs.sugarlabs.org bugs.sugarlabs.org] against component [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=activities.sugarlabs.org&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&order=priority activities.sugarlabs.org]. Semi-automate common maintenance tasks; like adding a new Sugar version. Document future maintenance on the Wiki.
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git. See [https://github.com/sugarlabs/aslo source code].

|-
| valign=top width="15%" style="background:#e3e4e5;" |School Management Backend
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Sugar is a desktop and a collection of apps. It has great internal features for collaboration and journaling. But it doesn't have any mechanism for managing courses/curriculum/administrative functions commonly found in "school management systems". It could be possible to overlay on top of Sugar web-services such a toolkit.
;Expected results: a framework, a core implementation, and documentation for expanding the implementation.
;Knowledge prerequisites: Python, django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Timbre Widget for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Ayush Kumar designed a widget for designing voices for Music Blocks (See [http://kuckuck.treehouse.su:5000/task/5948636577923072/instance/5685003230904320/]). This project would be to implement the design.
;Expected results: a working widget for Music Blocks for manipulating Timbre.
;Knowledge prerequisites: JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |Sugarizer Server Dashboard [[File:Dashboard server.png|90px|thumb|center]]
| valign=top width="15%" | Lionel Laské Michaël Ohayon
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on Sugar Web library, which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates activities written for Sugar in Sugar Web. The goal of this specific project is to create the "Sugarizer Server Dashboard". This feature will require an enhancement of the existing Sugarizer Server API specifically to integrate a real authentication mechanism.

;Expected results: Sugarizer Server Dashboard is a web admin console for Sugarizer Server. The Dashboard will allow to manage and analyze all activity on a Sugarizer Server. Dashboard features will include:
* Users: how many users has been registered on the server, how many users currently connected, top users on the server, last users connection, create/edit/remove an user.
* Journal: how many Journals and how many entries in Journal on the server, last Journal and last entries, size of Journals, top Journals, edit a journal (see/update/remove) entries.
* Application: how many applications are available on the server, change application visibility from Client, update order and way to appear in favorite view.
* Graphic and request: display graphics and report on previous data.

;Knowledge prerequisites: HTML5/JavaScript, bootstrap, node.js, MongoDB
;How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then install Sugarizer server using instructions [https://github.com/llaske/sugarizer/blob/master/README.md#server here], finally explore the [http://sugarizer.org/apidoc/ Sugarizer Server API] and think about way to implement dashboard features with existing API.

|-
| valign=top width="15%" style="background:#e3e4e5;" |Sugarizer Deployement and Management Tool for Android [[File:Sugarizermdmtool.png|90px|thumb|center]]
| valign=top width="15%" | Michaël Ohayon Lionel Laské
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies. Sugarizer can be deployed on many devices including Android phones and tablets. The goal of this specific project is to create the "Sugarizer Deployment and Management Tool for Android".

;Expected results: Sugarizer Server Deployment and Management Tool is a GUI Tool working on GNU/Linux, Mac and Windows to deploy and configure Android devices using ADB (Android Debug Bridge).
* Inventory : Collect and store devices data like serial number, os version, device name, installed applications, current Android launcher and Sugarizer availability.
* Application Manager : Install or remove applications using APK files.
* File Manager : Add / Remove files
* Input Manager : Click / Touch coordinates on the screen, launch applications to perform automations.
* Scenario Writer : Allow '''non developpers''' to create sequences to perform all the steps previously defined.

;Knowledge prerequisites: Java and JavaFX / Kotlin and TornadoFX
;How to start: Create a Java or Kotlin project using Intellij and display a window using JavaFX or TornadoFX. Then add https://github.com/vidstige/jadb and display connected android devices in the window.

|-
| valign=top width="15%" style="background:#e3e4e5;" |User Manual for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need something a bit more polished as a user manual.
;Expected results: A website and PDF document that can be bound.
;Knowledge prerequisites: Knowledge of music theory, writing skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Just say no to GTK2
| valign=top width="15%" | Ignacio Rodriguez Sam Parkinson
Abhijit Patel
| align=left valign=top |
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.
;Expected results: New versions of Turtle, Speak, Chat, Record, and a dozen others
;Knowledge prerequisites: Knowledge of GTK, GST, and Python
|-
| valign=top width="15%" style="background:#e3e4e5;" |Develop Activity AKA Pippy JS, Taller del Artesano 2
| valign=top width="15%" |Sebastian Silva
| align=left valign=top |
;Brief explanation: We don't have a Javascript IDE for writing activities. This is a proposal to collaborate in making one. It would have templates for writing Javascript and Python.
;Expected results: New activity capable of making new activities, runnable in Web and Sugarizer
;Knowledge prerequisites: Python, Javascript, HTML5, CSS

|-
| valign=top width="15%" style="background:#e3e4e5;" |Debian SugarBlend
A.K.A: Harmonic Distribution, Deployment Platform
| valign=top width="15%" |Sebastian Silva Jonas Smedegaard
| align=left valign=top |
;Brief explanation: Debian is a base for many educational derivative distribution. We would like to make a SugarBlend that is a good base for local integrators.
;Expected results: Debian SugarBlend of upcoming Debian 9 (Stretch)
;Knowledge prerequisites: Debian packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Sugar on Raspberry Pi
| valign=top width="15%" |Walter Bender
| align=left valign=top |
;Brief explanation: Raspberry Pi is a popular tool with the Maker Movement. Sugar runs quite well on RPi3, but it is in need of some love.
;Expected results: Packaged Sugar for RPi suitable for inclusion on the [https://www.raspberrypi.org/downloads/ RPi download page].
;Knowledge prerequisites: Debian and/or Fedora packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks for Mobile [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri
| align=left valign=top |
;Brief explanation: Music Blocks was written for a browser, not mobile. It would be great to have a version native to mobile.
;Expected results: Working version on Android/and/or iOS. Some UI adjustments will be necessary.
;Knowledge prerequisites: Knowledge of JavaScript/Codrova/React and/or Swift.

|

|-
| valign=top width="15%" style="background:#e3e4e5;" |Collab Rethink 
| valign=top width="15%" | Abhijit Patel Walter Bender
| align=left valign=top |
;Brief explanation: Sugar collaboration uses a deprecated library, python-telepathy, which we no longer wish to maintain. We need to upgrade Sugar collab using something better
;Expected results: Working version of revised collab system.
* Refactored presenceservice
* Common Collabwrapper module for all sugar activities.

;Knowledge prerequisites: python, prior knowledge of networking. knowledge of telepathy might be useful.
|
}