Difference between revisions of "Sugar Labs/Teams"
Jump to navigation
Jump to search
m (add development team) |
|||
| Line 11: | Line 11: | ||
Sugar supports the notions that learners should “share by default” and be able to “explore, express, debug, and critique.” | Sugar supports the notions that learners should “share by default” and be able to “explore, express, debug, and critique.” | ||
| + | === Development Team === | ||
=== Design Team === | === Design Team === | ||
| − | |||
| − | |||
<div style="background: #ffdfbf; padding: 10px; border: 1px solid #fdb873"> | <div style="background: #ffdfbf; padding: 10px; border: 1px solid #fdb873"> | ||
Revision as of 11:38, 15 November 2008
This article is a stub. You can help Sugar Labs by expanding it.
Technical Mission
Sugar supports the notions that learners should “share by default” and be able to “explore, express, debug, and critique.”
Development Team
Design Team
Testing Team
Documentation Team
Mission - Provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.
Coordinator - David Farning
Educational Mission
Sugar is useful only to the extent it is used by the learning community.
Deployment Team
Community Mission
Sugar Labs is here to support community innovation, entrepreneurship, and enterprise.