Sugar Labs/Teams: Difference between revisions
m add development team |
m add education team, oversight board |
||
| Line 33: | Line 33: | ||
---- | ---- | ||
</div> | </div> | ||
=== Education Team === | |||
=== Deployment Team === | === Deployment Team === | ||
{{:DeploymentTeam/Mission}} | {{:DeploymentTeam/Mission}} | ||
| Line 43: | Line 43: | ||
== 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. | ||
===Community === | |||
=== Marketing Team === | === Marketing Team === | ||
{{:MarketingTeam/Mission}} | {{:MarketingTeam/Mission}} | ||
=== Oversight Board === | |||
=== Wiki Team === | === Wiki Team === | ||
Revision as of 11:46, 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.
Education Team
Deployment Team
Community Mission
Sugar Labs is here to support community innovation, entrepreneurship, and enterprise.