Development Team

From Sugar Labs
Jump to: navigation, search
This page is marked for graduation to the main website.
There may be relevant discussion on the talk page.

Move to


The mission of the Development Team is to build and maintain the core Sugar environment. This includes specifying and implementing new features in conjunction with the Design Team, fixing bugs as they are found by the Testing team and the Sugar community, and generally making Sugar awesome in all ways.


The development team has a regular IRC meeting (See the Sugar Labs calendar). Find out more about the meeting time and upcoming and earlier meetings here. Help: Using IRC

Team lead

The Development Team coordinator position carries administrative tasks such as organizing regular meetings, keeping the TODO list updated, keeping the membership list updated, and making sure that the team has clear goals and is kept focused. We are currently accepting nominations for an election for this position, see Development_Team/Team_Lead_Candidates_2010_05.


See the Development Team/Release page.

Release manager

We have defined the role of the release manager for the past 3 releases as the following:

  • Setting the schedule.
  • Making sure that the Features/Policy is followed by submitters.
  • Keeping this wiki updated with the released modules and making sure to have final release notes available.
  • Sending email reminders about approaching Freezes, tarball due dates, etc.


The schedule is based on GNOME releases, a 6-month release cycle.

Development systems

All of core Sugar development except system-dependent modifications can be done on a standard computer by installing sugar-build and editing with your favorite editor (eclipse/pydev, emacs, vim, etc.). Activity (aka application) development can be done in many environments using pre-compiled packages ("sucrose") or images ("starch").

See also the Platform Team/Sweets technology.

Document your work

See Features/Feature Template for an example.

Code review

Patches to Sugar are more than welcome. There are guidelines for code review to get them accepted.

Package Sucrose for your distribution

  • Currently there are efforts to maintain Sugar as part of Debian, Ubuntu, and Fedora.
  • Help us maintain good communication with distribution packagers to assist in this. Join the Platform Team.

Kill Bugs!

Project Ideas

  • Want to work on an interesting Sugar project, or have an idea of your own? Check the project ideas page.
  • Prepare a new Sugar Feature.
  • See the Summer of Code project; ideas, students, mentors, and organization help are welcomed.

Platform Release Cycles

Sugar platform release version cycle: | 0.82 | 0.84 | 0.86 | 0.88 | 0.90 | 0.92 | 0.94 | 0.96 | 0.98 | 0.100 | 0.102 | 0.104 | 0.106 | 0.108 | 0.110 |

Template:Current Stable Release holds the release number.

See 0.108/Notes for the release notes.

Development Team/Release


Development Team/API policyDevelopment Team/Activities/CompatibilityDevelopment Team/Almanac
Development Team/Almanac/API ChangesDevelopment Team/Almanac/Activity BundlesDevelopment Team/Almanac/Code Snippets
Development Team/Almanac/Code Snippets/translationsDevelopment Team/Almanac/GStreamerDevelopment Team/Almanac/GTK's Clipboard Module
Development Team/Almanac/InternationalizationDevelopment Team/Almanac/Making IconsDevelopment Team/Almanac/Pango
Development Team/Almanac/Python Standard LoggingDevelopment Team/Almanac/Shared Sugar ActivitiesDevelopment Team/Almanac/Sugar.presence
Development Team/Almanac/Sugar.presence.activityDevelopment Team/Almanac/Sugar.presence.buddyDevelopment Team/Almanac/Sugar.presence.presenceservice
Development Team/Almanac/lang-esDevelopment Team/Almanac/sugar.activity.activityDevelopment Team/Almanac/sugar.activity.activityfactory
Development Team/Almanac/sugar.activity.registryDevelopment Team/Almanac/sugar.datastore.datastoreDevelopment Team/Almanac/sugar.env
Development Team/Almanac/ Team/Almanac/ Team/Almanac/
Development Team/Almanac/ Team/Almanac/ Team/Almanac/
Development Team/Almanac/sugar.loggerDevelopment Team/Almanac/sugar.mimeDevelopment Team/Almanac/sugar.profile
Development Team/Almanac/translationsDevelopment Team/ArchitectureDevelopment Team/Arduino
Development Team/BugShuffleDevelopment Team/Buildbot
Development Team/ChrootDevelopment Team/Code Review
Development Team/Code guidelinesDevelopment Team/Collaboration RefactoringDevelopment Team/Community
Development Team/ContactsDevelopment Team/CoordinatorDevelopment Team/Datastore Rewrite
Development Team/EmbeddedDevelopment Team/EnvironmentDevelopment Team/FAQ
Development Team/Getting InvolvedDevelopment Team/IssuesDevelopment Team/Jhbuild
Development Team/Jhbuild/DebianDevelopment Team/Jhbuild/FedoraDevelopment Team/Jhbuild/OS X/translations
Development Team/Jhbuild/UbuntuDevelopment Team/Jhbuild/lang-esDevelopment Team/Jhbuild/lang-ja
Development Team/Jhbuild/translationsDevelopment Team/Low-level Activity APIDevelopment Team/Manual
Development Team/Manual/SetupDevelopment Team/Manual/lang-jaDevelopment Team/Manual/lang-ko
Development Team/Manual/translationsDevelopment Team/MeetingsDevelopment Team/Meetings/Logs/August 28 2009
Development Team/Meetings/Logs/May 21 2009Development Team/Meetings/Logs/September 01 2009Development Team/Meetings/Logs/September 10 2009
Development Team/MemoryDevelopment Team/Memory/Leak testingDevelopment Team/Memory/Usage Analysis
Development Team/Mini tutorialsDevelopment Team/MissionDevelopment Team/Obsolete
Development Team/Obsolete/Sugar is not Product but EcosystemDevelopment Team/Obsolete/sugar-portDevelopment Team/Packaging
Development Team/PerformanceDevelopment Team/PrerequisitesDevelopment Team/Presence Service Removal
Development Team/ProfilingDevelopment Team/Project IdeasDevelopment Team/Python Packages
Development Team/QuickstartDevelopment Team/ReleaseDevelopment Team/Release/Modules
Development Team/Resources
Development Team/Sound
Development Team/Source CodeDevelopment Team/Sugar-Build
Development Team/Sugar Architectural DiagramDevelopment Team/Sugargame
Development Team/Sugargame/ExamplesDevelopment Team/TODODevelopment Team/Team Lead Candidates 2010 05
Development Team/TutorialsDevelopment Team/Understanding the Code
Development Team/Upstream DownstreamDevelopment Team/lang-es