10
edits
Changes
Created page with "== Developing for Sugar == So you want to contribute to Sugar in code? You've come to the right place. There is always work to do, and we appreciate anyway you can help. <br> ..."
== Developing for Sugar ==
So you want to contribute to Sugar in code? You've come to the right place. There is always work to do, and we appreciate anyway you can help.
<br> There are two ways you can contribute to Sugar in code -
* Contribute to the Sugar shell itself or the related components(like toolkit)
* Contribute to the Activities
'''Note:''' This page isn't complete. Please add whatever seems important.
== Learning required skills ==
Here is a list of recommended resources to learn -
* Python - [http://www.diveintopython.net/toc/index.html Dive into Python], [http://learnpythonthehardway.org/book/ Learn Python the Hard Way]
* git - [http://git-scm.com/book Pro Git book]
* GTK3 for Python - [http://python-gtk-3-tutorial.readthedocs.org/en/latest/ Read the Docs GTK+3 book]
== Contributing to Sugar shell and related components ==
These are the main skills required for developing Sugar shell and toolkit -
* Python
* C
* GTK+ 3
* git
The code for the Sugar shell is on Github. You will need a Github account to contribute and you need to know git, a version control system. <br/>
All repositories in Sugar can be found at our [https://github.com/sugarlabs Github Organization]. See the [http://developer.sugarlabs.org/ developer] website for more information. <br>
Looking for something to do? Check these out -
* [https://github.com/ignaciouy/sugar-irc/wiki/Top-Ten-Tickets-This-Week Top Ten Bugs this week]
* [http://bugs.sugarlabs.org/ Bug Tracker]
== Contributing to Activities ==
These are the main skills required for developing Sugar shell and toolkit -
* Python
* GTK+ 3
* git
You can get started using this manual - http://en.flossmanuals.net/make-your-own-sugar-activities/ <br>
'''Note:''' This manual is a bit outdated, but most of the information still applies. <br>
You can obtain source code from our Gitorious instance - http://git.sugarlabs.org/ <br>
Create an account there, and proceed. It is very much similar to Github.
So you want to contribute to Sugar in code? You've come to the right place. There is always work to do, and we appreciate anyway you can help.
<br> There are two ways you can contribute to Sugar in code -
* Contribute to the Sugar shell itself or the related components(like toolkit)
* Contribute to the Activities
'''Note:''' This page isn't complete. Please add whatever seems important.
== Learning required skills ==
Here is a list of recommended resources to learn -
* Python - [http://www.diveintopython.net/toc/index.html Dive into Python], [http://learnpythonthehardway.org/book/ Learn Python the Hard Way]
* git - [http://git-scm.com/book Pro Git book]
* GTK3 for Python - [http://python-gtk-3-tutorial.readthedocs.org/en/latest/ Read the Docs GTK+3 book]
== Contributing to Sugar shell and related components ==
These are the main skills required for developing Sugar shell and toolkit -
* Python
* C
* GTK+ 3
* git
The code for the Sugar shell is on Github. You will need a Github account to contribute and you need to know git, a version control system. <br/>
All repositories in Sugar can be found at our [https://github.com/sugarlabs Github Organization]. See the [http://developer.sugarlabs.org/ developer] website for more information. <br>
Looking for something to do? Check these out -
* [https://github.com/ignaciouy/sugar-irc/wiki/Top-Ten-Tickets-This-Week Top Ten Bugs this week]
* [http://bugs.sugarlabs.org/ Bug Tracker]
== Contributing to Activities ==
These are the main skills required for developing Sugar shell and toolkit -
* Python
* GTK+ 3
* git
You can get started using this manual - http://en.flossmanuals.net/make-your-own-sugar-activities/ <br>
'''Note:''' This manual is a bit outdated, but most of the information still applies. <br>
You can obtain source code from our Gitorious instance - http://git.sugarlabs.org/ <br>
Create an account there, and proceed. It is very much similar to Github.