Summer of Code/Resources

Sugar Labs is a big project. Like all big projects, it has a big wiki. Here are some pointers:

Getting Orientated

 * 1) Learn about the  Sugar Learning Platform
 * 2) Sign up to our  mailing lists & connect via our  IRC channels
 * 3) Learn how the different Sugar Labs  project teams work together

Getting the Code

 * 1) Know git? Visit our resource page for developers to see the repositories of all of the Sugar modules & core Activities
 * 2) You may wish to  learn the terms we use to describe Sugar's components

Fixing Bugs
Getting to work on bugs is a great way to start your introduction to the Sugar code base. Hint: Search for sugar-love in the bug tracker.
 * 1) Visit https://dev.sugarlabs.org, also known as https://bugs.sugarlabs.org/
 * 2) Learn our  bug status codes

GSoC Project Ideas
Are you looking for things that could occupy your time over the summer break? There are several proposals that are looking for some enthusiastic support:


 * Development Team/Project Ideas
 * Activity Team/Project Ideas
 * Sugar Camp, Boston 2008
 * Summer_of_Code/Ideas
 * OLPC:Category:GSoC_proposals
 * OLPC:Projects and Proposals

We are also very keen to have a student or two adopt a mature Activity. This would involve completing a set of non-trivial patches for a particular Activity. This is a great opportunity to get to know how others' code is written. You'll be able to show to your future employers that you're able to fit in nicely with a currenty software project.

Proposal Template
See Summer_of_Code/Template.

Development Team

 * Almanac is the hub of the development team. The development team's focus is the core of the Sugar Learning Platform.

Activity Team

 * Resources is a portal of resources for the Activity team. The Activity team is focused on maintaining the individual Activities that sit within the Sugar Learning Platform.

Sugar Labs

 * Sugar Labs/Communication channels for communication channels