Sugar Labs - User contributions [en]

Oversight Board/2025-2026-candidates/Sebastian Silva

2024-11-22T19:34:17Z

Sebastian: /* About Me */

=== About Me ===

Hi, I’m Sebastián Silva, also known as Icarito. I’ve been part of Sugar Labs since 2008, contributing in various ways, including mentoring in Google Summer of Code and developing educational tools. I’m also the creator of one of the most popular Sugar Activities, HablarConSara - https://wiki.laptop.org/go/HablarConSara , an old chatbot integrated with Speak.

I’ve always believed in the power of free software to transform education, and I’d love to continue supporting Sugar Labs as part of the oversight board.

=== Vision ===

I've since worked on facilitating learning of novice programmers, I'd love revisit our learning routes. Also I'm involved in a Laptop project that doesn't use Sugar. Would love to reduce the distance to making it useful for us.

=== Goals ===
If elected to the oversight board, I commit to:

* Attending meetings regularly to stay actively involved in decision-making.
* Supporting community projects and helping contributors bring their ideas to life.
* Working to expand Sugar Labs’ reach and make it accessible to more educators, students, and developers.

I’m excited about the opportunity to contribute further and support the amazing work of this community.

Oversight Board/2025-2026-candidates/Sebastian Silva

2024-11-22T18:57:27Z

Sebastian: /* Goals */

=== About Me ===

