Talk:Sugar Labs/Getting Involved: Difference between revisions
Garycmartin (talk | contribs) Linking to original pdf artwork if others need to re-use/modify |
|||
| Line 36: | Line 36: | ||
* [[File:Content_Writer.pdf]] | * [[File:Content_Writer.pdf]] | ||
* [[File:Content_Writer_BW.pdf]] | * [[File:Content_Writer_BW.pdf]] | ||
== Do you think there are some easy projects with which I can help Sugar Labs and at the same time gain some practical experience programming? == | |||
We'd love to get you involved. (FYI, there is a group of students | |||
working with Sugar/OLPC in a local school. I can introduce you if you | |||
are interested.) | |||
Re where to get started, there are number of different options. | |||
Perhaps the easiest route is to simply take a Sugar Activity that you | |||
find interesting and make a modification of some sort. This will get | |||
you engaged with the Sugar codebase in a give you a toe hold into | |||
getting more involved. Or you could try writing a Sugar activity from | |||
scratch (really not so difficult and reasonably well documented these | |||
days: http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction). | |||
Keep it simple to begin with and well aligned with some personal | |||
interest. | |||
There is a running list of open tickets (bug reports and feature | |||
requests) here: http://bugs.sugarlabs.org/. This interface is | |||
optimized for the seasoned developer, not newbies, but if you have the | |||
fortitude, you will find lots of introductory challenges. | |||
There is also a Feature request section of our wiki. Many of these | |||
project need a champion and again, some are relatively easy to | |||
approach as someone new to Python | |||
([[Features]]). | |||
Finally, there is no penalty for trying and not succeeding in any of | |||
these tasks. You learn through doing, so jump in. | |||
regards. | |||