Sugar Labs - User contributions [en]

Summer of Code/2017

2017-03-19T23:59:10Z

Davelab6: Remove Dave Crossland as mentor

== Project Ideas ==

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

|-
| valign=top width="15%" style="background:#e3e4e5;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
| align=left valign=top |
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details. See [[Translation Team]] for framework description.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |New Back-end Server for Turtle Blocks and Music Blocks<br>[[File:Git logo.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Vikram Ahuja<br>Ignacio Rodriguez
| align=left valign=top |
;Brief explanation: Last year we sponsored [http://vikramahujagsoc.blogspot.com/ an exploration] of using a git-like back end for projects so that they could be cloned, forked, etc. This summer we would like to implement and deploy this new approach.
;Expected results: Deployment of "git" back end.
;Knowledge prerequisites: Knowledge of Git, JavaScript, server-side skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Going Beyond Equal Temperament in Music Blocks<br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/issues Music Blocks issues].
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory

|-
| valign=top width="15%" style="background:#e3e4e5;" |Giving Sugar Labs Website a New Look
| valign=top width="15%" | Ignacio Rodriguez<br>Samson Goddy<br>Tymon Radzik
| align=left valign=top |
;Brief explanation: Sugar Labs would like a new look for its [https://github.com/sugarlabs/www-sugarlabs homepage], with the goals of making it more attractive and easier to explore (See link to get more information concerning the [https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md proposed homepage]).
;Expected results: Deployment of a new website for Sugar Labs
;Knowledge prerequisites: JavaScript, HTML, CSS, Ruby, JQuery, jeckyl, and/or django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Maintenance of activities.sugarlabs.org (ASLO)
| valign=top width="15%" | (volunteers?)
| align=left valign=top |
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded. Some maintenance tasks are needed. Sugar uses activities.sugarlabs.org in Software Update in My Settings, and has a link to it in the Browse default page.
;Expected results: Fix downloads by non-Sugar browsers; old versions are offered. Fix downloads by new versions of Sugar; old versions are offered. Make activity maintainer take-over easier; not easy at the moment. Adopt the new look from the new [http://www.sugarlabs.org/ sugarlabs.org] site; theme now is quite old. Show new activity.info metadata such as source repository. Other problems listed in [http://bugs.sugarlabs.org bugs.sugarlabs.org] against component [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=activities.sugarlabs.org&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&order=priority activities.sugarlabs.org]. Semi-automate common maintenance tasks; like adding a new Sugar version. Document future maintenance on the Wiki.
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git. See [https://github.com/sugarlabs/aslo source code].

|-
| valign=top width="15%" style="background:#e3e4e5;" |School Management Backend
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Sugar is a desktop and a collection of apps. It has great internal features for collaboration and journaling. But it doesn't have any mechanism for managing courses/curriculum/administrative functions commonly found in "school management systems". It could be possible to overlay on top of Sugar web-services such a toolkit.
;Expected results: a framework, a core implementation, and documentation for expanding the implementation.
;Knowledge prerequisites: Python, django

|-
| valign=top width="15%" style="background:#e3e4e5;" |Timbre Widget for Music Blocks<br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: Ayush Kumar designed a widget for designing voices for Music Blocks (See [http://kuckuck.treehouse.su:5000/task/5948636577923072/instance/5685003230904320/]). This project would be to implement the design.
;Expected results: a working widget for Music Blocks for manipulating Timbre.
;Knowledge prerequisites: JavaScript

|-
| valign=top width="15%" style="background:#e3e4e5;" |{{anchor|sugdash}}Sugarizer Server Dashboard<br>[[File:Dashboard server.png|90px|thumb|center]]
| valign=top width="15%" | Lionel Laské<br>Michaël Ohayon
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on Sugar Web library, which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates activities written for Sugar in Sugar Web. The goal of this specific project is to create the "Sugarizer Server Dashboard". This feature will require an enhancement of the existing Sugarizer Server API specifically to integrate a real authentication mechanism.

;Expected results: Sugarizer Server Dashboard is a web admin console for Sugarizer Server. The Dashboard will allow to manage and analyze all activity on a Sugarizer Server. Dashboard features will include:
* Users: how many users has been registered on the server, how many users currently connected, top users on the server, last users connection, create/edit/remove an user.
* Journal: how many Journals and how many entries in Journal on the server, last Journal and last entries, size of Journals, top Journals, edit a journal (see/update/remove) entries.
* Application: how many applications are available on the server, change application visibility from Client, update order and way to appear in favorite view.
* Graphic and request: display graphics and report on previous data.

;Knowledge prerequisites: HTML5/JavaScript, bootstrap, node.js, MongoDB
;How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then install Sugarizer server using instructions [https://github.com/llaske/sugarizer/blob/master/README.md#server here], finally explore the [http://sugarizer.org/apidoc/ Sugarizer Server API] and think about way to implement dashboard features with existing API.

|-
| valign=top width="15%" style="background:#e3e4e5;" |{{anchor|sugmdm}}Sugarizer Deployement and Management Tool for Android<br>[[File:Sugarizermdmtool.png|90px|thumb|center]]
| valign=top width="15%" | Michaël Ohayon<br>Lionel Laské
|align=left valign=top |

;Brief explanation: [http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies. Sugarizer can be deployed on many devices including Android phones and tablets. The goal of this specific project is to create the "Sugarizer Deployment and Management Tool for Android".

;Expected results: Sugarizer Server Deployment and Management Tool is a GUI Tool working on GNU/Linux, Mac and Windows to deploy and configure Android devices using ADB (Android Debug Bridge).
* Inventory : Collect and store devices data like serial number, os version, device name, installed applications, current Android launcher and Sugarizer availability.
* Application Manager : Install or remove applications using APK files.
* File Manager : Add / Remove files
* Input Manager : Click / Touch coordinates on the screen, launch applications to perform automations.
* Scenario Writer : Allow '''non developpers''' to create sequences to perform all the steps previously defined.

;Knowledge prerequisites: Java and JavaFX / Kotlin and TornadoFX
;How to start: Create a Java or Kotlin project using Intellij and display a window using JavaFX or TornadoFX. Then add https://github.com/vidstige/jadb and display connected android devices in the window.

|-
| valign=top width="15%" style="background:#e3e4e5;" |User Manual for Music Blocks<br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need something a bit more polished as a user manual.
;Expected results: A website and PDF document that can be bound.
;Knowledge prerequisites: Knowledge of music theory, writing skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |Just say no to GTK2
| valign=top width="15%" | Ignacio Rodriguez<br>Sam Parkinson
Abhijit Patel
| align=left valign=top |
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.
;Expected results: New versions of Turtle, Speak, Chat, Record, and a dozen others
;Knowledge prerequisites: Knowledge of GTK, GST, and Python
|-
| valign=top width="15%" style="background:#e3e4e5;" |Develop Activity<br>AKA Pippy JS, Taller del Artesano 2
| valign=top width="15%" |Sebastian Silva
| align=left valign=top |
;Brief explanation: We don't have a Javascript IDE for writing activities. This is a proposal to collaborate in making one. It would have templates for writing Javascript and Python.
;Expected results: New activity capable of making new activities, runnable in Web and Sugarizer
;Knowledge prerequisites: Python, Javascript, HTML5, CSS

|-
| valign=top width="15%" style="background:#e3e4e5;" |Debian SugarBlend
A.K.A: Harmonic Distribution, Deployment Platform
| valign=top width="15%" |Sebastian Silva<br>Jonas Smedegaard
| align=left valign=top |
;Brief explanation: Debian is a base for many educational derivative distribution. We would like to make a SugarBlend that is a good base for local integrators.
;Expected results: Debian SugarBlend of upcoming Debian 9 (Stretch)
;Knowledge prerequisites: Debian packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Sugar on Raspberry Pi
| valign=top width="15%" |Walter Bender
| align=left valign=top |
;Brief explanation: Raspberry Pi is a popular tool with the Maker Movement. Sugar runs quite well on RPi3, but it is in need of some love.
;Expected results: Packaged Sugar for RPi suitable for inclusion on the [https://www.raspberrypi.org/downloads/ RPi download page].
;Knowledge prerequisites: Debian and/or Fedora packaging, Linux system, Shell scripting

|-
| valign=top width="15%" style="background:#e3e4e5;" |Music Blocks for Mobile<br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri
| align=left valign=top |
;Brief explanation: Music Blocks was written for a browser, not mobile. It would be great to have a version native to mobile.
;Expected results: Working version on Android/and/or iOS. Some UI adjustments will be necessary.
;Knowledge prerequisites: Knowledge of JavaScript/Codrova/React and/or Swift.

|

|-
| valign=top width="15%" style="background:#e3e4e5;" |Collab Rethink<br>
| valign=top width="15%" | Abhijit Patel<br>Walter Bender
| align=left valign=top |
;Brief explanation: Sugar collaboration uses a deprecated library, python-telepathy, which we no longer wish to maintain. We need to upgrade Sugar collab using something better
;Expected results: Working version of revised collab system.
* Refactored presenceservice
* Common Collabwrapper module for all sugar activities.

;Knowledge prerequisites: python, prior knowledge of networking. knowledge of telepathy might be useful.
|
}

Sugar Labs/Members

2016-08-07T17:43:56Z

Davelab6: Add commitee info

<noinclude>[[Category:Policy]]</noinclude>
== Sugar Labs Membership ==
The Sugar Labs [[Sugar Labs/Members/List|members list]] consists of most of the contributors to the Sugar project. Members can run for election to the [[Oversight Board|Oversight Board]], vote in the elections for the Oversight Board, and suggest [[Sugar Labs/Governance#Sugar Labs Referenda|referenda]].

Any "significant and sustained" contributor to Sugar Labs is eligible for membership. Although it is difficult to specify a precise definition, a [[Sugar_Labs/Sugar_contributors|contributor]] generally must have contributed to a non-trivial improvement of the Sugar project or Sugar Labs activity. Contributions may be code, documentation, translations, maintenance of project-wide resources, ''running a Sugar deployment'', or other non-trivial activities which benefit Sugar Labs. Membership eligibility is an individual determination: while contributions made in the course of employment will be considered, they will generally be ascribed to the individuals involved, rather than accruing to all employees of a "contributing" corporation. The Membership and Elections Committee will oversee membership applications (Please apply by sending email to ''members at sugarlabs.org'').

The Membership and Elections Committee will review the membership list for currency once per year. Any member may join this committee, which is currently staffed by [[User:Sebastian/FuenteLibre|Sebastian Silva]], [[Samson Goddy]], and [mailto:cbigenho@hotmail.com Caryl Bigenho].

== Applying for membership ==
All submissions MUST be sent via email to '''members''' at '''sugarlabs.org'''. Submissions sent to other email addresses or sent after the deadline will not be processed for this year's election. Someone on the '''MEC''' will reply to your query within 2 business days. If you don't get a reply after a week, please contact the [[Samson Goddy]] or [mailto:cbigenho@hotmail.com Caryl Bigenho].

In your email, please include:
* Your name
* Your [[IRC]] / Wiki / [http://git.sugarlabs.org Gitorious] username
* A description of your contribution to Sugar Labs, links are preferable.

== Currency assurance policy ==

In order to ensure that the Sugar Labs Membership list is reflective of the current status of the project and its participants, once a year members will be asked to confirm that they still wish to be a Sugar Labs Member. If this request bounces, or if a request has not been replied to after it has been a) resent, b) checked for a more current email address, and c) six months have passed, the member will be sent a removal notice with an invitation to reapply.

The most recent currency review was in January 2016.

== Members List ==
This is our [http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List Sugar_Labs/Members/List].

== Membership Committee ==

For 2015 to 2016-08-01 the Membership and Election Committee was Caryl Bigenho, Samson Goddy, and Sebastian Silva.

The [[Oversight Board]] appoints members to the committee though a normal motion procedure.

== See Also ==
* [[Service/email]]

[[Category:Participate]]

2016 Goals

2016-08-07T16:51:49Z

Davelab6: add 2015 survey

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* to set up a matrix of VirtualBox prebuilt Sugar VMs, perhaps in partnership with Oracle;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment, how to get connected to the net with devices like https://smile.amazon.com/gp/product/B017CZWBBG/ and http://outernet.is/;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.);
** to update https://spins.fedoraproject.org/soas/ (see http://lists.sugarlabs.org/archive/marketing/2015-May/003859.html);
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to consolidate libre licensed books about Sugar;
** port [[olpc:Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom|http://wiki.laptop.org/go/Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom]] to our site;
** port https://www.gitbook.com/book/icarito/physics-with-xo/details to our site;
** liberate the ''Learning To Change The World'' text, and write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]] and [[Oversight_Board/Deployment_Survey_2015]]);
* to host the http://turtleartday.org website (see [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17116.html thread]);
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* to list critiques of OLPC and Sugar Labs and summarise the actionable recommendations;
** https://www.scribd.com/document/33505402/Has-the-non-profit-business-model-adopted-by-One-Laptop-Per-Child-hindered-its-success;
** [list more here];
* to move from IRC (and perhaps the mailing lists) to a [http://www.mattermost.org/why-we-made-mattermost-an-open-source-slack-alternative/ mattermost] instance;
* to set up https://botbot.me/irc-guide/ in the sugar-meeting channel
* [your goal here]

2016 Goals

2016-08-06T04:42:59Z

Davelab6: do botbot logged

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* to set up a matrix of VirtualBox prebuilt Sugar VMs, perhaps in partnership with Oracle;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment, how to get connected to the net with devices like https://smile.amazon.com/gp/product/B017CZWBBG/ and http://outernet.is/;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.);
** to update https://spins.fedoraproject.org/soas/ (see http://lists.sugarlabs.org/archive/marketing/2015-May/003859.html);
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to consolidate libre licensed books about Sugar;
** port [[olpc:Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom|http://wiki.laptop.org/go/Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom]] to our site;
** port https://www.gitbook.com/book/icarito/physics-with-xo/details to our site;
** liberate the ''Learning To Change The World'' text, and write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website (see [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17116.html thread]);
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* to list critiques of OLPC and Sugar Labs and summarise the actionable recommendations;
** https://www.scribd.com/document/33505402/Has-the-non-profit-business-model-adopted-by-One-Laptop-Per-Child-hindered-its-success;
** [list more here];
* to move from IRC (and perhaps the mailing lists) to a [http://www.mattermost.org/why-we-made-mattermost-an-open-source-slack-alternative/ mattermost] instance;
* to set up https://botbot.me/irc-guide/ in the sugar-meeting channel
* [your goal here]

Service/turtleartday.org

2016-07-27T04:55:22Z

Davelab6: Initial version based on https://wiki.sugarlabs.org/go/Service/www

== Description ==

The [[Turtle Art]] front page.

Managed with the Jekyll CMS, it contains static articles describing the annual event.

== Hostnames ==

http://www.turtleartday.org

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

marketing AT sugarlabs DOT org

== Sysadmins ==

Send email to the systems sugar labs list.

== Notes ==

In https://github.com/sugarlabs/turtleartday.org/settings/hooks there is a webhook defined, as documented at https://developer.github.com/webhooks/

This sends a POST request in JSON format to https://hook.sugarlabs.org/www.turtleartday.org

A container named org.turtleartday.www-rebuilder is in charge of processing this payload, which does the following:

1. Install jekyll.
2. Clone the SL repo.
3. Install Flask
4. Execute a Flask Python App which does the following: pull the repo and jekyll build. This app doesn't parse the POST request.

The site is generated in the folder /clone/_site which is bind to the following dir in freedom: /srv/tad-out. This is the doc root for the site in the nginx server block.

== Upgrade notes ==

Remember to restart the org.turtleartday.www-rebuilder container after upgrading freedom.

[[Category:Service|www]]

Service/www

2016-07-27T04:52:54Z

Davelab6: Update to 2016 reality

== Description ==

The SugarLabs front page.

Managed with the Jekyll CMS, it contains static articles describing the project.

== Hostnames ==

* http://www.sugarlabs.org

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

marketing AT sugarlabs DOT org

== Sysadmins ==

Send email to the systems sugar labs list.

== Notes ==

In https://github.com/sugarlabs/www-sugarlabs/settings/hooks there is a webhook defined, as documented at https://developer.github.com/webhooks/

This sends a POST request in JSON format to https://hook.sugarlabs.org/www.sugarlabs.org

A container named org.sugarlabs.www-rebuilder is in charge of processing this payload, which does the following:

1. Install jekyll.
2. Clone the SL repo.
3. Install Flask
4. Execute a Flask Python App which does the following: pull the repo and jekyll build. This app doesn't parse the POST request.

The site is generated in the folder /clone/_site which is bind to the following dir in freedom: /srv/www-out. This is the doc root for the SL in the nginx server block.

== Upgrade notes ==

Remember to restart the org.sugarlabs.www-rebuilder container after upgrading freedom.

[[Category:Service|www]]

Sugar Labs/Current Events

2016-07-23T15:55:24Z

Davelab6: Fix URL

<noinclude>
== What's new ==

This page is updated every few weeks with notes from the Sugar Labs community. (The digest is also sent to the community-news at sugarlabs.org list, blogged at [http://walterbender.org/ walterbender.org], and [[Archive/Current Events|archived here]].) If you would like to contribute, please send email to [[User:walter|walter]] at sugarlabs.org by the weekend. (Also visit <span class="plainlinks">[http://planet.sugarlabs.org planet.sugarlabs.org].</span>)

</noinclude>
== Sugar Digest ==

1. Marvin Minsky was fond of saying that there is nothing more dangerous than when a roomful of people all agree with each other. We don't have to worry about that in the Sugar community!!! Marvin also observed that "it's very important to have friends who can solve problems you can't." The diversity of our community is its strength.

Another Marvin quote relevant to our current quest to define ourselves as a community: "Our present culture may be largely shaped by this strange idea of isolating children's thought from adult thought. Perhaps the way our culture educates its children better explains why most of us come out as dumb as they do, than it explains how some of us come out as smart as they do." As Laura Vargas put it recently, Sugar Labs is a community "where you can learn how to design, develop and deploy high-quality Free Software." Within our community, children and adults are working together.

2. Sam Parkinson is our new release manager. Sam, a former GCI winner from Australia, has been responsible for many of the patches to the Sugar toolkit over the past few releases and has also been one of our most prelific code reviewers. Martin Abente, our release manager for the past four releases, has agreed to mentor Sam during the transition. Tip of the hat to Martin for all of his contributions and continued support.

3. Mariah Noelle Villarreal just got back from the Google Code-in reunion, where she represented Sugar Labs. She had a chance to meet Ezequiel and Piotr, our two winners, and spend time with members of the other participating projects. Mariah brought multiple copies of Sugar on a Stick to hand out and reports that there was a positive reception, especially among some of the parents in attendance. She also voiced some disappointment with the degree of awareness of Software Libre among attendees. FWIW, Devin Ulibarri and I are working on a new paper regarding the importance of Software Libre to education. Stay tuned.

4. I just got back from a trip to Santiago, Chile, where I was hosted by the education division of Fundación Chile. (Cecilia Rodriguez Alcala Garcia, formally of Educa Paraguay, was responsible for my invitation to run some workshops and give a keynote address at Creo Chile.) The theme of my workshops was programming as a vehicle for engaging in critical thinking. I introduced Turtle Blocks and Music Blocks first to a team of engineers from throughout the foundation, then to an executive group, then to a "hacker" group attending the Creo Chile event, and finally to a group of children and their parents. I was assisted by Andrea Vasquez Garcia, without whom I would have been lost. In addition, I participated in a workshop run by a local rap artist, Nelson Bobadilla Alvarado, and an educator, Francisca Petrovich Ursic. We did a collaborative, interactive Music Blocks program, whereby we could programmatically participate in the performance. A bit crude, but I learned a lot in the process. My keynote, which I have uploaded to [[File:FchBender2016.pdf]], focused on Sugar and the role of Software Libre in education.

In the workshop for executives, I was challenged to write a Turtle program to calculate the expected value of the number of coin flips required to get three heads or three tails in a row. My response can be seen at [http://walterbender.github.io/turtleblocksjs/?file=threeinarow.tb].

One sub-goal of my trip was to seek advice regarding a reference machine for Sugar. Alas, I was not yet able to get a definitive answer, as the foundation does not directly distribute hardware and the ministry of education has a wide variance in the types of machines they distribute. But I hope to get some feedback on this topic in the coming weeks.

While I was in Santiago, Chile defeated Mexico in the Copa América. I credited the win to Sugar (and the Chilean futbol shirt I was wearing). Hopefully it will mean that Sugar will find a warn reception in Chile.

5. Google Summer of Code is well underway. Mentors are writing mid-term evaluations this week. Be sure to check out the great work being done by our interns, including [https://github.com/sugarlabs/edit-fonts-activity], [http://vikramahujagsoc.blogspot.in/], [https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/313#discussion_r63140566], [http://musicblocks.net/2016/06/13/multiple-rhythm-rulers/], [https://www.youtube.com/watch?v=FAHUOBJ7fqk], and [https://iamutkarshtiwari.wordpress.com/].

6. On the flight back from Santiago, I wrote a Python script to convert glif files into Turtle Block projects. (Tip of the hat to Eli Heuer for providing me some sample glif files.) The results are quite fun (See [http://walterbender.github.io/musicblocks/?file=a.tb]). Next up, a version where each knot and control point is represented by a turtle, and thus the glyph will be editable.

=== In the Community ===

7. Gary Stager has written a nice [https://www.edsurge.com/news/2016-06-07-as-the-maker-movement-turns-45-gary-stager-pays-tribute-to-m-i-t-computing-pioneer-cynthia-solomon tribute to Cynthia Solomon] in celebration of the 45th anniversary of the Maker Movement.

8. Our next [[Oversight_Board#Next_meeting|oversight board meeting]] is [http://www.timeanddate.com/countdown/generic?iso=20160701T15&p0=43&msg=SLOB+meeting Friday, 1 July at 19:00 UTC]. Please join us on irc.freenode.net #sugar-meeting.

=== Tech Talk ===

9. Sam has announced the second release leading up to Sugar 0.110. Recent changes include:
* James Cameron fixed Gtk 3.6 compatibility and an edge case with bundle erasure
* Utkarsh Tiwari added a WiFi password visibility toggle
* Abhijit Patel added a PopWindow api for sugar toolkit
* Sebastian Silva fixed Broadway compatibility for `sugar-activity`
* The [http://wiki.sugarlabs.org/go/Features/Tick_based_animation smooth animations feature] landed
* Git submodules are now supported by the bundlebuilder
* Improved Gtk 3.20 support
* Misc bug/interface fixes

Sam has been busy updating the [https://developer.sugarlabs.org/sugar3/sugar3.graphics.icon.html API documentation] and is soliciting feedback. Also, San has updated Fedora [https://copr.fedorainfracloud.org/coprs/samtoday/sugar/ COPR] with the new versions of the Sugar packages. Tarballs for sugar, sugar-toolkit-gtk3 and sugar-artwork are in the usual places on the download server [http://download.sugarlabs.org/sources/sucrose/glucose/].

10. Tom Gilliard reports the availability of Sugar spins for Fedora24 ([http://dl.fedoraproject.org/pub/alt/unofficial/releases/24/x86_64/Fedora-SoaS-Live-x86_64-24-20160614.n.0.iso x86_64], [http://dl.fedoraproject.org/pub/alt/unofficial/releases/24/i386/Fedora-SoaS-Live-i386-24-20160614.n.0.iso i386]).

=== Sugar Labs ===

11. Please visit our [http://planet.sugarlabs.org planet].

<noinclude>

== Community News archive ==

An '''[[Archive/Current Events|archive]]''' of this digest is available.

==Planet==

<span class="plainlinks">The Sugar Labs [http://planet.sugarlabs.org/ Planet] is found [http://planet.sugarlabs.org/ here].</span>

==Sugar in the news==
{|
|-
|align=right valign=top|23 Jul 2016||'''La Tercera''' – [http://www.tendencias.com/2016/07/27-689886-9-walter-bender-cuando-todos-estan-de-acuerdo-con-todos-es-bastante-peligroso.shtml Cuando todos están de acuerdo con todos es bastante peligroso]
|-
|align=right valign=top|02 May 2016||'''Fedora Insider''' – [http://www.linuxinsider.com/story/Fedora-Based-Sugar-on-a-Stick-Is-One-Sweet-Desktop-83446.html Fedora-based Sugar on a Stick is one sweet desktop]
|-
|align=right valign=top|09 Feb 2016||'''www.montevideo.com''' – [http://www.montevideo.com.uy/auc.aspx?299096 DOS URUGUAYOS ENTRE GANADORES DEL CONCURSO GOOGLE CODE-IN]
|-
|align=right valign=top|28 Aug 2015||'''Musson Foundation''' – [https://youtu.be/HZtVv2nlP8Y Jamaica Girls Code] (video)
|-
|align=right valign=top|28 Aug 2015||'''Google Open Source''' – [http://google-opensource.blogspot.com/2015/08/my-sweet-adventures-with-sugar-labs-and.html My sweet adventures with Sugar Labs and Google Code-in]
|-
|align=right valign=top|09 May 2015||'''La Prensa''' – [http://www.laprensa.com.ni/2015/05/09/nacionales/1829026-de-alumnos-a-creadores-de-su-aprendizaje De alumnos a creadores de su aprendizaje]
|-
|align=right valign=top|30 Apr 2015||'''Diario La República''' – [http://www.republica.com.uy/investigador-sueco-visito-uruguay-para-conocer-el-proyecto-butia/514419/ Swedish researcher visited Uruguay to meet the project Butiá]
|-
|align=right valign=top|24 Apr 2015||'''Jamaica Observer''' – [http://www.jamaicaobserver.com/magazines/career/Future-coders_18811152 Future Coders]
|-
|align=right valign=top|24 Apr 2015||'''Jamaica Information Service''' – [http://jis.gov.jm/state-minister-urges-young-women-enter-ict-sector/ State minister urges young women to enter ICT sector]
|-
|align=right valign=top|6 Feb 2015||'''Cromo''' – [http://www.cromo.com.uy/2015/02/el-chico-google/ El chico Google]
|-
|align=right valign=top|5 Feb 2015||'''Capital Noticias Canelones''' – [https://www.google.com/url?q=https%3A%2F%2Fwww.facebook.com%2Fvideo.php%3Fv%3D400864146741913%26set%3Dvb.246080195553643%26type%3D2%26theater&sa=D&sntz=1&usg=AFQjCNFGeMoL69EHGf4Kudmoxo47duJf_Q El joven de Canelones, Ignacio Rodríguez, ganó nuevamente la competencia de programación de Google.] (video)
|-
|align=right valign=top|3 Feb 2015||'''montevideo.com''' – [http://www.montevideo.com.uy/auc.aspx?261076 Código joven]
|-
|align=right valign=top|1 Dec 2014||'''Google Open Source Blog''' – [http://google-opensource.blogspot.com/2014/12/3-2-1-code-in-inviting-teens-to.html 3, 2, 1 Code-in: Inviting teens to contribute to open source]
|-
|align=right valign=top|7 Oct 2014||'''Kauffman Report''' – [http://www.kauffman.org/blogs/policy-dialogue/2014/august/paraguay-thirsty-for-21st-century-education Paraguay Thirsty for 21st-Century Education]
|-
|align=right valign=top|25 Sept 2014||'''ANEP''' – [http://www.anep.edu.uy/anep/index.php/897-fecundo-intercambio-de-jovenes-de-todo-el-mundo-en-encuentro-de-programadores Fecundo intercambio de jovenes de todo el mundo en encuentro de programadores]
|-
|align=right valign=top|12 Jun 2014||'''Producción Nacional''' – [https://www.youtube.com/watch?v=0YbRCMRpstg Innovando con XO] (video)
|-
|align=right valign=top|28 Apr 2014||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/suplementos/centinela/paraguay-educa-realiza-talleres-de-programacion-y-de-robotica-1238493.html Paraguay Educa realiza talleres de programación y de robótica]
|-
|align=right valign=top|21 Apr 2014||'''El Tiempo''' – [http://www.eltiempo.com/vida-de-hoy/educacion/entrevista-de-el-tiempo-a-walter-bender_13855020-4 'Cada niño podría ser un maestro del 'software': Walter Bender]
|-
|align=right valign=top|2 Apr 2014||'''vera.tv''' – [http://tv.vera.com.uy/video/7012 Antel vuelta a clases] (video)
|-
|align=right valign=top|4 Feb 2014||'''La Diaria''' – [http://ladiaria.com.uy/articulo/2014/2/en-codigo/ En código]
|-
|align=right valign=top|24 Jan 2014||'''Espectador''' – [http://www.espectador.com/sociedad/283177/entre-los-ganadores-del-concurso-anual-de-programacion-de-google-code-in-hay-nuevamente-un-joven-uruguayo Entre los ganadores del concurso anual de programación de Google Code-in hay nuevamente un joven uruguayo]
|-
|align=right valign=top|23 Jan 2014||'''El Pais''' – [http://www.elpais.com.uy/vida-actual/ensena-profesores-ahora-premia-google.html Le enseña a sus profesores y ahora lo premia Google]
|-
|align=right valign=top|20 Jan 2014||'''Google Open Source Blog''' – [http://google-opensource.blogspot.com/ Google Code-in 2013 - drumroll please!]
|-
|align=right valign=top|28 Nov 2013||'''BBVA Paraguay''' – [http://www.youtube.com/watch?v=y_wTBs2ektI&feature=youtu.be&utm_source=buffer&utm_campaign=Buffer&utm_content=bufferbac3c&utm_medium=twitter Turtle Art Day in Caacupé] (video)
|-
|align=right valign=top|17 Oct 2013||'''ANTEL Integra''' – [http://www.integra.antel.com.uy/2013/10/educacion/turtle-art-la-plataforma-del-butia/ Turtle Art: la plataforma del Butiá]
|-
|align=right valign=top|14 Oct 2013||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/locales/software-libre-es-tema-de-paneles-en-la-cumbre-627064.html Software libre es tema de paneles en la cumbre]
|-
|align=right valign=top|14 Oct 2013||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/locales/programar-ayuda-a-los-ninos-a-pensar-628059.html Programar ayuda a los niños a pensar]
|-
|align=right valign=top|14 Oct 2013||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/locales/hoy-es-el-dia-de-tortugarte-en-caacupe-627470.html Hoy es el Día de TortugArte, en Caacupé]
|-
|align=right valign=top|14 Oct 2013||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/locales/las-tic-en-la-educacion-son-clave-para-el-desarrollo-del-pais-aseguran-627469.html Las TIC en la educación son clave para el desarrollo del país, aseguran]
|-
|align=right valign=top|12 Oct 2013||'''Cromo''' – [http://www.cromo.com.uy/2013/10/mhijo-el-programador/ M’hijo el programador]
|-
|align=right valign=top|08 Aug 2013||'''News1''' – [http://news1.kr/articles/1273059 Interview with former MIT Media Lab director] (in Korean)
|-
|align=right valign=top|12 Jul 2013||'''RIT''' – [http://www.rit.edu/news/story.php?id=50113 ‘Sky Time’ video game selected for White House Champions of Change event July 23]
|-
|align=right valign=top|28 Apr 2013||'''BBC Mundo''' – [http://www.bbc.co.uk/mundo/noticias/2013/04/130422_programadores_adolescentes_am.shtml Los programadores adolescentes premiados por Google]
|-
|align=right valign=top|07 Feb 2013||'''el Neuvo Herald''' – [http://www.elnuevoherald.com/2013/02/07/1402134/joven-uruguayo-brilla-como-programador.html Joven uruguayo brilla como programador y es distinguido por Google]
|-
|align=right valign=top|06 Feb 2013||'''el Observador''' – [http://www.elobservador.com.uy/noticia/242936/joven-uruguayo-gana-la-competencia-google-code/ Joven uruguayo gana la competencia Google Code] (Also see [http://people.sugarlabs.org/aguz/gci-press-interviews.html GCI press interviews])
|-
|align=right valign=top|07 Sep 2012||'''NDTV''' – [http://gadgets.ndtv.com/laptops/news/one-laptop-per-child-initiative-a-hit-in-rural-india-263867 One Laptop Per Child initiative a hit in rural India]
|-
|align=right valign=top|08 Jul 2012||'''Estado de S. Paulo''' – [http://blogs.estadao.com.br/radar-tecnologico/2012/07/08/para-educar/ Para educar]
|-
|align=right valign=top|24 Apr 2012||'''Pacific Standard''' – [http://www.psmag.com/education/one-laptop-per-child-redux-38589/ OLPC Redux]
|-
|align=right valign=top|12 Apr 2012||'''Huffington Post''' – [http://www.huffingtonpost.com/ketaki-desai/one-laptop-per-child_b_1417801.html Hult Global Case Challenge: One Laptop Per Child]
|-
|align=right valign=top|30 Mar 2012||'''newswise''' – [http://www.newswise.com/articles/sugar-on-a-stick-helps-kids-learn-how-to-learn “Sugar on a Stick” Helps Kids Learn How to Learn]
|-
|align=right valign=top|11 Jan 2012||'''Boston Herald''' – [http://bostonherald.com/business/technology/general/view.bg?articleid=1394672 One Laptop Per Child screening $100 tablet]
|-
|align=right valign=top|10 Jan 2012||'''ars technica''' – [http://arstechnica.com/gadgets/news/2012/01/charging-by-crank-bicycle-waterwheel-hands-on-with-the-olpc-xo-30-tablet.ars Crank, bicycle, and waterwheel: hands-on with the OLPC XO 3.0 tablet]
|-
|align=right valign=top|08 Jan 2012||'''The Verge''' – [http://www.theverge.com/2012/1/8/2691733/olpc-xo-3-0-tablet-pictures-video OLPC XO 3.0 tablet preview: impressions, video, and pictures]
|-
|align=right valign=top|07 Jan 2012||'''The Verge''' – [http://www.theverge.com/2012/1/6/2688604/olpc-xo-3-0-tablet-a-8-inch-tablet-with-android-and-sugar-options-for OLPC XO 3.0 tablet: an 8-inch tablet for $100, with Android and Sugar options for the children]
|-
|align=right valign=top|23 Dec 2011||'''Miller-McCune''' – [http://www.miller-mccune.com/education/one-laptop-per-child-redux-38589/ One Laptop Per Child Redux]
|-
|align=right valign=top|18 Oct 2011||'''BDU''' – [http://www.youtube.com/watch?v=IcpzVnuFP0M&feature=channel_video_title Robotics in Uruguay] (video)
|-
|align=right valign=top|11 Aug 2011||'''Berlin.de''' – [http://www.berlin.de/projektzukunft/presse/aktuelle-pressemitteilung/detailseite/datum/2011/08/08/gewinner-des-berliner-landeswettbewerbs-zu-open-source-stehen-fest/ Gewinner des Berliner Landeswettbewerbs zu Open Source stehen fest]
|-
|align=right valign=top|25 Jul 2011||'''CCC Classic''' – [http://wiki.sugarlabs.org/go/File:CCC-StartingLine.jpg Garmin-sugarlabs development cycling team at Crit starting line]
|-
|align=right valign=top|25 Jul 2011||'''CCC Classic''' – [http://wiki.sugarlabs.org/go/File:CCC-after.jpg Garmin-sugarlabs development cycling team after Crit]
|-
|align=right valign=top|13 Apr 2011||'''framablog''' – [http://www.framablog.org/index.php/post/2011/04/13/sugar-labs-education-walter-bender L'expérience Sugar Labs préfigure-t-elle une révolution éducative du XXIe siècle?]
|-
|align=right valign=top|05 Apr 2011||'''Businesswire''' – [http://www.businesswire.com/news/home/20110405006842/en/Government-Peru-Expands-Laptop-Child-Program-Local The Government of Peru Expands the One Laptop Per Child Program with Local Manufacturing]
|-
|align=right valign=top|31 Jan 2011||'''Sundance''' – [http://www.youtube.com/watch?v=ABp7GkLgN94 A Day in the Life – Peru]
|-
|align=right valign=top|01 Dec 2010||'''velonation''' – [http://www.velonation.com/News/ID/6564/Sugar-Labs-to-back-Garmin-Cervelos-development-team-in-unique-arrangement.aspx Sugar Labs to back Garmin-Cervelo’s development team in unique arrangement]
|-
|align=right valign=top|28 Oct 2010||'''UCR''' – [http://www.ucr.ac.cr/noticias/2010/10/28/nuevas-tecnologias-deben-estar-al-alcance-de-todos-los-ninos-y-ninas.html Nuevas tecnologías deben estar al alcance de todos los niños y niñas]
|-
|align=right valign=top|05 Oct 2010||'''xconomy''' – [http://www.xconomy.com/boston/2010/10/05/one-ecosystem-per-child-walter-bender-and-olpc-reunite-to-enhance-learning-and-grow-economies-in-developing-nations/#comments One Ecosystem per Child]
|-
|align=right valign=top|08 Sep 2010||'''FLOSS Weekly''' – [http://twit.tv/floss134 Sugar Labs]
|-
|align=right valign=top|09 Aug 2010||'''ABC digital''' – [http://www.abc.com.py/abc/nota/165361-Indicadores-constatan-el-impacto-positivo-en-el-aprendizaje-de-ninos/ Indicadores constatan el impacto positivo en el aprendizaje de niños]
|-
|align=right valign=top|23 Jun 2010||'''ABC digital''' – [http://www.abc.com.py/abc/nota/137383-Xo-para-todas-las-escuelas-de-Caacup%C3%A9/ Xo para todas las escuelas de Caacupé]
|-
|align=right valign=top|21 Jun 2010||'''La Nacion''' – [http://www.lanacion.com.py/noticias_um-312380.htm “Buscamos que los niños no solo usen softwares, sino que puedan crear uno”]
|-
|align=right valign=top|20 Jun 2010||'''UltimaHora.com''' – [http://www.ultimahora.com/notas/332297-La-laptop-une-a-padres,-alumnos-y-docentes La laptop une a padres, alumnos y docentes]
|-
|align=right valign=top|15 Jun 2010||'''The H''' – [http://www.h-online.com/open/news/item/OLPC-XO-1-5-software-updated-1022936.html OLPC XO-1.5 software updated]
|-
|align=right valign=top|10 Jun 2010||'''engadget''' – [http://www.engadget.com/2010/06/11/sugar-on-a-stick-hits-3-0-teaches-us-about-a-new-kind-of-fruit/ Sugar on a Stick hits 3.0, teaches us about a new kind of fruit]
|-
|align=right valign=top|27 May 2010||'''Pro Linux DE''' – [http://www.pro-linux.de/news/1/15722/sugar-on-a-stick-v3-freigegeben.html Sugar on a Stick v3 freigegeben] (German)
|-
|align=right valign=top|27 May 2010||'''NY Times''' – [http://bits.blogs.nytimes.com/2010/05/27/olpc-partners-with-marvell-to-launch-100-tablet/?src=busln One Laptop Per Child Project Works With Marvell to Produce a $100 Tablet]
|-
|align=right valign=top|27 May 2010||'''PC World''' – [http://www.pcworld.com/businesscenter/article/197361/olpc_rules_out_windows_for_xo3.html OLPC Rules out Windows for XO-3]
|-
|align=right valign=top|03 May 2010||'''WXXI: Mixed Media''' – [http://www.publicbroadcasting.net/wxxi/news.newsmain/article/0/0/1644648/news/Mixed.Media.Special.Edition.05-03-10 Interview with Walter Bender] (audio)
|-
|align=right valign=top|03 May 2010||'''Linux Magazine''' – [http://www.linux-magazine.com/Online/News/OLPC-Computers-for-Palestinian-Refugee-Children OLPC Computers for Palestinian Refugee Children]
|-
|align=right valign=top|14 Apr 2010||'''National Science Foundation''' – [http://www.nsf.gov/discoveries/disc_summ.jsp?cntn_id=116638 XO Laptops Inspire Learning In Birmingham, Alabama] ([http://www.nsf.gov/cgi-bin/good-bye?http://www.youtube.com/watch?v=inxOg-dt6rw video])
|-
|align=right valign=top|02 Apr 2010||<div class="NavFrame collapsed"><div class="NavHead">'''Dailymotion''' – [http://www.dailymotion.com/video/xct0lp_un-jour-a-paris-ensembles-pour-olpc_tech Un jour... à Paris... ensembles pour OLPC et Sugar...] (video) </div><div class="NavContent">{{#widget:Daily Motion
|id=xct0lp
|width=420
|height=336
}}</div></div>
|-
|align=right valign=top|15 Mar 2010||'''nbc13.com''' – [http://www2.nbc13.com/vtm/news/local/article/video_birmingham_city_students_opt_to_spend_spring_break_in_class_xo_comput/138224/ Birmingham City students opt to spend spring break in class, XO computer camps] (video)
|-
|align=right valign=top|18 Feb 2010||'''LWN''' – [https://lwn.net/SubscriberLink/374790/8dc41b030f4562b1/ Karma targets easier creation of educational software]
|-
|align=right valign=top|05 Feb 2010||'''iprofesional''' – [http://tecnologia.iprofesional.com/notas/93943-La-PC-barata-de-Negroponte-desembarca-en-la-Argentina-para-pelear-contra-Intel.html La PC barata de Negroponte desembarca en la Argentina para pelear contra Intel]
|-
|align=right valign=top|14 Jan 2010||'''AALF''' – [http://www.aalf.org/articles/view.php?ArticleID=86 Open Systems for Broader Change]
|-
|align=right valign=top|03 Jan 2010||'''Educacion 2.0''' – [http://www.educdoscero.com/2009/12/plan-ceibal-el-libro.html PLAN CEIBAL, El Libro]
|-
|align=right valign=top|14 Dec 2009||'''xconomy''' – [http://www.xconomy.com/boston/2009/12/14/sugar-gets-sweeter-former-olpc-exec-walter-bender-on-netbooks-e-books-blueberry-and-cloudberry/?single_page=true Sugar gets sweeter]
|-
|align-right valign=top|10 Dec 2009||'''ars technica''' – [http://arstechnica.com/open-source/reviews/2009/12/sugar-software-environment-gets-sweeter-with-version-2.ars Sugar software environment gets sweeter with version 2]
|-
|align=right valign=top|09 Dec 2009||'''Wired''' – [http://www.wired.com/geekdad/2009/12/new-sugar-on-a-stick-brings-much-needed-improvements/ New Sugar on a Stick Brings Much Needed Improvements]
|-
|align=right valign=top|08 Dec 2009||'''engadget''' – [http://www.engadget.com/2009/12/08/sugar-on-a-stick-os-goes-to-2-0-gets-blueberry-coating-and-crea/ Sugar on a Stick OS goes to 2.0, gets Blueberry coating and creamy Fedora 12 center (video)]
|-
|align=right valign=top|07 Dec 2009||'''Teleread.org''' – [http://www.teleread.org/2009/12/07/sugar-on-a-stick-what-it-means-for-e-books-and-education/ Sugar on a Stick: What it means for e-books and education]
|-
|align=right valign=top|27 Nov 2009||'''CNET Japan''' – [http://japan.cnet.com/special/story/0,2000056049,20404126,00.htm 「コードを見せて、もっと良くなるよ」と言える子どもが生まれる--Sugar Labsが描く未来]
|-
|align=right valign=top|16 Nov 2009||'''zanichelli''' – [http://scienze.zanichelli.it/notizie/2009/11/16/intervista-walter-bender-e-sugar-labs/ software libero a scuola]
|-
|align=right valign=top|12 Nov 2009||'''opensuse.org''' – [http://en.opensuse.org/Marketing/Team/11_2_Launch/Announcement openSUSE 11.2 Released]
|-
|align=right valign=top|07 Nov 2009||'''My Broadband News''' – [http://mybroadband.co.za/news/Software/10351.html Mandriva 2010 packs a punch [and Sugar]]
|-
|align=right valign=top|06 Nov 2009||'''GhanaWeb''' – [http://www.ghanaweb.com/GhanaHomePage/NewsArchive/artikel.php?ID=171387 Open education and an IT-enabled economic growth in Ghana: Musings of a dutiful citizen]
|-
|align=right valign=top|26 Oct 2009||'''Linux Magazine ES''' – [http://www.linux-magazine.es/issue/54/078-083_SugarLM54.pdf Software Libre como apoyo al aprendizaje]
|-
|align=right valign=top|09 Oct 2009||'''interdisciplines''' – [http://www.interdisciplines.org/mobilea2k/papers/2 OLPC and Sugar: mobility through the community]
|-
|align=right valign=top|08 Oct 2009||'''IBM developerWorks''' – [http://www.ibm.com/developerworks/linux/library/l-linux-10th-anniversary/index.html 10 important Linux developments everyone should know about]
|-
|align=right valign=top|01 Oct 2009||'''OLPC France''' – [http://olpc-france.org/wiki/index.php?title=Interview_Walter_Bender_au_SugarCamp Interview Walter Bender au SugarCamp]
|-
|align=right valign=top|25 Sep 2009||'''The Inquirer''' – [http://www.theinquirer.net/inquirer/news/1555781/one-laptop-per-child-marches One Laptop per Child marches on]
|-
|align=right valign=top|18 Sep 2009||'''Groklaw''' – [http://www.groklaw.net/article.php?story=20090918110925298 The Role of Free Software in Education]
|-
|align=right valign=top|18 Sep 2009||'''Reuters''' – [http://www.reuters.com/article/pressRelease/idUS97755+18-Sep-2009+PRN20090918 Sugar Labs and Free Software Foundation Celebrate Software Freedom Day]
|-
|align=right valign=top|17 Sep 2009||'''ICTDev.org''' – [http://ictdev.org/pulse/20090916/ict4d/dreaming-again-one-laptop-child Dream Again with One Laptop per Child]
|-
|align=right valign=top|26 Aug 2009||'''Latinux''' – [http://www.latinuxmagazine.com/ediciones/pdf/latinux-magazine-VolINum1-beta.pdf Azúcar en una memoria USB]
|-
|align=right valign=top|03 Aug 2009||'''Wired: Geek Dad''' – [http://www.wired.com/geekdad/2009/08/inventing-a-new-paradigm-sugarlabs-and-the-sugar-ui/ Inventing a New Paradigm: SugarLabs and the Sugar UI]
|-
|align=right valign=top|30 Jul 2009||'''Zanichelli''' – [http://scienze.zanichelli.it/notizie/2009/06/30/sugar-on-a-stick-imparare-insieme/ Sugar on a Stick: imparare insieme]
|-
|align=right valign=top|23 Jul 2009||'''Everything USB''' – [http://www.everythingusb.com/recycle-usb-17077.html RecycleUSB.com - Donate your Flash Drives for a Good Cause]
|-
|align=right valign=top|22 Jul 2009||'''OLPC France''' – [http://olpc-france.org/blog/2009/07/sugar-mauvaise-presse-et-mise-au-point/ Sugar : mauvaise presse et mise au point]
|-
|align=right valign=top|13 Jul 2009||'''Spiegel Online''' – [http://www.spiegel.de/netzwelt/tech/0,1518,634718,00.html Das zuckersüße Leichtbau-Linux]
|-
|align=right valign=top|07 Jul 2009||'''ComputerWorldUK''' – [http://www.computerworlduk.com/community/blogs/index.cfm?entryid=2334&blogid=14 Gran Canaria Desktop Summit: a Study in Contrasts]
|-
|align=right valign=top|06 Jul 2009||'''Windows Forest''' – [http://www.forest.impress.co.jp/article/2009/06/30/olpcusb.html USBメモリなどから“OLPC”用のOSを利用できる「Sugar on a Stick」が無償公開]
|-
|align=right valign=top|02 Jul 2009||'''Howard County Library''' – [http://hclibrary.org/opensource/?p=228 Sugar on a Stick]
|-
|align=right valign=top|27 Jun 2009||'''Deutschlandfunk''' – [http://www.dradio.de/dlf/sendungen/computer/989765/ Süßes für die Kleinen: Sugar ist Linux speziell für Kinder] (in Deutsch)
|-
|align=right valign=top|26 Jun 2009||'''EduTech''' – [http://blogs.worldbank.org/edutech/sugar-on-a-stick-and-other-delectables-praise-for-the-lowly-usb-drive Sugar on a stick, and other delectables (praise for the lowly USB drive)]
|-
|align=right valign=top|26 Jun 2009||'''ars technica''' – [http://arstechnica.com/open-source/news/2009/06/sugar-on-a-stick-brings-sweet-taste-of-linux-to-classrooms.ars Sugar on a Stick brings sweet taste of Linux to classrooms]
|-
|align=right valign=top|24 Jun 2009||'''BBC''' – [http://news.bbc.co.uk/2/hi/technology/8117064.stm OLPC software to power aging PCs]
|-
|align=right valign=top|24 Jun 2009||'''Technology Review''' – [http://www.technologyreview.com/computing/22919/ $100 Laptop Becomes a $5 PC]
|-
|align=right valign=top|15 Jun 2009||'''TechSavvyKids''' – [http://techsavvykids.podomatic.com/player/web/2009-06-15T11_15_29-07_00 Episode 10 FOSSVT: Sugar on a Stick] (audio)
|-
|align=right valign=top|10 Jun 2009||'''LWN.net''' – [http://lwn.net/SubscriberLink/336910/3878a88c0c27f977/ Sugar moves from the shadow of OLPC]
|-
|align=right valign=top|27 May 2009||'''LWN.net''' – [http://lwn.net/SubscriberLink/334911/cf451c615cfdaa33/ Activities and the move to context-oriented desktops] (subscriber link)
|-
|align=right valign=top|27 May 2009||'''Business Wire''' – [http://www.businesswire.com/portal/site/home/permalink/?ndmViewId=news_view&newsId=20090527006237&newsLang=en Dailymotion Launches Support for Open Video Formats and Video HTML Tag]
|-
|align=right valign=top|01 May 2009||'''Guysoft''' – [http://guysoft.wordpress.com/2009/05/01/nokia-n810-running-olpc-sugar/ Nokia N810 Running OLPC Sugar]
|-
|align=right valign=top|29 Apr 2009||'''El Mercurio''' – [http://www.mer.cl/modulos/catalogo/Paginas/2009/04/29/MERSTVS017AA2904.htm?idnoticia=CC116HNVJ120090429 Así se vivió la fiesta del software libre]
|-
|align=right valign=top|27 Apr 2009||'''ostatic''' – [http://ostatic.com/blog/sugar-on-a-stick-good-for-kids-minds-and-school-budgets Sugar on a Stick: Good for Kids' Minds (and School Budgets)]
|-
|align=right valign=top|25 Apr 2009||'''Free Software Magazine''' – [http://www.freesoftwaremagazine.com/columns/bittersweet_facts_about_olpc_and_sugar The Bittersweet Facts about OLPC and Sugar]
|-
|align=right valign=top|24 Apr 2009||'''ars technica''' – [http://arstechnica.com/open-source/news/2009/04/sugar-labs-releases-beta-of-live-usb-learning-environment.ars First taste: Sugar on a Stick learning platform]
|-
|align=right valign=top|22 Apr 2009||'''Betanews''' – [http://www.betanews.com/article/Beta-of-Live-USB-Sugar-OS-opens/1240409113#talkback Beta of Live USB Sugar OS opens]
|-
|align=right valign=top|27 Mar 2009||'''Mass High Tech''' – [http://www.masshightech.com/stories/2009/03/23/weekly3-Google-promotes-summer-open-source-internships.html Google promotes summer open-source internships]
|-
|align=right valign=top|18 Mar 2009||'''Metropolis''' – [http://www.metropolismag.com/story/20090318/a-good-argument A Good Argument]
|-
|align=right valign=top|16 Mar 2009||'''Laptop Magazine''' – [http://blog.laptopmag.com/sugar-labs-new-version-of-sugar-learning-platform-is-netbook-and-pc-ready Sugar Labs’ New Version of Sugar Learning Platform Is Netbook and PC Ready]
|-
|align=right valign=top|16 Mar 2009||'''Market Watch''' – [http://www.marketwatch.com/news/story/sugar-labs-nonprofit-announces-new/story.aspx?guid={EF4B8934-0046-465F-AD4D-E82FBCE8F1EC}&dist=msr_7 Sugar Labs Nonprofit Announces New Version of Sugar Learning Platform for Children, Runs on Netbooks and PCs]
|-
|align=right valign=top|14 Feb 2009||'''OLPC Learning Club – DC''' – [http://olpclearningclub.org/meetings/learning-learning-on-a-stick/ Learning Learning on a Stick]
|-
|align=right valign=top|05 Feb 2009||'''xconomy''' – [http://www.xconomy.com/boston/2009/02/05/sugar-beyond-the-xo-laptop-walter-bender-on-olpc-sucrose-084-and-sugar-on-a-stick/ Sugar Beyond the XO Laptop: Walter Bender on OLPC, Sucrose 0.84, and “Sugar on a Stick”]
|-
|align=right valign=top|26 Jan 2009||'''Linus Magazine''' – [http://www.linux-magazine.com/content/view/full/32999 Sugar Defies OLPC Cutbacks]
|-
|align=right valign=top|19 Jan 2009||'''Feeding the Penguins''' – [http://morgancollett.wordpress.com/2009/01/19/the-status-of-sugar-post-olpc/ The status of Sugar, post-OLPC]
|-
|align=right valign=top|16 Jan 2009||'''OLPC News''' – [http://www.olpcnews.com/software/sugar/xo_acer_aspire_one_thin_client_sugar.html Sugar on Acer Aspire One & Thin Client via LTSP]
|-
|align=right valign=top|12 Jan 2009||'''Bill Kerr''' – [http://billkerr2.blogspot.com/2009/01/thoughts-about-olpc-cutbacks.html thoughts about olpc cutbacks]
|-
|align=right valign=top|07 Jan 2009||'''ars technica''' – [http://arstechnica.com/news.ars/post/20090107-olpc-downsizes-half-of-its-staff-cuts-sugar-development.html OLPC downsizes half of its staff, cuts Sugar development]
|-
|align=right valign=top|06 Jan 2009||'''OLPC News''' – [http://www.olpcnews.com/sales_talk/microsoft/how_microsoft_got_xp_on_the_xo.html An Inside Look at how Microsoft got XP on the XO]
|-
|align=right valign=top|30 Dec 2008||'''OLPC News''' – [http://www.olpcnews.com/software/sugar/sugar_labs_status_at_six_month.html Sugar Labs Status at Six Months]
|-
|align=right valign=top|22 Dec 2008||'''The GNOME Project''' – [http://www.gnome.org/press/releases/2008-12-sugarlabs.html Sugar Labs, the nonprofit behind the OLPC software, is joining the GNOME Foundation]
|-
|align=right valign=top|16 Dec 2008||'''Feeding the Penguins''' – [http://morgancollett.wordpress.com/2008/12/15/sugar-git-repository-change/ Sugar git repository change]
|-
|align=right valign=top|14 Dec 2008||'''NPR''' – [http://www.npr.org/templates/story/story.php?storyId=96825852 Laptop Deal Links Rural Peru To Opportunity, Risk (Part 2)]
|-
|align=right valign=top|13 Dec 2008||'''NPR''' – [http://www.npr.org/templates/story/story.php?storyId=96510072 Laptops May Change The Way Rural Peru Learns (Part 1)]
|-
|align=right valign=top|09 Dec 2008||'''SFC''' – [http://conservancy.softwarefreedom.org/news/2008/dec/09/sugar/ Sugar Labs joins Conservancy]
|-
|align=right valign=top|31 Oct 2008||'''Linux Devices''' – [http://www.linuxdevices.com/news/NS3023016259.html An OLPC dilemma: Linux or Windows?]
|-
|align=right valign=top|10 Oct 2008||'''Feeding the Penguin''' – [http://morgancollett.wordpress.com/2008/10/10/sugar-on-ubuntu/ Sugar on Ubuntu]
|-
|align=right valign=top|21 Sep 2008||'''Groklaw''' – [http://www.groklaw.net/article.php?story=20080920181151638 Interview with Walter Bender of Sugar Labs]
|-
|align=right valign=top|17 Sep 2008||'''Bill Kerr''' – [http://billkerr2.blogspot.com/2008/09/sugar-labs.html Sugar Labs]
|-
|align=right valign=top|16 Sep 2008||'''Open Source''' – [http://opensource.sfsu.edu/node/562 Sugar everywhere]
|-
|align=right valign=top|28 Aug 2008||'''OLPC News''' – [http://www.olpcnews.com/use_cases/education/an_answer_to_question_22.html An answer to Walter Bender's question 22]
|-
|align=right valign=top|20 Aug 2008||'''OLPC News''' – [http://www.olpcnews.com/software/operating_system/sugarizing_it_intel_classmate_2.html Sugarize it: Intel Classmate 2]
|-
|align=right valign=top|08 Aug 2008||'''Investor's Business Daily''' – [http://www.investors.com/Tech/TechExecQA.asp?artid=303074322503278 'Learning' Vs. Laptop Was Issue]
|-
|align=right valign=top|06 Aug 2008||'''OLPC News''' – [http://www.olpcnews.com/people/leadership/23_questions_on_technology_education.html Twenty-three Questions on Technology and Education]
|-
|align=right valign=top|18 Jul 2008||'''Bill Kerr''' – [http://billkerr2.blogspot.com/2008/07/evaluating-sugar-in-developed-world.html evaluating Sugar in the developed world]
|-
|align=right valign=top|28 Jun 2008||'''OLPC News''' – [http://www.olpcnews.com/software/sugar/cutting_edge_sugar_ui.html A Cutting Edge Sugar User Interface Demo]
|-
|align=right valign=top|18 Jun 2008||'''PC World''' – [http://www.pcworld.com/businesscenter/article/147265/olpc_spinoff_developing_ui_for_intels_classmate_pc.html OLPC Spin-off Developing UI for Intel's Classmate PC]
|-
|align=right valign=top|17 Jun 2008||'''Datamation''' – [http://itmanagement.earthweb.com/osrc/article.php/12068_3753376_1 If Business Succeeds with GNU/Linux, Why Not OLPC?]
|-
|align=right valign=top|11 Jun 2008||'''LinuxInsider''' – [http://www.linuxinsider.com/story/Sugar-Labs-Walter-Bender-on-the-Sweetness-of-Collaborative-Learning-63354.html The Sweetness of Collaborative Learning]
|-
|align=right valign=top|06 Jun 2008||'''Bill Kerr''' – [http://billkerr2.blogspot.com/2008/06/untangling-free-sugar-and.html untangling Free, Sugar, and Constructionism]
|-
|align=right valign=top|06 Jun 2008||'''Open Education''' – [http://www.openeducation.net/2008/06/03/walter-bender-discusses-sugar-labs-foundation/ Walter Bender Discusses Sugar Labs Foundation]
|-
|align=right valign=top|06 Jun 2008||'''BusinessWeek''' – [http://prod-blogs.businessweek.com/globalbiz/blog/globespotting/archives/2008/06/olpc_the_educat.html OLPC: The Educational Philosophy Controversy]
|-
|align=right valign=top|05 Jun 2008||'''Code Culture''' – [http://radian.org/notebook/distraction-machine The Distraction Machine]
|-
|align=right valign=top|05 Jun 2008||'''BusinessWeek''' – [http://www.businessweek.com/globalbiz/blog/globespotting/archives/2008/06/olpc_the_open-s.html OLPC: The Open-Source Controversy]
|-
|align=right valign=top|27 May 2008||'''The New York Times''' – [http://bits.blogs.nytimes.com/2008/05/27/why-walter-bender-left-one-laptop-per-child-edited-hold-for-wed-am/ Why Walter Bender Left One Laptop Per Child]
|-
|align=right valign=top|26 May 2008||'''ars technica''' – [http://arstechnica.com/news.ars/post/20080526-former-olpc-software-president-wants-to-expand-sugars-reach.html OLPC software maker splits from X0 hardware, goes solo]
|-
|align=right valign=top|22 May 2008||'''BetaNews''' – [http://www.betanews.com/article/Linux_startup_Sugar_Labs_in_informal_talks_with_four_laptop_makers/1211467857 Linux start-up Sugar Labs in informal talks with four laptop makers]
|-
|align=right valign=top|16 May 2008||'''OSTATIC''' – [http://ostatic.com/162220-blog/olpcs-open-source-sugar-platform-aims-for-new-hardware OLPC's Open Source Sugar Platform Aims for New Hardware]
|-
|align=right valign=top|16 May 2008||'''PCWorld''' – [http://www.pcworld.com/businesscenter/article/146002/bender_forms_group_to_promote_olpcs_sugar_ui.html Bender Forms Group to Promote OLPC's Sugar UI]
|-
|align=right valign=top|16 May 2008||'''MHT''' – [http://masshightech.bizjournals.com/masshightech/stories/2008/05/12/daily35.html Bender jumps from OLPC, founds Sugar Labs]
|-
|align=right valign=top|16 May 2008||'''News.com''' – [http://www.news.com/8301-10784_3-9946242-7.html Sugar Labs will make OLPC interface available for Eee PC, others]
|-
|align=right valign=top|16 May 2008||'''Feeding the Peguins''' – [http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/ The future of Sugar]
|-
|align=right valign=top|16 May 2008||'''Sugar list''' – [http://lists.laptop.org/pipermail/sugar/2008-May/005800.html A few thoughts on SugarLabs]
|-
|align=right valign=top|16 May 2008||'''xconomy''' – [http://www.xconomy.com/2008/05/16/bender-creates-sugar-labs-new-foundation-to-adapt-olpcs-laptop-interface-for-other-machines/ Bender Creates Sugar Labs—New Foundation to Adapt OLPC’s Laptop Interface for Other Machines]
|-
|align=right valign=top|16 May 2008||'''BBC''' – [http://news.bbc.co.uk/2/hi/technology/7405346.stm '$100 laptop' platform moves on]
|-
|align=right valign=top|15 May 2008||'''OLPC wiki''' – [http://wiki.laptop.org/go/AnnounceFAQ Dual-boot XO] Claim: OLPC will not work to port Sugar to Windows.
|-
|align=right valign=top|16 May 2008||'''Softpedia''' – [http://news.softpedia.com/news/Bender-Launches-Sugar-Labs-for-Better-Development-of-OLPC-039-s-Sugar-UI-85881.shtml Bender Launches Sugar Labs for Better Development of OLPC's Sugar UI]
|}

==Press releases==
http://www.sugarlabs.org/press

[[Category:General public]]
</noinclude>

2016 Goals

2016-07-23T13:14:56Z

Davelab6: Add sean's old VM idea

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* to set up a matrix of VirtualBox prebuilt Sugar VMs, perhaps in partnership with Oracle;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment, how to get connected to the net with devices like https://smile.amazon.com/gp/product/B017CZWBBG/ and http://outernet.is/;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.);
** to update https://spins.fedoraproject.org/soas/ (see http://lists.sugarlabs.org/archive/marketing/2015-May/003859.html);
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to consolidate libre licensed books about Sugar;
** port [[olpc:Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom|http://wiki.laptop.org/go/Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom]] to our site;
** port https://www.gitbook.com/book/icarito/physics-with-xo/details to our site;
** liberate the ''Learning To Change The World'' text, and write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website (see [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17116.html thread]);
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* to list critiques of OLPC and Sugar Labs and summarise the actionable recommendations;
** https://www.scribd.com/document/33505402/Has-the-non-profit-business-model-adopted-by-One-Laptop-Per-Child-hindered-its-success;
** [list more here];
* to move from IRC (and perhaps the mailing lists) to a [http://www.mattermost.org/why-we-made-mattermost-an-open-source-slack-alternative/ mattermost] instance;
* [your goal here]

Vision

2016-07-23T13:13:52Z

Davelab6: Add page, redirect to the current proposal

#REDIRECT [[Vision_proposal_2016]]

ReleaseTeam

2016-07-13T12:43:21Z

Davelab6: Redirected page to Development Team

#REDIRECT [[Development_Team]]

ReleaseTeam

2016-07-13T12:43:00Z

Davelab6: Created page with "#RELEASE Development_Team"

#RELEASE Development_Team

2016 Goals

2016-07-11T13:16:12Z

Davelab6: add soas link

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment, how to get connected to the net with devices like https://smile.amazon.com/gp/product/B017CZWBBG/ and http://outernet.is/;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.);
** to update https://spins.fedoraproject.org/soas/ (see http://lists.sugarlabs.org/archive/marketing/2015-May/003859.html);
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to consolidate libre licensed books about Sugar;
** port [[olpc:Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom|http://wiki.laptop.org/go/Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom]] to our site;
** port https://www.gitbook.com/book/icarito/physics-with-xo/details to our site;
** liberate the ''Learning To Change The World'' text, and write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website (see [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17116.html thread]);
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* to list critiques of OLPC and Sugar Labs and summarise the actionable recommendations;
** https://www.scribd.com/document/33505402/Has-the-non-profit-business-model-adopted-by-One-Laptop-Per-Child-hindered-its-success;
** [list more here];
* to move from IRC (and perhaps the mailing lists) to a [http://www.mattermost.org/why-we-made-mattermost-an-open-source-slack-alternative/ mattermost] instance;
* [your goal here]

2016 Goals

2016-07-11T13:06:37Z

Davelab6: move to mattermost

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment, how to get connected to the net with devices like https://smile.amazon.com/gp/product/B017CZWBBG/ and http://outernet.is/;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.);
** to update https://spins.fedoraproject.org/soas/;
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to consolidate libre licensed books about Sugar;
** port [[olpc:Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom|http://wiki.laptop.org/go/Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom]] to our site;
** port https://www.gitbook.com/book/icarito/physics-with-xo/details to our site;
** liberate the ''Learning To Change The World'' text, and write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website (see [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17116.html thread]);
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* to list critiques of OLPC and Sugar Labs and summarise the actionable recommendations;
** https://www.scribd.com/document/33505402/Has-the-non-profit-business-model-adopted-by-One-Laptop-Per-Child-hindered-its-success;
** [list more here];
* to move from IRC (and perhaps the mailing lists) to a [http://www.mattermost.org/why-we-made-mattermost-an-open-source-slack-alternative/ mattermost] instance;
* [your goal here]

2016 Goals

2016-07-11T01:37:05Z

Davelab6: point to how to get connected

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment, how to get connected to the net with devices like https://smile.amazon.com/gp/product/B017CZWBBG/ and http://outernet.is/;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.);
** to update https://spins.fedoraproject.org/soas/;
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to consolidate libre licensed books about Sugar;
** port [[olpc:Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom|http://wiki.laptop.org/go/Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom]] to our site;
** port https://www.gitbook.com/book/icarito/physics-with-xo/details to our site;
** liberate the ''Learning To Change The World'' text, and write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website (see [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17116.html thread]);
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* to list critiques of OLPC and Sugar Labs and summarise the actionable recommendations;
** https://www.scribd.com/document/33505402/Has-the-non-profit-business-model-adopted-by-One-Laptop-Per-Child-hindered-its-success;
** [list more here];
* [your goal here]

2016 Goals

2016-07-10T19:25:15Z

Davelab6: update soas page

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.);
** to update https://spins.fedoraproject.org/soas/;
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to consolidate libre licensed books about Sugar;
** port [[olpc:Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom|http://wiki.laptop.org/go/Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom]] to our site;
** port https://www.gitbook.com/book/icarito/physics-with-xo/details to our site;
** liberate the ''Learning To Change The World'' text, and write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website (see [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17116.html thread]);
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* to list critiques of OLPC and Sugar Labs and summarise the actionable recommendations;
** https://www.scribd.com/document/33505402/Has-the-non-profit-business-model-adopted-by-One-Laptop-Per-Child-hindered-its-success;
** [list more here];
* [your goal here]

Oversight Board/Mission

2016-07-06T19:47:19Z

Davelab6:

The mission of the oversight board is to ensure that the Sugar Labs community has clarity of purpose and the means to collaborate in achieving its goals. (See [[Sugar_Labs/Governance]])

<noinclude>
[[Category:Governance]]
</noinclude>

Sugar Labs/FAQ

2016-07-06T19:30:06Z

Davelab6: Remove transcluded pages, just link to them

{{Graduate|Some useful stuff in here}}

<noinclude>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</noinclude>
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]''', or follow the question links at the top of the major sections, or visit [[:Category:FAQ]].
__TOC__
==Sugar==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== What is Sugar? ===
:Sugar is an educational software platform built with the Python programming language and based on the principles of cognitive and social constructivism. See [[What is Sugar?]].

=== Who is doing Sugar development? ===
:Sugar is a community project where all work is done by volunteers. You can get an idea of the people involved from the [[Development Team/Release/Modules]] page.

=== Does Sugar support Android? ===
: Not at this time, although there are some developers working to change that situation. See this [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg13765.html mailing list thread].

=== What makes Sugar different from other educational software platforms? ===
* See [[Marketing Team/Website#Website_2|Website sandbox]].
:The Sugar interface, in its departure from the desktop metaphor for computing, is the first serious attempt to create a user interface that is based on both cognitive and social constructivism: learners should engage in authentic exploration and collaboration. It is based on three very simple principles about what makes us human: (1) everyone is a teacher and a learner; (2) humans by their nature are social beings; and (3) humans by their nature are expressive. These are the pillars of a user experience for learning.

:Sugar also considers two aphorisms: (1) you learn through doing, so if you want more learning, you want more doing; and (2) love is a better master than duty—you want people to engage in things that are authentic to them, things that they love.

:The presence of other people is inherent to the Sugar interface: collaboration is a first-order experience. Students and teachers engage in a dialog with each other, support each other, critique each other, and share ideas.

:Sugar is also discoverable: it can accommodate a wide variety of users, with different levels of skill in terms of reading, language, and different levels of experience with computing. It is easy to approach, and yet it doesn't put an upper bound on personal expression; one can peel away layers and go deeper and deeper, with few restrictions.

:Sugar is based on Python, an interpreted language, allowing the direct appropriation of ideas: in whatever realm the learner is exploring—music, browsing, reading, writing, programming, graphics, etc.—they are able to drill deeper; they are not going to hit a wall, since they can, at every level, engage in debugging both their personal expression and the very tools that they use for that expression.

==Using Sugar==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== Who can use Sugar and how do they benefit? ===
:Sugar is a free software project, freely available to anyone who wants to use it or improve upon it.

:The Sugar platform was designed for young children (K–6), but it is finding applicability in a number of different venues where the simplicity of design maps is an enabler, e.g., mobile applications, the elderly, etc.

:'''Why Sugar?''' Sugar will engage even the youngest learner in the use of computation as a powerful "thing to think with." They will quickly become proficient in using the computer as a tool to engage in authentic problem-solving. Sugar users develop skills that help them in all aspects of life.
* Sugar comes with hundreds of tools for discovery through exploring, expressing, and sharing: browsing, writing, rich media, etc.
* Sugar comes with a built-in collaboration system: peer-to-peer learning; always-on support; and single-click sharing.
* Sugar comes with built-in tools for reflection; a built-in portfolio assessment tool that serves as a forum for discussion between children, their parents, and their teachers.
* The Sugar learning platform is discoverable: it uses simple means to reach to complex ends with no upper bound on where you can reach.
* Sugar is designed for local appropriation: it has built-in tools for making changes and improvements and a growing global community of support.
* Sugar puts an emphasis on learning through doing and debugging: more engaged learners are to tackle authentic problems.
* Sugar is available in a wide variety of forms: as part of GNU/Linux distributions; LiveUSB/CD; and in virtual machines or emulation.
:There is a further summary of the Sugar benefits [[Deployment Team/Small_deployment_guide#Why_Sugar|here]].

=== How can I get online with the Live USB/CD, and what can I do then? ===

:The Live USB device must be inserted into a USB port on your computer, the Live CD must be in your CD-ROM or DVD drive, when you start your computer, and your BIOS settings should be set to first look for an operating system there on the USB or CD-ROM device. If the settings are okay, the Live USB/CD will boot.

:After a little while, you will be prompted for a name and you will get to choose the colour of your avatar. This is a small X, like the arms and legs of a human, with an O as the head above the X. This is "you".

:Wait a little longer, and you will see "yourself" in the middle of the screen. Just below "you", is your journal, where everything you do is recorded.

:In the top left corner of the Frame is a circle of smaller circles. This is your Neighbourhood-circle. At the moment, only nearby wireless access points are visible as small coloured circles - more colour inside means better signal strength. Let your mouse pointer hover above a circle to see the name of the wireless network. A small padlock means you need to supply a username and password to access the network. Click the circle you would like to access. It should be a wireless network you know will grant you Internet access once you are connected. If the network is protected with a padlock, you will be prompted for a valid username and password at this point, so give these and click the OK-button. If everything is okay, you are now connected.

:You should soon see many small avatars like your own in your neighbourhood. Hover your mouse pointer above them to see what they are called.

:In the top left corner next to the Neighbourhood-circle, is your Friends-circle. You don't have any Sugar-friends at the moment, so this will be empty. Next to the Friends-circle is a circle with a single dot - that's right - it means you. Click the You-circle, and you will get back to you and your activities.

:Surrounding your avatar on the Home screen are many activities, so click the one that looks like a cartoon talk bubble to start the Chat-activity or some other activity - like the Paint-activity or the Calculator-activity. After a little while, the new activity opens. In the top right corner of all activities is a small menu, which says "Share with:". Click this to unfold the options, and choose Neighbourhood by clicking on it.

:Click the Neighbourhood-circle again, and you will notice that the activity is now visible to everyone in your neighbourhood. If you hover your mouse button over an activity in your neighbourhood, a small menu will unfold where you may choose to join the activity by selecting "Join" from the activity's menu. Remember, your neighbourhood is the entire world! People in other parts of the world may be working or sleeping when you start sharing your activities, so be patient - it might be many hours before anyone is available for a chat. Enjoy! :-)

=== Does Sugar run on {GNU/Linux, Fedora, Ubuntu, SUSE, MAC OS, Windows, etc.}? ===
:Please refer to the [[Supported systems]] page for an up-to-date list of supported systems.

=== Is there an image of the OS that can be run on a PC? ===
:You can download a Live USB image at [[Sugar on a Stick]] and a Live CD version of Sugar at http://wiki.laptop.org/go/LiveCd, or run Sugar natively on a [[Supported systems|supported system]]. (The language can be set from the Sugar-control-panel or My Settings link on the avatar panel.)

=== Does Sugar run on an ASUS Eee PC (or other "ultra-mobile" or "mini" PCs)?===
Yes. If it can run GNU/Linux and GNOME, it can run Sugar. Try [[Sugar on a Stick]] as a way to get started, but you should be able install it natively as well.

=== Is it possible to have mesh support with the Live USB/CD ? ===
Q: If I understand this correctly, mesh support means your wireless card functions as both an access point/router and a network node. In short, your wireless computer can pass along packages from nearby wireless computers and the other way round. Do you need special wireless cards for this, or is this a driver/software issue that could be fixed in the Live CD, so that more people can experience mesh networks?

:A: Yes, it will be possible to have [http://www.open80211s.org/trac/wiki/HOWTO-0.2.1 mesh support] with the Live CD shortly, provided you have a suitable wireless card.

:[http://www.o11s.org/ open80211s] is an open-source implementation of the emerging IEEE 802.11s wireless mesh standard. It has been accepted in the mainline Linux kernel and is included in release 2.6.26. The resulting software will run on GNU/Linux on commodity PC hardware.

:Open80211s is based on the mac80211 wireless stack and should run on any of the wireless cards that mac80211 supports. At present, September 2008, four families of drivers are supported or partially supported. The ath5k driver supports Atheros WLAN based chipsets, the b43 driver supports the 802.11 B/G family of wireless chips Broadcom produces, libertas_tf supports the Marvell 88W83886 USB device as found in the OLPC XO-1 laptop, and the zd1211rw driver covers a large proportion of USB-wireless devices on the consumer market as these are based on the ZyDAS ZD1211. Several months after the acquisition, Atheros rebranded the ZyDAS ZD1211 chip to AR5007UG.

== Sugar Labs ==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== What is Sugar Labs? ===
:Sugar Labs, a non-profit foundation, serves as a support base and gathering place for the community of educators and software developers who want to extend the Sugar platform and who have been creating Sugar-compatible applications.

=== What is the mission of Sugar Labs? ===
:The overarching mission of Sugar Labs is to support the Sugar platform through software development, and community outreach and support. The purpose of the Sugar platform is provide a software and content environment that enhances learning. Towards this end, Sugar is designed to facilitate learners to “explore, express, debug, and critique.”

=== What are the principles that guide Sugar Labs? ===
:Sugar Labs subscribes to principle that learning thrives within a culture of freedom of expression, hence it has a natural affinity with the free software movement (Please see [[Sugar_Labs#Principles|Principles]] page in this wiki for more details). The core Sugar platform has been developed under a GNU General Public License (GPL); individual activities may be under different licenses.

=== What is the relationship of Sugar Labs to One Laptop per Child? ===
:Sugar was originally developed as the user interface (UI) for the One Laptop per Child (OLPC) XO-1 laptop. Sugar Labs was established as an independent entity in order to facilitate the growth of Sugar beyond any single hardware platform. While Sugar Labs has a cooperative working relationship with OLPC, it is by no means an exclusive or proprietary relationship. Sugar Labs is not bound to any specific hardware platform or Linux distribution (Please see [[Supported systems]]).

:Sugar Labs is the upstream community for the Sugar project. Sugar Labs welcomes a close working relationship with OLPC. Sugar Labs also welcomes cooperation with other laptop and computer manufacturers and software and content providers.

:OLPC and Sugar Labs are not diverging, we are on the same page; we are both hoping to fund and support Sugar so that we can continue to provide the best learning experience for children. The Sugar Labs initiative is consistent with taking Sugar to the next level; this is not inconsistent with what OLPC is doing. Any help from outside or inside OLPC should help establish Sugar as a more stable and better product.

=== Who is upstream for Sugar? ===
:Sugar Labs is the upstream for the Sugar project.

=== Who is Sugar Labs? ===
:Sugar is a community project, so it is the sum of those of you who participate. Sugar Labs was started by some Sugar-community members: [[User:Walter|Walter Bender]], [[User:ChristophD|Christoph Derndorfer]], [[User:Bert|Bert Freudenberg]], [[User:Marcopg|Marco Pesenti Gritti]], [[User:Bernie|Bernardo Innocenti]], Aaron Kaplan, [[User:Erikos|Simon Schampijer]], and [[User:Tomeu|Tomeu Vizoso]]. We have rules of [[Sugar Labs/Governance | governance]] that have been vetted by a process of public discussion.

=== How do I get involved? ===
:Please see the [[Sugar Labs/Getting Involved|Getting Involved]] page in this wiki.

=== How do I learn more about Sugar Labs? ===
:Check out the following additional FAQs, and join the IAEP mailing list and ask us about anything related to the project that isn't related to code.

* [[Activity Team/FAQ|Activities]]
* [[Deployment Team/FAQ|Deployment]]
* [[Design Team/FAQ|Design]]
* [[Development Team/FAQ|Development]]
* [[Documentation Team/FAQ|Documentation]]
* [[Education Team/FAQ|Education]]
* [[Infrastructure Team/FAQ|Infrastructure]]
* [[Local Labs/FAQ|Local Labs]]
* [[Marketing Team/FAQ|Marketing]]
* [[Math4Team/FAQ|Math4 Project]]
* [[Oversight Board|Oversight Board]]
* [[Sugar on a Stick/FAQ|Sugar on a Stick]]
* [[BugSquad/FAQ|Testing]]
* [[Translation Team/FAQ|Translation]]
* [[Wiki Team/FAQ| Wiki]]

[[Category:General public]]
[[Category:FAQ]]

Sugar Labs/Governance

2016-07-06T19:26:24Z

Davelab6: Fix link

<noinclude>{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}
[[Category:General public]]
[[Category:Governance]]
[[Category:Policy]]
</noinclude>

==Sugar Labs Rules of Governance==
Please comment on the [[Talk:Sugar Labs/Governance|discussion page]].

----

One of the challenges that free software projects face is the impact of governance on their community members: while FLOSS licenses assure access to source code, that doesn't guarantee a successful project. A governance model can help ensure that the project is run in a professional, disciplined, and equitable manner. Good governance lets the community engage in discourse and provides a transparent mechanism for arbitration in the hopefully rare circumstances in which it is necessary.

Some attributes that are necessary for good governance include: meritocracy, transparency of process, open access to anyone who has demonstrated the skills to contribute, and a means to ensure a balance of control so that no one special interest wrests control of either the discourse or the decision-making.

===Software Freedom Conservancy===

Sugar Labs is a member of the [http://conservancy.softwarefreedom.org Software Freedom Conservancy] (SFC). This places the project under the umbrella of a 501.3(c) foundation. "The Conservancy provides member projects with free financial and administrative services, but does not involve itself with technological and artistic decisions. By joining the Conservancy, member FLOSS projects can obtain the benefits of a formal legal structure while keeping themselves focused on software development." Governance must be maintained by Sugar Labs on its own behalf to provide for the long term success and stability of Sugar.

The [[Sugar_Labs/SFC_Fiscal_Agreement|agreement between Sugar Labs and the SFC is here]].

The following governance model is largely derived from the model used by the Gnome Foundation (Please see [http://foundation.gnome.org/about/ gnome.org/about]).

==== Transactions ====

As a fiscal sponsor for FOSS projects, the Conservancy provides member projects with financial and administrative services:

* [[Sugar_Labs/Governance/Transactions#Request_for_payment|Request for payment]]
* [[Sugar_Labs/Governance/Transactions#Project_proposal_approval|Project proposal approval]]
* [[Sugar_Labs/Governance/Transactions#License_request|License request]]

===Oversight Board===

The central administrative body of Sugar Labs is termed the [[Oversight_Board|Oversight Board]].

Sugar Labs shall be governed by an Oversight Board, consisting of seven (7) members elected by the Sugar community—the Sugar Membership. The positions on the Oversight Board will be on a two-year staggered basis. The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board. The Oversight Board shall meet at least once per quarter to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. (It is expected that more frequent meeting will be required in the early stages of the program.) The minutes to these meetings shall be posted publicly on the Sugar Labs wiki ([[Oversight Board/Minutes]]).

The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board.

The Oversight Board will elect a single individual to communicate with the Conservancy (the "Representative") and shall notify the Conservancy promptly following the election of a new Representative. The Representative will have the authority to instruct the Conservancy on the Project's behalf on all matters.

The current list of Oversight Board members is on the [[Oversight Board]] page.

====Decision Panels====

The Oversight Board's role is to manage the day-to-day affairs of Sugar Labs and to help the community to build consensus. On the rare occasion of a contentious issue on which no general consensus can be reached, the Oversight Board is responsible for convening a Decision Panel. The Oversight Board will be responsible for determining when a Decision Panel is required and for selecting members for the Decision Panel. Members of the Oversight Board are not permitted to serve on a Decision Panel. A Decision Panel will solicit community input, discuss (in private if they deem it necessary), reach a conclusion internally, and produce a report documenting their conclusion. (Anyone may submit advice to a Decision Panel.) The Oversight Board will review and ratify Decision Panel reports.

===Advisory Board===

The [[Sugar Labs/Governance/Advisory Board|Advisory Board]] is made up of organizations and companies that support Sugar Labs. The Advisory Board has no decision-making authority but provides a vehicle for its members to communicate with the Oversight Board and help the Directors guide the overall direction of Sugar and the Sugar Labs Project. The Advisory Board will appoint (up to) three (3) members who will be non-voting attendees of Oversight Board meetings. The Advisory Board will meet up to twice per year.

The Advisory Board consists of representatives from the following Sugar Labs Foundation member corporations and projects.

Advisory board member companies pay an annual fee which helps finance the operations of the Sugar Labs Project.

=== Special Interest Groups ===

Special Interest Groups (SIGs) may be established by any member. They can be formed around
any topic and, if they prove to be useful, can be designated as official committees.
SIGs typically organize themselves as [[Sugar Labs/Teams|Teams]], [[:Category:Project|Projects]], or [[Local Labs]].

===Sugar Labs Referenda===

At times an issue may arise that merits gathering consensus from the community. Any member of the Sugar Labs Foundation can suggest a referendum. To be accepted, a request for a referendum must be endorsed by 10% of all of the membership. The overall referendum process is overseen by the Membership and Elections Committee, which can be reached at elections@sugarlabs.org.

A 75% vote of all of the members can override an Oversight Board decision.

=== Subpages ===

{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Sugar Labs/Roles

2016-07-06T19:26:09Z

Davelab6: Redirect to Oversight Board

#REDIRECT [[Oversight Board]]

Oversight Board

2016-07-06T19:24:33Z

Davelab6: Inline Sugar Labs/Roles contents

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude>
{{TOCright}}

== Mission ==

{{:Oversight_Board/Mission}}

== The Oversight Board ==

The current oversight board members are:

* [[User:Walter|Walter Bender]]
* Lionel Laské
* Sameer Verma
* [[User:Holt|Adam Holt]]
* [[Claudia Urrea]]
* [[User: Jmgarcia|José Miguel García]]
* Tony Anderson

===Contacts===

* slobs AT lists.sugarlabs.org - A private list for the Oversight Board members; all emails that do not ask to be private (or are not obviously intended to be private) will be forwarded to the publicly archived IAEP list.
* ombudsman AT sugarlabs.org - A neutral party with whom anyone (member or non-member) may consult privately. The ombudsman will report to the Oversight Board and the community each month that a consultation occurs. [[User:Bert|Bert Freudenberg]] is Ombudsman.

[[Category:Oversight board]]
[[Category:Contact]]

== Meetings ==

We meet on IRC at 19:00 UTC on the first Friday of each month (irc.freenode.net #sugar-meeting).

{{:Oversight_Board/Next_meeting}}

=== Previous Meetings ===

Minutes and logs from previous meeting can be found at [[Oversight Board/Minutes]].

== Decisions ==

Board actions and decisions are found at [[Oversight Board/Decisions]].

== Additional roles within Sugar Labs==

The [[Oversight Board]] is responsible for appointing delegates with executive functions.
Any Sugar Labs [[Sugar Labs/Members|member]] can be appointed by the board. Existing
delegates include:

* <strike>[[Sugar Labs/Executive_Director|Executive Director]] (ED)</strike>
* [[Sugar Labs/Treasurer|Treaurer]]
* [[Sugar Labs/Members|Membership Committee]]
* [[Sugar Labs/Ombudsman|Ombudsman]]

Coordinators are appointed independently by each SIG.

* [[Sugar Labs/Teams|Team Coordinators]]
* [[Sugar Labs/Projects|Project Managers]]
* [[Local Labs|Coordinators of Local Labs]]

The [[Oversight Board]] appoints one of its members as a liaison to each SIG.

== Former Board Members ==

We'd like to thank the follow former board members for their contributions:

* [[User:Marcopg|Marco Pesenti Gritti]] (2008–2009)
* [[User:Gdk|Greg Dekoenigsberg]] (2008–2009)
* [[User:Dfarning|David Farning]] (2008–2009)
* [[User:Tomeu|Tomeu Vizoso]] (2008-2010)
* [[User:Bernie|Bernie Innocenti]] (2008-2011)
* [[User:Alsroot|Aleksey Lim]] (2008-2012)
* [[User:Cjb|Chris Ball]] (2008-2012)
* [[User:SeanDaly|Sean Daly]] (2009–2010)
* [[User:Mchua|Mel Chua]] (2009-2011)
* [[User:Sebastian|Sebastian Silva]] (2010-2012)
* [[User:Gardito|Gerald Ardito]] (2013–2014)
* [[User:Francis|Daniel Francis]] (-2015)
* [[User:Cjl|Chris Leonard]] (-2015)
* [[User:Godiard|Gonzalo Odiard]] (-2015)

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

[[Category:Oversight board]]
[[Category:Governance]]

[[Category:Team]]

Sugar Labs/Governance

2016-07-06T19:24:08Z

Davelab6: Remove transcluded Sugar Labs/Roles page

<noinclude>{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}
[[Category:General public]]
[[Category:Governance]]
[[Category:Policy]]
</noinclude>

==Sugar Labs Rules of Governance==
Please comment on the [[Talk:Sugar Labs/Governance|discussion page]].

----

One of the challenges that free software projects face is the impact of governance on their community members: while FLOSS licenses assure access to source code, that doesn't guarantee a successful project. A governance model can help ensure that the project is run in a professional, disciplined, and equitable manner. Good governance lets the community engage in discourse and provides a transparent mechanism for arbitration in the hopefully rare circumstances in which it is necessary.

Some attributes that are necessary for good governance include: meritocracy, transparency of process, open access to anyone who has demonstrated the skills to contribute, and a means to ensure a balance of control so that no one special interest wrests control of either the discourse or the decision-making.

===Software Freedom Conservancy===

Sugar Labs is a member of the [http://conservancy.softwarefreedom.org Software Freedom Conservancy] (SFC). This places the project under the umbrella of a 501.3(c) foundation. "The Conservancy provides member projects with free financial and administrative services, but does not involve itself with technological and artistic decisions. By joining the Conservancy, member FLOSS projects can obtain the benefits of a formal legal structure while keeping themselves focused on software development." Governance must be maintained by Sugar Labs on its own behalf to provide for the long term success and stability of Sugar.

The [[Sugar_Labs/SFC_Fiscal_Agreement|agreement between Sugar Labs and the SFC is here]].

The following governance model is largely derived from the model used by the Gnome Foundation (Please see [http://foundation.gnome.org/about/ gnome.org/about]).

==== Transactions ====

As a fiscal sponsor for FOSS projects, the Conservancy provides member projects with financial and administrative services:

* [[Sugar_Labs/Governance/Transactions#Request_for_payment|Request for payment]]
* [[Sugar_Labs/Governance/Transactions#Project_proposal_approval|Project proposal approval]]
* [[Sugar_Labs/Governance/Transactions#License_request|License request]]

===Oversight Board===

The central administrative body of Sugar Labs is termed the [[Oversight_Board|Oversight Board]].

Sugar Labs shall be governed by an Oversight Board, consisting of seven (7) members elected by the Sugar community—the Sugar Membership. The positions on the Oversight Board will be on a two-year staggered basis. The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board. The Oversight Board shall meet at least once per quarter to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. (It is expected that more frequent meeting will be required in the early stages of the program.) The minutes to these meetings shall be posted publicly on the Sugar Labs wiki ([[Oversight Board/Minutes]]).

The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board.

The Oversight Board will elect a single individual to communicate with the Conservancy (the "Representative") and shall notify the Conservancy promptly following the election of a new Representative. The Representative will have the authority to instruct the Conservancy on the Project's behalf on all matters.

The current list of Oversight Board members is on the [[Sugar Labs]] page.

====Decision Panels====

The Oversight Board's role is to manage the day-to-day affairs of Sugar Labs and to help the community to build consensus. On the rare occasion of a contentious issue on which no general consensus can be reached, the Oversight Board is responsible for convening a Decision Panel. The Oversight Board will be responsible for determining when a Decision Panel is required and for selecting members for the Decision Panel. Members of the Oversight Board are not permitted to serve on a Decision Panel. A Decision Panel will solicit community input, discuss (in private if they deem it necessary), reach a conclusion internally, and produce a report documenting their conclusion. (Anyone may submit advice to a Decision Panel.) The Oversight Board will review and ratify Decision Panel reports.

===Advisory Board===

The [[Sugar Labs/Governance/Advisory Board|Advisory Board]] is made up of organizations and companies that support Sugar Labs. The Advisory Board has no decision-making authority but provides a vehicle for its members to communicate with the Oversight Board and help the Directors guide the overall direction of Sugar and the Sugar Labs Project. The Advisory Board will appoint (up to) three (3) members who will be non-voting attendees of Oversight Board meetings. The Advisory Board will meet up to twice per year.

The Advisory Board consists of representatives from the following Sugar Labs Foundation member corporations and projects.

Advisory board member companies pay an annual fee which helps finance the operations of the Sugar Labs Project.

=== Special Interest Groups ===

Special Interest Groups (SIGs) may be established by any member. They can be formed around
any topic and, if they prove to be useful, can be designated as official committees.
SIGs typically organize themselves as [[Sugar Labs/Teams|Teams]], [[:Category:Project|Projects]], or [[Local Labs]].

===Sugar Labs Referenda===

At times an issue may arise that merits gathering consensus from the community. Any member of the Sugar Labs Foundation can suggest a referendum. To be accepted, a request for a referendum must be endorsed by 10% of all of the membership. The overall referendum process is overseen by the Membership and Elections Committee, which can be reached at elections@sugarlabs.org.

A 75% vote of all of the members can override an Oversight Board decision.

=== Subpages ===

{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Marketing Team

2016-07-06T03:08:51Z

Davelab6: NYC Surveys

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>
'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.'''
Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet.
It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.
</div>

{{TOCright}}

{{:Marketing Team/Mission}}

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Sean's 2009 - 2015 Overview ==

Sean Daly acted as Marketing Team Coordinator 2008-2016, and when he stepped down on June 23 2016 he offered the following overview:

The 2009 marketing strategy we implemented, based on Sugar on a Stick, was very successful for a time during the netbook boom, but today's environment is very different with tablets, iOS/Android, etc. I had suggested two other ideas since then to the community to facilitate Sugar for teachers: prebuilt VMs for VirtualBox, and preloaded bootable SD cards and branded cases for Raspberry Pi. Since then, Lionel has developed Sugarizer, which in my view deserves serious consideration for marketing initiatives targeting teachers. Dave's efforts to identify a reference platform are also useful.

Samuel suggested a SWOT analysis today - it's an excellent suggestion, the last one we did is now way out of date. Work with Samuel and Dave and Samson on that, it will be helpful even for project recruitment which is their focus. A competitive landscape survey will be complementary to the SWOT. When the community reaches consensus on the project's vision, work on marketing objectives (as opposed to project objectives) can be done. This usually involves a calendar with what actions are planned. If budget is available, you will want metrics - ways to measure spend effectiveness.

Brand values: this is about how Sugar is different from anything else. We always emphasized low-floor, no ceiling; support for minority languages which for-profit companies ignore; the pedagogical pedigree; View Source; collaboration; the Journal.

There is also the PR aspect - targeting journalists, bloggers, and influencers. Communiqués are important for allowing a site visitor to get an idea of the project's direction in just a few minutes. Historically, we put PR on newswires. But these days, social media is very effective. Here's a tip for news coverage: if an initiative will influence large-buyer decisions (education ministries), or represents a real innovation (value proposition for less than what people usually pay), there could be press interest.

We have been using eReleases, a small company in Baltimore or Philly don't remember - http://ereleases.com - who have a great deal for nonprofits ("CauseWire"). The company president is Mickie Kennedy, and we have worked with editor Allison McAlister. We haven't done newswire PR for some time - I haven't known what newsworthy info we could put out that could possibly be picked up by traditional media, with the exception of GSoC news. There is an eReleases archives our PR.

The ongoing challenge is overcoming negative image perceptions of OLPC - that the $100 unit price didn't happen, that the project was somehow influenced by Microsoft, even that the project still exists. There is also an identified issue that our slick logo encourages a perception that we are a for-profit startup, not a nonprofit volunteer org. this is why we said "Nonprofit" in many of our PR communiqué titles.

My advice is to not waste time documenting the 2009-2010 strategy or my 2011-2012 attempts to develop a new one. Start from scratch - a SWOT analysis and competitive landscape is the starting point. Translate the SL project objectives into marketing objectives, define a calendar and metrics. You've stated recruitment objectives, but not a strategy... execution (facebook + Google AdWords) seems already decided, which IMHO is putting the cart before the horse, but no big deal.

https://wiki.sugarlabs.org/images/4/47/MCFE_Final_Presentation_SugarLabs_12-11.pdf

Caroline Meeks put together the SWOT analysis in this prez. I don't remember if I had assisted with that. I seem to remember having worked on another. I will search my offline archives, which are very complete concerning SL - I have everything from when I started.

This may be useful for very brief marketing strategy historical overview
http://lists.sugarlabs.org/archive/marketing/2013-November/003607.html

The success of the SoaS marketing initiative encouraged some SL members to assert control over the name, the trademark, the technical architecture, and the marketing of it. As a result the lead developer of SoaS left the project.

Peter had justifiably complained on IRC around 2010 that there was no marketing strategy page. I had chosen not to create one at the time because OLPC was involved in fierce competition with Intel Classmate offerings running Windows, and we were aware that our marketing initiatives were being monitored. This lack of clarity may have been a mistake, but my goal had been to disrupt the MS/Intel sales force talking points. The marketing team which was numerous at the time all knew the strategy.

=== Walter's 2016 Marketing Plan ===

Walter Bender offered this view for future marketing efforts:

What I would like from marketing is some mechanism for highlighting the powerful ideas in Sugar that seem to be lacking in most other systems so that even if a school decides to go with a different product/project, they put pressure on that project to provide tools, not apps, collaboration, transparency, self reflection and group critique, and responsibility on the shoulders of students and teachers to shape their own world.

A few observations/thoughts that may help us in focusing our marketing efforts:

(1) The primary source of push back in AU re Sugar was the browser. Schools had websites that they were interested in accessing that were not supported by Browse at the time. This is something we can turn around in the devel team and maybe something we need to surface in marketing: that Sugar is web/cloud enabled on top of all its other virtues. (I had been keeping the name "cloudberry" in reserve for this.) Ironically, at the time we added Sugar extensions for access to Google Drive (among other clud-based services), NSW got in bed with Microsoft and prohibited schools from using non-MS cloud services. OLPC AU never promoted the Sugar cloud-enabled features.

(2) The switch to Windows 10 by OLPC AU is a total capitulation to the "we don't have a clue as to what is of value in terms of pedagogy, so we'll make a deal with whomever will give us the best deal camp." Not sure what our response should/can be in such circumstances.

(3) There is a still strong interest in Sugar in Paraguay and some momentum to go national. We could try to ride that wave. We've been invited to come to Paraguay in October.

(4) I'm pushing hard in Chile... we'll see what happens.

(5) In UY, they are still using Sugar in primary schools (on Ubuntu). We should market in the Ubuntu space (I had had an offer from Ubuntu to let us do the equivalent of a Fedora Spin which we could follow up on).

(6) We should push on Red Hat to give us more exposure.

(7) Can we get a Sugarizer pilot going in a school to get a sense of what it means.

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== Google Non Profits AdWords ===

SL is obtaining $10,000 per month AdWords credit that Google offers to nonprofits and will use to run adwords campaigns by these members:

* Dave Crossland
* Sean Daly
* Samson Goddy
* Walter Bender

The marketing strategy will be to seek new members. Three kinds of members will be sought: (1) software developers, to write python and javascript programs (2) translators, to localize the programs, and (3) technical authors, to increase adoption by specific audiences - parents and schools.

Next Goal: Obtain access to the AdWords account.

Deadline: July 30 2016

=== Local Labs Survey 2016 ===

Sugar Labs will survey end users to better understand how Sugar is being adopted and adapted.
See also

* [[Marketing Team/Local Labs Survey 2016]]
* In late 2015/early 2016, Sam Parkinson ran a survey on http://socialhelp.sugarlabs.org and wrote a report ([[Media:2016_Socialhelp_Survey_Analysis.pdf]]) and published the source data ([[File:2016_SocialHelp_Survey_Response_Data.ods]])
* [http://download.laptop.org/content/conf/20080520-country-wkshp/Presentations/OLPC%20Country%20Meeting%20-%20Day%204%20-%20May%2023rd,%202008/OLPC%20student%20survey%20-%20Teaching%20Matters.pdf 2008 user survey in NYC] (also [http://www.teachingmatters.org/files/olpc_kappa.pdf official report])

Next Goal: List as many end users as possible.

Deadline: August 30 2016

=== New Website ===

In late 2010, four students from the MIT Sloan MarketLab worked on a study of the Sugar Labs website.
Their conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues, as well as the technical orientation of our web presence.

* The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar
* Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]
* A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]
* The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

Our polished static website as a landing page for Sugar Labs was redone in March-May 2011, see [[Marketing Team/Website]] history

Next Goal: Get the SL 2016 Vision, Mission, and Goals approved by SLOBs

Deadline: September 15 2016

===Events===

See [[Marketing Team/Events]] for a table of events we are targeting.

Next Goal: List possible future events.

Deadline: September 30 2016

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/press

Next Goal: Draft the next press release; Develop a [[Marketing Team/Press contacts]] list with education-oriented publications.

Deadline: September 30 2016

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

Next Goal: List contributors active in 2016

Deadline: August 30 2016

=== Swag ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, umbrellas, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]]

Next Goal: Design new swag for 2016

Deadline: September 30 2016

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

2016 Goals

2016-07-04T15:18:59Z

Davelab6: add critiques

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to consolidate libre licensed books about Sugar;
** port [[olpc:Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom|http://wiki.laptop.org/go/Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom]] to our site;
** port https://www.gitbook.com/book/icarito/physics-with-xo/details to our site;
** liberate the ''Learning To Change The World'' text, and write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website (see [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17116.html thread]);
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* to list critiques of OLPC and Sugar Labs and summarise the actionable recommendations;
** https://www.scribd.com/document/33505402/Has-the-non-profit-business-model-adopted-by-One-Laptop-Per-Child-hindered-its-success;
** [list more here];
* [your goal here]

2016 Goals

2016-07-04T15:16:56Z

Davelab6: clarify books goals

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to consolidate libre licensed books about Sugar;
** port [[olpc:Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom|http://wiki.laptop.org/go/Sdenka_Salas_-_The_XO_Laptop_in_the_Classroom]] to our site;
** port https://www.gitbook.com/book/icarito/physics-with-xo/details to our site;
** liberate the ''Learning To Change The World'' text, and write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website (see [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17116.html thread]);
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* [your goal here]

2016 Goals

2016-07-02T21:34:51Z

Davelab6: add TDA thread

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to liberate the ''Learning To Change The World'' text;
** to write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website (see [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17116.html thread]);
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* [your goal here]

2016 Goals

2016-07-02T21:00:17Z

Davelab6: link to LTCTW chapter

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to liberate the ''Learning To Change The World'' text;
** to write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]) starting with [[User:Walter/Fueling Learning With Sugar]];
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website;
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* [your goal here]

2016 Goals

2016-07-02T17:00:16Z

Davelab6: Package python sugar for Android

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on Android with [https://python-for-android.readthedocs.io/en/latest/ python-for-android];
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to liberate the ''Learning To Change The World'' text;
** to write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]);
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website;
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* [your goal here]

Oversight Board/Decisions

2016-07-01T20:38:42Z

Davelab6: Add motions passed at today's IRC meeting

This page (largely complete) is intended to be a one-stop place for reviewing all of the Sugar Labs oversight board (SLOB) actions and decisions.

The date headlines are the date that the motion is agreed, disagreed, or - in the case of motions to be voted on via email within 7 days of posting which did not get voted on - failed by timing out.

Due to confusion about Sugar Labs governance, during 2016 several members of the project not on the SLOB posted motions, but these were not seconded, and have been struck out to show they were considered by some SLOB members are invalid.

== 2016-07-01 ==

[http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-07-01T19:00:23 IRC log]

;AGREED MOTION 2016-42 Walter Bender, posting motion initially drafted by Caryl Bigenho (member) and Tony Anderson (SLOB) and Adam Holt (SLOB): The Sugar Labs Oversight Board shall appoint a Finance Manager by majority vote from among the members of Sugar Labs Oversight Board. The Finance Manager serves at the will of the board. The Finance Manager may be paid a stipend at the discretion of the board. Duties of the Finance Manager will be to: 1. Serve as Sugar Lab's central coordinator on all financial matters. 2. Report quarterly at a scheduled Oversight Board meeting the following: Confirmation of the accuracy of the previous quarter's report according to the Software Freedom Conservancy; Balance at the beginning of the quarter preceding the meeting; Expenses during the quarter; Income received during the quarter; Balance at the end of the quarter. 3. The Finance Manager has discretion to approve petty cash amounts up to $200 to pay for miscellaneous expenditures critical for the functioning of Sugar Labs. If approved and everything is in order, these will often be paid within (about) 30 days of when they are submitted to the Software Freedom Conservancy, who control Sugar Labs' banking. If not approved, the applicant is free to ask for a vote at a future Oversight Board meeting. 4. All motions for funding of larger projects will be presented first to the Finance Manager who will review them to be sure the funds are being used in a way that appears fiscally sound. If everything is in order, the Finance Manager will place the motion on the agenda for consideration at the next possible Oversight Board meeting, and circulate on the IAEP mailing list for public discussion. 5. At the meeting, after a finance motion has been moved and seconded, discussion should be confined to the motion.<br>(5 votes for, 2 against)<br>(Full motion with sample financial report available at http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17107.html)

;AGREED MOTION 2016-41 Walter Bender, posting motion initially drafted by Dave Crossland: To request a membership donation from each currently active Sugar Labs Member to be allocated to the General Fund for the calendar year of 2016, and a public statement about how they use Sugar and why they are involved in Sugar Labs to post on the website; there is no penalty for not paying a membership or not providing a statement; by default members who donate will be kept private, and requested to opt-in to be recognised. The donation requested will be $12 USD from members who self-identify as low-income (such as students); $36 USD from general members; $120 from members who can opt-in to be placed prominently on the website; and $600 from members who can (privately if they wish) submit a release codename, subject to SLOB approval.<br>(4 votes for, 1 against, 2 abstain)<br>(note that the "low income" solicitation did not reach consensus during the meeting and Dave Crossland offered to work with the board to ensure the solicitation will meet their approval before it is sent to members.)

== 2016-06-30 ==
;<s>MEMBER MOTION 2016-40 Dave Crossland</s>: <s>To append to existing bylaw for Finance Manager new procedures.</s>
;<s>MEMBER MOTION 2016-39 Dave Crossland</s>: <s>To replace existing bylaw for Finance Manager.</s>

== 2016-06-14 ==
;<s>MEMBER MOTION 2016-38 Dave Crossland</s>: <s>to consider email votes on motions only valid if they are sent to both the SLOBs and IAEP mailing lists. (not seconded)</s>

== 2016-06-11 ==
;<s>MEMBER MOTION 2016-37 Dave Crossland, posting motion initially drafted by Tony Anderson</s>: <s>to undertake a fund raising drive. Arrangements will be made to enable on-line contributions by PayPal, debit or credit card or other means. Once the means to make contributions is in place, the Financial Manager will initiate and lead the drive. The Sugar Labs web site will show progress in donations toward the goal. (not seconded)</s>

== 2016-06-10 ==
;<s>MEMBER MOTION 2016-36 Dave Crossland</s>: <s>to vote on each motion proposed by a member, dropping the current practice of requiring a seconding before voting. (not seconded)</s>
;<s>MEMBER MOTION 2016-35 Dave Crossland</s>: <s>to agree the following procedure for all future monthly SLOB meetings: the chair will confirm the meeting meets quorum; the chair will make any announcements submitted to them before the meeting; the chair will announce the first motion pending a vote on that day; each present SLOB member will announce their vote; the chair will announce the outcome of the motion; the chair will announce the next motion, until all motions are voted on; the chair will invite everyone attending to an open discussion of any topic until the meeting ends at the time scheduled. (not seconded)</s>
;AGREED MOTION 2016-34 Walter Bender, posting motion initially drafted by Dave Crossland: Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (5 votes for, 1 against, 1 abstain, see http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg16711.html)
;<s>MEMBER MOTION 2016-33 Laura Vargas</s>: <s>to update current SL vision statement ("About Sugar Labs(R): Sugar Labs(R) is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs(R) is supported by donations and is seeking funding to accelerate development.") to the new proposed text: "Sugar Labs is a global community where you can learn how to design, develop and deploy high-quality Free/Libre Software that facilitates self-discovery learning experiences and collaboration among young children of all continents." (not seconded)</s>

== 2016-06-09 ==
;<s>MEMBER MOTION 2016-32 Dave Crossland</s>: <s>The value of $Y in the Finance Manager Guidelines should be $200 (not seconded)</s>

== 2016-06-03 ==

[http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-06-03T19:01:08 IRC log]
;FAILED MOTION 2016-31 Walter Bender, posting motion initially drafted by Dave Crossland: To adopt the [https://wiki.sugarlabs.org/index.php?title=Vision_proposal_2016&oldid=98911 Vision proposal 2016]. (not seconded)
;<s>MEMBER MOTION 2016-30 Dave Crossland</s>: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa <s>To add to the bylaws a new section, “Sugar Labs Oversight Board Spending Guidelines”</s>] <s>(dependent upon MOTION 2016-27)</s>
;<s>MEMBER MOTION 2016-29 Dave Crossland</s>: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa <s>To append the following text to the existing bylaw for the Finance Manager office</s>] <s>(dependent upon MOTION 2016-27)</s>
;FAILED MOTION 2016-28 Walter Bender, posting motion initially drafted by Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To define procedures for requesting, obtaining, and reporting use of SugarLabs funds] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-27 Walter Bender, posting motion initially drafted by Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded)

== 2016-05-29 ==

;<s>MEMBER MOTION 2016-26 Dave Crossland</s>: <s>To request donations from Sugar Labs Members, to be allocated to the General Fund through the SFC. The annual donation requested will be $12 USD from members who self-identify as low-income (such as students); $36, $120, or $600 USD from general members. (not seconded)</s>

;<s>MEMBER MOTION 2016-25 Dave Crossland</s>: <s>To request a membership donation from each currently active Sugar Labs Member to be allocated to the General Fund for the calendar year of 2016, and a public statement about how they use Sugar and why they are involved in Sugar Labs to post on the website; there is no penalty for not paying a membership or not providing a statement; by default members who donate will be kept private, and requested to opt-in to be recognised. The donation requested will be $12 USD from members who self-identify as low-income (such as students); $36 USD from general members; $120 from members who can opt-in to be placed prominently on the website; and $600 from members who can (privately if they wish) submit a release codename, subject to SLOB approval. (seconded at http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg16767.html but all SLOBs abstained)</s>

;<s>MEMBER MOTION 2016-24 Dave Crossland</s>: <s>Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (not seconded)</s>

== 2016-05-25 ==
;<s>MEMBER MOTION 2016-23 Caryl Bigenho</s>: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit <s>To define procedures for requesting, obtaining, and reporting use of SugarLabs funds</s>] <s>(dependent upon MOTION 2016-22)</s>
;<s>MEMBER MOTION 2016-22 Caryl Bigenho</s>: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit <s>To replace existing bylaw for Finance Manager</s>] <s>(not seconded)</s>

== 2016-05-12 ==
;AGREED MOTION 2016-21 Walter Bender: to reimburse Edgar Quispe for expenses incurred representing Sugar Labs at the Traducción e interpretación en las lenguas originarias del Perú meeting in Lima. The cost is $168.88. : (See http://lists.sugarlabs.org/archive/iaep/2016-May/018196.html)

== 2016-05-11 ==
;FAILED MOTION 2016-20 Walter Bender: to allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit. : (3 votes for, 1 vote against, and 4 abstains)

== 2016-05-06 ==
;AGREED MOTION 2016-19 Walter Bender, posting motion initially drafted by Dave Crossland: To pay for laboratoriosazucar.org domain registration renewal
;FAILED MOTION 2016-27 Walter Bender, posting motion initially drafted by Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded, further drafting requested)
;AGREED MOTION 2016-14 Walter Bender, posting motion initially drafted by : To fund a program to initiate the translation of Sugar into Yoruba. The work would be led by Samson Goddy and reviewed by Chris Leonard, in his role as Translation Community Manager (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052462.html]).
;AGREED MOTION 2016-13 Walter Bender, posting motion initially drafted by Dave Crossland: To update the Sugar License from GPLv2 to GPLv3 [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052552.html]
;FAILED MOTION 2016-12 Walter Bender: To allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052463.html]).
;FAILED MOTION 2016-11 Lionel Laske: To adopt the wiki Vision proposal for 2016 (not seconded)

== 2016-04-09 ==
;AGREED MOTION 2016-10 Walter Bender: To offer Devin U. an honorarium ($500) to compensate him since he needed to take a week off from work to run two Turtle/Music Blocks workshops at the Constructionism Conference. The funds would be allocated from the Trip Advisor grant which are in support of promoting and advancing Turtle Blocks around the world. (Vote taken by email.)
;AGREED MOTION 2016-09 Walter Bender: Walter, as PI of the Trip Advisor grant, will inform the SL oversight board of his plans for workshops that fall under the guise promotion of Turtle Blocks but otherwise has discretion in organizing and funding these events, within the budget constraints of grant and the travel guidelines of the SFC. (Vote taken by email.)

== 2016-04-07 ==
;<s>MEMBER MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference])</s>: <s>All funds raised by any Sugar Labs community member in the name of Sugar Project's translations must be directed to the “Sugar Projects Translation's Fund”. (not seconded)</s>
;<s>MEMBER MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference])</s>: <s>The present SugarLabs Oversight board appoints the current Translation's Committee, with the full responsability of reviewing, upgrading, approving and overseeing Sugar Translation Projects and Proposals made by any interested party, with special attention to Native Languages communities. (not seconded)</s>
;<s>MEMBER MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference])</s>: <s>Requests for funds will be presented to the Translation's Committee, in writing, with copy to the IAEP mailing list and the Localization mailing list, at least 72 hours in advance of the monthly scheduled "Translation Committee Meeting". Committe members shall vote during the meeting for approval by simple majority. All interested parties, must also send the proposal to the IAEP mailing list and the Localization mailing list, in advance. (not seconded)</s>

== 2016-04-06 ==
;AGREED MOTION 2016-08: To approve the position of Translation-Community Manager as described at [[Translation-Community Manager]].
;AGREED MOTION 2016-07: That Chris Leonard be named to this position effective immediately.
;AGREED MOTION 2016-06: That the Translation-Community Manager be paid a stipend of $1000/month.

== 2016-04-01 ==
;AGREED MOTION 2016-05: In keeping with the board 2010's decision on this matter from a different era, it was suggest that if a Board Member (1) fails to vote and attend pre-scheduled Board meetings for more than 12 weeks, (2) resigns or (3) dies, then the Board is empowered and encouraged to appoint a replacement for this seat. Finally, just a clarification that the Replacement Board Member would be required to defend their seat during the very next election.

== 2016-03-04 ==
;AGREED MOTION 2016-04: Based on [[Translation Proposal]], Tony (and other SLOB members) should write up a job description with goals and reporting structure for a coordinator position to be submitted to the SFC.
;AGREED MOTION 2016-03: Restrict email voting to 1 week going forward, to remove confusion from the current voting process, keeping focus. Board members' email votes would be required to arrive within One Week Maximum (168.0 hours) of the original motion. (Any motion that fails to pass within this 1-week sunset period, can of course be attempted again in future, e.g. if long-term overseas/off-grid/medical absences require another later vote on the same topic).

== 2016-02-12 ==
;AGREED MOTION 2016-02: Moving regular SLOB meeting dates to the first Friday of the month at 16UTC
;AGREED MOTION 2016-01: Apply for GSoC 2016 (Lionel and Walter as co-admins)

== 2015-12-17 ==
;FAILED MOTION 2015-07(3 In Favor, 4 Abstentions): to pay Devin Ulibarri $500 for help organize and run the Turtle workshop in Bangkok
(See renewed motion passed on 2016-04-09.)

== 2015-10-12 ==
;AGREED MOTION 2015-06: Apply to GCI

== 2015-09-14 ==
;AGREED MOTION 2015-05: funding to file an affidavits required to maintain the registration of Sugar Labs' trademarks with the USPTO.
;ACTION: Walter to recruit mentors for GCI

== 2015-07-06 ==
;ACTION: acknowledged the numerous contributions to Sugar from the late Marco Presenti Gritti.

== 2015-05-06 ==
;AGREED MOTION 2015-04: via email to add Samson Goody to the Membership Committee (DONE)

== 2015-05-04 ==
;AGREED MOTION 2015-03: to share survey results with community (DONE)
;ACTION: Gonzalo to post results (DONE)
;ACTION: Gonzalo to write to each of the respondents
;AGREED MOTION 2015-02: that Claudia and Walter go to NI to discuss Sugar/OLPC future with the Zamoras
;ACTION: Walter to make a first pass at culling the decisions from past meetings into one page (this page)

== 2015-04-06 ==
;AGREED MOTION 2015-01: appoint Icarito and Caryl to the election committee and to try to recruit a youth member to the committee.

== 2015-01-14 ==
;ACTION: organize a summit to discuss the future of Sugar
;ACTION: do a survey to solicit feedback from deployments
0
== 2014-10-07 ==
;ACTION: Recruit mentors for GCI
;ACTION: Recruit candidates for oversight board

== 2014-07-08 ==
;AGREED MOTION 2014-02: on a .UY venue for a summit in September 2014. Jose Miguel and Daniel will get back to us about specifics.

== 2014-03-03 ==
;ACTION: everyone solicit students for GSoC

== 2014-02-05 ==
;AGREED MOTION 2014-01: to Gonzalo and Manuq's proposal for Background Image Contest

== 2013-11-04 ==
;AGREED MOTION 2013-06: Luke to run election for oversight board again
;AGREED MOTION 2013-05: to give cjl discretion over the i18n funds in the Trip Advisor grant

== 2013-10-18 ==
;AGREED MOTION 2013-04: we would apply again to Google Code In

== 2013-03-21 ==
;AGREED MOTION 2013-03: the next release will be Sugar 1.0

== 2013-02-25 ==
;AGREED MOTION 2013-02: to establish a category for Sugar Labs advisors/educators/friends
;ACTION: Claudia and Walter will meet to start planning Turtle Art Day
;AGREED MOTION 2013-01: to apply for Google Summer of Code 2013

== 2013-01-07 ==
;ACTION: ClaudiaU agreed to share ''Making Learning Visible'' with SLOB members (and Tonyf and JT4Sugar)

== 2012-05-30 ==
;AGREED MOTION 2012-05: to modify the Trademark and Local Labs pages in the wiki (See [[/Oversight_Board/Meeting_Minutes-2012-05-30#1._Updates_to_the_TM_policy_.28Trademark.29|TM Policy]] and [[Oversight_Board/Meeting_Minutes-2012-05-30#2._Updates_to_the_Local_Lab_wiki_.28Local_Labs.29|Local Labs Policy]])

== 2012-05-03 ==
;AGREED MOTION 2012-04: We approved a budget of up to US $5000 for two servers.
;AGREED MOTION 2012-03: Sugar Labs joins the SFC GPL enforcement program
;ACTION MOTION 2012-02: Walter to bring code-of-conduct discussion to the community.
;ACTION MOTION 2012-01: SLOB members to get signed agreements to the SFC regarding new SFC by-laws.

== 2011-12-02 ==
;AGREED MOTION 2011-09: The Sugar Labs Oversight Board thanked Bernie Innocenti and Mel Chua for their dedicated service to the community in their role as members of the oversight board.

== 2011-09-16 ==
;AGREED MOTION 2011-08: to keep the GSoC 2010 mentor funds as our general funds.

== 2011-08-05 ==
;AGREED MOTION 2011-07: to award Sugar participation certificates (See [[Oversight_Board/2011/Meeting_Minutes-2011-08-05#Certificate_program|Certificate Program]]).
;AGREED MOTION 2011-06: to give North Dakota State University authority to establish a local Sugar Lab.

== 2011-06-09 ==
;AGREED MOTION 2011-05: to endorse Free Software as defined here: http://www.gnu.org/philosophy/free-sw.html

== 2011-05-08 ==
;AGREED MOTION 2011-04: Bernie (head of infrastructure team) is authorized to approve spending tickets filed on the bug tracker up to $200.
;AGREED MOTION 2011-03: to update the governance page.

== 2011-02-10 ==
;AGREED MOTION 2011-02: SL endorses the idea that community members have kids: means more Sugar hackers in the future !!
;AGREED MOTION 2011-01: Local labs can issue Sugar certificates (and charge for this service whatever they want) but only if: (1) they maintain a page on our wiki explaining what content they use for training, where to download it, and what pricing they use; and (2) all the content they use for training is licensed under one of the licenses recommend by http://opensource.org/docs/osd and/or http://fedoraproject.org/wiki/[…]ing#Good_Licenses.

== 2010-12-13 ==
;AGREED MOTION 2010-10: [[Oversight_Board/Project_Motion]]
;AGREED MOTION 2010-09: SL would like to acknowledge and celebrate the marriage of acaire11 and icarito : the first Sugar marriage!!!

== 2010-12-01 ==
;AGREED MOTION 2010-08: Each active team and local lab should propose a few delegates from that team to SLOBs. We will invite the delegates to SLOBs meetings, and rotate scheduled times during SLOBs meetings to hear reports from their team or lab.
;AGREED MOTION 2010-07: The default time/day of the week for SLOBs meetings will be Thursdays at 15:00 EST (20:00 UTC)
;AGREED MOTION 2010-06: If a SLOB member misses one month of regular weekly meetings in a row, twice during one calendar year, SLOBs may find a replacement for their seat.

== 2010-09-28 ==
;AGREED MOTION 2010-05: We, the SLOB, acknowledge and praise the efforts of the release team for bringing us 0.90!!

== 2010-05-07 ==
;AGREED MOTION 2010-04: to a [[Trademark]] policy.

== 2010-03-05 ==
;AGREED MOTION 2010-03: (1) Bundles with non-Sugar dependencies be clearly marked in ASLO; (2) We work towards a mechanism for supporting access to non-Sugar dependencies--a specific endorsement of being open; and (3) We do not restrict ASLO while we progress towards #2.

== 2010-02-26 ==
;AGREED MOTION 2010-02: to authorize Bernie to spec out a machine around $2000, send details to systems@ for review, decide exactly where it will be hosted, then buy it.

== 2010-01-22 ==
;AGREED MOTION 2010-01: to authorize Luke Faraone to ship some used hardware from the Wikipedia Foundation (12 servers) to various hosting sites. The cost should not exceed US$300.

== 2009-12-18 ==
;AGREED MOTION 2009-18: Sugar Labs encourages all GNU/Linux distributions to package and distribute Sugar, and if possible will assist with hosting and infrastructure. SL Marketing may strategically decide to focus resources towards specific distributions in the interest of promoting Sugar more effectively.
;AGREED MOTION 2009-17: Yes, "Sugar on a Stick" should be reserved by Sugar Labs for use by the SoaS-Fedora distribution so that Sugar can be marketed effectively, until such time when a trademark policy, agreement, and process is put in place: SoaS will be the first project to go through that process.

== 2009-12-11 ==
;AGREED MOTION 2009-16: to adopt http://opensource.org/docs/osd as a set of guidelines for what is permitted on ASLO, for both software and content, and http://fedoraproject.org/wiki/Licensing#Good_Licenses's opinions on specific licenses where applicable, and always asking the SFC for advice when a particular license is under question.
;AGREED MOTION 2009-15: SL is and should be a GNU/Linux distributor.
;AGREED MOTION 2009-14: SL wishes to spread the use of Sugar and consequently works with GNU/Linux distros to produce and offer downloadable versions. This work can include helping to promote distros, and hosting them.
;AGREED MOTION 2009-13: SL should not be completely neutral about promoting distros, but it should only choose to more strongly promote a distro based on technical merit and maintainer activity, and should publish the criteria it uses for making that decision. Furthermore, SL should be neutral about providing infrastructure resources (hosting, etc) to distros."

== 2009-12-04 ==
;AGREED MOTION 2009-12: when a DP fails to meet a deadline, the decision passes to SLOBs.

== 2009-11-20 ==
;AGREED MOTION 2009-11: Close the slobs@ list to just SLOBs, move current slobs@ traffic to iaep@ with a [SLOBS] subject line tag where at all possible.
;AGREED MOTION 2009-10: Give a two-week deadline to the Soas DP

== 2009-09-25 ==
;AGREED MOTION 2009-09: We appointed a decision panel (by a vote of 3 for, 0 against, 1 abstain, 3 absent) with the following mandate:
:"Investigate the situation of how SoaS should be treated by Sugar Labs, and related questions, including answers to the following:
:"Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"
:"Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
:"Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"
:Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"

== 2008-09-05 ==
;AGREED MOTION 2009-08: The Oversight Board acknowledged and celebrated the great job Simon has been doing on managing the 0.82 release.

== 2009-07-18 ==
;AGREED MOTION 2009-07: There was consensus that we have made sufficient outreach to the community that the initial list is a fair representation of Sugar Labs; we look forward to having the Membership Committee take it from http://selectricity.org/
;AGREED MOTION 2009-06: There was consensus that Walter would put together a strawman election process based upon the Selectricity tool. We are targeting an August election.
;AGREED MOTION 2009-05: There was consensus that we begin with just Oversight and Members committees.
;AGREED MOTION 2009-04: We agreed for the need to solicit more feedback in the wiki for the design direction being proposed by Luca.
;AGREED MOTION 2009-03: We agreed that further discussions with the SFLA about the merits of trademark protection is needed.
;AGREED MOTION 2009-02: We agreed on the desirability of Sugar Labs participation at conferences around the world, but hope to meet the need by utilizing locals to whatever extent possible. We also discussed the desirability to have a meeting of Sugar Labs developers a couple of times per year. We discussed the possibility of an on-line meeting that leverages resources above and beyond IRC.
;AGREED MOTION 2009-01: on the necessity of Sugar Labs participation in the learning community, but don't yet have a good handle on the best and most efficient means of accomplishing this.

Oversight Board

2016-07-01T20:16:29Z

Davelab6: clarify slobs list will be fwd'd

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude>
{{TOCright}}

== Mission ==

{{:Oversight_Board/Mission}}

== The Oversight Board ==

The current oversight board members are:

* [[User:Walter|Walter Bender]]
* Lionel Laské
* Sameer Verma
* [[User:Holt|Adam Holt]]
* [[Claudia Urrea]]
* [[User: Jmgarcia|José Miguel García]]
* Tony Anderson

===Contacts===

* slobs AT lists.sugarlabs.org - A private list for the Oversight Board members; all emails that do not ask to be private (or are not obviously intended to be private) will be forwarded to the publicly archived IAEP list.
* ombudsman AT sugarlabs.org - A neutral party with whom anyone (member or non-member) may consult privately. The ombudsman will report to the Oversight Board and the community each month that a consultation occurs. [[User:Bert|Bert Freudenberg]] is Ombudsman.

[[Category:Oversight board]]
[[Category:Contact]]

== Meetings ==

We meet on IRC at 19:00 UTC on the first Friday of each month (irc.freenode.net #sugar-meeting).

{{:Oversight_Board/Next_meeting}}

=== Previous Meetings ===

Minutes and logs from previous meeting can be found at [[Oversight Board/Minutes]].

== Decisions ==

Board actions and decisions are found at [[Oversight Board/Decisions]].

== Additional roles within Sugar Labs==

{{Transclude|Sugar Labs/Roles|heading=<nowiki></nowiki>}}

== Former Board Members ==

We'd like to thank the follow former board members for their contributions:

* [[User:Marcopg|Marco Pesenti Gritti]] (2008–2009)
* [[User:Gdk|Greg Dekoenigsberg]] (2008–2009)
* [[User:Dfarning|David Farning]] (2008–2009)
* [[User:Tomeu|Tomeu Vizoso]] (2008-2010)
* [[User:Bernie|Bernie Innocenti]] (2008-2011)
* [[User:Alsroot|Aleksey Lim]] (2008-2012)
* [[User:Cjb|Chris Ball]] (2008-2012)
* [[User:SeanDaly|Sean Daly]] (2009–2010)
* [[User:Mchua|Mel Chua]] (2009-2011)
* [[User:Sebastian|Sebastian Silva]] (2010-2012)
* [[User:Gardito|Gerald Ardito]] (2013–2014)
* [[User:Francis|Daniel Francis]] (-2015)
* [[User:Cjl|Chris Leonard]] (-2015)
* [[User:Godiard|Gonzalo Odiard]] (-2015)

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

[[Category:Oversight board]]
[[Category:Governance]]

[[Category:Team]]

Oversight Board/Decisions

2016-07-01T05:32:09Z

Davelab6: Strike out potentially invalid motions.

This page (largely complete) is intended to be a one-stop place for reviewing all of the Sugar Labs oversight board (SLOB) actions and decisions.

The date headlines are the date that the motion is agreed, disagreed, or - in the case of motions to be voted on via email within 7 days of posting which did not get voted on - failed by timing out.

Due to confusion about Sugar Labs governance, during 2016 several members of the project not on the SLOB posted motions, but these were not seconded, and have been struck out to show they were considered by some SLOB members are invalid.

== 2016-06-30 ==
;<s>MEMBER MOTION 2016-40 Dave Crossland</s>: <s>To append to existing bylaw for Finance Manager new procedures.</s>
;<s>MEMBER MOTION 2016-39 Dave Crossland</s>: <s>To replace existing bylaw for Finance Manager.</s>

== 2016-06-14 ==
;<s>MEMBER MOTION 2016-38 Dave Crossland</s>: <s>to consider email votes on motions only valid if they are sent to both the SLOBs and IAEP mailing lists. (not seconded)</s>

== 2016-06-11 ==
;<s>MEMBER MOTION 2016-37 Dave Crossland, posting motion initially drafted by Tony Anderson</s>: <s>to undertake a fund raising drive. Arrangements will be made to enable on-line contributions by PayPal, debit or credit card or other means. Once the means to make contributions is in place, the Financial Manager will initiate and lead the drive. The Sugar Labs web site will show progress in donations toward the goal. (not seconded)</s>

== 2016-06-10 ==
;<s>MEMBER MOTION 2016-36 Dave Crossland</s>: <s>to vote on each motion proposed by a member, dropping the current practice of requiring a seconding before voting. (not seconded)</s>
;<s>MEMBER MOTION 2016-35 Dave Crossland</s>: <s>to agree the following procedure for all future monthly SLOB meetings: the chair will confirm the meeting meets quorum; the chair will make any announcements submitted to them before the meeting; the chair will announce the first motion pending a vote on that day; each present SLOB member will announce their vote; the chair will announce the outcome of the motion; the chair will announce the next motion, until all motions are voted on; the chair will invite everyone attending to an open discussion of any topic until the meeting ends at the time scheduled. (not seconded)</s>
;AGREED MOTION 2016-34 Walter Bender, posting motion initially drafted by Dave Crossland: Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (5 votes for, 1 against, 1 abstain, see http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg16711.html)
;<s>MEMBER MOTION 2016-33 Laura Vargas</s>: <s>to update current SL vision statement ("About Sugar Labs(R): Sugar Labs(R) is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs(R) is supported by donations and is seeking funding to accelerate development.") to the new proposed text: "Sugar Labs is a global community where you can learn how to design, develop and deploy high-quality Free/Libre Software that facilitates self-discovery learning experiences and collaboration among young children of all continents." (not seconded)</s>

== 2016-06-09 ==
;<s>MEMBER MOTION 2016-32 Dave Crossland</s>: <s>The value of $Y in the Finance Manager Guidelines should be $200 (not seconded)</s>

== 2016-06-03 ==

[http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-06-03T19:01:08|IRC log]
;FAILED MOTION 2016-31 Walter Bender, posting motion initially drafted by Dave Crossland: To adopt the [https://wiki.sugarlabs.org/index.php?title=Vision_proposal_2016&oldid=98911 Vision proposal 2016]. (not seconded)
;<s>MEMBER MOTION 2016-30 Dave Crossland</s>: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa <s>To add to the bylaws a new section, “Sugar Labs Oversight Board Spending Guidelines”</s>] <s>(dependent upon MOTION 2016-27)</s>
;<s>MEMBER MOTION 2016-29 Dave Crossland</s>: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa <s>To append the following text to the existing bylaw for the Finance Manager office</s>] <s>(dependent upon MOTION 2016-27)</s>
;FAILED MOTION 2016-28 Walter Bender, posting motion initially drafted by Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To define procedures for requesting, obtaining, and reporting use of SugarLabs funds] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-27 Walter Bender, posting motion initially drafted by Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded)

== 2016-05-29 ==

;<s>MEMBER MOTION 2016-26 Dave Crossland</s>: <s>To request donations from Sugar Labs Members, to be allocated to the General Fund through the SFC. The annual donation requested will be $12 USD from members who self-identify as low-income (such as students); $36, $120, or $600 USD from general members. (not seconded)</s>

;<s>MEMBER MOTION 2016-25 Dave Crossland</s>: <s>To request a membership donation from each currently active Sugar Labs Member to be allocated to the General Fund for the calendar year of 2016, and a public statement about how they use Sugar and why they are involved in Sugar Labs to post on the website; there is no penalty for not paying a membership or not providing a statement; by default members who donate will be kept private, and requested to opt-in to be recognised. The donation requested will be $12 USD from members who self-identify as low-income (such as students); $36 USD from general members; $120 from members who can opt-in to be placed prominently on the website; and $600 from members who can (privately if they wish) submit a release codename, subject to SLOB approval. (seconded at http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg16767.html but all SLOBs abstained)</s>

;<s>MEMBER MOTION 2016-24 Dave Crossland</s>: <s>Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (not seconded)</s>

== 2016-05-25 ==
;<s>MEMBER MOTION 2016-23 Caryl Bigenho</s>: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit <s>To define procedures for requesting, obtaining, and reporting use of SugarLabs funds</s>] <s>(dependent upon MOTION 2016-22)</s>
;<s>MEMBER MOTION 2016-22 Caryl Bigenho</s>: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit <s>To replace existing bylaw for Finance Manager</s>] <s>(not seconded)</s>

== 2016-05-12 ==
;AGREED MOTION 2016-21 Walter Bender: to reimburse Edgar Quispe for expenses incurred representing Sugar Labs at the Traducción e interpretación en las lenguas originarias del Perú meeting in Lima. The cost is $168.88. : (See http://lists.sugarlabs.org/archive/iaep/2016-May/018196.html)

== 2016-05-11 ==
;FAILED MOTION 2016-20 Walter Bender: to allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit. : (3 votes for, 1 vote against, and 4 abstains)

== 2016-05-06 ==
;AGREED MOTION 2016-19 Walter Bender, posting motion initially drafted by Dave Crossland: To pay for laboratoriosazucar.org domain registration renewal
;FAILED MOTION 2016-27 Walter Bender, posting motion initially drafted by Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded, further drafting requested)
;AGREED MOTION 2016-14 Walter Bender, posting motion initially drafted by : To fund a program to initiate the translation of Sugar into Yoruba. The work would be led by Samson Goddy and reviewed by Chris Leonard, in his role as Translation Community Manager (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052462.html]).
;AGREED MOTION 2016-13 Walter Bender, posting motion initially drafted by Dave Crossland: To update the Sugar License from GPLv2 to GPLv3 [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052552.html]
;FAILED MOTION 2016-12 Walter Bender: To allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052463.html]).
;FAILED MOTION 2016-11 Lionel Laske: To adopt the wiki Vision proposal for 2016 (not seconded)

== 2016-04-09 ==
;AGREED MOTION 2016-10 Walter Bender: To offer Devin U. an honorarium ($500) to compensate him since he needed to take a week off from work to run two Turtle/Music Blocks workshops at the Constructionism Conference. The funds would be allocated from the Trip Advisor grant which are in support of promoting and advancing Turtle Blocks around the world. (Vote taken by email.)
;AGREED MOTION 2016-09 Walter Bender: Walter, as PI of the Trip Advisor grant, will inform the SL oversight board of his plans for workshops that fall under the guise promotion of Turtle Blocks but otherwise has discretion in organizing and funding these events, within the budget constraints of grant and the travel guidelines of the SFC. (Vote taken by email.)

== 2016-04-07 ==
;<s>MEMBER MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference])</s>: <s>All funds raised by any Sugar Labs community member in the name of Sugar Project's translations must be directed to the “Sugar Projects Translation's Fund”. (not seconded)</s>
;<s>MEMBER MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference])</s>: <s>The present SugarLabs Oversight board appoints the current Translation's Committee, with the full responsability of reviewing, upgrading, approving and overseeing Sugar Translation Projects and Proposals made by any interested party, with special attention to Native Languages communities. (not seconded)</s>
;<s>MEMBER MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference])</s>: <s>Requests for funds will be presented to the Translation's Committee, in writing, with copy to the IAEP mailing list and the Localization mailing list, at least 72 hours in advance of the monthly scheduled "Translation Committee Meeting". Committe members shall vote during the meeting for approval by simple majority. All interested parties, must also send the proposal to the IAEP mailing list and the Localization mailing list, in advance. (not seconded)</s>

== 2016-04-06 ==
;AGREED MOTION 2016-08: To approve the position of Translation-Community Manager as described at [[Translation-Community Manager]].
;AGREED MOTION 2016-07: That Chris Leonard be named to this position effective immediately.
;AGREED MOTION 2016-06: That the Translation-Community Manager be paid a stipend of $1000/month.

== 2016-04-01 ==
;AGREED MOTION 2016-05: In keeping with the board 2010's decision on this matter from a different era, it was suggest that if a Board Member (1) fails to vote and attend pre-scheduled Board meetings for more than 12 weeks, (2) resigns or (3) dies, then the Board is empowered and encouraged to appoint a replacement for this seat. Finally, just a clarification that the Replacement Board Member would be required to defend their seat during the very next election.

== 2016-03-04 ==
;AGREED MOTION 2016-04: Based on [[Translation Proposal]], Tony (and other SLOB members) should write up a job description with goals and reporting structure for a coordinator position to be submitted to the SFC.
;AGREED MOTION 2016-03: Restrict email voting to 1 week going forward, to remove confusion from the current voting process, keeping focus. Board members' email votes would be required to arrive within One Week Maximum (168.0 hours) of the original motion. (Any motion that fails to pass within this 1-week sunset period, can of course be attempted again in future, e.g. if long-term overseas/off-grid/medical absences require another later vote on the same topic).

== 2016-02-12 ==
;AGREED MOTION 2016-02: Moving regular SLOB meeting dates to the first Friday of the month at 16UTC
;AGREED MOTION 2016-01: Apply for GSoC 2016 (Lionel and Walter as co-admins)

== 2015-12-17 ==
;FAILED MOTION 2015-07(3 In Favor, 4 Abstentions): to pay Devin Ulibarri $500 for help organize and run the Turtle workshop in Bangkok
(See renewed motion passed on 2016-04-09.)

== 2015-10-12 ==
;AGREED MOTION 2015-06: Apply to GCI

== 2015-09-14 ==
;AGREED MOTION 2015-05: funding to file an affidavits required to maintain the registration of Sugar Labs' trademarks with the USPTO.
;ACTION: Walter to recruit mentors for GCI

== 2015-07-06 ==
;ACTION: acknowledged the numerous contributions to Sugar from the late Marco Presenti Gritti.

== 2015-05-06 ==
;AGREED MOTION 2015-04: via email to add Samson Goody to the Membership Committee (DONE)

== 2015-05-04 ==
;AGREED MOTION 2015-03: to share survey results with community (DONE)
;ACTION: Gonzalo to post results (DONE)
;ACTION: Gonzalo to write to each of the respondents
;AGREED MOTION 2015-02: that Claudia and Walter go to NI to discuss Sugar/OLPC future with the Zamoras
;ACTION: Walter to make a first pass at culling the decisions from past meetings into one page (this page)

== 2015-04-06 ==
;AGREED MOTION 2015-01: appoint Icarito and Caryl to the election committee and to try to recruit a youth member to the committee.

== 2015-01-14 ==
;ACTION: organize a summit to discuss the future of Sugar
;ACTION: do a survey to solicit feedback from deployments
0
== 2014-10-07 ==
;ACTION: Recruit mentors for GCI
;ACTION: Recruit candidates for oversight board

== 2014-07-08 ==
;AGREED MOTION 2014-02: on a .UY venue for a summit in September 2014. Jose Miguel and Daniel will get back to us about specifics.

== 2014-03-03 ==
;ACTION: everyone solicit students for GSoC

== 2014-02-05 ==
;AGREED MOTION 2014-01: to Gonzalo and Manuq's proposal for Background Image Contest

== 2013-11-04 ==
;AGREED MOTION 2013-06: Luke to run election for oversight board again
;AGREED MOTION 2013-05: to give cjl discretion over the i18n funds in the Trip Advisor grant

== 2013-10-18 ==
;AGREED MOTION 2013-04: we would apply again to Google Code In

== 2013-03-21 ==
;AGREED MOTION 2013-03: the next release will be Sugar 1.0

== 2013-02-25 ==
;AGREED MOTION 2013-02: to establish a category for Sugar Labs advisors/educators/friends
;ACTION: Claudia and Walter will meet to start planning Turtle Art Day
;AGREED MOTION 2013-01: to apply for Google Summer of Code 2013

== 2013-01-07 ==
;ACTION: ClaudiaU agreed to share ''Making Learning Visible'' with SLOB members (and Tonyf and JT4Sugar)

== 2012-05-30 ==
;AGREED MOTION 2012-05: to modify the Trademark and Local Labs pages in the wiki (See [[/Oversight_Board/Meeting_Minutes-2012-05-30#1._Updates_to_the_TM_policy_.28Trademark.29|TM Policy]] and [[Oversight_Board/Meeting_Minutes-2012-05-30#2._Updates_to_the_Local_Lab_wiki_.28Local_Labs.29|Local Labs Policy]])

== 2012-05-03 ==
;AGREED MOTION 2012-04: We approved a budget of up to US $5000 for two servers.
;AGREED MOTION 2012-03: Sugar Labs joins the SFC GPL enforcement program
;ACTION MOTION 2012-02: Walter to bring code-of-conduct discussion to the community.
;ACTION MOTION 2012-01: SLOB members to get signed agreements to the SFC regarding new SFC by-laws.

== 2011-12-02 ==
;AGREED MOTION 2011-09: The Sugar Labs Oversight Board thanked Bernie Innocenti and Mel Chua for their dedicated service to the community in their role as members of the oversight board.

== 2011-09-16 ==
;AGREED MOTION 2011-08: to keep the GSoC 2010 mentor funds as our general funds.

== 2011-08-05 ==
;AGREED MOTION 2011-07: to award Sugar participation certificates (See [[Oversight_Board/2011/Meeting_Minutes-2011-08-05#Certificate_program|Certificate Program]]).
;AGREED MOTION 2011-06: to give North Dakota State University authority to establish a local Sugar Lab.

== 2011-06-09 ==
;AGREED MOTION 2011-05: to endorse Free Software as defined here: http://www.gnu.org/philosophy/free-sw.html

== 2011-05-08 ==
;AGREED MOTION 2011-04: Bernie (head of infrastructure team) is authorized to approve spending tickets filed on the bug tracker up to $200.
;AGREED MOTION 2011-03: to update the governance page.

== 2011-02-10 ==
;AGREED MOTION 2011-02: SL endorses the idea that community members have kids: means more Sugar hackers in the future !!
;AGREED MOTION 2011-01: Local labs can issue Sugar certificates (and charge for this service whatever they want) but only if: (1) they maintain a page on our wiki explaining what content they use for training, where to download it, and what pricing they use; and (2) all the content they use for training is licensed under one of the licenses recommend by http://opensource.org/docs/osd and/or http://fedoraproject.org/wiki/[…]ing#Good_Licenses.

== 2010-12-13 ==
;AGREED MOTION 2010-10: [[Oversight_Board/Project_Motion]]
;AGREED MOTION 2010-09: SL would like to acknowledge and celebrate the marriage of acaire11 and icarito : the first Sugar marriage!!!

== 2010-12-01 ==
;AGREED MOTION 2010-08: Each active team and local lab should propose a few delegates from that team to SLOBs. We will invite the delegates to SLOBs meetings, and rotate scheduled times during SLOBs meetings to hear reports from their team or lab.
;AGREED MOTION 2010-07: The default time/day of the week for SLOBs meetings will be Thursdays at 15:00 EST (20:00 UTC)
;AGREED MOTION 2010-06: If a SLOB member misses one month of regular weekly meetings in a row, twice during one calendar year, SLOBs may find a replacement for their seat.

== 2010-09-28 ==
;AGREED MOTION 2010-05: We, the SLOB, acknowledge and praise the efforts of the release team for bringing us 0.90!!

== 2010-05-07 ==
;AGREED MOTION 2010-04: to a [[Trademark]] policy.

== 2010-03-05 ==
;AGREED MOTION 2010-03: (1) Bundles with non-Sugar dependencies be clearly marked in ASLO; (2) We work towards a mechanism for supporting access to non-Sugar dependencies--a specific endorsement of being open; and (3) We do not restrict ASLO while we progress towards #2.

== 2010-02-26 ==
;AGREED MOTION 2010-02: to authorize Bernie to spec out a machine around $2000, send details to systems@ for review, decide exactly where it will be hosted, then buy it.

== 2010-01-22 ==
;AGREED MOTION 2010-01: to authorize Luke Faraone to ship some used hardware from the Wikipedia Foundation (12 servers) to various hosting sites. The cost should not exceed US$300.

== 2009-12-18 ==
;AGREED MOTION 2009-18: Sugar Labs encourages all GNU/Linux distributions to package and distribute Sugar, and if possible will assist with hosting and infrastructure. SL Marketing may strategically decide to focus resources towards specific distributions in the interest of promoting Sugar more effectively.
;AGREED MOTION 2009-17: Yes, "Sugar on a Stick" should be reserved by Sugar Labs for use by the SoaS-Fedora distribution so that Sugar can be marketed effectively, until such time when a trademark policy, agreement, and process is put in place: SoaS will be the first project to go through that process.

== 2009-12-11 ==
;AGREED MOTION 2009-16: to adopt http://opensource.org/docs/osd as a set of guidelines for what is permitted on ASLO, for both software and content, and http://fedoraproject.org/wiki/Licensing#Good_Licenses's opinions on specific licenses where applicable, and always asking the SFC for advice when a particular license is under question.
;AGREED MOTION 2009-15: SL is and should be a GNU/Linux distributor.
;AGREED MOTION 2009-14: SL wishes to spread the use of Sugar and consequently works with GNU/Linux distros to produce and offer downloadable versions. This work can include helping to promote distros, and hosting them.
;AGREED MOTION 2009-13: SL should not be completely neutral about promoting distros, but it should only choose to more strongly promote a distro based on technical merit and maintainer activity, and should publish the criteria it uses for making that decision. Furthermore, SL should be neutral about providing infrastructure resources (hosting, etc) to distros."

== 2009-12-04 ==
;AGREED MOTION 2009-12: when a DP fails to meet a deadline, the decision passes to SLOBs.

== 2009-11-20 ==
;AGREED MOTION 2009-11: Close the slobs@ list to just SLOBs, move current slobs@ traffic to iaep@ with a [SLOBS] subject line tag where at all possible.
;AGREED MOTION 2009-10: Give a two-week deadline to the Soas DP

== 2009-09-25 ==
;AGREED MOTION 2009-09: We appointed a decision panel (by a vote of 3 for, 0 against, 1 abstain, 3 absent) with the following mandate:
:"Investigate the situation of how SoaS should be treated by Sugar Labs, and related questions, including answers to the following:
:"Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"
:"Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
:"Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"
:Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"

== 2008-09-05 ==
;AGREED MOTION 2009-08: The Oversight Board acknowledged and celebrated the great job Simon has been doing on managing the 0.82 release.

== 2009-07-18 ==
;AGREED MOTION 2009-07: There was consensus that we have made sufficient outreach to the community that the initial list is a fair representation of Sugar Labs; we look forward to having the Membership Committee take it from http://selectricity.org/
;AGREED MOTION 2009-06: There was consensus that Walter would put together a strawman election process based upon the Selectricity tool. We are targeting an August election.
;AGREED MOTION 2009-05: There was consensus that we begin with just Oversight and Members committees.
;AGREED MOTION 2009-04: We agreed for the need to solicit more feedback in the wiki for the design direction being proposed by Luca.
;AGREED MOTION 2009-03: We agreed that further discussions with the SFLA about the merits of trademark protection is needed.
;AGREED MOTION 2009-02: We agreed on the desirability of Sugar Labs participation at conferences around the world, but hope to meet the need by utilizing locals to whatever extent possible. We also discussed the desirability to have a meeting of Sugar Labs developers a couple of times per year. We discussed the possibility of an on-line meeting that leverages resources above and beyond IRC.
;AGREED MOTION 2009-01: on the necessity of Sugar Labs participation in the learning community, but don't yet have a good handle on the best and most efficient means of accomplishing this.

Oversight Board/Decisions

2016-06-30T16:48:33Z

Davelab6: add 2 motions

This page (largely complete) is intended to be a one-stop place for reviewing all of the Sugar Labs oversight board (SLOB) actions and decisions.

The date headlines are the date that the motion is agreed, disagreed, or - in the case of motions to be voted on via email within 7 days of posting which did not get voted on - failed by timing out.

== 2016-06-30 ==
;PENDING MOTION 2016-40 Dave Crossland: To append to existing bylaw for Finance Manager new procedures.
;PENDING MOTION 2016-39 Dave Crossland: To replace existing bylaw for Finance Manager.

== 2016-06-14 ==
;FAILED MOTION 2016-38 Dave Crossland: to consider email votes on motions only valid if they are sent to both the SLOBs and IAEP mailing lists. (not seconded)

== 2016-06-11 ==
;FAILED MOTION 2016-37 Tony Anderson: to undertake a fund raising drive. Arrangements will be made to enable on-line contributions by PayPal, debit or credit card or other means. Once the means to make contributions is in place, the Financial Manager will initiate and lead the drive. The Sugar Labs web site will show progress in donations toward the goal. (not seconded)

== 2016-06-10 ==
;FAILED MOTION 2016-36 Dave Crossland: to vote on each motion proposed by a member, dropping the current practice of requiring a seconding before voting. (not seconded)
;FAILED MOTION 2016-35 Dave Crossland: to agree the following procedure for all future monthly SLOB meetings: the chair will confirm the meeting meets quorum; the chair will make any announcements submitted to them before the meeting; the chair will announce the first motion pending a vote on that day; each present SLOB member will announce their vote; the chair will announce the outcome of the motion; the chair will announce the next motion, until all motions are voted on; the chair will invite everyone attending to an open discussion of any topic until the meeting ends at the time scheduled. (not seconded)
;AGREED MOTION 2016-34 Dave Crossland: Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (5 votes for, 1 against, 1 abstain, see http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg16711.html)
;FAILED MOTION 2016-33 Laura Vargas: to update current SL vision statement ("About Sugar Labs(R): Sugar Labs(R) is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs(R) is supported by donations and is seeking funding to accelerate development.") to the new proposed text: "Sugar Labs is a global community where you can learn how to design, develop and deploy high-quality Free/Libre Software that facilitates self-discovery learning experiences and collaboration among young children of all continents." (not seconded)

== 2016-06-09 ==
;FAILED MOTION 2016-32 Dave Crossland: The value of $Y in the Finance Manager Guidelines should be $200 (not seconded)

== 2016-06-03 ==

[http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-06-03T19:01:08|IRC log]
;FAILED MOTION 2016-31 Dave Crossland: To adopt the [https://wiki.sugarlabs.org/index.php?title=Vision_proposal_2016&oldid=98911 Vision proposal 2016]. (not seconded)
;FAILED MOTION 2016-30 Dave Crossland: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa To add to the bylaws a new section, “Sugar Labs Oversight Board Spending Guidelines”] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-29 Dave Crossland: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa To append the following text to the existing bylaw for the Finance Manager office] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-28 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To define procedures for requesting, obtaining, and reporting use of SugarLabs funds] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-27 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded)

== 2016-05-29 ==

;FAILED MOTION 2016-26 Dave Crossland: To request donations from Sugar Labs Members, to be allocated to the General Fund through the SFC. The annual donation requested will be $12 USD from members who self-identify as low-income (such as students); $36, $120, or $600 USD from general members. (not seconded)

;FAILED MOTION 2016-25 Dave Crossland: To request a membership donation from each currently active Sugar Labs Member to be allocated to the General Fund for the calendar year of 2016, and a public statement about how they use Sugar and why they are involved in Sugar Labs to post on the website; there is no penalty for not paying a membership or not providing a statement; by default members who donate will be kept private, and requested to opt-in to be recognised. The donation requested will be $12 USD from members who self-identify as low-income (such as students); $36 USD from general members; $120 from members who can opt-in to be placed prominently on the website; and $600 from members who can (privately if they wish) submit a release codename, subject to SLOB approval. (seconded at http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg16767.html but all SLOBs abstained)

;FAILED MOTION 2016-24 Dave Crossland: Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (not seconded)

== 2016-05-25 ==
;FAILED MOTION 2016-23 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To define procedures for requesting, obtaining, and reporting use of SugarLabs funds] (dependent upon MOTION 2016-22)
;FAILED MOTION 2016-22 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded)

== 2016-05-12 ==
;AGREED MOTION 2016-21 Walter Bender: to reimburse Edgar Quispe for expenses incurred representing Sugar Labs at the Traducción e interpretación en las lenguas originarias del Perú meeting in Lima. The cost is $168.88. (See http://lists.sugarlabs.org/archive/iaep/2016-May/018196.html)

== 2016-05-11 ==
;FAILED MOTION 2016-20: to allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit. (3 votes for, 1 vote against, and 4 abstains)

== 2016-05-06 ==
;AGREED MOTION 2016-19: To pay for laboratoriosazucar.org domain registration renewal
;FAILED MOTION 2016-27 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded, further drafting requested)
;AGREED MOTION 2016-14: To fund a program to initiate the translation of Sugar into Yoruba. The work would be led by Samson Goddy and reviewed by Chris Leonard, in his role as Translation Community Manager (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052462.html]).
;AGREED MOTION 2016-13 Dave Crossland: To update the Sugar License from GPLv2 to GPLv3 [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052552.html]
;FAILED MOTION 2016-12: To allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052463.html]).
;FAILED MOTION 2016-11 Lionel Laske: To adopt the wiki Vision proposal for 2016 (not seconded)

== 2016-04-09 ==
;AGREED MOTION 2016-10 Walter Bender: To offer Devin U. an honorarium ($500) to compensate him since he needed to take a week off from work to run two Turtle/Music Blocks workshops at the Constructionism Conference. The funds would be allocated from the Trip Advisor grant which are in support of promoting and advancing Turtle Blocks around the world. (Vote taken by email.)
;AGREED MOTION 2016-09 Walter Bender: Walter, as PI of the Trip Advisor grant, will inform the SL oversight board of his plans for workshops that fall under the guise promotion of Turtle Blocks but otherwise has discretion in organizing and funding these events, within the budget constraints of grant and the travel guidelines of the SFC. (Vote taken by email.)

== 2016-04-07 ==
;FAILED MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): All funds raised by any Sugar Labs community member in the name of Sugar Project's translations must be directed to the “Sugar Projects Translation's Fund”. (not seconded)
;FAILED MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): The present SugarLabs Oversight board appoints the current Translation's Committee, with the full responsability of reviewing, upgrading, approving and overseeing Sugar Translation Projects and Proposals made by any interested party, with special attention to Native Languages communities. (not seconded)
;FAILED MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): Requests for funds will be presented to the Translation's Committee, in writing, with copy to the IAEP mailing list and the Localization mailing list, at least 72 hours in advance of the monthly scheduled "Translation Committee Meeting". Committe members shall vote during the meeting for approval by simple majority. All interested parties, must also send the proposal to the IAEP mailing list and the Localization mailing list, in advance. (not seconded)

== 2016-04-06 ==
;AGREED MOTION 2016-08: To approve the position of Translation-Community Manager as described at [[Translation-Community Manager]].
;AGREED MOTION 2016-07: That Chris Leonard be named to this position effective immediately.
;AGREED MOTION 2016-06: That the Translation-Community Manager be paid a stipend of $1000/month.

== 2016-04-01 ==
;AGREED MOTION 2016-05: In keeping with the board 2010's decision on this matter from a different era, it was suggest that if a Board Member (1) fails to vote and attend pre-scheduled Board meetings for more than 12 weeks, (2) resigns or (3) dies, then the Board is empowered and encouraged to appoint a replacement for this seat. Finally, just a clarification that the Replacement Board Member would be required to defend their seat during the very next election.

== 2016-03-04 ==
;AGREED MOTION 2016-04: Based on [[Translation Proposal]], Tony (and other SLOB members) should write up a job description with goals and reporting structure for a coordinator position to be submitted to the SFC.
;AGREED MOTION 2016-03: Restrict email voting to 1 week going forward, to remove confusion from the current voting process, keeping focus. Board members' email votes would be required to arrive within One Week Maximum (168.0 hours) of the original motion. (Any motion that fails to pass within this 1-week sunset period, can of course be attempted again in future, e.g. if long-term overseas/off-grid/medical absences require another later vote on the same topic).

== 2016-02-12 ==
;AGREED MOTION 2016-02: Moving regular SLOB meeting dates to the first Friday of the month at 16UTC
;AGREED MOTION 2016-01: Apply for GSoC 2016 (Lionel and Walter as co-admins)

== 2015-12-17 ==
;FAILED MOTION 2015-07(3 In Favor, 4 Abstentions): to pay Devin Ulibarri $500 for help organize and run the Turtle workshop in Bangkok
(See renewed motion passed on 2016-04-09.)

== 2015-10-12 ==
;AGREED MOTION 2015-06: Apply to GCI

== 2015-09-14 ==
;AGREED MOTION 2015-05: funding to file an affidavits required to maintain the registration of Sugar Labs' trademarks with the USPTO.
;ACTION: Walter to recruit mentors for GCI

== 2015-07-06 ==
;ACTION: acknowledged the numerous contributions to Sugar from the late Marco Presenti Gritti.

== 2015-05-06 ==
;AGREED MOTION 2015-04: via email to add Samson Goody to the Membership Committee (DONE)

== 2015-05-04 ==
;AGREED MOTION 2015-03: to share survey results with community (DONE)
;ACTION: Gonzalo to post results (DONE)
;ACTION: Gonzalo to write to each of the respondents
;AGREED MOTION 2015-02: that Claudia and Walter go to NI to discuss Sugar/OLPC future with the Zamoras
;ACTION: Walter to make a first pass at culling the decisions from past meetings into one page (this page)

== 2015-04-06 ==
;AGREED MOTION 2015-01: appoint Icarito and Caryl to the election committee and to try to recruit a youth member to the committee.

== 2015-01-14 ==
;ACTION: organize a summit to discuss the future of Sugar
;ACTION: do a survey to solicit feedback from deployments
0
== 2014-10-07 ==
;ACTION: Recruit mentors for GCI
;ACTION: Recruit candidates for oversight board

== 2014-07-08 ==
;AGREED MOTION 2014-02: on a .UY venue for a summit in September 2014. Jose Miguel and Daniel will get back to us about specifics.

== 2014-03-03 ==
;ACTION: everyone solicit students for GSoC

== 2014-02-05 ==
;AGREED MOTION 2014-01: to Gonzalo and Manuq's proposal for Background Image Contest

== 2013-11-04 ==
;AGREED MOTION 2013-06: Luke to run election for oversight board again
;AGREED MOTION 2013-05: to give cjl discretion over the i18n funds in the Trip Advisor grant

== 2013-10-18 ==
;AGREED MOTION 2013-04: we would apply again to Google Code In

== 2013-03-21 ==
;AGREED MOTION 2013-03: the next release will be Sugar 1.0

== 2013-02-25 ==
;AGREED MOTION 2013-02: to establish a category for Sugar Labs advisors/educators/friends
;ACTION: Claudia and Walter will meet to start planning Turtle Art Day
;AGREED MOTION 2013-01: to apply for Google Summer of Code 2013

== 2013-01-07 ==
;ACTION: ClaudiaU agreed to share ''Making Learning Visible'' with SLOB members (and Tonyf and JT4Sugar)

== 2012-05-30 ==
;AGREED MOTION 2012-05: to modify the Trademark and Local Labs pages in the wiki (See [[/Oversight_Board/Meeting_Minutes-2012-05-30#1._Updates_to_the_TM_policy_.28Trademark.29|TM Policy]] and [[Oversight_Board/Meeting_Minutes-2012-05-30#2._Updates_to_the_Local_Lab_wiki_.28Local_Labs.29|Local Labs Policy]])

== 2012-05-03 ==
;AGREED MOTION 2012-04: We approved a budget of up to US $5000 for two servers.
;AGREED MOTION 2012-03: Sugar Labs joins the SFC GPL enforcement program
;ACTION MOTION 2012-02: Walter to bring code-of-conduct discussion to the community.
;ACTION MOTION 2012-01: SLOB members to get signed agreements to the SFC regarding new SFC by-laws.

== 2011-12-02 ==
;AGREED MOTION 2011-09: The Sugar Labs Oversight Board thanked Bernie Innocenti and Mel Chua for their dedicated service to the community in their role as members of the oversight board.

== 2011-09-16 ==
;AGREED MOTION 2011-08: to keep the GSoC 2010 mentor funds as our general funds.

== 2011-08-05 ==
;AGREED MOTION 2011-07: to award Sugar participation certificates (See [[Oversight_Board/2011/Meeting_Minutes-2011-08-05#Certificate_program|Certificate Program]]).
;AGREED MOTION 2011-06: to give North Dakota State University authority to establish a local Sugar Lab.

== 2011-06-09 ==
;AGREED MOTION 2011-05: to endorse Free Software as defined here: http://www.gnu.org/philosophy/free-sw.html

== 2011-05-08 ==
;AGREED MOTION 2011-04: Bernie (head of infrastructure team) is authorized to approve spending tickets filed on the bug tracker up to $200.
;AGREED MOTION 2011-03: to update the governance page.

== 2011-02-10 ==
;AGREED MOTION 2011-02: SL endorses the idea that community members have kids: means more Sugar hackers in the future !!
;AGREED MOTION 2011-01: Local labs can issue Sugar certificates (and charge for this service whatever they want) but only if: (1) they maintain a page on our wiki explaining what content they use for training, where to download it, and what pricing they use; and (2) all the content they use for training is licensed under one of the licenses recommend by http://opensource.org/docs/osd and/or http://fedoraproject.org/wiki/[…]ing#Good_Licenses.

== 2010-12-13 ==
;AGREED MOTION 2010-10: [[Oversight_Board/Project_Motion]]
;AGREED MOTION 2010-09: SL would like to acknowledge and celebrate the marriage of acaire11 and icarito : the first Sugar marriage!!!

== 2010-12-01 ==
;AGREED MOTION 2010-08: Each active team and local lab should propose a few delegates from that team to SLOBs. We will invite the delegates to SLOBs meetings, and rotate scheduled times during SLOBs meetings to hear reports from their team or lab.
;AGREED MOTION 2010-07: The default time/day of the week for SLOBs meetings will be Thursdays at 15:00 EST (20:00 UTC)
;AGREED MOTION 2010-06: If a SLOB member misses one month of regular weekly meetings in a row, twice during one calendar year, SLOBs may find a replacement for their seat.

== 2010-09-28 ==
;AGREED MOTION 2010-05: We, the SLOB, acknowledge and praise the efforts of the release team for bringing us 0.90!!

== 2010-05-07 ==
;AGREED MOTION 2010-04: to a [[Trademark]] policy.

== 2010-03-05 ==
;AGREED MOTION 2010-03: (1) Bundles with non-Sugar dependencies be clearly marked in ASLO; (2) We work towards a mechanism for supporting access to non-Sugar dependencies--a specific endorsement of being open; and (3) We do not restrict ASLO while we progress towards #2.

== 2010-02-26 ==
;AGREED MOTION 2010-02: to authorize Bernie to spec out a machine around $2000, send details to systems@ for review, decide exactly where it will be hosted, then buy it.

== 2010-01-22 ==
;AGREED MOTION 2010-01: to authorize Luke Faraone to ship some used hardware from the Wikipedia Foundation (12 servers) to various hosting sites. The cost should not exceed US$300.

== 2009-12-18 ==
;AGREED MOTION 2009-18: Sugar Labs encourages all GNU/Linux distributions to package and distribute Sugar, and if possible will assist with hosting and infrastructure. SL Marketing may strategically decide to focus resources towards specific distributions in the interest of promoting Sugar more effectively.
;AGREED MOTION 2009-17: Yes, "Sugar on a Stick" should be reserved by Sugar Labs for use by the SoaS-Fedora distribution so that Sugar can be marketed effectively, until such time when a trademark policy, agreement, and process is put in place: SoaS will be the first project to go through that process.

== 2009-12-11 ==
;AGREED MOTION 2009-16: to adopt http://opensource.org/docs/osd as a set of guidelines for what is permitted on ASLO, for both software and content, and http://fedoraproject.org/wiki/Licensing#Good_Licenses's opinions on specific licenses where applicable, and always asking the SFC for advice when a particular license is under question.
;AGREED MOTION 2009-15: SL is and should be a GNU/Linux distributor.
;AGREED MOTION 2009-14: SL wishes to spread the use of Sugar and consequently works with GNU/Linux distros to produce and offer downloadable versions. This work can include helping to promote distros, and hosting them.
;AGREED MOTION 2009-13: SL should not be completely neutral about promoting distros, but it should only choose to more strongly promote a distro based on technical merit and maintainer activity, and should publish the criteria it uses for making that decision. Furthermore, SL should be neutral about providing infrastructure resources (hosting, etc) to distros."

== 2009-12-04 ==
;AGREED MOTION 2009-12: when a DP fails to meet a deadline, the decision passes to SLOBs.

== 2009-11-20 ==
;AGREED MOTION 2009-11: Close the slobs@ list to just SLOBs, move current slobs@ traffic to iaep@ with a [SLOBS] subject line tag where at all possible.
;AGREED MOTION 2009-10: Give a two-week deadline to the Soas DP

== 2009-09-25 ==
;AGREED MOTION 2009-09: We appointed a decision panel (by a vote of 3 for, 0 against, 1 abstain, 3 absent) with the following mandate:
:"Investigate the situation of how SoaS should be treated by Sugar Labs, and related questions, including answers to the following:
:"Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"
:"Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
:"Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"
:Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"

== 2008-09-05 ==
;AGREED MOTION 2009-08: The Oversight Board acknowledged and celebrated the great job Simon has been doing on managing the 0.82 release.

== 2009-07-18 ==
;AGREED MOTION 2009-07: There was consensus that we have made sufficient outreach to the community that the initial list is a fair representation of Sugar Labs; we look forward to having the Membership Committee take it from http://selectricity.org/
;AGREED MOTION 2009-06: There was consensus that Walter would put together a strawman election process based upon the Selectricity tool. We are targeting an August election.
;AGREED MOTION 2009-05: There was consensus that we begin with just Oversight and Members committees.
;AGREED MOTION 2009-04: We agreed for the need to solicit more feedback in the wiki for the design direction being proposed by Luca.
;AGREED MOTION 2009-03: We agreed that further discussions with the SFLA about the merits of trademark protection is needed.
;AGREED MOTION 2009-02: We agreed on the desirability of Sugar Labs participation at conferences around the world, but hope to meet the need by utilizing locals to whatever extent possible. We also discussed the desirability to have a meeting of Sugar Labs developers a couple of times per year. We discussed the possibility of an on-line meeting that leverages resources above and beyond IRC.
;AGREED MOTION 2009-01: on the necessity of Sugar Labs participation in the learning community, but don't yet have a good handle on the best and most efficient means of accomplishing this.

Oversight Board/Decisions

2016-06-30T16:47:19Z

Davelab6: Correct abstain vote on 2016-25

This page (largely complete) is intended to be a one-stop place for reviewing all of the Sugar Labs oversight board (SLOB) actions and decisions.

The date headlines are the date that the motion is agreed, disagreed, or - in the case of motions to be voted on via email within 7 days of posting which did not get voted on - failed by timing out.

== 2016-06-14 ==
;FAILED MOTION 2016-38 Dave Crossland: to consider email votes on motions only valid if they are sent to both the SLOBs and IAEP mailing lists. (not seconded)

== 2016-06-11 ==
;FAILED MOTION 2016-37 Tony Anderson: to undertake a fund raising drive. Arrangements will be made to enable on-line contributions by PayPal, debit or credit card or other means. Once the means to make contributions is in place, the Financial Manager will initiate and lead the drive. The Sugar Labs web site will show progress in donations toward the goal. (not seconded)

== 2016-06-10 ==
;FAILED MOTION 2016-36 Dave Crossland: to vote on each motion proposed by a member, dropping the current practice of requiring a seconding before voting. (not seconded)
;FAILED MOTION 2016-35 Dave Crossland: to agree the following procedure for all future monthly SLOB meetings: the chair will confirm the meeting meets quorum; the chair will make any announcements submitted to them before the meeting; the chair will announce the first motion pending a vote on that day; each present SLOB member will announce their vote; the chair will announce the outcome of the motion; the chair will announce the next motion, until all motions are voted on; the chair will invite everyone attending to an open discussion of any topic until the meeting ends at the time scheduled. (not seconded)
;AGREED MOTION 2016-34 Dave Crossland: Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (5 votes for, 1 against, 1 abstain, see http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg16711.html)
;FAILED MOTION 2016-33 Laura Vargas: to update current SL vision statement ("About Sugar Labs(R): Sugar Labs(R) is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs(R) is supported by donations and is seeking funding to accelerate development.") to the new proposed text: "Sugar Labs is a global community where you can learn how to design, develop and deploy high-quality Free/Libre Software that facilitates self-discovery learning experiences and collaboration among young children of all continents." (not seconded)

== 2016-06-09 ==
;FAILED MOTION 2016-32 Dave Crossland: The value of $Y in the Finance Manager Guidelines should be $200 (not seconded)

== 2016-06-03 ==

[http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-06-03T19:01:08|IRC log]
;FAILED MOTION 2016-31 Dave Crossland: To adopt the [https://wiki.sugarlabs.org/index.php?title=Vision_proposal_2016&oldid=98911 Vision proposal 2016]. (not seconded)
;FAILED MOTION 2016-30 Dave Crossland: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa To add to the bylaws a new section, “Sugar Labs Oversight Board Spending Guidelines”] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-29 Dave Crossland: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa To append the following text to the existing bylaw for the Finance Manager office] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-28 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To define procedures for requesting, obtaining, and reporting use of SugarLabs funds] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-27 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded)

== 2016-05-29 ==

;FAILED MOTION 2016-26 Dave Crossland: To request donations from Sugar Labs Members, to be allocated to the General Fund through the SFC. The annual donation requested will be $12 USD from members who self-identify as low-income (such as students); $36, $120, or $600 USD from general members. (not seconded)

;FAILED MOTION 2016-25 Dave Crossland: To request a membership donation from each currently active Sugar Labs Member to be allocated to the General Fund for the calendar year of 2016, and a public statement about how they use Sugar and why they are involved in Sugar Labs to post on the website; there is no penalty for not paying a membership or not providing a statement; by default members who donate will be kept private, and requested to opt-in to be recognised. The donation requested will be $12 USD from members who self-identify as low-income (such as students); $36 USD from general members; $120 from members who can opt-in to be placed prominently on the website; and $600 from members who can (privately if they wish) submit a release codename, subject to SLOB approval. (seconded at http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg16767.html but all SLOBs abstained)

;FAILED MOTION 2016-24 Dave Crossland: Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (not seconded)

== 2016-05-25 ==
;FAILED MOTION 2016-23 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To define procedures for requesting, obtaining, and reporting use of SugarLabs funds] (dependent upon MOTION 2016-22)
;FAILED MOTION 2016-22 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded)

== 2016-05-12 ==
;AGREED MOTION 2016-21 Walter Bender: to reimburse Edgar Quispe for expenses incurred representing Sugar Labs at the Traducción e interpretación en las lenguas originarias del Perú meeting in Lima. The cost is $168.88. (See http://lists.sugarlabs.org/archive/iaep/2016-May/018196.html)

== 2016-05-11 ==
;FAILED MOTION 2016-20: to allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit. (3 votes for, 1 vote against, and 4 abstains)

== 2016-05-06 ==
;AGREED MOTION 2016-19: To pay for laboratoriosazucar.org domain registration renewal
;FAILED MOTION 2016-27 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded, further drafting requested)
;AGREED MOTION 2016-14: To fund a program to initiate the translation of Sugar into Yoruba. The work would be led by Samson Goddy and reviewed by Chris Leonard, in his role as Translation Community Manager (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052462.html]).
;AGREED MOTION 2016-13 Dave Crossland: To update the Sugar License from GPLv2 to GPLv3 [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052552.html]
;FAILED MOTION 2016-12: To allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052463.html]).
;FAILED MOTION 2016-11 Lionel Laske: To adopt the wiki Vision proposal for 2016 (not seconded)

== 2016-04-09 ==
;AGREED MOTION 2016-10 Walter Bender: To offer Devin U. an honorarium ($500) to compensate him since he needed to take a week off from work to run two Turtle/Music Blocks workshops at the Constructionism Conference. The funds would be allocated from the Trip Advisor grant which are in support of promoting and advancing Turtle Blocks around the world. (Vote taken by email.)
;AGREED MOTION 2016-09 Walter Bender: Walter, as PI of the Trip Advisor grant, will inform the SL oversight board of his plans for workshops that fall under the guise promotion of Turtle Blocks but otherwise has discretion in organizing and funding these events, within the budget constraints of grant and the travel guidelines of the SFC. (Vote taken by email.)

== 2016-04-07 ==
;FAILED MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): All funds raised by any Sugar Labs community member in the name of Sugar Project's translations must be directed to the “Sugar Projects Translation's Fund”. (not seconded)
;FAILED MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): The present SugarLabs Oversight board appoints the current Translation's Committee, with the full responsability of reviewing, upgrading, approving and overseeing Sugar Translation Projects and Proposals made by any interested party, with special attention to Native Languages communities. (not seconded)
;FAILED MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): Requests for funds will be presented to the Translation's Committee, in writing, with copy to the IAEP mailing list and the Localization mailing list, at least 72 hours in advance of the monthly scheduled "Translation Committee Meeting". Committe members shall vote during the meeting for approval by simple majority. All interested parties, must also send the proposal to the IAEP mailing list and the Localization mailing list, in advance. (not seconded)

== 2016-04-06 ==
;AGREED MOTION 2016-08: To approve the position of Translation-Community Manager as described at [[Translation-Community Manager]].
;AGREED MOTION 2016-07: That Chris Leonard be named to this position effective immediately.
;AGREED MOTION 2016-06: That the Translation-Community Manager be paid a stipend of $1000/month.

== 2016-04-01 ==
;AGREED MOTION 2016-05: In keeping with the board 2010's decision on this matter from a different era, it was suggest that if a Board Member (1) fails to vote and attend pre-scheduled Board meetings for more than 12 weeks, (2) resigns or (3) dies, then the Board is empowered and encouraged to appoint a replacement for this seat. Finally, just a clarification that the Replacement Board Member would be required to defend their seat during the very next election.

== 2016-03-04 ==
;AGREED MOTION 2016-04: Based on [[Translation Proposal]], Tony (and other SLOB members) should write up a job description with goals and reporting structure for a coordinator position to be submitted to the SFC.
;AGREED MOTION 2016-03: Restrict email voting to 1 week going forward, to remove confusion from the current voting process, keeping focus. Board members' email votes would be required to arrive within One Week Maximum (168.0 hours) of the original motion. (Any motion that fails to pass within this 1-week sunset period, can of course be attempted again in future, e.g. if long-term overseas/off-grid/medical absences require another later vote on the same topic).

== 2016-02-12 ==
;AGREED MOTION 2016-02: Moving regular SLOB meeting dates to the first Friday of the month at 16UTC
;AGREED MOTION 2016-01: Apply for GSoC 2016 (Lionel and Walter as co-admins)

== 2015-12-17 ==
;FAILED MOTION 2015-07(3 In Favor, 4 Abstentions): to pay Devin Ulibarri $500 for help organize and run the Turtle workshop in Bangkok
(See renewed motion passed on 2016-04-09.)

== 2015-10-12 ==
;AGREED MOTION 2015-06: Apply to GCI

== 2015-09-14 ==
;AGREED MOTION 2015-05: funding to file an affidavits required to maintain the registration of Sugar Labs' trademarks with the USPTO.
;ACTION: Walter to recruit mentors for GCI

== 2015-07-06 ==
;ACTION: acknowledged the numerous contributions to Sugar from the late Marco Presenti Gritti.

== 2015-05-06 ==
;AGREED MOTION 2015-04: via email to add Samson Goody to the Membership Committee (DONE)

== 2015-05-04 ==
;AGREED MOTION 2015-03: to share survey results with community (DONE)
;ACTION: Gonzalo to post results (DONE)
;ACTION: Gonzalo to write to each of the respondents
;AGREED MOTION 2015-02: that Claudia and Walter go to NI to discuss Sugar/OLPC future with the Zamoras
;ACTION: Walter to make a first pass at culling the decisions from past meetings into one page (this page)

== 2015-04-06 ==
;AGREED MOTION 2015-01: appoint Icarito and Caryl to the election committee and to try to recruit a youth member to the committee.

== 2015-01-14 ==
;ACTION: organize a summit to discuss the future of Sugar
;ACTION: do a survey to solicit feedback from deployments
0
== 2014-10-07 ==
;ACTION: Recruit mentors for GCI
;ACTION: Recruit candidates for oversight board

== 2014-07-08 ==
;AGREED MOTION 2014-02: on a .UY venue for a summit in September 2014. Jose Miguel and Daniel will get back to us about specifics.

== 2014-03-03 ==
;ACTION: everyone solicit students for GSoC

== 2014-02-05 ==
;AGREED MOTION 2014-01: to Gonzalo and Manuq's proposal for Background Image Contest

== 2013-11-04 ==
;AGREED MOTION 2013-06: Luke to run election for oversight board again
;AGREED MOTION 2013-05: to give cjl discretion over the i18n funds in the Trip Advisor grant

== 2013-10-18 ==
;AGREED MOTION 2013-04: we would apply again to Google Code In

== 2013-03-21 ==
;AGREED MOTION 2013-03: the next release will be Sugar 1.0

== 2013-02-25 ==
;AGREED MOTION 2013-02: to establish a category for Sugar Labs advisors/educators/friends
;ACTION: Claudia and Walter will meet to start planning Turtle Art Day
;AGREED MOTION 2013-01: to apply for Google Summer of Code 2013

== 2013-01-07 ==
;ACTION: ClaudiaU agreed to share ''Making Learning Visible'' with SLOB members (and Tonyf and JT4Sugar)

== 2012-05-30 ==
;AGREED MOTION 2012-05: to modify the Trademark and Local Labs pages in the wiki (See [[/Oversight_Board/Meeting_Minutes-2012-05-30#1._Updates_to_the_TM_policy_.28Trademark.29|TM Policy]] and [[Oversight_Board/Meeting_Minutes-2012-05-30#2._Updates_to_the_Local_Lab_wiki_.28Local_Labs.29|Local Labs Policy]])

== 2012-05-03 ==
;AGREED MOTION 2012-04: We approved a budget of up to US $5000 for two servers.
;AGREED MOTION 2012-03: Sugar Labs joins the SFC GPL enforcement program
;ACTION MOTION 2012-02: Walter to bring code-of-conduct discussion to the community.
;ACTION MOTION 2012-01: SLOB members to get signed agreements to the SFC regarding new SFC by-laws.

== 2011-12-02 ==
;AGREED MOTION 2011-09: The Sugar Labs Oversight Board thanked Bernie Innocenti and Mel Chua for their dedicated service to the community in their role as members of the oversight board.

== 2011-09-16 ==
;AGREED MOTION 2011-08: to keep the GSoC 2010 mentor funds as our general funds.

== 2011-08-05 ==
;AGREED MOTION 2011-07: to award Sugar participation certificates (See [[Oversight_Board/2011/Meeting_Minutes-2011-08-05#Certificate_program|Certificate Program]]).
;AGREED MOTION 2011-06: to give North Dakota State University authority to establish a local Sugar Lab.

== 2011-06-09 ==
;AGREED MOTION 2011-05: to endorse Free Software as defined here: http://www.gnu.org/philosophy/free-sw.html

== 2011-05-08 ==
;AGREED MOTION 2011-04: Bernie (head of infrastructure team) is authorized to approve spending tickets filed on the bug tracker up to $200.
;AGREED MOTION 2011-03: to update the governance page.

== 2011-02-10 ==
;AGREED MOTION 2011-02: SL endorses the idea that community members have kids: means more Sugar hackers in the future !!
;AGREED MOTION 2011-01: Local labs can issue Sugar certificates (and charge for this service whatever they want) but only if: (1) they maintain a page on our wiki explaining what content they use for training, where to download it, and what pricing they use; and (2) all the content they use for training is licensed under one of the licenses recommend by http://opensource.org/docs/osd and/or http://fedoraproject.org/wiki/[…]ing#Good_Licenses.

== 2010-12-13 ==
;AGREED MOTION 2010-10: [[Oversight_Board/Project_Motion]]
;AGREED MOTION 2010-09: SL would like to acknowledge and celebrate the marriage of acaire11 and icarito : the first Sugar marriage!!!

== 2010-12-01 ==
;AGREED MOTION 2010-08: Each active team and local lab should propose a few delegates from that team to SLOBs. We will invite the delegates to SLOBs meetings, and rotate scheduled times during SLOBs meetings to hear reports from their team or lab.
;AGREED MOTION 2010-07: The default time/day of the week for SLOBs meetings will be Thursdays at 15:00 EST (20:00 UTC)
;AGREED MOTION 2010-06: If a SLOB member misses one month of regular weekly meetings in a row, twice during one calendar year, SLOBs may find a replacement for their seat.

== 2010-09-28 ==
;AGREED MOTION 2010-05: We, the SLOB, acknowledge and praise the efforts of the release team for bringing us 0.90!!

== 2010-05-07 ==
;AGREED MOTION 2010-04: to a [[Trademark]] policy.

== 2010-03-05 ==
;AGREED MOTION 2010-03: (1) Bundles with non-Sugar dependencies be clearly marked in ASLO; (2) We work towards a mechanism for supporting access to non-Sugar dependencies--a specific endorsement of being open; and (3) We do not restrict ASLO while we progress towards #2.

== 2010-02-26 ==
;AGREED MOTION 2010-02: to authorize Bernie to spec out a machine around $2000, send details to systems@ for review, decide exactly where it will be hosted, then buy it.

== 2010-01-22 ==
;AGREED MOTION 2010-01: to authorize Luke Faraone to ship some used hardware from the Wikipedia Foundation (12 servers) to various hosting sites. The cost should not exceed US$300.

== 2009-12-18 ==
;AGREED MOTION 2009-18: Sugar Labs encourages all GNU/Linux distributions to package and distribute Sugar, and if possible will assist with hosting and infrastructure. SL Marketing may strategically decide to focus resources towards specific distributions in the interest of promoting Sugar more effectively.
;AGREED MOTION 2009-17: Yes, "Sugar on a Stick" should be reserved by Sugar Labs for use by the SoaS-Fedora distribution so that Sugar can be marketed effectively, until such time when a trademark policy, agreement, and process is put in place: SoaS will be the first project to go through that process.

== 2009-12-11 ==
;AGREED MOTION 2009-16: to adopt http://opensource.org/docs/osd as a set of guidelines for what is permitted on ASLO, for both software and content, and http://fedoraproject.org/wiki/Licensing#Good_Licenses's opinions on specific licenses where applicable, and always asking the SFC for advice when a particular license is under question.
;AGREED MOTION 2009-15: SL is and should be a GNU/Linux distributor.
;AGREED MOTION 2009-14: SL wishes to spread the use of Sugar and consequently works with GNU/Linux distros to produce and offer downloadable versions. This work can include helping to promote distros, and hosting them.
;AGREED MOTION 2009-13: SL should not be completely neutral about promoting distros, but it should only choose to more strongly promote a distro based on technical merit and maintainer activity, and should publish the criteria it uses for making that decision. Furthermore, SL should be neutral about providing infrastructure resources (hosting, etc) to distros."

== 2009-12-04 ==
;AGREED MOTION 2009-12: when a DP fails to meet a deadline, the decision passes to SLOBs.

== 2009-11-20 ==
;AGREED MOTION 2009-11: Close the slobs@ list to just SLOBs, move current slobs@ traffic to iaep@ with a [SLOBS] subject line tag where at all possible.
;AGREED MOTION 2009-10: Give a two-week deadline to the Soas DP

== 2009-09-25 ==
;AGREED MOTION 2009-09: We appointed a decision panel (by a vote of 3 for, 0 against, 1 abstain, 3 absent) with the following mandate:
:"Investigate the situation of how SoaS should be treated by Sugar Labs, and related questions, including answers to the following:
:"Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"
:"Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
:"Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"
:Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"

== 2008-09-05 ==
;AGREED MOTION 2009-08: The Oversight Board acknowledged and celebrated the great job Simon has been doing on managing the 0.82 release.

== 2009-07-18 ==
;AGREED MOTION 2009-07: There was consensus that we have made sufficient outreach to the community that the initial list is a fair representation of Sugar Labs; we look forward to having the Membership Committee take it from http://selectricity.org/
;AGREED MOTION 2009-06: There was consensus that Walter would put together a strawman election process based upon the Selectricity tool. We are targeting an August election.
;AGREED MOTION 2009-05: There was consensus that we begin with just Oversight and Members committees.
;AGREED MOTION 2009-04: We agreed for the need to solicit more feedback in the wiki for the design direction being proposed by Luca.
;AGREED MOTION 2009-03: We agreed that further discussions with the SFLA about the merits of trademark protection is needed.
;AGREED MOTION 2009-02: We agreed on the desirability of Sugar Labs participation at conferences around the world, but hope to meet the need by utilizing locals to whatever extent possible. We also discussed the desirability to have a meeting of Sugar Labs developers a couple of times per year. We discussed the possibility of an on-line meeting that leverages resources above and beyond IRC.
;AGREED MOTION 2009-01: on the necessity of Sugar Labs participation in the learning community, but don't yet have a good handle on the best and most efficient means of accomplishing this.

Welcome to the Sugar Labs wiki

2016-06-27T12:36:53Z

Davelab6:

__NOEDITSECTION__
__NOTOC__

{| border="0" 
|- row1
|<span class="linkgroup">[[File:Download_Mirabell.png|center|link=Downloads]]<br>[[Image:Sugarlabs_mainpage_01.png|link=Sugar Labs/Getting Involved]]</span>
| 
;First time visit?: Please take a look around our wiki. Explore the menus along the left side of the page. If you ever get lost, just click on the logo at the top left of every page and you will return to this page. See [[Wiki_Team/Resources#Sugar_Labs_Wiki_Guide|this guide]] for help with wiki editing, and check out the [[Getting Started]] page!

;Want to help?: Welcome to the Sugar Labs community! We are contributors of all types - teachers, writers, coders, designers, testers, and more - who work together from around the world on Sugar. Visit the '''[[Sugar Labs/Getting Involved | Getting Involved]]''' page, and find out how you can join in the fun of learning. We have some [[Vacancies]] and are always looking for maintainers and testers.

;Using Sugar?: Get more Activities from http://activities.sugarlabs.org

;Software Developer?: Check out our developer documentation on Github, https://github.com/sugarlabs/sugar-docs

|- row2

|}

<div style="background:#c8edff;border:1px solid #cdf; word-spacing:15px; padding: 0px 5px; font-size:100%; text-align:center" class="linkgroup">
'''[[Sugar Labs/Current Events | News]] [[Sugar Labs/Getting Involved | Join]] [[Downloads]] [[Sugar Labs/Contacts | Contact]] [[Sugar Labs | About Us]]'''
</div>

=== Community News ===

{{:Sugar_Labs/Current_Events}}

For less recent news about Sugar Labs, visit [[Sugar Labs/Current Events|Current Events]] and the [[Archive/Current Events|Current Events Archive]].
We've also archived all our Press Releases at http://www.sugarlabs.org/press and the [[News]] previously posted on this front page.

''[[Trademark|Sugar Labs<sup>®</sup>]] is a member project of the [http://www.sfconservancy.org/ Software Freedom Conservancy], a USA 501(c)(3) not-for-profit organization, and is supported by our generous [[Sugar Labs/Getting Involved|contributors]] and [[Sugar Labs/Thank You|sponsors]].''

<noinclude>
{{Translations | [[Welcome to the Sugar Labs wiki|english]] | [[Welcome to the Sugar Labs wiki/lang-es|español]] | [[Welcome to the Sugar Labs wiki/lang-pt_BR|português brasil]] | [[Welcome to the Sugar Labs wiki/lang-ps|پښتو]] | [[Welcome to the Sugar Labs wiki/lang-ru_RU|русский]]}}
</noinclude>

2016 Goals

2016-06-27T12:13:18Z

Davelab6: add req for all grants to be online;

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to liberate the ''Learning To Change The World'' text;
** to write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]);
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** to put all grant application/approval documents (drafts and final copies) on the wiki;
** to ask Project Instigators for monthly updates;
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website;
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* [your goal here]

Infrastructure Team/Migrating to GitHub

2016-06-27T12:11:48Z

Davelab6: add translations stuff

__NOTOC__

== Sugar Activities Developers: Take 10 Minutes to move to Github Today! ==

Part of the vision of Sugar Labs is to introduce young people to the software freedom movement.
A successful introduction means they are actively participating in Sugar's development, and the wider libre software world.
The majority of libre software in 2016 is developed on Github, and it advances our cause to use the same collaboration platform as most other project use.

The Sugar codebase has begun transitioning to Github in [https://www.github.com/sugarlabs www.github.com/sugarlabs].
So we now invite all Activity developers to do 2 things to complete this transition.

This should take you no more than 10 minutes:

1. Migrate your project source code and issue tracking to Github (https://help.github.com/articles/create-a-repo)

2. Once your project is set up as a Github Repo, please transfer it to github.com/sugarlabs so it is more discoverable (https://help.github.com/articles/transferring-a-repository/)

After the transfer, we'll update the activity.info file of the activity itself with the new URL
We'll also invite your Github username to join the [https://www.github.com/sugarlabs github.com/sugarlabs] organization, so you can transfer activities to yourself.

No longer involved? To pass your Activity on to the community to maintain, drop a line to <sugar-devel@lists.sugarlabs.org>.
If you read this well after May 2016, we may have already forked your repo into the org to maintain an 'official' copy of it, but transferring is better than forking so that Github shows the sugarlabs repo as the 'upstream' repo on network graph pages ([https://github.com/sugarlabs/sugar/network example])

New to Github? Check their excellent documentation at guides.github.com, help.github.com, try.github.io

=== Details ===

All our code, bugs and discussions should be in one place.

In 2013 Sugar's core components moved from http://git.sugarlabs.org/sugar-old to https://github.com/sugarlabs/sugar, but all issue tracking stayed at bugs.sugarlabs.org instead of moving to https://github.com/sugarlabs/sugar/issues and some code stayed in git.sugarlabs.org and some moved to personal Github username areas.

This scattering

* deters new contributors;
* makes existing contributor's lives more painful;
* wastes time from our systems team volunteers (as we have a hard time keeping hackers out of trac, and need to spend time upgrading any service we run ourselves)

Two solutions have been proposed:

;1. Consolidate on Github:Set trac and gitorious read only, and then making it a static html archive, while moving all issue tracking and git hosting of each sugar repo to Github.

;2. Abandon Github:Consolidate on our own systems; I guess this means setting up gogs or gitlab to replace gitorious, and perhaps something else to replace trac, and then removing each sugar repo from Github that we control, and regularly encouraging all sugar activities on github to move to our infrastructure.

The developer community has discussed this ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/thread.html#51788 thread]) and reached consensus in favour of (1) with the following comments:

=== Benefits of Github Consolidation ===

;Notification: This is handled due to the way that Github org membership works. Github-users in a 'developers' Github-team within the Github-organization will be emailed all posts to all repos that are added to that team (done here, http://imgur.com/gUTNFfV)

;Search: Github provides org-wide search, and this is discoverable when you visit github.com/sugarlabs the search input widget at the top changes to show that the search is scoped to that organization. After entering a search query, a familiar search syntax is used in the query, and in the URL string. Eg, https://github.com/search?q=org%3Afontforge+x11&type=Issues

;Discoverability: It will be easier for new developers to find and contribute if Sugar is all on github.

* Github allows us to separate issue into separate Sugar and Sugar Activity trackers, trackers are found predictably at github.com/sugarlabs/activity-name/issues
* It serves as an issue aggregation tool, as all issue trackers in the github.com can be searched by visiting github.com/sugarlabs and using the search input at the very top of the page ([https://github.com/search?q=org%3Asugarlabs&ref=searchresults&type=Issues&utf8=%E2%9C%93 example])
* https://github.com/sugarlabs/sugar/issues/ can be used as a default issue tracker, if there is any ambiguity on where to file an issue
* Issues on Github can be linked to pull requests that resolve them (and even close them automatically by including "closes #issue_id" in the commit/pr message)
* Github automatically places backlinks in issues that are referred to by other issuer or PRs, it is relatively convenient to manage the set of a github organization's per-repo issue trackers. Github makes this easy because it will add backlinks in the destination issue's timeline when that issue is mentioned in the original; and it will automatically create such links if you type user/repo#issueNumber :) As an example of this back-linking, see these 2 links, https://github.com/llaske/sugarizer/issues/49 (link at end of first post) and https://github.com/mattlag/Glyphr-Studio/issues/234 (currently link is at the bottom :)

;Focus: SugarLabs should focus on core-competencies. Managing version control servers shouldn't be one of them. Support for "how to use git" would be mostly on github rather than SugarLab's systems

;Developer Preference: Getting existing Github users to move their activities out of Github doesn't seem realistic. Developers know that Github is stable and has security and longevity. People new to Github have a wider interest in signing up for it - because almost all other libre software projects that they will interact with are currently on the service.

;Viability: There are only [https://bugs.sugarlabs.org/query?status=new&status=assigned&status=accepted&status=reopened&component=Sugar&order=priority 182 open issues on bugs.sugarlabs.org] so moving them over can be done in a day

;Automation: Github enables easier automation of the release process, and easier tying of Sugar Activity version numbers to moments in git commit histories.

;Fully Featured: Github doesn't exclude users from features based on their ability to pay; all features are available to non-paying users. Instead of charging for features, they require non-paying users to have all their repos be public; the only thing that they charge for is how many users can participate in private repos. https://github.com/pricing/plans explains this, and there are no gotchas.

;Pseudonymity: Github does not require real names. To maintain pseudonymity, you can sign up using http://mailinator.com or a github-specific disposable email account.

== Further Actions For The Sugar Labs Team ==

* Do another list of repos not using sugar3, eg with <code>from sugar.activity import activity</code>
* Set up a "full notifications" team in the github organization so that all github users that join this team get emailed every issue, pr, and comment for every github project within the organization.

* Configure all non-github issue trackers to prominently direct users to the new github url, and disallow new issues, or simply to have their theme templates hide the 'new issue' link, and eventually to be configured read only and then fully archived by conversion to a static HTML site.

* Review the wiki and website advising users where to post an issue, and update to point to Github

* Write a py/js script that uses the Github API to check issue tags are consistent across all SL repos; this can start with a manual checklist to run through when accepting a repo transfer to the sugarlabs org. Also, ensure each activity's /README.md file (that Github presents on github.com/sugarlabs/activity-name as processed markdown) has explicit information about standard things, like where its issue tracker is.

* Once all activities are migrated to Github, set the Gitorious and Trac instances to be read-only.
* Once all activities are migrated to Github, set a naming convention like "activity-xyz"

== List of Existing Repos To Transfer ==

On 2016-05-16 https://github.com/search?l=&q=%22from+sugar3.activity+import+activity%22+language%3APython&ref=advsearch&type=Code&utf8=%E2%9C%93 shows 327 code results, which when scraped and deduplicated lists 202 repos that are python sugar activities, which are listed here alphabetically by repo name (so duplicate repo names are adjacent)

The process of migrating to Github is:

1. request that all duplicate repos become forks of their most actively maintained repo, by being removed and then fork from the upstream, to create a github network graph.

2. request that the most actively maintained or de facto upstream repos transfer to github.com/sugarlabs

3. update any sugarlabs repos with newer commits found on git.sl.o

4. migrate any activities not yet on github from sl.o

This ensures that the github repositories that we minimise the number of sugar repos on github outside the sugarlabs repo network graph, are the repos transferred to the sugarlab org are actually the canonical repos.

* https://github.com/walterbender/abacus
* https://github.com/Boquete/activity-sliderpuzzle
** https://github.com/Boquete/activity-sliderpuzzle/issues/1 it is1 commit ahead of upstream
** https://git.sugarlabs.org/slider-puzzle-branch is the upstream repo, with a PR (https://git.sugarlabs.org/slider-puzzle-branch/mainline/merge_requests/1)
** https://git.sugarlabs.org/acsliderpuzzle/acsliderpuzzle/commits/master is a duplicate repo, to be compared
* https://github.com/walterbender/AEIOU
* https://github.com/cristian99garcia/agubrowser-activity
** https://github.com/cristian99garcia/agubrowser-activity/issues/1 transfer req
* https://github.com/puneetgkaur/backup_sugar_sugartoolkit (not canonical repo)
* https://github.com/samdroid-apps/bibliography-activity
* https://github.com/cristian99garcia/blender-activity
** https://github.com/cristian99garcia/blender-activity/issues/1 transfer req
* [https://github.com/ezequielpereira/Bridge/issues https://github.com/ezequielpereira/Bridge/]
** https://github.com/ezequielpereira/Bridge/issues/3 transfer req
* https://github.com/richaseh/browse (not canonical repo)
* https://github.com/samdroid-apps/browse (not canonical repo)
* https://github.com/sugarlabs/browse-activity
* https://github.com/iamutkarshtiwari/Browse-fiddleFeature (not canonical repo)
* https://github.com/cristian99garcia/calculator (not canonical repo)
** https://github.com/cristian99garcia/calculator/issues/1 transfer req
* https://github.com/llaske/Canope.activity
* https://github.com/walterbender/cardsort
* https://github.com/ezequielpereira/cavestory
* https://github.com/cristian99garcia/cedit-activity
** https://github.com/cristian99garcia/cedit-activity/issues/1 transfer req
* https://github.com/ceibal-tatu/ceibal-notifica
* https://github.com/Daksh/CeibalRadio
* https://github.com/aguzubiaga/chart
** https://github.com/aguzubiaga/chart/issues/2 transfer request
* https://github.com/walterbender/chat
** https://github.com/walterbender/chat/issues/3 transfer request
* https://github.com/City-busz/city-repository
* https://github.com/godiard/classroomexplore
* https://github.com/walterbender/clipart
* https://github.com/godiard/clock-activity
** https://github.com/godiard/clock-activity/issues/4 transfer req
*** https://github.com/cristian99garcia/ClockActivity (not canonical repo)
**** https://github.com/cristian99garcia/ClockActivity/issues/1 refork req
*** https://github.com/tchx84/ClockActivity (not canonical repo)
* https://github.com/Grumbel/clockgr
* https://github.com/cristian99garcia/collabedit
** https://github.com/cristian99garcia/collabedit/issues/1 transfer req
* https://github.com/walterbender/colordeducto
* https://github.com/sdanielf/comunicate
* https://github.com/godiard/comunicator-maker-activity
** https://github.com/godiard/comunicator-maker-activity/issues/2 transfer request
** https://github.com/tchx84/comunicator-maker-activity is a fork, no action
* https://github.com/ezequielpereira/Constellationsflashcards
* https://github.com/ers-devs/contact-app
* https://github.com/walterbender/convert
* https://github.com/walterbender/cookiesearch
* https://github.com/Richardopy/cuadradomagico
* https://github.com/cristian99garcia/dasher-activity
** https://github.com/cristian99garcia/dasher-activity/issues/1 transfer req
* https://github.com/tchx84/debian-pkg-sugar-toolkit-gtk3
* https://github.com/fdanesse/DesafioMundial
* https://github.com/godiard/develop-activity
* https://github.com/cristian99garcia/devtutor-activity
** https://github.com/cristian99garcia/devtutor-activity/issues/1 transfer req
* https://github.com/walterbender/dimensions
* https://github.com/godiard/distance-activity
* https://github.com/godiard/domino-activity
* https://github.com/activitycentral/ebookreader
* https://github.com/ezequielpereira/Edit
* https://github.com/godiard/favorite-fonts-activity
** this is now upstream in the sl org, so requested it become a fork, https://github.com/godiard/favorite-fonts-activity/issues/1
* https://github.com/godiard/finance-activity
** https://github.com/tchx84/sugar-finance-activity/commits/master has a commit not in upstream, so https://github.com/godiard/finance-activity/issues/4, then https://github.com/tchx84/sugar-finance-activity/issues/1
* https://github.com/walterbender/flip
* https://github.com/i5o/followme
** https://github.com/i5o/followme/issues/1 refork req
** https://github.com/AlanJAS/followme/issues/3 transfer req
* https://github.com/godiard/fototoon-activity
** https://github.com/godiard/fototoon-activity/issues/6 transfer request
** https://github.com/ceibal-tatu/fototoon-activity has a hard coding change that seems fine to forget
* https://github.com/walterbender/fractionbounce
* https://github.com/FundacionZamoraTeran/Genios
* https://github.com/lesivan/Genios
* https://github.com/godiard/get-books-activity
** https://github.com/tchx84/get-books-activity is a fork
** https://github.com/i5o/getbooks is not a fork so asked it to become one, https://github.com/i5o/getbooks/issues/1
** https://github.com/manuq/get-books is not a fork so asked it to become one, https://github.com/manuq/get-books/issues/1
* https://github.com/jdsimmons/getiabooks
** https://github.com/jdsimmons/getiabooks/issues/1 transfer request
* https://github.com/ezequielpereira/Gmail
* https://github.com/cristian99garcia/guido-van-robot-activity
** https://github.com/cristian99garcia/guido-van-robot-activity/issues/1 transfer req
* https://github.com/ezequielpereira/HacketyHack
* https://github.com/georgejhunt/HaitiDictionary.activity
* [https://github.com/tchx84/harvest-client/issues https://github.com/tchx84/harvest-client/]
** https://github.com/tchx84/harvest-client/issues/5 transfer request
* [https://github.com/tchx84/harvest-server/issues https://github.com/tchx84/harvest-server/]
** https://github.com/tchx84/harvest-server/issues/6 transfer request
* https://github.com/manuq/hello-world
** https://github.com/manuq/hello-world/issues/1 transfer req
** https://github.com/erilyth/Hello-World-Python_Sugar not canonical, a GSOC application requirement is to create a new hello world activity, so this is fine where it is
* https://github.com/godiard/help-activity
* https://github.com/fdanesse/Historico
* https://github.com/walterbender/iknowmyabcs
* https://github.com/godiard/imageviewer-activity
* https://github.com/walterbender/infoslicer
* https://github.com/godiard/ingenium-activity
* https://github.com/manuq/instalador-harvest-ceibal
* https://github.com/i5o/install-extensions
* https://github.com/godiard/irc-activity
** https://github.com/godiard/irc-activity/issues/7 transfer request
** https://github.com/i5o/irc-activity is not a fork so request it become one, https://github.com/i5o/irc-activity/issues/1
* https://github.com/fdanesse/JAMediaPyGiHack
* https://github.com/ezequielpereira/Java
* https://github.com/ezequielpereira/JClic
* https://github.com/godiard/journalshare-activity
* https://github.com/godiard/jukebox-activity
* https://github.com/llaske/KAView.activity
* https://github.com/ezequielpereira/Kiwix
* https://github.com/cristian99garcia/laybrinth-activity (not canonical repo)
** https://github.com/cristian99garcia/laybrinth-activity/issues/1 transfer req
* https://github.com/Boquete/activity-labyrinth (not canonical repo)
** Canonical repo?
** https://github.com/labyrinth-team/labyrinth
** https://git.sugarlabs.org/labyrinth
* https://github.com/ezequielpereira/Lemonade
* https://github.com/walterbender/lettermatch
* https://github.com/walterbender/letters
** https://github.com/walterbender/letters/issues/2 transfer req
** https://github.com/i5o/letters is not a fork so request it become one, https://github.com/i5o/irc-activity/issues/1
* https://github.com/godiard/level-activity
** https://github.com/godiard/level-activity/issues/2 transfer req
** https://github.com/ndefilippis/level-tool is not a fork so request it become one, https://github.com/ndefilippis/level-tool/issues/1
* https://github.com/walterbender/locosugar
* https://github.com/godiard/log-activity
** https://github.com/godiard/log-activity/issues/5 transfer req
*** https://github.com/i5o/log is not a fork so request it become one, https://github.com/i5o/log/issues/3
* https://github.com/shridharmishra4/mainline
* https://github.com/walterbender/makeymakey
* https://github.com/i5o/manage-homeviews
** https://github.com/svineet/manage-homeviews is a fork
* https://github.com/cristian99garcia/maps-activity
** https://github.com/cristian99garcia/maps-activity/issues/1 transfer req
** https://github.com/cristian99garcia/mapa-ceibal-activity is duplicate, so suggest removing it https://github.com/cristian99garcia/mapa-ceibal-activity/issues/1
* https://github.com/ezequielpereira/MathGraph32
* https://github.com/godiard/maze-activity
* https://github.com/FundacionZamoraTeran/Megamente
* https://github.com/godiard/memorize-activity
** https://github.com/godiard/memorize-activity/issues/5 transfer req
** https://github.com/tchx84/memorize-activity is a fork
* https://github.com/cristian99garcia/micropolis-activity
** https://github.com/cristian99garcia/micropolis-activity/issues/1 transfer req
* https://github.com/godiard/music-keyboard-activity
* https://github.com/shlesha/My-Activities
* https://github.com/jdsimmons/myosa-examples
* https://github.com/walterbender/napier
* https://github.com/i5o/numbers
* https://github.com/walterbender/nutrition
* https://github.com/kperisetla/Oopsy
* https://github.com/godiard/paint-activity
* https://github.com/walterbender/paths
* https://github.com/walterbender/physics
* https://github.com/cristian99garcia/pilas-activity
** https://github.com/cristian99garcia/pilas-activity/issues/1 transfer req
* https://github.com/walterbender/Pippy
* https://github.com/cristian99garcia/pocket-lrad-activity
** https://github.com/cristian99garcia/pocket-lrad-activity/issues/1 transfer req
* https://github.com/cristian99garcia/PolariActivity
** https://github.com/cristian99garcia/PolariActivity/issues/1 transfer req
* https://github.com/godiard/poll-activity
** https://github.com/godiard/poll-activity/issues/2 transfer req
** https://github.com/cristian99garcia/poll-activity/issues/1 is not a fork so req'd it to be
** https://github.com/Daksh/poll is not a fork, so req'd it be, https://github.com/Daksh/poll/issues/1
* https://github.com/walterbender/portfolio
* https://github.com/cristhofert/presentation
* https://github.com/walterbender/primedimensions
* https://github.com/cristian99garcia/pydebug-activity
** https://github.com/cristian99garcia/pydebug-activity/issues/1 transfer req
* https://github.com/puneetgkaur/pygame_camera
* https://github.com/i5o/qr-reader
* https://github.com/godiard/read-activity
* https://github.com/jdsimmons/readetexts
* https://github.com/walterbender/recall
* https://github.com/i5o/record-gtk3 (not canonical repo)
* https://github.com/walterbender/reflect
* https://github.com/walterbender/reflection
** https://github.com/walterbender/reflection/issues/2 transfer request
** https://github.com/ShivamNegi/Reflections_Activity is not a fork, https://github.com/ShivamNegi/Reflections_Activity/issues/1
* https://github.com/cristian99garcia/riverhex-activity
** https://github.com/cristian99garcia/riverhex-activity/issues/1 transfer req
* https://github.com/walterbender/ruler
* https://github.com/FOSSRIT/Sash
* https://github.com/quozl/settime-activity
* https://github.com/ezequielpereira/ShowJPEG
* https://github.com/cristian99garcia/showntell-activity
** https://github.com/cristian99garcia/showntell-activity/issues/1 transfer req
* https://github.com/erilyth/Simon_Says-Sugar
* https://github.com/walterbender/slideruler
* https://github.com/ezequielpereira/Snow
* https://github.com/inkyfingers/SoaS_Loader
* https://github.com/svineet/Solari
* https://github.com/samdroid-apps/sour-textbook
* https://github.com/i5o/spirolaterals
* https://github.com/walterbender/story
* https://github.com/walterbender/storydos
* https://github.com/jdsimmons/sugar-commander
* https://github.com/tchx84/sugar-finance-activity
* https://github.com/cygwinports-extras/sugar-HelloWorld
* https://github.com/i5o/sugar-irc-client
* https://github.com/native93/Sugar-paint-activity
* https://github.com/curiousguy13/sugar-python3-tests
* https://github.com/prasoon2211/sugar-social-help
* https://github.com/sugarlabs/sugar-toolkit-gtk3
** https://github.com/ceibal-tatu/sugar-toolkit-gtk3 is not a fork, but the whole org needs to be dealt with at once
** https://github.com/gusDuarte/sugar-toolkit-gtk3 is not a fork, req'd at https://github.com/gusDuarte/sugar-toolkit-gtk3/issues/1
** https://github.com/manuq/sugar-toolkit-gtk3 is not a fork, but has no issue tracker to request, so need to pm
** https://github.com/tchx84/sugar-toolkit-gtk3-1 is a fork of manuq, can just be removed, but no issue tracker, so need to pm
** https://github.com/AbrahmAB/sugar-toolkit-gtk3-proto is not a fork, req'd at https://github.com/AbrahmAB/sugar-toolkit-gtk3-proto/issues/1
* https://github.com/walterbender/sugarchess
* https://github.com/cristian99garcia/sugarcity-activity
** https://github.com/cristian99garcia/sugarcity-activity/issues/1 transfer req
* https://github.com/ezequielpereira/Sugarizador
* https://github.com/ezequielpereira/Sugarizehelp
* https://github.com/llaske/sugarizer
** https://github.com/llaske/sugarizer/issues/47 transfer request
* https://github.com/erilyth/Sugarizer-Clone-Sugarlabs- (not canonical repo)
* https://github.com/godiard/tamtam
** https://github.com/godiard/tamtam/issues/1 transfer request
** https://github.com/sethwoodworth/tamtam not fork, requested, https://github.com/sethwoodworth/tamtam/issues/1
** https://github.com/shridharmishra4/tamtam not fork, requested, https://github.com/shridharmishra4/tamtam/issues/1
* https://github.com/fdanesse/TamTamMini
* https://github.com/cristian99garcia/teachteacher-activity
** https://github.com/cristian99garcia/teachteacher-activity/issues/1 transfer req
* https://github.com/godiard/terminal-activity
* https://github.com/ezequielpereira/Time-Line
* https://github.com/walterbender/training
* https://github.com/erik/translate-activity
* https://github.com/i5o/triples
* https://github.com/cristian99garcia/turtleart
** https://github.com/cristian99garcia/turtleart/issues/1 transfer req
* https://github.com/walterbender/turtlepond
* https://github.com/cristian99garcia/tuxmath-activity
** https://github.com/cristian99garcia/tuxmath-activity/issues/1 transfer req
* https://github.com/llaske/VideoViewer.activity
* https://github.com/jdsimmons/viewslides
* https://github.com/ezequielpereira/VncLauncher
* https://github.com/samdroid-apps/web-maker-activity
* https://github.com/sehgalvibhor/WebConfusion
** https://github.com/sehgalvibhor/WebConfusion/issues/10 transfer request
** https://github.com/crusher95/webconfusion is a fork
* https://github.com/i5o/whatis
* https://github.com/walterbender/wordcloud
* https://github.com/walterbender/worddimensions
* https://github.com/godiard/words-activity
* https://github.com/godiard/write-activity
* https://github.com/godiard/write-books-activity
* https://github.com/ezequielpereira/XaoS
* https://github.com/i5o/xo-icon
* https://github.com/i5o/xo-retroscope
* https://github.com/walterbender/xocolors
* https://github.com/ezequielpereira/XOlympics
* https://github.com/walterbender/yupana
* https://github.com/cristian99garcia/pymusicblocks/issues/1 transfer req
* https://github.com/cristian99garcia/spanish-guarani/issues/1 transfer req
* https://github.com/cristian99garcia/pyeyes-activity/issues/1 transfer req
* https://github.com/cristian99garcia/playgo-activity/issues/1 transfer req
* https://github.com/cristian99garcia/reversi-activity transfer req
* https://github.com/cristian99garcia/Wine.activity transfer req
* https://github.com/cristian99garcia/supervampireninjazero-activity/issues/1 transfer req
* https://github.com/cristian99garcia/supertux-activity/issues/1 transfer req
* https://github.com/icarito/sugar-launcher-applet/issues/1 transfer req
* https://github.com/AlanJAS/panorama/issues/2 transfer req
* https://github.com/AlanJAS/biorhythm/issues/2 transfer req
* https://github.com/AlanJAS/pointillism/issues/3 transfer req
* https://github.com/AlanJAS/dotsAndBoxes/issues/3 transfer req
* https://github.com/AlanJAS/iknowAmerica/issues/4 transfer req
* https://github.com/AlanJAS/iknowMadagascar/issues/2 transfer req
* https://github.com/iamutkarshtiwari/Flappy-Birds/issues/6 transfer req
** https://github.com/AlanJAS/flappy/issues/1 transfer req - maybe duplicate?
* https://github.com/AlanJAS/jump/issues/2 transfer req
* https://github.com/AlanJAS/nxt transfer req
* https://github.com/AlanJAS/iknowUruguay/issues/1 transfer req
* [https://github.com/AlanJAS/iknowRwanda/issues/1 https://github.com/AlanJAS/iknowRwanda/issues/1 transfer req]
* [https://github.com/AlanJAS/iknowIndia/issues/1 https://github.com/AlanJAS/iknowIndia/issues/1 transfer req]
* https://github.com/AlanJAS/iknowPeru/issues/1 transfer req
* https://github.com/AlanJAS/iknowSriLanka/issues/1 transfer req
* https://github.com/AlanJAS/iknowEditor/issues/1 transfer req
* https://github.com/AlanJAS/cellgame/issues/1 transfer req
* https://github.com/AlanJAS/arduino/issues/1 transfer req
* https://github.com/samdroid-apps/collabwrapper/issues/4 transfer req
* https://github.com/axitkhurana/gmoksaya/issues/1 transfer req
* https://github.com/studiobytestorm/JS-Shell/issues/1 transfer req
* https://github.com/lionaneesh/sugarlabs-calculate/issues/3 needs to be reforked after https://github.com/sugarlabs/sugarlabs-calculate/issues/34 is closed
* Move all https://github.com/sugarlabs-infra repos
* Remove all inactive members from the org, and shift all owners who don't perform admin tasks to member status

https://github.com/ceibal-tatu has many repos, but they seem stale. It would be good to find who owns this and help them update it.

https://github.com/quozl/implode-activity/issues/3#event-669749829 transfer request rejected.

https://github.com/AlanJAS/fischerTX/issues/1 may not be relevant

=== Translations Migration ===

Please prioritize rescue of these activities stranded on gitorious
that have i18/L10n already.

ClassroomBroadcast
RafaelOrtiz
* https://git.sugarlabs.org/classroombroadcast

Jigsaw puzzle
alsroot
* https://git.sugarlabs.org/jigsaw-puzzle-branch

Slider puzzle
alsroot
* https://git.sugarlabs.org/slider-puzzle-branch

StopWatch
RafaelOrtiz
* https://git.sugarlabs.org/stopwatch

Analyze
garycmartin
* https://git.sugarlabs.org/analyze

Arithmetic
cjb
* https://git.sugarlabs.org/arithmetic

CartoonBuilder
alsroot
* https://git.sugarlabs.org/cartoon-builder

Colors
wadeb
* https://git.sugarlabs.org/colors

FlipSticks
alsroot
* https://git.sugarlabs.org/flipsticks

Gogo
dmoc
* https://git.sugarlabs.org/gogo

If you could hunt these down, it would be nice

Graph Plotter
Hello Mesh
HitTheBalls
HMouse
JAMedia
Kandid
Karma 6 English animal identification
Lanzar
Mateton
Play Go
Plot
PyDebug
StoryBuilder
Telescope

And if you do find them and move them, edits to this page would be
much appreciated.

https://wiki.sugarlabs.org/go/Translation_Team/Pootle_Projects/Repositories

Marketing Team

2016-06-27T04:30:30Z

Davelab6: Add PR company info

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>
'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.'''
Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet.
It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.
</div>

{{TOCright}}

{{:Marketing Team/Mission}}

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Sean's 2009 - 2015 Overview ==

Sean Daly acted as Marketing Team Coordinator 2008-2016, and when he stepped down on June 23 2016 he offered the following overview:

The 2009 marketing strategy we implemented, based on Sugar on a Stick, was very successful for a time during the netbook boom, but today's environment is very different with tablets, iOS/Android, etc. I had suggested two other ideas since then to the community to facilitate Sugar for teachers: prebuilt VMs for VirtualBox, and preloaded bootable SD cards and branded cases for Raspberry Pi. Since then, Lionel has developed Sugarizer, which in my view deserves serious consideration for marketing initiatives targeting teachers. Dave's efforts to identify a reference platform are also useful.

Samuel suggested a SWOT analysis today - it's an excellent suggestion, the last one we did is now way out of date. Work with Samuel and Dave and Samson on that, it will be helpful even for project recruitment which is their focus. A competitive landscape survey will be complementary to the SWOT. When the community reaches consensus on the project's vision, work on marketing objectives (as opposed to project objectives) can be done. This usually involves a calendar with what actions are planned. If budget is available, you will want metrics - ways to measure spend effectiveness.

Brand values: this is about how Sugar is different from anything else. We always emphasized low-floor, no ceiling; support for minority languages which for-profit companies ignore; the pedagogical pedigree; View Source; collaboration; the Journal.

There is also the PR aspect - targeting journalists, bloggers, and influencers. Communiqués are important for allowing a site visitor to get an idea of the project's direction in just a few minutes. Historically, we put PR on newswires. But these days, social media is very effective. Here's a tip for news coverage: if an initiative will influence large-buyer decisions (education ministries), or represents a real innovation (value proposition for less than what people usually pay), there could be press interest.

We have been using eReleases, a small company in Baltimore or Philly don't remember - http://ereleases.com - who have a great deal for nonprofits ("CauseWire"). The company president is Mickie Kennedy, and we have worked with editor Allison McAlister. We haven't done newswire PR for some time - I haven't known what newsworthy info we could put out that could possibly be picked up by traditional media, with the exception of GSoC news. There is an eReleases archives our PR.

The ongoing challenge is overcoming negative image perceptions of OLPC - that the $100 unit price didn't happen, that the project was somehow influenced by Microsoft, even that the project still exists. There is also an identified issue that our slick logo encourages a perception that we are a for-profit startup, not a nonprofit volunteer org. this is why we said "Nonprofit" in many of our PR communiqué titles.

My advice is to not waste time documenting the 2009-2010 strategy or my 2011-2012 attempts to develop a new one. Start from scratch - a SWOT analysis and competitive landscape is the starting point. Translate the SL project objectives into marketing objectives, define a calendar and metrics. You've stated recruitment objectives, but not a strategy... execution (facebook + Google AdWords) seems already decided, which IMHO is putting the cart before the horse, but no big deal.

https://wiki.sugarlabs.org/images/4/47/MCFE_Final_Presentation_SugarLabs_12-11.pdf

Caroline Meeks put together the SWOT analysis in this prez. I don't remember if I had assisted with that. I seem to remember having worked on another. I will search my offline archives, which are very complete concerning SL - I have everything from when I started.

This may be useful for very brief marketing strategy historical overview
http://lists.sugarlabs.org/archive/marketing/2013-November/003607.html

The success of the SoaS marketing initiative encouraged some SL members to assert control over the name, the trademark, the technical architecture, and the marketing of it. As a result the lead developer of SoaS left the project.

Peter had justifiably complained on IRC around 2010 that there was no marketing strategy page. I had chosen not to create one at the time because OLPC was involved in fierce competition with Intel Classmate offerings running Windows, and we were aware that our marketing initiatives were being monitored. This lack of clarity may have been a mistake, but my goal had been to disrupt the MS/Intel sales force talking points. The marketing team which was numerous at the time all knew the strategy.

=== Walter's 2016 Marketing Plan ===

Walter Bender offered this view for future marketing efforts:

What I would like from marketing is some mechanism for highlighting the powerful ideas in Sugar that seem to be lacking in most other systems so that even if a school decides to go with a different product/project, they put pressure on that project to provide tools, not apps, collaboration, transparency, self reflection and group critique, and responsibility on the shoulders of students and teachers to shape their own world.

A few observations/thoughts that may help us in focusing our marketing efforts:

(1) The primary source of push back in AU re Sugar was the browser. Schools had websites that they were interested in accessing that were not supported by Browse at the time. This is something we can turn around in the devel team and maybe something we need to surface in marketing: that Sugar is web/cloud enabled on top of all its other virtues. (I had been keeping the name "cloudberry" in reserve for this.) Ironically, at the time we added Sugar extensions for access to Google Drive (among other clud-based services), NSW got in bed with Microsoft and prohibited schools from using non-MS cloud services. OLPC AU never promoted the Sugar cloud-enabled features.

(2) The switch to Windows 10 by OLPC AU is a total capitulation to the "we don't have a clue as to what is of value in terms of pedagogy, so we'll make a deal with whomever will give us the best deal camp." Not sure what our response should/can be in such circumstances.

(3) There is a still strong interest in Sugar in Paraguay and some momentum to go national. We could try to ride that wave. We've been invited to come to Paraguay in October.

(4) I'm pushing hard in Chile... we'll see what happens.

(5) In UY, they are still using Sugar in primary schools (on Ubuntu). We should market in the Ubuntu space (I had had an offer from Ubuntu to let us do the equivalent of a Fedora Spin which we could follow up on).

(6) We should push on Red Hat to give us more exposure.

(7) Can we get a Sugarizer pilot going in a school to get a sense of what it means.

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== Google Non Profits AdWords ===

SL is obtaining $10,000 per month AdWords credit that Google offers to nonprofits and will use to run adwords campaigns by these members:

* Dave Crossland
* Sean Daly
* Samson Goddy
* Walter Bender

The marketing strategy will be to seek new members. Three kinds of members will be sought: (1) software developers, to write python and javascript programs (2) translators, to localize the programs, and (3) technical authors, to increase adoption by specific audiences - parents and schools.

Next Goal: Obtain access to the AdWords account.

Deadline: July 30 2016

=== Local Labs Survey 2016 ===

Sugar Labs will survey end users to better understand how Sugar is being adopted and adapted.
See also

* [[Marketing Team/Local Labs Survey 2016]]
* In late 2015/early 2016, Sam Parkinson ran a survey on http://socialhelp.sugarlabs.org and wrote a report ([[Media:2016_Socialhelp_Survey_Analysis.pdf]]) and published the source data ([[File:2016_SocialHelp_Survey_Response_Data.ods]])

Next Goal: List as many end users as possible.

Deadline: August 30 2016

=== New Website ===

In late 2010, four students from the MIT Sloan MarketLab worked on a study of the Sugar Labs website.
Their conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues, as well as the technical orientation of our web presence.

* The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar
* Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]
* A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]
* The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

Our polished static website as a landing page for Sugar Labs was redone in March-May 2011, see [[Marketing Team/Website]] history

Next Goal: Get the SL 2016 Vision, Mission, and Goals approved by SLOBs

Deadline: September 15 2016

===Events===

See [[Marketing Team/Events]] for a table of events we are targeting.

Next Goal: List possible future events.

Deadline: September 30 2016

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/press

Next Goal: Draft the next press release; Develop a [[Marketing Team/Press contacts]] list with education-oriented publications.

Deadline: September 30 2016

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

Next Goal: List contributors active in 2016

Deadline: August 30 2016

=== Swag ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, umbrellas, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]]

Next Goal: Design new swag for 2016

Deadline: September 30 2016

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

2016 Goals

2016-06-27T04:28:39Z

Davelab6: list consultancies;

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO;
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to liberate the ''Learning To Change The World'' text;
** to write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]);
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website;
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* to clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* to list consultancies that can offer commercial support, as recommended by http://lwn.net/Articles/689596/;
* [your goal here]

2016 Goals

2016-06-26T23:22:46Z

Davelab6: python 3, hydrogen editor

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port all Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to port all Activities and Sugar from Python 2 to Python 3;
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to develop a better Activity for creating Activities, with features from Bret Victor's essays, like https://atom.io/packages/hydrogen;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO,
**
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to liberate the ''Learning To Change The World'' text;
** to write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]);
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website;
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* [your goal here]

Vision proposal 2016/Call 2

2016-06-26T20:21:03Z

Davelab6: Add my summary

[[File:Sugarlabs-strategy-overview.webm]]

[[:File:Sugarlabs-strategy-overview.webm]]

=== Summary ===

[[User:Davelab6]] provided the following summary:

In the period 0m-7m, you say that that there should be 2 units of analysis, for Sugar Labs and for Sugar, and therefore 2 separate sets of Vision/Mission/Goals/etc, but these should be aligned. Is this correct?

Then 8m-18m, you describe a 7 phase model of a firm:

1. Inbound logistics (capital goods, labour)

2. Operations (production, combination of capital goods and labour to produce commodities; Sugar Labs )

3. Outbound Logistics (distribution, shipping, go to market; eg each sugar release being minted, and then a distro packaging it, or OLPC taking a sugar release and combining it with some distro)

4. Marketing and Sales (managing perceptions, which for a software freedom project is often not sales as in exchange of commodities for money, but instead the success of propaganda at converting neutral people to advocates who agree with the ideology)

5. Service (Consulting, eg the process of working with schools to realise the value created in earlier stages which may be obvious to us but not to them.)

You then group phases 1-3 as 'supply side' and 4-5 as 'demand side,' and note that traditionally OLPC has taken care of the demand side while Sugar Labs has taken care of the supply side; and note that such partitioning of supply/demand often creates conflict in free software projects which have more appreciation for the left side than for the right side; and note that the demand side needs attention as it increases the value of the software created.

This all seems sage to me :) Did I miss any essential point?

Then 18m-31m you describe a 5 phase model of strategy:

1. Vision (long term) 'dream statement' of where we dream to be in a few years - the world we hope to arrive into, the big picture we are moving towards.

2. Mission (long term) what are we, what do we do, why do we do it - this should hold good for the same amount of time as the Vision; what exists today, that powers us to move towards the Vision

3. Goals (mid term) expected outcomes that are not measurable, eg "Increase adoption of Sugar by non-English-native-speaking children". These typically arise from a SWOT analysis.

4. Objectives (mid term) specific targets that are measurable, eg "Increase 8 translation locales from 80% coverage to 100% coverage before 2017/1/1"

5. Tasks (short term) actual activities that are assigned to people to get done, eg "Chris Leonard to organize volunteers to meet the translation objective."

You noted that typically the common focus of activity of free software projects is at the 4-5 level, with bon mots like "release early, release often," while 1-2-3 change slowly and typically get much less attention from free software project contributors, and the Sugar project isn't alone in this.

Again, I concur. Something I found missing from your presentation was a guide to how long (ie, in word count) these statements should be. What do you think?

You also noted that while there is no general recommendation for what duration to consider long, mid or short term - as this is relative to each given project - and the core idea is that the earlier phases change less often than the latter ones - you give some recommended durations for the lifespan of these statements for the Sugar Project.

I therefore propose the following concrete dates for these durations, that are within your recommended durations:

1. Vision (now - 2020/1/1)

2. Mission (now - 2020/1/1)

3. Goals (now - 2018/1/1)

4. Objectives (now - 2018/1/1)

5. Tasks (now - 2017/1/1)

You also note that this phase strategy is a framework for situating the SWOT analysis that Sean called for, that is, it is a method for defining Objectives. You point to the 2x2 matrix graphic on https://en.wikipedia.org/wiki/SWOT_analysis and note that Strengths/Weaknesses are internal to the project - aspects that we control - while Opportunities/Threats are external, beyond our control; and these can be combined to generate 4 categories of objectives:

1. S + O = things to pursue

2. W + O = things to convert

3. S + T = things to reduce

4. W + T = things to defend

However, since this is phase 4 of 5, and we haven't finished defining the earlier stages, I propose to postpone a SWOT analysis until those stages are wrapped up.

Finally 31m-33m you conclude that the approach to drafting a vision statement with wide consensus is not productive when done via email or an IRC board meeting, and you want SLOB and the community to understand there is a specific process you have in mind for developing these productively, and to be patient as this process can take time to wrap up; and you offer to do some other screencasts to present further details of that specific process.

This is awesome! I'm looking forward to the next screencast so we can learn how to participate in defining the vision productively :)

=== Transcript ===

hello this is sameer me when I have been following a lot of the discussions on many different meaningless that we have for sugar and I AP and so on and something that stands out is that we seem to have a lot of confusion around the various terms that are you especially when it comes to the the process of creating a strategic plan so we look at terms like vision mission most of these terms are fairly standard of the occasionally there will be a minor difference here and there but it's important to understand what these terms mean across the board before we even embark on trying to define these things it's also important to define the scope in terms of the scope of the problem you're trying to look at so i figured i do a small short screencast to talk through some of these things I've got some slides here and this is fairly generic with lots of variations here done for different products but some of these things are coming from my own experience as a business school professor and working with some other nonprofits and open source projects where we've actually gone through an exercise to do something like this

so in this particular case the unit of analysis is the the thing that we're trying to work with this is the scope that i was talking about so for instance we have a lot of conversations where we see people coming up with vision statements for instance that talk about what they want sugar to be what they would like for sure their labs to be should XO ones be included in should we talk about raspberry pi what about sugar Iser and usually those email conversations and IRC conversations end up being a collection of a lot of so part of the things that we need to be very clear about here is the unit of analysis and as far as I'm concerned as a member of the sugar labs oversight board everything that I want to look at it through the lens of sugar labs so here's the point of distinction sugar labs and sugar are not the same sugar is a free and open source project which is which originally came out of the old pc effort and is now managed by a whole bunch of people contributions including code and documentation and translation and all that so that's sugar it's an entity that we've established to support the cause of sugar to foster it to facilitate it the whole bunch of different ways to support the project so for instance sugar labs is a is a project in the sense that itself it's under the software freedom Conservancy and so the the nonprofit status for instance is applicable to sugar labs so if if somebody said you know I'd like to give you a hundred dollars they they can give those hundred dollars to show their labs so sugar labs is the entity sugar is the project and the two are different and this is an important point of distinction because if you look at how sugar operates on the project it's very decentralized we do have a release manager for different relievers so somebody who simply manages a fair number of decisions but the contributions come from many different places and then we leverage infrastructure and I get get help and so on and so it allows us to decentralize the whole process and manage things in different spheres and still be able to so that's sugar but sugar land itself for instance follow the slightly different structures of for instance there is the oversight board with seven members there is legal counsel that is SF seed is accounting there is a 501 C 3 status there is a bank account with money and all of those things so it's not quite be centralized there are certain hierarchies that have to be considered because of the fiscal responsibility legal responsibility and and I think that's one of the points of conflict which is if we look at the two as one then we can't really use a specific model to apply to both and you have lots of confounding variables where they get mixed up so ideally the way they should work is that we look at sugar labs as one entity or a unit of analysis in this case and then we look at sugar as another unit of for instance because I've volunteered to be on the sugar lab door sideboard and my lens is sugar labs now somebody else who contributes to the sugar project perhaps your lens can be the sugar project and so we can think of two parallel efforts to do this kind of stuff which has come up with mission vision and so on but they need to be separate and then at some point you want to have strategic alignment between the two so because she loves was created to there needs to be strategic alignment obviously we can't have the two running supporting entirely different things so we the the one way to bring them together is to have that alignment between the vision of sugar and the vision of sugar labs the Machine sugar and the Machine sugar labs as opposed to saying that we combine the two and come up with one vision for the whole thing so that's I think it's a major source of conflict in terms of trying to determine what sugar lab should do and be versus what sugar should do and be so in this case I'm going to pick on the lens as the unit a unit of analysis as as sugar labs and so even if i look at the project called sugar I would look at it through the lens of sugar lips ok more on this a little later then come to this concert this is the value chain this is used quite several industry in fact and it's basically a combination of what is the

we see that the motivations to produce software are many but typically tends to

you know we have five or six pack is available so supply side is pretty heavy managing the demand side though is often a challenge because software is produced

so we have lots of these bits and pieces that can get weave together into a system however the demand side unless they really know how to use this is often far removed so i'll spend about five minutes maybe less on this but I wanted to bring this in because this also brings in the whole question of where marketing fits which is a very undervalued concept when it comes to many open-source projects free open source projects so this is the classic value chain this comes from michael porter way back it's got a whole bunch of things here in this inbound logistics operations are logistics so on and so forth and then you've got all these support activities so the purpose of this conversation I want to disregard the upper part that you know something we can talk about later and focus on what's here and so are we done the same thing so this is what we had this is what we have now we have five segments to this chain inbound logistics operations outbound logistics marketing and sales and service and you can think of this as something where this would be applicable to you know perhaps a product like a pair of shoes if you produce a pair of shoes you would go across through this whole thing so if you start off with involving mystic this would be the raw materials and the labor a few producing shoes this would be the the rubber the leather and of course the labor the people who come to the factory to actually build those shoes put those together in our case it would be ideas and code and documentation and all the contribution that we provide to sugar the project itself now for sugar labs it would be the kinds of things that we provided input into sugar labs again in terms of whether to the volunteer work or attend the next step is production and so looking at the sugar the project this would be where you bring in all the contributions from different people into a process where you can put it all together to make it work right so this would be the infrastructure where everything is hosted tested debugging this would be very much like the factory you would have to produce shoes then we have the next part which is the outbound logistics and this is where the so when the release manager says here the release 108 that's taking all the code that came in from here through the operations and then saying it will be basically free the bunch of things and say this is what we produce or for instance when all pc says we'll take a bunch of sugar stuff so this is the supply side process where you have raw materials and labor coming in production happening and then you do distribution and shipping so it comes out of distribution and shipping is effectively a release in our case of say sugar or an old pc image in case of all pc where they put it together and and shipping up but this is where with respect to software projects the software comes up especially with open source free and open source projects this is where the the output is the tarball perhaps or the the decatur depository and next comes the marketing and sales section so often in free and open source projects this is the part that is not focused on because a lot of the work is done on the supply site with the thinking that once the code is produced it can speak for itself and marketing and sales comes with an afterthought particularly sales because in many cases you know we're not selling anything that is no sale effectively but here the word sales is more to do with not necessarily transaction money but saying I agree with what you are saying and therefore I will you know move in the direction to adopted marketing is that link which is what helps us manage perceptions for any population or any so think of we we have these conversations about mailing lists being for developers vs teachers two very different groups and often developers are ok with email lists and IRC but teachers are not this has to do with managing perception because in the world of feature the way they manage things is software developers do teachers are not comfortable with a lot of things that software development people are and so even though the the software that is the teacher in this case is not able to see how that fits in her world and so they say you know this is not something i want to deal with it or perhaps i'll give you another example like when we start the semester let me begin with the textbook and some kind of a software package or tool that comes with the textbook for addressing certain certain problems you know in now if the software kept on changing every few weeks it becomes very hard to manage that class so there is expectation that the software essentially stays the same the the user interface doesn't change the the features essentially stay the same for the duration of a semester or so these are all very different perceptions that people have and a lot of the marketing stuff is about managing those perceptions and then that leads into sales if you manage those perceptions well then your target population will be closer to actually adopting and therefore be the sale section and eventually it is a fifth one which is service and this has to do with things like consulting and perhaps some of the consulting stuff in our case would be the process of working with educators working with principal school district people do to clarify the value proposition in a sense that there's all this good stuff that happened on the left side here the supply side but why is it important for them what role can it play in many cases it may be evident to us that match to them we may know that little there's all this good stuff and sugar that you can use kids can learn a lot of things but perhaps not evident to the other side especially the people who make decisions and so that's where this comes in which is the ability to provide some kind of a service beyond actually making the decision or making the sale where they adopt the software so there's a 50 some real well maybe come back to this later so the way this is split is you've got a supply-side on the demand side you can work on the supply side and produce a lot of software but if you do not work very few people would not what it is and so for instance the largest customer sugar is all pc but outside of all pc there are very very few people who and so until the right side of the value chain is managed and extended that is something that will not happen and that's where the details of marketing so on commit so this is this is the value chain instrument that may perhaps be useful to understand that the activities on the left side versus the right side are two very different kinds of things i often see this conflict or disagreement on email lists where marketing is something that's an afterthought it's a one-time thing you know let's go and raise some money let's do ads and those kinds of things and it's not quite that simple yeah it's a very different way of managing things and I also notice that many open-source projects will have a lot of appreciation for the left side but not so much for the right side and that's just the nature of how the projects are we spend so much time on the next site of the chain that it's kinda hard to look at the things on the right side now that on the contrary view for instance went to a business school you will see how the right side actually extends the value of the website it's not replacing it to start left versus write the value actually increases when you go from the left to the right and so to increase the value of what is produced by say sugar the fourth and the fifth blocks here have to be worried about

so this is a typical strategy crosses that you begin with vision once you have a vision statement then you look at a mission statement when you look at goals when you look at objectives and tasks and the way these are divided is typically along the lines that vision and mission is supposed to be long term and long term is a relative thing but in the in that relative scope original mission or long-term items that is that they should not change for the long duration with goals and objectives can be midterm so short and long term so there is an inherent hierarchy here and i suspect that because there is an it also doesn't lend itself relieved well too many free and open source software products because what I've seen in other products that I've worked with is that a lot of the work done in software development in these projects tend to be here and be the tasks section so lots of short iterative tasks so that whole concept of released early release often happens in this is this layer here about the tasks but as you go further up the exactly time to get slow because they don't change as much and because we tend to be close to the it's harder to them say oh there's anything worthwhile further up here so why bother but it's important to have this understanding that the strategy a tiered process with long-term mid term and short term so if i have to give examples i would say save vision and mission statements should be somewhere in the range of three to five years then you can look at goals and objectives which would be perhaps in the 18 month time frame maybe 12 month time frame and then that can be broken down into tasks of three to six months and either again to set of numbers but to give you an estimate if you're working on tasks which are in the range of three to six months it's hard to them switch and say oh there is something that does not change for five years but ideally you do want your original mission to mark change often because it's supposed to give you direction and that direction should be so if we were to for instance look at the old pc project 2007 is when they this is 2016 9 years out you know we'd want for things to stay stable for a long duration of time and then you know perhaps the nature of the problem will change as it has been the things like a whole bunch of other devices that are there in the market that did not exist back then and so you may have to them go back and revise your vision original mission and then follow the goals and objectives from that and the tasks so this is a typical strategy process the vision statement is it's a dream statement as in we dream to be this in X number of years where do we think we will be next number of years so again should reverse the sugar labs the door should be different but it would be along those lines which is maybe sugar will be used by twenty-five percent of the schools in the US are our it will be used by one-third of the the children of the world is purposefully nonspecific because it's something that is very hard to assess but you have to have something some kind of a place to be in X number of years so that becomes the vision and in our case I guess we're still working on what that vision should be so leave it at that and then the mission part is the water my mission statement is you know what are so and again i will specify that sugar levels of sugar those are two different things so then it needs to be a mission statement for sugar labs and a mission statement for sugar and they can be similar which would allude to some alignment and then questions like what is it that we do so like what sugar laps to sugar labs supports Foster's facilitates defense I don't know those are the different kinds of words to look at why is it that so what is the purpose of this and then it also holds good for the 4 X number of years where we would want the vision and mission to have approximately the same life cycle so by the time you think your vision is getting stale it would be time to devise not just a vision but also the mission so that they're both at the same for the same number of years I think this statement has multiple parts to it that may or may not qualify as the mission statement but again that's not my exercise to take on it's something that sugar Labs has to figure out so for instance the first part there sugar lapses volunteer-driven member yes and then it is part of the sfc and it originally came out of sugar lab what it is what it is that sugar labs actually does so vision is very hard to be and mission is based on what we know here and now so there is a difference of time which is mission is typically grounded with of course there are no guarantees but unless we figure out where we would like it's kind of hard to get there you can think of it as a bus where the mission the back wheels that actually push the bus and the vision is the steering column and the front wheels that actually provide direction to enable us to get there so these are the two things that are important and this is where we so this is we would begin with vision and mission and then move on to the

it is also broad-based so it's not very specific but it is a little more specific than the vision part so for instance increase the adoption of sugar in the education sector and now i'm not saying an option by what percentage or which market just sort of increase the adoption of sugar in the education sector so that's a goal to fulfill that goal for instance we would come up with specific targets and will become the objectives so specific targets that has helped achieve those so in this case for instance you will see increased translations by three percent in the next six months so that's the metric that's the number we are looking at and I can be may or may not achieve that objective but it's and so this is going further down in that hierarchy of being more specific now how do you increase translations by three percent that's where the tasks would come it and it would be like that these are the things we have to do so this is the activity part which will help execute or our help achieve those so you do this task this may help us achieve the objective which then these are also short term and so for instance it may be to sign a partnership

then comes this business of Swat strengths weaknesses opportunities and threats this is another thing we've done an exercise like this in the past i believe it's useful but where does it fit in the whole map so this is kind of where it fits we do the original mission when we start to willingly they have to come from someplace and swat is where they come so once you're done with SWAT you would pull a list of goals from SWAT and obviously you cannot go through all of those so you would prioritize and say let's take these four for these five and then build the objectives on that so let's see what happens with SWAT so it basically has about strengths weaknesses opportunities and threats again this is specific to the unit of analysis so if I did it's what i would do it for sugar laps and I would look at sugar labs as to what the strengths are off sugar labs and weaknesses and the the interesting distinction here is if you look vertically there is strength and opportunities of the plus points of those are helpful weaknesses and threats are harmful but more importantly we've got the other distinction which is this that strengths and weaknesses are internal to an organization where as opportunities and threats are external and this is an important distinction because you know what it's easy to understand what's this part has well basically the internal part is something that we can we can control because its internal to the organization so the things that we have within sugar labs are the things that we can work on external is something that's not in your control and so the most you can do is either avoid or average but you can actually change the external origin the origin items such as strengths and weaknesses so this is an important distinction in swat is that once you do so what you split and look at internal external understand that internal is what we control that the external so next and then you know in terms of doing the swot analysis we would basically say okay let's make a list of all the sprints the sugar house on the weakness of the sugar laps house all the opportunities that your labs has and all once you do that we start to prepare those and the pairing happens again internal versus external so we will do pairing likes trends and opportunities what are we good at and one of the opportunities out there you combine similarly you look at weaknesses that sugar Labs has opportunities that exist can we convert some of the weaknesses easily and intuitively easily so that we may pursue those opportunities so that becomes a conversion . strength and what are the threats that are out there what are we good at can we use our strength to actually reduce some of those threats and if not then just move on and then finally weaknesses and threats which is we know we are not very good at certain things can we actually defend ourselves from so you end up at four combinations pursue convert reduce and defend and so so you can pull out a bunch of goals and then prioritize them and say these are these levels are not so easy and you would pick the number of ones that can be actually worked out so these would be the goals from these goals will would

so these four items here would give us those goals the goals and objectives somewhat measurable so we can come back to it in six months and say what did we actually say achieve three percent chance of translations are about right and in fact that's where the reports coming in are translation would be very helpful because they have some metrics so that is the whole process I said this is very important which is the lens that we use so personally for me i'm going to focus on demand of sugar labs sugar is a project that i've used

extracting data from the journal analyzing it doing some analytics working on that stuff but at this point my position and my strength is with the organization sugar labs itself so that's the lens i'm going to use and even if i I'm going to look at it from the lens of sugar lap so this is one important point the value chain part is for your understanding of how marketing work so that's another conversation to be had but the important thing here is that the right side here the demand side is really what matters in extending the value of what sugar already produces and then finally this map here and if you vision mission is long term so even if you don't know five years that's a be 23 years vision mission will be three years goals objectives would be 12 to 18 months passed so would be three to six months and the third part would be to skip ahead SWAT to come up with some specific goals and basically do this so I may do water to other screencasts in the spain same area to to help i will also reiterate as I've done in a couple of my emails before that let me forward here that the the approach to being able to come up with a consensus-builder vision statement is not something where we threw out a bunch let me copy paste your cut yours and you know Adam glued together and come up - coming over with with a vision statement and a mission statement but it it's not something that can be done for the board meeting or just sending in fact there are lots of things that happen an email that tend to amplify the so there are different ways to do it I'm happy to suggest that support and even helped run some of those things but it is important for i think the the sugar labs oversight board and the sugar community to understand that these are things that have a specific process and they take time so i hope this helps

Vision proposal 2016

2016-06-25T13:53:48Z

Davelab6: Add call 2

The following is a DRAFT, that will be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year. Your edits are welcome!

You may also enjoy related pages:

* [[2016 Goals]]
* [[Mission proposal 2016]]
* [[Vision_proposal_2016/Call_1]]
* [[Vision_proposal_2016/Call_2]]

<hr>

Sugar is high-quality software for learning, especially by younger children.

Sugar is designed for use by people who do not yet have regular or reliable internet access.

The Sugar Desktop runs on inexpensive desktop and laptop computers that have modest capacity, such as the XO-1 "$100 Laptop" developed by One Laptop per Child (OLPC).

A web-based version is under development for tablets and phones, called Sugarizer.

Sugar Activities are applications that run in Sugarizer or the Sugar Desktop.

Sugar Activities encourage learning through self-discovery and encourage collaboration, expression, and reflection.

Sugar realises the educational vision of Seymour Papert and Alan Kay by providing a low floor and no ceiling.

Every Sugar Activity respects every user's freedom to run, study, modify and redistribute it using software licenses compatible with the GNU General Public License (GPL) Version 3 or later.

Sugar development began in 2006 at OLPC, and in 2009 Sugar Labs was established in service to the Sugar community as a volunteer-led and non-profit project.

In 2016 the Sugar community is global, and we at Sugar Labs aspire to include users and contributors in all countries, all languages, and all cultures.

We facilitate knowledge and software sharing among all people; we relate the software freedom movement to education.

We provide plans for how to best use Sugar to improve learning, intended for individual parents and teachers all the way to national policy.

We raise funds and use them to accelerate the progress of our Members, enabling them to access laptops, travel, and more.

We make things to think with.

Join us.

Vision proposal 2016/Call 2

2016-06-25T13:45:18Z

Davelab6: Initial page

[[File:Sugarlabs-strategy-overview.webm]]

[[:File:Sugarlabs-strategy-overview.webm]]

=== Transcript ===

hello this is sameer me when I have been following a lot of the discussions on many different meaningless that we have for sugar and I AP and so on and something that stands out is that we seem to have a lot of confusion around the various terms that are you especially when it comes to the the process of creating a strategic plan so we look at terms like vision mission most of these terms are fairly standard of the occasionally there will be a minor difference here and there but it's important to understand what these terms mean across the board before we even embark on trying to define these things it's also important to define the scope in terms of the scope of the problem you're trying to look at so i figured i do a small short screencast to talk through some of these things I've got some slides here and this is fairly generic with lots of variations here done for different products but some of these things are coming from my own experience as a business school professor and working with some other nonprofits and open source projects where we've actually gone through an exercise to do something like this

so in this particular case the unit of analysis is the the thing that we're trying to work with this is the scope that i was talking about so for instance we have a lot of conversations where we see people coming up with vision statements for instance that talk about what they want sugar to be what they would like for sure their labs to be should XO ones be included in should we talk about raspberry pi what about sugar Iser and usually those email conversations and IRC conversations end up being a collection of a lot of so part of the things that we need to be very clear about here is the unit of analysis and as far as I'm concerned as a member of the sugar labs oversight board everything that I want to look at it through the lens of sugar labs so here's the point of distinction sugar labs and sugar are not the same sugar is a free and open source project which is which originally came out of the old pc effort and is now managed by a whole bunch of people contributions including code and documentation and translation and all that so that's sugar it's an entity that we've established to support the cause of sugar to foster it to facilitate it the whole bunch of different ways to support the project so for instance sugar labs is a is a project in the sense that itself it's under the software freedom Conservancy and so the the nonprofit status for instance is applicable to sugar labs so if if somebody said you know I'd like to give you a hundred dollars they they can give those hundred dollars to show their labs so sugar labs is the entity sugar is the project and the two are different and this is an important point of distinction because if you look at how sugar operates on the project it's very decentralized we do have a release manager for different relievers so somebody who simply manages a fair number of decisions but the contributions come from many different places and then we leverage infrastructure and I get get help and so on and so it allows us to decentralize the whole process and manage things in different spheres and still be able to so that's sugar but sugar land itself for instance follow the slightly different structures of for instance there is the oversight board with seven members there is legal counsel that is SF seed is accounting there is a 501 C 3 status there is a bank account with money and all of those things so it's not quite be centralized there are certain hierarchies that have to be considered because of the fiscal responsibility legal responsibility and and I think that's one of the points of conflict which is if we look at the two as one then we can't really use a specific model to apply to both and you have lots of confounding variables where they get mixed up so ideally the way they should work is that we look at sugar labs as one entity or a unit of analysis in this case and then we look at sugar as another unit of for instance because I've volunteered to be on the sugar lab door sideboard and my lens is sugar labs now somebody else who contributes to the sugar project perhaps your lens can be the sugar project and so we can think of two parallel efforts to do this kind of stuff which has come up with mission vision and so on but they need to be separate and then at some point you want to have strategic alignment between the two so because she loves was created to there needs to be strategic alignment obviously we can't have the two running supporting entirely different things so we the the one way to bring them together is to have that alignment between the vision of sugar and the vision of sugar labs the Machine sugar and the Machine sugar labs as opposed to saying that we combine the two and come up with one vision for the whole thing so that's I think it's a major source of conflict in terms of trying to determine what sugar lab should do and be versus what sugar should do and be so in this case I'm going to pick on the lens as the unit a unit of analysis as as sugar labs and so even if i look at the project called sugar I would look at it through the lens of sugar lips ok more on this a little later then come to this concert this is the value chain this is used quite several industry in fact and it's basically a combination of what is the

we see that the motivations to produce software are many but typically tends to

you know we have five or six pack is available so supply side is pretty heavy managing the demand side though is often a challenge because software is produced

so we have lots of these bits and pieces that can get weave together into a system however the demand side unless they really know how to use this is often far removed so i'll spend about five minutes maybe less on this but I wanted to bring this in because this also brings in the whole question of where marketing fits which is a very undervalued concept when it comes to many open-source projects free open source projects so this is the classic value chain this comes from michael porter way back it's got a whole bunch of things here in this inbound logistics operations are logistics so on and so forth and then you've got all these support activities so the purpose of this conversation I want to disregard the upper part that you know something we can talk about later and focus on what's here and so are we done the same thing so this is what we had this is what we have now we have five segments to this chain inbound logistics operations outbound logistics marketing and sales and service and you can think of this as something where this would be applicable to you know perhaps a product like a pair of shoes if you produce a pair of shoes you would go across through this whole thing so if you start off with involving mystic this would be the raw materials and the labor a few producing shoes this would be the the rubber the leather and of course the labor the people who come to the factory to actually build those shoes put those together in our case it would be ideas and code and documentation and all the contribution that we provide to sugar the project itself now for sugar labs it would be the kinds of things that we provided input into sugar labs again in terms of whether to the volunteer work or attend the next step is production and so looking at the sugar the project this would be where you bring in all the contributions from different people into a process where you can put it all together to make it work right so this would be the infrastructure where everything is hosted tested debugging this would be very much like the factory you would have to produce shoes then we have the next part which is the outbound logistics and this is where the so when the release manager says here the release 108 that's taking all the code that came in from here through the operations and then saying it will be basically free the bunch of things and say this is what we produce or for instance when all pc says we'll take a bunch of sugar stuff so this is the supply side process where you have raw materials and labor coming in production happening and then you do distribution and shipping so it comes out of distribution and shipping is effectively a release in our case of say sugar or an old pc image in case of all pc where they put it together and and shipping up but this is where with respect to software projects the software comes up especially with open source free and open source projects this is where the the output is the tarball perhaps or the the decatur depository and next comes the marketing and sales section so often in free and open source projects this is the part that is not focused on because a lot of the work is done on the supply site with the thinking that once the code is produced it can speak for itself and marketing and sales comes with an afterthought particularly sales because in many cases you know we're not selling anything that is no sale effectively but here the word sales is more to do with not necessarily transaction money but saying I agree with what you are saying and therefore I will you know move in the direction to adopted marketing is that link which is what helps us manage perceptions for any population or any so think of we we have these conversations about mailing lists being for developers vs teachers two very different groups and often developers are ok with email lists and IRC but teachers are not this has to do with managing perception because in the world of feature the way they manage things is software developers do teachers are not comfortable with a lot of things that software development people are and so even though the the software that is the teacher in this case is not able to see how that fits in her world and so they say you know this is not something i want to deal with it or perhaps i'll give you another example like when we start the semester let me begin with the textbook and some kind of a software package or tool that comes with the textbook for addressing certain certain problems you know in now if the software kept on changing every few weeks it becomes very hard to manage that class so there is expectation that the software essentially stays the same the the user interface doesn't change the the features essentially stay the same for the duration of a semester or so these are all very different perceptions that people have and a lot of the marketing stuff is about managing those perceptions and then that leads into sales if you manage those perceptions well then your target population will be closer to actually adopting and therefore be the sale section and eventually it is a fifth one which is service and this has to do with things like consulting and perhaps some of the consulting stuff in our case would be the process of working with educators working with principal school district people do to clarify the value proposition in a sense that there's all this good stuff that happened on the left side here the supply side but why is it important for them what role can it play in many cases it may be evident to us that match to them we may know that little there's all this good stuff and sugar that you can use kids can learn a lot of things but perhaps not evident to the other side especially the people who make decisions and so that's where this comes in which is the ability to provide some kind of a service beyond actually making the decision or making the sale where they adopt the software so there's a 50 some real well maybe come back to this later so the way this is split is you've got a supply-side on the demand side you can work on the supply side and produce a lot of software but if you do not work very few people would not what it is and so for instance the largest customer sugar is all pc but outside of all pc there are very very few people who and so until the right side of the value chain is managed and extended that is something that will not happen and that's where the details of marketing so on commit so this is this is the value chain instrument that may perhaps be useful to understand that the activities on the left side versus the right side are two very different kinds of things i often see this conflict or disagreement on email lists where marketing is something that's an afterthought it's a one-time thing you know let's go and raise some money let's do ads and those kinds of things and it's not quite that simple yeah it's a very different way of managing things and I also notice that many open-source projects will have a lot of appreciation for the left side but not so much for the right side and that's just the nature of how the projects are we spend so much time on the next site of the chain that it's kinda hard to look at the things on the right side now that on the contrary view for instance went to a business school you will see how the right side actually extends the value of the website it's not replacing it to start left versus write the value actually increases when you go from the left to the right and so to increase the value of what is produced by say sugar the fourth and the fifth blocks here have to be worried about

so this is a typical strategy crosses that you begin with vision once you have a vision statement then you look at a mission statement when you look at goals when you look at objectives and tasks and the way these are divided is typically along the lines that vision and mission is supposed to be long term and long term is a relative thing but in the in that relative scope original mission or long-term items that is that they should not change for the long duration with goals and objectives can be midterm so short and long term so there is an inherent hierarchy here and i suspect that because there is an it also doesn't lend itself relieved well too many free and open source software products because what I've seen in other products that I've worked with is that a lot of the work done in software development in these projects tend to be here and be the tasks section so lots of short iterative tasks so that whole concept of released early release often happens in this is this layer here about the tasks but as you go further up the exactly time to get slow because they don't change as much and because we tend to be close to the it's harder to them say oh there's anything worthwhile further up here so why bother but it's important to have this understanding that the strategy a tiered process with long-term mid term and short term so if i have to give examples i would say save vision and mission statements should be somewhere in the range of three to five years then you can look at goals and objectives which would be perhaps in the 18 month time frame maybe 12 month time frame and then that can be broken down into tasks of three to six months and either again to set of numbers but to give you an estimate if you're working on tasks which are in the range of three to six months it's hard to them switch and say oh there is something that does not change for five years but ideally you do want your original mission to mark change often because it's supposed to give you direction and that direction should be so if we were to for instance look at the old pc project 2007 is when they this is 2016 9 years out you know we'd want for things to stay stable for a long duration of time and then you know perhaps the nature of the problem will change as it has been the things like a whole bunch of other devices that are there in the market that did not exist back then and so you may have to them go back and revise your vision original mission and then follow the goals and objectives from that and the tasks so this is a typical strategy process the vision statement is it's a dream statement as in we dream to be this in X number of years where do we think we will be next number of years so again should reverse the sugar labs the door should be different but it would be along those lines which is maybe sugar will be used by twenty-five percent of the schools in the US are our it will be used by one-third of the the children of the world is purposefully nonspecific because it's something that is very hard to assess but you have to have something some kind of a place to be in X number of years so that becomes the vision and in our case I guess we're still working on what that vision should be so leave it at that and then the mission part is the water my mission statement is you know what are so and again i will specify that sugar levels of sugar those are two different things so then it needs to be a mission statement for sugar labs and a mission statement for sugar and they can be similar which would allude to some alignment and then questions like what is it that we do so like what sugar laps to sugar labs supports Foster's facilitates defense I don't know those are the different kinds of words to look at why is it that so what is the purpose of this and then it also holds good for the 4 X number of years where we would want the vision and mission to have approximately the same life cycle so by the time you think your vision is getting stale it would be time to devise not just a vision but also the mission so that they're both at the same for the same number of years I think this statement has multiple parts to it that may or may not qualify as the mission statement but again that's not my exercise to take on it's something that sugar Labs has to figure out so for instance the first part there sugar lapses volunteer-driven member yes and then it is part of the sfc and it originally came out of sugar lab what it is what it is that sugar labs actually does so vision is very hard to be and mission is based on what we know here and now so there is a difference of time which is mission is typically grounded with of course there are no guarantees but unless we figure out where we would like it's kind of hard to get there you can think of it as a bus where the mission the back wheels that actually push the bus and the vision is the steering column and the front wheels that actually provide direction to enable us to get there so these are the two things that are important and this is where we so this is we would begin with vision and mission and then move on to the

it is also broad-based so it's not very specific but it is a little more specific than the vision part so for instance increase the adoption of sugar in the education sector and now i'm not saying an option by what percentage or which market just sort of increase the adoption of sugar in the education sector so that's a goal to fulfill that goal for instance we would come up with specific targets and will become the objectives so specific targets that has helped achieve those so in this case for instance you will see increased translations by three percent in the next six months so that's the metric that's the number we are looking at and I can be may or may not achieve that objective but it's and so this is going further down in that hierarchy of being more specific now how do you increase translations by three percent that's where the tasks would come it and it would be like that these are the things we have to do so this is the activity part which will help execute or our help achieve those so you do this task this may help us achieve the objective which then these are also short term and so for instance it may be to sign a partnership

then comes this business of Swat strengths weaknesses opportunities and threats this is another thing we've done an exercise like this in the past i believe it's useful but where does it fit in the whole map so this is kind of where it fits we do the original mission when we start to willingly they have to come from someplace and swat is where they come so once you're done with SWAT you would pull a list of goals from SWAT and obviously you cannot go through all of those so you would prioritize and say let's take these four for these five and then build the objectives on that so let's see what happens with SWAT so it basically has about strengths weaknesses opportunities and threats again this is specific to the unit of analysis so if I did it's what i would do it for sugar laps and I would look at sugar labs as to what the strengths are off sugar labs and weaknesses and the the interesting distinction here is if you look vertically there is strength and opportunities of the plus points of those are helpful weaknesses and threats are harmful but more importantly we've got the other distinction which is this that strengths and weaknesses are internal to an organization where as opportunities and threats are external and this is an important distinction because you know what it's easy to understand what's this part has well basically the internal part is something that we can we can control because its internal to the organization so the things that we have within sugar labs are the things that we can work on external is something that's not in your control and so the most you can do is either avoid or average but you can actually change the external origin the origin items such as strengths and weaknesses so this is an important distinction in swat is that once you do so what you split and look at internal external understand that internal is what we control that the external so next and then you know in terms of doing the swot analysis we would basically say okay let's make a list of all the sprints the sugar house on the weakness of the sugar laps house all the opportunities that your labs has and all once you do that we start to prepare those and the pairing happens again internal versus external so we will do pairing likes trends and opportunities what are we good at and one of the opportunities out there you combine similarly you look at weaknesses that sugar Labs has opportunities that exist can we convert some of the weaknesses easily and intuitively easily so that we may pursue those opportunities so that becomes a conversion . strength and what are the threats that are out there what are we good at can we use our strength to actually reduce some of those threats and if not then just move on and then finally weaknesses and threats which is we know we are not very good at certain things can we actually defend ourselves from so you end up at four combinations pursue convert reduce and defend and so so you can pull out a bunch of goals and then prioritize them and say these are these levels are not so easy and you would pick the number of ones that can be actually worked out so these would be the goals from these goals will would

so these four items here would give us those goals the goals and objectives somewhat measurable so we can come back to it in six months and say what did we actually say achieve three percent chance of translations are about right and in fact that's where the reports coming in are translation would be very helpful because they have some metrics so that is the whole process I said this is very important which is the lens that we use so personally for me i'm going to focus on demand of sugar labs sugar is a project that i've used

extracting data from the journal analyzing it doing some analytics working on that stuff but at this point my position and my strength is with the organization sugar labs itself so that's the lens i'm going to use and even if i I'm going to look at it from the lens of sugar lap so this is one important point the value chain part is for your understanding of how marketing work so that's another conversation to be had but the important thing here is that the right side here the demand side is really what matters in extending the value of what sugar already produces and then finally this map here and if you vision mission is long term so even if you don't know five years that's a be 23 years vision mission will be three years goals objectives would be 12 to 18 months passed so would be three to six months and the third part would be to skip ahead SWAT to come up with some specific goals and basically do this so I may do water to other screencasts in the spain same area to to help i will also reiterate as I've done in a couple of my emails before that let me forward here that the the approach to being able to come up with a consensus-builder vision statement is not something where we threw out a bunch let me copy paste your cut yours and you know Adam glued together and come up - coming over with with a vision statement and a mission statement but it it's not something that can be done for the board meeting or just sending in fact there are lots of things that happen an email that tend to amplify the so there are different ways to do it I'm happy to suggest that support and even helped run some of those things but it is important for i think the the sugar labs oversight board and the sugar community to understand that these are things that have a specific process and they take time so i hope this helps

Marketing Team

2016-06-24T12:22:18Z

Davelab6: Title sections, add more walter ideas

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>
'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.'''
Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet.
It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.
</div>

{{TOCright}}

{{:Marketing Team/Mission}}

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Sean's 2009 - 2015 Overview ==

Sean Daly acted as Marketing Team Coordinator 2008-2016, and when he stepped down on June 23 2016 he offered the following overview:

The 2009 marketing strategy we implemented, based on Sugar on a Stick, was very successful for a time during the netbook boom, but today's environment is very different with tablets, iOS/Android, etc. I had suggested two other ideas since then to the community to facilitate Sugar for teachers: prebuilt VMs for VirtualBox, and preloaded bootable SD cards and branded cases for Raspberry Pi. Since then, Lionel has developed Sugarizer, which in my view deserves serious consideration for marketing initiatives targeting teachers. Dave's efforts to identify a reference platform are also useful.

Samuel suggested a SWOT analysis today - it's an excellent suggestion, the last one we did is now way out of date. Work with Samuel and Dave and Samson on that, it will be helpful even for project recruitment which is their focus. A competitive landscape survey will be complementary to the SWOT. When the community reaches consensus on the project's vision, work on marketing objectives (as opposed to project objectives) can be done. This usually involves a calendar with what actions are planned. If budget is available, you will want metrics - ways to measure spend effectiveness.

Brand values: this is about how Sugar is different from anything else. We always emphasized low-floor, no ceiling; support for minority languages which for-profit companies ignore; the pedagogical pedigree; View Source; collaboration; the Journal.

There is also the PR aspect - targeting journalists, bloggers, and influencers. Communiqués are important for allowing a site visitor to get an idea of the project's direction in just a few minutes. Historically, we put PR on newswires. But these days, social media is very effective. Here's a tip for news coverage: if an initiative will influence large-buyer decisions (education ministries), or represents a real innovation (value proposition for less than what people usually pay), there could be press interest.

The ongoing challenge is overcoming negative image perceptions of OLPC - that the $100 unit price didn't happen, that the project was somehow influenced by Microsoft, even that the project still exists. There is also an identified issue that our slick logo encourages a perception that we are a for-profit startup, not a nonprofit volunteer org. this is why we said "Nonprofit" in many of our PR communiqué titles.

My advice is to not waste time documenting the 2009-2010 strategy or my 2011-2012 attempts to develop a new one. Start from scratch - a SWOT analysis and competitive landscape is the starting point. Translate the SL project objectives into marketing objectives, define a calendar and metrics. You've stated recruitment objectives, but not a strategy... execution (facebook + Google AdWords) seems already decided, which IMHO is putting the cart before the horse, but no big deal.

https://wiki.sugarlabs.org/images/4/47/MCFE_Final_Presentation_SugarLabs_12-11.pdf

Caroline Meeks put together the SWOT analysis in this prez. I don't remember if I had assisted with that. I seem to remember having worked on another. I will search my offline archives, which are very complete concerning SL - I have everything from when I started.

This may be useful for very brief marketing strategy historical overview
http://lists.sugarlabs.org/archive/marketing/2013-November/003607.html

The success of the SoaS marketing initiative encouraged some SL members to assert control over the name, the trademark, the technical architecture, and the marketing of it. As a result the lead developer of SoaS left the project.

Peter had justifiably complained on IRC around 2010 that there was no marketing strategy page. I had chosen not to create one at the time because OLPC was involved in fierce competition with Intel Classmate offerings running Windows, and we were aware that our marketing initiatives were being monitored. This lack of clarity may have been a mistake, but my goal had been to disrupt the MS/Intel sales force talking points. The marketing team which was numerous at the time all knew the strategy.

=== Walter's 2016 Marketing Plan ===

Walter Bender offered this view for future marketing efforts:

What I would like from marketing is some mechanism for highlighting the powerful ideas in Sugar that seem to be lacking in most other systems so that even if a school decides to go with a different product/project, they put pressure on that project to provide tools, not apps, collaboration, transparency, self reflection and group critique, and responsibility on the shoulders of students and teachers to shape their own world.

A few observations/thoughts that may help us in focusing our marketing efforts:

(1) The primary source of push back in AU re Sugar was the browser. Schools had websites that they were interested in accessing that were not supported by Browse at the time. This is something we can turn around in the devel team and maybe something we need to surface in marketing: that Sugar is web/cloud enabled on top of all its other virtues. (I had been keeping the name "cloudberry" in reserve for this.) Ironically, at the time we added Sugar extensions for access to Google Drive (among other clud-based services), NSW got in bed with Microsoft and prohibited schools from using non-MS cloud services. OLPC AU never promoted the Sugar cloud-enabled features.

(2) The switch to Windows 10 by OLPC AU is a total capitulation to the "we don't have a clue as to what is of value in terms of pedagogy, so we'll make a deal with whomever will give us the best deal camp." Not sure what our response should/can be in such circumstances.

(3) There is a still strong interest in Sugar in Paraguay and some momentum to go national. We could try to ride that wave. We've been invited to come to Paraguay in October.

(4) I'm pushing hard in Chile... we'll see what happens.

(5) In UY, they are still using Sugar in primary schools (on Ubuntu). We should market in the Ubuntu space (I had had an offer from Ubuntu to let us do the equivalent of a Fedora Spin which we could follow up on).

(6) We should push on Red Hat to give us more exposure.

(7) Can we get a Sugarizer pilot going in a school to get a sense of what it means.

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== Google Non Profits AdWords ===

SL is obtaining $10,000 per month AdWords credit that Google offers to nonprofits and will use to run adwords campaigns by these members:

* Dave Crossland
* Sean Daly
* Samson Goddy
* Walter Bender

The marketing strategy will be to seek new members. Three kinds of members will be sought: (1) software developers, to write python and javascript programs (2) translators, to localize the programs, and (3) technical authors, to increase adoption by specific audiences - parents and schools.

Next Goal: Obtain access to the AdWords account.

Deadline: July 30 2016

=== Local Labs Survey 2016 ===

Sugar Labs will survey end users to better understand how Sugar is being adopted and adapted.
See also

* [[Marketing Team/Local Labs Survey 2016]]
* In late 2015/early 2016, Sam Parkinson ran a survey on http://socialhelp.sugarlabs.org and wrote a report ([[Media:2016_Socialhelp_Survey_Analysis.pdf]]) and published the source data ([[File:2016_SocialHelp_Survey_Response_Data.ods]])

Next Goal: List as many end users as possible.

Deadline: August 30 2016

=== New Website ===

In late 2010, four students from the MIT Sloan MarketLab worked on a study of the Sugar Labs website.
Their conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues, as well as the technical orientation of our web presence.

* The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar
* Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]
* A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]
* The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

Our polished static website as a landing page for Sugar Labs was redone in March-May 2011, see [[Marketing Team/Website]] history

Next Goal: Get the SL 2016 Vision, Mission, and Goals approved by SLOBs

Deadline: September 15 2016

===Events===

See [[Marketing Team/Events]] for a table of events we are targeting.

Next Goal: List possible future events.

Deadline: September 30 2016

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/press

Next Goal: Draft the next press release; Develop a [[Marketing Team/Press contacts]] list with education-oriented publications.

Deadline: September 30 2016

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

Next Goal: List contributors active in 2016

Deadline: August 30 2016

=== Swag ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, umbrellas, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]]

Next Goal: Design new swag for 2016

Deadline: September 30 2016

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2016-06-24T12:17:09Z

Davelab6: Add more of Sean's proposals

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>
'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.'''
Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet.
It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.
</div>

{{TOCright}}

{{:Marketing Team/Mission}}

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Overview ==

Sean Daly acted as Marketing Team Coordinator 2008-2016, and when he stepped down on June 23 2016 he offered the following overview:

The 2009 marketing strategy we implemented, based on Sugar on a Stick, was very successful for a time during the netbook boom, but today's environment is very different with tablets, iOS/Android, etc. I had suggested two other ideas since then to the community to facilitate Sugar for teachers: prebuilt VMs for VirtualBox, and preloaded bootable SD cards and branded cases for Raspberry Pi. Since then, Lionel has developed Sugarizer, which in my view deserves serious consideration for marketing initiatives targeting teachers. Dave's efforts to identify a reference platform are also useful.

Samuel suggested a SWOT analysis today - it's an excellent suggestion, the last one we did is now way out of date. Work with Samuel and Dave and Samson on that, it will be helpful even for project recruitment which is their focus. A competitive landscape survey will be complementary to the SWOT. When the community reaches consensus on the project's vision, work on marketing objectives (as opposed to project objectives) can be done. This usually involves a calendar with what actions are planned. If budget is available, you will want metrics - ways to measure spend effectiveness.

Brand values: this is about how Sugar is different from anything else. We always emphasized low-floor, no ceiling; support for minority languages which for-profit companies ignore; the pedagogical pedigree; View Source; collaboration; the Journal.

There is also the PR aspect - targeting journalists, bloggers, and influencers. Communiqués are important for allowing a site visitor to get an idea of the project's direction in just a few minutes. Historically, we put PR on newswires. But these days, social media is very effective. Here's a tip for news coverage: if an initiative will influence large-buyer decisions (education ministries), or represents a real innovation (value proposition for less than what people usually pay), there could be press interest.

The ongoing challenge is overcoming negative image perceptions of OLPC - that the $100 unit price didn't happen, that the project was somehow influenced by Microsoft, even that the project still exists. There is also an identified issue that our slick logo encourages a perception that we are a for-profit startup, not a nonprofit volunteer org. this is why we said "Nonprofit" in many of our PR communiqué titles.

My advice is to not waste time documenting the 2009-2010 strategy or my 2011-2012 attempts to develop a new one. Start from scratch - a SWOT analysis and competitive landscape is the starting point. Translate the SL project objectives into marketing objectives, define a calendar and metrics. You've stated recruitment objectives, but not a strategy... execution (facebook + Google AdWords) seems already decided, which IMHO is putting the cart before the horse, but no big deal.

https://wiki.sugarlabs.org/images/4/47/MCFE_Final_Presentation_SugarLabs_12-11.pdf

Caroline Meeks put together the SWOT analysis in this prez. I don't remember if I had assisted with that. I seem to remember having worked on another. I will search my offline archives, which are very complete concerning SL - I have everything from when I started.

This may be useful for very brief marketing strategy historical overview
http://lists.sugarlabs.org/archive/marketing/2013-November/003607.html

The success of the SoaS marketing initiative encouraged some SL members to assert control over the name, the trademark, the technical architecture, and the marketing of it. As a result the lead developer of SoaS left the project.

Peter had justifiably complained on IRC around 2010 that there was no marketing strategy page. I had chosen not to create one at the time because OLPC was involved in fierce competition with Intel Classmate offerings running Windows, and we were aware that our marketing initiatives were being monitored. This lack of clarity may have been a mistake, but my goal had been to disrupt the MS/Intel sales force talking points. The marketing team which was numerous at the time all knew the strategy.

Walter Bender offered this view for future marketing efforts:

''What I would like from marketing is some mechanism for highlighting the powerful ideas in Sugar that seem to be lacking in most other systems so that even if a school decides to go with a different product/project, they put pressure on that project to provide tools, not apps, collaboration, transparency, self reflection and group critique, and responsibility on the shoulders of students and teachers to shape their own world.''

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== Google Non Profits AdWords ===

SL is obtaining $10,000 per month AdWords credit that Google offers to nonprofits and will use to run adwords campaigns by these members:

* Dave Crossland
* Sean Daly
* Samson Goddy
* Walter Bender

The marketing strategy will be to seek new members. Three kinds of members will be sought: (1) software developers, to write python and javascript programs (2) translators, to localize the programs, and (3) technical authors, to increase adoption by specific audiences - parents and schools.

Next Goal: Obtain access to the AdWords account.

Deadline: July 30 2016

=== Local Labs Survey 2016 ===

Sugar Labs will survey end users to better understand how Sugar is being adopted and adapted.
See also

* [[Marketing Team/Local Labs Survey 2016]]
* In late 2015/early 2016, Sam Parkinson ran a survey on http://socialhelp.sugarlabs.org and wrote a report ([[Media:2016_Socialhelp_Survey_Analysis.pdf]]) and published the source data ([[File:2016_SocialHelp_Survey_Response_Data.ods]])

Next Goal: List as many end users as possible.

Deadline: August 30 2016

=== New Website ===

In late 2010, four students from the MIT Sloan MarketLab worked on a study of the Sugar Labs website.
Their conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues, as well as the technical orientation of our web presence.

* The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar
* Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]
* A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]
* The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

Our polished static website as a landing page for Sugar Labs was redone in March-May 2011, see [[Marketing Team/Website]] history

Next Goal: Get the SL 2016 Vision, Mission, and Goals approved by SLOBs

Deadline: September 15 2016

===Events===

See [[Marketing Team/Events]] for a table of events we are targeting.

Next Goal: List possible future events.

Deadline: September 30 2016

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/press

Next Goal: Draft the next press release; Develop a [[Marketing Team/Press contacts]] list with education-oriented publications.

Deadline: September 30 2016

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

Next Goal: List contributors active in 2016

Deadline: August 30 2016

=== Swag ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, umbrellas, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]]

Next Goal: Design new swag for 2016

Deadline: September 30 2016

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2016-06-24T00:50:08Z

Davelab6: add walter's vision

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>
'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.'''
Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet.
It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.
</div>

{{TOCright}}

{{:Marketing Team/Mission}}

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Overview ==

Sean Daly acted as Marketing Team Coordinator 2008-2016, and when he stepped down on June 23 2016 he offered the following overview:

The 2009 marketing strategy we implemented, based on Sugar on a Stick, was very successful for a time during the netbook boom, but today's environment is very different with tablets, iOS/Android, etc. I had suggested two other ideas since then to the community to facilitate Sugar for teachers: prebuilt VMs for VirtualBox, and preloaded bootable SD cards and branded cases for Raspberry Pi. Since then, Lionel has developed Sugarizer, which in my view deserves serious consideration for marketing initiatives targeting teachers. Dave's efforts to identify a reference platform are also useful.

Samuel suggested a SWOT analysis today - it's an excellent suggestion, the last one we did is now way out of date. Work with Samuel and Dave and Samson on that, it will be helpful even for project recruitment which is their focus. A competitive landscape survey will be complementary to the SWOT. When the community reaches consensus on the project's vision, work on marketing objectives (as opposed to project objectives) can be done. This usually involves a calendar with what actions are planned. If budget is available, you will want metrics - ways to measure spend effectiveness.

Brand values: this is about how Sugar is different from anything else. We always emphasized low-floor, no ceiling; support for minority languages which for-profit companies ignore; the pedagogical pedigree; View Source; collaboration; the Journal.

There is also the PR aspect - targeting journalists, bloggers, and influencers. Communiqués are important for allowing a site visitor to get an idea of the project's direction in just a few minutes. Historically, we put PR on newswires. But these days, social media is very effective. Here's a tip for news coverage: if an initiative will influence large-buyer decisions (education ministries), or represents a real innovation (value proposition for less than what people usually pay), there could be press interest.

The ongoing challenge is overcoming negative image perceptions of OLPC - that the $100 unit price didn't happen, that the project was somehow influenced by Microsoft, even that the project still exists. There is also an identified issue that our slick logo encourages a perception that we are a for-profit startup, not a nonprofit volunteer org. this is why we said "Nonprofit" in many of our PR communiqué titles.

Walter Bender offered this view for future marketing efforts:

''What I would like from marketing is some mechanism for highlighting the powerful ideas in Sugar that seem to be lacking in most other systems so that even if a school decides to go with a different product/project, they put pressure on that project to provide tools, not apps, collaboration, transparency, self reflection and group critique, and responsibility on the shoulders of students and teachers to shape their own world.''

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== Google Non Profits AdWords ===

SL is obtaining $10,000 per month AdWords credit that Google offers to nonprofits and will use to run adwords campaigns by these members:

* Dave Crossland
* Sean Daly
* Samson Goddy
* Walter Bender

The marketing strategy will be to seek new members. Three kinds of members will be sought: (1) software developers, to write python and javascript programs (2) translators, to localize the programs, and (3) technical authors, to increase adoption by specific audiences - parents and schools.

Next Goal: Obtain access to the AdWords account.

Deadline: July 30 2016

=== Local Labs Survey 2016 ===

Sugar Labs will survey end users to better understand how Sugar is being adopted and adapted.
See also

* [[Marketing Team/Local Labs Survey 2016]]
* In late 2015/early 2016, Sam Parkinson ran a survey on http://socialhelp.sugarlabs.org and wrote a report ([[Media:2016_Socialhelp_Survey_Analysis.pdf]]) and published the source data ([[File:2016_SocialHelp_Survey_Response_Data.ods]])

Next Goal: List as many end users as possible.

Deadline: August 30 2016

=== New Website ===

In late 2010, four students from the MIT Sloan MarketLab worked on a study of the Sugar Labs website.
Their conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues, as well as the technical orientation of our web presence.

* The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar
* Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]
* A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]
* The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

Our polished static website as a landing page for Sugar Labs was redone in March-May 2011, see [[Marketing Team/Website]] history

Next Goal: Get the SL 2016 Vision, Mission, and Goals approved by SLOBs

Deadline: September 15 2016

===Events===

See [[Marketing Team/Events]] for a table of events we are targeting.

Next Goal: List possible future events.

Deadline: September 30 2016

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/press

Next Goal: Draft the next press release; Develop a [[Marketing Team/Press contacts]] list with education-oriented publications.

Deadline: September 30 2016

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

Next Goal: List contributors active in 2016

Deadline: August 30 2016

=== Swag ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, umbrellas, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]]

Next Goal: Design new swag for 2016

Deadline: September 30 2016

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

2016 Goals

2016-06-23T20:19:33Z

Davelab6: Clean up https://wiki.sugarlabs.org/go/Sugar_Labs/Teams

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO,
**
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to liberate the ''Learning To Change The World'' text;
** to write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]);
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website;
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* clean up [[Sugar Labs/Teams|Sugar Labs/Teams;]]
* [your goal here]

Marketing Team/Coordinator

2016-06-23T20:19:17Z

Davelab6: Sean -> Dave

[[User:Davelab6|Davelab6]]

Marketing Team

2016-06-23T20:11:10Z

Davelab6: Rework page

Marketing Team

2016-06-23T04:53:35Z

Davelab6: Add adwords project

2016 Goals

2016-06-22T15:51:42Z

Davelab6: note adwords blocked on Conservancy, add Sean's RPi enclosure idea;

''The following is a DRAFT, that will eventually be presented to the Sugar Labs Oversight Board at a regularly scheduled monthly meeting as a motion to approve it for the year.''

''Your edits are welcome!''

''You may also enjoy the [[Vision proposal 2016]] page''

TODO: convert this structured list into a spreadsheet (and then back into a wiki table with [http://marianogappa.github.io/mediawiki-table-utility/ http://marianogappa.github.io/mediawiki-table-utility]) with cols for who/when/etc

== Software Goals ==

* to successfully complete our six GSoC projects;
* to make two releases of Sugar, one in February (0.108) and one in October (0.110);
** to package 0.110 for Fedora and Debian;
** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
** to check that all activities work well on the XO-1;
** to make a release video, similar to the [https://www.youtube.com/watch?v=PXFaXAGIw04 release video for 0.106];
* to allow Sugar Activities to run outside Sugar;
** on GNOME/KDE/XFCE and other free desktops;
** on ChromeOS;
*** with [http://www.howtogeek.com/208368/how-to-run-a-full-linux-desktop-in-a-browser-tab-on-your-chromebook/ Crouton];
*** with broadway;
** on Windows;
** on Mac OS X;
* to port more Activities to Sugarizer, the web-based version of Sugar;
* to port Activities from PyGTK+3 to PyQt ([http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt docs]);
* to localize the activities/games that were produced in collaboration with the children of the Seed-Programmers Workshop+SugarCamp in Chía (La ciudad de la luna ;) Colombia in 2014;
* to make "Sugar On A Stick" into "Sugar Local Lab On A Stick," so that sugar communities without active/direct internet connections can do more to self-support themselves, and eventually upload what they have back to the central repos;
* to make Sugarizer self-translatable, and via sugar-web thus make sugar desktop self-translatable;
* to complete the documentation of the Sugar toolkit;
* to consolidate all active development to Github (see [[Infrastructure Team/Migrating to GitHub]]);
** to transfer the repositories of all of the core Sugar activities to github.com/sugarlabs, and set Gitorious read-only;
** to transfer the issue tracking from bugs.sugarlabs.org to github.com/sugarlabs, and set Trac read-only;
** to transfer the development discussions from sugar-devel to the issue tracker, and set the list read-only;
* to measure Sugar against the LF CII Best Practices (https://bestpractices.coreinfrastructure.org/ [https://github.com/sugarlabs/www-sugarlabs/issues/47 + www-sugarlabs#47]);
* Improve ASLO (which is by far the most important web service of Sugar Labs according to http://stats.sugarlabs.org/);
** to link each activity entry to its github repo;
** to tag each activity entry with the releases that it is known to work with;
** to identify each activity entry as working/unavailable for each version of the XO;
** to update each activity to use the cpu architecture and sugar toolkit version detection (in newer releases) to ensure there is is a single canonical version of each activity;
* to ensure all Sugar Labs services are running the latest versions;
* change the UI font to noto;
* to update the Sugar HIG;
* to improve support for touch only based interfaces (e.g. virtual keyboard support);
* to revisit original Sugar design goals and see if any are able move forward (overlay chat, bulletin board, Journal object vs action view, Journal versioning UI, etc);
* to gather feedback and usage information from real users to improve the design loop;
* to sign all commits on core repos ([https://help.github.com/articles/signing-commits-using-gpg/ details]);
* to have all github members use 2-factor authentication;
* to have an activity for [http://www.qb64.net qb64] (LGPL) which per http://www.nicolasbize.com/blog/30-years-later-qbasic-is-still-the-best/ is the best for very young kids (7 years) to learn code with typing;
** to have an activity for https://github.com/antirez/load81;
* review http://www.hackety.com/questions for UX ideas;
* to add a simple [http://www.lowband.org www.lowband.org] integration into Browse;
* to curate ASLO,
**
* [your goal here]

== Organization Goals ==

* to fully staff all boards, offices, and committees;
* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
* to make a release event for the 0.110 release;
** to track the event with https://github.com/OpenTechStrategies/streetcrm;
** to hold a "new contributor day" event, at which the experienced contributors meet with the newcomers and, together, work through the new-contributor documentation that the experienced folks themselves have written. That lets the two communities work together, and it lets the experienced coders see firsthand what struggles the new contributors encounter—including, notably, where the new-contributor documentation is falling short. Having "onboarding" documentation was important, and equally important is to encourage bug reports and patches to that documentation from new contributors as they work through it (edited from [https://lwn.net/SubscriberLink/687736/ba8b082ec178312a/ lwn]);
** to screen the "Web" documentary (as OLPC SF Summit 2015 did, [http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg15273.html reference]);
* to find and develop as a reference a new laptop for kids with;
** required attributes
*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
*** zero proprietary software (in bios, firmware, drivers, soundcard, wifi, graphics card, etc) such that it becomes FSF endorsed;
** desirable attributes
*** rugged casing
*** low power consumption
*** sunlight-readable screen (as found in the XO and nowhere else)
* to offer github.com/sugarlabs organization membership as a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;
** to find out and document on the site why past deployments moved away from Sugar Desktop;
** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);
** to show the finances on the website. https://github.com/NYCComptroller/Checkbook might be relevant, and also https://github.com/OpenTechStrategies/anvil which wraps [https://github.com/ledger/ledger ledger-cli] which Conservancy uses at the moment. (Conservancy also started a replacement - http://npoacct.sfconservancy.org/ - but per [http://lists.sfconservancy.org/pipermail/npo-accounting/2014q4/thread.html this discussion] it has stalled out.
* to successfully apply for Sugar to be listed in https://education.github.com/pack;
* to liberate the ''Learning To Change The World'' text;
** to write a new and more detailed history of Sugar ([http://lists.sugarlabs.org/archive/sugar-devel/2013-January/041578.html reference]);
* to raise funds
** to develop a supporting members list, by making a 'super list' with as many possible members as possible, such as from [[Special:LastUserLogin]] (admins only) and mailman and [[Sugar_Labs/Members/List]];
** to make persistent quarterly attempts to contact members until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or explain why they don't want to make a donation;
** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816);
** to find out of US DoE funding for Open Education is available ([http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg10761.html reference]);
** to successfully apply to Y Combinator ([https://80000hours.org/2015/08/why-is-80000-hours-in-y-combinator-as-a-non-profit-and-whats-it-like/ reference]), [http://www.newschallenge.org/ Knight Foundation grants], and [http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=12819&org=OISE&from=home NSF/USAID grant];
** (more ideas in https://titanpad.com/SLFC);
* to run a joyful election for the 2017 board;
** to deploy a SL instance of the https://dem.tools Elections app (https://github.com/nditech/elections) or https://github.com/OpenTechStrategies/openstv, or if our own voting tool is not ready in time, use http://civs.cs.cornell.edu again ([http://lists.sugarlabs.org/archive/iaep/2015-March/017291.html reference]) ;
** to get an accurate list of active members. There are some 'ambient' lists of members - eg, the wiki's usernames list, the total of all emails subscribed to all mailing lists - and then the list at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List is and the subset of that at https://wiki.sugarlabs.org/go/Sugar_Labs/Members/Survey2015 - However, this subset is unreliable, so we'll develop a 'super list' with as many possible members as possible, and then make persistent attempts to contact them until they show they are active members.
* to run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]]);
* to host the http://turtleartday.org website;
* to implement specific outreach strategies for:
** homeschool/unschool parents/families;
** families with children on the autism spectrum;
** montessori private/charter schools;
** regular private/charter schools;
** regular state schools;
*** to create detailed guides describing how Sugar can be integrated with 1 US state curriculum, derived from work Claudia and Mellisa did for OLPC-A;
** regular state school districts;
*** to solicit the requirements that 1 school district has to deploy Sugar (such as any tweaks to the software that they require);
** (This [http://theconversation.com/why-schools-should-provide-one-laptop-per-child-58696 theconversation] article is a helpful lead in this direction)
* to work with OLPC Inc. to:
** get an end-of-life schedule for each XO model, either privately or publicly;
** get their lesson plans for Sugar, either privately or publicly;
** remove everyone from http://one.laptop.org/about/people that is no longer involved in the project;
** chat with each person who is actively involved in 2016 about what they are doing and what they would like to see changed in Sugar;
** align their roadmap with ours;
* to find a large organization to champion usage of Sugar, and be a willing reference when other organizations ask about using it to find a 2nd large org;
* to flush the ASLO update/new activities queue every week;
* to hold a [[Sugar Summit]] in October/November;
* to develop a marketing strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg01515.html;
** to develop a social media strategy, based on http://www.mail-archive.com/marketing%40lists.sugarlabs.org/msg00974.html;
** to sign up for https://www.google.com/nonprofits/account/signup/us?hl=en and then https://www.google.com/grants/ to run an AdWords campaign (currently blocked on Conservancy);
* to provide access to the Pratham StoryWeaver books (See thread "Re: [UKids] Fwd: [IAEP] StoryWeaverp");
* to make a Sugar-branded enclosure for Raspberry Pi 3, distributed through the RPi partner network;
* [your goal here]

Oversight Board/Decisions

2016-06-22T02:42:11Z

Davelab6: add link for GSOC

This page (largely complete) is intended to be a one-stop place for reviewing all of the Sugar Labs oversight board (SLOB) actions and decisions.

The date headlines are the date that the motion is agreed, disagreed, or - in the case of motions to be voted on via email within 7 days of posting which did not get voted on - failed by timing out.

== 2016-06-14 ==
;FAILED MOTION 2016-38 Dave Crossland: to consider email votes on motions only valid if they are sent to both the SLOBs and IAEP mailing lists. (not seconded)

== 2016-06-11 ==
;FAILED MOTION 2016-37 Tony Anderson: to undertake a fund raising drive. Arrangements will be made to enable on-line contributions by PayPal, debit or credit card or other means. Once the means to make contributions is in place, the Financial Manager will initiate and lead the drive. The Sugar Labs web site will show progress in donations toward the goal. (not seconded)

== 2016-06-10 ==
;FAILED MOTION 2016-36 Dave Crossland: to vote on each motion proposed by a member, dropping the current practice of requiring a seconding before voting. (not seconded)
;FAILED MOTION 2016-35 Dave Crossland: to agree the following procedure for all future monthly SLOB meetings: the chair will confirm the meeting meets quorum; the chair will make any announcements submitted to them before the meeting; the chair will announce the first motion pending a vote on that day; each present SLOB member will announce their vote; the chair will announce the outcome of the motion; the chair will announce the next motion, until all motions are voted on; the chair will invite everyone attending to an open discussion of any topic until the meeting ends at the time scheduled. (not seconded)
;AGREED MOTION 2016-34 Dave Crossland: Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (5 votes for, 1 against, 1 abstain, see http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg16711.html)
;FAILED MOTION 2016-33 Laura Vargas: to update current SL vision statement ("About Sugar Labs(R): Sugar Labs(R) is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs(R) is supported by donations and is seeking funding to accelerate development.") to the new proposed text: "Sugar Labs is a global community where you can learn how to design, develop and deploy high-quality Free/Libre Software that facilitates self-discovery learning experiences and collaboration among young children of all continents." (not seconded)

== 2016-06-09 ==
;FAILED MOTION 2016-32 Dave Crossland: The value of $Y in the Finance Manager Guidelines should be $200 (not seconded)

== 2016-06-03 ==

[http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-06-03T19:01:08|IRC log]
;FAILED MOTION 2016-31 Dave Crossland: To adopt the [https://wiki.sugarlabs.org/index.php?title=Vision_proposal_2016&oldid=98911 Vision proposal 2016]. (not seconded)
;FAILED MOTION 2016-30 Dave Crossland: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa To add to the bylaws a new section, “Sugar Labs Oversight Board Spending Guidelines”] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-29 Dave Crossland: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa To append the following text to the existing bylaw for the Finance Manager office] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-28 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To define procedures for requesting, obtaining, and reporting use of SugarLabs funds] (dependent upon MOTION 2016-27)
;FAILED MOTION 2016-27 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded)

== 2016-05-29 ==

;FAILED MOTION 2016-26 Dave Crossland: To request donations from Sugar Labs Members, to be allocated to the General Fund through the SFC. The annual donation requested will be $12 USD from members who self-identify as low-income (such as students); $36, $120, or $600 USD from general members. (not seconded)

;FAILED MOTION 2016-25 Dave Crossland: To request a membership donation from each currently active Sugar Labs Member to be allocated to the General Fund for the calendar year of 2016, and a public statement about how they use Sugar and why they are involved in Sugar Labs to post on the website; there is no penalty for not paying a membership or not providing a statement; by default members who donate will be kept private, and requested to opt-in to be recognised. The donation requested will be $12 USD from members who self-identify as low-income (such as students); $36 USD from general members; $120 from members who can opt-in to be placed prominently on the website; and $600 from members who can (privately if they wish) submit a release codename, subject to SLOB approval. (not seconded)

;FAILED MOTION 2016-24 Dave Crossland: Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (not seconded)

== 2016-05-25 ==
;FAILED MOTION 2016-23 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To define procedures for requesting, obtaining, and reporting use of SugarLabs funds] (dependent upon MOTION 2016-22)
;FAILED MOTION 2016-22 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded)

== 2016-05-12 ==
;AGREED MOTION 2016-21 Walter Bender: to reimburse Edgar Quispe for expenses incurred representing Sugar Labs at the Traducción e interpretación en las lenguas originarias del Perú meeting in Lima. The cost is $168.88. (See http://lists.sugarlabs.org/archive/iaep/2016-May/018196.html)

== 2016-05-11 ==
;FAILED MOTION 2016-20: to allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit. (3 votes for, 1 vote against, and 4 abstains)

== 2016-05-06 ==
;AGREED MOTION 2016-19: To pay for laboratoriosazucar.org domain registration renewal
;FAILED MOTION 2016-27 Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded, further drafting requested)
;AGREED MOTION 2016-14: To fund a program to initiate the translation of Sugar into Yoruba. The work would be led by Samson Goddy and reviewed by Chris Leonard, in his role as Translation Community Manager (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052462.html]).
;AGREED MOTION 2016-13 Dave Crossland: To update the Sugar License from GPLv2 to GPLv3 [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052552.html]
;FAILED MOTION 2016-12: To allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052463.html]).
;FAILED MOTION 2016-11 Lionel Laske: To adopt the wiki Vision proposal for 2016 (not seconded)

== 2016-04-09 ==
;AGREED MOTION 2016-10 Walter Bender: To offer Devin U. an honorarium ($500) to compensate him since he needed to take a week off from work to run two Turtle/Music Blocks workshops at the Constructionism Conference. The funds would be allocated from the Trip Advisor grant which are in support of promoting and advancing Turtle Blocks around the world. (Vote taken by email.)
;AGREED MOTION 2016-09 Walter Bender: Walter, as PI of the Trip Advisor grant, will inform the SL oversight board of his plans for workshops that fall under the guise promotion of Turtle Blocks but otherwise has discretion in organizing and funding these events, within the budget constraints of grant and the travel guidelines of the SFC. (Vote taken by email.)

== 2016-04-07 ==
;FAILED MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): All funds raised by any Sugar Labs community member in the name of Sugar Project's translations must be directed to the “Sugar Projects Translation's Fund”. (not seconded)
;FAILED MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): The present SugarLabs Oversight board appoints the current Translation's Committee, with the full responsability of reviewing, upgrading, approving and overseeing Sugar Translation Projects and Proposals made by any interested party, with special attention to Native Languages communities. (not seconded)
;FAILED MOTION 2016-08a Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): Requests for funds will be presented to the Translation's Committee, in writing, with copy to the IAEP mailing list and the Localization mailing list, at least 72 hours in advance of the monthly scheduled "Translation Committee Meeting". Committe members shall vote during the meeting for approval by simple majority. All interested parties, must also send the proposal to the IAEP mailing list and the Localization mailing list, in advance. (not seconded)

== 2016-04-06 ==
;AGREED MOTION 2016-08: To approve the position of Translation-Community Manager as described at [[Translation-Community Manager]].
;AGREED MOTION 2016-07: That Chris Leonard be named to this position effective immediately.
;AGREED MOTION 2016-06: That the Translation-Community Manager be paid a stipend of $1000/month.

== 2016-04-01 ==
;AGREED MOTION 2016-05: In keeping with the board 2010's decision on this matter from a different era, it was suggest that if a Board Member (1) fails to vote and attend pre-scheduled Board meetings for more than 12 weeks, (2) resigns or (3) dies, then the Board is empowered and encouraged to appoint a replacement for this seat. Finally, just a clarification that the Replacement Board Member would be required to defend their seat during the very next election.

== 2016-03-04 ==
;AGREED MOTION 2016-04: Based on [[Translation Proposal]], Tony (and other SLOB members) should write up a job description with goals and reporting structure for a coordinator position to be submitted to the SFC.
;AGREED MOTION 2016-03: Restrict email voting to 1 week going forward, to remove confusion from the current voting process, keeping focus. Board members' email votes would be required to arrive within One Week Maximum (168.0 hours) of the original motion. (Any motion that fails to pass within this 1-week sunset period, can of course be attempted again in future, e.g. if long-term overseas/off-grid/medical absences require another later vote on the same topic).

== 2016-02-12 ==
;AGREED MOTION 2016-02: Moving regular SLOB meeting dates to the first Friday of the month at 16UTC
;AGREED MOTION 2016-01: Apply for GSoC 2016 (Lionel and Walter as co-admins)

== 2015-12-17 ==
;FAILED MOTION 2015-07(3 In Favor, 4 Abstentions): to pay Devin Ulibarri $500 for help organize and run the Turtle workshop in Bangkok
(See renewed motion passed on 2016-04-09.)

== 2015-10-12 ==
;AGREED MOTION 2015-06: Apply to GCI

== 2015-09-14 ==
;AGREED MOTION 2015-05: funding to file an affidavits required to maintain the registration of Sugar Labs' trademarks with the USPTO.
;ACTION: Walter to recruit mentors for GCI

== 2015-07-06 ==
;ACTION: acknowledged the numerous contributions to Sugar from the late Marco Presenti Gritti.

== 2015-05-06 ==
;AGREED MOTION 2015-04: via email to add Samson Goody to the Membership Committee (DONE)

== 2015-05-04 ==
;AGREED MOTION 2015-03: to share survey results with community (DONE)
;ACTION: Gonzalo to post results (DONE)
;ACTION: Gonzalo to write to each of the respondents
;AGREED MOTION 2015-02: that Claudia and Walter go to NI to discuss Sugar/OLPC future with the Zamoras
;ACTION: Walter to make a first pass at culling the decisions from past meetings into one page (this page)

== 2015-04-06 ==
;AGREED MOTION 2015-01: appoint Icarito and Caryl to the election committee and to try to recruit a youth member to the committee.

== 2015-01-14 ==
;ACTION: organize a summit to discuss the future of Sugar
;ACTION: do a survey to solicit feedback from deployments
0
== 2014-10-07 ==
;ACTION: Recruit mentors for GCI
;ACTION: Recruit candidates for oversight board

== 2014-07-08 ==
;AGREED MOTION 2014-02: on a .UY venue for a summit in September 2014. Jose Miguel and Daniel will get back to us about specifics.

== 2014-03-03 ==
;ACTION: everyone solicit students for GSoC

== 2014-02-05 ==
;AGREED MOTION 2014-01: to Gonzalo and Manuq's proposal for Background Image Contest

== 2013-11-04 ==
;AGREED MOTION 2013-06: Luke to run election for oversight board again
;AGREED MOTION 2013-05: to give cjl discretion over the i18n funds in the Trip Advisor grant

== 2013-10-18 ==
;AGREED MOTION 2013-04: we would apply again to Google Code In

== 2013-03-21 ==
;AGREED MOTION 2013-03: the next release will be Sugar 1.0

== 2013-02-25 ==
;AGREED MOTION 2013-02: to establish a category for Sugar Labs advisors/educators/friends
;ACTION: Claudia and Walter will meet to start planning Turtle Art Day
;AGREED MOTION 2013-01: to apply for Google Summer of Code 2013

== 2013-01-07 ==
;ACTION: ClaudiaU agreed to share ''Making Learning Visible'' with SLOB members (and Tonyf and JT4Sugar)

== 2012-05-30 ==
;AGREED MOTION 2012-05: to modify the Trademark and Local Labs pages in the wiki (See [[/Oversight_Board/Meeting_Minutes-2012-05-30#1._Updates_to_the_TM_policy_.28Trademark.29|TM Policy]] and [[Oversight_Board/Meeting_Minutes-2012-05-30#2._Updates_to_the_Local_Lab_wiki_.28Local_Labs.29|Local Labs Policy]])

== 2012-05-03 ==
;AGREED MOTION 2012-04: We approved a budget of up to US $5000 for two servers.
;AGREED MOTION 2012-03: Sugar Labs joins the SFC GPL enforcement program
;ACTION MOTION 2012-02: Walter to bring code-of-conduct discussion to the community.
;ACTION MOTION 2012-01: SLOB members to get signed agreements to the SFC regarding new SFC by-laws.

== 2011-12-02 ==
;AGREED MOTION 2011-09: The Sugar Labs Oversight Board thanked Bernie Innocenti and Mel Chua for their dedicated service to the community in their role as members of the oversight board.

== 2011-09-16 ==
;AGREED MOTION 2011-08: to keep the GSoC 2010 mentor funds as our general funds.

== 2011-08-05 ==
;AGREED MOTION 2011-07: to award Sugar participation certificates (See [[Oversight_Board/2011/Meeting_Minutes-2011-08-05#Certificate_program|Certificate Program]]).
;AGREED MOTION 2011-06: to give North Dakota State University authority to establish a local Sugar Lab.

== 2011-06-09 ==
;AGREED MOTION 2011-05: to endorse Free Software as defined here: http://www.gnu.org/philosophy/free-sw.html

== 2011-05-08 ==
;AGREED MOTION 2011-04: Bernie (head of infrastructure team) is authorized to approve spending tickets filed on the bug tracker up to $200.
;AGREED MOTION 2011-03: to update the governance page.

== 2011-02-10 ==
;AGREED MOTION 2011-02: SL endorses the idea that community members have kids: means more Sugar hackers in the future !!
;AGREED MOTION 2011-01: Local labs can issue Sugar certificates (and charge for this service whatever they want) but only if: (1) they maintain a page on our wiki explaining what content they use for training, where to download it, and what pricing they use; and (2) all the content they use for training is licensed under one of the licenses recommend by http://opensource.org/docs/osd and/or http://fedoraproject.org/wiki/[…]ing#Good_Licenses.

== 2010-12-13 ==
;AGREED MOTION 2010-10: [[Oversight_Board/Project_Motion]]
;AGREED MOTION 2010-09: SL would like to acknowledge and celebrate the marriage of acaire11 and icarito : the first Sugar marriage!!!

== 2010-12-01 ==
;AGREED MOTION 2010-08: Each active team and local lab should propose a few delegates from that team to SLOBs. We will invite the delegates to SLOBs meetings, and rotate scheduled times during SLOBs meetings to hear reports from their team or lab.
;AGREED MOTION 2010-07: The default time/day of the week for SLOBs meetings will be Thursdays at 15:00 EST (20:00 UTC)
;AGREED MOTION 2010-06: If a SLOB member misses one month of regular weekly meetings in a row, twice during one calendar year, SLOBs may find a replacement for their seat.

== 2010-09-28 ==
;AGREED MOTION 2010-05: We, the SLOB, acknowledge and praise the efforts of the release team for bringing us 0.90!!

== 2010-05-07 ==
;AGREED MOTION 2010-04: to a [[Trademark]] policy.

== 2010-03-05 ==
;AGREED MOTION 2010-03: (1) Bundles with non-Sugar dependencies be clearly marked in ASLO; (2) We work towards a mechanism for supporting access to non-Sugar dependencies--a specific endorsement of being open; and (3) We do not restrict ASLO while we progress towards #2.

== 2010-02-26 ==
;AGREED MOTION 2010-02: to authorize Bernie to spec out a machine around $2000, send details to systems@ for review, decide exactly where it will be hosted, then buy it.

== 2010-01-22 ==
;AGREED MOTION 2010-01: to authorize Luke Faraone to ship some used hardware from the Wikipedia Foundation (12 servers) to various hosting sites. The cost should not exceed US$300.

== 2009-12-18 ==
;AGREED MOTION 2009-18: Sugar Labs encourages all GNU/Linux distributions to package and distribute Sugar, and if possible will assist with hosting and infrastructure. SL Marketing may strategically decide to focus resources towards specific distributions in the interest of promoting Sugar more effectively.
;AGREED MOTION 2009-17: Yes, "Sugar on a Stick" should be reserved by Sugar Labs for use by the SoaS-Fedora distribution so that Sugar can be marketed effectively, until such time when a trademark policy, agreement, and process is put in place: SoaS will be the first project to go through that process.

== 2009-12-11 ==
;AGREED MOTION 2009-16: to adopt http://opensource.org/docs/osd as a set of guidelines for what is permitted on ASLO, for both software and content, and http://fedoraproject.org/wiki/Licensing#Good_Licenses's opinions on specific licenses where applicable, and always asking the SFC for advice when a particular license is under question.
;AGREED MOTION 2009-15: SL is and should be a GNU/Linux distributor.
;AGREED MOTION 2009-14: SL wishes to spread the use of Sugar and consequently works with GNU/Linux distros to produce and offer downloadable versions. This work can include helping to promote distros, and hosting them.
;AGREED MOTION 2009-13: SL should not be completely neutral about promoting distros, but it should only choose to more strongly promote a distro based on technical merit and maintainer activity, and should publish the criteria it uses for making that decision. Furthermore, SL should be neutral about providing infrastructure resources (hosting, etc) to distros."

== 2009-12-04 ==
;AGREED MOTION 2009-12: when a DP fails to meet a deadline, the decision passes to SLOBs.

== 2009-11-20 ==
;AGREED MOTION 2009-11: Close the slobs@ list to just SLOBs, move current slobs@ traffic to iaep@ with a [SLOBS] subject line tag where at all possible.
;AGREED MOTION 2009-10: Give a two-week deadline to the Soas DP

== 2009-09-25 ==
;AGREED MOTION 2009-09: We appointed a decision panel (by a vote of 3 for, 0 against, 1 abstain, 3 absent) with the following mandate:
:"Investigate the situation of how SoaS should be treated by Sugar Labs, and related questions, including answers to the following:
:"Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"
:"Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
:"Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"
:Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"

== 2008-09-05 ==
;AGREED MOTION 2009-08: The Oversight Board acknowledged and celebrated the great job Simon has been doing on managing the 0.82 release.

== 2009-07-18 ==
;AGREED MOTION 2009-07: There was consensus that we have made sufficient outreach to the community that the initial list is a fair representation of Sugar Labs; we look forward to having the Membership Committee take it from http://selectricity.org/
;AGREED MOTION 2009-06: There was consensus that Walter would put together a strawman election process based upon the Selectricity tool. We are targeting an August election.
;AGREED MOTION 2009-05: There was consensus that we begin with just Oversight and Members committees.
;AGREED MOTION 2009-04: We agreed for the need to solicit more feedback in the wiki for the design direction being proposed by Luca.
;AGREED MOTION 2009-03: We agreed that further discussions with the SFLA about the merits of trademark protection is needed.
;AGREED MOTION 2009-02: We agreed on the desirability of Sugar Labs participation at conferences around the world, but hope to meet the need by utilizing locals to whatever extent possible. We also discussed the desirability to have a meeting of Sugar Labs developers a couple of times per year. We discussed the possibility of an on-line meeting that leverages resources above and beyond IRC.
;AGREED MOTION 2009-01: on the necessity of Sugar Labs participation in the learning community, but don't yet have a good handle on the best and most efficient means of accomplishing this.