Difference between revisions of "Development Team"

From Sugar Labs
Jump to: navigation, search
Line 1: Line 1:
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}
+
<noinclude>{{GoogleTrans-en}}{{TeamHeader|Development Team|roadmap_link=Release/Roadmap/{{Upcoming Stable Release}}}}</noinclude>{{TOCright}}
{{TeamHeader|Development Team|roadmap_link=Release/Roadmap/{{Upcoming Stable Release}}}}</noinclude>{{TOCright}}
 
  
 
==Mission==
 
==Mission==
Line 32: Line 31:
 
==Release Notes==
 
==Release Notes==
 
'''[[/Release/CurrentRelease/Sucrose]]'''
 
'''[[/Release/CurrentRelease/Sucrose]]'''
{{Special:PrefixIndex/Development Team/Release}}
 
  
 
== Subpages ==
 
== Subpages ==

Revision as of 02:09, 3 July 2009

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

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

Kill Bugs!

Project Ideas

Release Notes

/Release/CurrentRelease/Sucrose

Subpages