Difference between revisions of "Sugar Labs"

From Sugar Labs
Jump to: navigation, search
m (Made the text a little bit mor scannable; added wiki tags for headers and numbered lists. Feel free to change back.)
m (Community News)
 
(100 intermediate revisions by 19 users not shown)
Line 1: Line 1:
==Sugar Labs: a software-development association==
+
<noinclude>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}
 +
[[Category:General public]]
 +
[[Category:Team]]</noinclude>__TOC__
  
The Sugar development platform is available under the open-source GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs”, a (soon to be established) non-profit foundation will serve 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.
+
===Mission===
  
===Goals===
+
[[Trademark|Sugar Labs<sup>®</sup>]] is a volunteer-driven member project of [http://www.sfconservancy.org/ Software Freedom Conservancy], a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates [[Sugar Labs/Getting Involved|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 [[Donate|funding]] to accelerate development.
  
 +
== [[:Category:Team|Teams]] ==
 +
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 [[:Category:Team | ''Team'' category page]] collects all Sugar Labs wiki pages with a ''Team'' tag.
 +
== [[:Category:Project|Projects]] ==
 +
Sugar Labs is working on a few [[:Category:Project|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:
 +
 +
| [[Harmonic Distribution]] | [https://sugardextrose.org/ Dextrose] | [[Sugar Creation Kit]] | [[Sugar on a Stick]] |
 +
 +
| [[Replacing Textbooks]] | [[Math4Team |Math4 Project]] |
 +
 +
| [[Summer of Code]] |
 +
 +
== Sugar Labs: a community ==
 +
:::::::<span style="font-size: 150%">for learning and software-development</span>
 +
The Sugar development platform is available under the open-source GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs” is a member project of the [http://sfconservancy.org/ Software Freedom Conservancy] (a non-profit foundation to produce and distribute and support the use of free software) 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.
 +
 +
=== Education Goals ===
 +
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.
 +
 +
=== Technical Goals ===
 
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:
 
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:
  
# A goal is to make it “simple” to share Sugar activities. This will require an architecture that allows discovery of activities.
+
* To make it “simple” to share Sugar activities. This will require an architecture that allows discovery of activities.
# A second goal is 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 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.
# A third goal is to make it  “simple” to write Sugar activities. This necessitates stable APIs and   example code that uses these APIs.
+
* To make it  “simple” to write Sugar activities. This necessitates stable APIs and example code that uses these APIs.
# A fourth goal is to make Sugar activities even more secure. Our principal user community is comprised of children; they must be protected from malware, phishing, botnets, etc.
+
* To make Sugar activities even more secure. Our principal user community is comprised of children; they must be protected from malware, phishing, botnets, etc.
 +
 
 +
=== Community Goals ===
 +
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 a common goal while maintaining independence, so that each participant has the ability to act independently. For these reasons, Sugar Labs subscribes to these principles (from [http://flors.wordpress.com/2008/05/04/the-paradigm-of-the-open-organization/]):
+
=== Principles ===
 +
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 [http://flors.wordpress.com/2008/05/04/the-paradigm-of-the-open-organization/ here], which are the author's own translation of an [http://web.archive.org/web/20050317231119/http://interactors.coop/organizacionabierta original text in Spanish.]
  
 
====Identity====
 
====Identity====
 
+
* Clear mission – Fully disclosed objectives.
* Clear mission – Full disclosed objectives.
 
 
* Declared commitments – Affinities and aversions explained.
 
* Declared commitments – Affinities and aversions explained.
* Explicit connections outside – Relationships with other organizations listed.
+
* Declared outside connections – Relationships with other organizations explicitly listed.
  
 
====Structure====
 
====Structure====
 
 
* Horizontal organization – Teams and facilitators work on responsibilities and agreements.
 
* Horizontal organization – Teams and facilitators work on responsibilities and agreements.
 
* Identified contributors – Who is who, people are reachable.
 
* Identified contributors – Who is who, people are reachable.
 
* Clear responsibilities – Who is in charge of what.
 
* Clear responsibilities – Who is in charge of what.
* Activities described – All the ongoing work is acknowledged.
+
* Activities described – All of the ongoing work is acknowledged.
 +
See [[Wiki_Team/Guide/Wiki_Structure | Wiki Structure]] for a guide to how the wiki models Sugar Labs' structure.
  
 
====Operation====
 
====Operation====
 
 
* Open participation – Anybody can access the information and get a first responsibility.
 
* Open participation – Anybody can access the information and get a first responsibility.
* Meritocracy – Responsibilities are acquired (or lost) based on own skills and contributors’ support.
+
* 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.
 
* Voluntary (non-)engagement – Nobody is forced to be involved or to keep responsibilities.
  
 
====Information====
 
====Information====
 
 
* Regular reports – Reported activities and future plans allow monitoring and participation.
 
* Regular reports – Reported activities and future plans allow monitoring and participation.
 
* Information accessible – Even internal operational information is available by default.
 
* Information accessible – Even internal operational information is available by default.
* Explicit confidentiality – It is explained what areas are confidential, why and who can access them.
+
*: We try to operate '''''[[Archive/Current_Events/2009-06-10#En_plein_air|en plein air]]'''''.
 +
* Explicit confidentiality – It is explained what matters are confidential, why, and who can access them.
  
 
====Goods====
 
====Goods====
 
+
* Economic model – Feasibility and sustainability plans are exposed. (Please see/contribute to the discussion [[Sugar Labs/Funding|here]].)
* Economic model – Feasibility and sustainability plans are exposed.
 
 
* Resources – Inventory of items detailing who contributed what and why.
 
* Resources – Inventory of items detailing who contributed what and why.
 
* Public accounts – It’s clear where the money comes from and where it goes.
 
* Public accounts – It’s clear where the money comes from and where it goes.
 +
* A special [[Sugar Labs/Thank You|thanks]] to our contributors.
 +
 +
=== [[Sugar Labs/Governance|Governance]] ===
 +
Informed by the above principles, Sugar Labs has a [[Sugar Labs/Governance|governance model]].
 +
 +
==[[Sugar Labs/Roadmap|Roadmap]]==
 +
The [[Sugar Labs/Roadmap|Sugar Community roadmap]] is used to guide our community efforts:
 +
* Mission, Vision, Values
 +
* Distribution
 +
* Deployments
 +
* Quality Assurance
 +
* Infrastructure
 +
 +
==[[Sugar Labs/Current Events|Community News]]==
 +
A [[Sugar Labs/Current Events|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 [http://lists.sugarlabs.org/listinfo/community-news community-news at lists.sugarlabs.org] list and blogged at [http://walterbender.org/ walterbender.org].) If you would like to contribute, please send email to [[User:walter|walter]] at sugarlabs.org by the weekend. (Also visit [http://planet.sugarlabs.org planet.sugarlabs.org].)
 +
 +
An '''[[Archive/Current Events|archive]]''' of Sugar Digests is available.
 +
 +
==[[Sugar Labs/Events | Events Calendar]]==
 +
Sugar [[Sugar Labs/Events | community events]] are posted in a public calendar within the Google Calendar system. The calendar is available in a variety of formats: <span class="plainlinks"> [[Image:XML.gif|link=http://www.google.com/calendar/feeds/6n9a99dr5knag9tp0obc0rncug%40group.calendar.google.com/public/basic]] [[Image:ICal.gif|link=http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics]] [[Image:HTML.gif|link=http://www.google.com/calendar/embed?src=6n9a99dr5knag9tp0obc0rncug%40group.calendar.google.com&ctz=America/New_York]].
 +
 +
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.
 +
 +
== [[Local Labs]] ==
 +
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:
 +
 +
| [http://co.sugarlabs.org/go/Laboratorios_Azúcar_Colombia Sugar Labs Colombia] | [http://cl.sugarlabs.org/go/Página_Principal Sugar Labs Chile] | [[Sugar Labs DC]] | [http://pe.sugarlabs.org/ Sugar Labs Peru] | [http://ar.sugarlabs.org/ Sugar Labs Argentina] |
 +
<div class="NavFrame "><div class="NavHead">'''Local Lab wiki portal''' </div><div class="NavContent">
 +
{|
 +
|[http://co.sugarlabs.org/go/Laboratorios_Azúcar_Colombia Sugar Labs Colombia]
 +
{{#widget:Iframe
 +
|url=http://co.sugarlabs.org
 +
|width=410
 +
|height=342
 +
|border=1
 +
}}
 +
|[http://cl.sugarlabs.org/go/Página_Principal Chile Local Labs]
 +
{{#widget:Iframe
 +
|url=http://cl.sugarlabs.org
 +
|width=410
 +
|height=342
 +
|border=1
 +
}}
 +
|-
 +
|[[Sugar Labs DC]]
 +
{{#widget:Iframe
 +
|url=http://wiki.sugarlabs.org/go/Sugar_Labs_DC
 +
|width=410
 +
|height=342
 +
|border=1
 +
}}
 +
|[http://pe.sugarlabs.org/ Sugar Labs Peru]
 +
{{#widget:Iframe
 +
|url=http://pe.sugarlabs.org/
 +
|width=410
 +
|height=342
 +
|border=1
 +
}}
 +
|-
 +
|[http://ar.sugarlabs.org/ Sugar Labs Argentina]
 +
{{#widget:Iframe
 +
|url=http://ar.sugarlabs.org
 +
|width=410
 +
|height=342
 +
|border=1
 +
}}
 +
| Who's next?
 +
|}
 +
</div></div>
 +
 +
== Subpages index ==
 +
{{Special:PrefixIndex/Sugar_Labs/}}

Latest revision as of 08:08, 20 December 2016

Community Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Events Calendar

Mission

Sugar Labs® is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking funding to accelerate development.

Teams

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.

Projects

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:

| Harmonic Distribution | Dextrose | Sugar Creation Kit | Sugar on a Stick |

| Replacing Textbooks | Math4 Project |

| 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” is a member project of the Software Freedom Conservancy (a non-profit foundation to produce and distribute and support the use of free software) 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.

Education Goals

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.

Technical Goals

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.

Community Goals

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.

Principles

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.

Identity

  • Clear mission – Fully disclosed objectives.
  • Declared commitments – Affinities and aversions explained.
  • Declared outside connections – Relationships with other organizations explicitly listed.

Structure

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

Operation

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

Information

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

Goods

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

Governance

Informed by the above principles, Sugar Labs has a governance model.

Roadmap

The Sugar Community roadmap is used to guide our community efforts:

  • Mission, Vision, Values
  • Distribution
  • Deployments
  • Quality Assurance
  • Infrastructure

Community News

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.

Events Calendar

Sugar community events are posted in a public calendar within the Google Calendar system. The calendar is available in a variety of formats: XML.gif ICal.gif HTML.gif.

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.

Local Labs

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 Colombia | Sugar Labs Chile | Sugar Labs DC | Sugar Labs Peru | Sugar Labs Argentina |

Subpages index