Difference between revisions of "Summer of Code/Resources"

From Sugar Labs
Jump to navigation Jump to search
m
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 }}{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}</noinclude>{{TOCright}}
+
<noinclude>{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}</noinclude>{{TOCright}}
 
Sugar Labs is a big project. Like all big projects, it has a big wiki. Here are some pointers:
 
Sugar Labs is a big project. Like all big projects, it has a big wiki. Here are some pointers:
  
Line 15: Line 15:
 
=== Fixing Bugs ===
 
=== 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.
 
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.
# Visit http://dev.sugarlabs.org, also known as http://bugs.sugarlabs.org/
+
# Visit https://dev.sugarlabs.org, also known as https://bugs.sugarlabs.org/
 
# Learn our [[BugSquad/Status_Fields | bug status codes]]
 
# Learn our [[BugSquad/Status_Fields | bug status codes]]
  
Line 40: Line 40:
  
 
===[[Sugar Labs]]===
 
===[[Sugar Labs]]===
* '''[[Sugar Labs/Contacts]]''' for communication channels
+
* '''[[Sugar Labs/Communication channels]]''' for communication channels
  
 
[[Category:Resource]]
 
[[Category:Resource]]
 
[[Category:Idea]]
 
[[Category:Idea]]

Revision as of 20:34, 10 March 2010

Summer of Code Project Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

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

First Steps

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 source code page 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:

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.


Further Resources

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