10,579
edits
Changes
Jump to navigation
Jump to search
Line 6:
Line 6: − + − # A goal is 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.+ − # A third goal is 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.+ + + + + + + + + + + + + + + + + + +
→Goals
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.
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.
===Goals===
=== 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:
* 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===
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.
=== 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===
===Principles===