Sugar Labs - User contributions [en]

User:Sridhar

2013-07-09T13:40:46Z

Sridhar:

{{TOCright}}

My name is '''Sridhar Dhanapalan'''. I was the Engineering Manager at [http://www.laptop.org.au OLPC Australia] from 2010 to 2013.

I am known as '''Yama''' online (irc.freenode.net, etc.).

Blog: http://www.dhanapalan.com/blog/

About me: http://www.dhanapalan.com/blog/about/

Summary of FLOSS contributions: https://wiki.ubuntu.com/SridharDhanapalan

OLPC Wiki page: http://wiki.laptop.org/go/User:Sridhar

----

[[User:Sridhar/2011_SLOB_platform|2011 Sugar Labs Oversight Board election platform]]

User:Sridhar

2013-06-04T06:46:35Z

Sridhar: link to OLPC Wiki page

{{TOCright}}

My name is '''Sridhar Dhanapalan''', and I am the Engineering Manager at [http://www.laptop.org.au OLPC Australia].

I am known as '''Yama''' online (irc.freenode.net, etc.).

Blog: http://www.dhanapalan.com/blog/

About me: http://www.dhanapalan.com/blog/about/

Summary of FLOSS contributions: https://wiki.ubuntu.com/SridharDhanapalan

OLPC Wiki page: http://wiki.laptop.org/go/User:Sridhar

----

[[User:Sridhar/2011_SLOB_platform|2011 Sugar Labs Oversight Board election platform]]

Platform Team/Usage Statistics

2012-10-25T05:45:18Z

Sridhar:

== Summary ==

Sugar usage statistics might be very useful from, e.g., an educational or research point of view. Statistics might be anonymous or personalized (by taking special efforts to keep information secure and local for use only by a particular deployment).

== Counter types ==

[[#Statistics|Measured]] statistic values might be one of the following types:

* ''absolute'' value to use as-is, e.g., amount of free disk space;
* ''uptime'' number of seconds since event start, e.g., how long window is active; if event is not active, value will be reset to zero;
* ''gauge'' is for things like temperatures or number of people in a room, i.e., value can grow and fall in time;
* ''counter'' a counter, number of times event was triggered during single time frame; value can be more or equal to zero.

== Statistics ==

All types of statistics are identified by IDs in a dot separated hierarchy. This makes it possible to refer to the particular type or level of data.

* '''''shell''''' Shell related stats.
** '''shell.uptime''' ''uptime'' How long Shell is running.
** '''shell.active''' ''uptime'' How long Shell window is on top.
** '''shell.friends''' ''absolute'' Number of buddies in the Groups view.
* '''''journal''''' Journal related activity.
** '''journal.uptime''' ''uptime'' How long Journal is running.
** '''journal.active''' ''uptime'' How long Journal window is on top.
** '''journal.creates''' ''counter'' Number of create requests sent from the Journal window.
** '''journal.updates''' ''counter'' Number of update requests sent from the Journal window.
** '''journal.deletes''' ''counter'' Number of delete requests sent from the Journal window.
* '''''activity''''' Activities related stats; specified only for the particular activity.
** '''activity.uptime''' ''uptime'' How long Activity is running.
** '''activity.active''' ''uptime'' How long Activity window is on top.
** '''activity.instances''' ''gauge'' How many instances launched.
** '''activity.new''' ''counter'' How many running instances with new Journal entity.
** '''activity.resumed''' ''counter'' How many running instances with resumed Journal entity.
** '''activity.buddies''' ''gauge'' Number of buddies Activity is interacting with for all running instances.
* '''''application''''' Applications related stats in non-Sugar mode; specified only for the particular application.
** '''application.uptime''' ''uptime'' How long application is running.
** '''application.active''' ''uptime'' How long application window is on top.
* '''''network''''' Network related stats.
** '''network.uptime''' ''uptime'' How long client is connected to the Internet.
** '''network.school''' ''uptime'' How long client is connected to school network.
* '''''system''''' System related stats.
** '''system.uptime''' ''uptime'' System uptime value.
** '''system.diskfree''' ''absolute'' How many storage space is free, in kilobytes, for the home directory.

== Implementation ==

* [[Platform_Team/sugar-stats|sugar-stats]] library.
* [[Platform_Team/Server_Kit/sugar-client|sugar-client]] starting from 1.2 version, Sugar client complex solution that uses [[Sugar_Server_Kit/sugar-stats|sugar-stats]] library.

== See also ==

* Paraguayan Activity usage [http://wiki.paraguayeduca.org/index.php/Analisis_de_Uso_de_Actividades analysis] basing on Journal records.
* Australian [https://sugardextrose.org/issues/59 request] for statistics gathering.

Design Team/Sugar Shell Touch Input

2012-08-20T23:52:00Z

Sridhar:

==System wide==
* Hide pointer cursor when touch screen interaction is occurring, reveal if/when mouse or trackpad is used
: ''On Android 4 after not using the trackpad for a few seconds the cursor is hidden again, which works quite well --erikos''
: ''John pointed me towards XFixes HideCursor/ShowCursor and that there is a [https://bugzilla.gnome.org/show_bug.cgi?id=650604 feature ticket] and a [http://mail.gnome.org/archives/commits-list/2011-June/msg02029.html patch] for gnome-settings-daemon that Sugar could hook into (out of my depth here, didn't get any working code) --gary''
: ''Apparently John (mentioned briefly in a voice call) has added some hooks for us to easily enable and disable the hardware cursor, not yet investigated the code yet --gary''
: ''[ftp://export.lcs.mit.edu/contrib/utilities/unclutter-8.README Unclutter] is a very simple utility that hides a cursor if it has not moved. Or maybe we can hide the pointer in tablet (e-book) mode and keep it in laptop mode?'' --[[User:Sridhar|Sridhar]] 19:51, 20 August 2012 (EDT)
* Palette hover/click behaviours
** Single tap of a button with a primary action should _not_ trigger hover delay palette content (to prevent toolbar palettes and help hints obscuring UI after use)
** Touch and hold _should_ trigger full display of palette content (like a right click, no extra delay)
*: ''I'm [http://ux.stackexchange.com/questions/24460/press-and-hold-or-long-press-gestures-unintuitive concerned] about the undiscoverability of long-press actions, particularly for new users.'' --[[User:Sridhar|Sridhar]] 19:51, 20 August 2012 (EDT)
** Tapping an icon with no primary action should instantly open the full menu/palette, no delay (e.g. Frame right edge buddy icon/s)
* Hide all keyboard shortcut accelerators when booting on touch only devices
* Make toolbar overflow drop-down widget a standard sugar toolbutton width to allow easier access
* Up/down menu/combo overflow UI too thin (hard to scroll up, gtk combo widget needs work here)

====Text editing====
* Touch friendly text selection handles
** Custom Sugar design, use user colours for selection handles (or monochrome theme as a fallback) at each end of text (Carlos upstreamed [http://git.gnome.org/browse/gtk+/log/?h=touch-text-selection patches] to gtk3+)
*** Example [http://people.sugarlabs.org/garycmartin/Text_touch_place_insertion_point_design/ animation] placing the cursor via touch
*** Example [http://people.sugarlabs.org/garycmartin/Text_touch_place_selection_design/ animation] making text selections via touch
*** Example [http://www.lanedo.com/~carlos/touch-text-selection.webm movie] of Gtk3 patches (not Sugar themed yet) from Carlos.
** Selection palette Cut/Copy/Paste/Speak (Share selection with friend feature?) Rough [http://wiki.sugarlabs.org/go/File:Cut_Copy_Paste_Speak_palettte_mockup.png example mockup].
*** Should Cut be introduced? Not something previously exposed in the Sugar UI. Drag & drop of a selection is difficult/error prone via touch, adding Cut would help mitigate a removal of selection drag & drop.
*** We could rely on the Sugar primary Edit toolbar, but only if we can guarantee that the toolbar is always visible when an OSK is being displayed e.g. scrolling canvas to keep current input widget cursor visible and not behind the virtual keyboard.
*** Text vs. icons vs. text & icons for palette
**** Text only provides a minimum sized palette
**** Icon only provides translation neutral palette but provides no textual hints to aid discovery
**** Text and Icon palette may be too large (obscure too much canvas)
** Editable vs. non-editable widget interaction? e.g. Selecting text from web page, vs. selecting text in a text input widget should be identical if possible.
** Single tap to insert cursor (snap to end of existing word?)
** Drag cursor widget to move cursor position (other designs also raise a zoom lens for small screen accuracy but often designs based on Phone size screen limitations)
** Touch, hold and drag to make a selection (snap to end of existing word as per current Write implementation?)
** Touch and hold to auto select a single word, widget handles at each end of selection.
** ''Double tap and drag to select a range of text, same as above (double tap is not a Sugar design, but a fallback for users used to existing implementations as per Android/iOS)''
** ''Double tap to auto select a single word, widget handles at each end of selection (double tap is not a Sugar design, but a fallback for users used to existing implementations as per Android/iOS)''

==Frame==
* Frame expose/hide gesture, swipe in from any screen edge, swipe out over any screen edge
** Hide Frame gesture would need to avoid being interpreted as a canvas scroll (will need tuning, probably a combination of touch start edge proximity and gesture speed)
** Need to consider Frame vs. page turning gestures, left/right page turning would need to avoid screen edge to allow for Frame gesture
** Frame expose/hide gesture, could be limited to a swipe in/out from any screen corner if we find accidental activations at screen edges are triggered too often
* Hide keyboard shortcut hint accelerators from tool buttons and palettes (on devices with touch only hardware)
** Investigate areas where we may want to add a visual button, make an existing button more accessible, or add a multi touch gesture in places where an accelerator key may be frequently used e.g. Alt-tab between open activities could be improved by making the Frame Activity Zoom icon act like Alt-tab (clicking more than once cycles between instances), or perhaps allowing an activity toolbar to be swiped to switch activities.
* Hide/expose on screen keyboard. Show either the Frame or on screen keyboard, but never both at the same time
* Access Point device palette in lower Frame edge does not respond to touch events

== Home==

====Favourite view====
* Instantly open the large central buddy XO icon palette when clicking/tapping
* Add new grid layout?
* Maximise Activity icon size for finger friendliness
* Disable Activity icon dragging for fixed layouts, or fully implement feature
* Activity palette start rework... (temporally might want to remove primary start action and just expose the full palette on click/tap)

====List view====
* Scrolling
* Favourite star hit behaviour

==Neighborhood view==
* Remove primary action from AP icons (prevent accidental connection to random APs)
* Remove primary action from ad-hoc icons (prevent accidental connection to random APs)
* Invoke full ad-hoc, AP, Activity, Buddy palettes on single tap
* Remove primary action from shared Activities (prevent accidental join of a shared activity)

==Group view==
* Remove primary action from shared Activities
* Invoke Buddy palette on single touch

==Journal==
* Touch and hold on an activity icon should open the full palette (like a right click)
* Touch dragging on an activity icon should allow that entry to be dragged to the bottom Journal pane UI for copying to another location
* Touch dragging up/down on the canvas should smooth scroll the Journal list
* Touching the Sort view toolbar icon while the palette is already visible, should dismiss the palette (should use this behaviour system wide)
* Single touching a combo widget (e.g. Anything, Anytime) should lock open the menu for easier discovery (touching and dragging is a nice quick way to access an item but less obvious)
* Combo widgets don't behave nicely if the current item selection is near the bottom of the menu, scrolling up is awkward, should show as many items as we can rather than lots of blank space when near the bottom of the list

==Details view==
* Favorite star hit target too small to easily touch
* Confirmation alert dialogue needed for Erase toolbar button (to prevent accidental data loss)
* Confirmation alert dialogue needed for Duplicate toolbar button (for user feedback as to the action)

Design Team/Sugar Shell Touch Input

2012-08-20T23:51:07Z

Sridhar:

==System wide==
* Hide pointer cursor when touch screen interaction is occurring, reveal if/when mouse or trackpad is used
: ''On Android 4 after not using the trackpad for a few seconds the cursor is hidden again, which works quite well --erikos''
: ''John pointed me towards XFixes HideCursor/ShowCursor and that there is a [https://bugzilla.gnome.org/show_bug.cgi?id=650604 feature ticket] and a [http://mail.gnome.org/archives/commits-list/2011-June/msg02029.html patch] for gnome-settings-daemon that Sugar could hook into (out of my depth here, didn't get any working code) --gary''
: ''Apparently John (mentioned briefly in a voice call) has added some hooks for us to easily enable and disable the hardware cursor, not yet investigated the code yet --gary''
: ''[ftp://export.lcs.mit.edu/contrib/utilities/unclutter-8.README Unclutter] is a very simple utility that hides a cursor if it has not moved. Or maybe we can hide the pointer in tablet (e-book) mode and keep it in laptop mode?'' --[[User:Sridhar|Sridhar]] 19:51, 20 August 2012 (EDT)
* Palette hover/click behaviours
** Single tap of a button with a primary action should _not_ trigger hover delay palette content (to prevent toolbar palettes and help hints obscuring UI after use)
** Touch and hold _should_ trigger full display of palette content (like a right click, no extra delay)
: ''I'm [http://ux.stackexchange.com/questions/24460/press-and-hold-or-long-press-gestures-unintuitive concerned] about the undiscoverability of long-press actions, particularly for new users.'' --[[User:Sridhar|Sridhar]] 19:51, 20 August 2012 (EDT)
** Tapping an icon with no primary action should instantly open the full menu/palette, no delay (e.g. Frame right edge buddy icon/s)
* Hide all keyboard shortcut accelerators when booting on touch only devices
* Make toolbar overflow drop-down widget a standard sugar toolbutton width to allow easier access
* Up/down menu/combo overflow UI too thin (hard to scroll up, gtk combo widget needs work here)

====Text editing====
* Touch friendly text selection handles
** Custom Sugar design, use user colours for selection handles (or monochrome theme as a fallback) at each end of text (Carlos upstreamed [http://git.gnome.org/browse/gtk+/log/?h=touch-text-selection patches] to gtk3+)
*** Example [http://people.sugarlabs.org/garycmartin/Text_touch_place_insertion_point_design/ animation] placing the cursor via touch
*** Example [http://people.sugarlabs.org/garycmartin/Text_touch_place_selection_design/ animation] making text selections via touch
*** Example [http://www.lanedo.com/~carlos/touch-text-selection.webm movie] of Gtk3 patches (not Sugar themed yet) from Carlos.
** Selection palette Cut/Copy/Paste/Speak (Share selection with friend feature?) Rough [http://wiki.sugarlabs.org/go/File:Cut_Copy_Paste_Speak_palettte_mockup.png example mockup].
*** Should Cut be introduced? Not something previously exposed in the Sugar UI. Drag & drop of a selection is difficult/error prone via touch, adding Cut would help mitigate a removal of selection drag & drop.
*** We could rely on the Sugar primary Edit toolbar, but only if we can guarantee that the toolbar is always visible when an OSK is being displayed e.g. scrolling canvas to keep current input widget cursor visible and not behind the virtual keyboard.
*** Text vs. icons vs. text & icons for palette
**** Text only provides a minimum sized palette
**** Icon only provides translation neutral palette but provides no textual hints to aid discovery
**** Text and Icon palette may be too large (obscure too much canvas)
** Editable vs. non-editable widget interaction? e.g. Selecting text from web page, vs. selecting text in a text input widget should be identical if possible.
** Single tap to insert cursor (snap to end of existing word?)
** Drag cursor widget to move cursor position (other designs also raise a zoom lens for small screen accuracy but often designs based on Phone size screen limitations)
** Touch, hold and drag to make a selection (snap to end of existing word as per current Write implementation?)
** Touch and hold to auto select a single word, widget handles at each end of selection.
** ''Double tap and drag to select a range of text, same as above (double tap is not a Sugar design, but a fallback for users used to existing implementations as per Android/iOS)''
** ''Double tap to auto select a single word, widget handles at each end of selection (double tap is not a Sugar design, but a fallback for users used to existing implementations as per Android/iOS)''

==Frame==
* Frame expose/hide gesture, swipe in from any screen edge, swipe out over any screen edge
** Hide Frame gesture would need to avoid being interpreted as a canvas scroll (will need tuning, probably a combination of touch start edge proximity and gesture speed)
** Need to consider Frame vs. page turning gestures, left/right page turning would need to avoid screen edge to allow for Frame gesture
** Frame expose/hide gesture, could be limited to a swipe in/out from any screen corner if we find accidental activations at screen edges are triggered too often
* Hide keyboard shortcut hint accelerators from tool buttons and palettes (on devices with touch only hardware)
** Investigate areas where we may want to add a visual button, make an existing button more accessible, or add a multi touch gesture in places where an accelerator key may be frequently used e.g. Alt-tab between open activities could be improved by making the Frame Activity Zoom icon act like Alt-tab (clicking more than once cycles between instances), or perhaps allowing an activity toolbar to be swiped to switch activities.
* Hide/expose on screen keyboard. Show either the Frame or on screen keyboard, but never both at the same time
* Access Point device palette in lower Frame edge does not respond to touch events

== Home==

====Favourite view====
* Instantly open the large central buddy XO icon palette when clicking/tapping
* Add new grid layout?
* Maximise Activity icon size for finger friendliness
* Disable Activity icon dragging for fixed layouts, or fully implement feature
* Activity palette start rework... (temporally might want to remove primary start action and just expose the full palette on click/tap)

====List view====
* Scrolling
* Favourite star hit behaviour

==Neighborhood view==
* Remove primary action from AP icons (prevent accidental connection to random APs)
* Remove primary action from ad-hoc icons (prevent accidental connection to random APs)
* Invoke full ad-hoc, AP, Activity, Buddy palettes on single tap
* Remove primary action from shared Activities (prevent accidental join of a shared activity)

==Group view==
* Remove primary action from shared Activities
* Invoke Buddy palette on single touch

==Journal==
* Touch and hold on an activity icon should open the full palette (like a right click)
* Touch dragging on an activity icon should allow that entry to be dragged to the bottom Journal pane UI for copying to another location
* Touch dragging up/down on the canvas should smooth scroll the Journal list
* Touching the Sort view toolbar icon while the palette is already visible, should dismiss the palette (should use this behaviour system wide)
* Single touching a combo widget (e.g. Anything, Anytime) should lock open the menu for easier discovery (touching and dragging is a nice quick way to access an item but less obvious)
* Combo widgets don't behave nicely if the current item selection is near the bottom of the menu, scrolling up is awkward, should show as many items as we can rather than lots of blank space when near the bottom of the list

==Details view==
* Favorite star hit target too small to easily touch
* Confirmation alert dialogue needed for Erase toolbar button (to prevent accidental data loss)
* Confirmation alert dialogue needed for Duplicate toolbar button (for user feedback as to the action)

Sugar on a Stick/Downloads

2012-05-24T08:10:24Z

Sridhar: clarified versions: 32-bit vs 64-bit

<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}</noinclude>__NOTOC__
{|
|-
| rowspan="3" style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickPineapple.png|320px|left|link=http://spins.fedoraproject.org/soas/#downloads]]
| colspan="2" style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [http://fedoraproject.org Fedora®] [http://spins.fedoraproject.org/soas Spin] [[wikipedia:Live USB|Live USB]] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]] and designed to fit on an ordinary USB thumbdrive ("stick").

It will run on any recent x86-based computer that can boot from a USB stick (check the BIOS settings if it doesn't work straight away). This includes most Windows and Linux PCs and x86 Macs.

You can use SoaS to demo Sugar almost anywhere without disturbing the contents of the computer you use, and if people like what they see, you can [[Sugar_Creation_Kit/sck/liveinst|install]] Sugar on a Stick to their hard drives or other sticks from the demo stick.


Version 6, our most recent, is named '''[[Sugar on a Stick/Pineapple|Pineapple]]''' and was released on '''08 November 2011.'''
|- style="border: 0; border-width: 0; text-align: center"
|
[[File:Download Mirabell.png|link=http://download.fedoraproject.org/pub/alt/spins/linux/releases/16/Spins/x86_64/Fedora-16-x86_64-Live-SoaS.iso]]
x86_64 (64-bit)
|
[[File:Download Mirabell.png|link=http://download.fedoraproject.org/pub/alt/spins/linux/releases/16/Spins/i686/Fedora-16-i686-Live-SoaS.iso]]
i686 (32-bit)
|-
| colspan="2" style="border: 0; border-width: 0; text-align: center" |[[Sugar on a Stick/Pineapple/hashes | hashes to verify downloads]]

'''See these [[Sugar on a Stick/Installation|installation instructions]].'''
|}
BitTorrent links are available at the [http://spins.fedoraproject.org/soas/#downloads Spins download page].

''Fedora and the Infinity design logo are trademarks of Red Hat, Inc.''

{{warning|'''Commercial sources''' of USB flash drives and SDHC cards loaded with Sugar on a Stick, [[Sugar_Creation_Kit#Commercial_source_of_SoaS-loaded_media | are available]]; however, beware that they may lack features!}}

BugSquad/Get Logs

2012-04-26T01:08:49Z

Sridhar: /* The Log Activity */

<noinclude>{{TOCright}}
[[Category:Testing]]
[[Category:BugSquad]]
[[Category:HowTo]]
</noinclude>

== What are the logs useful for ==
If you provide debugging logs to a ticket, you'll be making it much easier to developers to fix the issue. In most of the cases it will be easiest for you to reproduce the bug.

== The Log Activity ==

The [[olpc:Log]] Activity, is a Sugar-based log viewer that is in most distributions to help you view software logs. You can copy text from the view pane into the Sugar clipboard, then from the clipboard keep it into the Journal, and then attach that Journal item into the [http://bugs.sugarlabs.org bugs.sugarlabs.org] or [http://dev.laptop.org dev.laptop.org] [Attach file] > [Browse...] dialogs, or paste relevant pieces directly into the bug description.

You can use the Log Collector to easily export all logs to the journal in a handy zip bundle:

[[Image:Log Collector.png|615px]]

== Enabling Sugar debug logging ==
Starting with the 0.83 development release, we created the text file, ~/.sugar/debug (shown in the gray box below), which gets read at sugar startup. All the logging options are commented out by default. Use your editor of choice and remove the '#' before the line 'export SUGAR_LOGGER_LEVEL=debug' to enable Sugar debug logging.
<pre>
# Uncomment the following lines to turn on many sugar debugging
# log files and features
#export LM_DEBUG=net
#export GABBLE_DEBUG=all
#export GABBLE_LOGFILE=$HOME/.sugar/default/logs/telepathy-gabble.log
#export SALUT_DEBUG=all
#export SALUT_LOGFILE=$HOME/.sugar/default/logs/telepathy-salut.log
#export GIBBER_DEBUG=all
#export PRESENCESERVICE_DEBUG=1
#export SUGAR_LOGGER_LEVEL=debug

# Uncomment the following line to enable core dumps
#ulimit -c unlimited
</pre>

=== Where are the logs placed ===
* Perform the minimal steps to reproduce the bug.
* The relevant logs are stored in '~/.sugar/default/logs', (e.g, org.laptop.WebActivity-1.log for the log of the first Browse instance).

=== Using the sugar-emulator ===
If you are using a version older than the development release 0.83, run the emulator with the following command:
SUGAR_LOGGER_LEVEL=debug sugar-emulator

=== Presence service ===
If your bug involves the presence service, you might also want to follow the steps for [[BugSquad/Telepathy Debugging]].

== On the XO-1 (using Sugar 0.82.x)==
These are general steps to follow when providing logs for a bug:

* Start the Terminal activity.
* Type the following:
echo 'export SUGAR_LOGGER_LEVEL=debug' >> /home/olpc/.xsession

* Reboot, or just restart X using ctrl+alt+erase

The file <tt>~/.xsession-example</tt> contains other settings useful for debugging. You can copy individual lines from this or copy the entire file to <tt>~/.xsession</tt>.

== On other machines (Sugar.84)==
Sugar activities have logs
<code>~/.sugar/default/logs/ </code>
so go to
<code>someuser</code>
type
<code> ls -al</code>
then drill down to
<code> ~/.sugar/default/logs/</code>
for the error messages.

Another useful command is:
<code>dmesg</code>
It prints out all of the kernel's messages and warnings for this session, with any new stuff at the end.

File:Log Collector.png

2012-04-26T01:06:55Z

Sridhar: Log activity: Log Collector feature

Log activity: Log Collector feature

User:Sridhar/2011 SLOB platform

2011-11-07T13:11:49Z

Sridhar:

The easiest way to find out about me is to visit my Web site [http://www.dhanapalan.com/blog/about/].

Amongst a variety of Free and Open Source Software contributions since the 1990s [https://wiki.ubuntu.com/SridharDhanapalan], I have previously been a board member of Linux Australia and President of the Sydney Linux Users Group (SLUG). I have given presentations at various events including linux.conf.au, OSDC, SLUG, Software Freedom Day and Document Freedom Day.

For nearly two years I have served full-time as OLPC Australia's Engineering Manager, liaising between developers and educators to ensure that we are able to satisfy requirements on the ground. My team at OLPC Australia take this very seriously, to the point of extending OLPC's core principles with two of our own [http://www.laptop.org.au/vision/core-principles]:
* Empowering Teachers
* Community Engagement

In my day-to-day work, I am in constant contact with schools, communities, governments and other relevant bodies. I have developed an appreciation for Sugar as much more than software - it is a platform that supports education, community and culture. Everything we build is done so in consultation with educators and other stakeholders, in consideration of the whole picture. For instance, the operating system that we carry on our XOs [https://dev.laptop.org.au/projects/xo-au/wiki/List_of_improvements_in_XO-AU_builds_2010-2011] was developed in tandem with our certification system [http://edu.laptop.org.au/laptop/xo-cert-course].

I am proud to say that our approach has shown tremendous success [http://www.youtube.com/watch?v=cO-VNhgZLDw]. You can read our Policy Document [http://edu.laptop.org.au/laptop/policy-document] to gain a full appreciation of our programme.

As a Sugar Labs Oversight Board member, I aim to bring this same kind of holistic approach to guiding Sugar. My strength is in using my extensive Free Software experience to meet real needs on the ground. I strongly believe that for Sugar to grow, it needs to have strong representation from all stakeholders, including deployments.

Our contributions to Sugar have been numerous. We have extended the OLPC XS Schoolserver with our XS-AU [https://dev.laptop.org.au/projects/xs-au/wiki], creating a far more flexible collaboration solution. We have partnered with Activity Central to develop many improvements for the platform. These are currently being tested in Dextrose developer builds, and will be upstreamed in the near future.

While it's all well and good to speak about past achievements, it's important as a Board member to have a vision for the future. We need to broaden the developer and user base. We need to make it simpler to access Sugar.

On the developer side, we should embrace [http://www.dhanapalan.com/blog/2011/06/20/why-free-and-open-matters/] Web [http://www.dhanapalan.com/blog/2011/06/23/html5-in-sugar/] standards and allow activities to be created in HTML5. We are working [https://dev.laptop.org.au/issues/742] on that.

On the user side, I'd like Sugar to be made available on more devices. I am encouraged by the work being made to port Sugar to GTK+ 3. This will lay the groundwork for Sugar on tablets, such as the XO-3. We need to think ahead to ensure longevity of the Sugar platform and mission.

User:Sridhar/2011 SLOB platform

2011-11-07T13:08:41Z

Sridhar:

The easiest way to find out about me is to visit my Web site [http://www.dhanapalan.com/blog/about/].

Amongst a variety of Free and Open Source Software contributions [https://wiki.ubuntu.com/SridharDhanapalan], I have previously been a board member of Linux Australia and President of the Sydney Linux Users Group (SLUG). I have given presentations at various events including linux.conf.au, OSDC, SLUG, Software Freedom Day and Document Freedom Day.

For nearly two years I have served full-time as OLPC Australia's Engineering Manager, liaising between developers and educators to ensure that we are able to satisfy requirements on the ground. My team at OLPC Australia take this very seriously, to the point of extending OLPC's core principles with two of our own [http://www.laptop.org.au/vision/core-principles]:
* Empowering Teachers
* Community Engagement

In my day-to-day work, I am in constant contact with schools, communities, governments and other relevant bodies. I have developed an appreciation for Sugar as much more than software - it is a platform that supports education, community and culture. Everything we build is done so in consultation with educators and other stakeholders, in consideration of the whole picture. For instance, the operating system that we carry on our XOs [https://dev.laptop.org.au/projects/xo-au/wiki/List_of_improvements_in_XO-AU_builds_2010-2011] was developed in tandem with our certification system [http://edu.laptop.org.au/laptop/xo-cert-course].

I am proud to say that our approach has shown tremendous success [http://www.youtube.com/watch?v=cO-VNhgZLDw]. You can read our Policy Document [http://edu.laptop.org.au/laptop/policy-document] to gain a full appreciation of our programme.

As a Sugar Labs Oversight Board member, I aim to bring this same kind of holistic approach to guiding Sugar. My strength is in using my extensive Free Software experience to meet real needs on the ground. I strongly believe that for Sugar to grow, it needs to have strong representation from all stakeholders, including deployments.

Our contributions to Sugar have been numerous. We have extended the OLPC XS Schoolserver with our XS-AU [https://dev.laptop.org.au/projects/xs-au/wiki], creating a far more flexible collaboration solution. We have partnered with Activity Central to develop many improvements for the platform. These are currently being tested in Dextrose developer builds, and will be upstreamed in the near future.

While it's all well and good to speak about past achievements, it's important as a Board member to have a vision for the future. We need to broaden the developer and user base. We need to make it simpler to access Sugar.

On the developer side, we should embrace [http://www.dhanapalan.com/blog/2011/06/20/why-free-and-open-matters/] Web [http://www.dhanapalan.com/blog/2011/06/23/html5-in-sugar/] standards and allow activities to be created in HTML5. We are working [https://dev.laptop.org.au/issues/742] on that.

On the user side, I'd like Sugar to be made available on more devices. I am encouraged by the work being made to port Sugar to GTK+ 3. This will lay the groundwork for Sugar on tablets, such as the XO-3. We need to think ahead to ensure longevity of the Sugar platform and mission.

Oversight Board/2011-2012-candidates

2011-11-07T12:52:10Z

Sridhar: added Sridhar Dhanapalan as a candidate

<noinclude>[[Category:Oversight board]]
[[Category:Governance]]
[[Category:Team]]
</noinclude>

==Election==
Three (3) seats are open ([[Sugar Labs/Governance#Oversight_Board|due to staggered seat terms]]) for election / re-election to the [[Oversight Board|Sugar Labs Oversight Board]] for 2011-2012, those of Walter Bender, Mel Chua, and Bernie Innocenti.

==Candidates==
Here are the candidates:

* '''Your name''' (''link to your platform'')
* Gerald Ardito [[User:Gardito | 2011 Statement]]
* Walter Bender [[User:Walter/2011_position_statement|2011 Position Statement]]
* Sridhar Dhanapalan [[User:Sridhar/2011_SLOB_platform|2011 Sugar Labs Oversight Board election platform]]
* Nick Doiron [[User:Ndoiron/2011-2012_candidacy|2011-2012 Candidacy]]
* David Farning [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg12527.html Candidacy post]
* Chris Leonard (cjl) [[User:Cjl/Candidate_Statement|2011 Candidate Statement]]

==References==
* [[Oversight_Board/2010-2011-candidates]]
* [[Oversight_Board/2009-2010-candidates]]
* 23 September 2009 - [http://lists.sugarlabs.org/archive/iaep/2009-September/008620.html Oversight Board election procedure update]
* [[Archive/Current Events/2009-08-05#Help_wanted]]
* [[Sugar Labs/Members]]

User:Sridhar/2011 SLOB platform

2011-11-07T12:50:06Z

Sridhar:

The easiest way to find out about me is to visit my Web site [http://www.dhanapalan.com/blog/about/].

Amongst a variety of Free and Open Source Software contributions [https://wiki.ubuntu.com/SridharDhanapalan], I have previously been a board member of Linux Australia and President of the Sydney Linux Users Group (SLUG). I have given presentations at various events including linux.conf.au, OSDC, SLUG, Software Freedom Day and Document Freedom Day.

For nearly two years I have served full-time as OLPC Australia's Engineering Manager, liaising between developers and educators to ensure that we are able to satisfy requirements on the ground. My team at OLPC Australia take this very seriously, to the point of extending OLPC's core principles with two of our own [http://www.laptop.org.au/vision/core-principles]:
* Empowering Teachers
* Community Engagement

In my day-to-day work, I am in constant contact with schools, communities, governments and other relevant bodies. I have developed an appreciation for Sugar as much more than software - it is a platform that supports education, community and culture. Everything we build is done so in consultation with educators and other stakeholders, in consideration of the whole picture. For instance, the operating system that we carry on our XOs [https://dev.laptop.org.au/projects/xo-au/wiki/List_of_improvements_in_XO-AU_builds_2010-2011] was developed in tandem with our certification system [http://edu.laptop.org.au/laptop/xo-cert-course].

I am proud to say that our approach has shown tremendous success [http://www.youtube.com/watch?v=cO-VNhgZLDw]. You can read our Policy Document [http://edu.laptop.org.au/laptop/policy-document] to gain a full appreciation of our programme.

As a Sugar Labs Oversight Board member, I aim to bring this same kind of holistic approach to guiding Sugar. My strength is in using my extensive Free Software experience to meet real needs on the ground. I strongly believe that for Sugar to grow, it needs to have strong representation from all stakeholders, including deployments.

Our contributions to Sugar have been numerous. We have extended the OLPC XS Schoolserver with our XS-AU [https://dev.laptop.org.au/projects/xs-au/wiki], creating a far more flexible collaboration solution. We have partnered with Activity Central to develop many improvements for the platform. These are currently being tested in Activity Central's Dextrose developer builds, and will be upstreamed in the near future.

While it's all well and good to speak about past achievements, it's important as a Board member to have a vision for the future. We need to broaden the developer and user base. We need to make it simpler to access Sugar.

On the developer side, we should embrace [http://www.dhanapalan.com/blog/2011/06/20/why-free-and-open-matters/] Web [http://www.dhanapalan.com/blog/2011/06/23/html5-in-sugar/] standards and allow activities to be created in HTML5. We are working [https://dev.laptop.org.au/issues/742] on that.

On the user side, I'd like Sugar to be made available on more devices. I am encouraged by the work being made to port Sugar to GTK+ 3. This will lay the groundwork for Sugar on tablets, such as the XO-3. We need to think ahead to ensure longevity of the Sugar platform and mission.

User:Sridhar/2011 SLOB platform

2011-11-07T12:47:53Z

Sridhar:

The easiest way to find out about me is to visit my Web site [http://www.dhanapalan.com/blog/about/].

Amongst a variety of Free and Open Source Software contributions [https://wiki.ubuntu.com/SridharDhanapalan], I have previously been a board member of Linux Australia and President of the Sydney Linux Users Group (SLUG). I have given presentations at various events including linux.conf.au, OSDC, SLUG, Software Freedom Day and Document Freedom Day.

For nearly two years I have served full-time as OLPC Australia's Engineering Manager, liaising between developers and educators to ensure that we are able to satisfy requirements on the ground. My team at OLPC Australia take this very seriously, to the point of extending OLPC's core principles with two of our own [http://www.laptop.org.au/vision/core-principles]:
* Empowering Teachers
* Community Engagement

In my day-to-day work, I am in constant contact with schools, communities, governments and other relevant bodies. I have developed an appreciation for Sugar as much more than software - it is a platform that supports education, community and culture. Everything we build is done so in consultation with educators and other stakeholders, in consideration of the whole picture. For instance, the operating system that we carry on our XOs [https://dev.laptop.org.au/projects/xo-au/wiki/List_of_improvements_in_XO-AU_builds_2010-2011] was developed in tandem with our certification system [http://edu.laptop.org.au/laptop/xo-cert-course].

I am proud to say that our approach has shown tremendous success [http://www.youtube.com/watch?v=cO-VNhgZLDw]. You can read our Policy Document [http://edu.laptop.org.au/laptop/policy-document] to gain a full appreciation of our programme.

As a Sugar Labs Oversight Board member, I aim to bring this same kind of holistic approach to guiding Sugar. My strength is in using my extensive Free Software experience to meet real needs on the ground. I strongly believe that for Sugar to grow, it needs to have strong representation from all stakeholders, including deployments.

Our contributions to Sugar have been numerous. We have extended the OLPC XS Schoolserver with our XS-AU [https://dev.laptop.org.au/projects/xs-au/wiki], creating a far more flexible collaboration solution. We have partnered with Activity Central to develop many improvements for the platform. These are currently being tested in Activity Central's Dextrose developer builds, and will be upstreamed in the near future.

While it's all well and good to speak about past achievements, it's important as a Board member to have a vision for the future. We need to broaden the developer and user base. We need to make it simpler to access Sugar.

On the developer side, we should embrace [http://www.dhanapalan.com/blog/2011/06/20/why-free-and-open-matters/] Web [http://www.dhanapalan.com/blog/2011/06/23/html5-in-sugar/] standards and allow activities to be created in HTML5. We are working [https://dev.laptop.org.au/issues/742] on that.

On the user side, I'd like Sugar to be made available on more devices. I am encouraged by the work being made to port Sugar to GTK+ 3. This will lay the groundwork for Sugar on tablets, such as the XO-3.

User:Sridhar/2011 SLOB platform

2011-11-07T12:46:17Z

Sridhar: Created page with "The easiest way to find out about me is to visit my Web site [http://www.dhanapalan.com/blog/about/]. Amongst a variety of Free and Open Source Software contributions [h..."

The easiest way to find out about me is to visit my Web site [http://www.dhanapalan.com/blog/about/].

Amongst a variety of Free and Open Source Software contributions [https://wiki.ubuntu.com/SridharDhanapalan], I have previously been a board member of Linux Australia and President of the Sydney Linux Users Group (SLUG). I have given presentations at various events including linux.conf.au, OSDC, SLUG, Software Freedom Day and Document Freedom Day.

For nearly two years I have served full-time as OLPC Australia's Engineering Manager, liaising between developers and educators to ensure that we are able to satisfy requirements on the ground. My team at OLPC Australia take this very seriously, to the point of extending OLPC's core principles with two of our own [http://www.laptop.org.au/vision/core-principles]:
* Empowering Teachers
* Community Engagement

In my day-to-day work, I am in constant contact with schools, communities, governments and other relevant bodies. I have developed an appreciation for Sugar as much more than software - it is a platform that supports education, community and culture. Everything we build is done so in consultation with educators and other stakeholders, in consideration of the whole picture. For instance, the operating system that we carry on our XOs [https://dev.laptop.org.au/projects/xo-au/wiki/List_of_improvements_in_XO-AU_builds_2010-2011] was developed in tandem with our certification system [http://edu.laptop.org.au/laptop/xo-cert-course].

I am proud to say that our approach has shown tremendous success [http://www.youtube.com/watch?v=cO-VNhgZLDw]. You can read our Policy Document [http://edu.laptop.org.au/laptop/policy-document] to gain a full appreciation of our programme.

As a Sugar Labs Oversight Board member, I aim to bring this same kind of holistic approach to guiding Sugar. My strength is in using my extensive Free Software experience to meet real needs on the ground. I strongly believe that for Sugar to grow, it needs to have strong representation from all stakeholders, including deployments.

Our contributions to Sugar have been numerous. We have extended the OLPC XS Schoolserver with our XS-AU [https://dev.laptop.org.au/projects/xs-au/wiki], creating a far more flexible collaboration solution. We have partnered with Activity Central to develop many improvements for the platform. These are currently being tested in Activity Central's Dextrose developer builds, and will be upstreamed in the near future.

It's all well and good to speak about past achievements, but it's important as a Board member to have a vision for the future. We need to broaden the developer and user base. We need to make it simpler to access Sugar.

On the developer side, we should embrace [http://www.dhanapalan.com/blog/2011/06/20/why-free-and-open-matters/] Web [http://www.dhanapalan.com/blog/2011/06/23/html5-in-sugar/] standards and allow activities to be created in HTML5. We are working [https://dev.laptop.org.au/issues/742] on that.

On the user side, I'd like Sugar to be made available on more devices. I am encouraged by the work being made to port Sugar to GTK+ 3. This will lay the groundwork for Sugar on tablets, such as the XO-3.

User:Sridhar

2011-11-07T12:38:13Z

Sridhar:

{{TOCright}}

My name is '''Sridhar Dhanapalan''', and I am the Engineering Manager at [http://www.laptop.org.au OLPC Australia]. My [http://www.laptop.org.au/node/87/lightbox2 professional bio] is on the OLPC Australia Web site.

I am known as '''Yama''' online (irc.freenode.net, etc.).

Blog: http://www.dhanapalan.com/blog/

About me: http://www.dhanapalan.com/blog/about/

Summary of FLOSS contributions: https://wiki.ubuntu.com/SridharDhanapalan

----

[[User:Sridhar/2011_SLOB_platform|2011 Sugar Labs Oversight Board election platform]]

User:Sridhar

2011-11-07T12:33:44Z

Sridhar: Created page with "{{TOCright}} My name is '''Sridhar Dhanapalan''', and I am the Engineering Manager at [http://www.laptop.org.au OLPC Australia]. My [http://www.laptop.org.au/node/87/lightbox2 p..."

Activity Team

2011-06-04T02:31:09Z

Sridhar: /* Creating a new activity */

<noinclude><div class="noprint">{{TeamHeader|Activity Team}}</div></noinclude>

==Mission==

{{:Activity Team/Mission}}

==Tips for Activity Developers==

=== Ask your 'newbie' question on-line ===

Join [http://en.wikipedia.org/wiki/IRC IRC] channel [irc://irc.freenode.net/sugar-newbies #sugar-newbies] (e.g. via [http://webchat.freenode.net/?randomnick=1&prompt=1&channels=sugar-newbies web client]) and ask your question about activity, or sugar core, development process. Also browse chat [http://meeting.sugarlabs.org/sugar-newbies logs].

=== Creating a new activity ===

See [[Activity Team/Creating a New Activity|Creating a New Activity]] and [[Activity Team/Resources|Activity Team Resources]].

=== Problems logging in to Gitorious? ===

Gitorious users are sometimes having their IP addresses incorrectly blacklisted at http://git.sugarlabs.org/. If your SSH key is rejected with the error "Access denied or bad repository path", please open a ticket by emailing git AT sugarlabs DOT org.

===Move an activity===

We need help moving activities over to Sugar Labs from OLPC's servers. This is a great way to get started helping out the Activity Team. See [[Activity Team/How_to_migrate_from_OLPC]] for instructions, and [[Activity Team/Activity Status]] for the list of activities that need to be moved.

While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct. This will really help out the distro packagers.

===Cross-platform compatibility===

As Sugar is integrated into more distros and the hardware base expands, it is important to keep Activity developers informed of any issues they need be aware of. For example, when Sugar was only expected to run on the XO-1 laptop, it was safe to assume that the display was always 1200x900.

The [[Activity Team/Compatibility Tips|Compatibility Tips]] page is a place to accumulate tips.

===Modify Activities===

A guide has been written describing how to make simple modifications to popular Sugar activities. Examples include adding sounds to TamTam, blocks to TurtleArt, buttons to Calculate, etc.

*[[Activity_Team/Modifying_an_Activity]]

===Internationalization===

We use '''[http://docs.python.org/library/gettext.html gettext]''' to internationalize activities. The basic steps are:

In your Python code:
from gettext import gettext as _

Hence forth, encapsulate strings that you want translated in _():
_('string to be translated')

Run <code>setup.py</code> to generate a POT file for your project. This file will contain a reference to all of the encapsulated strings.

From here, you need to:
# <code>git add</code>, <code>commit</code>, and <code>push</code> the POT file to git
# request that your project be added to the pootle server (by filing a task to the localization component on bugs.sugarlabs.org)
# add pootle as a committer to your project on gitorious

Once translations are committed to your project:
# do a <code>git pull</code> to get a local copy of the .po files
# run <code>setup.py fix_manifest</code> to create the .mo files used at run time
Details can be found on the [[Translation_Team/i18n_Best_Practices]].

===General overview of git===

Read the brief overview below but then '''start''' with our [[Activity Team/Git Tutorial|git tutorial]].

====glossary====

;VCS: Version Control System — keeps track of changes to a set of files.
;git: the distributed VCS used by Sugar Labs
;commit: set of changes to files tracked by a VCS, accompanied by metadata (author, description, etc.)
;diff/patch: (usually textual) representation of changes. These are also the names of specific tools used to create/apply these representations of changes.
;repository: storage place for commits, usually of a certain piece of software
;gitorious: software for hosting git repositories, including a web interface for administration
;git.sugarlabs.org: server hosted by Sugar Labs running gitorious

====Setup====
(once per machine you're working on)
git clone git://git.sugarlabs.org/whatever/mainline.git whatever

====Regular usage====
cd whatever
[hack away and test your changes]
git diff
[review your changes, go back to hacking if you notice a mistake]
git status
git add NameOfNewFile # if you created any file you want included
git commit -a
[describe your changes - by convention the first line is a summary and the remaining lines are long description]
[start again at hacking if you're offline]
git log origin/master..master # shows you all commits not pushed yet
git push # if/once you are online

Git offers a lot more commands and features that can make your life
easier, but it's best to start off small and use only those mentioned
above. It's very easy to get confused if you're unfamiliar with git.

Even if you use the more advanced features, git does a pretty good job at
allowing you to recover from your mistakes.
So if you ever mess up and don't know how to fix it yourself, please
stop (at least for me that's usually the hardest part ;) ), try to
recollect the exact sequence of actions (e.g. from shell history) and ask
for help.

----

Once you have [[Activity Team/How_to_migrate_from_OLPC|migrated]] your project, you may have some more detailed [[Activity Team/Git FAQ|questions regarding how Sugar Labs uses git]], particularly in regard to patch management.

----

{{:Activity Team/Git}}

== Maintainers ==

Please see [[File:How_to_become_a_maintainer.pdf]] for an overview of the Activity maintenance process.

== Testers ==

Please see the [[Features/Soas_V4/ASLOxo_Activity_Test_Table|Activity Test-table page]] for tester information.

== Background information ==

=== Sugar Activities ===

There is an [[Activities]] page where we highlight Sugar activities in the wiki. (We need to discuss how best to manage the content of this page as well as how to manage the activity-specific sub-pages.)

===Sugar [[Human Interface Guidelines]]===

The [[Human_Interface_Guidelines|Sugar Human Interface Guidelines]] content has also been migrated to Sugar Labs. This guide is a critical resource when designing activities.
: An [[Activity Team/Project Ideas#Activity HIG|Activity HIG]] discussion

===Sugar Almanac===

The [[Development Team/Almanac|Sugar Almanac]] content has been migrated to Sugar Labs. It's a great, quick reference when building python Activities.

===activities.sugarlabs.org===

The [http://activities.sugarlabs.org Sugar Activity Library] is our user-facing portal for Sugar activities. The site uses the back-end Mozilla built for Firefox and Thunderbird extensions at addons.mozilla.org, called Remora. To help out, check out [[Activity Library]].

===sugar-widgets library===

See [[Development Team/sugar-port]].

===sugar-sprites library===

See [[Activity Team/Sugar-sprites]]

== Misc. ==

===Mime types and file suffixes===

You can associate your activity with mime types by including a mime_types entry in the activity/activity.info file; e.g.

mime_types = text/plain;text/x-python;text/x-logo;text/x-svg;application/xml;text/html;text/xml;image/svg+xml

You can associate your activity with a file suffix by including a mimetypes.xml file in your activity subdirectory:

<?xml version="1.0" encoding="UTF-8"?>
<mime-info xmlns="http://www.freedesktop.org/standards/shared-mime-info">
<mime-type type="application/x-turtle-art">
<comment xml:lang="en">Turtle Art</comment>
<glob pattern="*.ta"/>
</mime-type>
</mime-info>

'''Note:''' You cannot just copy your activity into the ~/Activities directory. You have to install it as a .xo bundle or using 'setup.py install' (note that the latter is tricky as the command might get your paths messed up). This installation step will create a file --> ~/.local/share/mime/packages/<your-bundle_id>.xml

If your activity does not register any mimetype, then it won't matter.

If your activity was already properly installed (with sugar-install-bundle), then copying new source into Activities will not be affected by this problem unless the new source registers a new mimetype that the old source did not.

=== Activity Team users on activities.sugarlabs.org ===

Fake emails to identify users:
* ''activity.team@sugarlabs.org'' activities that are supported by Activity Team
* ''trash@dev.null'' activities to remove

===setup.py===

There is a handy utility that is a standard part of Sugar Activity bundles, setup.py. You should use it to create and update POT files, generate a MANIFEST file and update locale files, and create .xo and .tar files for distribution.

./setup.py genpot # generates or updates the POT file used by gettext for internationalization
./setup.py build
./setup.py fix_manifest # updates the MANIFEST file and generates or updates the locale files used for internationalization
./setup.py dist_xo # creates an .xo bundle from your project
./setup.py dist_source # creates a .tar.gz file from your project

===Packaging activities discussion===

We are currently discussing how to package activities in the future, in order to support all distributions. Please add your comments to the following pages.
* [[Activity Team/Packaging|Packaging]]
** should we remove "Activities" section from that page; all issues where moved to Activity_Status page [[User:Alsroot|alsroot]] 10:33, 16 January 2009 (UTC)
* [[Activity Team/Packaging Ideas|Packaging ideas]]

=== The Sugar Control Panel ===

While not strictly in the realm of Activities, it may be useful on occasion to add a section to the Sugar Control Panel. [[Activity Team/Control Panel|Things to keep in mind]].

=== A typical update cycle ===

Anyone can contribute a patch to a Sugar Activity. The typical work cycle involves an interaction with the activity (project) maintainer as follows:
# make a clone (anyone)
# make your changes (anyone)
# mail your patch to sugar_devel (anyone)
# make changes as per suggestions by the project maintainer and developer community (anyone)
# push your changes (anyone)
# request a merge (anyone)
# write release notes (anyone)
# tag the new version in git (project maintainer)
# create the .xo and .tar files (project maintainer)
# upload .tar to download.sugarlabs.org (project maintainer)
# upload .xo to activities.sugarlabs.org (project maintainer)
# update wiki documentation (anyone)

=== OLPC XO game buttons ===

The game buttons on the OLPC XO are accessible:
* The left-side buttons map to KP_Up, KP_Right, KP_Down, and KP_Left
* The right-side buttons map to KP_Page_Up (o), KP_End (✓), KP_Page_Down (×), and KP_Home (◽)

=== The Sugar Object Chooser ===

The Object Chooser is the activity-level user interface to the Journal. Examples and caveats are found [[Activity_Team/Object_Chooser|here]].

==[[Activity Team/Project Ideas|Project Ideas]]==

The Activity Team always needs project ideas and suggestions. Post your ideas to [[Activity Team/Project Ideas]].

If you see something here you would like to help with, please [[Activity Team/Contacts|contact us]].

[[User:Wade|Wade]] 17:19, 13 January 2009 (UTC)

==Additional resources==

Additional resources may be found [[Activity_Team/Resources|here]].

==Sugar Activity development courses==

There are university- and secondary-school-level courses being taught around Sugar development. Several of the syllabi are on line:

* http://wiki.paraguayeduca.org/index.php/Curso_Sugar_FPUNA is being adapted by UNA
* http://teachingopensource.org/index.php/RIT/The_Course is being taught at RIT

==Meetings==

Please check [[/Meetings]] for meeting schedules/logs.

== Moving to Sugar Labs ==

A few notes re moving to the Sugar Labs infrastructure:

* use git init to create a new project unless it already exists.
* use <code>setup.py dist_source</code> to make the source package associated with your project.
* source packages now go in:
download.sugarlabs.org:/srv/www-sugarlabs/download/sources/

: from there, if your project (if it is an Activity) probably belongs in the honey subdirectory, e.g.,
download.sugarlabs.org:/srv/www-sugarlabs/download/sources/honey/Abacus/

: If your project is part of the Sugar core, it goes in sucrose/fructose/ (for core Activities) or sucrose/glucose (for core modules), e.g.,
download.sugarlabs.org:/srv/www-sugarlabs/download/sources/fructore/TurtleArt/
download.sugarlabs.org:/srv/www-sugarlabs/download/sources/glucose/sugar-toolkit/

* don't forget to update addons as well!!
activities.sugarlabs.org

* and to copy the tar file to download.sugarlabs.org
download.sugarlabs.org:/download/sources/honey/...
download.sugarlabs.org:/download/sources/sucrose/fructose/...

== Subpages ==
{{Special:PrefixIndex/{{PAGENAME}}/}}

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

Supported systems

2011-05-08T10:53:17Z

Sridhar: correcting link

<noinclude>[[Category:Supported systems]]</noinclude>

:<big>'''Note:''' Development changes occur rapidly, and the documentation here lags the current state of systems development. For the latest information on any development project, visit their work sites.</big>

See [[Sugar System Stack]] for a picture of the software stack.
=== Ways to run Sugar ===

Determine which of the various methods of running Sugar meet your needs:
* '''Pre-installed Sugar:'''
*: Some computers come with Sugar pre-installed, most notably the OLPC XO-1 laptop.
* '''Live CD / Live USB:'''
*: Suitable for trying Sugar without having to install any software on almost any computer—just boot Sugar off of a CD or USB drive. '''Note:''' When booting a Live CD, the Journal is not automatically saved on shutdown, because the boot media is readonly. All changes are lost upon shutdown or reboot. This is not a limitation for Live USB installations. See our [[Sugar on a Stick]] project page.
* '''Install Sugar:'''
*: If you are running one of the currently supported distributions, you can install Sugar using your systems standard package manager, e.g., Synaptic, apt-get, or yum.
*: Make custom Fedora F11/F12 Sugar Install or Live DVD/CD's [http://wiki.sugarlabs.org/go/Community/Distributions/Fedora#Make_you_own_custom_Fedora_F11.2F12_Install_or_Live_DVD.2FCD.27s]
* '''Emulator/Virtualizer:'''
*: [[QEMU]], [[VirtualBox]], or [[VMware]] let you run Sugar in an emulator or by virtualization on your computer—you'll need to install an emulator from which you launch Sugar and one of the [[Emulator image files]].
Refer to the [[#Matrix of Sugar solutions|matrix]] below to find a Sugar solution that works for you.

=== Computer labs ===

* Bill Kerr has written up instructions for trying Sugar in computer labs which run only Windows
*:(Please see [http://billkerr2.blogspot.com/2008/07/evaluating-sugar-in-developed-world.html].)

* Caroline Meeks is developing a deployment model that only requires one USB stick per child. (Please see [[Sugar on a Stick]].)

==Matrix of Sugar solutions==
There are many ways to run Sugar:
* As a [[#Starch|complete disk image]] on an existing machine;
* As a [[#Sucrose|session]] on a Linux system; or
* As part of a [[#Systems|complete hardware-software platform]].

===[[/Technical considerations | Technical considerations]]===
: A discussion of '''technical considerations''' regarding supported systems.

===Starch===

[[Image:Sugar-on-CD-USB.jpg]]

[[Taxonomy#Starch.28es.29:_A_complete_disk_image_for_Sugar|Starch]] is a complete disk image for Sugar.
{{Dated}}
{| class="wikitable"
|+ '''A complete disk image for Sugar'''
|-
!Name
!Sugar Version
!Tested
!Notes
|-
|[[Image:Fedora.jpg|30px]][[Sugar on a Stick]] [[Sugar_on_a_Stick/Mango Lassi|Mango Lassi]]
| 0.90.3-1
|latest
|This is a Live USB of the Sugar, and one of the primary focuses of Sugar development. 
may be installed to HD/USB with liveinst in sugar-terminal
|-
|[[Image:Fedora.jpg|30px]][[Sugar on a Stick]] [[Sugar_on_a_Stick/Mirabelle|Mirabelle]]
| 0.88.0
|
|may be installed to HD/USB with liveinst in sugar-terminal
|-
|[[Image:Fedora.jpg|30px]][[Sugar on a Stick]] [[Sugar_on_a_Stick/Blueberry|Blueberry]]
| 0.86.3
|
|
|-
|[[Image:Fedora.jpg|30px]][[Sugar on a Stick]] [[Sugar_on_a_Stick/Strawberry|Strawberry]]
| 0.84.5
|
|
|-
|[ftp://rohrmoser-engineering.de/pub/XO-LiveCD/XO-LiveCD_091203.iso LiveBackup XO-LiveCD]
|0.82
|No
|This is a Live CD of the OLPC system. [ftp://rohrmoser-engineering.de/pub/XO-LiveCD/XO-LiveCD_090308.pdf Release Notes]
|-
|[[Image:Fedora.jpg|30px]]
|0.84.2
|yes
|Sugar Desktop on a Stick is a Fedora11 Sugar USB.img [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Linux#Download_of_Prebuilt_SUGAR-DESKTOP_USB.img_file] "real install" 4GB stick
|-
|[[Image:Fedora.jpg|30px]]
|
|
|Sugar on a Stick is a Fedora Live USB. There is also [http://dev.laptop.org/~cjb/rawhide-xo/ Fedora "Rawhide" on XO] development.
|-
|[[Image:Ubuntu.jpg|30px]][http://dev.laptop.org/~probono/sbuntu/ Ubuntu LiveCD/LiveUSB]
|0.82
|
|Instructions for installing a Ubuntu LiveUSB
|}

===Sucrose===

[[Taxonomy#Sucrose:_The_interface.2C_plus_a_set_of_demonstration_activities|Sucrose]] is the Sugar interface plus a set of demonstration activities. System maintainers should visit the [[Packaging Team]] page.

{| class="wikitable"
|+ '''The interface, plus a set of demonstration activities'''
|-
!Operating System !! Version !! Sugar Version !! Bundled !! Tested !! [[Packaging Team|Collaboration Links]] !! Notes
|-
|colspan=7 align=center|binary packages available
|-
|[[Image:Debian.jpg|30px]]Debian||5.0 (Squeeze)||0.84 - 0.88||Yes||Yes||http://cdimage.debian.org/debian-cd/5.0.7/i386/iso-cd/debian-507-i386-netinst.iso http://wiki.sugarlabs.org/go/Community/Distributions/Debian ||[http://wiki.debian.org/Sugar Sugar on Debian] ||
|-
|[[Image:Fedora.jpg|30px]]Fedora||7,8,9||0.82||Yes||Yes|| || [[Community/Distributions/Fedora | Sugar on Fedora]]
|-
|[[Image:Ubuntu.jpg|30px]]Ubuntu||8.04 (Hardy)||0.79.0-0ubuntu3||Yes||Yes||https://wiki.ubuntu.com/Sugar|| [[Community/Distributions/Ubuntu | Sugar on Ubuntu]]
|-
|[[Image:Ubuntu.jpg|30px]]Ubuntu ||8.10 (Intrepid)||0.82||Yes|| || || [[Community/Distributions/Ubuntu#Sucrose_0.82 | Sugar on Ubuntu]]
|-
|[[Image:Ubuntu.jpg|30px]]Ubuntu ||9.04 (Jackalope) 9.10 (Koala)||0.84||Yes|| || || [[Community/Distributions/Ubuntu#Sugar on Ubuntu 9.04 (jaunty) | Sugar on Jackalope or Koala]]
|-
|[[Image:Ubuntu.jpg|30px]]Ubuntu||10.04 10.10||sweets-0.88.1||Yes||Yes||[[Community/Distributions/Ubuntu]]|| [[Community/Distributions/Ubuntu | Sugar on Ubuntu]]
|-
|[[Image:Alt_linux_team_small.png|36px]]ALT Linux||4.1 Sisyphus||0.82 SugarPlatform-0.84||Yes|||| || [[Community/Distributions/ALTLinux | Sugar on ALT Linux]]
|-
|[[Image:mandriva.png|36px]]Mandriva||2009.1 Cooker||SugarPlatform-0.84 SugarPlatform-0.84||Yes Yes|||| ||[[Community/Distributions/Mandriva | Sugar on Mandriva]]
|-
|[[Image:mandriva.png|36px]]Mandriva||2010.0||SugarPlatform-0.86||Yes Yes|||| ||[[Community/Distributions/Mandriva | Sugar on Mandriva]]
|-
|[[Image:mandriva.png|36px]]Mandriva||2010.1 2010.2|||SugarPlatform-0.90.1 SugarPlatform-0.90.1||Yes Yes||Yes Yes||http://torrent.mandriva.com/public/2010.1/ http://torrent.mandriva.com/public/2010.2/ ||[[Community/Distributions/Mandriva | Sugar on Mandriva]]
|-
|[[File:Trisquel_icon.png|36px]]Trisquel||Trisquel-3.0 Trisquel-4.0.1 Trisquel-4.5|||SugarPlatform-0.86.2 sweets-0.88.1 SugarPlatform-0.90.1||Yes Yes Yes||Yes Yes Yes||http://devel.trisquel.info/sugar/trisquel-sugar_3.0-LATEST_i686.iso http://trisquel.info/en/download|| [[Community/Distributions/Trisquel]] [[Trisquel On A Sugar Toast]]
|-
|[[Image:Suse-small.jpg|36px]]OpenSUSE||11.3||0.88.0||Yes||Yes ||http://en.opensuse.org/Sugar http://download.opensuse.org/repositories/Education/images/iso/openSUSE-Sugar-11.3.i686-1.0.0-Build6.3.iso|| [http://en.opensuse.org/Sugar Sugar on OpenSUSE]]
|-
|[[Image:Apple.gif|36px]] OS X (Intel)|| || || || ||[[Emulator image files]] [[Sugar Creation Kit#Virtualbox-Virtualization]] || [[Supported_systems/Mac|Sugar on a Mac (in emulation)]]
|-
|[[Image:Caixa Mágica.png|36px]]Caixa Mágica||15||SugarPlatform-0.88 Uses Mandriva repos||Yes||Yes ||[http://wiki.sugarlabs.org/go/Community/Distributions/Magalh%C3%A3es#caixamagica-linux-live-15-final-GNOME-int-cdrom-i586_with_sugar_0.88.0 caixamagica-linux-live-15-final-GNOME-int-cdrom-i586_with_sugar_0.88.0] || [[Community/Distributions/Magalhães | Sugar on Magalhães]]
|-
|colspan=7 align=center|packages not pre-built
|-
|[[Image:Gentoo-logo.svg|36px]]Gentoo||2009-03-19||0.84 9999||Yes|| || || [[Community/Distributions/Gentoo | Sugar on Gentoo]]
|-
|[[Image:Slackware.png|65px]]||Slackware 12|| || || || ||[http://wiki.laptop.org/go/Sugar_on_Slackware Sugar on Slackware]
|-
|[[Image:XP.gif|78px]]||WindowsXP|| || ||No|| || [[Supported systems/Windows|Sugar on Windows (using QEMU)]]
|}

===Sugar for various hardware systems===
Since Sugar is now available on most major GNU/Linux distributions, it is possible to run Sugar almost any computer that can run GNU/Linux. We highlight some systems below. Please add your favorite to the list.

{| class="wikitable"
|+ '''Complete Sugar Solutions'''
|-
!Manufacturer
!Model
!Operating System
!Tested
!Notes
|-
| [http://www.laptop.org OLPC]
| XO-1
| Fedora 9
| Yes
| Standard (reference) distribution
|-
| [http://www.asus.com ASUSTeK]
| Eee PC
|
| In initial testing phase
|
|-
| [http://www.intel.com Intel]
| Classmate Gen 1 & Gen 2
|
| under development
|
|-
|MacBook Air
| MacBook Air
|OSX 10.6.6 (Virtualbox 4.0.2)[http://wiki.sugarlabs.org/go/Emulator_image_files#VirtualBox VirtualBox runs on most hardware and OS's]
|Works well in VirtualBox including wireless and magic mouse
|Burned Soas.iso for Soas-v4 and Soas-v3 boot fine [http://wiki.sugarlabs.org/go/Downloads#Apple_Mac_OS_X Apple_Mac_OS_X] [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Mac Sugar_on_a_Stick/Mac]
|}

== Getting the Sugar sources ==
Distributors can find the latest sources for the sucrose components [[Development Team/Release/CurrentRelease/Sucrose#Getting_the_sources|here]]. Each [http://sugarlabs.org/go/Development_Team/Release/Roadmap#Schedule sucrose roadmap] entry has as well links to the release pages of earlier releases.

==Updating Sugar to the Latest Version==


[http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu http://wiki.sugarlabs.org/images/e/e2/Ubuntu.jpg]


===Ubuntu===

'''[[Community/Distributions/Ubuntu]]'''
: UbuntuSugarRemix and 10.04LTS

'''https://wiki.ubuntu.com/Sugar'''
: UbuntuSugarRemix

The Sugar packages in
Ubuntu 9.04 and 8.10 [[Community/Distributions/Ubuntu#Using_sugar_PPAs]].

For a LiveCD/LiveUSB, check out the instructions [http://dev.laptop.org/~probono/sbuntu/].'''(Note that this produces a very old sugar version 0.82.1)'''

Updated sucrose packages are usually published in a PPA: See [[Community/Distributions/Ubuntu#Sugar_on_Ubuntu_8.04|here]] for details.

If you want up-to-the-minute freshness (and brokenness) you can use [[Development Team/Jhbuild|jhbuild]] to build from source instead of the released packages. Follow the instructions [[Development Team/Jhbuild#Creating_an_xsession_for_Sugar-jhbuild|here]] to install sugar-jhbuild as an xsession option.


[[File:Debian.jpg|link=Community/Distributions/Debian]]


===Debian===

'''http://wiki.sugarlabs.org/go/Community/Distributions/Debian'''
*sugar 0.88.0 works nicely in Debian squeeze

Sucrose packages are usually updated in unstable. These packages migrate to testing after a while. You can see the current package versions [http://packages.debian.org/search?keywords=sugar&searchon=names&suite=all&section=all here].

If you want up-to-the-minute freshness (and brokenness) you can use [[Development Team/Jhbuild|jhbuild]] to build from source instead of the released packages.


[http://wiki.sugarlabs.org/go/Community/Distributions/Fedora http://wiki.sugarlabs.org/images/1/1e/Fedora.jpg]


===Fedora===

==== Fedora LiveCD/Live USB ====
:Project page: http://fedoraproject.org/wiki/Sugar (superseding: http://fedoraproject.org/wiki/Sugar_Spin)

With this spin, you'll be able to run Sugar, which is developed by Sugarlabs and the desktop environment used on the OLPC, directly from a Live CD! You'll find several activities on the image including most notably...

* sugar-browse - a web browsing activity based on xulrunner
* sugar-write - a word processor based on abiword

...along with several other activities including Chat support.

:See our [[Sugar_on_a_Stick | Sugar on a Stick page]].

The Fedora OLPC SIG, https://fedoraproject.org/wiki/OLPC, will be importing further activities into Fedora, which might be installed using ''yum install sugar-*'' at a later time.

:Recent development spins:
::http://download.sugarlabs.org/soas/snapshots/1/

For more information, please refer to the announcement here:

https://www.redhat.com/archives/fedora-olpc-list/2008-December/msg00061.html

Fedora 11 Preview contains USB Creator which can make USB and SD's with persistence of Fedora F11 (and Sugar if added with Synaptic) and Soas-beta's [satellit 04/30/2009]

What if you wanted to put it quickly onto your USB Key? You'll just need to grab Luke Macken's liveusb-creator, which already includes support for the Sugar Spin. Here's the link:

:http://fedorahosted.org/liveusb-creator/

The liveusb-creator still contains an old link, which is the reason why you'll need to download the spin manually until this gets fixed.

'''Tip of the hat:''' Sebastian Dziallas and the Fedora team

==== Fedora on an OLPC XO ====

On an OLPC XO-1 laptop, run olpc-update as root.

Normally you only need to run ''olpc-update'' in the Terminal application with a build number, like this:

# sudo olpc-update 767

'''Note:''' Now you can do this by means of the graphical [[olpc:Sugar Control Panel|Sugar Control Panel]].

===OLPC Clean Install===

http://wiki.laptop.org/go/Clean-install_procedure

====Joyride====
See [[OLPC:Future releases]], the Joyride train is in the round house.

<big>Joyride is for developers; it is not supported. Joyride builds may cause data corruption and in rare cases, even cause hardware damage, so please do not use Joyride on mission-critical systems.</big>

Joyride contains all the "bleeding-edge" features that are being debugged for inclusion in the next release.

Open the Terminal application and type the following, substituting 2469 for the latest version number.

# olpc-update joyride-2469

'''What's the latest version?''' You can find the latest build number (shown above as 1779) at the bottom of http://xs-dev.laptop.org/~cscott/xo-1/streams/joyride/

Updates usually takes 10–15 minutes. It's advised that you plug your XO in while Sugar updates itself, then reboot it to see the new OS take effect.

==== Other Options ====

These are options that can be used with the update command:

# olpc-update --help
<pre><nowiki>
Usage:
olpc-update [options] --hints hints-file
olpc-update [options] [-rf] build-number
olpc-update [options] [-rf] --usb
olpc-update --version
olpc-update --help

For example:
olpc-update 630
olpc-update joyride-1779
olpc-update update.1-700

Options:
-h, --help show this help message and exit
-f, --full skip incremental update attempt.
--force force update to an unsigned build.
-r, --reboot reboot after a successful update.
--hints=FILE name of json-encoded hints dictionary identifying the desired
new version.
-u, --usb upgrade from new build on inserted USB stick.
-v display verbose progress information; repeat for more verbose
output.
-q, --quiet don't output anything; use exit status to indicate success.
--version display version and license information.
</nowiki></pre>

[[File:Gentoo-logo-small.jpg|link=Community/Distributions/Gentoo]]

==== Fedora on the XO-1 ====

One of the updated ways of installing sugar on the XO can be seen here.

http://wiki.laptop.org/go/F11_for_XO-1

==== SOAS on the XO ====
You can also install sugar on a stick on the XO-1

* [[Sugar_on_a_Stick/Installation/OLPC]]

===Gentoo===
* There are two methods to get Sugar on your Gentoo box: [[Community/Distributions/Gentoo#sugar-jhbuild|sugar-jhbuild]] and [[Community/Distributions/Gentoo#Sugar overlay|Sugar overlay]]. '''See''' [[Community/Distributions/Gentoo|Gentoo]] for details.


[[File:Alt_linux_team_tiny.png|link=Community/Distributions/ALTLinux]]


===ALT Linux===
* ALT Linux Team is an international software developers team, collectively working on [http://en.altlinux.org/Sisyphus Sisyphus].

*'''To install''' Sugar try these [[Community/Distributions/ALTLinux#Setup|packages]].


[[File:Mandriva.png|link=Community/Distributions/Mandriva]]


===Mandriva===
To install Sugar on Mandriva follow these [[Community/Distributions/Mandriva#Setup|instructions]].