10,505
edits
Changes
Jump to navigation
Jump to search
Line 47:
Line 47: − + − === Getting started with coding ===+ − − Sugar development is in either Python or Javascript. − − * You will need knowledge of Python and GTK (See http://python-gtk-3-tutorial.readthedocs.org/en/latest/); − * or Javascript/HTML5; − * and then the basic of Sugar development (See http://www.flossmanuals.net/make-your-own-sugar-activities/); − * and to have a Sugar development environment running (See http://developer.sugarlabs.org). − − Please note that you must run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and pyflakes on your code ''before'' submitting your patches. − − === Getting started with GIT === − − Some knowledge of git is important as your work will be submitted to our git repository (https://github.com/sugarlabs). The basic mechanism is a pull request (PR), which is detailed in [http://developer.sugarlabs.org/contributing.md.html]. − − GitHub provides a tutorial (See https://try.github.io/levels/1/challenges/1), although there are many others as well. − − Note that our bug tracker is http:bugs.sugarlabs.org. − − === Getting started with Sugarizer === − − Sugar Web Framework is the JavaScript Framework for Sugar [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md]. Sugarizer [http://sugarizer.org] is a subset of Sugar that allow runing activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.
→Some basics about Sugar Labs
It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.
It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.
== Some basics about Sugar Labs ==
== Some basics about Sugar Labs and Sugar development ==
For some basics about the project, see [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].
For some basics about the project, see [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].
{{:Google Code In 2017/background}}
== This is a stub for 25+ example tasks new for GCI 2016. ==
== This is a stub for 25+ example tasks new for GCI 2016. ==