Hi, I’m Sebastián Silva, also known as Icarito. I’ve been part of Sugar Labs since 2008, contributing in various ways, including mentoring in Google Summer of Code and developing educational tools. I’m also the creator of one of the most popular Sugar Activities, [HablarConSara](https://wiki.laptop.org/go/HablarConSara), which helps children learn Spanish pronunciation.

I’ve always believed in the power of free software to transform education, and I’d love to continue supporting Sugar Labs as part of the oversight board.

=== Vision ===

I've since worked on facilitating learning of novice programmers, I'd love revisit our learning routes. Also I'm involved in a Laptop project that doesn't use Sugar. Would love to reduce the distance to making it useful for us.

=== Goals ===
If elected to the oversight board, I commit to:

* Attending meetings regularly to stay actively involved in decision-making.
* Supporting community projects and helping contributors bring their ideas to life.
* Working to expand Sugar Labs’ reach and make it accessible to more educators, students, and developers.

I’m excited about the opportunity to contribute further and support the amazing work of this community.

Oversight Board/2025-2026-candidates/Sebastian Silva

2024-11-22T18:56:54Z

Sebastian: /* Goals */

=== About Me ===

Hi, I’m Sebastián Silva, also known as Icarito. I’ve been part of Sugar Labs since 2008, contributing in various ways, including mentoring in Google Summer of Code and developing educational tools. I’m also the creator of one of the most popular Sugar Activities, [HablarConSara](https://wiki.laptop.org/go/HablarConSara), which helps children learn Spanish pronunciation.

I’ve always believed in the power of free software to transform education, and I’d love to continue supporting Sugar Labs as part of the oversight board.

=== Vision ===

I've since worked on facilitating learning of novice programmers, I'd love revisit our learning routes. Also I'm involved in a Laptop project that doesn't use Sugar. Would love to reduce the distance to making it useful for us.

=== Goals ===
If elected to the oversight board, I commit to:

* Attending meetings regularly to stay actively involved in decision-making.
* Supporting community projects and helping contributors bring their ideas to life.
* Working to expand Sugar Labs’ reach and make it accessible to more educators, students, and developers.

I’m excited about the opportunity to contribute further and support the amazing work of this community.

Oversight Board/2025-2026-candidates/Sebastian Silva

2024-11-22T18:56:15Z

Sebastian: First version

=== About Me ===

Hi, I’m Sebastián Silva, also known as Icarito. I’ve been part of Sugar Labs since 2008, contributing in various ways, including mentoring in Google Summer of Code and developing educational tools. I’m also the creator of one of the most popular Sugar Activities, [HablarConSara](https://wiki.laptop.org/go/HablarConSara), which helps children learn Spanish pronunciation.

I’ve always believed in the power of free software to transform education, and I’d love to continue supporting Sugar Labs as part of the oversight board.

=== Vision ===

I've since worked on facilitating learning of novice programmers, I'd love revisit our learning routes. Also I'm involved in a Laptop project that doesn't use Sugar. Would love to reduce the distance to making it useful for us.

=== Goals ===
If elected to the oversight board, I commit to:

Attending meetings regularly to stay actively involved in decision-making.
Supporting community projects and helping contributors bring their ideas to life.
Working to expand Sugar Labs’ reach and make it accessible to more educators, students, and developers.

I’m excited about the opportunity to contribute further and support the amazing work of this community.

Infrastructure Team/Contacts

2018-01-31T17:27:20Z

Sebastian: /* Core admins */

<noinclude>{{TeamHeader|Infrastructure Team}}</noinclude>
{{TOCright}}

== Team coordinator ==
{{:Infrastructure Team/Coordinator}}

== Support and administrative requests ==

'''Please, do not cc multiple administrative contacts in the same email.''' If you do not receive an answer within 48 hours, please ping one of us by email or IRC.

;User accounts
:<accounts AT sugarlabs DOT org>
:See also [[Service/Account]]

;Sugar Labs web site and wiki
:<webmaster AT sugarlabs DOT org>
:See also [[Service/wiki]]

;Git project hosting
:<gitmaster AT sugarlabs DOT org>
:See also [[Service/git]]

;Sugar Planet
:<planetmaster AT sugarlabs DOT org>
:See also [[Sysadmin/Planet_syndication_request]], [[Service/planet]]

;DNS Management and Domains Registration
:<hostmaster AT sugarlabs DOT org>
:See also [[Service/Nameservers]]

;Other requests
:<sysadmin AT sugarlabs DOT org>

== Team Contacts ==

* Infrastructure Team mailing-list: http://lists.sugarlabs.org/listinfo/systems
* IRC: [http://chat.sugarlabs.org #sugar on FreeNode]

== Services status ==

http://identi.ca/group/sugarlabsstatus

This Identi.ca feed sends updates about the health status of all our
services and machines. Subscribe if you want to be notified.

Notifications for planned service outages are also posted ahead of time on our
"It's An Education Project" (iaep) list (check the [http://wiki.sugarlabs.org/go/Mailing_Lists#General_Lists Mailing Lists] page).

== Sysadmin Contacts ==

;For problems with a specific service (e.g. [[Service/wiki|this wiki]]): consult the specific [[Service]] page for a list of sysadmin contacts
;For problems with a server (e.g. [[Machine/sunjammer|sunjammer]]): consult the specific [[Machine]] page for a list of sysadmin contacts
;For anything else: your friendly sysadmins can be contacted at '''<sysadmin ''AT'' sugarlabs ''DOT'' org>'''

== Core admins ==

For urgent matters, the core Sugar Labs sysadmins are:

* [[User:Bernie|Bernie Innocenti]], '''bernie''' on [http://chat.sugarlabs.org/ #sugar], PGP [http://keys.sugarlabs.org:11371/pks/lookup?op=vindex&search=0x71FF4BAC 71FF4BAC]
* [[User:Scg|Samuel Cantero]], '''scg''' on [http://chat.sugarlabs.org/ #sugar]
* [[User:SAMdroid|Sam Parkinson]], '''samdroid''' on [http://chat.sugarlabs.org/ #sugar]
For any non-urgent business, preferably use the official administrative contacts instead of contacting any individual system administrator directly.

Obsolete Machine/jita

2018-01-29T05:48:25Z

Sebastian: Undo revision 101278 by Sebastian (talk) Actually, it's okay to shut this down.

{{TOCright}}

== Hostnames ==

* http://jita.sugarlabs.org

== Hardware ==

* KVM VM

== Location ==

[[Machine/justice|Justice]]

== Admins ==

* [[User:alsroot|Aleksey Lim]]
* [[User:Scg|Samuel Cantero]], '''scg''' on [http://chat.sugarlabs.org/ #sugar]

== Backups ==

* Daily system-full-backup to [[Machine/backup]]. Ask admins for encryption password.
* Daily system-remote-backup to [[Machine/backup]]. Encrypted with keys of bernie.

== Notes ==

Directory usage:

* {{Code|/srv/<app>}} directories with installed applications

Obsolete Machine/jita

2018-01-29T05:44:32Z

Sebastian: Undo revision 101277 by MrBIOS (talk) Actually I continue to support the Sugar Network, thanks.

{{TOCright}}

== Hostnames ==

* http://jita.sugarlabs.org

== Hardware ==

* KVM VM

== Location ==

[[Machine/justice|Justice]]

== Admins ==

* [[User:Sebastian|Sebastian Silva]], '''icarito''' on [http://chat.sugarlabs.org/ #sugar]
* [[User:Scg|Samuel Cantero]], '''scg''' on [http://chat.sugarlabs.org/ #sugar]

== Backups ==

* Daily system-full-backup to [[Machine/backup]]. Ask admins for encryption password.
* Daily system-remote-backup to [[Machine/backup]]. Encrypted with keys of bernie.

== Notes ==

Directory usage:

* {{Code|/srv/<app>}} directories with installed applications

Features

2017-10-12T05:50:10Z

Sebastian: /* Feature status */

<noinclude>__FORCETOC__</noinclude>
==[[Features/Policy|Policy]]==

This section of the wiki is for proposing and tracking new Sugar features. As described in more detail on the [[Features/Policy|''Policy Page'']], we have a process by which ''community ideas on how Sugar should evolve'' get transformed into ''actionable proposals''.

===Upcoming Stable Release Roadmap===
The upcoming stable release is Sugar [[{{Upcoming Stable Release}}]].
* See the [[{{Upcoming Stable Release}}/Roadmap]] and [[{{Upcoming Stable Release}}/Feature List]]

=== Feature status ===
{| class="wikitable sortable" border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: black;"
|-
!Feature
!Component
!Proposed by
!Status
|-
|[[Features/3G Support|3G Support]]||Sugar||Martin Abente||Landed
|-
|[[Features/About Me|About Me]]||Sugar||Walter Bender||Landed
|-
|[[Features/Accessibility control panel|Accessibility control panel]]||Sugar||Esteban Arias||In progress
|-
|[[Features/Accessibility virtual keyboard|Accessibility virtual keyboard]]||Sugar||Esteban Arias||In progess
|-
|[[Features/Activity.info|Activity.info]]||Sugar Toolkit||Walter Bender||Idea stage
|-
|[[Features/Activity Help|Activity Help]]||Sugar||Kalpa Welivitigoda||Landed
|-
|[[Features/Activity Objects|Activity Objects]]||Sugar Toolkit||Aleksey Lim||Idea stage
|-
|[[Features/Activity as a regular Journal Object|Activity as a regular Journal Object]]||Sugar||Aleksey Lim||Idea stage
|-
|[[Features/Activity specific metadata in Journal|Activity specific metadata in Journal]]||Sugar||Walter Bender||In progress
|-
|[[Features/Ad hoc Networking|Ad hoc Networking]]||Sugar||Simon Schampijer||Landed
|-
|[[Features/Add Information In About Computer|Add Information In About Computer]]||Sugar||Gonzalo Odiard||Landed
|-
|[[Features/Automatic Proxy Settings|Automatic Proxy Settings]]||Sugar||Ariel Calzada||In progress
|-
|[[Features/Automatic activity updates|Automatic activity updates]]||Sugar||Daniel Drake||Landed
|-
|[[Features/Avoid surplus Activity launching|Avoid surplus Activity launching]]||Sugar||Christoph Derndorfer||Obsolete
|-
|[[Features/Background image on home view|Background image on home view]]||Sugar||Walter Bender||Landed
|-
|[[Features/Backup and Restore|Backup and Restore]]||Sugar||Greg Smith||Landed
|-
|[[Features/Buddy Positioning|Buddy Positioning]]||Sugar||Simon Schampijer||In progress
|-
|[[Features/Bug Report|Bug Report]]||Sugar||Aleksey Lim||Idea stage
|-
|[[Features/Bulletin Board|Bulletin Board]]||Sugar||Walter Bender||Obsolete
|-
|[[Features/Can share|Can share]]||Sugar||Simon Schampijer||Idea stage
|-
|[[Features/Change home view name|Change home view name]]||Sugar||James Cameron||Waiting review
|-
|[[Features/Classroom management|Classroom management]]||Sugar||Walter Bender||In progress
|-
|[[Features/Clipboard Item Transfer|Clipboard Item Transfer]]||Sugar||Simon Schampijer||Idea stage
|-
|[[Features/Clock in Frame|Clock in Frame]]||Sugar||Tony Forster||In progress
|-
|[[Features/Comment box in journal detail view|Comment box in journal detail view]]||Sugar||Walter Bender||Landed
|-
|[[Features/Configuring Hidden Wifi Access Points|Configuring Hidden Wifi Access Points]]||Sugar||Ajay Garg||Landed
|-
|[[Features/Connection Indication|Connection Indication]]||Sugar||Simon Schampijer||Idea stage
|-
|[[Features/Content support|Content support]]||Sugar||Daniel Drake||Landed
|-
|[[Features/Cordova Container for Sugar|Cordova Container for Sugar]]||Sugarizer||Lionel Laské & Puneet Kaur||Landed
|-
|[[Features/Develop Web|Develop Web]]||Sugar Activity||Kartik K Perisetla||Idea stage
|-
|[[Features/Discovery mode|Discovery mode]]||Sugar||John Tierney||Idea stage
|-
|[[Features/Display Device|Display Device]]||Sugar||Martin Abente||Landed
|-
|[[Features/Display section for control panel|Display section for control panel]]||Sugar||Walter Bender||Idea stage
|-
|[[Features/Dotted Activity Versions|Dotted Activity Versions]]||Sugar||Simon Schampijer||Landed
|-
|[[Features/Edit panel on Frame|Edit panel on Frame]]||Sugar||Walter Bender||Idea stage
|-
|[[Features/Enhanced Gettext|Enhanced Gettext]]||Sugar Toolkit||Sayamindu Dasgupta||Landed
|-
|[[Features/Enhanced color selector|Enhanced color selector]]||Sugar||Walter Bender||Landed
|-
|[[Features/Evince Introspection Bindings|Evince Introspection Bindings]]||Sugar Activity||Gonzalo Odiard||Landed
|-
|[[Features/Fast Language Switch|Fast Language Switch]]||Sugar||Aleksey Lim||Idea stage
|-
|[[Features/Fixing Collab (Tubes)|Fixing Collab (Tubes)]]||Sugar Toolkit||Sam Parkinson||Landed
|-
|[[Features/Flash Activities|Flash Activities]]||Sugar Toolkit||Tomeu Vizoso||Landed
|-
|[[Features/Font configuration|Font configuration]]||Sugar||Daniel Drake||Unknown
|-
|[[Features/Frame Panels|Frame Panels]]||Sugar||Aleksey Lim||Unknown
|-
|[[Features/FreeDesktop integration|FreeDesktop integration]]||Sugar Toolkit||Sebastian Silva||In progress
|-
|[[Features/GObject Introspection|GObject Introspection]]||Sugar Toolkit||Tomeu Vizoso||Landed
|-
|[[Features/GTK3|GTK3]]||Sugar||Tomeu||Landed
|-
|[[Features/Global Text To Speech|Global Text To Speech]]||Sugar||Gonzalo Odiard||Landed
|-
|[[Features/Host Version|Host Version]]||Sugar||Christoph Derndorfer||Idea stage
|-
|[[Features/Icon Change|Icon Change]]||Sugar||Ignacio Rodríguez||Landed*
|-
|[[Features/Improved Accessibility|Improved Accessibility]]||Sugar||Tomeu Vizoso||Landed
|-
|[[Features/Inquiry learning global chat|Inquiry learning global chat]]||Sugar Activity||John Tierney||Idea stage
|-
|[[Features/Introduction Tutorial|Introduction Tutorial]]||Sugar Activity||Erick Lavoie||Landed*
|-
|[[Features/Join Limits|Join Limits]]||Sugar||Walter Bender||Landed
|-
|[[Features/Journal Entry Sharing|Journal Entry Sharing]]||Sugar||Simon Schampijer||Landed
|-
|[[Features/Journal Sort|Journal Sort]]||Sugar||Andrés Ambrois||Landed
|-
|[[Features/Journal Volume Toolbar enhancement|Journal Volume Toolbar enhancement]]||Sugar||Walter Bender||Idea stage
|-
|[[Features/Journal data tagged private or public|Journal data tagged private or public]]||Sugar||Walter Bender, Gonzalo Odiard||Idea stage
|-
|[[Features/Keyboard CP Section|Keyboard CP Section]]||Sugar||Sayamindu Dasgupta||Landed
|-
|[[Features/Language keyboard options|Language keyboard options]]||Sugar||Walter Bender||Idea stage
|-
|[[Features/Launch Limits|Launch Limits]]||Sugar||Walter Bender||Landed
|-
|[[Features/Lease Information Display|Lease Information Display]]||Sugar||Anish Mangal||Unknown
|-
|[[Features/License selection in Journal|License selection in Journal]]||Sugar||Anish Mangal||Unknown
|-
|[[Features/Messages Notification|Messages Notification]]||Sugar||Martin Abente||Landed
|-
|[[Features/Metacity|Metacity]]||Sugar||Tomeu Vizoso||Landed
|-
|[[Features/Multi XS-server registration|Multi XS-server registration]]||Sugar||Manash Pratim Das||In progress
|-
|[[Features/Multi selection|Multi selection]]||Sugar||Ajay Garg||Landed
|-
|[[Features/Multiple home views|Multiple home views]]||Sugar||Walter Bender||Landed
|-
|[[Features/Neighborhood List View|Neighborhood List View]]||Sugar||Tomeu Vizoso||Idea stage
|-
|[[Features/Network control panel|Network control panel]]||Sugar||Frederick Grose||Landed
|-
|[[Features/New ASLO|New ASLO]]||Infrastructure||Sam Parkinson||In progress
|-
|[[Features/New Toolbar Design|New Toolbar Design]]||Sugar Toolkit||Aleksey Lim||Landed
|-
|[[Features/Notification Progress Bar|Notification Progress Bar]]||Sugar||Sam Parkinson||In progress
|-
|[[Features/Notification Replacement|Notification Replacement]]||Sugar||Sam Parkinson||In progress
|-
|[[Features/Notification System|Notification System]]||Sugar||Sam Parkinson||In progress
|-
|[[Features/Notification Urgency|Notification Urgency]]||Sugar||Sam Parkinson||In progress
|-
|[[Features/Object Bundles|Object Bundles]]||Sugar||Aleksey Lim||Unknown
|-
|[[Features/Object Collections|Object Collections]]||Sugar||Aleksey Lim||Unknown
|-
|[[Features/Onscreen Keyboard|Onscreen Keyboard]]||Sugar|| Sayamindu||Landed
|-
|[[Features/Optimize TreeViews|Optimize TreeViews]]||Sugar||Manuel Quiñones and Gonzalo Odiard||Landed
|-
|[[Features/Optional activity updates|Optional activity updates]]||Sugar||Martin Abente Lahaye||Landed
|-
|[[Features/Optional adhoc autoconnect|Optional adhoc autoconnect]]||Sugar||Martin Abente Lahaye||Landed
|-
|[[Features/Parental controls|Parental controls]]||Sugar||Tony Forster||Idea stage
|-
|[[Features/Patch workflow|Patch workflow]]||Infrastucture||ALeksey Lim||Obsolete
|-
|[[Features/Peer to Peer Objects Sharing|Peer to Peer Objects Sharing]]||Sugar||Aleksey Lim||Landed
|-
|[[Features/Plain Query Format|Plain Query Format]]||Sugar||Aleksey Lim||Idea stage
|-
|[[Features/Print Support|Print Support]]||Sugar||Daniel Castelo||Unknown
|-
|[[Features/Problem Reports|Problem Reports]]||Sugar Activity||Wade Brainerd||Landed*
|-
|[[Features/Proxy Settings|Proxy Settings]]||Sugar||Sascha Silbe||Landed
|-
|[[Features/Publish Sugar Version|Publish Sugar Version]]||Sugar||Gonzalo Odiard||Landed
|-
|[[Features/Remove Presence Service|Remove Presence Service]]||Sugar||Tomeu Vizoso||Landed
|-
|[[Features/Replace GtkMenu|Replace GtkMenu]]||Sugar Toolkit||Sam Parkinson||In progress
|-
|[[Features/Replace combo box in journal search|Replace combo box in journal search]]||Sugar||Walter Bender||Landed
|-
|[[Features/Replace combo box in language panel|Replace combo box in language panel]]||Sugar||Walter Bender||Landed
|-
|[[Features/Resource monitoring|Resource monitoring]]||Sugar||Fred Grose||Unknown
|-
|[[Features/Revised Browse default-bookmarks.html|Revised Browse default-bookmarks.html]]||Sugar Activity||Mel Chua||Landed
|-
|[[Features/Semantic Web|Semantic Web]]||Sugar Toolkit||Christophe Gueret||In progress
|-
|[[Features/Server Objects Sharing|Server Objects Sharing]]||Infrastucture||Aleksey Lim||Idea stage
|-
|[[Features/Show Thumb Drives As Hierarchical|Show Thumb Drives As Hierarchical]]||Sugar||James Simmons||Idea stage
|-
|[[Features/Signed Bundles|Signed Bundles]]||Infrastucture||Wade||Idea stage
|-
|[[Features/SimpleActivity|SimpleActivity]]||Sugar Toolkit||Agustin Zubiaga||Landed
|-
|[[Features/Simple Messages Notification|Simple Messages Notification]]||Sugar|| Martin Abente||Landed
|-
|[[Features/Smart Objects|Smart Objects]]||Sugar||Aleksey Lim||Idea stage
|-
|[[Features/SoaS Creation Station|SoaS Creation Station]]||Infrastructure||Thomas Gilliard||In progress
|-
|[[Features/SoaS Remixability|SoaS Remixability]]||Infrastructure||Thomas Gilliard||In progress
|-
|[[Features/SoaS customization|SoaS customization]]||Infrastructure||Thomas Gilliard||In progress
|-
|[[Features/Social Help|Social Help]]||Infrastructure||Sam Parkinson||Landed
|-
|[[Features/Spent Times|Spent Times]]||Sugar||Martin Abente Lahaye||Landed
|-
|[[Features/Spiral Home View|Spiral Home View]]||Sugar||Walter Bender||Landed
|-
|[[Features/Start activity from another activity|Start activity from another activity]]||Sugar Toolkit||Manuel Quiñones||Landed
|-
|[[Features/Statistics gathering|Statistics gathering]]||Sugar Toolkit||Sebastian Silva||Obsolete
|-
|[[Features/Sugar3 Docs|Sugar3 Docs]]||Infrastructure||Sam Parkinson||In progress
|-
|[[Features/Sugar Activity Library on a Stick|Sugar Activity Library on a Stick]]||Infrastructure||Tom Gilliard||Landed
|-
|[[Features/Sugar Adhoc Networks|Sugar Adhoc Networks]]||Sugar||Simon Schampijer||Landed
|-
|[[Features/Sugar Bundles|Sugar Bundles]]||Sugar||Aleksey Lim||Idea stage
|-
|[[Features/Sugar Creation Kit DVD|Sugar Creation Kit DVD]]||Infrastructure||Thomas Gilliard||Landed
|-
|[[Features/Sugar Update Control ASLO|Sugar Update Control ASLO]]||Sugar||David Farning||Landed
|-
|[[Features/Sync datastore object changes|Sync datastore object changes]]||Sugar||Simon Schampijer||Unknown
|-
|[[Features/TableView Widget|TableView Widget]]||Sugar Toolkit||Aleksey Lim||Obsolete
|-
|[[Features/Tabs In Browse|Tabs In Browse]]||Sugar Activity||Tomeu Vizoso||Landed
|-
|[[Features/Tags in Journal|Tags in Journal]]||Sugar||Aleksey Lim||Landed
|-
|[[Features/Teacher Buddy|Teacher Buddy]]||Sugar||Walter Bender||In progress
|-
|[[Features/Terminal Sharing|Terminal Sharing]]||Sugar Activity||Ben Schwartz||Landed
|-
|[[Features/Text To Speech In The Toolkit|Text To Speech In The Toolkit]]||Sugar Toolkit||Gonzalo Odiard||Landed
|-
|[[Features/Thumbs View in Journal|Thumbs View in Journal]]||Sugar||Aleksey Lim||Landed
|-
|[[Features/Tick based animation|Tick based animation]]||Sugar||Sam Parkinson||In progress
|-
|[[Features/Toolbar utils|Toolbar utils]]||Sugar Toolkit||Walter Bender||Obsolete
|-
|[[Features/Touch|Touch]]||Sugar||Simon Schampijer||Landed
|-
|[[Features/Touchpad control panel section|Touchpad control panel section]]||Sugar||Walter Bender||Landed
|-
|[[Features/Transfer to many|Transfer to many]]||Sugar||Simon Schampijer||Landed
|-
|[[Features/Trigger Bundle Add|Trigger Bundle Add]]||Sugar||Martin Abente Lahaye||Landed
|-
|[[Features/Unified Browser for Objects|Unified Browser for Objects]]||Sugar||Aleksey Lim||Idea stage
|-
|[[Features/Update Favorites|Update Favorites]]||Sugar||Walter Bender||Landed
|-
|[[Features/WPA-WPA2-Enterprise-Network-Connections|WPA-WPA2-Enterprise-Network-Connections]]||Sugar||Sascha Silbe||Landed
|-
|[[Features/WebKit|WebKit]]||Sugar Activity||Daniel Drake||Landed
|-
|[[Features/Web services|Web services]]||Sugar||Walter Bender||Landed
|-
|[[Features/Write to journal anytime|Write to journal anytime]]||Sugar Toolkit||Walter Bender||Landed
|}

===See also===

For a more organized view of the features, see [[:Category:Feature]]

More information:

[[Request New Features]] | [[Wish list]] | [[:Category:Idea]] | [[:Category:FeatureLanded]]

==Subpages==
Features currently under consideration are described on individual subpages, linked below.{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Machine/vote

2017-09-25T03:42:10Z

Sebastian: Add missing docs

<noinclude>{{TOCright}}</noinclude>

== Info ==

This is a special purpose server used for hosting surveying tools for the Membership and Election Committee. It was first created in [http://meeting.sugarlabs.org/sugar-meeting/2015-11-02#i_2855082 2015] and kept dormant until 2017 it was used again for the same purpose, and adding Ignacio as sysadmin.

== Services ==

Currently only to receive email verification requests from Ignacio's Flask verify script.

== Sysadmin procedures ==

Document here when necessary. Currently no passwords are used, only ssh keys for login. Sugar Labs admins may login from the virsh console on Freedom without further credentials for root.

== Location ==

This is a vm running of Freedom. Allocated 2GB Ram + 20GB Storage.

== Network configuration ==

* Currently using dynamically asigned IP. Need own IP.

== Backups ==

None at the moment.

== Admins ==

Admins with root access:

* Ignacio
* [[User:Sebastian|Sebastian Silva]], icarito on #sugar Freenode
* Laura

Talk:Sugar Labs/Conduct

2017-09-23T11:30:48Z

Sebastian: List requirements for a proper CoC

From http://geekfeminism.wikia.com/wiki/Community_anti-harassment:

In order to adopt a policy, you need at minimum, the following:

* a policy
* a contact point where harassment reports can be received
* a group of responders who receive reports and have the power to act on them up to and including excluding harassers from your community

Oversight Board/2017-2019-candidates

2017-09-23T01:42:55Z

Sebastian:

==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 (versión en [http://educa.juegos/workspace/sugarlabs_platform_2017/index_es.html Español])=

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 ''[[Sugar_Labs/Conduct|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.

=Sameer Verma=
My background [[User:Sverma|here]].

=== Introduction===

I am a professor in the Information Systems department at San Francisco State University, in San Francisco, California USA. I also serve on the Board of Directors of the Drupal Association, which gives me significant insights into how large FOSS projects work both in the community and the enterprise. I am the founder of the OLPC San Francisco volunteer community, that continues to be active around OLPC's original mission and projects that have grown from that ecosystem, including Sugar, XS, XOVis and others.

=== Experience ===

My experience with Sugar projects are based on a three-pronged approach:

:''Education''

:Understanding constructivist, constructionist, instructional and ad-hoc learning models. I look for accommodating for the gap between what may be prescribed, and what can actually be implemented in the field.

:''Technology''

:Hardware, software, and network combinations that make these projects work in the “middle of nowhere” communities. My professional training comes in handy when working on these technology bits.

:''Social Context''

:Understanding social context is the most important of the three approaches. Providing powerful life-changing educational tools to communities is not enough unless we also understand their cultural and social underpinnings.

=== Expected Contribution ===

To maintain Sugar's technology focus as a medium of delivery, while maintaining the education message. I hope to bring my skills and expertise to contribute to the strategic direction of Sugar the project, and its implementations on any device, anywhere.

=Sean Daly=

I am an independent journalist, formerly working for a large company in IT, communications, advertising and marketing. As my children are (mostly) grown, and I set my own work schedule, I will have time to commit to Sugar again. I have been part of Sugar Labs since 2009, including a term as a SLOB, and was Marketing Coordinator for 5 years.

The major changes in "educational technology" - from computer lab, to netbook, to tablet - mean that beyond the XO platform, Sugar must adapt and indeed is doing so, through Sugarizer and other initiatives. At the same time, the rapid growth of social media has created new opportunities to communicate about Sugar, opportunities which are not being seized today.

As a SLOB, I will work to grow our community and to raise awareness of Sugar.

=Adam Holt=

As its 10-year anniversary quickly approaches, Sugar Labs needs to do more than survive as a fragile vessel for One Laptop per Child's many still unmet dreams.

Sugar Labs can now begin standing up conscientiously in new areas, building on real-world deliverables like Sugarizer 0.9 on Internet-in-a-Box (a.k.a. the OLPC School Server Community Edition, http://schoolserver.org) now in use in a very rapidly growing number of countries where the XO laptop never quite took root:

https://www.socallinuxexpo.org/scale/15x/speakers/adam-holt 
https://www.socallinuxexpo.org/scale/15x/presentations/internet-box

Google Summer of Code (GSoC) and Google Code-in (GCI) are an amazingly powerful start to bring us together constructing collaboratively + openly + coherently -- but these are not the only revenue/volunteer streams Sugar Labs and the Sugar Movement can bank on during its second decade!

All such strategic progress is beginning to take shape for an entirely new generation of DIY Sugar culture. But it is thanks to an underlying non-chaotic legal and accounting strategy with the Software Freedom Conservancy that all this is possible.

I have worked for 10 years with Sugar Labs (originally as OLPC's Community Support Manager) and then as Sugar Labs' liaison/representative to the Software Freedom Conservancy (SFC) for 2 years now to solidify a foundation here.

= Claudia Urrea =
I have more 20 years of experience in the field of Education and Technology. I am currently working at the MIT Jameel World Education Lab (J-WEL) as the Associate Director PreK-12. I have helped multiple governments and non-government agencies to empower and support schools and communities of learners to evolve from traditional teaching methods into progressive learning environments.

I have a degree in Computer Science/Systems Engineering, a Master's degree in Educational Media and Technology from Boston University, and a doctorate degree from the MIT Media Laboratory. During my PhD thesis, I studied the implications of one to one learning in a rural setting in Latin America, which provided the knowledge and experience that I brought to the Interamerican Development Bank as a consultant in the Education Sector, and later, during 5 years I spent with One Laptop Per Child (OLPC) as Director of Learning. My interests include computational thinking and open-free software, personalized and digital learning and assessment, curriculum design, education for developing countries, teacher professional development, educational programming and robotics, maker education, quality learning at scale, among others.

During the last year at OLPC, I joined the Sugar Labs board, which allowed to develop a number of programs, resources and events in collaboration with Walter Bender and other members of the community. My current position at MIT and my knowledge of both Sugar Labs and the international educational community would allow me to bring new opportunities for Sugar Labs. I have witness the powerful opportunities SugarLabs and the work of the community have brought to a great number of children and young adults from many countries in the world. I would like to work hard to try to bring those to many more.

==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.
[[User:Ignacio|Ignacio Rodríguez]] [http://lists.sugarlabs.org/archive/systems/2017-August/005520.html will be in charge] of all the technical procedures with the assistance of Sugar Labs infrastructure team: systems AT list.sugarlabs.org

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].

During [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01T19:10:08 September's meeting] the Board '''confirmed September 27, 2017 as the deadline for new memberships request to participate on 2017-2019 elections'''.

Oversight Board/2017-2019-candidates

2017-09-21T07:30:27Z

Sebastian: /* Sebastian Silva */ Added link to Spanish translation.

==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 (versión en [http://educa.juegos/workspace/sugarlabs_platform_2017/index_es.html Español])=

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.

=Sameer Verma=
My background [[User:Sverma|here]].

=== Introduction===

I am a professor in the Information Systems department at San Francisco State University, in San Francisco, California USA. I also serve on the Board of Directors of the Drupal Association, which gives me significant insights into how large FOSS projects work both in the community and the enterprise. I am the founder of the OLPC San Francisco volunteer community, that continues to be active around OLPC's original mission and projects that have grown from that ecosystem, including Sugar, XS, XOVis and others.

=== Experience ===

My experience with Sugar projects are based on a three-pronged approach:

:''Education''

:Understanding constructivist, constructionist, instructional and ad-hoc learning models. I look for accommodating for the gap between what may be prescribed, and what can actually be implemented in the field.

:''Technology''

:Hardware, software, and network combinations that make these projects work in the “middle of nowhere” communities. My professional training comes in handy when working on these technology bits.

:''Social Context''

:Understanding social context is the most important of the three approaches. Providing powerful life-changing educational tools to communities is not enough unless we also understand their cultural and social underpinnings.

=== Expected Contribution ===

To maintain Sugar's technology focus as a medium of delivery, while maintaining the education message. I hope to bring my skills and expertise to contribute to the strategic direction of Sugar the project, and its implementations on any device, anywhere.

=Sean Daly=

I am an independent journalist, formerly working for a large company in IT, communications, advertising and marketing. As my children are (mostly) grown, and I set my own work schedule, I will have time to commit to Sugar again. I have been part of Sugar Labs since 2009, including a term as a SLOB, and was Marketing Coordinator for 5 years.

The major changes in "educational technology" - from computer lab, to netbook, to tablet - mean that beyond the XO platform, Sugar must adapt and indeed is doing so, through Sugarizer and other initiatives. At the same time, the rapid growth of social media has created new opportunities to communicate about Sugar, opportunities which are not being seized today.

As a SLOB, I will work to grow our community and to raise awareness of Sugar.

=Adam Holt=

As its 10-year anniversary quickly approaches, Sugar Labs needs to do more than survive as a fragile vessel for One Laptop per Child's many still unmet dreams.

Sugar Labs can now begin standing up conscientiously in new areas, building on real-world deliverables like Sugarizer 0.9 on Internet-in-a-Box (a.k.a. the OLPC School Server Community Edition, http://schoolserver.org) now in use in a very rapidly growing number of countries where the XO laptop never quite took root:

https://www.socallinuxexpo.org/scale/15x/speakers/adam-holt 
https://www.socallinuxexpo.org/scale/15x/presentations/internet-box

Google Summer of Code (GSoC) and Google Code-in (GCI) are an amazingly powerful start to bring us together constructing collaboratively + openly + coherently -- but these are not the only revenue/volunteer streams Sugar Labs and the Sugar Movement can bank on during its second decade!

All such strategic progress is beginning to take shape for an entirely new generation of DIY Sugar culture. But it is thanks to an underlying non-chaotic legal and accounting strategy with the Software Freedom Conservancy that all this is possible.

I have worked for 10 years with Sugar Labs (originally as OLPC's Community Support Manager) and then as Sugar Labs' liaison/representative to the Software Freedom Conservancy (SFC) for 2 years now to solidify a foundation here.

= Claudia Urrea =
I have more 20 years of experience in the field of Education and Technology. I am currently working at the MIT Jameel World Education Lab (J-WEL) as the Associate Director PreK-12. I have helped multiple governments and non-government agencies to empower and support schools and communities of learners to evolve from traditional teaching methods into progressive learning environments.

I have a degree in Computer Science/Systems Engineering, a Master's degree in Educational Media and Technology from Boston University, and a doctorate degree from the MIT Media Laboratory. During my PhD thesis, I studied the implications of one to one learning in a rural setting in Latin America, which provided the knowledge and experience that I brought to the Interamerican Development Bank as a consultant in the Education Sector, and later, during 5 years I spent with One Laptop Per Child (OLPC) as Director of Learning. My interests include computational thinking and open-free software, personalized and digital learning and assessment, curriculum design, education for developing countries, teacher professional development, educational programming and robotics, maker education, quality learning at scale, among others.

During the last year at OLPC, I joined the Sugar Labs board, which allowed to develop a number of programs, resources and events in collaboration with Walter Bender and other members of the community. My current position at MIT and my knowledge of both Sugar Labs and the international educational community would allow me to bring new opportunities for Sugar Labs. I have witness the powerful opportunities SugarLabs and the work of the community have brought to a great number of children and young adults from many countries in the world. I would like to work hard to try to bring those to many more.

==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.
[[User:Ignacio|Ignacio Rodríguez]] [http://lists.sugarlabs.org/archive/systems/2017-August/005520.html will be in charge] of all the technical procedures with the assistance of Sugar Labs infrastructure team: systems AT list.sugarlabs.org

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].

During [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01T19:10:08 September's meeting] the Board '''confirmed September 27, 2017 as the deadline for new memberships request to participate on 2017-2019 elections'''.

Talk:Oversight Board/2017-2019-candidates

2017-09-16T01:07:54Z

Sebastian:

I suppose the (seemingly arbitrary) limit of 1500 characters has forced me to be focused. You can look at the change log to see my 3000 character statement. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 16:13, 31 August 2017 (EDT)

The 1500 character's limit is strategic to increase readability of all candidates statements. It was properly presented as the requirement for valid candidacies to current Oversight Board during [http://meeting.sugarlabs.org/sugar-meeting/2017-08-04 August meeting]. [[User:Laura Vargas|Laura Vargas]] ([[User talk:Laura Vargas|talk]]) 20:01, 31 August 2017 (EDT)

:I don't follow the logic--seems arbitrary. I didn't agree with purging the members list either. But I defer to the committee. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 20:26, 31 August 2017 (EDT)

:Seems you have passed my answer on the previous paragraph. Again, please read to remember this procedure was approved during SLOB's August meeting. [http://meeting.sugarlabs.org/sugar-meeting/2017-08-04 August meeting][[User:Laura Vargas|Laura Vargas]] ([[User talk:Laura Vargas|talk]]) 00:08, 13 September 2017 (EDT)

::On the contrary, I have read the minutes in the link you provided and no where do I see a discussion about restricting statements to 1500 characters. Also, nowhere to I see documentation of the members committee discussion of this decision. I stand by my opinion that it is arbitrary and unnecessary. I also reiterate my decision to defer to the committee (although it would be comforting to see the discussion thread backing up your assertion.) --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 08:04, 13 September 2017 (EDT)

:: Walter, backing up my assertion please read Line at 19:08 "Candidates should create a wiki entry below (1 entry per candidate, 1.500 characters max) sharing their vision and motivation." Not arbitrary but consented. Anyhow, you have been the only candidate complaining so I guess the limit was logic for everyone else. [[User:Laura Vargas|Laura Vargas]] ([[User talk:Laura Vargas|talk]]) 08:10, 13 September 2017 (EDT)

::I am not sure how I missed the line at 19:08. Nonetheless, this reads as a report from the members committee, not an oversight board decision. Where is the members committee meeting log? I still see no justification ("logic") behind the limit explained and stand by my right to disagree with the decision. I am a bit taken back by your characterizing my disagreeing as complaining. I thought we were a community that welcomed discussion and criticism of the status quo. And I will say yet again, although I disagree with the decision (and the means by which it has been enforced), I defer to the committee. My statement is <= 1500 characters. I am not sure what more you want from me Laura. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 08:32, 13 September 2017 (EDT)

:: Again, the decision was taken by the Membership and Elections Committee and ratified during the SLOB's meeting. We try to keep the Systems list copied on all meetings in case you want to explore how we have taken all decisions about the elections. I guess your criticism is OK but inaccuracy and is not. Meeting complete Reference at http://lists.sugarlabs.org/archive/systems/2017-August/005514.html [[User:Laura Vargas|Laura Vargas]] ([[User talk:Laura Vargas|talk]]) 09:05, 13 September 2017 (EDT)

:::(0) Thank you for acknowledging that I am entitled to an opinion. (1) I have seen no evidence presented that any decision was taken by the Membership and Elections Committee. I await the link to that discussion. (2) Your reporting the decision to the oversight board is not a ratification. Can you please explain where I am inaccurate? If you go back to my original post, I didn't question the process by which the decision was made -- although now I have my doubts as I see no discussion of the 1500 character limit by the committee, only your proposing it -- but rather, I expressed my opinion of the decision. How is that "inaccurate"? Meanwhile, back to coding. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 09:16, 13 September 2017 (EDT)

I strongly suggest candidates to optimize space given and avoid irrelevant information such as quoting other people's thoughts different from those thoughts of the candidate him/her self. Instead I suggest candidates to focus on a simple message to share your motivation, vision and/or management skills that make you an ideal candidate for the Sugar Labs Oversight Board.
[[User:Laura Vargas|Laura Vargas]] ([[User talk:Laura Vargas|talk]]) 20:06, 31 August 2017 (EDT)
and updated by [[User:Laura Vargas|Laura Vargas]] ([[User talk:Laura Vargas|talk]]) 02:20, 7 September 2017 (EDT)

:Another "properly presented" requirement? --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 20:26, 31 August 2017 (EDT)
:Thank you for your clarification. While I appreciate your input, I do think it is appropriate to quote people from whom I have drawn inspiration regarding the development of and sustaining of Sugar, so I will risk leaving my statement as is. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 07:19, 7 September 2017 (EDT)

As a candidate who read the instructions and wrote within the limit, I think it is disrespectful of other candidates to bypass this requirement, even if you don't agree with it. There are plenty of venues for expression of your opinion, but it is fair to voters to have a summary in one location.
[[User:Sebastian|Sebastian]] ([[User talk:Sebastian|talk]]) 21:07, 15 September 2017 (EDT)

Design Team/Contacts

2017-09-14T11:46:37Z

Sebastian: /* Team Members */

<noinclude>{{TeamHeader|Design Team|roadmap_link=Design Team/Vision|roadmap_label=Vision}}[[Category:Design Team]][[Category:Contact]]
</noinclude>

== Coordinators ==
{{:Design Team/Coordinator}}

== IRC channel ==
Sugar designers (and developers) hang out in the [irc://irc.freenode.net/sugar #sugar] channel on irc.freenode.net.

== Team Members ==
Please add yourself to the list if you're interested in participating!

*[[User:Walter | Walter Bender]]
*[[User:MartinDengler | Martin Dengler]]
*[[User:Eben | Eben Eliason]]
*[[User:FGrose | Frederick Grose]]
*[[User:sascha_silbe | Sascha Silbe]]
*[[User:Walter | Fadi Tash]]
*[[User:Josh | Josh Williams]]
*[[User:David Brown|David Brown]] 21:37, 22 August 2012 (EDT)
* [[User:Sebastian|Sebastian Silva]]
* [[User:Laura Vargas|Laura Vargas]]

Design Team/Contacts

2017-09-14T11:45:28Z

Sebastian: /* Team Members */

2017-02-19T16:03:41Z

Sebastian: /* Core admins */

<noinclude>{{TeamHeader|Infrastructure Team}}</noinclude>
{{TOCright}}

== Team coordinator ==
{{:Infrastructure Team/Coordinator}}

== Support and administrative requests ==

'''Please, do not cc multiple administrative contacts in the same email.''' If you do not receive an answer within 48 hours, please ping one of us by email or IRC.

;User accounts
:<accounts AT sugarlabs DOT org>
:See also [[Service/Account]]

;Sugar Labs web site and wiki
:<webmaster AT sugarlabs DOT org>
:See also [[Service/wiki]]

;Git project hosting
:<gitmaster AT sugarlabs DOT org>
:See also [[Service/git]]

;Sugar Planet
:<planetmaster AT sugarlabs DOT org>
:See also [[Sysadmin/Planet_syndication_request]], [[Service/planet]]

;DNS Management and Domains Registration
:<hostmaster AT sugarlabs DOT org>
:See also [[Service/Nameservers]]

;Other requests
:<sysadmin AT sugarlabs DOT org>

== Team Contacts ==

* Infrastructure Team mailing-list: http://lists.sugarlabs.org/listinfo/systems
* IRC: [http://chat.sugarlabs.org #sugar on FreeNode]

== Services status ==

http://identi.ca/group/sugarlabsstatus

This Identi.ca feed sends updates about the health status of all our
services and machines. Subscribe if you want to be notified.

Notifications for planned service outages are also posted ahead of time on our
"It's An Education Project" (iaep) list (check the [http://wiki.sugarlabs.org/go/Mailing_Lists#General_Lists Mailing Lists] page).

== Sysadmin Contacts ==

;For problems with a specific service (e.g. [[Service/wiki|this wiki]]): consult the specific [[Service]] page for a list of sysadmin contacts
;For problems with a server (e.g. [[Machine/sunjammer|sunjammer]]): consult the specific [[Machine]] page for a list of sysadmin contacts
;For anything else: your friendly sysadmins can be contacted at '''<sysadmin ''AT'' sugarlabs ''DOT'' org>'''

== Core admins ==

For urgent matters, the core Sugar Labs sysadmins are:

* [[User:Bernie|Bernie Innocenti]], '''bernie''' on [http://chat.sugarlabs.org/ #sugar], PGP [http://keys.sugarlabs.org:11371/pks/lookup?op=vindex&search=0x71FF4BAC 71FF4BAC]
* [[User:Sebastian|Sebastian Silva]], '''icarito''' on [http://chat.sugarlabs.org/ #sugar], GPG [http://pgp.mit.edu/pks/lookup?op=get&search=0x0F2D4857959A0072 959A0072]
* [[User:Scg|Samuel Cantero]], '''scg''' on [http://chat.sugarlabs.org/ #sugar]
* [[User:SAMdroid|Sam Parkinson]], '''samdroid''' on [http://chat.sugarlabs.org/ #sugar]
For any non-urgent business, preferably use the official administrative contacts instead of contacting any individual system administrator directly.

== We Care (tm) ==

[[Image:Barbeque computer.jpg]]

[[Category:Contact]]

Sugar Labs/Conduct

2017-01-18T05:56:51Z

Sebastian: Added references

<noinclude>
[[Category:Policy]]
{{Draft | Hi Priority}}
</noinclude>

There is a current code of conduct which dates back to 2009 at [[Sugar_Labs/Legal/Code_of_Conduct]]. The following is a proposed update of it. A motion to adopt it will be made when there's been some discussion.

=== Why have a Code of Conduct? ===
Online communities include people from many different backgrounds. The Go contributors are committed to providing a friendly, safe and welcoming environment for all, regardless of age, disability, gender, nationality, race, religion, sexuality, or similar personal characteristic.

The first goal of the Code of Conduct is to specify a baseline standard of behavior so that people with different social values and communication styles can talk about Go effectively, productively, and respectfully.

The second goal is to provide a mechanism for resolving conflicts in the community when they arise.

The third goal of the Code of Conduct is to make our community welcoming to people from different backgrounds. Diversity is critical to the project; for Go to be successful, it needs contributors and users from all backgrounds. (See Go, Open Source, Community.)

With that said, a healthy community must allow for disagreement and debate. The Code of Conduct is not a mechanism for people to silence others with whom they disagree.

==== References ====
http://geekfeminism.wikia.com/wiki/Community_anti-harassment

https://golang.org/conduct

https://www.rust-lang.org/en-US/conduct.html

http://maitria.com/coc

https://rfc.unprotocols.org/spec:1/C4/

Sugar Labs/Conduct

2017-01-14T17:05:10Z

Sebastian:

2016-04-17T06:25:37Z

Sebastian:

* [[0.110/Feature List/Sugar ScreenshotDialogPopup|Screenshot Dialog Popup]]
* [[Features/Replace_GtkMenu|Replace Gtk Menu]] https://github.com/sugarlabs/sugar/pull/567 -> Note, feel free to adopt this if you want it to actually get done
* https://bugs.sugarlabs.org/ticket/4900 https://github.com/sugarlabs/sugar/pull/609
* [[Features/FreeDesktop integration|Better integrate with X11 FreeDesktop]]

Translation-Community Manager

2016-04-06T04:43:11Z

Sebastian: Defined as paid delegation. Added language about prior teams.

The Translation-Community Manager leads and co-ordinates the efforts of the Sugar community to enable users to experience Sugar in their own language. This is a paid delegation currently being debated by SLOBs.

This delegation is not meant to eclipse [[Translation Team]], its [[Translation_Team/Coordinator|coordinators]], or any other party interested in helping out with localization.

== Background ==

Translation often refers to the specific task of providing text in a target language from the
text in the source language. For software, this task is conventionally divided into two steps:

* Internationalization (I10n)
::Enable localization in the base software; and
* Localization (L10n)
::Provide local-language equivalents for text in the base software.

The base software for Sugar consists of two major components:

* Sugar Desktop
:: The Sugar Desktop is part of a [https://fedoraproject.org/wiki/Remix Fedora Remix]. It provides the basic means for user interaction with Sugar. (Note that the Journal activity is a part of the Sugar Desktop.)

* Sugar Activities
:: Sugar provides a library, ASLO (activities.sugarlabs.org), of several hundred individual activities that a user can install and run. (Note that many Sugar activities can run independently from the Sugar Desktop, e.g., the GNOME Desktop, the Sugarizer environment, or in a web browser.)

Internationalization (I10n) prepares the Sugar Desktop and Sugar Activities for localization (L10n).
* I18n
::Sugar and its activities are primarily written in Python (although increasingly JavaScript is being used for activity development). I18n is supported by giving developers a means to identify text that can be displayed to the user. Alternate text can be provided in other languages than the original and the user can select an alternate language for Sugar and the activities to use in displaying this text.

::Selecting an alternate language for Sugar requires other technical steps. The language must be visible in Sugar (in the [https://github.com/sugarlabs/sugar/blob/master/extensions/cpsection/language/model.py#L124 Language Control Panel]). Selecting the language needs to change other aspects of Sugar (e.g display right-left, handle '.' or ',' for decimals and grouping multiples of 1000, display of dates, and so on).

* L10n
::Sugarlabs provides a service hosted at http://translate.sugarlabs.org that supports localization of Sugar. It is based on Pootle, a process and software to facilitate localization. In particular, it stores files with the original text for Sugar and its activities and files with the strings for local language

:The overall process is fail-safe in the sense that if an alternate language is selected but there is no string available in that language, Sugar displays the original string found in the code (most often English). http://translate.sugarlabs.org saves translated strings that are immediately available for use in subsequent releases, leaving localizers to provide strings for new text in the release. If that text is not provided, the original text is displayed.
==User Environment==
Sugar (Fedora Remix) is the software that supports the OLPC XO laptop. There have been about 2.5 million of these laptops manufactured and distributed. Many of these laptops are in daily use at schools and other institutions throughout the world. Typically, these laptops are used in a language of instruction (English, Spanish, French, ...). (The Remix is also on other hardware and is the basis of Sugar on a Stick, although no firm figures are available on how many learners use the Remix. There is also Debian support for the Sugar Desktop.)

At the schools using Sugar, many of the users communicate in a native language other than English. For example, in the Philippines, there are two official languages: Filipino (Tagalog) and English. While users can take advantage of Sugar and the laptops in English, they would enjoy an opportunity to use them in Filipino. In addition, there are indigenous languages spoken by some of the users. Making the Sugar experience available in these languages is typical of the localization opportunities for Sugar.

In most cases localization is done by language specialists under the umbrella of Pootle (http://pootle.translatehouse.org/). This process requires technical skills and effective access to the internet.

Translation requires language skills in the target language and the source language (e.g. English, Spanish, French). If possible, I18n and specific language help arranged by the Translation-Community Manager should enable Sugar users to perform this localization on their own laptops. The installation or updating of the localization on translate.sugarlabs.org should be arranged by the Translation-Community Manager. (Also, providing a common intermediary language, such as Spanish, when translating to an indigenous language, such as Aymara, falls under the responsibility of the Translation-Community Manager: there are many more Aymara speakers who know Spanish than English.)

==Software Environment==

Change is an essential feature of computer use. Platforms change. Sugar is faced with some immediate tasks relating to this change:

* Touch screen replacing trackpad and mouse keys, and, often, the keyboard;
* Move to Android and Web sevrices, which do not directly support Python;
* Developer focus on HTML5, CSS3, and JavaScript as an implementation environment for activities (and the Sugar experience itself).

==Duties==

The Translation-Community Manager, reporting to the Sugar Labs Oversight Board, is responsible to lead the community in supporting its goal to provide the Sugar experience in the users native language. The Translation-Community Manager will:

* Work with the community to recruit volunteer help in supporting the translation process (occasional professional services to seed L10n efforts may be contracted as well.);
* Advise the Sugar Labs Oversight Board of supporting projects that need funding and to manage these projects, if approved;
* Develop and maintain the I18n capabilities of Sugar and its activities;
*# Arrange for development and maintenance of the I18n infrastructure such as translate.sugarlabs.org;
*# Arrange for an inventory of Sugar activities in ASLO (activities.sugarlabs.org) showing the current I18n and L10n status of each;
*# Arrange for development and maintenance of I18n infrastructure to support new and emerging platforms and software environments for Sugar;
* Work with the community to identify schools and institutions that have deployed Sugar and to arrange for members of the community to reach out to these deployments to offer help with localization or other needs;
*# Arrange as needed to add a language to those with I18n support in Sugar and Sugar activities;
*# Arrange for a simple and well-documented procedure for these deployments to provide their own translation and to share the results with the community;
* Report monthly to the Sugar Labs Oversight Board and to the community and to the public on the status of the translations program, preferably by blogging informally (blog posts can be any length) to http://planet.sugarlabs.org using plain language that is understandable to almost all.
* Report every 4 months on tactical/strategic/financial choices; reports can be of any length and should be posted/archived together to a unique URL (linked from http://wiki.sugarlabs.org/go/Translation-Community_Manager) one month prior to the completion of each 4-month cycle, mentioning:
*# What actually happened over current 4-month cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)
*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we tactically nurture continuous improvement?
*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.

The Sugar Labs Oversight Board must affirm continuation (or renewal) of the contract before the end of each 4-month cycle. (It is anticipated that this will largely be a "rubber-stamping" procedure; the expectation is that the contract will renew—insofar as funds allow—while the translation community strengthens. But this "dead man's switch" is a critical check to keep us—each and all—conscientiously engaged, accountable, and involved.)

File:Html5 logo.png

2016-03-13T14:02:50Z

Sebastian:

Summer of Code/2016

2016-03-10T19:09:40Z

Sebastian: /* Sugar Core */

'''Students''': See our guide on [[Summer_of_Code#How_to_participate|how to participate in Google Summer of Code]] for more information.

== Project candidates ==

In the table below is a list of projects potential participants might contribute to in the GSoC program.

;Note 0: These are project ideas from Sugar Labs contributors. '''Students, feel free to propose your ideas as well.'''
;Note 1: Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.
;Note 2: Potential students, more project ideas can be found on our [[Features]] page.

== Sugar Core ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project
|-
!valign=top | ||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.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python
|-
!valign=top | [[File:Journal-12.jpeg|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Journal Rethink ||valign=top width="15%" | Sam Parkinson ||align=left valign=top|
;Brief explanation: The Sugar Journal could be rethought to add more emphasis on collaboration, or adding more organisational support for creating "projects" among other things.
;Expected results: Working code for the journal and vague ideas (more concrete than this) defined ahead of time.
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+.
|-
!valign=top | [[Image:Sugarlabs_mainpage_01.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Groups Rethink ||valign=top width="15%" | Sam Parkinson ||align=left valign=top|
;Brief explanation: Sugar has a buddies/group zoom view, which is very limited. It could be further integrated with sugar (eg. send to group, share with group, have a shared group journal) and expanded upon (having multiple groups user configured, like: a science prac group, a drama play group, etc.).
;Expected results: Working code for the Sugar and vague ideas (more concrete than this) defined ahead of time.
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+. Knowledge of telepathy is might be helpful.

|-
!valign=top | [[File:reflect.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Reflect Activity||valign=top width="15%" | Sam Parkinson and Walter Bender ||align=left valign=top|
;Brief explanation: The Sugar Journal is designed to be a place of reflection. We have the basic stub of a reflection activity that attempts to encourage more reflection and as a vehicle for sharing criticism. This idea needs more thought and coding.
;Expected results: A solid formulation of how the activity will work in the classroom and working code for the Reflect Activity.
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+.

|-
!valign=top | [[File:git_logo.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Git backend||valign=top width="15%" | Martin Abente Lahaye and Walter Bender ||align=left valign=top|
;Brief explanation: The Sugar Journal doesn't do a great job of supporting versioning or forking. This project is to build a backend for the Journal that is based on git, which does support versioning and forking. By building on top of a git hosting site we get the added benefit of network access as well.
;Expected results: Working code and an integration with Turtle Blocks
;Knowledge prerequisite: Strong background in Git and scripting languages such as Python, Ruby and JavaScript.

|-
!valign=top | || valign=top style="background:#e3e4e5;" | Performance tuning on machines with limited memory || valign=top | Samuel Greenfeld||align=left valign=top |
;Brief explanation: The newer Sugar builds have performance issues on some old hardware with limited memory. This is keeping some Sugar deployments from upgrading. This project is to look into the performance issues and tune Sugar for low-memory devices.
;Expected results: build suitable for running on OLPC XO-1 hardware
;Knowledge prerequisite:

|-
!valign=top | || valign=top style="background:#e3e4e5;" | Re-design collaboration with web technologies || valign=top | Martin Abente Lahaye and Walter Bender ||align=left valign=top |
;Brief explanation: Now that JavaScript has become a first class citizen in the Sugar ecosystem, we must re-design our collaboration model to allow collaboration between web activities regardless of the platform.
;Knowledge prerequisite: JavaScript, web sockets, web services.

|-
!valign=top | [[File:freedesktop_logo.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Make Sugar compliant with Freedesktop standards||valign=top width="15%" | [[User:Sebastian|Sebastian]] ([[User talk:Sebastian|talk]]) 13:50, 10 March 2016 (EST) ||align=left valign=top|
;Brief explanation: Support Freedesktop.Org Desktop Entry specification for launching non-sugar applications, icon standards, etc. Find other ways to make Sugar useful as Linux desktop. Make it easy to run Sugar Activities in regular Linux desktop.
;Expected results: Improved user experience for users of regular Linux apps, merged to Sugar mainline.
;Knowledge prerequisite: Strong background in GTK, Python and GNU/Linux.

|-
!valign=top | [[File:html5_logo.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Port Sugar to the Broadwayd HTML5 GTK Backend||valign=top width="15%" | [[User:Sebastian|Sebastian]] ([[User talk:Sebastian|talk]]) 14:09, 10 March 2016 (EST) ||align=left valign=top|
;Brief explanation: Sugar uses GTK3. Recently GTK3 released support for a HTML5 native backend called Broadwayd.
;Expected results: Make it feasible to run Sugar and pure gtk3 activities thru a browser (not Sugarizer). Docker container for Sugar on Broadwayd.
;Knowledge prerequisite: Strong background in GTK, Python and GNU/Linux. Docker.

|}

== Sugar Activities ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!valign=top | [[File:confusion.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Beyond Flashcards: Programming to ReadJS||valign=top width="15%" | Walter Bender||align=left valign=top|
;Brief explanation: Back in the 1980s, IBM had a literacy program, "Writing to Read". The gist was that writing was a great way to spark a child's interest in reading. What if writing code could achieve a similar result? The project is to explore how programming might be incorporated into a literacy program. Like turtle, only simple sentences instead of stacks. It would be a "whole word" approach rather than a "phonics" approach: they can take "sentences" and make paragraphs that result in animations.
;Expected results: Working prototype
;Knowledge prerequisite: Strong background in Python or JavaScript

|-
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" | Covert Record, Clock, Speak and Measure to gstreamer 1.0 ||valign=top width="15%" | <TBD> ||align=left valign=top|
;Brief explanation: The vast majority of Activities that use gstreamer for sound have been converted to gstreamer 1.0 because the older 0.10 is now End of Life and is no longer being developed. It also adds quite a large set of extra duplicate dependencies to Sugar distributions. There's a lot of good examples of Activities that have been converted to provide excellent examples. The gstreamer 1.0 bindings are provided by gobject-introspection so it also assists in the conversion of Activities to gtk3.
;Expected results: As many of the above Activities converted to use gst 1.0
;Knowledge prerequisite: Strong background in Python, gobject-introspection and gstreamer

|-
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" | Covert TamTam to Csound6 ||valign=top width="15%" | <TBD> ||align=left valign=top|
;Brief explanation: TamTam makes extensive use of CSound, other Activities like Memorize, Pippy, and TurtleBlocks also can make use of CSound bindings. With the introduction of CSound 6 to a number of distributions TamTam needs migration to use the newer version of CSound.
;Expected results: Convert TamTam to use CSound6, possibly other Activities
;Knowledge prerequisite: Strong background in Python, background in CSound

|-
!valign=top | [[File:Music-Blocks.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Music Widgets||valign=top width="15%" | Devin Ulibarri ||align=left valign=top|
;Brief explanation: Development four new widgets to improve the possibilities for music
learning as well as overall user-experience for Music Blocks. The widgets are 1. Pitch-Staircase 2. Tempo 3. Rhythm Rulers, and 4. Free-Pitch Slider. Widgets will integrate with the current coding environment without disrupting the underlying language in any way (like the current pitch-time matrix).
;Expected results: Users will use these to explore musical concepts and generate desired
blocks from their experiments.
;Knowledge prerequisite: Strong background in Javascript, Basic knowledge of Music Theory
and/or physics
|}

== Sugar Activities (and Ports) ==

These are existing and new activities we'd like to see enhanced. We expect that the activities will take on new UI features and pedagogical significance.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!valign=top | [[File:Music-Blocks.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Music Blocks Challenges||valign=top width="15%" | Devin Ulibarri||align=left valign=top|
;Brief explanation: Development of the "Power Piece" concept for teaching music and programming. (Power Pieces introduce rich musical ideas that can be studied, analyzed, transformed, and re-imagined, they are ripe for open-ended explorations.)
;Expected results: A well-documented series of activities for exploring musical and programming concepts using the Music Blocks activity as a foundation.
;Knowledge prerequisite: Strong background in Javascript, Music Theory
|-
!valign=top | [[File:Nutrition-icon.svg|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Nutritional Microworld||valign=top width="15%" | w/Dr. Jessica Early||align=left valign=top|
;Brief explanation: We have the basic building blocks (Turtle Nutrition) for programming with food as a datatype. What we are missing is a collection of meaningful activities to use with the tool as exemplars. We want to develop a an open-ended, yet
relevant tool—one that invites learners to explore fundamental concepts of nutrition that are both intrinsic to nutrition yet transcendent of a specific discipline.
;Expected results: A well-documented series of activities for exploring nutrition that use the nutrition plugin as a basis. A series of workshops to study these ideas with children.
;Knowledge prerequisite: Strong background in Javascript, some background in Nutrition.
|-
!valign=top | [[File:Turtle-Flags.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Turtle Confusion/Flags JS||valign=top width="15%" | Walter Bender||align=left valign=top|
;Brief explanation: Port of Turtle Confusion and Turlte Flags.
;Expected results: A framework for creating challenges and a few exemplars.
;Knowledge prerequisite: Strong background in Javascript

|-
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" | Tux Math||valign=top width="15%" | Tony Anderson ||align=left valign=top|
The TuxMath activity is popular with deployments. However, the upstream version appears to be abandoned. This task would be to implement a sugar-web-activity math game comparable to TuxMath.

|}

== Sugar Technology ==

Sugar is based on the Python programming language and the GTK libraries. We also support some web technologies: HTML5, CSS, and JavaScript.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!valign=top | [[File:Debugging.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Unit Testing ||valign=top width="15%" | TBD ||align=left valign=top|
Deep dive into unit tests. We have a framework but it provides scant coverage for Sugar core and almost no coverage for Sugar activities.
;Brief Description: The goal is to develop tests for many more subsystems in Sugar core and to light a fire under the developer community to write tests for Sugar activities.
;Expected Results: a new test suite and scads of documentation.
;Knowledge Prerequisite: A strong background in Python.

|-
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" | Redesign and recreate Sugar Labs webappearance ||valign=top width="15%" | Tymon Radzik ||align=left valign=top|
Create new modern and innovative design template for our websites and apply it to all our systems. Consider, how to improve our webappearance. Currently, almost every our website looks different than other and is created in different technology.
;Brief Description: The goal is to create new template to be used to unify view of our websites (main page, Wiki, Planet, Traslation system, ...) and apply it to our systems. It must include storing all code in one place (like in repositories on Github), reducing number of technologies used, improving SEO, considering other solutions to be used instead of obsolete pages and general design.
;Expected Results: new, better webappearance of Sugar Labs, basing on innovative template. All code should be placed in one place on Github.
;Knowledge Prerequisite: Strong skills in HTML5, CSS3, Javascript and other core webtechnologies; experience in creating modern website design.
|}

== Sugar on the Ground ==

A number of real-world issues crop up in deployments of Sugar, especially where resources are limited (bandwidth, CPU speed, battery life, local storage, etc.) These tasks are related to making Sugar more usable under such circumstances.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal save option ||valign=top width="15%" | Tony Anderson ||align=left valign=top|

The Sugar Journal should provide a 'save/save as' interface which should enable a user to choose whether to save the current document when an activity is closed. The interface should require a name change from 'current.activity' to a user supplied name. If the document is derived from one currently saved in the Journal, the user should be allowed to save (overwrite) or save as (create new document) by giving a new name to the document. This could be accomplished by showing a modal dialog at close time requesting the user to supply a name or not save the document. If the document has a user supplied name, the dialog could request the user to save or to provide a new name to create a new document.
;Note: this approach satisfies the needs referenced in the git task. Git is a little like a hammer looking for a nail. Using git for this function will likely double the size of the data stored in the Journal (based on normal experience using git). Unfortunately, we don't have this space on the XOs. The standard save/save as gives the user the ability to manage versions by using unique names.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal as a service ||valign=top width="15%" | Tony Anderson ||align=left valign=top|

The Journal activity is currently implemented as an activity. It should be changed to a 'service'. This means the Journal icon on the frame should be to the left of the zoom group icons to match the sequence on the keyboard. The Journal is always running as a service when the Sugar is running. It is accessible by the Journal key on the keyboard and also by the Journal button in the frame. When the view is switched to the Journal, clicking on the activity view (right most key of the zoom group) should switch the screen back to the current activity.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal backup and restore ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
Sugar provides a method to backup and restore the Journal (one method to a USB key and one method to the school server). The Journal also provides a select box to enable an action to be taken for all selected objects. This mechanism should be sufficient for the USB key case. However, the school server backup currently is based on taking a snapshot of the current Journal state. This means the size of the objects in a user's Journal cannot exceed the available local store on an XO (300MB for an XO-1, 1.9GB for other models). A mechanism is needed to save on the school server all documents created by the user and to restore a selected object to the Journal from the school server. Since many documents may represent library objects (e-books, audio, image or video media), the mechanism should recognize these and not save them as user documents. However, the metadata saved should enable the system to download the library items again as needed (and, as available).
;For example: the mechanism may be to upload Journal documents to an OwnCloud repository. The user could then select an item in the OwnCloud repository to be downloaded to the Journal. The user could also share any item in OwnCloud with other user groups or individuals
;Note: This would essentially accomplish the intent of the group/buddy task. Further, OwnCloud could be provided on a school server or on the internet. as appropriate.
;Note: There is a Sugar interface for saving to other cloud services, such as Google Docs, Dropbox, et al. that could be exploited.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal session data management ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
One goal of Sugar is to record information about user sessions. This is currently accomplished by creating statistics from the metadata stored in the Journal.
Unfortunately, a consequence is that the Journal view fills with essentially meaningless links to this metadata (mine fills with Terminal Activity and Log entries).
This makes it much harder for the user to identify meaningful Journal objects (documents, images, items from the library, ...). A mechanism is needed to that session data can be logged independently of the Journal view (i.e not shown on the screen). This logged information should be transferred to a backup repository (e.g. school server or USB drive) as soon as possible and deleted from the local store to free up space. The available reporting activities should be modified to use this new mechanism.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal quota management ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
The Journal icon provides information the amount of free space in the user's store. if this amount is less than 50MB, a dialog is shown requiring the user to switch to the Journal view and claiming that the 'Journal is Full'. This message is, at best, misleading. The available storage can arise from several causes - the fact that an activities 'instance' store was not deleted, the space required by installed activities, or space required by data files in /home/olpc/Library, or data stored by activities in 'data', 'instance' or 'temp'. Currently, Sugar provides no guidance or help to enable a user to deal with this problem short of reflashing the image. The goal of this task is to provide a quota management system on storage with a way for the user (e.g. by a special Sugar activity) to analyze the usage of storage and to save by usb key or school server or cloud storage large or currently unneeded items and then delete them. The system should show the user the size of items and provide updates on how much storage has been made free by his/her actions.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal activity resume feature ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
In Sugar's Home View, a click on an activity icon by default resumes the most recent instance of the activity. This capability is designed into the Journal and is redundant in the Home View. A Sugar activity is a tool to enable the user to accomplish some task. If that task is not completed, the user can resume it via the Journal. If the tool is to be used on a new task, the user can launch it from the Home View. The current Home View assumes that the intent of the user is to continue the most recent task with that tool.

This task should set the Home View default to launch a new instance of the activity. The Alt key should be set to enable resuming a selected instance of the activity. By serendipity, this also shows the Home View with black and white icons. Icons with color signifying a resumable instance use the colors associated with the laptop. Unfortunately many of these color combinations make the icon much more difficult to distinguish than the black and white version.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Activity resume feature ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
Sugar provides a 'web services' capability. However, these services are only available to an XO which has connection to the internet. This is not useful to a large number of users who do not have internet access. The school server (e.g. XSCE) provides an alternative to the internet for many deployments. This task is to provide a capability on the school server to support some or all of the Sugar web services (e.g. by OwnCloud or ELGG).

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar offline ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
There are a number of Sugar activities which currently require access to the internet (InfoSlicer, GetBooks). These activities should have an option to function with the school server. For example, GetBooks could access books on the school server and InfoSlicer could create slices from Wikipedia on the school server as Journal objects.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar "on-boarding" ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
Sugar users are often new to computers and not familiar with other operating systems. We need a mechanism to allow users to more quickly develop skills in using the capabilities of the XO ('onboarding'). One proposal is to develop scripts which lead the user through a series of interactive steps illustrating common usage of the XO with Sugar ([https://www.sam.today/blog/sugar-onboard-design.html]). This task is to implement an interpretive system that allows
deployments or experienced users to create an 'onboard' script that guides the user to carry out a task. The referenced proposal suggests some user tasks where this mechanism could be employed. Since there is no finite list of these tasks, an interpretive approach enables the scripts to be created as necessary.
;For example: how does a user switch to the Gnome desktop? A script could be created guiding the user through the necessary steps. How does the user make a screen shot, use Gimp in the gnome desktop to crop and resize, and then insert it as an image in a Write document? How does the user initiate or join a chat?

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | 32bit Sugar on Ubuntu||valign=top width="15%" | Tony Anderson ||align=left valign=top|
Sugar is available on the XO and some other platforms. In particular, Sugar is available for 64-bit systems with Ubuntu 14.04 LTS installed (http://wiki.sugarlabs.org/go/Ubuntu). Unfortunately, this procedure does not work with 32-bit systems. There exists an opportunity to deploy Sugar
with relatively inexpensive or refurbished laptops which do not provide 64-bit support. This task is to create a comparable version of Sugar which can
be installed on 32-bit systems as an alternate Ubuntu desktop.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | One to Many Sugar||valign=top width="15%" | Tony Anderson ||align=left valign=top|
The OLPC model is that each user has full possession and is the only user of an XO laptop. Therefore, Sugar assumes a 1-1 correspondence between users and XO serial numbers. However, Sugar is being used on other platforms (e.g. SOAS), where there is no obvious equivalent to a serial number. SOAS and James Cameron [citation?] have created versions of Sugar which do not assume the user is 'olpc', but implement a standard username/password login system. The users storage is allocated to his/her home directory.

This task is to create a Sugar image for the XO which allows for user's to login by username and password. The basic task is to move the Activities folder to a common space so that only one copy is needed per system. This will support deployments where one set of laptops are shared across multiple classes (and users) or where there one laptop is shared between two students - one in a morning shift and the other in an afternoon shift.

|}

== Sugarizer ==

[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 a bunch of activities written for Sugar in Sugar Web.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!valign=top | [[File:Sugarizer os android.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugarizer OS ||valign=top width="15%" | Lionel Laské and Michaël Ohayon||align=left valign=top|
The goal of this project is to create "Sugarizer OS".
Sugarizer OS is a way to boot directly a device on Sugarizer and allow the user to use both Sugarizer activities and system native applications. Sugarizer OS is not an OS but a way to propose a full Sugar experience on a non-Sugar device.

On Android, Sugarizer OS will take the form of an Android Launcher so it will be able to replace the standard Android launcher of the device. So the user will be able to launch both Sugarizer Activities and Android application from the Sugarizer home. The Sugarizer List View screen will let you choose which Android application icons will appear in the favorite view.

Into Sugarizer OS the Neighborhood view will let the user see and connect to a WiFi hotspot as in Sugar. The Sugarizer OS settings will allow to access to Android settings and let the use to switch to the standard Android launcher.

Prerequisite: Android, Java, HTML5/JavaScript.

How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then create your own APK following instructions [https://github.com/llaske/sugarizer/blob/master/README.md#build-client-for-android-or-ios here]. Think about how to adapt this APK to transform it into an Android launcher.

|-
!valign=top | [[File:Dashboard server.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugarizer Server Dashboard ||valign=top width="15%" | Lionel Laské and Michaël Ohayon ||align=left valign=top|
The goal of this project is to create the "Sugarizer Server Dashboard".
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.

Technology to use: 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.

|-
!valign=top | [[File:Fototoon-moon-speak.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugarizer Activity Set ||valign=top width="15%" | Lionel Laské and Michaël Ohayon ||align=left valign=top|
The goal of this project is to port some famous Sugar activities into HTML5/JavaScript Sugar Web activities that will be include into the Sugarizer Package. Three activities will be ported:
* Moon: Moon is a Moon phase viewer, includes Lunar phase information and eclipse data.
* Speak: Speak is a talking face. Anything you type will be spoken aloud using the speech synthesizer, espeak.
* Fototoon: Fototoon is an activity that let user create cartoons using pictures from the journal.

Technology to use: HTML5/JavaScript

How to start: Download and install Sugar like explain [https://wiki.sugarlabs.org/go/Downloads here] and install the existing version of activities to port: [http://activities.sugarlabs.org/us/sugar/addon/4034 Moon], [http://activities.sugarlabs.org/us/sugar/addon/4038 Speak], [http://activities.sugarlabs.org/us/sugar/addon/4253 Fototoon]. Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then create an empty Sugarizer activity following instructions [https://github.com/llaske/sugarizer/blob/master/README.md#create-your-own-activity here]. Think about how to reproduce features of existing activities.

|}

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

File:Freedesktop logo.png

2016-03-10T18:51:44Z

Sebastian: