Difference between revisions of "Development Team"

Revision as of 13:47, 8 April 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.

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").

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!

See our bug tracking system http://dev.sugarlabs.org/

Project Ideas

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

Release Notes

/Release/CurrentRelease/Sucrose

Subpages

@@ Line 22: / Line 22: @@
 == Project Ideas ==
-* Want to work on an interesting Sugar project, or have an idea of your own?  Check the [[Development Team/ProjectIdeas|project ideas]] page.
+* Want to work on an interesting Sugar project, or have an idea of your own?  Check the [[Development Team/Project Ideas|project ideas]] page.
 * See the [[Summer of Code]] effort; ideas, students, mentors, and organization help are welcomed.
 ==Release Notes==