Difference between revisions of "Development Team"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
== Development systems == | == Development systems == | ||
| − | All of Sugar development except system-dependent modifications can be done on a standard computer by compiling [[DevelopmentTeam/Jhbuild|jhbuild]]. Activity (aka application) development can be done in many environments using pre-compiled [[Supported_systems#Sucrose|packages]] ("sucrose") or [[Supported_systems#Starch|images]] ("starch"). | + | All of core Sugar development except system-dependent modifications can be done on a standard computer by compiling [[DevelopmentTeam/Jhbuild|jhbuild]]. Activity (aka application) development can be done in many environments using pre-compiled [[Supported_systems#Sucrose|packages]] ("sucrose") or [[Supported_systems#Starch|images]] ("starch"). |
== Code review == | == Code review == | ||
Revision as of 11:18, 17 March 2009
Mission
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. 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.