Changes

|-

|-

! Sugar desktop user experience on startup

! Sugar desktop user experience on startup

| yes, 0.112 || yes, 0.110 || no, must install packages

| yes, 0.112 || yes, 0.112 || no, must install packages

|-

|-

! Good for Sugar activity development

! Good for Sugar activity development

* For both, you will need knowledge of Sugar activity development, see the book [http://www.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities!]

* For both, you will need knowledge of Sugar activity development, see the book [http://www.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities!]

Python programmers, you must run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and pyflakes on your code ''before'' submitting your patches.

Python programmers, you should run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and flake8 on your changes ''before'' submitting your patches.

=== Getting started with GIT ===

=== Getting started with GIT ===

A few things to keep in mind:

A few things to keep in mind:

* Be sure that your commit and your pull request are linked to an Issue. (Linking to a GCI task is not useful as the GCI tasks are not public and they are transient. If there is no relevant issue, please create one.)

* Do not link commits or pull requests to a GCI task, as these are transient and not public,

* Be sure your commit message explain the problem and how it was solved.

* Link commits and pull requests to any relevant GitHub issue, and if there is no such issue, say so,

* Explain the problem and how it was solved in your commit message, not in your pull request.

=== Setting up a Sugarizer environment ===

=== Setting up a Sugarizer environment ===