Changes

Jump to navigation Jump to search
117 bytes removed ,  23:10, 4 December 2008
m
rearange sections
Line 2: Line 2:  
{{TeamHeader|Sugar Labs}}</noinclude>
 
{{TeamHeader|Sugar Labs}}</noinclude>
 
__NOTOC__
 
__NOTOC__
== Sugar Labs: a software-development and learning community ==
  −
  −
The Sugar development platform is available under the open-source GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs”, which is in the process of joining the Software Freedom Conservancy (a non-profit foundation to produce and distribute and support the use of free software) 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.
  −
   
==Welcome to the Sugar Community==
 
==Welcome to the Sugar Community==
 
This is the place to find out what is happening at Sugar Labs. Learn what tasks need to be done, what teams there are to join, and share news about recent events or current activities taking place at Sugar Labs.
 
This is the place to find out what is happening at Sugar Labs. Learn what tasks need to be done, what teams there are to join, and share news about recent events or current activities taking place at Sugar Labs.
Line 34: Line 30:  
* [[WikiTeam]] - Browse the wiki.
 
* [[WikiTeam]] - Browse the wiki.
   −
=== Technical Goals ===
+
== Sugar Labs: a learning and software-development community ==
 
+
The Sugar development platform is available under the open-source GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs”, which is in the process of joining the Software Freedom Conservancy (a non-profit foundation to produce and distribute and support the use of free software) 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 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.
      
=== Education Goals ===
 
=== 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:
 
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:
   Line 51: Line 40:  
* To provide a forum for discussion and support for technology for learning
 
* To provide a forum for discussion and support for technology for learning
 
* To provide mechanism for evaluation and dissemination of results.
 
* 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 ===
 
=== 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:
 
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:
   Line 62: Line 58:     
=== Principles ===
 
=== 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.]
 
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 – Full disclosed objectives.
 
* Clear mission – Full disclosed objectives.
 
* Declared commitments – Affinities and aversions explained.
 
* Declared commitments – Affinities and aversions explained.
Line 72: Line 66:     
====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.
Line 79: Line 72:     
====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 own skills and contributors’ support.
Line 85: Line 77:     
====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.
Line 91: Line 82:     
====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. (Please see/contribute to the discussion [[Sugar Labs/Funding|here]].)
 
* 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/ThankYou|thanks]] to our contributors.
 
* A special [[Sugar Labs/ThankYou|thanks]] to our contributors.
    
=== Governance ===
 
=== Governance ===
 
Informed by the above principles, Sugar Labs has a [[Sugar Labs/Governance|governance model]].
 
Informed by the above principles, Sugar Labs has a [[Sugar Labs/Governance|governance model]].
  −
=== Teams ===
  −
Sugar Labs is organized into [[Sugar Labs/Teams|teams]] to help put our goals into action.
      
[[Category:General public]]
 
[[Category:General public]]
2,751

edits

Navigation menu