Difference between revisions of "Development Team/Getting Involved"
Jump to navigation
Jump to search
m |
|||
(26 intermediate revisions by 10 users not shown) | |||
Line 1: | Line 1: | ||
− | <noinclude>{{ | + | <noinclude>{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude> |
− | + | ==Join the team== | |
− | + | Please add your name to [[Development_Team/Contacts#People|this list]]. | |
− | |||
− | [[Category: | + | ==Summer of Code== |
+ | See the [[Development Team/Project Ideas]] page, & [[Summer of Code]]. | ||
+ | |||
+ | ==Help Plan the Next Release== | ||
+ | See [[{{Upcoming Stable Release}}/Roadmap]], [[Features/Policy]], and [[Development Team/Meetings]]. | ||
+ | |||
+ | == Contribute code == | ||
+ | |||
+ | Please have a look at the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=!sugar&component=!journal&component=!sugar-datastore&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=milestone&keywords=~sugar-love sugar-love tickets]. These are smaller patches that are a good way to learn sugar code and contribute something to the project. You can ask for help on the mailing lists, on the #sugar IRC channel, or directly on the ticket; when you are ready, submit your patch for [[Development Team/Code Review|code review]]. | ||
+ | |||
+ | == Write your own activity == | ||
+ | |||
+ | See [[Activity Team/Resources]]. | ||
+ | |||
+ | [[Category:Development Team]] | ||
+ | [[Category:Participate]] |
Latest revision as of 12:08, 28 September 2010
Join the team
Please add your name to this list.
Summer of Code
See the Development Team/Project Ideas page, & Summer of Code.
Help Plan the Next Release
See 0.114/Roadmap, Features/Policy, and Development Team/Meetings.
Contribute code
Please have a look at the sugar-love tickets. These are smaller patches that are a good way to learn sugar code and contribute something to the project. You can ask for help on the mailing lists, on the #sugar IRC channel, or directly on the ticket; when you are ready, submit your patch for code review.