Sugar Labs - User contributions [en]

Activities/Tux Paint

2015-12-31T05:24:19Z

Daksh Shah:

<noinclude>[[Category:Activities|Tux Paint]]</noinclude>

[[Image:Tuxpaint-icon.svg]]

== Overview ==

This page is about Sugar support in Tux Paint.

Tux Paint is a drawing app for tiny kids. Most 3-year-old kids and many 2-year-old kids are able to use it, yet 10-year-old kids (and kid-like adults) enjoy it too. Tux Paint features Tux the penguin, like Clippy but not so annoying. Tux Paint uses stereo sound according to where the mouse pointer is. Tux Paint is translated into about 70 different languages, including big-alphabet and right-to-left ones.

== Sugar features ==

The Sugar patch adds the following features:

* Integrate Tux Paint window into the Sugar Shell.
* Following the regular Journal paradigm, save the current drawing to the Journal on exit, and load a saved drawing on resuming its Journal object.
* Use the Journal as a file picker on importing images.

== Build from sources ==

Install dependencies, for Fedora they are:

sudo yum install cmake gperf glib2-devel gtk2-devel libgee06-devel GConf2-devel dbus-glib-devel pango-devel librsvg2-devel python-devel pygtk2-devel pycairo-devel libpaper-devel cairo-devel fribidi-devel SDL-devel SDL_image-devel SDL_mixer-devel SDL_ttf-devel SDL_Pango-devel

and for Ubuntu they are:

sudo apt-get install cmake gperf libglib2.0-dev libgtk2.0-dev libgee-dev libgconf2-dev libdbus-glib-1-dev libghc-pango-dev librsvg2-dev python-dev python-gtk2-dev python-cairo-dev libpaper-dev libcairo2-dev libfribidi-dev libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-ttf2.0-dev libsdl-pango-dev

Fetch sources:

mkdir -p ~/src/tuxpaint
cd ~/src/tuxpaint
wget http://download.sugarlabs.org/sources/external/polyol/polyol-1.2.tar.gz
tar xzpvf polyol-1.2.tar.gz
git clone https://github.com/DakshShah/sltuxpaint

Build Polyol:

cd ~/src/tuxpaint/polyol-1.2
cmake -DCMAKE_INSTALL_PREFIX=$HOME/Activities/tuxpaint.activity && make && make install

Build TuxPaint:

cd ~/src/tuxpaint/sltuxpaint
PKG_CONFIG_PATH=$HOME/Activities/tuxpaint.activity/lib/pkgconfig make PREFIX=$HOME/Activities/tuxpaint.activity SUGAR=1
make PREFIX=$HOME/Activities/tuxpaint.activity SUGAR=1 install

Link activity directory:

cd ~/Activities/tuxpaint.activity
ln -s ~/src/tuxpaint/sltuxpaint/activity .

Make .xo:

cd $HOME/Activities && zip -r ~/tuxpaint-(Version_Number).xo tuxpaint.activity

