Difference between revisions of "Summer of Code/Resources"
Jump to navigation
Jump to search
(interim save) |
|||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <noinclude> | + | <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 10: | Line 10: | ||
=== Getting the Code === | === Getting the Code === | ||
| − | # Know git? Visit our [ | + | # 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 | # You may wish to [[Taxonomy | learn the terms]] we use to describe Sugar's components | ||
=== 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 | + | # 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 30: | Line 30: | ||
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. | 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== | ==Further Resources== | ||
| Line 37: | Line 40: | ||
===[[Activity Team]]=== | ===[[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. | + | * '''[[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]]=== | ||
| − | * '''[[Sugar Labs/ | + | * '''[[Sugar Labs/Communication channels]]''' for communication channels |
[[Category:Resource]] | [[Category:Resource]] | ||
[[Category:Idea]] | [[Category:Idea]] | ||
Latest revision as of 08:14, 1 March 2014
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:
- Development Team/Project Ideas
- Activity Team/Project Ideas
- Sugar Camp, Boston 2008
- OLPC: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
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