Difference between revisions of "Development Team"

From Sugar Labs
Jump to navigation Jump to search
m (update link)
Line 21: Line 21:
 
== Package Sucrose for your distribution ==
 
== Package Sucrose for your distribution ==
 
* Currently there are efforts to maintain Sugar as part of [[Community/Distributions/Debian|Debian]], [[Community/Distributions/Ubuntu|Ubuntu]], and [[Community/Distributions/Fedora|Fedora]].
 
* Currently there are efforts to maintain Sugar as part of [[Community/Distributions/Debian|Debian]], [[Community/Distributions/Ubuntu|Ubuntu]], and [[Community/Distributions/Fedora|Fedora]].
* Help us maintain good communication with distribution packagers to assist in this.
+
* Help us maintain good communication with distribution packagers to assist in this. Start a [[Packaging Team]].
  
 
== Kill Bugs! ==
 
== Kill Bugs! ==
* See our bug tracking system http://dev.sugarlabs.org/
+
* Help test. See [[{{Upcoming Stable Release}}/Testing]].
 +
* See our bug tracking system http://trac.sugarlabs.org/.
 +
* Join the [[BugSquad]].
  
 
== Project Ideas ==
 
== Project Ideas ==

Revision as of 11:50, 12 September 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 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

Platform Release Cycles

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

/Release/CurrentRelease/Sucrose

Subpages