Difference between revisions of "Summer of Code/Resources"

Latest revision as of 08:14, 1 March 2014

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

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

Getting the Code

Know git? Visit our resource page for developers to see the repositories of all of the Sugar modules & core Activities
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.

Visit https://dev.sugarlabs.org, also known as https://bugs.sugarlabs.org/
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.

Proposal Template

See Summer_of_Code/Template.

Further Resources

For Developers: almanac · api · bugs · gitorious · cgit · download · people · OLPC: wiki · activities · trac · cgit · build index · repository · firmware · Fedora: packages

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

@@ 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=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:
-==Project Ideas==
+== First Steps ==
-| [[Development Team/Project Ideas]] | [[Activity Team/Project Ideas]] | [[olpc:Projects_and_proposals|OLPC:Projects and Proposals]] |
+=== Getting Orientated ===
+# Learn about the [[Getting_Started | Sugar Learning Platform]]
+# Sign up to our [[Mailing_Lists | mailing lists]] & connect via our [[IRC | IRC channels]]
+# Learn how the different Sugar Labs [[Sugar_Labs/Getting_Involved | project teams]] work together
+=== Getting the Code ===
+# Know git? Visit our [http://developer.sugarlabs.org resource page for developers] to see the repositories of all of the Sugar modules & core Activities
+# You may wish to [[Taxonomy | 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.
+# Visit https://dev.sugarlabs.org, also known as https://bugs.sugarlabs.org/
+# Learn our [[BugSquad/Status_Fields | 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]]'''
+* '''[[Marketing_Team/Events/Sugarcamp_Boston_2008/Minutes#Items_from_the_roadmap_brainstorm |Sugar Camp, Boston 2008]]'''
+* '''[[OLPC:Summer_of_Code/Ideas]]'''
+* '''[[OLPC:Category:GSoC_proposals]]'''
+* '''[[olpc:Projects_and_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]].
+==Further Resources==
+{{Developers}}
+===[[Development Team]]===
+* '''[[Development Team/Almanac|Almanac]]''' is the hub of the development team. The development team's focus is the core of the Sugar Learning Platform.
+===[[Activity Team]]===
+* '''[[Activity Team/Resources|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
+[[Category:Resource]]
+[[Category:Idea]]