|
|
(24 intermediate revisions by one other user not shown) |
Line 1: |
Line 1: |
| ''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!''
| | |
| | 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! |
| | |
| | Proposal 1: |
| | |
| | “In 10 years or less, Sugar Labs is a solid global friendly libre software community where you can learn to design, develop, deploy and support high-quality self-discovery learning experiences and friendly collaboration environments among learners and makers of all continents, in all possible languages and all possible media of distribution." |
| | |
| | Proposal 2: |
| | |
| | [your proposal here...] |
| | |
| | You may also enjoy related pages: |
| | |
| | * [[2016 Goals]] |
| | * [[Mission proposal 2016]] |
| | * [[Vision_proposal_2016/Call_1]] |
| | * [[Vision_proposal_2016/Call_2]] |
|
| |
|
| <hr> | | <hr> |
Line 7: |
Line 23: |
| Sugar is designed for use by people who do not yet have regular or reliable internet access. | | 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; a web-based version is under development for tablets and phones called Sugarizer. | | 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). |
| | |
| Sugar Activities are applications that run in the Sugar Desktop or Sugarizer. Sugar Activities encourage learning through self-discovery and encourage collaboration, expression, and reflection.
| |
|
| |
|
| 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.
| | A web-based version is under development for tablets and phones, called Sugarizer. |
|
| |
|
| Sugar development began in 2006 as part of the One Laptop per Child (OLPC) project. | | Sugar Activities are applications that run in Sugarizer or the Sugar Desktop. |
|
| |
|
| In 2016, the Sugar community is global; we aspire to include users and contributors in all countries, all languages, and all cultures.
| | Sugar Activities encourage learning through self-discovery and encourage collaboration, expression, and reflection. |
|
| |
|
| We are Sugar Labs, a volunteer-led and non-profit organization in service to the Sugar community.
| | Sugar realises the educational vision of Seymour Papert and Alan Kay by providing a low floor and no ceiling. |
|
| |
|
| We facilitate knowledge and software sharing among all people; we relate the software freedom movement to education.
| | 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. |
| | |
| 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.
| | 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. |
|
| |
|
| <hr>
| | 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. |
|
| |
|
| Our 2016 goals include:
| | We facilitate knowledge and software sharing among all people; we relate the software freedom movement to education. |
|
| |
|
| Software:
| | We provide plans for how to best use Sugar to improve learning, intended for individual parents and teachers all the way to national policy. |
|
| |
|
| * to successfully complete our six GSoC projects;
| | We raise funds and use them to accelerate the progress of our Members, enabling them to access laptops, travel, and more. |
| * to make two releases of Sugar, one in February (0.108) and one in October (0.110);
| |
| ** to check all activities on github work with the 0.110 release, and ensure their <code>activity.info</code> file is current;
| |
| ** 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;
| |
| * to port more Activities to Sugarizer, the web-based version of Sugar;
| |
| * 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;
| |
| ** 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://github.com/sugarlabs/www-sugarlabs/issues/47 www-sugarlabs#47]);
| |
|
| |
|
| Organization:
| | We make things to think with. |
|
| |
|
| * to fully staff all boards, offices, and committees;
| | Join us. |
| * 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 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 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]], and then making persistent attempts to contact them until they pay a membership donation, ask for a membership bursary so they don't have to pay the fee personally, or tell us to go away;
| |
| ** to develop an affiliate members list, and a sponsors list (similar to https://opensource.org/node/816)
| |
| * 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 run a local labs 2016 survey (see [[Marketing_Team/Local_Labs_Survey_2016]])
| |
| * [your goal here]
| |