Install Run-time Dependencies: (from Sugar's Terminal)

cd sugar-build
./osbuild shell
sudo yum install libpaper SDL_Pango libgee06

== Get more stamps ==
There are two options,

1. You download the latest one's from the sourceforge repository's
For that, go to [http://sourceforge.net/projects/tuxpaint/files/tuxpaint-stamps this folder] and select the latest date's folder. From that, download a zip and extract all it's contents. Copy the contents from `TuxPaint/data/stamps` from the extracted zip and paste it under `sugar-build/activities/tuxpaint.activity/share/tuxpaint/stamps` if you want to add them after making xo or to `~/src/tuxpaint/sltuxpaint/stamps` if you want to do it before making the xo (Just after cloning the tuxpaint repository)

2. Rather than cloning the master branch of https://github.com/DakshShah/sltuxpaint, you can clone it's with [https://github.com/DakshShah/sltuxpaint/tree/withstamps stamps branch]. To do that, rather than running the command

git clone https://github.com/DakshShah/sltuxpaint

Do,

git clone -b withstamps https://github.com/DakshShah/sltuxpaint

== Getting involved ==

* For non-Sugar related changes, go to http://tuxpaint.org/help/.
* [http://bugs.sugarlabs.org/newticket?component=TuxPaint Report] on Sugar bugs.

== Resources ==

* [http://www.tuxpaint.org/ Home page]
* [http://git.sugarlabs.org/tuxpaint/ Sugar patch sources]
* [http://activities.sugarlabs.org/en-US/sugar/addon/4088 Sugar Activity Library page]
* [http://wiki.laptop.org/go/Tux_Paint Tux Paint on OLPC wiki]
* Trac tickets: [http://dev.laptop.org/query?component=tuxpaint-activity&col=id&col=summary&col=type&col=status&col=priority&col=milestone&col=time&col=changetime&order=priority OLPC], [http://bugs.sugarlabs.org/query?component=TuxPaint&col=id&col=summary&col=component&col=type&col=status&col=priority&col=milestone&col=time&col=changetime&order=priority Sugar Labs]

File:Frescobaldi mac 3.png

2015-12-18T17:06:20Z

Daksh Shah: Daksh Shah uploaded a new version of File:Frescobaldi mac 3.png

File:Frescobaldi mac 3.png

2015-12-18T15:36:13Z

Daksh Shah:

File:Frescobaldi mac 2.png

2015-12-18T15:33:31Z

Daksh Shah:

File:Frescobaldi mac 1.png

2015-12-18T15:30:18Z

Daksh Shah:

File:Lilypond mac install.png

2015-12-18T15:19:13Z

Daksh Shah:

File:Lilypond mac install 4.png

2015-12-18T05:51:16Z

Daksh Shah:

File:LilyPond Mac 3.png

2015-12-18T05:48:54Z

Daksh Shah:

File:LilyPond Mac 2.png

2015-12-18T05:46:24Z

Daksh Shah:

File:LilyPond Mac 1.png

2015-12-18T05:45:03Z

Daksh Shah:

File:MusicBlocksGitClone.png

2015-12-17T16:50:48Z

Daksh Shah:

File:MusicBlocks GitHubIO.png

2015-12-17T15:17:59Z

Daksh Shah:

File:Lilypond mac 8.png

2015-12-16T15:10:15Z

Daksh Shah:

File:Lilypond mac 7.png

2015-12-16T15:09:47Z

Daksh Shah:

File:Lilypond mac 6.png

2015-12-16T15:08:59Z

Daksh Shah:

File:Lilypond mac 5.png

2015-12-16T15:08:32Z

Daksh Shah:

File:Lilypond mac 4.png

2015-12-16T15:07:55Z

Daksh Shah:

File:Lilypond mac 3.png

2015-12-16T15:07:24Z

Daksh Shah:

File:Lilypond mac 2.png

2015-12-16T15:06:51Z

Daksh Shah:

File:Lilypond mac 1.png

2015-12-16T15:05:30Z

Daksh Shah:

File:Save as lilypond.svg

2015-12-16T10:42:22Z

Daksh Shah:

File:LilyPondWindows3.png

2015-12-15T14:44:58Z

Daksh Shah:

File:LilyPondWindows2.png

2015-12-15T14:44:09Z

Daksh Shah:

File:LilyPondWindows1.png

2015-12-15T14:43:35Z

Daksh Shah:

File:Save to ly MusicBlocks.png

2015-12-15T14:42:30Z

Daksh Shah:

Sugarizer

2015-12-12T18:54:56Z

Daksh Shah:

[[File:Sugarizer_responsive.png|200px|left]]

__TOC__

The Sugar Learning Platform is a leading learning platform developed for the One Laptop per Child project and used every day by nearly 3 million children around the world. With [http://sugarizer.org/ '''Sugarizer'''], you could discover the Sugar Learning Platform on any device: from the tiny Raspberry PI to the small Android/iOS tablet or the bigger PC/Mac. Enjoy the experience and help us reach every children on every device in every country.

Sugarizer is distributed in the form of 3 components:

* [http://sugarizer.org/#thinclient '''Thin Client''']: remote access to Sugarizer using a browser,
* [http://sugarizer.org/#client '''Client''']: Sugarizer running locally,
* [http://sugarizer.org/#server '''Server''']: place to run remote Sugarizer features.

== Thin Client ==

[[Image:Sugarizer_thinclient.svg|right]]

Sugarizer Thin Client is Sugarizer in a browser. It could work on any device with a recent Chrome/Chromium version, and has also been tested successfully on Firefox, Safari and IE. Sugarizer Thin Client doesn't need any installation on the device but requires a permanent access to a Sugarizer Server.

[http://server.sugarizer.org/ '''Run it Now''']

Features of Sugarizer Thin Client include:
* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see [https://en.wikipedia.org/wiki/Web_storage '''here''']),
* Running of remote stored Sugar Web Activities,
* Backup or sharing of local storage content to the Server,
* Presence and collaboration

Note: You can run sugarizer from the link above, but the Thin Client access is provided by all the Sugarizer Servers, so you can use others as well.

== Client ==

[[File:Sugarizer_client.svg|right]]

Sugarizer Client is Sugarizer installed locally on the device so it does not require any access to the Server - it works stand-alone. Server access could be required only when it needs network features. Sugarizer could work on any device with a recent Chrome/Chromium version and has also been tested successfully on Firefox, Safari and IE. Sugarizer Client is available for PC, for Android, iOS, Chrome Web App and for Firefox OS devices.

To install Sugarizer on a PC (GNU Linux/Mac OS/Windows), download the file [http://sugarizer.org/org.olpc-france.sugarizer.zip '''org.olpc-france.sugarizer.zip'''], unzip its content, then launch Chrome using the command line:
chrome --allow-file-access-from-files
Then open the "index.html" file in the browser. Note that the option "--allow-file-access-from-files" is needed to authorize access to local file. Don't forget to close all other instances of Chrome before using this option. For other browser equivalent options see [https://github.com/mrdoob/three.js/wiki/How-to-run-things-locally '''here''']. Do not hesitate to write a shortcut on this command for future use.

Note that if your browser is Chrome you could install Sugarizer as a Chrome Web App, just go to the Chrome Web Store (see [http://sugarizer.org/#stores '''here''']) and click on it. It will avoid you any installation.

Also, in case you are not able to make sugarizer work on Chromium on Ubuntu, you might want to consider trying to run it on Firefox.

Features of Sugarizer Client include:

* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see here),
* Running of locally stored Sugar Web Activities,
* Capability to connect to a server to backup or sharing local storage to the Server,
* Presence and collaboration

== Server ==

[[File:Sugarizer_server.svg|right]]

Sugarizer Server is the back-end for network features of Sugarizer. It means: allow deployment of Sugarizer on a local server, for example on a school server, so expose locally Thin Client (without Internet access). Sugarizer Server can also be used to provide collaboration features for Client and Thin Client on the network. Sugarizer Server could be deployed on any computer with Apache2, Node.js and MongoDB.

[http://sugarizer.org/org.olpc-france.sugarizer.zip '''Download Server''']

Sugarizer Server features include:

* Sugarizer Thin Client access,
* Backup and shared storage for Client and Thin Client,
* Presence and collaboration handling between Client/Thin Client on the same network

A Sugarizer server instance is accessible [http://server.sugarizer.org/ '''here'''].

== Sugarizer for Android ==
To install Sugarizer on Android, you could install it directly from Google Play, Amazon App Store or F-Droid (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use stores, you could download it directly. First "enable installation from unknown sources" in the Android device settings to allow the installation of an application outside Google Play (see [http://www.tech-recipes.com/rx/22616/android-allow-installation-of-non-market-apps/ '''here'''] to learn how). Then download the file [http://sugarizer.org/org.olpc-france.sugarizer.apk '''org.olpc-france.sugarizer.apk'''] from your browser and accept conditions.

[http://sugarizer.org/org.olpc-france.sugarizer.apk '''Download for Android''']

== Sugarizer for Firefox OS ==

To install Sugarizer on Firefox OS, you could install it directly from the Firefox Marketplace (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use the marketplace, you could download it directly. Just click on the button below and follow instructions on the next screen.

[http://sugarizer.org/firefoxos '''Download for Firefox OS''']

== How does it work ==

Sugarizer reproduce main features of the Sugar learning platform in HTML5/JavaScript. Sugarizer also expose these features to allow running of Sugar web activities wrote for Sugar 0.100. So all activities included in the Sugarizer package work in the same on Sugar 0.100.

== Where can I find the Source Code ==

The source code of sugarizer is available on [https://github.com/llaske/Sugarizer '''github'''], fork the repo to start hacking!

Sugarizer

2015-12-12T18:49:38Z

Daksh Shah:

__TOC__

The Sugar Learning Platform is a leading learning platform developed for the One Laptop per Child project and used every day by nearly 3 million children around the world. With [http://sugarizer.org/ '''Sugarizer'''], you could discover the Sugar Learning Platform on any device: from the tiny Raspberry PI to the small Android/iOS tablet or the bigger PC/Mac. Enjoy the experience and help us reach every children on every device in every country.

Sugarizer is distributed in the form of 3 components:

* [http://sugarizer.org/#thinclient '''Thin Client''']: remote access to Sugarizer using a browser,
* [http://sugarizer.org/#client '''Client''']: Sugarizer running locally,
* [http://sugarizer.org/#server '''Server''']: place to run remote Sugarizer features.

== Thin Client ==

[[Image:Sugarizer_thinclient.svg|right]]

Sugarizer Thin Client is Sugarizer in a browser. It could work on any device with a recent Chrome/Chromium version, and has also been tested successfully on Firefox, Safari and IE. Sugarizer Thin Client doesn't need any installation on the device but requires a permanent access to a Sugarizer Server.

[http://server.sugarizer.org/ '''Run it Now''']

Features of Sugarizer Thin Client include:
* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see [https://en.wikipedia.org/wiki/Web_storage '''here''']),
* Running of remote stored Sugar Web Activities,
* Backup or sharing of local storage content to the Server,
* Presence and collaboration

Note: You can run sugarizer from the link above, but the Thin Client access is provided by all the Sugarizer Servers, so you can use others as well.

== Client ==

[[File:Sugarizer_client.svg|right]]

Sugarizer Client is Sugarizer installed locally on the device so it does not require any access to the Server - it works stand-alone. Server access could be required only when it needs network features. Sugarizer could work on any device with a recent Chrome/Chromium version and has also been tested successfully on Firefox, Safari and IE. Sugarizer Client is available for PC, for Android, iOS, Chrome Web App and for Firefox OS devices.

To install Sugarizer on a PC (GNU Linux/Mac OS/Windows), download the file [http://sugarizer.org/org.olpc-france.sugarizer.zip '''org.olpc-france.sugarizer.zip'''], unzip its content, then launch Chrome using the command line:
chrome --allow-file-access-from-files
Then open the "index.html" file in the browser. Note that the option "--allow-file-access-from-files" is needed to authorize access to local file. Don't forget to close all other instances of Chrome before using this option. For other browser equivalent options see [https://github.com/mrdoob/three.js/wiki/How-to-run-things-locally '''here''']. Do not hesitate to write a shortcut on this command for future use.

Note that if your browser is Chrome you could install Sugarizer as a Chrome Web App, just go to the Chrome Web Store (see [http://sugarizer.org/#stores '''here''']) and click on it. It will avoid you any installation.

Also, in case you are not able to make sugarizer work on Chromium on Ubuntu, you might want to consider trying to run it on Firefox.

Features of Sugarizer Client include:

* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see here),
* Running of locally stored Sugar Web Activities,
* Capability to connect to a server to backup or sharing local storage to the Server,
* Presence and collaboration

== Server ==

[[File:Sugarizer_server.svg|right]]

Sugarizer Server is the back-end for network features of Sugarizer. It means: allow deployment of Sugarizer on a local server, for example on a school server, so expose locally Thin Client (without Internet access). Sugarizer Server can also be used to provide collaboration features for Client and Thin Client on the network. Sugarizer Server could be deployed on any computer with Apache2, Node.js and MongoDB.

[http://sugarizer.org/org.olpc-france.sugarizer.zip '''Download Server''']

Sugarizer Server features include:

* Sugarizer Thin Client access,
* Backup and shared storage for Client and Thin Client,
* Presence and collaboration handling between Client/Thin Client on the same network

A Sugarizer server instance is accessible [http://server.sugarizer.org/ '''here'''].

== Sugarizer for Android ==
To install Sugarizer on Android, you could install it directly from Google Play, Amazon App Store or F-Droid (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use stores, you could download it directly. First "enable installation from unknown sources" in the Android device settings to allow the installation of an application outside Google Play (see [http://www.tech-recipes.com/rx/22616/android-allow-installation-of-non-market-apps/ '''here'''] to learn how). Then download the file [http://sugarizer.org/org.olpc-france.sugarizer.apk '''org.olpc-france.sugarizer.apk'''] from your browser and accept conditions.

[http://sugarizer.org/org.olpc-france.sugarizer.apk '''Download for Android''']

== Sugarizer for Firefox OS ==

To install Sugarizer on Firefox OS, you could install it directly from the Firefox Marketplace (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use the marketplace, you could download it directly. Just click on the button below and follow instructions on the next screen.

[http://sugarizer.org/firefoxos '''Download for Firefox OS''']

== How does it work ==

Sugarizer reproduce main features of the Sugar learning platform in HTML5/JavaScript. Sugarizer also expose these features to allow running of Sugar web activities wrote for Sugar 0.100. So all activities included in the Sugarizer package work in the same on Sugar 0.100.

== Where can I find the Source Code ==

The source code of sugarizer is available on [https://github.com/llaske/Sugarizer '''github'''], fork the repo to start hacking!

File:Sugarizer responsive.png

2015-12-12T18:48:29Z

Daksh Shah:

File:Sugarizer.png

2015-12-12T18:47:33Z

Daksh Shah:

Sugarizer

2015-12-12T18:42:48Z

Daksh Shah:

The Sugar Learning Platform is a leading learning platform developed for the One Laptop per Child project and used every day by nearly 3 million children around the world. With [http://sugarizer.org/ '''Sugarizer'''], you could discover the Sugar Learning Platform on any device: from the tiny Raspberry PI to the small Android/iOS tablet or the bigger PC/Mac. Enjoy the experience and help us reach every children on every device in every country.

Sugarizer is distributed in the form of 3 components:

* [http://sugarizer.org/#thinclient '''Thin Client''']: remote access to Sugarizer using a browser,
* [http://sugarizer.org/#client '''Client''']: Sugarizer running locally,
* [http://sugarizer.org/#server '''Server''']: place to run remote Sugarizer features.

__TOC__

== Thin Client ==

[[Image:Sugarizer_thinclient.svg|right]]

Sugarizer Thin Client is Sugarizer in a browser. It could work on any device with a recent Chrome/Chromium version, and has also been tested successfully on Firefox, Safari and IE. Sugarizer Thin Client doesn't need any installation on the device but requires a permanent access to a Sugarizer Server.

[http://server.sugarizer.org/ '''Run it Now''']

Features of Sugarizer Thin Client include:
* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see [https://en.wikipedia.org/wiki/Web_storage '''here''']),
* Running of remote stored Sugar Web Activities,
* Backup or sharing of local storage content to the Server,
* Presence and collaboration

Note: You can run sugarizer from the link above, but the Thin Client access is provided by all the Sugarizer Servers, so you can use others as well.

== Client ==

[[File:Sugarizer_client.svg|right]]

Sugarizer Client is Sugarizer installed locally on the device so it does not require any access to the Server - it works stand-alone. Server access could be required only when it needs network features. Sugarizer could work on any device with a recent Chrome/Chromium version and has also been tested successfully on Firefox, Safari and IE. Sugarizer Client is available for PC, for Android, iOS, Chrome Web App and for Firefox OS devices.

To install Sugarizer on a PC (GNU Linux/Mac OS/Windows), download the file [http://sugarizer.org/org.olpc-france.sugarizer.zip '''org.olpc-france.sugarizer.zip'''], unzip its content, then launch Chrome using the command line:
chrome --allow-file-access-from-files
Then open the "index.html" file in the browser. Note that the option "--allow-file-access-from-files" is needed to authorize access to local file. Don't forget to close all other instances of Chrome before using this option. For other browser equivalent options see [https://github.com/mrdoob/three.js/wiki/How-to-run-things-locally '''here''']. Do not hesitate to write a shortcut on this command for future use.

Note that if your browser is Chrome you could install Sugarizer as a Chrome Web App, just go to the Chrome Web Store (see [http://sugarizer.org/#stores '''here''']) and click on it. It will avoid you any installation.

Also, in case you are not able to make sugarizer work on Chromium on Ubuntu, you might want to consider trying to run it on Firefox.

Features of Sugarizer Client include:

* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see here),
* Running of locally stored Sugar Web Activities,
* Capability to connect to a server to backup or sharing local storage to the Server,
* Presence and collaboration

== Server ==

[[File:Sugarizer_server.svg|right]]

Sugarizer Server is the back-end for network features of Sugarizer. It means: allow deployment of Sugarizer on a local server, for example on a school server, so expose locally Thin Client (without Internet access). Sugarizer Server can also be used to provide collaboration features for Client and Thin Client on the network. Sugarizer Server could be deployed on any computer with Apache2, Node.js and MongoDB.

[http://sugarizer.org/org.olpc-france.sugarizer.zip '''Download Server''']

Sugarizer Server features include:

* Sugarizer Thin Client access,
* Backup and shared storage for Client and Thin Client,
* Presence and collaboration handling between Client/Thin Client on the same network

A Sugarizer server instance is accessible [http://server.sugarizer.org/ '''here'''].

== Sugarizer for Android ==
To install Sugarizer on Android, you could install it directly from Google Play, Amazon App Store or F-Droid (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use stores, you could download it directly. First "enable installation from unknown sources" in the Android device settings to allow the installation of an application outside Google Play (see [http://www.tech-recipes.com/rx/22616/android-allow-installation-of-non-market-apps/ '''here'''] to learn how). Then download the file [http://sugarizer.org/org.olpc-france.sugarizer.apk '''org.olpc-france.sugarizer.apk'''] from your browser and accept conditions.

[http://sugarizer.org/org.olpc-france.sugarizer.apk '''Download for Android''']

== Sugarizer for Firefox OS ==

To install Sugarizer on Firefox OS, you could install it directly from the Firefox Marketplace (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use the marketplace, you could download it directly. Just click on the button below and follow instructions on the next screen.

[http://sugarizer.org/firefoxos '''Download for Firefox OS''']

== How does it work ==

Sugarizer reproduce main features of the Sugar learning platform in HTML5/JavaScript. Sugarizer also expose these features to allow running of Sugar web activities wrote for Sugar 0.100. So all activities included in the Sugarizer package work in the same on Sugar 0.100.

== Where can I find the Source Code ==

The source code of sugarizer is available on [https://github.com/llaske/Sugarizer '''github'''], fork the repo to start hacking!

Sugarizer

2015-12-12T18:39:43Z

Daksh Shah:

[File:Sugarizer_server.svg]

The Sugar Learning Platform is a leading learning platform developed for the One Laptop per Child project and used every day by nearly 3 million children around the world. With [http://sugarizer.org/ '''Sugarizer'''], you could discover the Sugar Learning Platform on any device: from the tiny Raspberry PI to the small Android/iOS tablet or the bigger PC/Mac. Enjoy the experience and help us reach every children on every device in every country.

Sugarizer is distributed in the form of 3 components:

* [http://sugarizer.org/#thinclient '''Thin Client''']: remote access to Sugarizer using a browser,
* [http://sugarizer.org/#client '''Client''']: Sugarizer running locally,
* [http://sugarizer.org/#server '''Server''']: place to run remote Sugarizer features.

== Thin Client ==

[Image:Sugarizer_thinclient.svg|right]

Sugarizer Thin Client is Sugarizer in a browser. It could work on any device with a recent Chrome/Chromium version, and has also been tested successfully on Firefox, Safari and IE. Sugarizer Thin Client doesn't need any installation on the device but requires a permanent access to a Sugarizer Server.

[http://server.sugarizer.org/ '''Run it Now''']

Features of Sugarizer Thin Client include:
* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see [https://en.wikipedia.org/wiki/Web_storage '''here''']),
* Running of remote stored Sugar Web Activities,
* Backup or sharing of local storage content to the Server,
* Presence and collaboration

Note: You can run sugarizer from the link above, but the Thin Client access is provided by all the Sugarizer Servers, so you can use others as well.

== Client ==

Sugarizer Client is Sugarizer installed locally on the device so it does not require any access to the Server - it works stand-alone. Server access could be required only when it needs network features. Sugarizer could work on any device with a recent Chrome/Chromium version and has also been tested successfully on Firefox, Safari and IE. Sugarizer Client is available for PC, for Android, iOS, Chrome Web App and for Firefox OS devices.

To install Sugarizer on a PC (GNU Linux/Mac OS/Windows), download the file [http://sugarizer.org/org.olpc-france.sugarizer.zip '''org.olpc-france.sugarizer.zip'''], unzip its content, then launch Chrome using the command line:
chrome --allow-file-access-from-files
Then open the "index.html" file in the browser. Note that the option "--allow-file-access-from-files" is needed to authorize access to local file. Don't forget to close all other instances of Chrome before using this option. For other browser equivalent options see [https://github.com/mrdoob/three.js/wiki/How-to-run-things-locally '''here''']. Do not hesitate to write a shortcut on this command for future use.

Note that if your browser is Chrome you could install Sugarizer as a Chrome Web App, just go to the Chrome Web Store (see [http://sugarizer.org/#stores '''here''']) and click on it. It will avoid you any installation.

Also, in case you are not able to make sugarizer work on Chromium on Ubuntu, you might want to consider trying to run it on Firefox.

Features of Sugarizer Client include:

* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see here),
* Running of locally stored Sugar Web Activities,
* Capability to connect to a server to backup or sharing local storage to the Server,
* Presence and collaboration

== Server ==
Sugarizer Server is the back-end for network features of Sugarizer. It means: allow deployment of Sugarizer on a local server, for example on a school server, so expose locally Thin Client (without Internet access). Sugarizer Server can also be used to provide collaboration features for Client and Thin Client on the network. Sugarizer Server could be deployed on any computer with Apache2, Node.js and MongoDB.

[http://sugarizer.org/org.olpc-france.sugarizer.zip '''Download Server''']

Sugarizer Server features include:

* Sugarizer Thin Client access,
* Backup and shared storage for Client and Thin Client,
* Presence and collaboration handling between Client/Thin Client on the same network

A Sugarizer server instance is accessible [http://server.sugarizer.org/ '''here'''].

== Sugarizer for Android ==
To install Sugarizer on Android, you could install it directly from Google Play, Amazon App Store or F-Droid (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use stores, you could download it directly. First "enable installation from unknown sources" in the Android device settings to allow the installation of an application outside Google Play (see [http://www.tech-recipes.com/rx/22616/android-allow-installation-of-non-market-apps/ '''here'''] to learn how). Then download the file [http://sugarizer.org/org.olpc-france.sugarizer.apk '''org.olpc-france.sugarizer.apk'''] from your browser and accept conditions.

[http://sugarizer.org/org.olpc-france.sugarizer.apk '''Download for Android''']

== Sugarizer for Firefox OS ==

To install Sugarizer on Firefox OS, you could install it directly from the Firefox Marketplace (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use the marketplace, you could download it directly. Just click on the button below and follow instructions on the next screen.

[http://sugarizer.org/firefoxos '''Download for Firefox OS''']

== How does it work ==

Sugarizer reproduce main features of the Sugar learning platform in HTML5/JavaScript. Sugarizer also expose these features to allow running of Sugar web activities wrote for Sugar 0.100. So all activities included in the Sugarizer package work in the same on Sugar 0.100.

== Where can I find the Source Code ==

The source code of sugarizer is available on [https://github.com/llaske/Sugarizer '''github'''], fork the repo to start hacking!

Sugarizer

2015-12-12T18:37:50Z

Daksh Shah:

[Image:Sugarizer server.svg]
The Sugar Learning Platform is a leading learning platform developed for the One Laptop per Child project and used every day by nearly 3 million children around the world. With [http://sugarizer.org/ '''Sugarizer'''], you could discover the Sugar Learning Platform on any device: from the tiny Raspberry PI to the small Android/iOS tablet or the bigger PC/Mac. Enjoy the experience and help us reach every children on every device in every country.

Sugarizer is distributed in the form of 3 components:

* [http://sugarizer.org/#thinclient '''Thin Client''']: remote access to Sugarizer using a browser,
* [http://sugarizer.org/#client '''Client''']: Sugarizer running locally,
* [http://sugarizer.org/#server '''Server''']: place to run remote Sugarizer features.

== Thin Client ==
[Image:Sugarizer_thinclient.svg|right]
Sugarizer Thin Client is Sugarizer in a browser. It could work on any device with a recent Chrome/Chromium version, and has also been tested successfully on Firefox, Safari and IE. Sugarizer Thin Client doesn't need any installation on the device but requires a permanent access to a Sugarizer Server.

[http://server.sugarizer.org/ '''Run it Now''']

Features of Sugarizer Thin Client include:
* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see [https://en.wikipedia.org/wiki/Web_storage '''here''']),
* Running of remote stored Sugar Web Activities,
* Backup or sharing of local storage content to the Server,
* Presence and collaboration

Note: You can run sugarizer from the link above, but the Thin Client access is provided by all the Sugarizer Servers, so you can use others as well.

== Client ==

Sugarizer Client is Sugarizer installed locally on the device so it does not require any access to the Server - it works stand-alone. Server access could be required only when it needs network features. Sugarizer could work on any device with a recent Chrome/Chromium version and has also been tested successfully on Firefox, Safari and IE. Sugarizer Client is available for PC, for Android, iOS, Chrome Web App and for Firefox OS devices.

To install Sugarizer on a PC (GNU Linux/Mac OS/Windows), download the file [http://sugarizer.org/org.olpc-france.sugarizer.zip '''org.olpc-france.sugarizer.zip'''], unzip its content, then launch Chrome using the command line:
chrome --allow-file-access-from-files
Then open the "index.html" file in the browser. Note that the option "--allow-file-access-from-files" is needed to authorize access to local file. Don't forget to close all other instances of Chrome before using this option. For other browser equivalent options see [https://github.com/mrdoob/three.js/wiki/How-to-run-things-locally '''here''']. Do not hesitate to write a shortcut on this command for future use.

Note that if your browser is Chrome you could install Sugarizer as a Chrome Web App, just go to the Chrome Web Store (see [http://sugarizer.org/#stores '''here''']) and click on it. It will avoid you any installation.

Also, in case you are not able to make sugarizer work on Chromium on Ubuntu, you might want to consider trying to run it on Firefox.

Features of Sugarizer Client include:

* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see here),
* Running of locally stored Sugar Web Activities,
* Capability to connect to a server to backup or sharing local storage to the Server,
* Presence and collaboration

== Server ==
Sugarizer Server is the back-end for network features of Sugarizer. It means: allow deployment of Sugarizer on a local server, for example on a school server, so expose locally Thin Client (without Internet access). Sugarizer Server can also be used to provide collaboration features for Client and Thin Client on the network. Sugarizer Server could be deployed on any computer with Apache2, Node.js and MongoDB.

[http://sugarizer.org/org.olpc-france.sugarizer.zip '''Download Server''']

Sugarizer Server features include:

* Sugarizer Thin Client access,
* Backup and shared storage for Client and Thin Client,
* Presence and collaboration handling between Client/Thin Client on the same network

A Sugarizer server instance is accessible [http://server.sugarizer.org/ '''here'''].

== Sugarizer for Android ==
To install Sugarizer on Android, you could install it directly from Google Play, Amazon App Store or F-Droid (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use stores, you could download it directly. First "enable installation from unknown sources" in the Android device settings to allow the installation of an application outside Google Play (see [http://www.tech-recipes.com/rx/22616/android-allow-installation-of-non-market-apps/ '''here'''] to learn how). Then download the file [http://sugarizer.org/org.olpc-france.sugarizer.apk '''org.olpc-france.sugarizer.apk'''] from your browser and accept conditions.

[http://sugarizer.org/org.olpc-france.sugarizer.apk '''Download for Android''']

== Sugarizer for Firefox OS ==

To install Sugarizer on Firefox OS, you could install it directly from the Firefox Marketplace (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use the marketplace, you could download it directly. Just click on the button below and follow instructions on the next screen.

[http://sugarizer.org/firefoxos '''Download for Firefox OS''']

== How does it work ==

Sugarizer reproduce main features of the Sugar learning platform in HTML5/JavaScript. Sugarizer also expose these features to allow running of Sugar web activities wrote for Sugar 0.100. So all activities included in the Sugarizer package work in the same on Sugar 0.100.

== Where can I find the Source Code ==

The source code of sugarizer is available on [https://github.com/llaske/Sugarizer '''github'''], fork the repo to start hacking!

File:Sugarizer thinclient.svg

2015-12-12T18:31:52Z

Daksh Shah:

File:Sugarizer server.svg

2015-12-12T18:31:38Z

Daksh Shah:

File:Sugarizer client.svg

2015-12-12T18:31:04Z

Daksh Shah:

Sugarizer

2015-12-12T18:29:56Z

Daksh Shah: Created page with "The Sugar Learning Platform is a leading learning platform developed for the One Laptop per Child project and used every day by nearly 3 million children around the world. Wit..."

The Sugar Learning Platform is a leading learning platform developed for the One Laptop per Child project and used every day by nearly 3 million children around the world. With [http://sugarizer.org/ '''Sugarizer'''], you could discover the Sugar Learning Platform on any device: from the tiny Raspberry PI to the small Android/iOS tablet or the bigger PC/Mac. Enjoy the experience and help us reach every children on every device in every country.

Sugarizer is distributed in the form of 3 components:

* [http://sugarizer.org/#thinclient '''Thin Client''']: remote access to Sugarizer using a browser,
* [http://sugarizer.org/#client '''Client''']: Sugarizer running locally,
* [http://sugarizer.org/#server '''Server''']: place to run remote Sugarizer features.

== Thin Client ==
Sugarizer Thin Client is Sugarizer in a browser. It could work on any device with a recent Chrome/Chromium version, and has also been tested successfully on Firefox, Safari and IE. Sugarizer Thin Client doesn't need any installation on the device but requires a permanent access to a Sugarizer Server.

[http://server.sugarizer.org/ '''Run it Now''']

Features of Sugarizer Thin Client include:
* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see [https://en.wikipedia.org/wiki/Web_storage '''here''']),
* Running of remote stored Sugar Web Activities,
* Backup or sharing of local storage content to the Server,
* Presence and collaboration

Note: You can run sugarizer from the link above, but the Thin Client access is provided by all the Sugarizer Servers, so you can use others as well.

== Client ==

Sugarizer Client is Sugarizer installed locally on the device so it does not require any access to the Server - it works stand-alone. Server access could be required only when it needs network features. Sugarizer could work on any device with a recent Chrome/Chromium version and has also been tested successfully on Firefox, Safari and IE. Sugarizer Client is available for PC, for Android, iOS, Chrome Web App and for Firefox OS devices.

To install Sugarizer on a PC (GNU Linux/Mac OS/Windows), download the file [http://sugarizer.org/org.olpc-france.sugarizer.zip '''org.olpc-france.sugarizer.zip'''], unzip its content, then launch Chrome using the command line:
chrome --allow-file-access-from-files
Then open the "index.html" file in the browser. Note that the option "--allow-file-access-from-files" is needed to authorize access to local file. Don't forget to close all other instances of Chrome before using this option. For other browser equivalent options see [https://github.com/mrdoob/three.js/wiki/How-to-run-things-locally '''here''']. Do not hesitate to write a shortcut on this command for future use.

Note that if your browser is Chrome you could install Sugarizer as a Chrome Web App, just go to the Chrome Web Store (see [http://sugarizer.org/#stores '''here''']) and click on it. It will avoid you any installation.

Also, in case you are not able to make sugarizer work on Chromium on Ubuntu, you might want to consider trying to run it on Firefox.

Features of Sugarizer Client include:

* Sugar Desktop view (Radial, List and Journal),
* Sugar Local data store storage - limited by the browser to 5Mb (see here),
* Running of locally stored Sugar Web Activities,
* Capability to connect to a server to backup or sharing local storage to the Server,
* Presence and collaboration

== Server ==
Sugarizer Server is the back-end for network features of Sugarizer. It means: allow deployment of Sugarizer on a local server, for example on a school server, so expose locally Thin Client (without Internet access). Sugarizer Server can also be used to provide collaboration features for Client and Thin Client on the network. Sugarizer Server could be deployed on any computer with Apache2, Node.js and MongoDB.

[http://sugarizer.org/org.olpc-france.sugarizer.zip '''Download Server''']

Sugarizer Server features include:

* Sugarizer Thin Client access,
* Backup and shared storage for Client and Thin Client,
* Presence and collaboration handling between Client/Thin Client on the same network

A Sugarizer server instance is accessible [http://server.sugarizer.org/ '''here'''].

== Sugarizer for Android ==
To install Sugarizer on Android, you could install it directly from Google Play, Amazon App Store or F-Droid (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use stores, you could download it directly. First "enable installation from unknown sources" in the Android device settings to allow the installation of an application outside Google Play (see [http://www.tech-recipes.com/rx/22616/android-allow-installation-of-non-market-apps/ '''here'''] to learn how). Then download the file [http://sugarizer.org/org.olpc-france.sugarizer.apk '''org.olpc-france.sugarizer.apk'''] from your browser and accept conditions.

[http://sugarizer.org/org.olpc-france.sugarizer.apk '''Download for Android''']

== Sugarizer for Firefox OS ==

To install Sugarizer on Firefox OS, you could install it directly from the Firefox Marketplace (see [http://sugarizer.org/#stores '''here''']). However if you don't want to use the marketplace, you could download it directly. Just click on the button below and follow instructions on the next screen.

[http://sugarizer.org/firefoxos '''Download for Firefox OS''']

== How does it work ==

Sugarizer reproduce main features of the Sugar learning platform in HTML5/JavaScript. Sugarizer also expose these features to allow running of Sugar web activities wrote for Sugar 0.100. So all activities included in the Sugarizer package work in the same on Sugar 0.100.

== Where can I find the Source Code ==

The source code of sugarizer is available on [https://github.com/llaske/Sugarizer '''github'''], fork the repo to start hacking!

Activity Team/Git Tutorial

2015-12-12T17:57:35Z

Daksh Shah: /* Branches */

<noinclude>{{TeamHeader|Activity Team}}</noinclude>

== GitHub ==

Sugar Labs uses GitHub as its primary server for git repositories. While you are welcome to use other servers, it is on GitHub where you will find the master branches of the core modules and core activities.

Getting started with GitHub

You will learn to do the following:
* Create an account, which you do once.
* Create and add an SSH key, which you do once or if you change system.
* Create a project, a local repository, and identify yourself to git, which you do once per project.
* Add source files, change existing source files, commit changes, push changes, and pull changes, which you do regularly.

=== Create an Account ===

Create an account [https://github.com/join here]

=== Create SSH Key on Windows ===

To create an SSH Key on Windows, download the latest [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] [http://the.earth.li/~sgtatham/putty/latest/x86/putty-installer.exe installer].

* Run the puttygen.exe utility to generate a pair of private/public keys.
* Click on the ''Generate'' button (Make sure SSH-2 RSA parameter is checked)
* Move the mouse around to generate your key.
* Once you have accumulated enough "heat", the application will generate your key pair.
* Make sure you enter a lengthy passphrase in the Key passphrase field and confirm it in the Confirm passphrase field.
* Click on the Save private key button to save your private key in a file.

Congratulations! With your mouse, select the content of the box labelled Public key and press Control-C to copy your public SSH key.
This key can now be used on GitHub to access Git on Windows. Good luck!

=== Create SSH Key on GNU/Linux ===

Skip this section if you already have an SSH key in <tt>.ssh</tt> directory that you trust.

(An easy-to-read tutorial for generating an ssh key can be found [https://help.github.com/articles/generating-ssh-keys here].)

To create a key use ''ssh-keygen''. The following command will create a “dsa” key:
ssh-keygen -t dsa

For creating a “rsa” key use:
ssh-keygen -t rsa

The key will be stored as two files in the hidden <tt>.ssh</tt> directory.

<tt>id_dsa.pub</tt> is your public key. <tt>id_dsa</tt> is your private key. Only you should have access to this private key. Access to the key will grant access to GitHub in your name. For example, here is a list of files in the <tt>.ssh</tt> directory of user strom:
ls -al ~/.ssh
-rw------- 1 strom strom 668 2009-12-17 21:51 id_dsa
-rw-r--r-- 1 strom strom 603 2009-12-17 21:51 id_dsa.pub

You should only need to create a key once, unless you change to another system, or a different Sugar-on-a-Stick drive, or you think your private key was compromised. If you do it again, you must also add the new key to GitHub as described in the next section.

=== Setup Git Desktop for Windows 7 or later ===

You can either directly download and install git from [https://git-scm.com/downloads here]

Or you can set up github desktop, which gives you a GUI to do a lot of things. You can download it from [https://desktop.github.com/ here]

=== Add SSH Key ===

Log in to GitHub at http://github.com and go [https://github.com/settings/ssh here] click on 'Add Ssh Key'. Choose a title. Open your public key in a text editor, web browser, or even ''cat'' command, and then copy and paste the key into the text entry field. Click on ''Save''.

Once you do this, GitHub trusts SSH connection from your system because your system has the private key, and GitHub has the public key. You should only need to do this once, unless you change to another system.

(With ssh-keygen you can specify the name of your key file. Using this feature is not a good idea, because we haven't tested it. Keys should generally be located in <tt>~/.ssh/id_rsa.pub</tt> or <tt>~/.ssh/id_dsa.pub</tt>.)

=== Identify Yourself to Git ===

Git on your local system must know your email and name. It uses this when you commit a change, so that when you push or mail it others will know who did it.

If you do not use git on your system for any other project, you can configure git:

git config --global user.email "your_email@example.com"
git config --global user.name "Your name"

You should only need to do this once on a system.

Otherwise, configure git in the repository:

cd ${SLUG}.git
git config user.email <email-you-used-for-registering-project>
git config user.name <your-name>

You should only need to do this once in a repository.

==GitHub Workflow==

=== Create a Project ===

You will create a project if you want to create a new activity or other feature which already has no related code. In case you want to make changes to the already present code, you will have to fork the repository(see the next heading)

Log in to GitHub at http://github.com and go [https://github.com/new here]. Choose a repository name, and write a description.

=== Fork A Repository ===

A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.

Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea.

Forking a repository is simple, just go to the repository page and click the fork icon and that is it! Now you can see the repository in the list of your own repositories.

==== Propose changes to someone else's project ====

A great example of using forks to propose changes is for bug fixes. Rather than logging an issue for a bug you've found, you can:

Fork the repository.
Make the fix.
Submit a pull request to the project owner.
If the project owner likes your work, they might pull your fix into the original repository!

=== Create Local Repository (Clone) ===

Clone it from GitHub:
git clone git@github.com:username/${SLUG}.git ${SLUG}.git

Replace ''${SLUG}'' with your project slug value.

Once you do this, you will have a local repository directory named ${SLUG}.git that shares the same history of changes (if any) of the repository at Sugar Labs. You should only need to do this once for each project and system. You can do it again if you need a fresh copy that has no changes.

=== Keep your fork synced ===

You might fork a project in order to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line.

When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.

Navigate to your repository folder from the terminal and then type,
git remote -v
and press Enter. You'll now see the current configured remote repository for your fork.

Next, Type
git remote add upstream
and then paste the URL of the main repository (from where you made your fork) and press Enter. It will look like `git remote add upstream https://github.com/Someone/something-anything.git`

To verify the new upstream repository you've specified for your fork, type
git remote -v
again. You should see the URL for your fork as origin, and the URL for the original repository as upstream.

Now in order to sync with the upstream URL that you added above, you will have to fetch the branches and their respective commits from the upstream repository. Commits to master will be stored in a local branch, upstream/master.
git fetch upstream

Check out your fork's local master branch.
git checkout master

Merge the changes from upstream/master into your local master branch. This brings your fork's master branch into sync with the upstream repository, without losing your local changes.
git merge upstream/master

==== Note: ====
1. If your local branch didn't have any unique commits, Git will instead perform a "fast-forward":

2. Syncing your fork only updates your local copy of the repository. To update your fork on GitHub, you must push your changes.

=== Branches ===

When you're working on a project, you're going to have a bunch of different features or ideas in progress at any given time – some of which are ready to go, and others which are not. Branching exists to help you manage this workflow.

When you create a branch in your project, you're creating an environment where you can try out new ideas. Changes you make on a branch don't affect the master `branch`, so you're free to experiment and commit changes, safe in the knowledge that your branch won't be merged until it's ready to be reviewed by someone you're collaborating with.

It is highly recommended that all work you do, should be done in a new branch so that even in case your changes break the code(which happens quite frequently for beginners), you can always easily just remove that branch and start again, and also it helps you to work on two different features simultaneously as you can do that in separate branches.

==== Using GitHub Website ====

You can create a new branch in a repository's branch selector menu. Just start typing the name of your branch; if it doesn't exist, GitHub will offer to create it for you:

Likewise, if you go to the Branches page on your repository, you have the option of deleting a branch, provided you have appropriate access to the repository, and that there isn’t an open pull request that depends on it:

==== Using the Terminal ====

The `git branch` command lets you create, list, rename, and delete branches. It doesn’t let you switch between branches or put a forked history back together again. For this reason, git branch is tightly integrated with the `git checkout` `and git merge` commands.

List all of the branches in your repository:
git branch

Create a new branch called <branch>. This does not check out the new branch:
git branch <branch>

Delete the specified branch. This is a “safe” operation in that Git prevents you from deleting the branch if it has unmerged changes:
git branch -d <branch>

Force delete the specified branch, even if it has unmerged changes. This is the command to use if you want to permanently throw away all of the commits associated with a particular line of development:
git branch -D <branch>

Rename the current branch to <branch>:
git branch -m <branch>

Check out the specified branch, which should have already been created with git branch. This makes <existing-branch> the current branch, and updates the working directory to match:
git checkout <existing-branch>

Create and check out <new-branch>. The -b option is a convenience flag that tells Git to run git branch <new-branch> before running git checkout <new-branch>:
git checkout -b <new-branch>

Same as the above invocation, but base the new branch off of <existing-branch> instead of the current branch:
git checkout -b <new-branch> <existing-branch>

Merge the specified branch into the current branch. Git will determine the merge algorithm automatically:
git merge <branch>

Merge the specified branch into the current branch, but always generate a merge commit (even if it was a fast-forward merge). This is useful for documenting all merges that occur in your repository:
git merge --no-ff <branch>

==== Tip ====

There's only one rule: anything in the master branch is always deployable.

Because of this, it's extremely important that your new branch is created off of master when working on a feature or a fix. Your branch name should be descriptive

For detailed explanation, look at the [https://www.atlassian.com/git/tutorials/using-branches/git-merge '''atlassian git tutorial''']

=== Commits ===

Once your branch has been created, it's time to start making changes. Whenever you add, edit, or delete a file, you're making a commit, and adding them to your branch. This process of adding commits keeps track of your progress as you work on a feature branch.

Commits also create a transparent history of your work that others can follow to understand what you've done and why. Each commit has an associated commit message, which is a description explaining why a particular change was made. Furthermore, each commit is considered a separate unit of change. This lets you roll back changes if a bug is found, or if you decide to head in a different direction.

In your local repository, find out from git what files you changed:
git status

Add any files that are new or changed:
git add <file path>

or too add all the files
git add --all

Tell git to collect the changes into a commit:
git commit

You should do this for every meaningful set of changes you make.

''Note'' <code> git commit </code> ''commits your changes to your local repository only.''

=== Request Review ===

Before you publish changes widely, you can ask others to review your work and comment on it.

git format-patch -1

or

git send-email

You may do this for every set of changes you make.

=== Push Changes ===

Your changes have to be pushed from your local repository to the repository at github so that others can see them there.

git push

You must do this for every set of changes you make, when you want to synchronise with other developers or prepare for a release.

=== Pull Request ===

In order to request the repository's owner to consider the changes that you made in your repository and include them in the main code, you will need to make a pull request. In order to do this, just open up your repository page, `https://github.com/yourUserName/RepoName`, now you will a line just above the contents saying something like `This branch is 1 commit ahead of walterbender:master.` and you will also thus be able to see a button to create a New Pull Request for the same, then you can review the changes made and the commits to be added in that request and also a message box for the message you would want others to read, describing the changes you made. Then you can proceed to successfully creating a pull request, which will then be reviewed by others. And you can discuss on the very same page regarding whatever needs to be done. And if all is perfect, your pull request will be merged into the main code!

== Other Notes ==

=== Tags ===

alsroot taught me about another git feature: tags

git tag -m "Release 36" v36 HEAD
git push --tags

[[Category:Activity Team]]
[[Category:HowTo]]

Activity Team/Git Tutorial

2015-12-12T17:32:36Z

Daksh Shah:

<noinclude>{{TeamHeader|Activity Team}}</noinclude>

== GitHub ==

Sugar Labs uses GitHub as its primary server for git repositories. While you are welcome to use other servers, it is on GitHub where you will find the master branches of the core modules and core activities.

Getting started with GitHub

You will learn to do the following:
* Create an account, which you do once.
* Create and add an SSH key, which you do once or if you change system.
* Create a project, a local repository, and identify yourself to git, which you do once per project.
* Add source files, change existing source files, commit changes, push changes, and pull changes, which you do regularly.

=== Create an Account ===

Create an account [https://github.com/join here]

=== Create SSH Key on Windows ===

To create an SSH Key on Windows, download the latest [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] [http://the.earth.li/~sgtatham/putty/latest/x86/putty-installer.exe installer].

* Run the puttygen.exe utility to generate a pair of private/public keys.
* Click on the ''Generate'' button (Make sure SSH-2 RSA parameter is checked)
* Move the mouse around to generate your key.
* Once you have accumulated enough "heat", the application will generate your key pair.
* Make sure you enter a lengthy passphrase in the Key passphrase field and confirm it in the Confirm passphrase field.
* Click on the Save private key button to save your private key in a file.

Congratulations! With your mouse, select the content of the box labelled Public key and press Control-C to copy your public SSH key.
This key can now be used on GitHub to access Git on Windows. Good luck!

=== Create SSH Key on GNU/Linux ===

Skip this section if you already have an SSH key in <tt>.ssh</tt> directory that you trust.

(An easy-to-read tutorial for generating an ssh key can be found [https://help.github.com/articles/generating-ssh-keys here].)

To create a key use ''ssh-keygen''. The following command will create a “dsa” key:
ssh-keygen -t dsa

For creating a “rsa” key use:
ssh-keygen -t rsa

The key will be stored as two files in the hidden <tt>.ssh</tt> directory.

<tt>id_dsa.pub</tt> is your public key. <tt>id_dsa</tt> is your private key. Only you should have access to this private key. Access to the key will grant access to GitHub in your name. For example, here is a list of files in the <tt>.ssh</tt> directory of user strom:
ls -al ~/.ssh
-rw------- 1 strom strom 668 2009-12-17 21:51 id_dsa
-rw-r--r-- 1 strom strom 603 2009-12-17 21:51 id_dsa.pub

You should only need to create a key once, unless you change to another system, or a different Sugar-on-a-Stick drive, or you think your private key was compromised. If you do it again, you must also add the new key to GitHub as described in the next section.

=== Setup Git Desktop for Windows 7 or later ===

You can either directly download and install git from [https://git-scm.com/downloads here]

Or you can set up github desktop, which gives you a GUI to do a lot of things. You can download it from [https://desktop.github.com/ here]

=== Add SSH Key ===

Log in to GitHub at http://github.com and go [https://github.com/settings/ssh here] click on 'Add Ssh Key'. Choose a title. Open your public key in a text editor, web browser, or even ''cat'' command, and then copy and paste the key into the text entry field. Click on ''Save''.

Once you do this, GitHub trusts SSH connection from your system because your system has the private key, and GitHub has the public key. You should only need to do this once, unless you change to another system.

(With ssh-keygen you can specify the name of your key file. Using this feature is not a good idea, because we haven't tested it. Keys should generally be located in <tt>~/.ssh/id_rsa.pub</tt> or <tt>~/.ssh/id_dsa.pub</tt>.)

=== Identify Yourself to Git ===

Git on your local system must know your email and name. It uses this when you commit a change, so that when you push or mail it others will know who did it.

If you do not use git on your system for any other project, you can configure git:

git config --global user.email "your_email@example.com"
git config --global user.name "Your name"

You should only need to do this once on a system.

Otherwise, configure git in the repository:

cd ${SLUG}.git
git config user.email <email-you-used-for-registering-project>
git config user.name <your-name>

You should only need to do this once in a repository.

==GitHub Workflow==

=== Create a Project ===

You will create a project if you want to create a new activity or other feature which already has no related code. In case you want to make changes to the already present code, you will have to fork the repository(see the next heading)

Log in to GitHub at http://github.com and go [https://github.com/new here]. Choose a repository name, and write a description.

=== Fork A Repository ===

A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.

Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea.

Forking a repository is simple, just go to the repository page and click the fork icon and that is it! Now you can see the repository in the list of your own repositories.

==== Propose changes to someone else's project ====

A great example of using forks to propose changes is for bug fixes. Rather than logging an issue for a bug you've found, you can:

Fork the repository.
Make the fix.
Submit a pull request to the project owner.
If the project owner likes your work, they might pull your fix into the original repository!

=== Create Local Repository (Clone) ===

Clone it from GitHub:
git clone git@github.com:username/${SLUG}.git ${SLUG}.git

Replace ''${SLUG}'' with your project slug value.

Once you do this, you will have a local repository directory named ${SLUG}.git that shares the same history of changes (if any) of the repository at Sugar Labs. You should only need to do this once for each project and system. You can do it again if you need a fresh copy that has no changes.

=== Keep your fork synced ===

You might fork a project in order to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line.

When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.

Navigate to your repository folder from the terminal and then type,
git remote -v
and press Enter. You'll now see the current configured remote repository for your fork.

Next, Type
git remote add upstream
and then paste the URL of the main repository (from where you made your fork) and press Enter. It will look like `git remote add upstream https://github.com/Someone/something-anything.git`

To verify the new upstream repository you've specified for your fork, type
git remote -v
again. You should see the URL for your fork as origin, and the URL for the original repository as upstream.

Now in order to sync with the upstream URL that you added above, you will have to fetch the branches and their respective commits from the upstream repository. Commits to master will be stored in a local branch, upstream/master.
git fetch upstream

Check out your fork's local master branch.
git checkout master

Merge the changes from upstream/master into your local master branch. This brings your fork's master branch into sync with the upstream repository, without losing your local changes.
git merge upstream/master

==== Note: ====
1. If your local branch didn't have any unique commits, Git will instead perform a "fast-forward":

2. Syncing your fork only updates your local copy of the repository. To update your fork on GitHub, you must push your changes.

=== Branches ===

When you're working on a project, you're going to have a bunch of different features or ideas in progress at any given time – some of which are ready to go, and others which are not. Branching exists to help you manage this workflow.

When you create a branch in your project, you're creating an environment where you can try out new ideas. Changes you make on a branch don't affect the master `branch`, so you're free to experiment and commit changes, safe in the knowledge that your branch won't be merged until it's ready to be reviewed by someone you're collaborating with.

==== Tip ====

There's only one rule: anything in the master branch is always deployable.

Because of this, it's extremely important that your new branch is created off of master when working on a feature or a fix. Your branch name should be descriptive

=== Commits ===

Once your branch has been created, it's time to start making changes. Whenever you add, edit, or delete a file, you're making a commit, and adding them to your branch. This process of adding commits keeps track of your progress as you work on a feature branch.

Commits also create a transparent history of your work that others can follow to understand what you've done and why. Each commit has an associated commit message, which is a description explaining why a particular change was made. Furthermore, each commit is considered a separate unit of change. This lets you roll back changes if a bug is found, or if you decide to head in a different direction.

In your local repository, find out from git what files you changed:
git status

Add any files that are new or changed:
git add <file path>

or too add all the files
git add --all

Tell git to collect the changes into a commit:
git commit

You should do this for every meaningful set of changes you make.

''Note'' <code> git commit </code> ''commits your changes to your local repository only.''

=== Request Review ===

Before you publish changes widely, you can ask others to review your work and comment on it.

git format-patch -1

or

git send-email

You may do this for every set of changes you make.

=== Push Changes ===

Your changes have to be pushed from your local repository to the repository at github so that others can see them there.

git push

You must do this for every set of changes you make, when you want to synchronise with other developers or prepare for a release.

=== Pull Request ===

In order to request the repository's owner to consider the changes that you made in your repository and include them in the main code, you will need to make a pull request. In order to do this, just open up your repository page, `https://github.com/yourUserName/RepoName`, now you will a line just above the contents saying something like `This branch is 1 commit ahead of walterbender:master.` and you will also thus be able to see a button to create a New Pull Request for the same, then you can review the changes made and the commits to be added in that request and also a message box for the message you would want others to read, describing the changes you made. Then you can proceed to successfully creating a pull request, which will then be reviewed by others. And you can discuss on the very same page regarding whatever needs to be done. And if all is perfect, your pull request will be merged into the main code!

== Other Notes ==

=== Tags ===

alsroot taught me about another git feature: tags

git tag -m "Release 36" v36 HEAD
git push --tags

[[Category:Activity Team]]
[[Category:HowTo]]

Activity Team/Git Tutorial

2015-12-12T17:22:33Z

Daksh Shah: Adding the GitHub Workflow and updated the page :)

<noinclude>{{TeamHeader|Activity Team}}</noinclude>

== GitHub ==

Sugar Labs uses GitHub as its primary server for git repositories. While you are welcome to use other servers, it is on GitHub where you will find the master branches of the core modules and core activities.

Getting started with GitHub

You will learn to do the following:
* Create an account, which you do once.
* Create and add an SSH key, which you do once or if you change system.
* Create a project, a local repository, and identify yourself to git, which you do once per project.
* Add source files, change existing source files, commit changes, push changes, and pull changes, which you do regularly.

=== Create an Account ===

Create an account [https://github.com/join here]

=== Create SSH Key on Windows ===

To create an SSH Key on Windows, download the latest [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] [http://the.earth.li/~sgtatham/putty/latest/x86/putty-installer.exe installer].

* Run the puttygen.exe utility to generate a pair of private/public keys.
* Click on the ''Generate'' button (Make sure SSH-2 RSA parameter is checked)
* Move the mouse around to generate your key.
* Once you have accumulated enough "heat", the application will generate your key pair.
* Make sure you enter a lengthy passphrase in the Key passphrase field and confirm it in the Confirm passphrase field.
* Click on the Save private key button to save your private key in a file.

Congratulations! With your mouse, select the content of the box labelled Public key and press Control-C to copy your public SSH key.
This key can now be used on GitHub to access Git on Windows. Good luck!

=== Create SSH Key on GNU/Linux ===

Skip this section if you already have an SSH key in <tt>.ssh</tt> directory that you trust.

(An easy-to-read tutorial for generating an ssh key can be found [https://help.github.com/articles/generating-ssh-keys here].)

To create a key use ''ssh-keygen''. The following command will create a “dsa” key:
ssh-keygen -t dsa

For creating a “rsa” key use:
ssh-keygen -t rsa

The key will be stored as two files in the hidden <tt>.ssh</tt> directory.

<tt>id_dsa.pub</tt> is your public key. <tt>id_dsa</tt> is your private key. Only you should have access to this private key. Access to the key will grant access to GitHub in your name. For example, here is a list of files in the <tt>.ssh</tt> directory of user strom:
ls -al ~/.ssh
-rw------- 1 strom strom 668 2009-12-17 21:51 id_dsa
-rw-r--r-- 1 strom strom 603 2009-12-17 21:51 id_dsa.pub

You should only need to create a key once, unless you change to another system, or a different Sugar-on-a-Stick drive, or you think your private key was compromised. If you do it again, you must also add the new key to GitHub as described in the next section.

=== Setup Git for Windows 8 ===

GitHub is one way you can set up Git on Windows 8. It can be downloaded from [http://github-windows.s3.amazonaws.com/GitHubSetup.exe here]

Once downloaded and installed, Git Shell can be used to execute Git commands.

=== Add SSH Key ===

Log in to GitHub at http://github.com and go [https://github.com/settings/ssh here] click on 'Add Ssh Key'. Choose a title. Open your public key in a text editor, web browser, or even ''cat'' command, and then copy and paste the key into the text entry field. Click on ''Save''.

Once you do this, GitHub trusts SSH connection from your system because your system has the private key, and GitHub has the public key. You should only need to do this once, unless you change to another system.

(With ssh-keygen you can specify the name of your key file. Using this feature is not a good idea, because we haven't tested it. Keys should generally be located in <tt>~/.ssh/id_rsa.pub</tt> or <tt>~/.ssh/id_dsa.pub</tt>.)

=== Identify Yourself to Git ===

Git on your local system must know your email and name. It uses this when you commit a change, so that when you push or mail it others will know who did it.

If you do not use git on your system for any other project, you can configure git:

git config -f ~/.gitconfig user.email <email-you-used-for-registering-project>
git config -f ~/.gitconfig user.name <your-name>

You should only need to do this once on a system.

Otherwise, configure git in the repository:

cd ${SLUG}.git
git config user.email <email-you-used-for-registering-project>
git config user.name <your-name>

You should only need to do this once in a repository.

==GitHub Workflow==

=== Create a Project ===

You will create a project if you want to create a new activity or other feature which already has no related code. In case you want to make changes to the already present code, you will have to fork the repository(see the next heading)

Log in to GitHub at http://github.com and go [https://github.com/new here]. Choose a repository name, and write a description.

=== Fork A Repository ===

A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.

Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea.

Forking a repository is simple, just go to the repository page and click the fork icon and that is it! Now you can see the repository in the list of your own repositories.

==== Propose changes to someone else's project ====

A great example of using forks to propose changes is for bug fixes. Rather than logging an issue for a bug you've found, you can:

Fork the repository.
Make the fix.
Submit a pull request to the project owner.
If the project owner likes your work, they might pull your fix into the original repository!

=== Create Local Repository (Clone) ===

Clone it from GitHub:
git clone git@github.com:username/${SLUG}.git ${SLUG}.git

Replace ''${SLUG}'' with your project slug value.

Once you do this, you will have a local repository directory named ${SLUG}.git that shares the same history of changes (if any) of the repository at Sugar Labs. You should only need to do this once for each project and system. You can do it again if you need a fresh copy that has no changes.

=== Keep your fork synced ===

You might fork a project in order to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line.

When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.

Navigate to your repository folder from the terminal and then type,
git remote -v
and press Enter. You'll now see the current configured remote repository for your fork.

Next, Type
git remote add upstream
and then paste the URL of the main repository (from where you made your fork) and press Enter. It will look like `git remote add upstream https://github.com/Someone/something-anything.git`

To verify the new upstream repository you've specified for your fork, type
git remote -v
again. You should see the URL for your fork as origin, and the URL for the original repository as upstream.

Now in order to sync with the upstream URL that you added above, you will have to fetch the branches and their respective commits from the upstream repository. Commits to master will be stored in a local branch, upstream/master.
git fetch upstream

Check out your fork's local master branch.
git checkout master

Merge the changes from upstream/master into your local master branch. This brings your fork's master branch into sync with the upstream repository, without losing your local changes.
git merge upstream/master

==== Note: ====
1. If your local branch didn't have any unique commits, Git will instead perform a "fast-forward":

2. Syncing your fork only updates your local copy of the repository. To update your fork on GitHub, you must push your changes.

=== Branches ===

When you're working on a project, you're going to have a bunch of different features or ideas in progress at any given time – some of which are ready to go, and others which are not. Branching exists to help you manage this workflow.

When you create a branch in your project, you're creating an environment where you can try out new ideas. Changes you make on a branch don't affect the master `branch`, so you're free to experiment and commit changes, safe in the knowledge that your branch won't be merged until it's ready to be reviewed by someone you're collaborating with.

==== Tip ====

There's only one rule: anything in the master branch is always deployable.

Because of this, it's extremely important that your new branch is created off of master when working on a feature or a fix. Your branch name should be descriptive

=== Commits ===

Once your branch has been created, it's time to start making changes. Whenever you add, edit, or delete a file, you're making a commit, and adding them to your branch. This process of adding commits keeps track of your progress as you work on a feature branch.

Commits also create a transparent history of your work that others can follow to understand what you've done and why. Each commit has an associated commit message, which is a description explaining why a particular change was made. Furthermore, each commit is considered a separate unit of change. This lets you roll back changes if a bug is found, or if you decide to head in a different direction.

In your local repository, find out from git what files you changed:
git status

Add any files that are new or changed:
git add <file path>

or too add all the files
git add --all

Tell git to collect the changes into a commit:
git commit

You should do this for every meaningful set of changes you make.

''Note'' <code> git commit </code> ''commits your changes to your local repository only.''

=== Request Review ===

Before you publish changes widely, you can ask others to review your work and comment on it.

git format-patch -1

or

git send-email

You may do this for every set of changes you make.

=== Push Changes ===

Your changes have to be pushed from your local repository to the repository at github so that others can see them there.

git push

You must do this for every set of changes you make, when you want to synchronise with other developers or prepare for a release.

=== Pull Request ===

In order to request the repository's owner to consider the changes that you made in your repository and include them in the main code, you will need to make a pull request. In order to do this, just open up your repository page, `https://github.com/yourUserName/RepoName`, now you will a line just above the contents saying something like `This branch is 1 commit ahead of walterbender:master.` and you will also thus be able to see a button to create a New Pull Request for the same, then you can review the changes made and the commits to be added in that request and also a message box for the message you would want others to read, describing the changes you made. Then you can proceed to successfully creating a pull request, which will then be reviewed by others. And you can discuss on the very same page regarding whatever needs to be done. And if all is perfect, your pull request will be merged into the main code!

== Other Notes ==

=== Tags ===

alsroot taught me about another git feature: tags

git tag -m "Release 36" v36 HEAD
git push --tags

[[Category:Activity Team]]
[[Category:HowTo]]

User:Daksh Shah

2015-12-10T22:20:41Z

Daksh Shah: /* Google Code-In 2015 */

== Google Code-In 2015 ==
{| class="wikitable"
|-
! Task
! Task Page Link
|-
| Install the Sugarizer Client development environment
| https://codein.withgoogle.com/dashboard/task-instances/5091163702820864/
|-
| Git Introduction
| https://codein.withgoogle.com/dashboard/task-instances/5788080128655360/
|-
| Port Manage homeviews activity to GSettings
| https://codein.withgoogle.com/dashboard/task-instances/4618919532822528/
|-
| Write: Word count
| https://codein.withgoogle.com/dashboard/task-instances/5210754919694336/
|-
| Music Blocks: Redesign and improve header icons
| https://codein.withgoogle.com/dashboard/task-instances/5092069370494976/
|}

===Icons for Music Blocks===

Preview:

[[Image:Preview_of_icons_musicblocks.png|900px]]

Icons:

[[Image:Clear-button.svg]][[Image:collapse.svg]][[Image:expand.svg]][[Image:fast-button.svg]][[Image:fast-button-2.svg]][[Image:help-button.svg]][[Image:Hide.svg]][[Image:maximize.svg]][[Image:minimize.svg]][[Image:Show.svg]][[Image:sidebar.svg]][[Image:sidebar-2.svg]][[Image:sidebar-maximize.svg]][[Image:slow-button.svg]][[Image:slow-button-2.svg]][[Image:slow-button-without-play.svg]][[Image:slow-music-button.svg]][[Image:slow-music-button-2.svg]][[Image:slow-music-button-3.svg]][[Image:slow-music-button-without-play.svg]][[Image:step-button.svg]][[Image:step-button-2.svg]][[Image:step-music-button.svg]][[Image:stop-turtle-button.svg]][[Image:stop-turtle-button-black.svg]]

User:Daksh Shah

2015-12-10T22:17:41Z

Daksh Shah: /* Icons for Music Blocks */

== Google Code-In 2015 ==
{| class="wikitable"
|-
! Task
! Task Page Link
|-
| Install the Sugarizer Client development environment
| https://codein.withgoogle.com/dashboard/task-instances/5091163702820864/
|-
| Git Introduction
| https://codein.withgoogle.com/dashboard/task-instances/5788080128655360/
|}
===Icons for Music Blocks===

Preview:

[[Image:Preview_of_icons_musicblocks.png|900px]]

Icons:

[[Image:Clear-button.svg]][[Image:collapse.svg]][[Image:expand.svg]][[Image:fast-button.svg]][[Image:fast-button-2.svg]][[Image:help-button.svg]][[Image:Hide.svg]][[Image:maximize.svg]][[Image:minimize.svg]][[Image:Show.svg]][[Image:sidebar.svg]][[Image:sidebar-2.svg]][[Image:sidebar-maximize.svg]][[Image:slow-button.svg]][[Image:slow-button-2.svg]][[Image:slow-button-without-play.svg]][[Image:slow-music-button.svg]][[Image:slow-music-button-2.svg]][[Image:slow-music-button-3.svg]][[Image:slow-music-button-without-play.svg]][[Image:step-button.svg]][[Image:step-button-2.svg]][[Image:step-music-button.svg]][[Image:stop-turtle-button.svg]][[Image:stop-turtle-button-black.svg]]

User:Daksh Shah

2015-12-10T22:13:49Z

Daksh Shah: /* Icons for Music Blocks */

== Google Code-In 2015 ==
{| class="wikitable"
|-
! Task
! Task Page Link
|-
| Install the Sugarizer Client development environment
| https://codein.withgoogle.com/dashboard/task-instances/5091163702820864/
|-
| Git Introduction
| https://codein.withgoogle.com/dashboard/task-instances/5788080128655360/
|}
===Icons for Music Blocks===

Preview:

[[Image:Preview_of_icons_musicblocks.png]]

Icons:

[[Image:clear-button]][[Image:collapse.svg]][[Image:expand.svg]][[Image:fast-button.svg]][[Image:fast-button-2.svg]][[Image:help-button.svg]][[Image:Hide.svg]][[Image:maximize.svg]][[Image:minimize.svg]][[Image:Show.svg]][[Image:sidebar.svg]][[Image:sidebar-maximize-2.svg]][[Image:sidebar-maximize.svg]][[Image:slow-button.svg]][[Image:slow-button-2.svg]][[Image:slow-button-without-play.svg]][[Image:slow-music-button.svg]][[Image:slow-music-button-2.svg]][[Image:slow-music-button-3.svg]][[Image:slow-music-button-without-play.svg]][[Image:step-button.svg]][[Image:step-button-2.svg]][[Image:step-music-button.svg]][[Image:stop-turtle-button.svg]][[Image:stop-turtle-button-black.svg]]

User:Daksh Shah

2015-12-10T22:06:54Z

Daksh Shah: /* Icons for Music Blocks */

User:Daksh Shah

2015-12-10T22:03:06Z

Daksh Shah: /* Icons for Music Blocks */

User:Daksh Shah

2015-12-10T21:59:42Z

Daksh Shah:

File:Slow-music-button-without-play.svg

2015-12-10T21:52:51Z

Daksh Shah: Daksh Shah uploaded a new version of File:Slow-music-button-without-play.svg