Difference between revisions of "Sugar Labs/Teams"
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
</div> | </div> | ||
| − | <div style="font-size: 1.3em; background: # | + | <div style="font-size: 1.3em; background: #bfffc9; padding: 10px; border: 1px solid #3db850"> |
== Educational Mission == | == Educational Mission == | ||
Sugar is useful only to the extent it is used by the learning community. | Sugar is useful only to the extent it is used by the learning community. | ||
| Line 27: | Line 27: | ||
</div> | </div> | ||
| − | <div style="font-size: 1.3em; background: # | + | <div style="font-size: 1.3em; background: #c2bfff; padding: 10px; border: 1px solid #817cfd"> |
== Community Mission == | == Community Mission == | ||
Sugar Labs is here to support community innovation, entrepreneurship, and enterprise. | Sugar Labs is here to support community innovation, entrepreneurship, and enterprise. | ||
Revision as of 13:07, 11 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.”
Design Team
Build Team
Release Team
Testing Team
Infrastructure Team
Educational Mission
Sugar is useful only to the extent it is used by the learning community.
Deployment Team
Documentation Team
Community Mission
Sugar Labs is here to support community innovation, entrepreneurship, and enterprise.