Development Team

From Sugar Labs

(Redirected from DevelopmentTeam)
Jump to:navigation, search

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

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

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.

Release manager

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

Schedule

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 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

Kill Bugs!

Project Ideas

Platform Release Cycles

Sugar platform release version cycle: | 0.82 | 0.84 | 0.86 | 0.88 | 0.90

Template:Current Stable Release holds the release number.

See 0.88/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/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/Mandriva
Development Team/Jhbuild/OS X/translationsDevelopment Team/Jhbuild/UbuntuDevelopment Team/Jhbuild/lang-es
Development Team/Jhbuild/lang-jaDevelopment Team/Jhbuild/translationsDevelopment Team/Low-level Activity API
Development Team/ManualDevelopment Team/Manual/SetupDevelopment Team/Manual/lang-ja
Development Team/Manual/lang-koDevelopment Team/Manual/translationsDevelopment Team/Meetings
Development Team/Meetings/Logs/August 28 2009Development Team/Meetings/Logs/May 21 2009Development Team/Meetings/Logs/September 01 2009
Development Team/Meetings/Logs/September 10 2009Development Team/MemoryDevelopment Team/Memory/Leak testing
Development Team/Memory/Usage AnalysisDevelopment Team/Mini tutorialsDevelopment Team/Mission
Development Team/ObsoleteDevelopment Team/Obsolete/Sugar is not Product but EcosystemDevelopment Team/Obsolete/sugar-port
Development Team/PackagingDevelopment Team/PerformanceDevelopment Team/Prerequisites
Development Team/Presence Service RemovalDevelopment Team/ProfilingDevelopment Team/Project Ideas
Development Team/Python PackagesDevelopment Team/QuickstartDevelopment Team/Release
Development Team/Release/CurrentRelease/SucroseDevelopment Team/Release/Modules
Development Team/Resources
Development Team/SoundDevelopment Team/Source Code
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
Sugar
Teams
Projects
Local Labs
Using the Wiki
Google Translations