Community/GettingInvolved
From SugarLabs
| Google Translations-Español-Български-中文(中国大陆)-中文(台灣)-Hrvatski-Česky-Dansk-Nederlands-Suomi-Français-Deutsch-Ελληνικά-हिन्दी-Italiano-日本語-한국어-Norsk (bokmål)-Polski-Português-Română-Русский-Svenska |
Home · Getting Involved · Contacts · Knowledge Base · FAQ · To Do List
The Sugar community is individuals, teams, and relationships. We all share one thing in common. We want to improve how computers are used in education.
Getting involved in the community is easy. Find an interesting team, start learning, and start contributing.
- AccessibiltyTeam - Responsible for accessibility issues within Sugar.
- BugSquad - Responsible for locating and fixing bugs.
- BuildTeam - Responsible for creating daily and release builds.
- DevelopmentTeam - Responsible for Developing the software modules within Sugar.
- DocumentationTeam - Responsible for writing both user and technical documentation.
- EducationTeam - Responsible for setting the Educational goals for the sugar Community.
- InfrastructureTeam - Responible for keep the Sugar Labs machines humming.
- LocalizationTeam - Responsible for localizing the sugar software.
- MarketingTeam - Responsible for marketing the Sugar brand and product.
- ReleaseTeam - Responsible for shipping the current release and planning for up coming releases.
- Sugar Labs - Responsible for governance and fund raising.
- TranslationTeam - Responsible for the translation needs of the community.
- UITeam - Responsible for the User interface.
- WikiTeam - Responsible for the Sugar Labs wiki.
Try joining a mailing list and get involved in the discussion.
- Its An Education Project - A discussion list for Sugar and the learning theories that it espouses.
- Sugar - Discussion of design, desktop platform and user experience.
