Sugar Labs® is a volunteer-driven 501(c)3 nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.
Sugar Labs is organized around overlapping Teams. Please use the Community panel in the wiki sidebar to visit and explore the work and events for each team. This Team category page collects all Sugar Labs wiki pages with a Team tag.
Sugar Labs is working on a few projects focused on delivering specific goals in a defined time period. The Projects panel in the wiki sidebar holds our premier projects. Please also see these project home pages:
| Summer of Code |
Sugar Labs: a community
- for learning and software-development
The Sugar development platform is available under the open-source GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs, Inc. and serves as a support base and gathering place for the community of educators and software developers who want to extend the platform and who have been creating Sugar-compatible applications.
Sugar is useful only to the extent it is used by the learning community. Thus, Sugar Labs is working with educators around the world to focus on these learning challenges:
- To make Sugar and Sugar activities freely and readily available to learners everywhere
- To explore and share best practices
- To provide a forum for discussion and support for technology for learning
- To provide mechanism for evaluation and dissemination of results.
Sugar supports the notions that learners should “share by default” and be able to “explore, express, debug, and critique.” Thus Sugar puts an emphasis on “activities” rather than “applications.” The foundation will focus on solving the challenges that are relevant to these aspects of the interface, namely:
- To make it “simple” to share Sugar activities. This will require an architecture that allows discovery of activities.
- To create versions of Sugar that run on multiple operating systems and on multiple hardware platforms. It should be “simple” to install Sugar everywhere. Specifically, it means packaging for every distribution and every virtual machine—removing hardware-related dependencies wherever possible.
- To make it “simple” to write Sugar activities. This necessitates stable APIs and example code that uses these APIs.
- To make Sugar activities even more secure. Our principal user community is comprised of children; they must be protected from malware, phishing, botnets, etc.
Sugar Labs is here to support community innovation, entrepreneurship, and enterprise. Sugar Labs would like to help community members start projects that help sustain and grow the Sugar technology and learning communities:
- To provide local and regional technical and pedagogical support.
- To create new learning activities and pedagogical practice.
- To provide localization and internationalization of software, content, and documentation.
- To provide integration and customization services.
In order for Sugar to be successful, it needs the participation of a large number of people who share common goals while maintaining independence, so that each participant has the ability to act independently. For these reasons, Sugar Labs subscribes to the principles described here, which are the author's own translation of an original text in Spanish.
- Clear mission – Fully disclosed objectives.
- Declared commitments – Affinities and aversions explained.
- Declared outside connections – Relationships with other organizations explicitly listed.
- Horizontal organization – Teams and facilitators work on responsibilities and agreements.
- Identified contributors – Who is who, people are reachable.
- Clear responsibilities – Who is in charge of what.
- Activities described – All of the ongoing work is acknowledged.
See Wiki Structure for a guide to how the wiki models Sugar Labs' structure.
- Open participation – Anybody can access the information and get a first responsibility.
- Meritocracy – Responsibilities are acquired (or lost) based on one's skills, results, and contributors’ support.
- Voluntary (non-)engagement – Nobody is forced to be involved or to keep responsibilities.
- Regular reports – Reported activities and future plans allow monitoring and participation.
- Information accessible – Even internal operational information is available by default.
- We try to operate en plein air.
- Explicit confidentiality – It is explained what matters are confidential, why, and who can access them.
- Economic model – Feasibility and sustainability plans are exposed. (Please see/contribute to the discussion here.)
- Resources – Inventory of items detailing who contributed what and why.
- Public accounts – It’s clear where the money comes from and where it goes.
- A special thanks to our contributors.
Informed by the above principles, Sugar Labs has a governance model.
The Sugar Community roadmap is used to guide our community efforts:
- Mission, Vision, Values
- Quality Assurance
A current events page is updated weekly (usually on Monday morning) with notes from the Sugar Labs community. (The Sugar Digest is also sent to the community-news at lists.sugarlabs.org list and blogged at walterbender.org.) If you would like to contribute, please send email to walter at sugarlabs.org by the weekend. (Also visit planet.sugarlabs.org.)
An archive of Sugar Digests is available.
Sugar community events are posted in a public calendar within the Google Calendar system. The calendar is available in a variety of formats:
Please contact User:Walter if you'd like to post an event to the calendar. Or simply post it below and it will be included.
A local Sugar Lab adapts the technology and pedagogy to an area's culture and resources (e.g., developing activities and content specific to a region); helps translate Sugar to the local language(s); supports Sugar deployments in area schools; creates a local community devoted to the Sugar Labs principles, making Sugar more open and sustainable; provides for communication, between the local communities and the global Sugar Labs community; develops Local content and software that can be used not only for local purposes but also for the overall community; hosts, co-hosts or partners in the organization of conferences, workshops, talks and meetings related to the use or development of Sugar.
Please visit these Local Labs:
- Sugar Labs/About
- Sugar Labs/Announcing Sugar Labs
- Sugar Labs/Background
- Sugar Labs/Business cards
- Sugar Labs/Communication channels
- Sugar Labs/Community Catalyst
- Sugar Labs/Conduct
- Sugar Labs/Contacts
- Sugar Labs/Contacts/Mail
- Sugar Labs/Current Events
- Sugar Labs/Current Events/lang-es
- Sugar Labs/Donate
- Sugar Labs/Events/Instructions
- Sugar Labs/Executive Director
- Sugar Labs/FAQ
- Sugar Labs/Funding
- Sugar Labs/Getting Involved
- Sugar Labs/Getting Involved/lang-es
- Sugar Labs/Governance
- Sugar Labs/Governance/Advisory Board
- Sugar Labs/Governance/Committees
- Sugar Labs/Governance/Membership
- Sugar Labs/Governance/Transactions
- Sugar Labs/Governance/lang-es
- Sugar Labs/Legal/Code of Conduct
- Sugar Labs/Legal/Logo and trademark policy
- Sugar Labs/Members
- Sugar Labs/Members/List
- Sugar Labs/Members/Survey2015
- Sugar Labs/Ombudsman
- Sugar Labs/Profiles
- Sugar Labs/Project Guidelines
- Sugar Labs/Resources/How to Attend a Meeting
- Sugar Labs/Resources/How to join a mailing list
- Sugar Labs/Resources/How to run a team
- Sugar Labs/Resources/Professional services
- Sugar Labs/Roadmap
- Sugar Labs/Running good meetings
- Sugar Labs/SFC Fiscal Agreement
- Sugar Labs/SOM
- Sugar Labs/SOM/IAEP
- Sugar Labs/SOM/Sugar
- Sugar Labs/Site support
- Sugar Labs/Sugar Labs joins the SFC
- Sugar Labs/Sugar contributors
- Sugar Labs/TODO
- Sugar Labs/Teams
- Sugar Labs/Thank You
- Sugar Labs/Treasurer
- Sugar Labs/Volunteer Funnel
- Sugar Labs/index.php