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>{{ 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}} |
− | ==Project Ideas== | + | 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 [[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 [[Development_Team/Source_Code | source code]] page 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 http://dev.sugarlabs.org, also known as http://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]]''' | | * '''[[Development Team/Project Ideas]]''' |
Line 9: |
Line 28: |
| * '''[[olpc:Projects_and_proposals|OLPC:Projects and Proposals]]''' | | * '''[[olpc:Projects_and_proposals|OLPC:Projects and Proposals]]''' |
| | | |
− | ==Resources== | + | 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== |
| {{Developers}} | | {{Developers}} |
| ===[[Development Team]]=== | | ===[[Development Team]]=== |
− | * '''[[Development Team/Almanac|Almanac]]''' | + | * '''[[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]]=== |
− | * '''[[Activity Team/Resources|Resources]] | + | * '''[[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]]=== |