Sugar Labs - User contributions [en]

File:Clock-nice.png

2018-01-20T08:13:02Z

Emilyo11: Emilyo11 uploaded a new version of File:Clock-nice.png

User:Emilyo11

2018-01-20T08:12:00Z

Emilyo11: Hello World

Hello World

File:Clock-nice.png

2018-01-20T08:08:23Z

Emilyo11: Emilyo11 uploaded a new version of File:Clock-nice.png

Features/GTK3/Porting

2017-12-23T07:08:40Z

Emilyo11: edit grammar

=Porting an existing activity to GTK3=
This is a guide to porting an existing activity from GTK2 to [http://developer.gnome.org/gtk3/stable/ GTK3]. It also shows the changes to use the new Sugar toolkit that also now uses [[Features/GTK3|GTK3]]. This guide uses the [http://git.sugarlabs.org/hello-world hello-world] activity as a simple example.

There is another guide written from scratch that uses this one as reference. It was done porting GetBooks Activity [[Features/GTK3/Porting/GetBooks]]

If you would like to reference other examples of GTK3 port:
* [https://github.com/sugarlabs/biorhythm/commit/c16de3b70cce2cc6f8af933e2b062c844a47c144/ Biorhythm]

==Preparation==
Before you start porting your activity you are encouraged to branch off a stable branch. This will allow you to keep on doing stable releases on the stable branch and new releases on the master branch. We highly recommend that you use the 'sugar-0.94' as the stable branch name because this will keep the repositories consistent and eases the development work. Let's step through this with a real life example:

The latest release of hello-world was version 3 (commit 04fb9beb708f1078aae93995da3ec06bac7aa433). We want to branch off at that point. If you did not do any changes after the last stable commit simply create a branch with:
git branch sugar-0.94

If you have already made commits after that, you need to go to that commit first and create a branch at that specific point in our case commit 04fb9beb708f1078aae93995da3ec06bac7aa433, there is a command to do that in one go:
git checkout -b sugar-0.94 04fb9beb708f1078aae93995da3ec06bac7aa433

In both cases this has created a local branch, as you can see by running 'git branch'; you should see the following (if you did the second command you will have sugar-0.94 already selected):

<pre>
[erikos@T61 helloworld]$ git branch
* master
sugar-0.94
</pre>

The 'sugar-0.94' branch is only available locally, as you can see by running 'git branch -r' which shows the remote branches:

<pre>
[erikos@T61 helloworld]$ git branch -r
origin/HEAD -> origin/master
origin/master
origin/sucrose-0.84
</pre>

The only branch available besides the master branch is the 'sucrose-0.84' branch. Let's push now our new branch to the remote repository to make it available for others:
<pre>
git push origin sugar-0.94
</pre>

The branch is now listed as a remote branch. You can verify as well on your [http://git.sugarlabs.org/hello-world/mainline gitorious page].
<pre>
[erikos@T61 helloworld]$ git branch -r
origin/HEAD -> origin/master
origin/master
origin/sucrose-0.84
origin/sugar-0.94
</pre>

You can switch now between those branches using 'git checkout <branch>'. And you can use 'git branch' to see which branch you are on (the one with the * before is the branch you are currently on).
<pre>
git checkout sugar-0.94
git checkout master
</pre>

==Cleanup, adopt to API changes in sugar-toolkit-gtk3 ==
''This should be done only on the master branch''! In the new sugar-toolkit-gtk3 we have removed old API, you should adjust your activity accordingly:
* the keep button has been removed completely
* the old-style toolbar has been removed
* do not use set_toolbox anymore use set_toolbar_box instead (see in [http://git.sugarlabs.org/~walter/abacus/walter-cairo/commit/6871dd340a89ade3b5361457e1bd1d58276a8efc Abacus])
* remove import of deprecated ActivityToolbox (see [http://git.sugarlabs.org/hello-world/mainline/commit/22060a3063b2d6fd38d6b1cd8d44946170255af3 hello-world])
* support for 'service_name' and 'class' has been removed from the activity.info make sure you are using: 'bundle_id' instead of 'service_name' and 'exec' instead of 'class' (see in [http://git.sugarlabs.org/record/mainline/commit/6e8968c71e474e2d8d86886badf5cf7d70217dc5 Record])

==Port the activity from GTK2 to GTK3==
To start, change the importing instruction for GTK from
import gtk
to
from gi.repository import Gtk

Remember to import the gi module and specify the Gtk version as 3.0 as well.
<pre>
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
</pre>

Then you have to change each call that involves Gtk, for example creating a button will look now like this:
button = Gtk.Button()

A simple hello world program in GTK3 looks like this:
<pre>
from gi.repository import Gtk

def _destroy_cb(widget, data=None):
Gtk.main_quit()

w = Gtk.Window()
w.connect("destroy", _destroy_cb)
label = Gtk.Label('Hello World!')
w.add(label)
w.show_all()

Gtk.main()
</pre>

For porting your activity you do have to change your calls for accessing widgets and services in the new GTK3 sugar-toolkit as well. The new namespace is called [https://developer.sugarlabs.org/sugar3/ sugar3], trying to reflect that GTK3 is the underlying technology. For example the import of the base activity class has to be changed from
from sugar.activity import activity
to
from sugar3.activity import activity

Make sure you change the setup.py in your activity to point to the new toolkit as well:
from sugar3.activity import bundlebuilder

The changes that were needed to port the hello-world activity can be seen in [http://git.sugarlabs.org/hello-world/mainline/commit/508e1c518b56cbde5508e560c8a2ff38a3518583 this commit].

Ok, let's do these changes now for your activity. Make sure you are in your master branch using the 'git branch' command (the master branch should have a '*' before it). Make your changes, commit them ('git commit -a') and push them to the remote repository ('git push origin master').

====Simple example on creating a toolbar====
One of Sugar's activity most unique user interface includes the toolbar. In order to reference the relevant modules and graphics, the sugar3 library has to be imported. These are the relevant ones that would enable us to create a simple toolbar containing the activity button and the stop button.
<pre>
from sugar3.activity import activity
from sugar3.graphics.toolbarbox import ToolbarBox
from sugar3.activity.widgets import ActivityToolbarButton
from sugar3.activity.widgets import StopButton
from sugar3.graphics.toolbarbox import ToolbarButton
from sugar3.graphics import style
</pre>

Since the ActivityToolbar() module has been deprecated, the toolbar can now be called using
ToolbarBox()
Then, from the ToolbarBox(), include the ActivityButton and StopButton. In order for the StopButton to be align to the right as per Sugar activity interface, a separator has to be included as well.

<pre>
toolbar_box = ToolbarBox()

activity_button = ActivityToolbarButton(self)
toolbar_box.toolbar.insert(activity_button, 0)
activity_button.show()

separator = Gtk.SeparatorToolItem()
separator.props.draw = False
separator.set_expand(True)
toolbar_box.toolbar.insert(separator, -1)
separator.show()

stop_button = StopButton(self)
toolbar_box.toolbar.insert(stop_button, -1)
stop_button.show()
self.set_toolbar_box(toolbar_box)
toolbar_box.show()
</pre>

===Tools===
There are tools to help you do the porting. There is a script in the pygobject repository for porting called [http://git.gnome.org/browse/pygobject/tree/pygi-convert.sh pygi-convert.sh], more info about the script can be found in [http://live.gnome.org/PyGObject/IntrospectionPorting the PyGObject Introspection Porting guide].

Here is a script to automate the rename of the imports '''sugar''' to '''sugar3''': [http://dev.laptop.org/~manuq/sugar-convert.sh sugar-convert.sh].

If you are having trouble finding how a particular GTK class/method/constant has been named in PyGI, run [http://dev.laptop.org/~dsd/20110806/pygi-enumerate.py pygi-enumerate.py] and grep the output. (this app lists all identified methods and constants). Usage example:

<pre>
$ python pygi-enumerate.py | grep get_selection
Gtk.AccelLabel.get_selection_bounds() (instance method)
Gtk.Editable.get_selection_bounds() (instance method)
Gtk.Entry.get_selection_bounds() (instance method)
Gtk.IconView.get_selection_mode() (instance method)
Gtk.Label.get_selection_bounds() (instance method)
Gtk.SelectionData.get_selection() (instance method)
Gtk.SpinButton.get_selection_bounds() (instance method)
Gtk.TextBuffer.get_selection_bound() (instance method)
Gtk.TextBuffer.get_selection_bounds() (instance method)
Gtk.TreeView.get_selection() (instance method)
</pre>

=== Constructor considerations ===

With PyGI it is possible to use Python-like constructors, or "new" functions e.g. the following are (usually) equivalent:
label = Gtk.Button()
label = Gtk.Button.new()

However, the first form is preferred: it is more Python-like. Internally, the difference is that Gtk.Label.new() translates to a call to gtk_label_new(), whereas Gtk.Label() (the preferred form) will directly construct an instance of GtkLabel at the GObject level.

If the constructor takes parameters, they '''must''' be named. The parameters correspond to GObject properties in the API documentation which are usually marked as "Construct". For example, the following code will not work:

expander = Gtk.Expander("my expander")

The (confusing) error is:
TypeError: GObject.__init__() takes exactly 0 arguments (1 given)

The solution is to go to the [http://developer.gnome.org/gtk3/3.2/GtkExpander.html#GtkExpander.properties GtkExpander API documentation] and find the appropriate property that we wish to set. In this case it is <b>label</b> (which is a Construct property, further increasing our confidence of success), so the code should be:

expander = Gtk.Expander(label="my expander")

Combining the two points above, if you wish to call a construct-like function such as gtk_button_new_with_label(), you do have the option of calling Gtk.Button.new_with_label(), however if we check the [http://developer.gnome.org/gtk3/3.2/GtkButton.html#GtkButton.properties GtkButton properties] we see one called "label" which is equivalent. Therefore gtk_button_new_with_label("foo") should be called as:
button = Gtk.Button(label="foo")

=== HBox, VBox, pack_start and pack_end ===

GtkHBox and GtkVBox, commonly used containers in GTK2 code, have pack_start and pack_end methods. These take 4 parameters:
# The widget to pack into the container
# '''expand''': Whether the child should receive extra space when the container grows (default True)
# '''fill''': True if space given to child by the expand option is actually allocated to child, rather than just padding it. This parameter has no effect if expand is set to False. A child is always allocated the full height of a gtk.HBox and the full width of a gtk.VBox. This option affects the other dimension. (default True)
# '''padding''': extra space in pixels to put between child and its neighbor (default 0)

In PyGTK, the expand, fill and padding parameters were optional: if unspecified, the default values above were used. In PyGI, these parameters are '''not''' optional: all 4 must be specified. Hence the rules for adding in the extra parameters are:

# If '''expand''' was not set, use value True
# If '''fill''' was not set, use value True. (however, if expand is False, this parameter gets ignored so False is an equally acceptable option when expand=False)
# If '''padding''' was not set, use value 0.

These parameters can be specified either as positional arguments or as named keyword arguments, however all 4 must always be specified. Some developers prefer keyword arguments, arguing that the following:
<pre>box.pack_start(widget, expand=True, fill=False, padding=4)</pre>
is much more readable than:
<pre>box.pack_start(widget, True, False, 4)</pre>

However, these functions are called extremely often; any mildly seasoned GTK developer will have memorized the order and meaning of the parameters. Some developers therefore prefer to avoid the extra work of dropping in hundreds of keyword arguments throughout the code and just use the positional ones. This is really up to you.

If you are using pack_start with the default values (expand=True, fill=True and padding=0), you can avoid using pack_start (and the parameter pain that it brings with it) by just using .add for some added cleanliness, e.g.
<pre>box.pack_start(widget, True, True, 0)</pre>
can be replaced with:
<pre>box.add(widget)</pre>

This is as far as you need to go for now. However, in GTK3, GtkVBox and GtkHBox have been deprecated, which means they might be removed in GTK3. The replacement is to use GtkBox directly, and you may wish to make this change now. e.g.:
<pre>vbox = Gtk.Box(orientation=Gtk.Orientation.VERTICAL)</pre>
<pre>hbox = Gtk.Box(orientation=Gtk.Orientation.HORIZONTAL, homogeneous=True, spacing=8)</pre>
However, it must be noted that if GtkBox is used directly (instead of using GtkHBox/GtkVBox), the default value of '''expand''' is now '''False'''. The implications of this are:
# You need to check your .add() calls, as previously they would behave as pack_start with expand=True, but now they will behave as expand=False (you need to change them to use pack_start with expand=True to retain the old behaviour)
# Every single pack_start call that has expand=False and padding=0 (and any value of fill) can be converted to .add() for cleanliness

=== GtkAlignment considerations ===

In PyGTK, the gtk.Alignment constructor takes four optional parameters:
# xalign: the fraction of horizontal free space to the left of the child widget. Ranges from 0.0 to 1.0. Default value 0.0.
# yalign: the fraction of vertical free space above the child widget. Ranges from 0.0 to 1.0. Default value 0.0.
# xscale: the fraction of horizontal free space that the child widget absorbs, from 0.0 to 1.0. Default value 0.0.
# yscale: the fraction of vertical free space that the child widget absorbs, from 0.0 to 1.0. Default value 0.0

In PyGI/GTK3, these parameters are still optional when used in the Gtk.Alignment constructor (as keyword arguments, as explained above). However, the default values have changed. They are now:
# xalign: default value 0.5
# yalign: default value 0.5
# xscale: default value 1
# yscale: default value 1

If your code was relying on the default value of 0 for any of these parameters in PyGTK, you will now need to explicitly specify that in your constructor. Similarly, if you were previously using construction parameters to select the now-default values, those parameters can be dropped.

Additionally, PyGTK accepted these construction parameters as positional arguments. As explained above, they must now be converted to keyword arguments.

=== Gdk ===
Previously, gdk was an attribute of the gtk module, which means that it can be called through gtk. For example, if we want to use color_parse():
gtk.gdk.color_parse(color)
However, what we have to do now is:
from gi.repository import Gdk
Then we can modify the code to the following:
Gdk.color_parse(color)

=== Pango ===
Following the release of Gtk3, we should not be importing pango like this:
import pango
In fact, we can now import pango as an attribute within the gtk3 library:
from gi.repository import Pango as pango

=== Other considerations ===

''self.allocation'' property is no longer available. Please search your code for "self.allocation" and replace it for "self.get_allocation()".

So to get the allocation size:

self.allocation.width
self.allocation.height

should be replaced by:

self.get_allocated_width()
self.get_allocated_height()

=== Constants ===

Most of the constants have slightly different formats, e.g.,

Gtk.StateFlags.NORMAL
Gtk.PolicyType.NEVER
Gtk.Justification.LEFT

=== Pixbufs ===

The pixbuf libraies are in their own repository

from gi.repository import GdkPixbuf

GdkPixbuf.Pixbuf.new_from_file()

==Make a release==
===Versioning===
If you do new releases the versioning of the GTK2 and GTK3 release should be different. For GTK2 releases you should use dotted versions for new development releases major versions. Let's have a look at hello-world as an example. The latest release of hello-world was version 3. Bug fix releases should be named 3.1 then 3.2 and so on. The new releases for the new development branch should be starting with a major number, in the case of hello-world version 4.

To minimise the maintainer overload we highly encourage you to only do bug-fix releases for the GTK2 branch. New features should only go into the new branch that is based on gobject-introspection and GTK3.

Note that some older versions of Sugar don't know how to parse dotted version numbers. An alternative to the above is to simply ensure that the version number of the GTK3 branch is always greater than (>) the version number of the GTK2 version.

===GIT conventions===
We've agreed that the GTK3 version should be in the '''master''' branch on gitorious.sugarlabs.org. The GTK2 version should be in a branch called '''gtk2'''.

Some helpful git foo:

From your repository, first create the GTK2 branch with:
git branch gtk2

Then pull in all GTK3 changes on top of the master branch:
git pull git://path/to/gtk3/repo

To move the gtk2 to gitorious.sugarlabs.org:
git checkout gtk2
git push -u origin gtk2

== Tips to Activity Developers ==

===Changes to the Clipboard===
Two things to note:

1. You need to specify a clipboard using get()
clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
2. You need to pass a length to set_text()
clipboard.set_text(string, len(string))

See [http://python-gtk-3-tutorial.readthedocs.org/en/latest/clipboard.html] for more details.

===Changes to Drag-and-Drop===
Slightly different syntax:
self.drag_dest_set(Gtk.DestDefaults.ALL, [],
Gdk.DragAction.COPY)
self.drag_dest_set_target_list(Gtk.TargetList.new([]))
self.drag_dest_add_text_targets()
self.connect('drag_data_received', self._drag_data_received)

and:
data.get_text()
or:
data.get_image()

See [http://python-gtk-3-tutorial.readthedocs.org/en/latest/drag_and_drop.html] for more details.

===Going from Drawable to Cairo===

GTK-3 does not support gtk Drawable objects, so the first step is to get your activity running under Cairo.

<pre>
import cairo

# From activity.Activity, you inherit a canvas.
# Create a Cairo context from the window.
cairo_context = self.canvas.get_window().cairo_create()

# Create an XLib surface to be used for drawing
xlib_surface = surface.create_similar(cairo.CONTENT_COLOR,
gtk.gdk.screen_width(),
gtk.gdk.screen_height())

# You'll need a Cairo context from which you'll build a GTK Cairo context
cairo_context = cairo.Context(xlib_surface)
cairo_context = gtk.gdk.CairoContext(cairo_context)

# Use this context as you would a Drawable, substituting Cairo commands
# for gtk commands, e.g.,
cairo_context.move_to(0, 0)
cairo_context.line_to(100, 100)
# Cairo uses floats from 0 to 1 for RGB values
cairo_context.set_source_rgb(r, g, b)
cairo_context.rectangle(x, y, w, h)
cairo_context.fill()

# To invalidate a region to force a refresh, use:
self.canvas.queue_draw_area(x, y, w, h)

# Handle the expose event
def do_expose_event(self, event):
# Create the cairo context
cairo_context = self.canvas.get_window().cairo_create()
cairo_context.rectangle(event.area.x, event.area.y,
event.area.width, event.area.height)
cairo_context.clip()
cairo_context.set_source_surface(xlib_surface)
cairo_context.paint()
</pre>

Pango is a bit different when used with Cairo:

<pre>
import pango, pangocairo

# Again, from the xlib_surface...
cairo_context = cairo.Context(xlib_surface)

# Create a PangoCairo context
cairo_context = pangocairo.CairoContext(cairo_context)

# The pango layout is created from the Cairo context
pango_layout = cairo_context.create_layout()

# You still use pango to set up font descriptions.
fd = pango.FontDescription('Sans')
fd.set_size(12 * pango.SCALE)

# Tell your pango layout about your font description
pango_layout.set_font_description(fd)

# Write text to your pango layout
pango_layout.set_text('Hello world', -1)

# Position it within the Cairo context
cairo_context.save()
cairo_context.translate(x, y)
cairo_context.rotate(pi / 3) # You can rotate text and images in Cairo
cairo_context.set_source_rgb(1, 0, 0)

# Finally, draw the text
cairo_context.update_layout(pango_layout)
cairo_context.show_layout(pango_layout)
cairo_context.restore()
</pre>

To draw a bitmap...

<pre>
# Again, from the xlib_surface...
cairo_context = cairo.Context(xlib_surface)

# Create a gtk context
cairo_context = gtk.gdk.CairoContext(cairo_context)
cairo_context.set_source_pixbuf(pixbuf, x, y)
cairo_context.rectangle(x, y, w, h)
cairo_context.fill()
</pre>

To read a pixel from the xlib surface...

<pre>
# create a new 1x1 cairo surface
cairo_surface = cairo.ImageSurface(cairo.FORMAT_RGB24, 1, 1);
cairo_context = cairo.Context(cairo_surface)
# translate xlib_surface so that target pixel is at 0, 0
cairo_context.set_source_surface(xlib_surface, -x, -y)
cairo_context.rectangle(0,0,1,1)
cairo_context.set_operator(cairo.OPERATOR_SOURCE)
cairo_context.fill()
cairo_surface.flush() # ensure all writing is done
# Read the pixel
return (ord(pixels[2]), ord(pixels[1]), ord(pixels[0]), 0)
</pre>

===Going from Cairo in GTK-2 to Cairo in GTK-3===

(See http://developer.gnome.org/pangomm/2.28/annotated.html for more details)
Not much changes, but...

The Cairo/Pango interaction is a little different:
<pre>
from gi.repository import Pango, PangoCairo

cairo_context = ...
pango_layout = PangoCairo.create_layout(cairo_context)
fd = Pango.FontDescription('Sans')
fd.set_size(12 * Pango.SCALE)
pango_layout.set_font_description(fd)
pango_layout.set_text('Hello World', -1)
cairo_context.set_source_rgb(1, 0, 0)
PangoCairo.update_layout(cairo_context, pango_layout)
PangoCairo.show_layout(cairo_context, pango_layout)
</pre>

The get_extents() method if different in PangoCairo. It calculates an extent as a Rectangle, but doesn't return anything. There is a method, get_logical_extents() that returns a Rectangle. Alas, it is not necessarily available after v1.16. Note that Rectangle is not a list but a class with methods for get_x(), get_y(), get_width(), and get_height(), so you cannot iter over it.

==== Replacing pixmaps with Cairo ====
You need to replace your pixmaps with Cairo in GTK3. See http://developer.gnome.org/gtk3/3.5/ch24s02.html#idp129615008 for example code.

===Taking a screenshot and making a thumbnail===
To make a screenshot of the window:
<pre>
width, height = window.get_width(), window.get_height()
thumb_surface = Gdk.Window.create_similar_surface(window,
cairo.CONTENT_COLOR,
width, height)

thumb_width, thumb_height = style.zoom(100), style.zoom(80)
cairo_context = cairo.Context(thumb_surface)
thumb_scale_w = thumb_width * 1.0 / width
thumb_scale_h = thumb_height * 1.0 / height
cairo_context.scale(thumb_scale_w, thumb_scale_h)
Gdk.cairo_set_source_window(cairo_context, window, 0, 0)
cairo_context.paint()
thumb_surface.write_to_png(png_path_or_filelike_object)
</pre>

===Creating a video widget===

Haven't gotten this working yet, but some necessary changes include:

Instead of
window.xid
use
get_property('window').get_xid()

Instead of
unset_flags(gtk.DOUBLE_BUFFERED)
set_flags(gtk.APP_PAINTABLE)
use
set_double_buffered(False)
set_app_paintable(True)

A more basic question is whether or not we migrate to gstreamer-1.0. If we do, some helpful documentation is found here [https://wiki.ubuntu.com/Novacut/GStreamer1.0].

== Resources ==
* PyGtk documentation
:: Gtk3: http://python-gtk-3-tutorial.readthedocs.org
:: gtk2: http://www.pygtk.org/docs/pygtk/
* Reference Manual
:: Gtk3: http://developer.gnome.org/gtk3/3.4/
* Gdk documentation:
:: Gdk3: http://developer.gnome.org/gdk/2.24/
* Pango documentation:
:: GTK3: http://developer.gnome.org/pangomm
* Gst-1.0 documentation
:: Gst-1: http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer/html/index.html
* Gst-1.0 porting hints
:: https://wiki.ubuntu.com/Novacut/GStreamer1.0

[[Category:Developer]]

= More porting wiki pages =

{{Special:PrefixIndex/Features/GTK3/Porting}}

Features/GTK3/Porting

2017-12-23T07:00:12Z

Emilyo11: Included sugar3, pango, gdk

=Porting an existing activity to GTK3=
This is a guide to porting an existing activity from GTK2 to [http://developer.gnome.org/gtk3/stable/ GTK3]. It also shows the changes to use the new Sugar toolkit that also now uses [[Features/GTK3|GTK3]]. This guide uses the [http://git.sugarlabs.org/hello-world hello-world] activity as a simple example.

There is another guide written from scratch that uses this one as reference. It was done porting GetBooks Activity [[Features/GTK3/Porting/GetBooks]]

If you would like to reference other examples of GTK3 port:
* [https://github.com/sugarlabs/biorhythm/commit/c16de3b70cce2cc6f8af933e2b062c844a47c144/ Biorhythm]

==Preparation==
Before you start porting your activity you are encouraged to branch off a stable branch. This will allow you to keep on doing stable releases on the stable branch and new releases on the master branch. We highly recommend that you use the 'sugar-0.94' as the stable branch name because this will keep the repositories consistent and eases the development work. Let's step through this with a real life example:

The latest release of hello-world was version 3 (commit 04fb9beb708f1078aae93995da3ec06bac7aa433). We want to branch off at that point. If you did not do any changes after the last stable commit simply create a branch with:
git branch sugar-0.94

If you have already made commits after that, you need to go to that commit first and create a branch at that specific point in our case commit 04fb9beb708f1078aae93995da3ec06bac7aa433, there is a command to do that in one go:
git checkout -b sugar-0.94 04fb9beb708f1078aae93995da3ec06bac7aa433

In both cases this has created a local branch, as you can see by running 'git branch'; you should see the following (if you did the second command you will have sugar-0.94 already selected):

<pre>
[erikos@T61 helloworld]$ git branch
* master
sugar-0.94
</pre>

The 'sugar-0.94' branch is only available locally, as you can see by running 'git branch -r' which shows the remote branches:

<pre>
[erikos@T61 helloworld]$ git branch -r
origin/HEAD -> origin/master
origin/master
origin/sucrose-0.84
</pre>

The only branch available besides the master branch is the 'sucrose-0.84' branch. Let's push now our new branch to the remote repository to make it available for others:
<pre>
git push origin sugar-0.94
</pre>

The branch is now listed as a remote branch. You can verify as well on your [http://git.sugarlabs.org/hello-world/mainline gitorious page].
<pre>
[erikos@T61 helloworld]$ git branch -r
origin/HEAD -> origin/master
origin/master
origin/sucrose-0.84
origin/sugar-0.94
</pre>

You can switch now between those branches using 'git checkout <branch>'. And you can use 'git branch' to see which branch you are on (the one with the * before is the branch you are currently on).
<pre>
git checkout sugar-0.94
git checkout master
</pre>

==Cleanup, adopt to API changes in sugar-toolkit-gtk3 ==
''This should be done only on the master branch''! In the new sugar-toolkit-gtk3 we have removed old API, you should adjust your activity accordingly:
* the keep button has been removed completely
* the old-style toolbar has been removed
* do not use set_toolbox anymore use set_toolbar_box instead (see in [http://git.sugarlabs.org/~walter/abacus/walter-cairo/commit/6871dd340a89ade3b5361457e1bd1d58276a8efc Abacus])
* remove import of deprecated ActivityToolbox (see [http://git.sugarlabs.org/hello-world/mainline/commit/22060a3063b2d6fd38d6b1cd8d44946170255af3 hello-world])
* support for 'service_name' and 'class' has been removed from the activity.info make sure you are using: 'bundle_id' instead of 'service_name' and 'exec' instead of 'class' (see in [http://git.sugarlabs.org/record/mainline/commit/6e8968c71e474e2d8d86886badf5cf7d70217dc5 Record])

==Port the activity from GTK2 to GTK3==
To start, change the importing instruction for GTK from
import gtk
to
from gi.repository import Gtk

Remember to import the gi module and specify the Gtk version as 3.0 as well.
<pre>
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
</pre>

Then you have to change each call that involves Gtk, for example creating a button will look now like this:
button = Gtk.Button()

A simple hello world program in GTK3 looks like this:
<pre>
from gi.repository import Gtk

def _destroy_cb(widget, data=None):
Gtk.main_quit()

w = Gtk.Window()
w.connect("destroy", _destroy_cb)
label = Gtk.Label('Hello World!')
w.add(label)
w.show_all()

Gtk.main()
</pre>

For porting your activity you do have to change your calls for accessing widgets and services in the new GTK3 sugar-toolkit as well. The new namespace is called [https://developer.sugarlabs.org/sugar3/ sugar3], trying to reflect that GTK3 is the underlying technology. For example the import of the base activity class has to be changed from
from sugar.activity import activity
to
from sugar3.activity import activity

Make sure you change the setup.py in your activity to point to the new toolkit as well:
from sugar3.activity import bundlebuilder

The changes that were needed to port the hello-world activity can be seen in [http://git.sugarlabs.org/hello-world/mainline/commit/508e1c518b56cbde5508e560c8a2ff38a3518583 this commit].

Ok, let's do these changes now for your activity. Make sure you are in your master branch using the 'git branch' command (the master branch should have a '*' before it). Make your changes, commit them ('git commit -a') and push them to the remote repository ('git push origin master').

====Simple example on creating a toolbar====
One of Sugar's activity most unique user interface includes the toolbar. In order to reference the relevant modules and graphics, the sugar3 library has to be imported. These are the relevant ones that would enable us to create a simple toolbar containing the activity button and the stop button.
<pre>
from sugar3.activity import activity
from sugar3.graphics.toolbarbox import ToolbarBox
from sugar3.activity.widgets import ActivityToolbarButton
from sugar3.activity.widgets import StopButton
from sugar3.graphics.toolbarbox import ToolbarButton
from sugar3.graphics import style
</pre>

Since the ActivityToolbar() module has been deprecated, the toolbar can now be called using
ToolbarBox()
Then, from the ToolbarBox(), include the ActivityButton and StopButton. In order for the StopButton to be align to the right as per Sugar activity interface, a separator has to be included as well.

<pre>
toolbar_box = ToolbarBox()

activity_button = ActivityToolbarButton(self)
toolbar_box.toolbar.insert(activity_button, 0)
activity_button.show()

separator = Gtk.SeparatorToolItem()
separator.props.draw = False
separator.set_expand(True)
toolbar_box.toolbar.insert(separator, -1)
separator.show()

stop_button = StopButton(self)
toolbar_box.toolbar.insert(stop_button, -1)
stop_button.show()
self.set_toolbar_box(toolbar_box)
toolbar_box.show()
</pre>

===Tools===
There are tools to help you do the porting. There is a script in the pygobject repository for porting called [http://git.gnome.org/browse/pygobject/tree/pygi-convert.sh pygi-convert.sh], more info about the script can be found in [http://live.gnome.org/PyGObject/IntrospectionPorting the PyGObject Introspection Porting guide].

Here is a script to automate the rename of the imports '''sugar''' to '''sugar3''': [http://dev.laptop.org/~manuq/sugar-convert.sh sugar-convert.sh].

If you are having trouble finding how a particular GTK class/method/constant has been named in PyGI, run [http://dev.laptop.org/~dsd/20110806/pygi-enumerate.py pygi-enumerate.py] and grep the output. (this app lists all identified methods and constants). Usage example:

<pre>
$ python pygi-enumerate.py | grep get_selection
Gtk.AccelLabel.get_selection_bounds() (instance method)
Gtk.Editable.get_selection_bounds() (instance method)
Gtk.Entry.get_selection_bounds() (instance method)
Gtk.IconView.get_selection_mode() (instance method)
Gtk.Label.get_selection_bounds() (instance method)
Gtk.SelectionData.get_selection() (instance method)
Gtk.SpinButton.get_selection_bounds() (instance method)
Gtk.TextBuffer.get_selection_bound() (instance method)
Gtk.TextBuffer.get_selection_bounds() (instance method)
Gtk.TreeView.get_selection() (instance method)
</pre>

=== Constructor considerations ===

With PyGI it is possible to use Python-like constructors, or "new" functions e.g. the following are (usually) equivalent:
label = Gtk.Button()
label = Gtk.Button.new()

However, the first form is preferred: it is more Python-like. Internally, the difference is that Gtk.Label.new() translates to a call to gtk_label_new(), whereas Gtk.Label() (the preferred form) will directly construct an instance of GtkLabel at the GObject level.

If the constructor takes parameters, they '''must''' be named. The parameters correspond to GObject properties in the API documentation which are usually marked as "Construct". For example, the following code will not work:

expander = Gtk.Expander("my expander")

The (confusing) error is:
TypeError: GObject.__init__() takes exactly 0 arguments (1 given)

The solution is to go to the [http://developer.gnome.org/gtk3/3.2/GtkExpander.html#GtkExpander.properties GtkExpander API documentation] and find the appropriate property that we wish to set. In this case it is <b>label</b> (which is a Construct property, further increasing our confidence of success), so the code should be:

expander = Gtk.Expander(label="my expander")

Combining the two points above, if you wish to call a construct-like function such as gtk_button_new_with_label(), you do have the option of calling Gtk.Button.new_with_label(), however if we check the [http://developer.gnome.org/gtk3/3.2/GtkButton.html#GtkButton.properties GtkButton properties] we see one called "label" which is equivalent. Therefore gtk_button_new_with_label("foo") should be called as:
button = Gtk.Button(label="foo")

=== HBox, VBox, pack_start and pack_end ===

GtkHBox and GtkVBox, commonly used containers in GTK2 code, have pack_start and pack_end methods. These take 4 parameters:
# The widget to pack into the container
# '''expand''': Whether the child should receive extra space when the container grows (default True)
# '''fill''': True if space given to child by the expand option is actually allocated to child, rather than just padding it. This parameter has no effect if expand is set to False. A child is always allocated the full height of a gtk.HBox and the full width of a gtk.VBox. This option affects the other dimension. (default True)
# '''padding''': extra space in pixels to put between child and its neighbor (default 0)

In PyGTK, the expand, fill and padding parameters were optional: if unspecified, the default values above were used. In PyGI, these parameters are '''not''' optional: all 4 must be specified. Hence the rules for adding in the extra parameters are:

# If '''expand''' was not set, use value True
# If '''fill''' was not set, use value True. (however, if expand is False, this parameter gets ignored so False is an equally acceptable option when expand=False)
# If '''padding''' was not set, use value 0.

These parameters can be specified either as positional arguments or as named keyword arguments, however all 4 must always be specified. Some developers prefer keyword arguments, arguing that the following:
<pre>box.pack_start(widget, expand=True, fill=False, padding=4)</pre>
is much more readable than:
<pre>box.pack_start(widget, True, False, 4)</pre>

However, these functions are called extremely often; any mildly seasoned GTK developer will have memorized the order and meaning of the parameters. Some developers therefore prefer to avoid the extra work of dropping in hundreds of keyword arguments throughout the code and just use the positional ones. This is really up to you.

If you are using pack_start with the default values (expand=True, fill=True and padding=0), you can avoid using pack_start (and the parameter pain that it brings with it) by just using .add for some added cleanliness, e.g.
<pre>box.pack_start(widget, True, True, 0)</pre>
can be replaced with:
<pre>box.add(widget)</pre>

This is as far as you need to go for now. However, in GTK3, GtkVBox and GtkHBox have been deprecated, which means they might be removed in GTK3. The replacement is to use GtkBox directly, and you may wish to make this change now. e.g.:
<pre>vbox = Gtk.Box(orientation=Gtk.Orientation.VERTICAL)</pre>
<pre>hbox = Gtk.Box(orientation=Gtk.Orientation.HORIZONTAL, homogeneous=True, spacing=8)</pre>
However, it must be noted that if GtkBox is used directly (instead of using GtkHBox/GtkVBox), the default value of '''expand''' is now '''False'''. The implications of this are:
# You need to check your .add() calls, as previously they would behave as pack_start with expand=True, but now they will behave as expand=False (you need to change them to use pack_start with expand=True to retain the old behaviour)
# Every single pack_start call that has expand=False and padding=0 (and any value of fill) can be converted to .add() for cleanliness

=== GtkAlignment considerations ===

In PyGTK, the gtk.Alignment constructor takes four optional parameters:
# xalign: the fraction of horizontal free space to the left of the child widget. Ranges from 0.0 to 1.0. Default value 0.0.
# yalign: the fraction of vertical free space above the child widget. Ranges from 0.0 to 1.0. Default value 0.0.
# xscale: the fraction of horizontal free space that the child widget absorbs, from 0.0 to 1.0. Default value 0.0.
# yscale: the fraction of vertical free space that the child widget absorbs, from 0.0 to 1.0. Default value 0.0

In PyGI/GTK3, these parameters are still optional when used in the Gtk.Alignment constructor (as keyword arguments, as explained above). However, the default values have changed. They are now:
# xalign: default value 0.5
# yalign: default value 0.5
# xscale: default value 1
# yscale: default value 1

If your code was relying on the default value of 0 for any of these parameters in PyGTK, you will now need to explicitly specify that in your constructor. Similarly, if you were previously using construction parameters to select the now-default values, those parameters can be dropped.

Additionally, PyGTK accepted these construction parameters as positional arguments. As explained above, they must now be converted to keyword arguments.

=== Gdk ===
Previously, gdk was an attribute of the gtk module, which means that it can be called through gtk. For example, if we want to use color_parse():
gtk.gdk.color_parse(color)
However, what we have to do now is:
from gi.repository import Gdk
Then we can modify the code to the following:
Gdk.color_parse(color)

=== Pango ===
Following the release of Gtk3, we should not be importing pango like this:
import pango
In fact, we ca now import pango as an attribute within the gtk3 library:
from gi.repository import Pango as pango

=== Other considerations ===

''self.allocation'' property is no longer available. Please search your code for "self.allocation" and replace it for "self.get_allocation()".

So to get the allocation size:

self.allocation.width
self.allocation.height

should be replaced by:

self.get_allocated_width()
self.get_allocated_height()

=== Constants ===

Most of the constants have slightly different formats, e.g.,

Gtk.StateFlags.NORMAL
Gtk.PolicyType.NEVER
Gtk.Justification.LEFT

=== Pixbufs ===

The pixbuf libraies are in their own repository

from gi.repository import GdkPixbuf

GdkPixbuf.Pixbuf.new_from_file()

==Make a release==
===Versioning===
If you do new releases the versioning of the GTK2 and GTK3 release should be different. For GTK2 releases you should use dotted versions for new development releases major versions. Let's have a look at hello-world as an example. The latest release of hello-world was version 3. Bug fix releases should be named 3.1 then 3.2 and so on. The new releases for the new development branch should be starting with a major number, in the case of hello-world version 4.

To minimise the maintainer overload we highly encourage you to only do bug-fix releases for the GTK2 branch. New features should only go into the new branch that is based on gobject-introspection and GTK3.

Note that some older versions of Sugar don't know how to parse dotted version numbers. An alternative to the above is to simply ensure that the version number of the GTK3 branch is always greater than (>) the version number of the GTK2 version.

===GIT conventions===
We've agreed that the GTK3 version should be in the '''master''' branch on gitorious.sugarlabs.org. The GTK2 version should be in a branch called '''gtk2'''.

Some helpful git foo:

From your repository, first create the GTK2 branch with:
git branch gtk2

Then pull in all GTK3 changes on top of the master branch:
git pull git://path/to/gtk3/repo

To move the gtk2 to gitorious.sugarlabs.org:
git checkout gtk2
git push -u origin gtk2

== Tips to Activity Developers ==

===Changes to the Clipboard===
Two things to note:

1. You need to specify a clipboard using get()
clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
2. You need to pass a length to set_text()
clipboard.set_text(string, len(string))

See [http://python-gtk-3-tutorial.readthedocs.org/en/latest/clipboard.html] for more details.

===Changes to Drag-and-Drop===
Slightly different syntax:
self.drag_dest_set(Gtk.DestDefaults.ALL, [],
Gdk.DragAction.COPY)
self.drag_dest_set_target_list(Gtk.TargetList.new([]))
self.drag_dest_add_text_targets()
self.connect('drag_data_received', self._drag_data_received)

and:
data.get_text()
or:
data.get_image()

See [http://python-gtk-3-tutorial.readthedocs.org/en/latest/drag_and_drop.html] for more details.

===Going from Drawable to Cairo===

GTK-3 does not support gtk Drawable objects, so the first step is to get your activity running under Cairo.

<pre>
import cairo

# From activity.Activity, you inherit a canvas.
# Create a Cairo context from the window.
cairo_context = self.canvas.get_window().cairo_create()

# Create an XLib surface to be used for drawing
xlib_surface = surface.create_similar(cairo.CONTENT_COLOR,
gtk.gdk.screen_width(),
gtk.gdk.screen_height())

# You'll need a Cairo context from which you'll build a GTK Cairo context
cairo_context = cairo.Context(xlib_surface)
cairo_context = gtk.gdk.CairoContext(cairo_context)

# Use this context as you would a Drawable, substituting Cairo commands
# for gtk commands, e.g.,
cairo_context.move_to(0, 0)
cairo_context.line_to(100, 100)
# Cairo uses floats from 0 to 1 for RGB values
cairo_context.set_source_rgb(r, g, b)
cairo_context.rectangle(x, y, w, h)
cairo_context.fill()

# To invalidate a region to force a refresh, use:
self.canvas.queue_draw_area(x, y, w, h)

# Handle the expose event
def do_expose_event(self, event):
# Create the cairo context
cairo_context = self.canvas.get_window().cairo_create()
cairo_context.rectangle(event.area.x, event.area.y,
event.area.width, event.area.height)
cairo_context.clip()
cairo_context.set_source_surface(xlib_surface)
cairo_context.paint()
</pre>

Pango is a bit different when used with Cairo:

<pre>
import pango, pangocairo

# Again, from the xlib_surface...
cairo_context = cairo.Context(xlib_surface)

# Create a PangoCairo context
cairo_context = pangocairo.CairoContext(cairo_context)

# The pango layout is created from the Cairo context
pango_layout = cairo_context.create_layout()

# You still use pango to set up font descriptions.
fd = pango.FontDescription('Sans')
fd.set_size(12 * pango.SCALE)

# Tell your pango layout about your font description
pango_layout.set_font_description(fd)

# Write text to your pango layout
pango_layout.set_text('Hello world', -1)

# Position it within the Cairo context
cairo_context.save()
cairo_context.translate(x, y)
cairo_context.rotate(pi / 3) # You can rotate text and images in Cairo
cairo_context.set_source_rgb(1, 0, 0)

# Finally, draw the text
cairo_context.update_layout(pango_layout)
cairo_context.show_layout(pango_layout)
cairo_context.restore()
</pre>

To draw a bitmap...

<pre>
# Again, from the xlib_surface...
cairo_context = cairo.Context(xlib_surface)

# Create a gtk context
cairo_context = gtk.gdk.CairoContext(cairo_context)
cairo_context.set_source_pixbuf(pixbuf, x, y)
cairo_context.rectangle(x, y, w, h)
cairo_context.fill()
</pre>

To read a pixel from the xlib surface...

<pre>
# create a new 1x1 cairo surface
cairo_surface = cairo.ImageSurface(cairo.FORMAT_RGB24, 1, 1);
cairo_context = cairo.Context(cairo_surface)
# translate xlib_surface so that target pixel is at 0, 0
cairo_context.set_source_surface(xlib_surface, -x, -y)
cairo_context.rectangle(0,0,1,1)
cairo_context.set_operator(cairo.OPERATOR_SOURCE)
cairo_context.fill()
cairo_surface.flush() # ensure all writing is done
# Read the pixel
return (ord(pixels[2]), ord(pixels[1]), ord(pixels[0]), 0)
</pre>

===Going from Cairo in GTK-2 to Cairo in GTK-3===

(See http://developer.gnome.org/pangomm/2.28/annotated.html for more details)
Not much changes, but...

The Cairo/Pango interaction is a little different:
<pre>
from gi.repository import Pango, PangoCairo

cairo_context = ...
pango_layout = PangoCairo.create_layout(cairo_context)
fd = Pango.FontDescription('Sans')
fd.set_size(12 * Pango.SCALE)
pango_layout.set_font_description(fd)
pango_layout.set_text('Hello World', -1)
cairo_context.set_source_rgb(1, 0, 0)
PangoCairo.update_layout(cairo_context, pango_layout)
PangoCairo.show_layout(cairo_context, pango_layout)
</pre>

The get_extents() method if different in PangoCairo. It calculates an extent as a Rectangle, but doesn't return anything. There is a method, get_logical_extents() that returns a Rectangle. Alas, it is not necessarily available after v1.16. Note that Rectangle is not a list but a class with methods for get_x(), get_y(), get_width(), and get_height(), so you cannot iter over it.

==== Replacing pixmaps with Cairo ====
You need to replace your pixmaps with Cairo in GTK3. See http://developer.gnome.org/gtk3/3.5/ch24s02.html#idp129615008 for example code.

===Taking a screenshot and making a thumbnail===
To make a screenshot of the window:
<pre>
width, height = window.get_width(), window.get_height()
thumb_surface = Gdk.Window.create_similar_surface(window,
cairo.CONTENT_COLOR,
width, height)

thumb_width, thumb_height = style.zoom(100), style.zoom(80)
cairo_context = cairo.Context(thumb_surface)
thumb_scale_w = thumb_width * 1.0 / width
thumb_scale_h = thumb_height * 1.0 / height
cairo_context.scale(thumb_scale_w, thumb_scale_h)
Gdk.cairo_set_source_window(cairo_context, window, 0, 0)
cairo_context.paint()
thumb_surface.write_to_png(png_path_or_filelike_object)
</pre>

===Creating a video widget===

Haven't gotten this working yet, but some necessary changes include:

Instead of
window.xid
use
get_property('window').get_xid()

Instead of
unset_flags(gtk.DOUBLE_BUFFERED)
set_flags(gtk.APP_PAINTABLE)
use
set_double_buffered(False)
set_app_paintable(True)

A more basic question is whether or not we migrate to gstreamer-1.0. If we do, some helpful documentation is found here [https://wiki.ubuntu.com/Novacut/GStreamer1.0].

== Resources ==
* PyGtk documentation
:: Gtk3: http://python-gtk-3-tutorial.readthedocs.org
:: gtk2: http://www.pygtk.org/docs/pygtk/
* Reference Manual
:: Gtk3: http://developer.gnome.org/gtk3/3.4/
* Gdk documentation:
:: Gdk3: http://developer.gnome.org/gdk/2.24/
* Pango documentation:
:: GTK3: http://developer.gnome.org/pangomm
* Gst-1.0 documentation
:: Gst-1: http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer/html/index.html
* Gst-1.0 porting hints
:: https://wiki.ubuntu.com/Novacut/GStreamer1.0

[[Category:Developer]]

= More porting wiki pages =

{{Special:PrefixIndex/Features/GTK3/Porting}}

Sugar Labs/FAQ

2017-01-07T16:16:19Z

Emilyo11: /* Using Sugar */

{{Graduate|Some useful stuff in here}}

<noinclude>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</noinclude>
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]''', or follow the question links at the top of the major sections, or visit [[:Category:FAQ]].
__TOC__
==Sugar==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== What is Sugar? ===
:Sugar is an educational software platform built with the Python programming language and based on the principles of cognitive and social constructivism. See [[What is Sugar?]].

=== Who is doing Sugar development? ===
:Sugar is a community project where all work is done by volunteers. You can get an idea of the people involved from the [[Development Team/Release/Modules]] page.

=== Does Sugar support Android? ===
: Not at this time, although there are some developers working to change that situation. See this [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg13765.html mailing list thread].

=== What makes Sugar different from other educational software platforms? ===
* See [[Marketing Team/Website#Website_2|Website sandbox]].
:The Sugar interface, in its departure from the desktop metaphor for computing, is the first serious attempt to create a user interface that is based on both cognitive and social constructivism: learners should engage in authentic exploration and collaboration. It is based on three very simple principles about what makes us human: (1) everyone is a teacher and a learner; (2) humans by their nature are social beings; and (3) humans by their nature are expressive. These are the pillars of a user experience for learning.

:Sugar also considers two aphorisms: (1) you learn through doing, so if you want more learning, you want more doing; and (2) love is a better master than duty—you want people to engage in things that are authentic to them, things that they love.

:The presence of other people is inherent to the Sugar interface: collaboration is a first-order experience. Students and teachers engage in a dialog with each other, support each other, critique each other, and share ideas.

:Sugar is also discoverable: it can accommodate a wide variety of users, with different levels of skill in terms of reading, language, and different levels of experience with computing. It is easy to approach, and yet it doesn't put an upper bound on personal expression; one can peel away layers and go deeper and deeper, with few restrictions.

:Sugar is based on Python, an interpreted language, allowing the direct appropriation of ideas: in whatever realm the learner is exploring—music, browsing, reading, writing, programming, graphics, etc.—they are able to drill deeper; they are not going to hit a wall, since they can, at every level, engage in debugging both their personal expression and the very tools that they use for that expression.

==Using Sugar==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== Who can use Sugar and how do they benefit? ===
:Sugar is a free software project, freely available to anyone who wants to use it or improve upon it.

:The Sugar platform was designed for young children (K–6), but it is finding applicability in a number of different venues where the simplicity of design maps is an enabler, e.g., mobile applications, the elderly, etc.

:'''Why Sugar?''' Sugar will engage even the youngest learner in the use of computation as a powerful "thing to think with." They will quickly become proficient in using the computer as a tool to engage in authentic problem-solving. Sugar users develop skills that help them in all aspects of life.
* Sugar comes with hundreds of tools for discovery through exploring, expressing, and sharing: browsing, writing, rich media, etc.
* Sugar comes with a built-in collaboration system: peer-to-peer learning; always-on support; and single-click sharing.
* Sugar comes with built-in tools for reflection; a built-in portfolio assessment tool that serves as a forum for discussion between children, their parents, and their teachers.
* The Sugar learning platform is discoverable: it uses simple means to reach to complex ends with no upper bound on where you can reach.
* Sugar is designed for local appropriation: it has built-in tools for making changes and improvements and a growing global community of support.
* Sugar puts an emphasis on learning through doing and debugging: more engaged learners are to tackle authentic problems.
* Sugar is available in a wide variety of forms: as part of GNU/Linux distributions; LiveUSB/CD; and in virtual machines or emulation.
:There is a further summary of the Sugar benefits [[Deployment Team/Small_deployment_guide#Why_Sugar|here]].

=== How can I get online with the Live USB/CD, and what can I do then? ===

:The Live USB device must be inserted into a USB port on your computer, the Live CD must be in your CD-ROM or DVD drive, when you start your computer, and your BIOS settings should be set to first look for an operating system there on the USB or CD-ROM device. If the settings are okay, the Live USB/CD will boot.

:After a little while, you will be prompted for a name and you will get to choose the colour of your avatar. This is a small X, like the arms and legs of a human, with an O as the head above the X. This is "you".

:Wait a little longer, and you will see "yourself" in the middle of the screen. Just below "you", is your journal, where everything you do is recorded.

:In the top left corner of the Frame is a circle of smaller circles. This is your Neighbourhood-circle. At the moment, only nearby wireless access points are visible as small coloured circles - more colour inside means better signal strength. Let your mouse pointer hover above a circle to see the name of the wireless network. A small padlock means you need to supply a username and password to access the network. Click the circle you would like to access. It should be a wireless network you know will grant you Internet access once you are connected. If the network is protected with a padlock, you will be prompted for a valid username and password at this point, so give these and click the OK-button. If everything is okay, you are now connected.

:You should soon see many small avatars like your own in your neighbourhood. Hover your mouse pointer above them to see their usernames.

:In the top left corner next to the Neighbourhood-circle, is your Friends-circle. You don't have any Sugar-friends at the moment, so this will be empty. Next to the Friends-circle is a circle with a single dot - that's right - it means you. Click the You-circle, and you will get back to you and your activities.

:Surrounding your avatar on the Home screen are many activities, so click the one that looks like a cartoon talk bubble to start the Chat-activity or some other activity - like the Paint-activity or the Calculator-activity. After a little while, the new activity opens. In the top right corner of all activities is a small menu, which says "Share with:". Click this to unfold the options, and choose Neighbourhood by clicking on it.

:Click the Neighbourhood-circle again, and you will notice that the activity is now visible to everyone in your neighbourhood. If you hover your mouse button over an activity in your neighbourhood, a small menu will unfold where you may choose to join the activity by selecting "Join" from the activity's menu. Remember, your neighbourhood is the entire world! People in other parts of the world may be working or sleeping when you start sharing your activities, so be patient - it might be many hours before anyone is available for a chat. Enjoy! :-)

=== Does Sugar run on {GNU/Linux, Fedora, Ubuntu, SUSE, MAC OS, Windows, etc.}? ===
:Please refer to the [[Supported systems]] page for an up-to-date list of supported systems.

=== Is there an image of the OS that can be run on a PC? ===
:You can download a Live USB image at [[Sugar on a Stick]] and a Live CD version of Sugar at http://wiki.laptop.org/go/LiveCd, or run Sugar natively on a [[Supported systems|supported system]]. (The language can be set from the Sugar-control-panel or My Settings link on the avatar panel.)

=== Does Sugar run on an ASUS Eee PC (or other "ultra-mobile" or "mini" PCs)?===
Yes. If it can run GNU/Linux and GNOME, it can run Sugar. Try [[Sugar on a Stick]] as a way to get started, but you should be able install it natively as well.

=== Is it possible to have mesh support with the Live USB/CD ? ===
Q: If I understand this correctly, mesh support means your wireless card functions as both an access point/router and a network node. In short, your wireless computer can pass along packages from nearby wireless computers and the other way round. Do you need special wireless cards for this, or is this a driver/software issue that could be fixed in the Live CD, so that more people can experience mesh networks?

:A: Yes, it will be possible to have [http://www.open80211s.org/trac/wiki/HOWTO-0.2.1 mesh support] with the Live CD shortly, provided you have a suitable wireless card.

:[http://www.o11s.org/ open80211s] is an open-source implementation of the emerging IEEE 802.11s wireless mesh standard. It has been accepted in the mainline Linux kernel and is included in release 2.6.26. The resulting software will run on GNU/Linux on commodity PC hardware.

:Open80211s is based on the mac80211 wireless stack and should run on any of the wireless cards that mac80211 supports. At present, September 2008, four families of drivers are supported or partially supported. The ath5k driver supports Atheros WLAN based chipsets, the b43 driver supports the 802.11 B/G family of wireless chips Broadcom produces, libertas_tf supports the Marvell 88W83886 USB device as found in the OLPC XO-1 laptop, and the zd1211rw driver covers a large proportion of USB-wireless devices on the consumer market as these are based on the ZyDAS ZD1211. Several months after the acquisition, Atheros rebranded the ZyDAS ZD1211 chip to AR5007UG.

=== Are there any platforms where Sugar runs on? ===
:The Sugar Learning Platform is a leading learning platform that began in the famous One Laptop Per Child project. It is used every day by nearly 3 million children around the world. [http://sugarizer.org/ Sugarizer] is a web implementation of the platform and runs on every device - from tiny Raspberry Pi computers to small Android and iOS phones to tablets and to laptops and desktops. It has 3 broad components:

:1. Web Application: a web application that runs in modern web browsers
:2. Application: an installable app for every operating system
:3. Server: a nodejs/express server for applications to connect with

:Enjoy the experience and help us reach every child on every device in every country.

== Sugar Labs ==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== What is Sugar Labs? ===
:Sugar Labs, a non-profit foundation, serves as a support base and gathering place for the community of educators and software developers who want to extend the Sugar platform and who have been creating Sugar-compatible applications.

=== What is the mission of Sugar Labs? ===
:The overarching mission of Sugar Labs is to support the Sugar platform through software development, and community outreach and support. The purpose of the Sugar platform is provide a software and content environment that enhances learning. Towards this end, Sugar is designed to facilitate learners to “explore, express, debug, and critique.”

=== What are the principles that guide Sugar Labs? ===
:Sugar Labs subscribes to principle that learning thrives within a culture of freedom of expression, hence it has a natural affinity with the free software movement (Please see [[Sugar_Labs#Principles|Principles]] page in this wiki for more details). The core Sugar platform has been developed under a GNU General Public License (GPL); individual activities may be under different licenses.

=== What is the relationship of Sugar Labs to One Laptop per Child? ===
:Sugar was originally developed as the user interface (UI) for the One Laptop per Child (OLPC) XO-1 laptop. Sugar Labs was established as an independent entity in order to facilitate the growth of Sugar beyond any single hardware platform. While Sugar Labs has a cooperative working relationship with OLPC, it is by no means an exclusive or proprietary relationship. Sugar Labs is not bound to any specific hardware platform or Linux distribution (Please see [[Supported systems]]).

:Sugar Labs is the upstream community for the Sugar project. Sugar Labs welcomes a close working relationship with OLPC. Sugar Labs also welcomes cooperation with other laptop and computer manufacturers and software and content providers.

:OLPC and Sugar Labs are not diverging, we are on the same page; we are both hoping to fund and support Sugar so that we can continue to provide the best learning experience for children. The Sugar Labs initiative is consistent with taking Sugar to the next level; this is not inconsistent with what OLPC is doing. Any help from outside or inside OLPC should help establish Sugar as a more stable and better product.

=== What is the standard Sugar license? ===
:Materials created by the Sugar Labs contributors are usually shared on GNU GPL free software license.

=== What is a Sugar Activity? ===
:Activity is a small educational application (like this one) built into Sugar. Anyone can create an activity, you too...!

=== Who is upstream for Sugar? ===
:Sugar Labs is the upstream for the Sugar project.

=== Who is Sugar Labs? ===
:Sugar is a community project, so it is the sum of those of you who participate. Sugar Labs was started by some Sugar-community members: [[User:Walter|Walter Bender]], [[User:ChristophD|Christoph Derndorfer]], [[User:Bert|Bert Freudenberg]], [[User:Marcopg|Marco Pesenti Gritti]], [[User:Bernie|Bernardo Innocenti]], Aaron Kaplan, [[User:Erikos|Simon Schampijer]], and [[User:Tomeu|Tomeu Vizoso]]. We have rules of [[Sugar Labs/Governance | governance]] that have been vetted by a process of public discussion.

=== How do I get involved? ===
:Please see the [[Sugar Labs/Getting Involved|Getting Involved]] page in this wiki.

=== How do I learn more about Sugar Labs? ===
:Check out the following additional FAQs, and join the IAEP mailing list and ask us about anything related to the project that isn't related to code.

* [[Activity Team/FAQ|Activities]]
* [[Deployment Team/FAQ|Deployment]]
* [[Design Team/FAQ|Design]]
* [[Development Team/FAQ|Development]]
* [[Documentation Team/FAQ|Documentation]]
* [[Education Team/FAQ|Education]]
* [[Infrastructure Team/FAQ|Infrastructure]]
* [[Local Labs/FAQ|Local Labs]]
* [[Marketing Team/FAQ|Marketing]]
* [[Math4Team/FAQ|Math4 Project]]
* [[Oversight Board|Oversight Board]]
* [[Sugar on a Stick/FAQ|Sugar on a Stick]]
* [[BugSquad/FAQ|Testing]]
* [[Translation Team/FAQ|Translation]]
* [[Wiki Team/FAQ| Wiki]]

[[Category:General public]]
[[Category:FAQ]]

Sugar Labs/FAQ

2017-01-07T16:11:58Z

Emilyo11: /* Sugar Labs */

{{Graduate|Some useful stuff in here}}

<noinclude>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</noinclude>
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]''', or follow the question links at the top of the major sections, or visit [[:Category:FAQ]].
__TOC__
==Sugar==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== What is Sugar? ===
:Sugar is an educational software platform built with the Python programming language and based on the principles of cognitive and social constructivism. See [[What is Sugar?]].

=== Who is doing Sugar development? ===
:Sugar is a community project where all work is done by volunteers. You can get an idea of the people involved from the [[Development Team/Release/Modules]] page.

=== Does Sugar support Android? ===
: Not at this time, although there are some developers working to change that situation. See this [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg13765.html mailing list thread].

=== What makes Sugar different from other educational software platforms? ===
* See [[Marketing Team/Website#Website_2|Website sandbox]].
:The Sugar interface, in its departure from the desktop metaphor for computing, is the first serious attempt to create a user interface that is based on both cognitive and social constructivism: learners should engage in authentic exploration and collaboration. It is based on three very simple principles about what makes us human: (1) everyone is a teacher and a learner; (2) humans by their nature are social beings; and (3) humans by their nature are expressive. These are the pillars of a user experience for learning.

:Sugar also considers two aphorisms: (1) you learn through doing, so if you want more learning, you want more doing; and (2) love is a better master than duty—you want people to engage in things that are authentic to them, things that they love.

:The presence of other people is inherent to the Sugar interface: collaboration is a first-order experience. Students and teachers engage in a dialog with each other, support each other, critique each other, and share ideas.

:Sugar is also discoverable: it can accommodate a wide variety of users, with different levels of skill in terms of reading, language, and different levels of experience with computing. It is easy to approach, and yet it doesn't put an upper bound on personal expression; one can peel away layers and go deeper and deeper, with few restrictions.

:Sugar is based on Python, an interpreted language, allowing the direct appropriation of ideas: in whatever realm the learner is exploring—music, browsing, reading, writing, programming, graphics, etc.—they are able to drill deeper; they are not going to hit a wall, since they can, at every level, engage in debugging both their personal expression and the very tools that they use for that expression.

==Using Sugar==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== Who can use Sugar and how do they benefit? ===
:Sugar is a free software project, freely available to anyone who wants to use it or improve upon it.

:The Sugar platform was designed for young children (K–6), but it is finding applicability in a number of different venues where the simplicity of design maps is an enabler, e.g., mobile applications, the elderly, etc.

:'''Why Sugar?''' Sugar will engage even the youngest learner in the use of computation as a powerful "thing to think with." They will quickly become proficient in using the computer as a tool to engage in authentic problem-solving. Sugar users develop skills that help them in all aspects of life.
* Sugar comes with hundreds of tools for discovery through exploring, expressing, and sharing: browsing, writing, rich media, etc.
* Sugar comes with a built-in collaboration system: peer-to-peer learning; always-on support; and single-click sharing.
* Sugar comes with built-in tools for reflection; a built-in portfolio assessment tool that serves as a forum for discussion between children, their parents, and their teachers.
* The Sugar learning platform is discoverable: it uses simple means to reach to complex ends with no upper bound on where you can reach.
* Sugar is designed for local appropriation: it has built-in tools for making changes and improvements and a growing global community of support.
* Sugar puts an emphasis on learning through doing and debugging: more engaged learners are to tackle authentic problems.
* Sugar is available in a wide variety of forms: as part of GNU/Linux distributions; LiveUSB/CD; and in virtual machines or emulation.
:There is a further summary of the Sugar benefits [[Deployment Team/Small_deployment_guide#Why_Sugar|here]].

=== How can I get online with the Live USB/CD, and what can I do then? ===

:The Live USB device must be inserted into a USB port on your computer, the Live CD must be in your CD-ROM or DVD drive, when you start your computer, and your BIOS settings should be set to first look for an operating system there on the USB or CD-ROM device. If the settings are okay, the Live USB/CD will boot.

:After a little while, you will be prompted for a name and you will get to choose the colour of your avatar. This is a small X, like the arms and legs of a human, with an O as the head above the X. This is "you".

:Wait a little longer, and you will see "yourself" in the middle of the screen. Just below "you", is your journal, where everything you do is recorded.

:In the top left corner of the Frame is a circle of smaller circles. This is your Neighbourhood-circle. At the moment, only nearby wireless access points are visible as small coloured circles - more colour inside means better signal strength. Let your mouse pointer hover above a circle to see the name of the wireless network. A small padlock means you need to supply a username and password to access the network. Click the circle you would like to access. It should be a wireless network you know will grant you Internet access once you are connected. If the network is protected with a padlock, you will be prompted for a valid username and password at this point, so give these and click the OK-button. If everything is okay, you are now connected.

:You should soon see many small avatars like your own in your neighbourhood. Hover your mouse pointer above them to see their usernames.

:In the top left corner next to the Neighbourhood-circle, is your Friends-circle. You don't have any Sugar-friends at the moment, so this will be empty. Next to the Friends-circle is a circle with a single dot - that's right - it means you. Click the You-circle, and you will get back to you and your activities.

:Surrounding your avatar on the Home screen are many activities, so click the one that looks like a cartoon talk bubble to start the Chat-activity or some other activity - like the Paint-activity or the Calculator-activity. After a little while, the new activity opens. In the top right corner of all activities is a small menu, which says "Share with:". Click this to unfold the options, and choose Neighbourhood by clicking on it.

:Click the Neighbourhood-circle again, and you will notice that the activity is now visible to everyone in your neighbourhood. If you hover your mouse button over an activity in your neighbourhood, a small menu will unfold where you may choose to join the activity by selecting "Join" from the activity's menu. Remember, your neighbourhood is the entire world! People in other parts of the world may be working or sleeping when you start sharing your activities, so be patient - it might be many hours before anyone is available for a chat. Enjoy! :-)

=== Does Sugar run on {GNU/Linux, Fedora, Ubuntu, SUSE, MAC OS, Windows, etc.}? ===
:Please refer to the [[Supported systems]] page for an up-to-date list of supported systems.

=== Is there an image of the OS that can be run on a PC? ===
:You can download a Live USB image at [[Sugar on a Stick]] and a Live CD version of Sugar at http://wiki.laptop.org/go/LiveCd, or run Sugar natively on a [[Supported systems|supported system]]. (The language can be set from the Sugar-control-panel or My Settings link on the avatar panel.)

=== Does Sugar run on an ASUS Eee PC (or other "ultra-mobile" or "mini" PCs)?===
Yes. If it can run GNU/Linux and GNOME, it can run Sugar. Try [[Sugar on a Stick]] as a way to get started, but you should be able install it natively as well.

=== Is it possible to have mesh support with the Live USB/CD ? ===
Q: If I understand this correctly, mesh support means your wireless card functions as both an access point/router and a network node. In short, your wireless computer can pass along packages from nearby wireless computers and the other way round. Do you need special wireless cards for this, or is this a driver/software issue that could be fixed in the Live CD, so that more people can experience mesh networks?

:A: Yes, it will be possible to have [http://www.open80211s.org/trac/wiki/HOWTO-0.2.1 mesh support] with the Live CD shortly, provided you have a suitable wireless card.

:[http://www.o11s.org/ open80211s] is an open-source implementation of the emerging IEEE 802.11s wireless mesh standard. It has been accepted in the mainline Linux kernel and is included in release 2.6.26. The resulting software will run on GNU/Linux on commodity PC hardware.

:Open80211s is based on the mac80211 wireless stack and should run on any of the wireless cards that mac80211 supports. At present, September 2008, four families of drivers are supported or partially supported. The ath5k driver supports Atheros WLAN based chipsets, the b43 driver supports the 802.11 B/G family of wireless chips Broadcom produces, libertas_tf supports the Marvell 88W83886 USB device as found in the OLPC XO-1 laptop, and the zd1211rw driver covers a large proportion of USB-wireless devices on the consumer market as these are based on the ZyDAS ZD1211. Several months after the acquisition, Atheros rebranded the ZyDAS ZD1211 chip to AR5007UG.

== Sugar Labs ==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== What is Sugar Labs? ===
:Sugar Labs, a non-profit foundation, serves as a support base and gathering place for the community of educators and software developers who want to extend the Sugar platform and who have been creating Sugar-compatible applications.

=== What is the mission of Sugar Labs? ===
:The overarching mission of Sugar Labs is to support the Sugar platform through software development, and community outreach and support. The purpose of the Sugar platform is provide a software and content environment that enhances learning. Towards this end, Sugar is designed to facilitate learners to “explore, express, debug, and critique.”

=== What are the principles that guide Sugar Labs? ===
:Sugar Labs subscribes to principle that learning thrives within a culture of freedom of expression, hence it has a natural affinity with the free software movement (Please see [[Sugar_Labs#Principles|Principles]] page in this wiki for more details). The core Sugar platform has been developed under a GNU General Public License (GPL); individual activities may be under different licenses.

=== What is the relationship of Sugar Labs to One Laptop per Child? ===
:Sugar was originally developed as the user interface (UI) for the One Laptop per Child (OLPC) XO-1 laptop. Sugar Labs was established as an independent entity in order to facilitate the growth of Sugar beyond any single hardware platform. While Sugar Labs has a cooperative working relationship with OLPC, it is by no means an exclusive or proprietary relationship. Sugar Labs is not bound to any specific hardware platform or Linux distribution (Please see [[Supported systems]]).

:Sugar Labs is the upstream community for the Sugar project. Sugar Labs welcomes a close working relationship with OLPC. Sugar Labs also welcomes cooperation with other laptop and computer manufacturers and software and content providers.

:OLPC and Sugar Labs are not diverging, we are on the same page; we are both hoping to fund and support Sugar so that we can continue to provide the best learning experience for children. The Sugar Labs initiative is consistent with taking Sugar to the next level; this is not inconsistent with what OLPC is doing. Any help from outside or inside OLPC should help establish Sugar as a more stable and better product.

=== What is the standard Sugar license? ===
:Materials created by the Sugar Labs contributors are usually shared on GNU GPL free software license.

=== What is a Sugar Activity? ===
:Activity is a small educational application (like this one) built into Sugar. Anyone can create an activity, you too...!

=== Who is upstream for Sugar? ===
:Sugar Labs is the upstream for the Sugar project.

=== Who is Sugar Labs? ===
:Sugar is a community project, so it is the sum of those of you who participate. Sugar Labs was started by some Sugar-community members: [[User:Walter|Walter Bender]], [[User:ChristophD|Christoph Derndorfer]], [[User:Bert|Bert Freudenberg]], [[User:Marcopg|Marco Pesenti Gritti]], [[User:Bernie|Bernardo Innocenti]], Aaron Kaplan, [[User:Erikos|Simon Schampijer]], and [[User:Tomeu|Tomeu Vizoso]]. We have rules of [[Sugar Labs/Governance | governance]] that have been vetted by a process of public discussion.

=== How do I get involved? ===
:Please see the [[Sugar Labs/Getting Involved|Getting Involved]] page in this wiki.

=== How do I learn more about Sugar Labs? ===
:Check out the following additional FAQs, and join the IAEP mailing list and ask us about anything related to the project that isn't related to code.

* [[Activity Team/FAQ|Activities]]
* [[Deployment Team/FAQ|Deployment]]
* [[Design Team/FAQ|Design]]
* [[Development Team/FAQ|Development]]
* [[Documentation Team/FAQ|Documentation]]
* [[Education Team/FAQ|Education]]
* [[Infrastructure Team/FAQ|Infrastructure]]
* [[Local Labs/FAQ|Local Labs]]
* [[Marketing Team/FAQ|Marketing]]
* [[Math4Team/FAQ|Math4 Project]]
* [[Oversight Board|Oversight Board]]
* [[Sugar on a Stick/FAQ|Sugar on a Stick]]
* [[BugSquad/FAQ|Testing]]
* [[Translation Team/FAQ|Translation]]
* [[Wiki Team/FAQ| Wiki]]

[[Category:General public]]
[[Category:FAQ]]

Sugar Labs/FAQ

2017-01-07T16:04:29Z

Emilyo11: /* How can I get online with the Live USB/CD, and what can I do then? */

{{Graduate|Some useful stuff in here}}

<noinclude>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</noinclude>
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]''', or follow the question links at the top of the major sections, or visit [[:Category:FAQ]].
__TOC__
==Sugar==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== What is Sugar? ===
:Sugar is an educational software platform built with the Python programming language and based on the principles of cognitive and social constructivism. See [[What is Sugar?]].

=== Who is doing Sugar development? ===
:Sugar is a community project where all work is done by volunteers. You can get an idea of the people involved from the [[Development Team/Release/Modules]] page.

=== Does Sugar support Android? ===
: Not at this time, although there are some developers working to change that situation. See this [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg13765.html mailing list thread].

=== What makes Sugar different from other educational software platforms? ===
* See [[Marketing Team/Website#Website_2|Website sandbox]].
:The Sugar interface, in its departure from the desktop metaphor for computing, is the first serious attempt to create a user interface that is based on both cognitive and social constructivism: learners should engage in authentic exploration and collaboration. It is based on three very simple principles about what makes us human: (1) everyone is a teacher and a learner; (2) humans by their nature are social beings; and (3) humans by their nature are expressive. These are the pillars of a user experience for learning.

:Sugar also considers two aphorisms: (1) you learn through doing, so if you want more learning, you want more doing; and (2) love is a better master than duty—you want people to engage in things that are authentic to them, things that they love.

:The presence of other people is inherent to the Sugar interface: collaboration is a first-order experience. Students and teachers engage in a dialog with each other, support each other, critique each other, and share ideas.

:Sugar is also discoverable: it can accommodate a wide variety of users, with different levels of skill in terms of reading, language, and different levels of experience with computing. It is easy to approach, and yet it doesn't put an upper bound on personal expression; one can peel away layers and go deeper and deeper, with few restrictions.

:Sugar is based on Python, an interpreted language, allowing the direct appropriation of ideas: in whatever realm the learner is exploring—music, browsing, reading, writing, programming, graphics, etc.—they are able to drill deeper; they are not going to hit a wall, since they can, at every level, engage in debugging both their personal expression and the very tools that they use for that expression.

==Using Sugar==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== Who can use Sugar and how do they benefit? ===
:Sugar is a free software project, freely available to anyone who wants to use it or improve upon it.

:The Sugar platform was designed for young children (K–6), but it is finding applicability in a number of different venues where the simplicity of design maps is an enabler, e.g., mobile applications, the elderly, etc.

:'''Why Sugar?''' Sugar will engage even the youngest learner in the use of computation as a powerful "thing to think with." They will quickly become proficient in using the computer as a tool to engage in authentic problem-solving. Sugar users develop skills that help them in all aspects of life.
* Sugar comes with hundreds of tools for discovery through exploring, expressing, and sharing: browsing, writing, rich media, etc.
* Sugar comes with a built-in collaboration system: peer-to-peer learning; always-on support; and single-click sharing.
* Sugar comes with built-in tools for reflection; a built-in portfolio assessment tool that serves as a forum for discussion between children, their parents, and their teachers.
* The Sugar learning platform is discoverable: it uses simple means to reach to complex ends with no upper bound on where you can reach.
* Sugar is designed for local appropriation: it has built-in tools for making changes and improvements and a growing global community of support.
* Sugar puts an emphasis on learning through doing and debugging: more engaged learners are to tackle authentic problems.
* Sugar is available in a wide variety of forms: as part of GNU/Linux distributions; LiveUSB/CD; and in virtual machines or emulation.
:There is a further summary of the Sugar benefits [[Deployment Team/Small_deployment_guide#Why_Sugar|here]].

=== How can I get online with the Live USB/CD, and what can I do then? ===

:The Live USB device must be inserted into a USB port on your computer, the Live CD must be in your CD-ROM or DVD drive, when you start your computer, and your BIOS settings should be set to first look for an operating system there on the USB or CD-ROM device. If the settings are okay, the Live USB/CD will boot.

:After a little while, you will be prompted for a name and you will get to choose the colour of your avatar. This is a small X, like the arms and legs of a human, with an O as the head above the X. This is "you".

:Wait a little longer, and you will see "yourself" in the middle of the screen. Just below "you", is your journal, where everything you do is recorded.

:In the top left corner of the Frame is a circle of smaller circles. This is your Neighbourhood-circle. At the moment, only nearby wireless access points are visible as small coloured circles - more colour inside means better signal strength. Let your mouse pointer hover above a circle to see the name of the wireless network. A small padlock means you need to supply a username and password to access the network. Click the circle you would like to access. It should be a wireless network you know will grant you Internet access once you are connected. If the network is protected with a padlock, you will be prompted for a valid username and password at this point, so give these and click the OK-button. If everything is okay, you are now connected.

:You should soon see many small avatars like your own in your neighbourhood. Hover your mouse pointer above them to see their usernames.

:In the top left corner next to the Neighbourhood-circle, is your Friends-circle. You don't have any Sugar-friends at the moment, so this will be empty. Next to the Friends-circle is a circle with a single dot - that's right - it means you. Click the You-circle, and you will get back to you and your activities.

:Surrounding your avatar on the Home screen are many activities, so click the one that looks like a cartoon talk bubble to start the Chat-activity or some other activity - like the Paint-activity or the Calculator-activity. After a little while, the new activity opens. In the top right corner of all activities is a small menu, which says "Share with:". Click this to unfold the options, and choose Neighbourhood by clicking on it.

:Click the Neighbourhood-circle again, and you will notice that the activity is now visible to everyone in your neighbourhood. If you hover your mouse button over an activity in your neighbourhood, a small menu will unfold where you may choose to join the activity by selecting "Join" from the activity's menu. Remember, your neighbourhood is the entire world! People in other parts of the world may be working or sleeping when you start sharing your activities, so be patient - it might be many hours before anyone is available for a chat. Enjoy! :-)

=== Does Sugar run on {GNU/Linux, Fedora, Ubuntu, SUSE, MAC OS, Windows, etc.}? ===
:Please refer to the [[Supported systems]] page for an up-to-date list of supported systems.

=== Is there an image of the OS that can be run on a PC? ===
:You can download a Live USB image at [[Sugar on a Stick]] and a Live CD version of Sugar at http://wiki.laptop.org/go/LiveCd, or run Sugar natively on a [[Supported systems|supported system]]. (The language can be set from the Sugar-control-panel or My Settings link on the avatar panel.)

=== Does Sugar run on an ASUS Eee PC (or other "ultra-mobile" or "mini" PCs)?===
Yes. If it can run GNU/Linux and GNOME, it can run Sugar. Try [[Sugar on a Stick]] as a way to get started, but you should be able install it natively as well.

=== Is it possible to have mesh support with the Live USB/CD ? ===
Q: If I understand this correctly, mesh support means your wireless card functions as both an access point/router and a network node. In short, your wireless computer can pass along packages from nearby wireless computers and the other way round. Do you need special wireless cards for this, or is this a driver/software issue that could be fixed in the Live CD, so that more people can experience mesh networks?

:A: Yes, it will be possible to have [http://www.open80211s.org/trac/wiki/HOWTO-0.2.1 mesh support] with the Live CD shortly, provided you have a suitable wireless card.

:[http://www.o11s.org/ open80211s] is an open-source implementation of the emerging IEEE 802.11s wireless mesh standard. It has been accepted in the mainline Linux kernel and is included in release 2.6.26. The resulting software will run on GNU/Linux on commodity PC hardware.

:Open80211s is based on the mac80211 wireless stack and should run on any of the wireless cards that mac80211 supports. At present, September 2008, four families of drivers are supported or partially supported. The ath5k driver supports Atheros WLAN based chipsets, the b43 driver supports the 802.11 B/G family of wireless chips Broadcom produces, libertas_tf supports the Marvell 88W83886 USB device as found in the OLPC XO-1 laptop, and the zd1211rw driver covers a large proportion of USB-wireless devices on the consumer market as these are based on the ZyDAS ZD1211. Several months after the acquisition, Atheros rebranded the ZyDAS ZD1211 chip to AR5007UG.

== Sugar Labs ==
: '''[[Talk:Sugar Labs/FAQ | Post new questions here]]'''.
=== What is Sugar Labs? ===
:Sugar Labs, a non-profit foundation, serves as a support base and gathering place for the community of educators and software developers who want to extend the Sugar platform and who have been creating Sugar-compatible applications.

=== What is the mission of Sugar Labs? ===
:The overarching mission of Sugar Labs is to support the Sugar platform through software development, and community outreach and support. The purpose of the Sugar platform is provide a software and content environment that enhances learning. Towards this end, Sugar is designed to facilitate learners to “explore, express, debug, and critique.”

=== What are the principles that guide Sugar Labs? ===
:Sugar Labs subscribes to principle that learning thrives within a culture of freedom of expression, hence it has a natural affinity with the free software movement (Please see [[Sugar_Labs#Principles|Principles]] page in this wiki for more details). The core Sugar platform has been developed under a GNU General Public License (GPL); individual activities may be under different licenses.

=== What is the relationship of Sugar Labs to One Laptop per Child? ===
:Sugar was originally developed as the user interface (UI) for the One Laptop per Child (OLPC) XO-1 laptop. Sugar Labs was established as an independent entity in order to facilitate the growth of Sugar beyond any single hardware platform. While Sugar Labs has a cooperative working relationship with OLPC, it is by no means an exclusive or proprietary relationship. Sugar Labs is not bound to any specific hardware platform or Linux distribution (Please see [[Supported systems]]).

:Sugar Labs is the upstream community for the Sugar project. Sugar Labs welcomes a close working relationship with OLPC. Sugar Labs also welcomes cooperation with other laptop and computer manufacturers and software and content providers.

:OLPC and Sugar Labs are not diverging, we are on the same page; we are both hoping to fund and support Sugar so that we can continue to provide the best learning experience for children. The Sugar Labs initiative is consistent with taking Sugar to the next level; this is not inconsistent with what OLPC is doing. Any help from outside or inside OLPC should help establish Sugar as a more stable and better product.

=== Who is upstream for Sugar? ===
:Sugar Labs is the upstream for the Sugar project.

=== Who is Sugar Labs? ===
:Sugar is a community project, so it is the sum of those of you who participate. Sugar Labs was started by some Sugar-community members: [[User:Walter|Walter Bender]], [[User:ChristophD|Christoph Derndorfer]], [[User:Bert|Bert Freudenberg]], [[User:Marcopg|Marco Pesenti Gritti]], [[User:Bernie|Bernardo Innocenti]], Aaron Kaplan, [[User:Erikos|Simon Schampijer]], and [[User:Tomeu|Tomeu Vizoso]]. We have rules of [[Sugar Labs/Governance | governance]] that have been vetted by a process of public discussion.

=== How do I get involved? ===
:Please see the [[Sugar Labs/Getting Involved|Getting Involved]] page in this wiki.

=== How do I learn more about Sugar Labs? ===
:Check out the following additional FAQs, and join the IAEP mailing list and ask us about anything related to the project that isn't related to code.

* [[Activity Team/FAQ|Activities]]
* [[Deployment Team/FAQ|Deployment]]
* [[Design Team/FAQ|Design]]
* [[Development Team/FAQ|Development]]
* [[Documentation Team/FAQ|Documentation]]
* [[Education Team/FAQ|Education]]
* [[Infrastructure Team/FAQ|Infrastructure]]
* [[Local Labs/FAQ|Local Labs]]
* [[Marketing Team/FAQ|Marketing]]
* [[Math4Team/FAQ|Math4 Project]]
* [[Oversight Board|Oversight Board]]
* [[Sugar on a Stick/FAQ|Sugar on a Stick]]
* [[BugSquad/FAQ|Testing]]
* [[Translation Team/FAQ|Translation]]
* [[Wiki Team/FAQ| Wiki]]

[[Category:General public]]
[[Category:FAQ]]

Sugar Labs/Current Events

2016-12-20T13:20:54Z

Emilyo11: /* Sugar Digest */

<noinclude>
== What's new ==

This page is updated every few weeks with notes from the Sugar Labs community. (The digest is also sent to the community-news at sugarlabs.org list, blogged at [http://walterbender.org/ walterbender.org], and [[Archive/Current Events|archived here]].) If you would like to contribute, please send email to [[User:walter|walter]] at sugarlabs.org by the weekend. (Also visit <span class="plainlinks">[http://planet.sugarlabs.org planet.sugarlabs.org].</span>)

</noinclude>
== Sugar Digest ==

1. Marvin Minsky was fond of saying that there is nothing more dangerous than when a roomful of people all agree with each other. We don't have to worry about that in the Sugar community!!! Marvin also observed that "it's very important to have friends who can solve problems you can't." The diversity of our community is its strength.

Another Marvin quote relevant to our current quest to define ourselves as a community: "Our present culture may be largely shaped by this strange idea of isolating children's thought from adult thought. Perhaps the way our culture educates its children better explains why most of us come out as dumb as they do, than it explains how some of us come out as smart as they do." As Laura Vargas put it recently, Sugar Labs is a community "where you can learn how to design, develop and deploy high-quality Free Software." Within our community, children and adults are working together.

2. Sam Parkinson is our new release manager. Sam, a former GCI winner from Australia, has been responsible for many of the patches to the Sugar toolkit over the past few releases and has also been one of our most prelific code reviewers. Martin Abente, our release manager for the past four releases, has agreed to mentor Sam during the transition. Tip of the hat to Martin for all of his contributions and continued support.

3. Mariah Noelle Villarreal just got back from the Google Code-in reunion, where she represented Sugar Labs. She had a chance to meet Ezequiel and Piotr, our two winners, and spend time with members of the other participating projects. Mariah brought multiple copies of Sugar on a Stick to hand out and reports that there was a positive reception, especially among some of the parents in attendance. She also voiced some disappointment with the degree of awareness of Software Libre among attendees. FWIW, Devin Ulibarri and I are working on a new paper regarding the importance of Software Libre to education. Stay tuned.

4. I just got back from a trip to Santiago, Chile, where I was hosted by the education division of Fundación Chile. (Cecilia Rodriguez Alcala Garcia, formally of Educa Paraguay, was responsible for my invitation to run some workshops and give a keynote address at Creo Chile.) The theme of my workshops was programming as a vehicle for engaging in critical thinking. I introduced Turtle Blocks and Music Blocks first to a team of engineers from throughout the foundation, then to an executive group, then to a "hacker" group attending the Creo Chile event, and finally to a group of children and their parents. I was assisted by Andrea Vasquez Garcia, without whom I would have been lost. In addition, I participated in a workshop run by a local rap artist, Nelson Bobadilla Alvarado, and an educator, Francisca Petrovich Ursic. We did a collaborative, interactive Music Blocks program, whereby we could programmatically participate in the performance. A bit crude, but I learned a lot in the process. My keynote, which I have uploaded to [[File:FchBender2016.pdf]], focused on Sugar and the role of Software Libre in education.

In the workshop for executives, I was challenged to write a Turtle program to calculate the expected value of the number of coin flips required to get three heads or three tails in a row. My response can be seen at [http://walterbender.github.io/turtleblocksjs/?file=threeinarow.tb].

One sub-goal of my trip was to seek advice regarding a reference machine for Sugar. Alas, I was not yet able to get a definitive answer, as the foundation does not directly distribute hardware and the ministry of education has a wide variance in the types of machines they distribute. But I hope to get some feedback on this topic in the coming weeks.

While I was in Santiago, Chile defeated Mexico in the Copa América. I credited the win to Sugar (and the Chilean futbol shirt I was wearing). Hopefully it will mean that Sugar will find a warn reception in Chile.

5. Google Summer of Code is well underway. Mentors are writing mid-term evaluations this week. Be sure to check out the great work being done by our interns, including [https://github.com/sugarlabs/edit-fonts-activity], [http://vikramahujagsoc.blogspot.in/], [https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/313#discussion_r63140566], [http://musicblocks.net/2016/06/13/multiple-rhythm-rulers/], [https://www.youtube.com/watch?v=FAHUOBJ7fqk], and [https://iamutkarshtiwari.wordpress.com/].

6. On the flight back from Santiago, I wrote a Python script to convert glif files into Turtle Block projects. (Tip of the hat to Eli Heuer for providing me some sample glif files.) The results are quite fun (See [http://walterbender.github.io/musicblocks/?file=a.tb]). Next up, a version where each knot and control point is represented by a turtle, and thus the glyph will be editable.

=== In the Community ===

7. Gary Stager has written a nice [https://www.edsurge.com/news/2016-06-07-as-the-maker-movement-turns-45-gary-stager-pays-tribute-to-m-i-t-computing-pioneer-cynthia-solomon tribute to Cynthia Solomon] in celebration of the 45th anniversary of the Maker Movement.

8. Please join us every 1st Friday of the month at UTC 1900 on irc.freenode.net #sugar-meeting.

=== Tech Talk ===

9. Sam has announced the second release leading up to Sugar 0.110. Recent changes include:
* James Cameron fixed Gtk 3.6 compatibility and an edge case with bundle erasure
* Utkarsh Tiwari added a WiFi password visibility toggle
* Abhijit Patel added a PopWindow api for sugar toolkit
* Sebastian Silva fixed Broadway compatibility for `sugar-activity`
* The [http://wiki.sugarlabs.org/go/Features/Tick_based_animation smooth animations feature] landed
* Git submodules are now supported by the bundlebuilder
* Improved Gtk 3.20 support
* Misc bug/interface fixes

Sam has been busy updating the [https://developer.sugarlabs.org/sugar3/sugar3.graphics.icon.html API documentation] and is soliciting feedback. Also, Sam has updated Fedora [https://copr.fedorainfracloud.org/coprs/samtoday/sugar/ COPR] with the new versions of the Sugar packages. Tarballs for sugar, sugar-toolkit-gtk3 and sugar-artwork are in the usual places on the download server [http://download.sugarlabs.org/sources/sucrose/glucose/].

10. Tom Gilliard reports the availability of Sugar spins for Fedora24 ([http://dl.fedoraproject.org/pub/alt/unofficial/releases/24/x86_64/Fedora-SoaS-Live-x86_64-24-20160614.n.0.iso x86_64], [http://dl.fedoraproject.org/pub/alt/unofficial/releases/24/i386/Fedora-SoaS-Live-i386-24-20160614.n.0.iso i386]).

=== Sugar Labs ===

11. Please visit our [http://planet.sugarlabs.org planet].

<noinclude>

== Community News archive ==

An '''[[Archive/Current Events|archive]]''' of this digest is available.

==Planet==

<span class="plainlinks">The Sugar Labs [http://planet.sugarlabs.org/ Planet] is found [http://planet.sugarlabs.org/ here].</span>

==Sugar in the news==
{|
|-
|align=right valogn=top|02 Nov 2016||'''BBVA''' – [https://www.youtube.com/watch?v=puA2NH2uVQQ&feature=youtu.be Sociedad de la Creatividad - desafíos de hoy para el futuro] (video)
|-
|align=right valign=top|23 Oct 2016||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/locales/la-computacion-es-una-herramienta-para-promover-agentes-de-cambio-1530653.html La computación es una herramienta para promover agentes de cambio]
|-
|align=right valign=top|23 Jul 2016||'''La Tercera''' – [http://www.latercera.com/noticia/tendencias/2016/07/27-689886-9-walter-bender-cuando-todos-estan-de-acuerdo-con-todos-es-bastante-peligroso.shtml Cuando todos están de acuerdo con todos es bastante peligroso]
|-
|align=right valign=top|02 May 2016||'''Fedora Insider''' – [http://www.linuxinsider.com/story/Fedora-Based-Sugar-on-a-Stick-Is-One-Sweet-Desktop-83446.html Fedora-based Sugar on a Stick is one sweet desktop]
|-
|align=right valign=top|09 Feb 2016||'''www.montevideo.com''' – [http://www.montevideo.com.uy/auc.aspx?299096 DOS URUGUAYOS ENTRE GANADORES DEL CONCURSO GOOGLE CODE-IN]
|-
|align=right valign=top|28 Aug 2015||'''Musson Foundation''' – [https://youtu.be/HZtVv2nlP8Y Jamaica Girls Code] (video)
|-
|align=right valign=top|28 Aug 2015||'''Google Open Source''' – [http://google-opensource.blogspot.com/2015/08/my-sweet-adventures-with-sugar-labs-and.html My sweet adventures with Sugar Labs and Google Code-in]
|-
|align=right valign=top|09 May 2015||'''La Prensa''' – [http://www.laprensa.com.ni/2015/05/09/nacionales/1829026-de-alumnos-a-creadores-de-su-aprendizaje De alumnos a creadores de su aprendizaje]
|-
|align=right valign=top|30 Apr 2015||'''Diario La República''' – [http://www.republica.com.uy/investigador-sueco-visito-uruguay-para-conocer-el-proyecto-butia/514419/ Swedish researcher visited Uruguay to meet the project Butiá]
|-
|align=right valign=top|24 Apr 2015||'''Jamaica Observer''' – [http://www.jamaicaobserver.com/magazines/career/Future-coders_18811152 Future Coders]
|-
|align=right valign=top|24 Apr 2015||'''Jamaica Information Service''' – [http://jis.gov.jm/state-minister-urges-young-women-enter-ict-sector/ State minister urges young women to enter ICT sector]
|-
|align=right valign=top|6 Feb 2015||'''Cromo''' – [http://www.cromo.com.uy/2015/02/el-chico-google/ El chico Google]
|-
|align=right valign=top|5 Feb 2015||'''Capital Noticias Canelones''' – [https://www.google.com/url?q=https%3A%2F%2Fwww.facebook.com%2Fvideo.php%3Fv%3D400864146741913%26set%3Dvb.246080195553643%26type%3D2%26theater&sa=D&sntz=1&usg=AFQjCNFGeMoL69EHGf4Kudmoxo47duJf_Q El joven de Canelones, Ignacio Rodríguez, ganó nuevamente la competencia de programación de Google.] (video)
|-
|align=right valign=top|3 Feb 2015||'''montevideo.com''' – [http://www.montevideo.com.uy/auc.aspx?261076 Código joven]
|-
|align=right valign=top|1 Dec 2014||'''Google Open Source Blog''' – [http://google-opensource.blogspot.com/2014/12/3-2-1-code-in-inviting-teens-to.html 3, 2, 1 Code-in: Inviting teens to contribute to open source]
|-
|align=right valign=top|7 Oct 2014||'''Kauffman Report''' – [http://www.kauffman.org/blogs/policy-dialogue/2014/august/paraguay-thirsty-for-21st-century-education Paraguay Thirsty for 21st-Century Education]
|-
|align=right valign=top|25 Sept 2014||'''ANEP''' – [http://www.anep.edu.uy/anep/index.php/897-fecundo-intercambio-de-jovenes-de-todo-el-mundo-en-encuentro-de-programadores Fecundo intercambio de jovenes de todo el mundo en encuentro de programadores]
|-
|align=right valign=top|12 Jun 2014||'''Producción Nacional''' – [https://www.youtube.com/watch?v=0YbRCMRpstg Innovando con XO] (video)
|-
|align=right valign=top|28 Apr 2014||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/suplementos/centinela/paraguay-educa-realiza-talleres-de-programacion-y-de-robotica-1238493.html Paraguay Educa realiza talleres de programación y de robótica]
|-
|align=right valign=top|21 Apr 2014||'''El Tiempo''' – [http://www.eltiempo.com/vida-de-hoy/educacion/entrevista-de-el-tiempo-a-walter-bender_13855020-4 'Cada niño podría ser un maestro del 'software': Walter Bender]
|-
|align=right valign=top|2 Apr 2014||'''vera.tv''' – [http://tv.vera.com.uy/video/7012 Antel vuelta a clases] (video)
|-
|align=right valign=top|4 Feb 2014||'''La Diaria''' – [http://ladiaria.com.uy/articulo/2014/2/en-codigo/ En código]
|-
|align=right valign=top|24 Jan 2014||'''Espectador''' – [http://www.espectador.com/sociedad/283177/entre-los-ganadores-del-concurso-anual-de-programacion-de-google-code-in-hay-nuevamente-un-joven-uruguayo Entre los ganadores del concurso anual de programación de Google Code-in hay nuevamente un joven uruguayo]
|-
|align=right valign=top|23 Jan 2014||'''El Pais''' – [http://www.elpais.com.uy/vida-actual/ensena-profesores-ahora-premia-google.html Le enseña a sus profesores y ahora lo premia Google]
|-
|align=right valign=top|20 Jan 2014||'''Google Open Source Blog''' – [http://google-opensource.blogspot.com/ Google Code-in 2013 - drumroll please!]
|-
|align=right valign=top|28 Nov 2013||'''BBVA Paraguay''' – [http://www.youtube.com/watch?v=y_wTBs2ektI&feature=youtu.be&utm_source=buffer&utm_campaign=Buffer&utm_content=bufferbac3c&utm_medium=twitter Turtle Art Day in Caacupé] (video)
|-
|align=right valign=top|17 Oct 2013||'''ANTEL Integra''' – [http://www.integra.antel.com.uy/2013/10/educacion/turtle-art-la-plataforma-del-butia/ Turtle Art: la plataforma del Butiá]
|-
|align=right valign=top|14 Oct 2013||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/locales/software-libre-es-tema-de-paneles-en-la-cumbre-627064.html Software libre es tema de paneles en la cumbre]
|-
|align=right valign=top|14 Oct 2013||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/locales/programar-ayuda-a-los-ninos-a-pensar-628059.html Programar ayuda a los niños a pensar]
|-
|align=right valign=top|14 Oct 2013||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/locales/hoy-es-el-dia-de-tortugarte-en-caacupe-627470.html Hoy es el Día de TortugArte, en Caacupé]
|-
|align=right valign=top|14 Oct 2013||'''ABC Color''' – [http://www.abc.com.py/edicion-impresa/locales/las-tic-en-la-educacion-son-clave-para-el-desarrollo-del-pais-aseguran-627469.html Las TIC en la educación son clave para el desarrollo del país, aseguran]
|-
|align=right valign=top|12 Oct 2013||'''Cromo''' – [http://www.cromo.com.uy/2013/10/mhijo-el-programador/ M’hijo el programador]
|-
|align=right valign=top|08 Aug 2013||'''News1''' – [http://news1.kr/articles/1273059 Interview with former MIT Media Lab director] (in Korean)
|-
|align=right valign=top|12 Jul 2013||'''RIT''' – [http://www.rit.edu/news/story.php?id=50113 ‘Sky Time’ video game selected for White House Champions of Change event July 23]
|-
|align=right valign=top|28 Apr 2013||'''BBC Mundo''' – [http://www.bbc.co.uk/mundo/noticias/2013/04/130422_programadores_adolescentes_am.shtml Los programadores adolescentes premiados por Google]
|-
|align=right valign=top|07 Feb 2013||'''el Neuvo Herald''' – [http://www.elnuevoherald.com/2013/02/07/1402134/joven-uruguayo-brilla-como-programador.html Joven uruguayo brilla como programador y es distinguido por Google]
|-
|align=right valign=top|06 Feb 2013||'''el Observador''' – [http://www.elobservador.com.uy/noticia/242936/joven-uruguayo-gana-la-competencia-google-code/ Joven uruguayo gana la competencia Google Code] (Also see [http://people.sugarlabs.org/aguz/gci-press-interviews.html GCI press interviews])
|-
|align=right valign=top|Jan 2013||'''Raspberry Pi Geek''' – [http://www.raspberry-pi-geek.com/Archive/2013/01/Pi-with-Sugar-and-turtles-as-a-learning-tool/(language)/eng-US Pi with Sugar and turtles as a learning tool]
|-
|align=right valign=top|07 Sep 2012||'''NDTV''' – [http://gadgets.ndtv.com/laptops/news/one-laptop-per-child-initiative-a-hit-in-rural-india-263867 One Laptop Per Child initiative a hit in rural India]
|-
|align=right valign=top|08 Jul 2012||'''Estado de S. Paulo''' – [http://blogs.estadao.com.br/radar-tecnologico/2012/07/08/para-educar/ Para educar]
|-
|align=right valign=top|24 Apr 2012||'''Pacific Standard''' – [http://www.psmag.com/education/one-laptop-per-child-redux-38589/ OLPC Redux]
|-
|align=right valign=top|12 Apr 2012||'''Huffington Post''' – [http://www.huffingtonpost.com/ketaki-desai/one-laptop-per-child_b_1417801.html Hult Global Case Challenge: One Laptop Per Child]
|-
|align=right valign=top|30 Mar 2012||'''newswise''' – [http://www.newswise.com/articles/sugar-on-a-stick-helps-kids-learn-how-to-learn “Sugar on a Stick” Helps Kids Learn How to Learn]
|-
|align=right valign=top|11 Jan 2012||'''Boston Herald''' – [http://bostonherald.com/business/technology/general/view.bg?articleid=1394672 One Laptop Per Child screening $100 tablet]
|-
|align=right valign=top|10 Jan 2012||'''ars technica''' – [http://arstechnica.com/gadgets/news/2012/01/charging-by-crank-bicycle-waterwheel-hands-on-with-the-olpc-xo-30-tablet.ars Crank, bicycle, and waterwheel: hands-on with the OLPC XO 3.0 tablet]
|-
|align=right valign=top|08 Jan 2012||'''The Verge''' – [http://www.theverge.com/2012/1/8/2691733/olpc-xo-3-0-tablet-pictures-video OLPC XO 3.0 tablet preview: impressions, video, and pictures]
|-
|align=right valign=top|07 Jan 2012||'''The Verge''' – [http://www.theverge.com/2012/1/6/2688604/olpc-xo-3-0-tablet-a-8-inch-tablet-with-android-and-sugar-options-for OLPC XO 3.0 tablet: an 8-inch tablet for $100, with Android and Sugar options for the children]
|-
|align=right valign=top|23 Dec 2011||'''Miller-McCune''' – [http://www.miller-mccune.com/education/one-laptop-per-child-redux-38589/ One Laptop Per Child Redux]
|-
|align=right valign=top|18 Oct 2011||'''BDU''' – [http://www.youtube.com/watch?v=IcpzVnuFP0M&feature=channel_video_title Robotics in Uruguay] (video)
|-
|align=right valign=top|11 Aug 2011||'''Berlin.de''' – [http://www.berlin.de/projektzukunft/presse/aktuelle-pressemitteilung/detailseite/datum/2011/08/08/gewinner-des-berliner-landeswettbewerbs-zu-open-source-stehen-fest/ Gewinner des Berliner Landeswettbewerbs zu Open Source stehen fest]
|-
|align=right valign=top|25 Jul 2011||'''CCC Classic''' – [http://wiki.sugarlabs.org/go/File:CCC-StartingLine.jpg Garmin-sugarlabs development cycling team at Crit starting line]
|-
|align=right valign=top|25 Jul 2011||'''CCC Classic''' – [http://wiki.sugarlabs.org/go/File:CCC-after.jpg Garmin-sugarlabs development cycling team after Crit]
|-
|align=right valign=top|13 Apr 2011||'''framablog''' – [http://www.framablog.org/index.php/post/2011/04/13/sugar-labs-education-walter-bender L'expérience Sugar Labs préfigure-t-elle une révolution éducative du XXIe siècle?]
|-
|align=right valign=top|05 Apr 2011||'''Businesswire''' – [http://www.businesswire.com/news/home/20110405006842/en/Government-Peru-Expands-Laptop-Child-Program-Local The Government of Peru Expands the One Laptop Per Child Program with Local Manufacturing]
|-
|align=right valign=top|31 Jan 2011||'''Sundance''' – [http://www.youtube.com/watch?v=ABp7GkLgN94 A Day in the Life – Peru]
|-
|align=right valign=top|01 Dec 2010||'''velonation''' – [http://www.velonation.com/News/ID/6564/Sugar-Labs-to-back-Garmin-Cervelos-development-team-in-unique-arrangement.aspx Sugar Labs to back Garmin-Cervelo’s development team in unique arrangement]
|-
|align=right valign=top|28 Oct 2010||'''UCR''' – [http://www.ucr.ac.cr/noticias/2010/10/28/nuevas-tecnologias-deben-estar-al-alcance-de-todos-los-ninos-y-ninas.html Nuevas tecnologías deben estar al alcance de todos los niños y niñas]
|-
|align=right valign=top|05 Oct 2010||'''xconomy''' – [http://www.xconomy.com/boston/2010/10/05/one-ecosystem-per-child-walter-bender-and-olpc-reunite-to-enhance-learning-and-grow-economies-in-developing-nations/#comments One Ecosystem per Child]
|-
|align=right valign=top|08 Sep 2010||'''FLOSS Weekly''' – [http://twit.tv/floss134 Sugar Labs]
|-
|align=right valign=top|09 Aug 2010||'''ABC digital''' – [http://www.abc.com.py/abc/nota/165361-Indicadores-constatan-el-impacto-positivo-en-el-aprendizaje-de-ninos/ Indicadores constatan el impacto positivo en el aprendizaje de niños]
|-
|align=right valign=top|23 Jun 2010||'''ABC digital''' – [http://www.abc.com.py/abc/nota/137383-Xo-para-todas-las-escuelas-de-Caacup%C3%A9/ Xo para todas las escuelas de Caacupé]
|-
|align=right valign=top|21 Jun 2010||'''La Nacion''' – [http://www.lanacion.com.py/noticias_um-312380.htm “Buscamos que los niños no solo usen softwares, sino que puedan crear uno”]
|-
|align=right valign=top|20 Jun 2010||'''UltimaHora.com''' – [http://www.ultimahora.com/notas/332297-La-laptop-une-a-padres,-alumnos-y-docentes La laptop une a padres, alumnos y docentes]
|-
|align=right valign=top|15 Jun 2010||'''The H''' – [http://www.h-online.com/open/news/item/OLPC-XO-1-5-software-updated-1022936.html OLPC XO-1.5 software updated]
|-
|align=right valign=top|10 Jun 2010||'''engadget''' – [http://www.engadget.com/2010/06/11/sugar-on-a-stick-hits-3-0-teaches-us-about-a-new-kind-of-fruit/ Sugar on a Stick hits 3.0, teaches us about a new kind of fruit]
|-
|align=right valign=top|27 May 2010||'''Pro Linux DE''' – [http://www.pro-linux.de/news/1/15722/sugar-on-a-stick-v3-freigegeben.html Sugar on a Stick v3 freigegeben] (German)
|-
|align=right valign=top|27 May 2010||'''NY Times''' – [http://bits.blogs.nytimes.com/2010/05/27/olpc-partners-with-marvell-to-launch-100-tablet/?src=busln One Laptop Per Child Project Works With Marvell to Produce a $100 Tablet]
|-
|align=right valign=top|27 May 2010||'''PC World''' – [http://www.pcworld.com/businesscenter/article/197361/olpc_rules_out_windows_for_xo3.html OLPC Rules out Windows for XO-3]
|-
|align=right valign=top|03 May 2010||'''WXXI: Mixed Media''' – [http://www.publicbroadcasting.net/wxxi/news.newsmain/article/0/0/1644648/news/Mixed.Media.Special.Edition.05-03-10 Interview with Walter Bender] (audio)
|-
|align=right valign=top|03 May 2010||'''Linux Magazine''' – [http://www.linux-magazine.com/Online/News/OLPC-Computers-for-Palestinian-Refugee-Children OLPC Computers for Palestinian Refugee Children]
|-
|align=right valign=top|14 Apr 2010||'''National Science Foundation''' – [http://www.nsf.gov/discoveries/disc_summ.jsp?cntn_id=116638 XO Laptops Inspire Learning In Birmingham, Alabama] ([http://www.nsf.gov/cgi-bin/good-bye?http://www.youtube.com/watch?v=inxOg-dt6rw video])
|-
|align=right valign=top|02 Apr 2010||<div class="NavFrame collapsed"><div class="NavHead">'''Dailymotion''' – [http://www.dailymotion.com/video/xct0lp_un-jour-a-paris-ensembles-pour-olpc_tech Un jour... à Paris... ensembles pour OLPC et Sugar...] (video) </div><div class="NavContent">{{#widget:Daily Motion
|id=xct0lp
|width=420
|height=336
}}</div></div>
|-
|align=right valign=top|15 Mar 2010||'''nbc13.com''' – [http://www2.nbc13.com/vtm/news/local/article/video_birmingham_city_students_opt_to_spend_spring_break_in_class_xo_comput/138224/ Birmingham City students opt to spend spring break in class, XO computer camps] (video)
|-
|align=right valign=top|18 Feb 2010||'''LWN''' – [https://lwn.net/SubscriberLink/374790/8dc41b030f4562b1/ Karma targets easier creation of educational software]
|-
|align=right valign=top|05 Feb 2010||'''iprofesional''' – [http://tecnologia.iprofesional.com/notas/93943-La-PC-barata-de-Negroponte-desembarca-en-la-Argentina-para-pelear-contra-Intel.html La PC barata de Negroponte desembarca en la Argentina para pelear contra Intel]
|-
|align=right valign=top|14 Jan 2010||'''AALF''' – [http://www.aalf.org/articles/view.php?ArticleID=86 Open Systems for Broader Change]
|-
|align=right valign=top|03 Jan 2010||'''Educacion 2.0''' – [http://www.educdoscero.com/2009/12/plan-ceibal-el-libro.html PLAN CEIBAL, El Libro]
|-
|align=right valign=top|14 Dec 2009||'''xconomy''' – [http://www.xconomy.com/boston/2009/12/14/sugar-gets-sweeter-former-olpc-exec-walter-bender-on-netbooks-e-books-blueberry-and-cloudberry/?single_page=true Sugar gets sweeter]
|-
|align-right valign=top|10 Dec 2009||'''ars technica''' – [http://arstechnica.com/open-source/reviews/2009/12/sugar-software-environment-gets-sweeter-with-version-2.ars Sugar software environment gets sweeter with version 2]
|-
|align=right valign=top|09 Dec 2009||'''Wired''' – [http://www.wired.com/geekdad/2009/12/new-sugar-on-a-stick-brings-much-needed-improvements/ New Sugar on a Stick Brings Much Needed Improvements]
|-
|align=right valign=top|08 Dec 2009||'''engadget''' – [http://www.engadget.com/2009/12/08/sugar-on-a-stick-os-goes-to-2-0-gets-blueberry-coating-and-crea/ Sugar on a Stick OS goes to 2.0, gets Blueberry coating and creamy Fedora 12 center (video)]
|-
|align=right valign=top|07 Dec 2009||'''Teleread.org''' – [http://www.teleread.org/2009/12/07/sugar-on-a-stick-what-it-means-for-e-books-and-education/ Sugar on a Stick: What it means for e-books and education]
|-
|align=right valign=top|27 Nov 2009||'''CNET Japan''' – [http://japan.cnet.com/special/story/0,2000056049,20404126,00.htm 「コードを見せて、もっと良くなるよ」と言える子どもが生まれる--Sugar Labsが描く未来]
|-
|align=right valign=top|16 Nov 2009||'''zanichelli''' – [http://scienze.zanichelli.it/notizie/2009/11/16/intervista-walter-bender-e-sugar-labs/ software libero a scuola]
|-
|align=right valign=top|12 Nov 2009||'''opensuse.org''' – [http://en.opensuse.org/Marketing/Team/11_2_Launch/Announcement openSUSE 11.2 Released]
|-
|align=right valign=top|07 Nov 2009||'''My Broadband News''' – [http://mybroadband.co.za/news/Software/10351.html Mandriva 2010 packs a punch [and Sugar]]
|-
|align=right valign=top|06 Nov 2009||'''GhanaWeb''' – [http://www.ghanaweb.com/GhanaHomePage/NewsArchive/artikel.php?ID=171387 Open education and an IT-enabled economic growth in Ghana: Musings of a dutiful citizen]
|-
|align=right valign=top|26 Oct 2009||'''Linux Magazine ES''' – [http://www.linux-magazine.es/issue/54/078-083_SugarLM54.pdf Software Libre como apoyo al aprendizaje]
|-
|align=right valign=top|09 Oct 2009||'''interdisciplines''' – [http://www.interdisciplines.org/mobilea2k/papers/2 OLPC and Sugar: mobility through the community]
|-
|align=right valign=top|08 Oct 2009||'''IBM developerWorks''' – [http://www.ibm.com/developerworks/linux/library/l-linux-10th-anniversary/index.html 10 important Linux developments everyone should know about]
|-
|align=right valign=top|01 Oct 2009||'''OLPC France''' – [http://olpc-france.org/wiki/index.php?title=Interview_Walter_Bender_au_SugarCamp Interview Walter Bender au SugarCamp]
|-
|align=right valign=top|25 Sep 2009||'''The Inquirer''' – [http://www.theinquirer.net/inquirer/news/1555781/one-laptop-per-child-marches One Laptop per Child marches on]
|-
|align=right valign=top|18 Sep 2009||'''Groklaw''' – [http://www.groklaw.net/article.php?story=20090918110925298 The Role of Free Software in Education]
|-
|align=right valign=top|18 Sep 2009||'''Reuters''' – [http://www.reuters.com/article/pressRelease/idUS97755+18-Sep-2009+PRN20090918 Sugar Labs and Free Software Foundation Celebrate Software Freedom Day]
|-
|align=right valign=top|17 Sep 2009||'''ICTDev.org''' – [http://ictdev.org/pulse/20090916/ict4d/dreaming-again-one-laptop-child Dream Again with One Laptop per Child]
|-
|align=right valign=top|26 Aug 2009||'''Latinux''' – [http://www.latinuxmagazine.com/ediciones/pdf/latinux-magazine-VolINum1-beta.pdf Azúcar en una memoria USB]
|-
|align=right valign=top|03 Aug 2009||'''Wired: Geek Dad''' – [http://www.wired.com/geekdad/2009/08/inventing-a-new-paradigm-sugarlabs-and-the-sugar-ui/ Inventing a New Paradigm: SugarLabs and the Sugar UI]
|-
|align=right valign=top|30 Jul 2009||'''Zanichelli''' – [http://scienze.zanichelli.it/notizie/2009/06/30/sugar-on-a-stick-imparare-insieme/ Sugar on a Stick: imparare insieme]
|-
|align=right valign=top|23 Jul 2009||'''Everything USB''' – [http://www.everythingusb.com/recycle-usb-17077.html RecycleUSB.com - Donate your Flash Drives for a Good Cause]
|-
|align=right valign=top|22 Jul 2009||'''OLPC France''' – [http://olpc-france.org/blog/2009/07/sugar-mauvaise-presse-et-mise-au-point/ Sugar : mauvaise presse et mise au point]
|-
|align=right valign=top|13 Jul 2009||'''Spiegel Online''' – [http://www.spiegel.de/netzwelt/tech/0,1518,634718,00.html Das zuckersüße Leichtbau-Linux]
|-
|align=right valign=top|07 Jul 2009||'''ComputerWorldUK''' – [http://www.computerworlduk.com/community/blogs/index.cfm?entryid=2334&blogid=14 Gran Canaria Desktop Summit: a Study in Contrasts]
|-
|align=right valign=top|06 Jul 2009||'''Windows Forest''' – [http://www.forest.impress.co.jp/article/2009/06/30/olpcusb.html USBメモリなどから“OLPC”用のOSを利用できる「Sugar on a Stick」が無償公開]
|-
|align=right valign=top|02 Jul 2009||'''Howard County Library''' – [http://hclibrary.org/opensource/?p=228 Sugar on a Stick]
|-
|align=right valign=top|27 Jun 2009||'''Deutschlandfunk''' – [http://www.dradio.de/dlf/sendungen/computer/989765/ Süßes für die Kleinen: Sugar ist Linux speziell für Kinder] (in Deutsch)
|-
|align=right valign=top|26 Jun 2009||'''EduTech''' – [http://blogs.worldbank.org/edutech/sugar-on-a-stick-and-other-delectables-praise-for-the-lowly-usb-drive Sugar on a stick, and other delectables (praise for the lowly USB drive)]
|-
|align=right valign=top|26 Jun 2009||'''ars technica''' – [http://arstechnica.com/open-source/news/2009/06/sugar-on-a-stick-brings-sweet-taste-of-linux-to-classrooms.ars Sugar on a Stick brings sweet taste of Linux to classrooms]
|-
|align=right valign=top|24 Jun 2009||'''BBC''' – [http://news.bbc.co.uk/2/hi/technology/8117064.stm OLPC software to power aging PCs]
|-
|align=right valign=top|24 Jun 2009||'''Technology Review''' – [http://www.technologyreview.com/computing/22919/ $100 Laptop Becomes a $5 PC]
|-
|align=right valign=top|15 Jun 2009||'''TechSavvyKids''' – [http://techsavvykids.podomatic.com/player/web/2009-06-15T11_15_29-07_00 Episode 10 FOSSVT: Sugar on a Stick] (audio)
|-
|align=right valign=top|10 Jun 2009||'''LWN.net''' – [http://lwn.net/SubscriberLink/336910/3878a88c0c27f977/ Sugar moves from the shadow of OLPC]
|-
|align=right valign=top|27 May 2009||'''LWN.net''' – [http://lwn.net/SubscriberLink/334911/cf451c615cfdaa33/ Activities and the move to context-oriented desktops] (subscriber link)
|-
|align=right valign=top|27 May 2009||'''Business Wire''' – [http://www.businesswire.com/portal/site/home/permalink/?ndmViewId=news_view&newsId=20090527006237&newsLang=en Dailymotion Launches Support for Open Video Formats and Video HTML Tag]
|-
|align=right valign=top|01 May 2009||'''Guysoft''' – [http://guysoft.wordpress.com/2009/05/01/nokia-n810-running-olpc-sugar/ Nokia N810 Running OLPC Sugar]
|-
|align=right valign=top|29 Apr 2009||'''El Mercurio''' – [http://www.mer.cl/modulos/catalogo/Paginas/2009/04/29/MERSTVS017AA2904.htm?idnoticia=CC116HNVJ120090429 Así se vivió la fiesta del software libre]
|-
|align=right valign=top|27 Apr 2009||'''ostatic''' – [http://ostatic.com/blog/sugar-on-a-stick-good-for-kids-minds-and-school-budgets Sugar on a Stick: Good for Kids' Minds (and School Budgets)]
|-
|align=right valign=top|25 Apr 2009||'''Free Software Magazine''' – [http://www.freesoftwaremagazine.com/columns/bittersweet_facts_about_olpc_and_sugar The Bittersweet Facts about OLPC and Sugar]
|-
|align=right valign=top|24 Apr 2009||'''ars technica''' – [http://arstechnica.com/open-source/news/2009/04/sugar-labs-releases-beta-of-live-usb-learning-environment.ars First taste: Sugar on a Stick learning platform]
|-
|align=right valign=top|22 Apr 2009||'''Betanews''' – [http://www.betanews.com/article/Beta-of-Live-USB-Sugar-OS-opens/1240409113#talkback Beta of Live USB Sugar OS opens]
|-
|align=right valign=top|27 Mar 2009||'''Mass High Tech''' – [http://www.masshightech.com/stories/2009/03/23/weekly3-Google-promotes-summer-open-source-internships.html Google promotes summer open-source internships]
|-
|align=right valign=top|18 Mar 2009||'''Metropolis''' – [http://www.metropolismag.com/story/20090318/a-good-argument A Good Argument]
|-
|align=right valign=top|16 Mar 2009||'''Laptop Magazine''' – [http://blog.laptopmag.com/sugar-labs-new-version-of-sugar-learning-platform-is-netbook-and-pc-ready Sugar Labs’ New Version of Sugar Learning Platform Is Netbook and PC Ready]
|-
|align=right valign=top|16 Mar 2009||'''Market Watch''' – [http://www.marketwatch.com/news/story/sugar-labs-nonprofit-announces-new/story.aspx?guid={EF4B8934-0046-465F-AD4D-E82FBCE8F1EC}&dist=msr_7 Sugar Labs Nonprofit Announces New Version of Sugar Learning Platform for Children, Runs on Netbooks and PCs]
|-
|align=right valign=top|14 Feb 2009||'''OLPC Learning Club – DC''' – [http://olpclearningclub.org/meetings/learning-learning-on-a-stick/ Learning Learning on a Stick]
|-
|align=right valign=top|05 Feb 2009||'''xconomy''' – [http://www.xconomy.com/boston/2009/02/05/sugar-beyond-the-xo-laptop-walter-bender-on-olpc-sucrose-084-and-sugar-on-a-stick/ Sugar Beyond the XO Laptop: Walter Bender on OLPC, Sucrose 0.84, and “Sugar on a Stick”]
|-
|align=right valign=top|26 Jan 2009||'''Linus Magazine''' – [http://www.linux-magazine.com/content/view/full/32999 Sugar Defies OLPC Cutbacks]
|-
|align=right valign=top|19 Jan 2009||'''Feeding the Penguins''' – [http://morgancollett.wordpress.com/2009/01/19/the-status-of-sugar-post-olpc/ The status of Sugar, post-OLPC]
|-
|align=right valign=top|16 Jan 2009||'''OLPC News''' – [http://www.olpcnews.com/software/sugar/xo_acer_aspire_one_thin_client_sugar.html Sugar on Acer Aspire One & Thin Client via LTSP]
|-
|align=right valign=top|12 Jan 2009||'''Bill Kerr''' – [http://billkerr2.blogspot.com/2009/01/thoughts-about-olpc-cutbacks.html thoughts about olpc cutbacks]
|-
|align=right valign=top|07 Jan 2009||'''ars technica''' – [http://arstechnica.com/news.ars/post/20090107-olpc-downsizes-half-of-its-staff-cuts-sugar-development.html OLPC downsizes half of its staff, cuts Sugar development]
|-
|align=right valign=top|06 Jan 2009||'''OLPC News''' – [http://www.olpcnews.com/sales_talk/microsoft/how_microsoft_got_xp_on_the_xo.html An Inside Look at how Microsoft got XP on the XO]
|-
|align=right valign=top|30 Dec 2008||'''OLPC News''' – [http://www.olpcnews.com/software/sugar/sugar_labs_status_at_six_month.html Sugar Labs Status at Six Months]
|-
|align=right valign=top|22 Dec 2008||'''The GNOME Project''' – [http://www.gnome.org/press/releases/2008-12-sugarlabs.html Sugar Labs, the nonprofit behind the OLPC software, is joining the GNOME Foundation]
|-
|align=right valign=top|16 Dec 2008||'''Feeding the Penguins''' – [http://morgancollett.wordpress.com/2008/12/15/sugar-git-repository-change/ Sugar git repository change]
|-
|align=right valign=top|14 Dec 2008||'''NPR''' – [http://www.npr.org/templates/story/story.php?storyId=96825852 Laptop Deal Links Rural Peru To Opportunity, Risk (Part 2)]
|-
|align=right valign=top|13 Dec 2008||'''NPR''' – [http://www.npr.org/templates/story/story.php?storyId=96510072 Laptops May Change The Way Rural Peru Learns (Part 1)]
|-
|align=right valign=top|09 Dec 2008||'''SFC''' – [http://conservancy.softwarefreedom.org/news/2008/dec/09/sugar/ Sugar Labs joins Conservancy]
|-
|align=right valign=top|31 Oct 2008||'''Linux Devices''' – [http://www.linuxdevices.com/news/NS3023016259.html An OLPC dilemma: Linux or Windows?]
|-
|align=right valign=top|10 Oct 2008||'''Feeding the Penguin''' – [http://morgancollett.wordpress.com/2008/10/10/sugar-on-ubuntu/ Sugar on Ubuntu]
|-
|align=right valign=top|21 Sep 2008||'''Groklaw''' – [http://www.groklaw.net/article.php?story=20080920181151638 Interview with Walter Bender of Sugar Labs]
|-
|align=right valign=top|17 Sep 2008||'''Bill Kerr''' – [http://billkerr2.blogspot.com/2008/09/sugar-labs.html Sugar Labs]
|-
|align=right valign=top|16 Sep 2008||'''Open Source''' – [http://opensource.sfsu.edu/node/562 Sugar everywhere]
|-
|align=right valign=top|28 Aug 2008||'''OLPC News''' – [http://www.olpcnews.com/use_cases/education/an_answer_to_question_22.html An answer to Walter Bender's question 22]
|-
|align=right valign=top|20 Aug 2008||'''OLPC News''' – [http://www.olpcnews.com/software/operating_system/sugarizing_it_intel_classmate_2.html Sugarize it: Intel Classmate 2]
|-
|align=right valign=top|08 Aug 2008||'''Investor's Business Daily''' – [http://www.investors.com/Tech/TechExecQA.asp?artid=303074322503278 'Learning' Vs. Laptop Was Issue]
|-
|align=right valign=top|06 Aug 2008||'''OLPC News''' – [http://www.olpcnews.com/people/leadership/23_questions_on_technology_education.html Twenty-three Questions on Technology and Education]
|-
|align=right valign=top|18 Jul 2008||'''Bill Kerr''' – [http://billkerr2.blogspot.com/2008/07/evaluating-sugar-in-developed-world.html evaluating Sugar in the developed world]
|-
|align=right valign=top|28 Jun 2008||'''OLPC News''' – [http://www.olpcnews.com/software/sugar/cutting_edge_sugar_ui.html A Cutting Edge Sugar User Interface Demo]
|-
|align=right valign=top|18 Jun 2008||'''PC World''' – [http://www.pcworld.com/businesscenter/article/147265/olpc_spinoff_developing_ui_for_intels_classmate_pc.html OLPC Spin-off Developing UI for Intel's Classmate PC]
|-
|align=right valign=top|17 Jun 2008||'''Datamation''' – [http://itmanagement.earthweb.com/osrc/article.php/12068_3753376_1 If Business Succeeds with GNU/Linux, Why Not OLPC?]
|-
|align=right valign=top|11 Jun 2008||'''LinuxInsider''' – [http://www.linuxinsider.com/story/Sugar-Labs-Walter-Bender-on-the-Sweetness-of-Collaborative-Learning-63354.html The Sweetness of Collaborative Learning]
|-
|align=right valign=top|06 Jun 2008||'''Bill Kerr''' – [http://billkerr2.blogspot.com/2008/06/untangling-free-sugar-and.html untangling Free, Sugar, and Constructionism]
|-
|align=right valign=top|06 Jun 2008||'''Open Education''' – [http://www.openeducation.net/2008/06/03/walter-bender-discusses-sugar-labs-foundation/ Walter Bender Discusses Sugar Labs Foundation]
|-
|align=right valign=top|06 Jun 2008||'''BusinessWeek''' – [http://prod-blogs.businessweek.com/globalbiz/blog/globespotting/archives/2008/06/olpc_the_educat.html OLPC: The Educational Philosophy Controversy]
|-
|align=right valign=top|05 Jun 2008||'''Code Culture''' – [http://radian.org/notebook/distraction-machine The Distraction Machine]
|-
|align=right valign=top|05 Jun 2008||'''BusinessWeek''' – [http://www.businessweek.com/globalbiz/blog/globespotting/archives/2008/06/olpc_the_open-s.html OLPC: The Open-Source Controversy]
|-
|align=right valign=top|27 May 2008||'''The New York Times''' – [http://bits.blogs.nytimes.com/2008/05/27/why-walter-bender-left-one-laptop-per-child-edited-hold-for-wed-am/ Why Walter Bender Left One Laptop Per Child]
|-
|align=right valign=top|26 May 2008||'''ars technica''' – [http://arstechnica.com/news.ars/post/20080526-former-olpc-software-president-wants-to-expand-sugars-reach.html OLPC software maker splits from X0 hardware, goes solo]
|-
|align=right valign=top|22 May 2008||'''BetaNews''' – [http://www.betanews.com/article/Linux_startup_Sugar_Labs_in_informal_talks_with_four_laptop_makers/1211467857 Linux start-up Sugar Labs in informal talks with four laptop makers]
|-
|align=right valign=top|16 May 2008||'''OSTATIC''' – [http://ostatic.com/162220-blog/olpcs-open-source-sugar-platform-aims-for-new-hardware OLPC's Open Source Sugar Platform Aims for New Hardware]
|-
|align=right valign=top|16 May 2008||'''PCWorld''' – [http://www.pcworld.com/businesscenter/article/146002/bender_forms_group_to_promote_olpcs_sugar_ui.html Bender Forms Group to Promote OLPC's Sugar UI]
|-
|align=right valign=top|16 May 2008||'''MHT''' – [http://masshightech.bizjournals.com/masshightech/stories/2008/05/12/daily35.html Bender jumps from OLPC, founds Sugar Labs]
|-
|align=right valign=top|16 May 2008||'''News.com''' – [http://www.news.com/8301-10784_3-9946242-7.html Sugar Labs will make OLPC interface available for Eee PC, others]
|-
|align=right valign=top|16 May 2008||'''Feeding the Peguins''' – [http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/ The future of Sugar]
|-
|align=right valign=top|16 May 2008||'''Sugar list''' – [http://lists.laptop.org/pipermail/sugar/2008-May/005800.html A few thoughts on SugarLabs]
|-
|align=right valign=top|16 May 2008||'''xconomy''' – [http://www.xconomy.com/2008/05/16/bender-creates-sugar-labs-new-foundation-to-adapt-olpcs-laptop-interface-for-other-machines/ Bender Creates Sugar Labs—New Foundation to Adapt OLPC’s Laptop Interface for Other Machines]
|-
|align=right valign=top|16 May 2008||'''BBC''' – [http://news.bbc.co.uk/2/hi/technology/7405346.stm '$100 laptop' platform moves on]
|-
|align=right valign=top|15 May 2008||'''OLPC wiki''' – [http://wiki.laptop.org/go/AnnounceFAQ Dual-boot XO] Claim: OLPC will not work to port Sugar to Windows.
|-
|align=right valign=top|16 May 2008||'''Softpedia''' – [http://news.softpedia.com/news/Bender-Launches-Sugar-Labs-for-Better-Development-of-OLPC-039-s-Sugar-UI-85881.shtml Bender Launches Sugar Labs for Better Development of OLPC's Sugar UI]
|}

==Press releases==
http://www.sugarlabs.org/press

[[Category:General public]]
</noinclude>

Sugar Labs

2016-12-20T13:08:42Z

Emilyo11: /* Community News */

<noinclude>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}
[[Category:General public]]
[[Category:Team]]</noinclude>__TOC__

===Mission===

[[Trademark|Sugar Labs<sup>®</sup>]] is a volunteer-driven member project of [http://www.sfconservancy.org/ Software Freedom Conservancy], a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates [[Sugar Labs/Getting Involved|volunteers]] around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking [[Donate|funding]] to accelerate development.

== [[:Category:Team|Teams]] ==
Sugar Labs is organized around overlapping Teams. Please use the '''Community''' panel in the wiki sidebar to visit and explore the work and events for each team.
This [[:Category:Team | ''Team'' category page]] collects all Sugar Labs wiki pages with a ''Team'' tag.
== [[:Category:Project|Projects]] ==
Sugar Labs is working on a few [[:Category:Project|projects]] focused on delivering specific goals in a defined time period. The '''Projects''' panel in the wiki sidebar holds our premier projects. Please also see these project home pages:

| [[Harmonic Distribution]] | [https://sugardextrose.org/ Dextrose] | [[Sugar Creation Kit]] | [[Sugar on a Stick]] |

| [[Replacing Textbooks]] | [[Math4Team |Math4 Project]] |

| [[Summer of Code]] |

== Sugar Labs: a community ==
:::::::<span style="font-size: 150%">for learning and software-development</span>
The Sugar development platform is available under the open-source GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs” is a member project of the [http://sfconservancy.org/ Software Freedom Conservancy] (a non-profit foundation to produce and distribute and support the use of free software) and serves as a support base and gathering place for the community of educators and software developers who want to extend the platform and who have been creating Sugar-compatible applications.

=== Education Goals ===
Sugar is useful only to the extent it is used by the learning community. Thus, Sugar Labs is working with educators around the world to focus on these learning challenges:

* To make Sugar and Sugar activities freely and readily available to learners everywhere
* To explore and share best practices
* To provide a forum for discussion and support for technology for learning
* To provide mechanism for evaluation and dissemination of results.

=== Technical Goals ===
Sugar supports the notions that learners should “share by default” and be able to “explore, express, debug, and critique.” Thus Sugar puts an emphasis on “activities” rather than “applications.” The foundation will focus on solving the challenges that are relevant to these aspects of the interface, namely:

* To make it “simple” to share Sugar activities. This will require an architecture that allows discovery of activities.
* To create versions of Sugar that run on multiple operating systems and on multiple hardware platforms. It should be “simple” to install Sugar everywhere. Specifically, it means packaging for every distribution and every virtual machine—removing hardware-related dependencies wherever possible.
* To make it “simple” to write Sugar activities. This necessitates stable APIs and example code that uses these APIs.
* To make Sugar activities even more secure. Our principal user community is comprised of children; they must be protected from malware, phishing, botnets, etc.

=== Community Goals ===
Sugar Labs is here to support community innovation, entrepreneurship, and enterprise. Sugar Labs would like to help community members start projects that help sustain and grow the Sugar technology and learning communities:

* To provide local and regional technical and pedagogical support.
* To create new learning activities and pedagogical practice.
* To provide localization and internationalization of software, content, and documentation.
* To provide integration and customization services.

=== Principles ===
In order for Sugar to be successful, it needs the participation of a large number of people who share common goals while maintaining independence, so that each participant has the ability to act independently. For these reasons, Sugar Labs subscribes to the principles described [http://flors.wordpress.com/2008/05/04/the-paradigm-of-the-open-organization/ here], which are the author's own translation of an [http://web.archive.org/web/20050317231119/http://interactors.coop/organizacionabierta original text in Spanish.]

====Identity====
* Clear mission – Fully disclosed objectives.
* Declared commitments – Affinities and aversions explained.
* Declared outside connections – Relationships with other organizations explicitly listed.

====Structure====
* Horizontal organization – Teams and facilitators work on responsibilities and agreements.
* Identified contributors – Who is who, people are reachable.
* Clear responsibilities – Who is in charge of what.
* Activities described – All of the ongoing work is acknowledged.
See [[Wiki_Team/Guide/Wiki_Structure | Wiki Structure]] for a guide to how the wiki models Sugar Labs' structure.

====Operation====
* Open participation – Anybody can access the information and get a first responsibility.
* Meritocracy – Responsibilities are acquired (or lost) based on one's skills, results, and contributors’ support.
* Voluntary (non-)engagement – Nobody is forced to be involved or to keep responsibilities.

====Information====
* Regular reports – Reported activities and future plans allow monitoring and participation.
* Information accessible – Even internal operational information is available by default.
*: We try to operate '''''[[Archive/Current_Events/2009-06-10#En_plein_air|en plein air]]'''''.
* Explicit confidentiality – It is explained what matters are confidential, why, and who can access them.

====Goods====
* Economic model – Feasibility and sustainability plans are exposed. (Please see/contribute to the discussion [[Sugar Labs/Funding|here]].)
* Resources – Inventory of items detailing who contributed what and why.
* Public accounts – It’s clear where the money comes from and where it goes.
* A special [[Sugar Labs/Thank You|thanks]] to our contributors.

=== [[Sugar Labs/Governance|Governance]] ===
Informed by the above principles, Sugar Labs has a [[Sugar Labs/Governance|governance model]].

==[[Sugar Labs/Roadmap|Roadmap]]==
The [[Sugar Labs/Roadmap|Sugar Community roadmap]] is used to guide our community efforts:
* Mission, Vision, Values
* Distribution
* Deployments
* Quality Assurance
* Infrastructure

==[[Sugar Labs/Current Events|Community News]]==
A [[Sugar Labs/Current Events|current events page]] is updated weekly (usually on Monday morning) with notes from the Sugar Labs community. (The Sugar Digest is also sent to the [http://lists.sugarlabs.org/listinfo/community-news community-news at lists.sugarlabs.org] list and blogged at [http://walterbender.org/ walterbender.org].) If you would like to contribute, please send email to [[User:walter|walter]] at sugarlabs.org by the weekend. (Also visit [http://planet.sugarlabs.org planet.sugarlabs.org].)

An '''[[Archive/Current Events|archive]]''' of Sugar Digests is available.

==[[Sugar Labs/Events | Events Calendar]]==
Sugar [[Sugar Labs/Events | community events]] are posted in a public calendar within the Google Calendar system. The calendar is available in a variety of formats: <span class="plainlinks"> [[Image:XML.gif|link=http://www.google.com/calendar/feeds/6n9a99dr5knag9tp0obc0rncug%40group.calendar.google.com/public/basic]] [[Image:ICal.gif|link=http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics]] [[Image:HTML.gif|link=http://www.google.com/calendar/embed?src=6n9a99dr5knag9tp0obc0rncug%40group.calendar.google.com&ctz=America/New_York]].

Please contact [[User:Walter]] if you'd like to post an event to the calendar. Or simply post it below and it will be included.

== [[Local Labs]] ==
A local Sugar Lab adapts the technology and pedagogy to an area's culture and resources (''e.g.'', developing activities and content specific to a region); helps translate Sugar to the local language(s); supports Sugar deployments in area schools; creates a local community devoted to the Sugar Labs principles, making Sugar more open and sustainable; provides for communication, between the local communities and the global Sugar Labs community; develops Local content and software that can be used not only for local purposes but also for the overall community; hosts, co-hosts or partners in the organization of conferences, workshops, talks and meetings related to the use or development of Sugar.

Please visit these Local Labs:

| [http://co.sugarlabs.org/go/Laboratorios_Azúcar_Colombia Sugar Labs Colombia] | [http://cl.sugarlabs.org/go/Página_Principal Sugar Labs Chile] | [[Sugar Labs DC]] | [http://pe.sugarlabs.org/ Sugar Labs Peru] | [http://ar.sugarlabs.org/ Sugar Labs Argentina] |
<div class="NavFrame "><div class="NavHead">'''Local Lab wiki portal''' </div><div class="NavContent">
{|
|[http://co.sugarlabs.org/go/Laboratorios_Azúcar_Colombia Sugar Labs Colombia]
{{#widget:Iframe
|url=http://co.sugarlabs.org
|width=410
|height=342
|border=1
}}
|[http://cl.sugarlabs.org/go/Página_Principal Chile Local Labs]
{{#widget:Iframe
|url=http://cl.sugarlabs.org
|width=410
|height=342
|border=1
}}
|-
|[[Sugar Labs DC]]
{{#widget:Iframe
|url=http://wiki.sugarlabs.org/go/Sugar_Labs_DC
|width=410
|height=342
|border=1
}}
|[http://pe.sugarlabs.org/ Sugar Labs Peru]
{{#widget:Iframe
|url=http://pe.sugarlabs.org/
|width=410
|height=342
|border=1
}}
|-
|[http://ar.sugarlabs.org/ Sugar Labs Argentina]
{{#widget:Iframe
|url=http://ar.sugarlabs.org
|width=410
|height=342
|border=1
}}
| Who's next?
|}
</div></div>

== Subpages index ==
{{Special:PrefixIndex/Sugar_Labs/}}

Sugar Labs/Members

2016-12-20T13:04:42Z

Emilyo11: /* Applying for membership */

<noinclude>[[Category:Policy]]</noinclude>
== Sugar Labs Membership ==
The Sugar Labs [[Sugar Labs/Members/List|members list]] consists of most of the contributors to the Sugar project. Members can run for election to the [[Oversight Board|Oversight Board]], vote in the elections for the Oversight Board, and suggest [[Sugar Labs/Governance#Sugar Labs Referenda|referenda]].

Any "significant and sustained" contributor to Sugar Labs is eligible for membership. Although it is difficult to specify a precise definition, a [[Sugar_Labs/Sugar_contributors|contributor]] generally must have contributed to a non-trivial improvement of the Sugar project or Sugar Labs activity. Contributions may be code, documentation, translations, maintenance of project-wide resources, ''running a Sugar deployment'', or other non-trivial activities which benefit Sugar Labs. Membership eligibility is an individual determination: while contributions made in the course of employment will be considered, they will generally be ascribed to the individuals involved, rather than accruing to all employees of a "contributing" corporation. The Membership and Elections Committee will oversee membership applications (Please apply by sending email to ''members at sugarlabs.org'').

The Membership and Elections Committee will review the membership list for currency once per year. Any member may join this committee, which is currently staffed by [[User:Sebastian/FuenteLibre|Sebastian Silva]], [[Samson Goddy]], and [mailto:cbigenho@hotmail.com Caryl Bigenho].

== Applying for membership ==
All submissions MUST be sent via email to '''members''' at '''sugarlabs.org'''. Submissions sent to other email addresses or sent after the deadline will not be processed for this year's election. Someone on the '''MEC''' will reply to your query within 2 business days. If you don't get a reply after a week, please contact [[Samson Goddy]] or [mailto:cbigenho@hotmail.com Caryl Bigenho].

In your email, please include:
* Your name
* Your [[IRC]] / Wiki / [http://git.sugarlabs.org Gitorious] username
* A description of your contribution to Sugar Labs, links are preferable.

== Currency assurance policy ==

In order to ensure that the Sugar Labs Membership list is reflective of the current status of the project and its participants, once a year members will be asked to confirm that they still wish to be a Sugar Labs Member. If this request bounces, or if a request has not been replied to after it has been a) resent, b) checked for a more current email address, and c) six months have passed, the member will be sent a removal notice with an invitation to reapply.

The most recent currency review was in January 2016.

== Members List ==
This is our [http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List Sugar_Labs/Members/List].

== Membership Committee ==

For 2015 to 2016-08-01 the Membership and Election Committee was Caryl Bigenho, Samson Goddy, and Sebastian Silva.

The [[Oversight Board]] appoints members to the committee though a normal motion procedure.

== See Also ==
* [[Service/email]]

[[Category:Participate]]

Activity Team/Git Tutorial

2016-12-06T04:46:40Z

Emilyo11: /* Sending a pull-request */

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

== Contributing ==

We use the pull-request model, see [https://help.github.com/articles/about-pull-requests/ github's help on pull-request].

In short, you will:

* file an issue about what you plan to change
* do your changes in a new branch
* push your branch and submit a pull-request for it
* go through the review process until your pull-request is merged
* close your issue

== Activity Repositories ==

To request a new activity repo, email the http://lists.sugarlabs.org/listinfo/systems list with the name of the repo and the github usernames who should have access.

We recommend using the same process as below to develop your own Activities.

== Modifying Sugar ==

Before going through the details on how to submit changes, let's look at the useful tools we provide to assist contributors in the process of modifying Sugar.

If you are hacking on sugar-web, run the testsuit with the karma command inside a osbuild shell:

karma start sugar-web/test/karma.conf.js

We encourage writing new unit tests for new features.

After you do the changes, run:

check

It will run all the code checks and the unit tests making sure you won't break the build when your changes are pushed. If the checks doesn't succeed because of coding style, see the coding style guide [https://developer.sugarlabs.org/web-style.md.html for web] or [https://developer.sugarlabs.org/python-style.md.html for Python]. If a test doesn't pass either your code needs to be fixed or the test need to be adapted.

== Open an Issue ==

We track issues in http://bugs.sugarlabs.org

Generally, each improvement to Sugar should start with an issue discussion, to ensure that work to fix a bug isn't wasted.

== 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.

You should fork the repository first. This step is needed only once. See [https://help.github.com/articles/fork-a-repo/ complete help in github]. Brief instructions follow using [https://github.com/sugarlabs/sugar/ sugar component] as example.

Navigate to the sugar repository, press Fork button, then

git clone https://github.com/YOUR-NAME/sugar.git
cd sugar
git remote add upstream https://github.com/sugarlabs/sugar.git
git fetch upstream

==== 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:

1. Fork the repository.

2. Make the fix.

3. Submit a pull request to the project owner.

4. If the project owner likes your work, they might pull your fix into the original repository!

=== Sending a 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!

Create one branch per topic

git checkout -b topic1

Make one or more commits and push the branch

git push origin topic1

Submit a pull request for the branch. Navigate to your repository page in github, switch to the branch you made, and then press the Pull Request button.

After that, the review process will happen in the pull-request page on github. The process ends with one of this:

1. A reviewer merges your request.

2. A reviewer rejects your request providing reasons (and closes the request)

3. A reviewer requires changes (and closes the request)

In case they ask you for changes, make them using [https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages interactive rebase]

git rebase -i master

Submit the changes to another remote branch

git push origin topic1:topic1-try2

Finally submit the new pull request through the github site as you did before.

Make sure to add "Fixes #1234" to the commit message, being #1234 the number of the issue ticket related to your changes. This way, the ticket will be closed automatically.

=== 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.

Don't forget to pull in changes from the master repository that is 'upstream.' To pull in upstream changes:

git fetch upstream
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.

=== Testing ===

We encourage testing before merging a pull-request.

So instead of merging directly with the "merge" button on github UI, we do a local merge, then test, then push.

See [https://help.github.com/articles/merging-a-pull-request/ github help on merging a pull-request]

The github page for the pull-request will provide you the right commands to do the local merge, similar to the following.

Get the changes from that branch to a new local branch:

git checkout -b SOME-USER-topic1 master
git pull https://github.com/SOME-USER/sugar.git topic1

Test! If everything is fine, merge:

git checkout master
git rebase SOME-USER-topic1
git push origin master

=== 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.

=== Close Issue ===

Once your changes are merged, you should close your issue. Be sure to thank everyone who helped you out along the way :)

== 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

2016-12-06T04:44:39Z

Emilyo11:

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

== Contributing ==

We use the pull-request model, see [https://help.github.com/articles/about-pull-requests/ github's help on pull-request].

In short, you will:

* file an issue about what you plan to change
* do your changes in a new branch
* push your branch and submit a pull-request for it
* go through the review process until your pull-request is merged
* close your issue

== Activity Repositories ==

To request a new activity repo, email the http://lists.sugarlabs.org/listinfo/systems list with the name of the repo and the github usernames who should have access.

We recommend using the same process as below to develop your own Activities.

== Modifying Sugar ==

Before going through the details on how to submit changes, let's look at the useful tools we provide to assist contributors in the process of modifying Sugar.

If you are hacking on sugar-web, run the testsuit with the karma command inside a osbuild shell:

karma start sugar-web/test/karma.conf.js

We encourage writing new unit tests for new features.

After you do the changes, run:

check

It will run all the code checks and the unit tests making sure you won't break the build when your changes are pushed. If the checks doesn't succeed because of coding style, see the coding style guide [https://developer.sugarlabs.org/web-style.md.html for web] or [https://developer.sugarlabs.org/python-style.md.html for Python]. If a test doesn't pass either your code needs to be fixed or the test need to be adapted.

== Open an Issue ==

We track issues in http://bugs.sugarlabs.org

Generally, each improvement to Sugar should start with an issue discussion, to ensure that work to fix a bug isn't wasted.

== 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.

You should fork the repository first. This step is needed only once. See [https://help.github.com/articles/fork-a-repo/ complete help in github]. Brief instructions follow using [https://github.com/sugarlabs/sugar/ sugar component] as example.

Navigate to the sugar repository, press Fork button, then

git clone https://github.com/YOUR-NAME/sugar.git
cd sugar
git remote add upstream https://github.com/sugarlabs/sugar.git
git fetch upstream

==== 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:

1. Fork the repository.

2. Make the fix.

3. Submit a pull request to the project owner.

4. If the project owner likes your work, they might pull your fix into the original repository!

== Sending a 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!

Create one branch per topic

git checkout -b topic1

Make one or more commits and push the branch

git push origin topic1

Submit a pull request for the branch. Navigate to your repository page in github, switch to the branch you made, and then press the Pull Request button.

After that, the review process will happen in the pull-request page on github. The process ends with one of this:

1. A reviewer merges your request.

2. A reviewer rejects your request providing reasons (and closes the request)

3. A reviewer requires changes (and closes the request)

In case they ask you for changes, make them using [https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages interactive rebase]

git rebase -i master

Submit the changes to another remote branch

git push origin topic1:topic1-try2

Finally submit the new pull request through the github site as you did before.

Make sure to add "Fixes #1234" to the commit message, being #1234 the number of the issue ticket related to your changes. This way, the ticket will be closed automatically.

=== 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.

Don't forget to pull in changes from the master repository that is 'upstream.' To pull in upstream changes:

git fetch upstream
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.

=== Testing ===

We encourage testing before merging a pull-request.

So instead of merging directly with the "merge" button on github UI, we do a local merge, then test, then push.

See [https://help.github.com/articles/merging-a-pull-request/ github help on merging a pull-request]

The github page for the pull-request will provide you the right commands to do the local merge, similar to the following.

Get the changes from that branch to a new local branch:

git checkout -b SOME-USER-topic1 master
git pull https://github.com/SOME-USER/sugar.git topic1

Test! If everything is fine, merge:

git checkout master
git rebase SOME-USER-topic1
git push origin master

=== 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.

=== Close Issue ===

Once your changes are merged, you should close your issue. Be sure to thank everyone who helped you out along the way :)

== 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]]