Line 35: |
Line 35: |
| | | |
| == Sugar Labs: a learning and software-development community == | | == 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. | + | 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 === | | === 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: |
| | | |
− | * To make Sugar and Sugar activities freely and readily available to learners everywhere; | + | * To make Sugar and Sugar activities freely and readily available to learners everywhere |
| * To explore and share best practices | | * To explore and share best practices |
| * To provide a forum for discussion and support for technology for learning | | * To provide a forum for discussion and support for technology for learning |
Line 50: |
Line 50: |
| * 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. |
| * 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. |
− | * 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. |
| * 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. |
| | | |