|Deletions are marked like this.||Additions are marked like this.|
|Line 16:||Line 16:|
=== Packaging ===
See our [[SugarTeam/Develop|development]] page regarding packaging processes. Our [[SugarTeam/Packages|Packages]] page has a TODO list.
|Line 32:||Line 37:|
|==== Preview Testing ====||==== PPA Preview Testing ====|
|Line 36:||Line 41:|
|=== Wiki Maintenance ===|
|Line 38:||Line 42:|
|At the present moment the wiki is growing quickly, we need a few more people to help get it into shape, please see our [[SugarTeam/Wiki|wiki standards]] page for more information.|
Welcome the Ubuntu Sugar Team, we are the folk that are maintaining the Sugar Learning Environment on Ubuntu. Sugar, originally designed for the One Laptop Per Child projects, promotes sharing, collaborative learning, and reflection. Through Sugar's clarity of design, children and their teachers have the opportunity to use computation on their own terms; they are free to reshape, reinvent, and reapply both software and content into powerful learning activities.
If you wish to contact the team, you can do so in several ways: the best way would be through the mailing list, the address is ubuntu-sugarteam AT lists DOT ubuntu DOT com. You an join the mailing list at http://lists.ubuntu.com/mailman/listinfo/Ubuntu-sugarteam. We can also be found on IRC, on the Freenode server irc.freenode.net at #ubuntu-sugarteam.
How to Contribute
The bug reporting page contains useful information on how you can report bugs in a way that will helps the team to process them more efficiently.
If you want to join the Sugar Team or just want to help out, triaging bugs is a fairly easy task that always needs to be done. Information on bug triaging can be found on triage procedures.
The next step is fixing the properly triaged issue reports, more information can be found on our development page.
We document our QA procedures in SugarTeam/QA
PPA Preview Testing
The last step is testing our new build before pushing them in the Ubuntu repositories. We have a set of preview archives for testing recent fixes.
|/Activities /Contacts /Develop /FAQ /GettingInvolved /Header /KnowledgeBase /Meeting /Package /Report /Roadmap /Tasks /Test|