Development Team

From Sugar Labs

Jump to: navigation, search

Contents

Mission

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.


Meetings

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

Mini tutorials

The development team hosts mini tutorials covering short (five-minute) topics relevant to writing Sugar activities. Please refer to the Mini tutorials page to sign up for teaching a topic.

Development systems

All of core Sugar development except system-dependent modifications can be done on a standard computer by compiling jhbuild 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").

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. Start a Packaging 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 |

Template:Current Stable Release holds the release number.

See 0.86/Notes for the release notes.

Subpages

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/sugar.graphics.alertDevelopment Team/Almanac/sugar.graphics.iconDevelopment Team/Almanac/sugar.graphics.notebook
Development Team/Almanac/sugar.graphics.styleDevelopment Team/Almanac/sugar.graphics.toolboxDevelopment Team/Almanac/sugar.graphics.toolbutton
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/BuildbotDevelopment Team/Chroot
Development Team/Code ReviewDevelopment Team/Code guidelines
Development Team/Collaboration RefactoringDevelopment Team/CommunityDevelopment Team/Contacts
Development Team/CoordinatorDevelopment Team/Datastore RewriteDevelopment Team/Embedded
Development Team/EnvironmentDevelopment Team/FAQDevelopment Team/Getting Involved
Development Team/IssuesDevelopment Team/JhbuildDevelopment Team/Jhbuild/Debian
Development Team/Jhbuild/FedoraDevelopment Team/Jhbuild/MandrivaDevelopment 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/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/CurrentRelease/Sucrose
Development Team/Release/Modules
Development Team/ResourcesDevelopment Team/SoundDevelopment Team/Source Code
Development Team/Sugar Architectural DiagramDevelopment Team/Sugargame
Development Team/Sugargame/ExamplesDevelopment Team/TODODevelopment Team/Tutorials
Development Team/Understanding the CodeDevelopment Team/Upstream Downstream
Development Team/lang-esDevelopment Team/sugar-port
Personal tools
Sugar
Teams
Projects
Local Labs
Google Translations
Using the Wiki