Sugar Labs - User contributions [en]

Sugar on a Stick release process

2010-07-27T11:30:51Z

Sdz: /* Test image */

<noinclude><div id="contentSub">< [[Sugar on a Stick]]</div>{{TOCright}}[[Category:Sugar on a Stick]]</noinclude>
== Feature process ==

The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.

* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.

=== How to submit a feature for consideration ===
# Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. ('''TODO:''' create ''Category:SoaS_v4_Feature'' so people can make their pages belong to the appropriate category so that we know which version you're targeting ).
# Place a link to your proposal in the [[#Current feature ideas]] section of this page while you're working on the document.
# Send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.
# When you think your feature proposal is ready, move it to the [[#Features submitted for review]] section of this page. It will be brought up at the next [[Sugar on a Stick meeting]], where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!

=== Approved features for the current release ===

''Features must be added to this list by a member of the release team. Place complete feature proposals in the [[#Features submitted for review]] section for consideration at the next meeting.''

* [[Features/Sugar_0.90|Sugar 0.90]]
* [[Features/Revised_Browse_default-bookmarks.html]]

=== Features submitted for review ===

When your feature proposal is complete and ready to review, add it to the list below. These will be considered at the next [[Sugar on a Stick meeting]].

* [[Updated Activities from the Mirabelle list]]
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability]
* Add feature here

=== Current feature ideas ===

These feature ideas are in various stages of development.

* School server
* [[Kickstart generator]]
* btrfs and snapshots
* systemd
* [[More robust iso]]
* Control Panel section for setting display parameters (e.g., VGA out)
* Simplifying Making a Custom remix and sharing the .ksfile and the CD.iso files on the wiki[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability]

== Testing process ==

Our test process, which is under construction, will consist of the following:

# An agreed-upon image each week for testers to attack (the daily build on $datetime of each week, for instance)
# An agreed-upon set of test cases for them to execute (iow, the "test plan" thing we haven't had before)
# An agreed-upon place and format for the results from running those test cases to be reported to
# An agreed-upon $datetime each week by which all test results for that week will be submitted - so that the development team has a chance to look at those results and revise the build before the next test image goes out.

The first thing we are doing is getting a weekly image under test to automatically appear at a static link; see [[#Test image]] below. We are going to set up a cron job so the nightly build (from http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ - which we need to start up again from the Fedora side) grabs and archives the appropriate image-under-test each week.

The last weekly testing update was 6/21/2010: http://lists.sugarlabs.org/archive/soas/2010-June/001560.html

=== Test image ===

<big><big>[http://people.sugarlabs.org/Tgillard/soas-v4-0725-Remix.iso Download the current (temporary) image under test]</big></big>

'''SPECIAL UPDATE, July 27, 2010: This week's test image is a remix by Tom Gillard due to a [https://bugzilla.redhat.com/show_bug.cgi?id=617115 bug in upstream Fedora] that prevents the automatically generated test image from booting.''' The normal test case image is available at http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso and this page will be edited when it works once again.

The test image is the most recent [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ nightly build] as of 23:59:59 on the most recent Thursday. Past test images are available at http://download.sugarlabs.org/soas/test/.

=== Test cases ===

We do not yet have test cases. They will appear here when they are available.
:Note: See Discussion for Notes on testing
* Prototype Tests:
: Activity Testing http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table based on [http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests-GC.ods]
: Install Testing http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table
: http://wiki.sugarlabs.org/go/0.90/Testing

=== Test results ===

A basic template for reporting simple smoke test results is [[Features/Soas V4/ASLOxo Activity Test Table]]. This needs to be moved to a proper namespace, and instructions need to be written. Instructions will be listed here when they are available.

Sugar on a Stick meetings

2010-07-19T21:37:23Z

Sdz: /* Minutes */

<noinclude><div id="contentSub">< [[Sugar on a Stick]]</div>
<noinclude>{{TOCright}}[[Category:Meetings]]</noinclude>
== Meeting details ==

Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.

We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)

[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]

== How we run meetings ==

With as much involvement as possible at all times.

The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].

Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.

== Agenda ==

{{Anchor|Next_Meeting}}

=== Every meeting ===

* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement
* [[Sugar on a Stick release process#Features submitted for review]]

=== Upcoming meeting ===

* http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process
* mtd: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases."
* what people plan to work on for the v4 cycle

== Future topics ==

== Procedure for Minutes and Logging ==

See the instructions on [[how to run a meeting]].

== Minutes ==
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html 2010-07-19 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100719_1506.html (log)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100712_1503.html 2010-07-12 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100712_1503.html (log)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]
* 2010-06-28 (no meeting)
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]

Sugar on a Stick meetings

2010-07-08T12:34:42Z

Sdz: /* Minutes */

<noinclude>{{TOCright}}
[[Category:Sugar on a Stick]]
[[Category:Meetings]]
</noinclude>
== Meeting details ==

Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.

We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)

[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]

== How we run meetings ==

With as much involvement as possible at all times.

The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].

Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.

== Agenda ==

{{Anchor|Next_Meeting}}

=== Every meeting ===

* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement
* [[Sugar on a Stick release process#Features submitted for review]]

=== Upcoming meeting ===

* http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process
* mtd: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases."
* what people plan to work on for the v4 cycle

== Future topics ==

== Procedure for Minutes and Logging ==

See the instructions on [[how to run a meeting]].

== Minutes ==
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]
* 2010-06-28 (no meeting)
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]

Sugar on a Stick meetings

2010-06-21T14:58:37Z

Sdz: /* Agenda */

<noinclude>{{TOCright}}
[[Category:Sugar on a Stick]]
[[Category:Meetings]]
</noinclude>
== Meeting details ==

Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.

We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)

[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]

== How we run meetings ==

With as much involvement as possible at all times.

The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].

Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.

== Agenda ==

{{Anchor|Next_Meeting}}

* [[Features/Revised_Browse_default-bookmarks.html]] - feature for consideration
:: Suggested that this use link to Wiki Page '''Introduction_to_Soas-v3_Mirabelle''' [http://wiki.sugarlabs.org/go/Talk:Sugar_Creation_Kit#Introduction_to_Soas-v3_Mirabelle]-To be updated for v4 when it is released
* dev-test-release cycle.
* mtd: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases."
* what people plan to work on for the v4 cycle

== Procedure for Minutes and Logging ==

See the instructions on [[how to run a meeting]].

== Minutes ==
* [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html 2010-06-14 (weekly meeting)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]

Sugar on a Stick release process

2010-06-07T21:49:32Z

Sdz: /* Feature process */

'''This page is a stub.''' It hasn't yet been filled in, but will be filled in soon - in the meantime, see [[Sugar on a Stick]] for more details about the project as a whole, or email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] with any questions. If you can help start filling in this page, please jump in and edit!

== Feature process ==

The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.

* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!
* ''What do I have to do now?'' Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. Most importantly, make it belong to the appropriate category so that we know which version you're targeting ('''TODO:''' create ''Category:SoaS_v4_Feature''). Finally, send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.
* ''What will happen then?'' After you've incorporated feedback from the mailing lists and the proposal fits the guidelines listed above, we'll stick it on the agenda for the next of our [[Sugar_on_a_Stick_meetings|meetings]] where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager for that release and currently formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.

=== Current feature ideas ===

* School server
* [[Kickstart generator]]
* Sugar Creation Kit DVD
** For "sneakernet" and behind firewall installs.
** Only requires 1 download, can be copied locally for a complete build environment for SOAS.
** Contains .iso files and instructions needed to create Soas USB's plus a majority of the .xo files from ASLO for installing activities by drag-drop into the sugar Journal.
* ASLOxo (most of ASLO .xo files on a USB stick for Drag-drop installs to Sugar Journal)

[[Category:Sugar on a Stick]]

Sugar on a Stick meetings

2010-06-07T21:40:12Z

Sdz: minor edits for last meeting

<noinclude>{{TOCright}}
[[Category:Sugar on a Stick]]
[[Category:Meetings]]
</noinclude>
== Meeting details ==

Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.

We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)

[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]

== How we run meetings ==

With as much involvement as possible at all times.

The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].

Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.

== Agenda ==

{{Anchor|Next_Meeting}}

Our next meeting is the SoaS v.4.0 planning meeting. Things to be decided:

* name & colors (current proposals are as follows)

{|border="1" cellspacing="0"
|-
| '''Name''' || '''Submitter'''
|-
| Cloudberry || Walter
|-
| 'Ōhelo Berries || Thomas
|-
| Sequoyah || Caryl
|-
| Gooseberry || Bert
|-
| Vanilla || Peter
|-
| Cookies & Cream || Peter
|-
| Alphonso || Anish
|-
| Jambul || Harriet
|-
| Sweet Cream || Mel
|-
| Lilikoi || Tom
|}

* dev-test-release cycle.

== Procedure for Minutes and Logging ==

See the instructions on [[how to run a meeting]].

== Minutes ==

* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]

Sugar on a Stick release process

2010-06-06T16:43:35Z

Sdz: /* Feature process */

'''This page is a stub.''' It hasn't yet been filled in, but will be filled in soon - in the meantime, see [[Sugar on a Stick]] for more details about the project as a whole, or email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] with any questions. If you can help start filling in this page, please jump in and edit!

== Feature process ==

The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.

* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!
* ''What do I have to do now?'' Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. Most importantly, make it belong to the appropriate category so that we know which version you're targeting ('''TODO:''' create ''Category:SoaS_v4_Feature''). Finally, send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.
* ''What will happen then?'' After you've incorporated feedback from the mailing lists and the proposal fits the guidelines listed above, we'll stick it on the agenda for the next of our [[Sugar_on_a_Stick_meetings|meetings]] where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!

=== Current feature ideas ===

* School server
* [[Kickstart generator]]
* Sugar Creation Kit DVD
** For "sneakernet" and behind firewall installs.
** Only requires 1 download, can be copied locally for a complete build environment for SOAS.
** Contains .iso files and instructions needed to create Soas USB's plus a majority of the .xo files from ASLO for installing activities by drag-drop into the sugar Journal.
* ASLOxo (most of ASLO .xo files on a USB stick for Drag-drop installs to Sugar Journal)

[[Category:Sugar on a Stick]]

Sugar on a Stick release process

2010-06-05T16:06:32Z

Sdz: add more content to the feature process

'''This page is a stub.''' It hasn't yet been filled in, but will be filled in soon - in the meantime, see [[Sugar on a Stick]] for more details about the project as a whole, or email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] with any questions. If you can help start filling in this page, please jump in and edit!

== Feature process ==

The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.

* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!
* ''What do I have to do now?'' Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. Most importantly, make it belong to the appropriate category so that we know which version you're targeting ('''TODO:''' create ''Category:SoaS_v4_Feature''). Finally, send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.

=== Current feature ideas ===

* School server
* [[Kickstart generator]]
* Sugar Creation Kit DVD
** For "sneakernet" and behind firewall installs.
** Only requires 1 download, can be copied locally for a complete build environment for SOAS.
** Contains .iso files and instructions needed to create Soas USB's plus a majority of the .xo files from ASLO for installing activities by drag-drop into the sugar Journal.
* ASLOxo (most of ASLO .xo files on a USB stick for Drag-drop installs to Sugar Journal)

[[Category:Sugar on a Stick]]

Sugar on a Stick meetings

2010-06-05T10:21:18Z

Sdz: /* Agenda */

<noinclude>{{TOCright}}
[[Category:Sugar on a Stick]]
[[Category:Meetings]]
</noinclude>
== Meeting details ==

Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.

We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)

[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]

== How we run meetings ==

With as much involvement as possible at all times.

The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].

Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.

== Agenda ==

{{Anchor|Next_Meeting}}

Our next meeting is the SoaS v.4.0 planning meeting. Things to be decided:

* name & colors (current proposals are as follows)

{|border="1" cellspacing="0"
|-
| '''Name''' || '''Submitter'''
|-
| Cloudberry || Walter
|-
| 'Ōhelo Berries || Thomas
|-
| Sequoyah || Caryl
|-
| Gooseberry || Bert
|-
| Vanilla || Peter
|-
| Cookies & Cream || Peter
|-
| Alphonso || Anish
|-
| Jambul || Harriet
|-
|}

* [[Sugar_on_a_Stick#Release_schedule|release schedule]]
* [[Sugar_on_a_Stick_release_process#Feature_process|feature process]]
* [[SoaS Activity Criteria|activity criteria]] as a subset of the feature process
* dev-test-release cycle.

== Procedure for Minutes and Logging ==

See the instructions on [[how to run a meeting]].

== Minutes ==

* [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100531_1507.html 2010-05-31 v3 Mirabelle release review meeting (regular weekly time)]

Sugar on a Stick/Activity Criteria

2010-06-03T15:32:56Z

Sdz: /* Be hosted on ASLO */

<big><big><big>'''''This is a draft discussion.''' It does not reflect policy (yet) - it is our attempt to define a clear policy for inclusion for the '''4th release''' of SoaS (October 2010, as per the [http://spins.fedoraproject.org Fedora Spin] release cycle).''</big></big></big>

== Introduction ==

This page is for gathering requirements for Activity inclusion on the default [[Sugar on a Stick]] image. These are the criteria we will be using to begin discussion on Activity inclusion in v.4.0, due for release at the end of October 2010.

There is a table of activities mapped against these criteria on the [[Talk:SoaS_Activity_Criteria|discussion page]].

== Proposed requirements ==

=== Have some clear pedagogical purpose ===

'''Rationale:''' Sugar is being developed in service of learning. We should focus on activities that can convey this message and, ideally, be readily incorporated into a lesson plan.

'''Test:''' Not really a test, but we can solicit feedback from teachers who use Sugar as to whether or not they think a particular activity has sufficient impact to merit making the short list.

'''Instructions:''' Email iaep and sur lists to solicit feedback.

=== Be installable via a package in the Fedora repositories ===

'''Rationale:''' Since SoaS is a [http://spins.fedoraproject.org Fedora Spin], everything that ships on the default image must be a package in Fedora. This is an upstream requirement.

'''Test:''' The version desired for inclusion should be in the [https://admin.fedoraproject.org/pkgdb/ Fedora repository] for the current Fedora version under development (in this case, F14).

'''Instructions:''' See https://fedoraproject.org/wiki/PackageMaintainers for more information on how to make a package (or get a package made) in Fedora. We may want to clean this up or make a Sugar-specific guide to packaging Activities in particular, or gather a team of volunteers who offer to do the packaging for Activity maintainers.

=== Be hosted on ASLO ===

'''Rationale:''' http://activities.sugarlabs.org is the Sugar Labs community's primary online mechanism for updating and installing Activities.

'''Test:''' Go to http://activities.sugarlabs.org and search for the Activity name. You should:
* be able to find the Activity
* be able to see that the Activity is properly categorized in one or more categories
* be able to see that the Activity's metadata (version number, "works with", etc.) is up to date
* be able to read an accurate and up to date summary of the Activity on its ASLO page
* be able to successfully download and install the Activity from ASLO's web interface

'''Instructions:''' We've instructions for activity authors how to upload their activities [[Activity_Library/Authors|on the wiki]].

=== Be translated in Pootle ===

'''Rationale:''' In order to support the usage of SoaS (and SoaS remixes) by students from around the world, it is important that Activities be translateable and set up for easy localization. Pootle is the system Sugar Labs uses for localization.

:Note, it may not be not absolutely essential that the localization is hosted on the Sugar Labs / OLPC Pootle instance [http://translate.sugarlabs.org/]. By way of example, see a number projects listed [[Translation_Team/Pootle_Projects#Other_projects_of_interest_.28not_locally_hosted.29|here]], including GCompris and TuxPaint where localization is handled elsewhere. It may be more of a build-process issue than an L10n issue to pull the PO files from these other sites. Requiring dual hosting of L10n doesn't sound like a win.[[User:Cjl|Cjl]] 17:04, 30 March 2010 (UTC)

'''Test:''' I am not sure what a good set of minimal "you are translateable" criteria would be. Suggestions?

:1) Simplest would be presence of the PO file in the Honey (or sometimes Fructose) projects on translate.sugarlabs.org; however, this is not always the case.

:2) Alternative acceptable (localized elsewhere) with clear documentation of how to participate in localization and get the localized PO files from their primary hosting location.

:[[User:Cjl|Cjl]] 17:14, 30 March 2010 (UTC)

'''Instructions:''' I can't find clear step-by-step instructions on how to get one's Activity into Pootle - can anyone else help find (or create) them?

: There are really only minimal instructions in the FAQ [[Translation_Team/FAQ#How_do_I_add_a_project_to_be_translated_.3F|here]], there is no question that we could use some improvement to our Translation Team documentation, including a better "Developer's Guide" entry point. [[User:Cjl|Cjl]] 17:14, 30 March 2010 (UTC)

=== Have a usage frontpage ===

'''Rationale:''' Users (particularly teachers) should be able to find a quick getting-started guide on usage that will let them evaluate whether they want to use an Activity for their classroom or not. They should be able to get a sense of what they can do with an Activity without having to spend an hour or two (per Activity!) exploring it in-depth - this page will provide what they need to decide whether they ''do'' want to spend an hour or two experimenting to figure out how they specifically want to use it with their class.

'''Test:''' The ASLO page for an Activity should include a link called "instructions for users" (note: this is fairly arbitrary and we may want to standardize on a better title/format) that leads to a tutorial on how to start and run the Activity in question. This can be anything from a page on the Sugar Labs wiki with screenshots all the way up to a [http://en.flossmanuals.net/ flossmanuals book] on just that Activity.

Suggested things for inclusion:

* what the Activity does
* intended audience (what assumptions does the design make? does it assume you can read, add, etc?)
* how to install it (can link to generic Activity instructions)
* how to start it (can link to generic Activity instructions)
* how to uninstall it (can link to generic Activity instructions)
* how to stop it (can link to generic Activity instructions)
* an explanation of the interface (what do the different buttons, etc. do?)
* how to begin exploring it (this can take several forms: a walkthrough of a few basic tasks, some hints on exercises/things-to-try, a link to galleries of existing work and classroom stories of that Activity's usage, etc.)

'''Instructions:''' We need to write instructions and gather more examples for this. Right now the best examples are the [http://en.flossmanuals.net/ flossmanuals books] on various Activities, but to expect every Activity to do a book seems like too much - we need examples of a good minimum bar, which is likely to be a well-made wiki page.

=== Have a development frontpage ===

'''Rationale:''' If an Activity is included on SoaS, it will be used by many people; in order to hold to the Sugar Labs principle of hackability (particularly by children), we need a good resource to get new hackers started.

'''Test:''' The ASLO page for an Activity should include a link called "get started with development" (note: this is fairly arbitrary and we may want to standardize on a better title/format) that leads to a place with instructions on how people can...
* view the source code
* download the source code
* modify the source code
* share their modifications
* view existing tickets/bugs/suggestions for things to work on

You may notice that the first 4 entries on this list map to the [http://www.gnu.org/philosophy/free-sw.html 4 essential software freedoms].

'''Instructions:''' We need instructions/examples of this. Please help!

=== Have a ticket queue ===

'''Rationale:''' Users need a place to report bugs.

'''Test:''' The ASLO page for an Activity should include a link called "report a bug / suggest an enhancement" (note: this is fairly arbitrary and we may want to standardize on a better title/format) that leads to the "new ticket" entry for that Activity's component (which may or may not be hosted on http://bugs.sugarlabs.org, especially in the case of an upstream project such as EToys). Since we may not be standardizing on bug trackers, each Activity ASLO page should also have a link to instructions on how to file a bug, perhaps something similar to [[BugSquad/Bug Report|this tutorial]]).

'''Instructions:''' The simplest way to do this is to get a Trac component for your Activity. We need instructions on how to do this (although I believe it is as simple as filing a Trac ticket requesting a Trac component). We may want to discuss ways that students and teachers can report bugs without having to create a Trac username (which is, for some, a significant barrier to entry - not that it's difficult to make an account, but that there may be reluctance to create an account, particularly for children).

=== Have and pass a smoke test ===

'''Rationale:''' We need a quick way to make sure the Activity works, so the Activity needs to define what it means for it to "work," and then come up with a straightforward set of instructions that anyone can use to demonstrate and/or verify that it is working.

'''Test:''' This should be fairly simple.
* Do you have a smoke test?
* Did you run it? (Can anyone else run it?)
* Did it pass? (Can you prove it?)
* Is there a place to file results? (Can people find them?)

'''Instructions:''' We need a guide on how to make a good smoke test. Sample Activity tests can be found at http://wiki.laptop.org/go/Test_cases_8.2.0#Activity-specific_test_cases, but they're old and there's no guidance on which are good tests or not.

=== Journal interaction works ===

'''Rationale:''' The Journal is one of the most interesting aspects of the Sugar platform and it really showcases what makes Sugar different.

'''Test:''' Test to make sure that the activity saves and resumes from the Journal.

'''Instructions:''' (1) Launch the activity. (2) Use the activity. (3) Close the activity. (4) Open the Journal entry associated with the activity. Did a preview image get created? (5) Resume the activity. Was the previous state of the activity restored?

=== Collaboration works ===

'''Rationale:''' Collaboration is one of the most interesting aspects of the Sugar platform and it really showcases what makes Sugar different.

'''Test:''' This only applies if the activity supports collaboration. Test to make sure that two SOAS can see the activity that is shared, join the activity, see the correct data during collaboration, and make sure it handles the originator leaving the activity gracefully.

'''Instructions:''' I am not sure what to put here, is this instructions for doing the test or for fixing collaboration bugs?

=== Add your own idea here ===

Be sure to describe:

'''Rationale:''' Where does this requirement come from and why is it important?

'''Test:''' how we can make sure that the requirement is met - what sort of testing needs to be done to verify this?

'''Instructions:''' links to instructions on how Activity authors and maintainers can fulfill the requirement, if possible.

[[Category:Sugar on a Stick]]

Sugar on a Stick/Mirabelle

2010-05-30T17:41:41Z

Sdz: /* Press coverage */

<noinclude>
[[Category:Live USB]]
[[Category:Sugar on a Stick]]
</noinclude>

{|
|-
| style="border: 0; border-width: 0;" |
== Sugar on a Stick - Mirabelle ==
: ''a Sugar environment you can carry in your pocket''

Mirabelle is the most recent release of the '''[[Sugar on a Stick]]''' project. It was released on '''25 May 2010.''' Mirabelle is named after the [[wikipedia:Mirabelle | Mirabelle plum]].
__TOC__

| style="border: 0; border-width: 0; width: 200px;" |[[File:SugaronastickMirabelle.png|450px|right|a Sugar environment you can carry in your pocket!]]
|}

== Release announcement ==

We are proud to announce the availability of [[Sugar on a Stick]] v.3, code-named Mirabelle. More information about Sugar on a Stick, including download and installation details, is available at http://spins.fedoraproject.org/soas/.

[[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]

=== What's new in Mirabelle ===

{|
|-
| style="border: 0; border-width: 0; width: 200px;" | [[File:Mirabelle-home-screen.png|200px|left|link=0.88/Notes]]
| style="border: 0; border-width: 0;" |
'''Sugar version 0.88.''' The most recent release of the Sugar Learning Platform features support for 3G connections, increased accessibility, and better integration with our Activity Portal (http://activities.sugarlabs.org) allowing students and teachers to update their sticks with additional Activities. More information about the 0.88 release of Sugar is available at [[0.88/Notes]].
|}

{|
|-
| style="border: 0; border-width: 0;" |
'''Customize your own remix of Sugar on a Stick.''' You'll notice that v.3 Mirabelle has a smaller Activity selection than its predecessors, Blueberry and Strawberry. We realized we'll never be able to create an Activity selection suitable for all deployments - instead, we've chosen to include and support a core set of basic, teacher-tested Activities in the default image, and invite deployments to use this as a base on which to build a customized Activity selection for their classrooms. Instructions on how to do this are available at http://download.sugarlabs.org/soas/docs/customization-guide/. A quick, but less pristine, method of build customization is available at [[Sugar on a Stick/Sugar Clone]].
| style="border: 0; border-width: 0; width: 120px;" |[[File:Cici-stick.jpg|120px|right|http://download.sugarlabs.org/soas/docs/customization-guide/]]
|}

{|
|-
| style="border: 0; border-width: 0; width: 150px;" | [[File:Fedora remix logo.png|left|link=http://spins.fedoraproject.org/soas]]
| style="border: 0; border-width: 0;" |
'''Sugar on a Stick is now a Fedora Spin.''' After two prior releases of being based on the [http://fedoraproject.org/wiki/Overview Fedora distribution], Sugar on a Stick has been recognized by the [http://fedoraproject.org Fedora Project] as an official [http://spins.fedoraproject.org Spin]. This ties us more closely to Fedora's release cycle and gives us resources from their engineering and marketing teams, which extends the reach of Sugar on a Stick and makes the project itself more sustainable. In exchange, users of Fedora have access to an easily deployable implementation of the Sugar Platform; it's a great example of a mutually beneficial upstream–downstream relationship.
|}

=== Contributing to Sugar on a Stick ===

The biggest difference in v.3 of Sugar on a Stick has been in its release processes and engineering sustainability; it's now much easier for new contributors to get involved. We continue to move towards our long-term vision of bringing stability and deployability to Sugar's personalized learning environment, and invite all interested parties to join us.

If you'd like to contribute to the next version, due for release in early November, join us at our Contributors Portal at '''[[Sugar on a Stick]]'''. All types of contributions are welcome, from the technical to the pedagogical, and we're happy to teach what we know and learn what you have to share.

Thank you to all the people involved for their awesome work!

== Press coverage ==

Feel free to add links to press coverage you find about Mirabelle to this section.

* [http://blog.internetnews.com/skerner/2010/05/sugar-on-a-stick-mirabelle-get.html 2010-05-28 Sugar on a Stick gets sweeter with Fedora Linux (InternetNews)]
* [http://www.linux-magazin.de/content/view/full/51984 2010-05-28 Sugar on a Stick v3.0 geht ins GSM-Netz (Linux-Magazin)]
* [http://www.pro-linux.de/news/1/15722/sugar-on-a-stick-v3-freigegeben.html 2010-05-27 Sugar on a Stick v3 freigegeben (Pro-Linux.de)]
* [http://lwn.net/Articles/389346/ 2010-05-26 Announcing Sugar on a Stick v.3 (LWN.net)]

Sugar on a Stick/Install

2010-05-25T23:42:04Z

Sdz: redirect for now: release time

#REDIRECT [[Sugar_on_a_Stick]]

Marketing Team/Events/LinuxTag2010

2010-05-17T14:23:52Z

Sdz: /* Attendees */

{{TOCright}}

= LinuxTag 2010 =

[http://www.linuxtag.org/2010/en.html http://www.linuxtag.org/2010/fileadmin/www.linuxtag.org/images/linuxtag-logo/LinuxTag-Logo-plain-blue.png]

== Event Details ==
LinuxTag is the most important place for Linux and open source software in Europe. In 2010, the 16th LinuxTag presents news for professional users, decision makers, developers, beginners and the Linux community - from '''9th until 12th June''' on the Fairground in Berlin.
For more information, go to the [http://www.linuxtag.org/2010/en.html LinuxTag 2010 website].

[http://www.linuxtag.org/2010/en/besucher/reiseplanung.html Here] are instructions how you get to Linuxtag.

== Sugar Organizer ==

[[User:Erikos | Simon Schampijer]] will be organizing Sugar's presence at LinuxTag 2010.

== Attendees ==

Are you planning to attend? Add your name and contact info below!

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name !! available from to !! stays at !! Note
|-
! [[User:Erikos | Simon Schampijer]]
| - || local || -
|-
! [[User:raffael.reichelt | Raffael Reichelt]]
| - || local || -
|-
! [[User:tony37 | Tony Anderson]]
| - || local || -
|-
! [[User:Sdz | Sebastian Dziallas]]
| - || to be determined || -
|}

== Sugar Activities ==
Sugar does advocate the concepts of activities - you learn through doing, so if you want more learning you want more doing. So the Sugar Labs team wants to get engaged at Linuxtag:

# We will aim to have a booth like last year
# There should be talks about Sugar, too

== Sugar Booth ==
''to be determined''



=== Shifts ===
''to be determined''


=== Storage Space ===
We have a coops (Germans would say Kabüffchen as a diminutive of Kabuff) at the booths. As this is only meant for booth equipment all the other belongings like jackets, luggage etc can be stored at the wardrobe without any cost.

=== Power and Internet Connectivity ===
Power and Internet will be provided by LinuxTag and Messe Berlin for the project booths. What we need are:
* extension cords
* long network cables
* switches

Not permitted by Linuxtag:
* wireless access points (You are not permitted to operate your private wireless LAN. Please take this serious. There will be several site surveys to ensure this.) - Mesh networking is allowed though
* coffeemakers, kettles and cooking stuff
* connect visitors to the project's network

=== Lunch ===
Linuxtag is offering Lunch for the helpers. If we want to participate we would need helpers and not only eaters. More information can be found [http://wiki.linuxtag.org/w/fp:Lunch_2009 at].

=== Flyer ===
* [[Media:Flyer_deutsch.pdf | german version PDF]]
* [[Media:Flyer_englisch.pdf | englisch version PDF]]

== TODO ==
''to be determined''

== Equipment ==
* Sugar Labs Booth Banner (1)
* Sugar Labs balloons (30), bars (68), clips (50)
* Flyers

== Lodging ==
* Accommodation Information from [http://www.linuxtag.org/2008/en/visitors/travel.html Linuxtag]
* [http://www.pension-freiraum.de/ Pension Freiraum]
** Nice area with bars restaurant cafe, about 25 minutes to the conference
* [http://www.hotel-funkturm-messe.de/english/home.html Hotel Funkturm]
** right next door to the conference area (room 4-6 persons, 100euro per night for the room, inclusive breakfast)

== Schedule ==
''to be determined''



== Impressions ==
''link your photos, add your comments here''

[[Category:Event]]

User:Sdz

2010-05-16T21:30:56Z

Sdz:

Sebastian Dziallas is a student, mainly working on the [[Sugar_on_a_Stick| Sugar on a Stick]] project right now. He's also working on Fedora, where he has founded the Education SIG and has attended FOSDEM 2009 in Brussels and SugarCamp 2009 in Berlin. You can reach him on IRC (nick: ''sdziallas''), while his blog is available [http://sdziallas.com/ here]. His Fedora user page lives [http://fedoraproject.org/wiki/User:Sdz here].

Summer of Code/2010/Improved Sugar on a Stick

2010-04-08T18:51:06Z

Sdz:

<noinclude>{{TOCright}}
[[Category:2010 GSoC applications]]
[[Category:GSoC]]
</noinclude>

=== About you ===

# What is your name? Sebastian Dziallas
# What is your email address? sebastian@when.com
# What is your Sugar Labs wiki username? [[User:Sdz|sdz]]
# What is your IRC nickname? sdziallas
# What is your primary language? German; English and French work fine, though.
# Where are you located, and what hours do you tend to work? Located close to Hannover in Germany with variable work hours; might be in different time zones during the summer.
# Have you participated in an open-source project before?
#* http://fedoraproject.org/wiki/User:Sdz
#* http://wiki.sugarlabs.org/go/User:Sdz

=== About your project ===

# What is the name of your project? Improving Sugar on a Stick
# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
#* I'm going to work on improving the means of communication between users, like students or deployments, and developers to reach out for feedback and interact. One of the biggest issue Sugar on a Stick has been facing in recent times is a lack of specific feedback. This is especially of importance, since Sugar on a Stick unites the Sugar learning environment with the Fedora linux distribution. Different, not-entirely-aligned release cycles have been a source for issues.
#* I plan to integrate features addressing this lack of feedback directly in the Sugar control panel -- or within a set of activities -- by making heavy use of various upstream projects. This proposal mentions a number of possible projects, which are all related, since they all partially address a certain area of these issues and would all have to be integrated in the control panel. This integration requires knowledge of Python, as well as of the general Sugar on a Stick build process using kickstart files.
#* The project I will tackle first is integrating Fedora's [https://fedorahosted.org/smolt/ Smolt] initiative in Sugar. Since Sugar on a Stick relies on the underlying distribution, understanding what hardware our users are using is crucial, especially when it comes to understanding and eventually fixing issues. By integrating this functionality, the process of fixing hardware related issues will improve significantly, as users will not need to execute cryptic commands and upload logs anymore, but will rather be able to post a link to their profile.
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
#* I'll be evaluating options of different options on file system usage for Sugar on a Stick, if time permits.
#* This also includes work on the [https://fedorahosted.org/liveusb-creator LiveUSB Creator], towards which this propsal might shift. Generally, I'll be trying to improve SoaS through providing, integrating or improving essential tools.
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
#* While the timeline is set in stone here already, the projects I'll be working on may shift with regard to the proposal above.
#* May 24 - 30: initial gathering of information, diving into python
#* May 31 - June 6: creation of first mockups
#* June 7 - 13: evaluation of upstream code base
#* June 14 - 20: further python knowledge gathering
#* June 21 - 27: attempt to integrate smolt into the control panel
#* June 28 - July 4: coding
#* July 5 - 11: evaluation of smolt integration, possible cleanups
#*--- mid-terms ---
#* July 12 - 18: creation of mockups for abrt
#* July 19 - 25: evaluation of upstream code base
#* July 26 - August 1: further python knowledge gathering
#* August 2 - 8: attempt to integrate abrt into the control panel
#* August 9 - 15: evaluation, possible cleanups and look at packagekit
# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
#* I've been part of the Sugar Labs community for probably two years now. However, my story starts earlier, when I was in high school and looking for an open source operating system. Somehow, I found my way into the Fedora Project and met people like Greg DeKoenigsberg. Suddenly I was not only leading the Fedora Education SIG, but also working on OLPC's operating system for the second G1G1 program. Later on, I worked on the Fedora Sugar Spin, which ultimately merged with the early Sugar on a Stick efforts, making the latter what it is now. I've been experienced several release cycles of open source software engineering thus far and am especially looking forward to work on coding over the summer.

=== You and the community ===

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
## Sugar on a Stick is a project that "enables children to reclaim computers". It's a project that reaches even further than other approaches seen before, as it significantly lowers the entry barrier for people to get their hands on their own personalized Sugar Learning Experience. By making this experience even better -- which is what this project aims for -- the general improvements arrive at one of Sugar's main ways of distribution. However, Sugar on a Stick is not just a distribution, it's a way of deploying Sugar. Successful pilots are taking off right now in Berlin and Boston and these kids there won't be the only ones to get their hands on the resulting improvements. Instead, the improvements will be included in the next iteration of Sugar on a Stick, enabling them to interact directly with our developers, resulting in a better product. [[User:Sdz| Sebastian Dziallas]]
## Sugar on a Stick is a cornerstone of the Sugar Labs strategy for reaching out to parents, teachers, and children. It provides a simple way for someone to give Sugar a test drive and it provides a cost-effective way to initiate and expand Sugar-based deployments (every child can use Sugar even though not every child can yet be given a computer of their own). This GSoC project is addresses some critical aspects of the Sugar-on-a-Stick project: user feedback and documentation. Specifically, the integration of Smolt will greatly enhance our ability to monitor the conditions under which Sugar on a Stick is being used, capturing a detailed record that will be invaluable to the development and support teams as they strive to make the project both more far reaching and robust. While it is not glamorous, it is critical to our being able to sustain and support Sugar on the variety of hardware found in the field. [[User:Walter| Walter Bender]]
## ''[comment needed -- commenter 2]''
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
#* I've been leading and coordinating technical support for a small XO deployment in a school here. While this might be an option, there are also other Sugar on a Stick related deployments currently going on in Berlin (Simon) and Boston (Mel) -- cooperating with these might be a good way of getting actual results from the field.
# What will you do if you get stuck on your project and your mentor isn't around?
#* Generally, I'd either try to get in touch with people I know from previous work who are aware of the issues I'd be facing or simply attempt to ask for more help in the appropriate channels, such as #sugar for directly development related topics and #fedora-olpc or #fedora-devel for questions related to the distribution itself. In case the latter one wouldn't be successful, I'd send emails off to the mailing lists, asking for help with a specific issue.
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
#* My blog is currently aggregated on both the Fedora Project's and Sugar Labs' planets, which is also where I'm going to post continuously about the state of my project and its progress. For more concrete questions, I'll be using the mailing list and IRC channels to interact directly with other developers.

=== Miscellaneous ===

# We want to make sure that you can set up a development environment before the summer starts: [http://sdz.fedorapeople.org/sugar-emulator.png click here]
# What is your t-shirt size? '''L'''
# Describe a great learning experience you had as a child.
#* The experience I'm going to describe didn't exactly in my childhood, but rather when I was growing up, actually not too long ago. It was when a good friend of mine gave me a Dr. Seuss book: ''"Oh, the Places you'll go"''! It's one of the most wonderful books I ever read -- and so is its message. It encourages you to keep going, no matter what happens, no matter how hard or lonely the world may seem. Because in the end, you'll succeed - ''"Yes! You will, indeed! (98 and 3/4 percent guaranteed.)"''. So you'll move mountains. And that's what I learned.
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
#* I apparently like Mirabelles and Cloudberries.

Summer of Code/2010/Improved Sugar on a Stick

2010-04-07T15:56:50Z

Sdz:

<noinclude>{{TOCright}}
[[Category:2010 GSoC applications]]
[[Category:GSoC]]
</noinclude>

=== About you ===

# What is your name? Sebastian Dziallas
# What is your email address? sebastian@when.com
# What is your Sugar Labs wiki username? [[User:Sdz|sdz]]
# What is your IRC nickname? sdziallas
# What is your primary language? German; English and French work fine, though.
# Where are you located, and what hours do you tend to work? Located close to Hannover in Germany with variable work hours; might be in different time zones during the summer.
# Have you participated in an open-source project before?
#* http://fedoraproject.org/wiki/User:Sdz
#* http://wiki.sugarlabs.org/go/User:Sdz

=== About your project ===

# What is the name of your project? Improving Sugar on a Stick
# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
#* I'm going to work on improving the means of communication between users, like students or deployments, and developers to reach out for feedback and interact. One of the biggest issue Sugar on a Stick has been facing in recent times is a lack of specific feedback. This is especially of importance, since Sugar on a Stick unites the Sugar learning environment with the Fedora linux distribution. Different, not-entirely-aligned release cycles have been a source for issues.
#* I plan to integrate features addressing this lack of feedback directly in the Sugar control panel -- or within a set of activities -- by making heavy use of various upstream projects. This proposal mentions a number of possible projects, which are all related, since they all partially address a certain area of these issues and would all have to be integrated in the control panel. This integration requires knowledge of Python, as well as of the general Sugar on a Stick build process using kickstart files.
#* The project I will tackle first is integrating Fedora's [https://fedorahosted.org/smolt/ Smolt] initiative in Sugar. Since Sugar on a Stick relies on the underlying distribution, understanding what hardware our users are using is crucial, especially when it comes to understanding and eventually fixing issues. By integrating this functionality, the process of fixing hardware related issues will improve significantly, as users will not need to execute cryptic commands and upload logs anymore, but will rather be able to post a link to their profile.
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
#* I'll be evaluating options of different options on file system usage for Sugar on a Stick, if time permits.
#* This also includes work on the [https://fedorahosted.org/liveusb-creator LiveUSB Creator], towards which this propsal might shift. Generally, I'll be trying to improve SoaS through providing, integrating or improving essential tools.
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
#* While the timeline is set in stone here already, the projects I'll be working on may shift with regard to the proposal above.
#* May 24 - 30: initial gathering of information, diving into python
#* May 31 - June 6: creation of first mockups
#* June 7 - 13: evaluation of upstream code base
#* June 14 - 20: further python knowledge gathering
#* June 21 - 27: attempt to integrate smolt into the control panel
#* June 28 - July 4: coding
#* July 5 - 11: evaluation of smolt integration, possible cleanups
#*--- mid-terms ---
#* July 12 - 18: creation of mockups for abrt
#* July 19 - 25: evaluation of upstream code base
#* July 26 - August 1: further python knowledge gathering
#* August 2 - 8: attempt to integrate abrt into the control panel
#* August 9 - 15: evaluation, possible cleanups and look at packagekit
# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
#* I've been part of the Sugar Labs community for probably two years now. However, my story starts earlier, when I was in high school and looking for an open source operating system. Somehow, I found my way into the Fedora Project and met people like Greg DeKoenigsberg. Suddenly I was not only leading the Fedora Education SIG, but also working on OLPC's operating system for the second G1G1 program. Later on, I worked on the Fedora Sugar Spin, which ultimately merged with the early Sugar on a Stick efforts, making the latter what it is now. I've been experienced several release cycles of open source software engineering thus far and am especially looking forward to work on coding over the summer.

=== You and the community ===

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
## Sugar on a Stick is a project that "enables children to reclaim computers". It's a project that reaches even further than other approaches seen before, as it significantly lowers the entry barrier for people to get their hands on their own personalized Sugar Learning Experience. By making this experience even better -- which is what this project aims for -- the general improvements arrive at one of Sugar's main ways of distribution. However, Sugar on a Stick is not just a distribution, it's a way of deploying Sugar. Successful pilots are taking off right now in Berlin and Boston and these kids there won't be the only ones to get their hands on the resulting improvements. Instead, the improvements will be included in the next iteration of Sugar on a Stick, enabling them to interact directly with our developers, resulting in a better product.
## ''[comment needed -- commenter 1]''
## ''[comment needed -- commenter 2]''
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
#* I've been leading and coordinating technical support for a small XO deployment in a school here. While this might be an option, there are also other Sugar on a Stick related deployments currently going on in Berlin (Simon) and Boston (Mel) -- cooperating with these might be a good way of getting actual results from the field.
# What will you do if you get stuck on your project and your mentor isn't around?
#* Generally, I'd either try to get in touch with people I know from previous work who are aware of the issues I'd be facing or simply attempt to ask for more help in the appropriate channels, such as #sugar for directly development related topics and #fedora-olpc or #fedora-devel for questions related to the distribution itself. In case the latter one wouldn't be successful, I'd send emails off to the mailing lists, asking for help with a specific issue.
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
#* My blog is currently aggregated on both the Fedora Project's and Sugar Labs' planets, which is also where I'm going to post continuously about the state of my project and its progress. For more concrete questions, I'll be using the mailing list and IRC channels to interact directly with other developers.

=== Miscellaneous ===

# We want to make sure that you can set up a development environment before the summer starts: [http://sdz.fedorapeople.org/sugar-emulator.png click here]
# What is your t-shirt size? '''L'''
# Describe a great learning experience you had as a child.
#* The experience I'm going to describe didn't exactly in my childhood, but rather when I was growing up, actually not too long ago. It was when a good friend of mine gave me a Dr. Seuss book: ''"Oh, the Places you'll go"''! It's one of the most wonderful books I ever read -- and so is its message. It encourages you to keep going, no matter what happens, no matter how hard or lonely the world may seem. Because in the end, you'll succeed - ''"Yes! You will, indeed! (98 and 3/4 percent guaranteed.)"''. So you'll move mountains. And that's what I learned.
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
#* I apparently like Mirabelles and Cloudberries.

Summer of Code/2010/Improved Sugar on a Stick

2010-04-06T19:16:18Z

Sdz:

<noinclude>{{TOCright}}
[[Category:2010 GSoC applications]]
[[Category:GSoC]]
</noinclude>

'''This page is a draft. Its content is being moved around and this is just a giant braindump!'''

=== About you ===

# What is your name? Sebastian Dziallas
# What is your email address? sebastian@when.com
# What is your Sugar Labs wiki username? [[User:Sdz|sdz]]
# What is your IRC nickname? sdziallas
# What is your primary language? German; English and French work fine, though.
# Where are you located, and what hours do you tend to work? Located close to Hannover in Germany with variable work hours; might be in different time zones during the summer.
# Have you participated in an open-source project before?
#* http://fedoraproject.org/wiki/User:Sdz
#* http://wiki.sugarlabs.org/go/User:Sdz

=== About your project ===

# What is the name of your project? Improving Sugar on a Stick
# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
#* I'm going to work on improving Sugar on a Stick by finding ways for users, no matter whether they are students or deployments, to interact with developers. One of the biggest issue Sugar on a Stick has been facing in recent times is a lack of specific feedback. This is especially of importance, since Sugar on a Stick unites the Sugar learning environment with the Fedora linux distribution. Different, not-entirely-aligned release cycles have been a source for issues.
#* I plan to integrate features addressing this lack of feedback directly in the Sugar control panel by making heavy use of various upstream projects. This proposal mentions a number of possible projects, which are all related, since they all partially address a certain area of these issues and would all have to be integrated in the control panel. This integration requires knowledge of Python, as well as of the general Sugar on a Stick build process using kickstart files.
#* The project I will tackle first is integrating Fedora's [https://fedorahosted.org/smolt/ Smolt] initiative in Sugar. Since Sugar on a Stick relies on the underlying distribution, understanding what hardware our users are using is crucial, especially when it comes to understanding and eventually fixing issues. By integrating this functionality, the process of fixing hardware related issues will improve significantly, as users will not need to execute cryptic commands and upload logs anymore, but will rather be able to post a link to their profile.
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
#* I'll be evaluating options of different options on file system usage for Sugar on a Stick, if time permits.
#* This also includes work on the [https://fedorahosted.org/liveusb-creator LiveUSB Creator], towards which this propsal might shift. Generally, I'll be trying to improve SoaS through providing, integrating or improving essential tools.
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
#* May 24 - 30: initial gathering of information, diving into python
#* May 31 - June 6: creation of first mockups
#* June 7 - 13: evaluation of upstream code base
#* June 14 - 20: further python knowledge gathering
#* June 21 - 27: attempt to integrate smolt into the control panel
#* June 28 - July 4: coding
#* July 5 - 11: evaluation of smolt integration, possible cleanups
#*--- mid-terms ---
#* July 12 - 18: creation of mockups for abrt
#* July 19 - 25: evaluation of upstream code base
#* July 26 - August 1: further python knowledge gathering
#* August 2 - 8: attempt to integrate abrt into the control panel
#* August 9 - 15: evaluation, possible cleanups and look at packagekit
# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
#* I've been part of the Sugar Labs community for probably two years now. However, my story starts earlier, when I was in high school and looking for an open source operating system. Somehow, I found my way into the Fedora Project and met people like Greg DeKoenigsberg. Suddenly I was not only leading the Fedora Education SIG, but also working on OLPC's operating system for the second G1G1 program. Later on, I worked on the Fedora Sugar Spin, which ultimately merged with the early Sugar on a Stick efforts, making the latter what it is now. I've been experienced several release cycles of open source software engineering thus far and am especially looking forward to work on coding over the summer.

=== You and the community ===

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
## Sugar on a Stick is a project that "enables children to reclaim computers". It's a project that reaches even further than other approaches seen before, as it significantly lowers the entry barrier for people to get their hands on their own personalized Sugar Learning Experience. By making this experience even better -- which is what this project aims for -- the general improvements arrive at one of Sugar's main ways of distribution. However, Sugar on a Stick is not just a distribution, it's a way of deploying Sugar. Successful pilots are taking off right now in Berlin and Boston and these kids there won't be the only ones to get their hands on the resulting improvements. Instead, the improvements will be included in the next iteration of Sugar on a Stick, enabling them to interact directly with our developers, resulting in a better product.
## ''[comment needed -- commenter 1]''
## ''[comment needed -- commenter 2]''
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
#* I've been leading and coordinating technical support for a small XO deployment in a school here. While this might be an option, there are also other Sugar on a Stick related deployments currently going on in Berlin (Simon) and Boston (Mel) -- cooperating with these might be a good way of getting actual results from the field.
# What will you do if you get stuck on your project and your mentor isn't around?
#* Generally, I'd either try to get in touch with people I know from previous work who are aware of the issues I'd be facing or simply attempt to ask for more help in the appropriate channels, such as #sugar for directly development related topics and #fedora-olpc or #fedora-devel for questions related to the distribution itself. In case the latter one wouldn't be successful, I'd send emails off to the mailing lists, asking for help with a specific issue.
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
#* My blog is currently aggregated on both the Fedora Project's and Sugar Labs' planets, which is also where I'm going to post continuously about the state of my project and its progress. For more concrete questions, I'll be using the mailing list and IRC channels to interact directly with other developers.

=== Miscellaneous ===

# We want to make sure that you can set up a development environment before the summer starts: [http://sdz.fedorapeople.org/sugar-emulator.png click here]
# What is your t-shirt size? '''L'''
# Describe a great learning experience you had as a child.
#* The experience I'm going to describe didn't exactly in my childhood, but rather when I was growing up, actually not too long ago. It was when a good friend of mine gave me a Dr. Seuss book: ''"Oh, the Places you'll go"''! It's one of the most wonderful books I ever read -- and so is its message. It encourages you to keep going, no matter what happens, no matter how hard or lonely the world may seem. Because in the end, you'll succeed - ''"Yes! You will, indeed! (98 and 3/4 percent guaranteed.)"''. So you'll move mountains. And that's what I learned.
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
#* I apparently like Mirabelles and Cloudberries.

Summer of Code/2010/Improved Sugar on a Stick

2010-04-06T18:18:45Z

Sdz: /* About your project */

<noinclude>{{TOCright}}
[[Category:2010 GSoC applications]]
[[Category:GSoC]]
</noinclude>

'''This page is a draft. Its content is being moved around and this is just a giant braindump!'''

=== About you ===

# What is your name? Sebastian Dziallas
# What is your email address? sebastian@when.com
# What is your Sugar Labs wiki username? [[User:Sdz|sdz]]
# What is your IRC nickname? sdziallas
# What is your primary language? German; English and French work fine, though.
# Where are you located, and what hours do you tend to work? Located close to Hannover in Germany with variable work hours; might be in different time zones during the summer.
# Have you participated in an open-source project before?
#* http://fedoraproject.org/wiki/User:Sdz
#* http://wiki.sugarlabs.org/go/User:Sdz

=== About your project ===

# What is the name of your project? Improving Sugar on a Stick
# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
#* I'm going to work on improving Sugar on a Stick by finding ways for users, no matter whether they are students or deployments, to interact with developers. One of the biggest issue Sugar on a Stick has been facing in recent times is a lack of specific feedback. This is especially of importance, since Sugar on a Stick unites the Sugar learning environment with the Fedora linux distribution. Different, not-entirely-aligned release cycles have been a source for issues.
#* I plan to integrate features addressing this lack of feedback directly in the Sugar control panel by making heavy use of various upstream projects. This proposal mentions a number of possible projects, which are all related, since they all partially address a certain area of these issues and would all have to be integrated in the control panel. This integration requires knowledge of Python, as well as of the general Sugar on a Stick build process using kickstart files.
#* The project I will tackle first is integrating Fedora's [https://fedorahosted.org/smolt/ Smolt] initiative in Sugar. Since Sugar on a Stick relies on the underlying distribution, understanding what hardware our users are using is crucial, especially when it comes to understanding and eventually fixing issues. By integrating this functionality, the process of fixing hardware related issues will improve significantly, as users will not need to execute cryptic commands and upload logs anymore, but will rather be able to post a link to their profile.
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
#* I'll be evaluating options of different options on file system usage for Sugar on a Stick, if time permits.
#* The same applies for work on the [https://fedorahosted.org/liveusb-creator LiveUSB Creator].
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
#* May 24 - 30: initial gathering of information, diving into python
#* May 31 - June 6: creation of first mockups
#* June 7 - 13: evaluation of upstream code base
#* June 14 - 20: further python knowledge gathering
#* June 21 - 27: attempt to integrate smolt into the control panel
#* June 28 - July 4: coding
#* July 5 - 11: evaluation of smolt integration, possible cleanups
#*--- mid-terms ---
#* July 12 - 18: creation of mockups for abrt
#* July 19 - 25: evaluation of upstream code base
#* July 26 - August 1: further python knowledge gathering
#* August 2 - 8: attempt to integrate abrt into the control panel
#* August 9 - 15: evaluation, possible cleanups and look at packagekit
# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
#* I've been part of the Sugar Labs community for probably two years now. However, my story starts earlier, when I was in high school and looking for an open source operating system. Somehow, I found my way into the Fedora Project and met people like Greg DeKoenigsberg. Suddenly I was not only leading the Fedora Education SIG, but also working on OLPC's operating system for the second G1G1 program. Later on, I worked on the Fedora Sugar Spin, which ultimately merged with the early Sugar on a Stick efforts, making the latter what it is now. I've been experienced several release cycles of open source software engineering thus far and am especially looking forward to work on coding over the summer.

=== You and the community ===

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
## Sugar on a Stick is a project that "enables children to reclaim computers". It's a project that reaches even further than other approaches seen before, as it significantly lowers the entry barrier for people to get their hands on their own personalized Sugar Learning Experience. By making this experience even better -- which is what this project aims for -- the general improvements arrive at one of Sugar's main ways of distribution. However, Sugar on a Stick is not just a distribution, it's a way of deploying Sugar. Successful pilots are taking off right now in Berlin and Boston and these kids there won't be the only ones to get their hands on the resulting improvements. Instead, the improvements will be included in the next iteration of Sugar on a Stick, enabling them to interact directly with our developers, resulting in a better product.
## ''[comment needed -- commenter 1]''
## ''[comment needed -- commenter 2]''
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
#* I've been leading and coordinating technical support for a small XO deployment in a school here. While this might be an option, there are also other Sugar on a Stick related deployments currently going on in Berlin (Simon) and Boston (Mel) -- cooperating with these might be a good way of getting actual results from the field.
# What will you do if you get stuck on your project and your mentor isn't around?
#* Generally, I'd either try to get in touch with people I know from previous work who are aware of the issues I'd be facing or simply attempt to ask for more help in the appropriate channels, such as #sugar for directly development related topics and #fedora-olpc or #fedora-devel for questions related to the distribution itself. In case the latter one wouldn't be successful, I'd send emails off to the mailing lists, asking for help with a specific issue.
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
#* My blog is currently aggregated on both the Fedora Project's and Sugar Labs' planets, which is also where I'm going to post continuously about the state of my project and its progress. For more concrete questions, I'll be using the mailing list and IRC channels to interact directly with other developers.

=== Miscellaneous ===

# We want to make sure that you can set up a development environment before the summer starts: [http://sdz.fedorapeople.org/sugar-emulator.png click here]
# What is your t-shirt size? '''L'''
# Describe a great learning experience you had as a child.
#* The experience I'm going to describe didn't exactly in my childhood, but rather when I was growing up, actually not too long ago. It was when a good friend of mine gave me a Dr. Seuss book: ''"Oh, the Places you'll go"''! It's one of the most wonderful books I ever read -- and so is its message. It encourages you to keep going, no matter what happens, no matter how hard or lonely the world may seem. Because in the end, you'll succeed - ''"Yes! You will, indeed! (98 and 3/4 percent guaranteed.)"''. So you'll move mountains. And that's what I learned.
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
#* I apparently like Mirabelles and Cloudberries.

Summer of Code/2010/Improved Sugar on a Stick

2010-04-05T20:53:47Z

Sdz: /* You and the community */

'''This page is a draft. Its content is being moved around and this is just a giant braindump!'''

=== About you ===

# What is your name? Sebastian Dziallas
# What is your email address? sebastian@when.com
# What is your Sugar Labs wiki username? [[User:Sdz|sdz]]
# What is your IRC nickname? sdziallas
# What is your primary language? German; English and French work fine, though.
# Where are you located, and what hours do you tend to work? Located close to Hannover in Germany with variable work hours; might be in different time zones during the summer.
# Have you participated in an open-source project before?
#* http://fedoraproject.org/wiki/User:Sdz
#* http://wiki.sugarlabs.org/go/User:Sdz

=== About your project ===

# What is the name of your project? Improving Sugar on a Stick
# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
#* I'm going to work on improving Sugar on a Stick by finding ways for users, no matter whether they are students or deployments, to interact with developers. One of the biggest issue Sugar on a Stick has been facing in recent times is a lack of specific feedback. This is especially of importance, since Sugar on a Stick unites the Sugar learning environment with the Fedora linux distribution. Different, not-entirely-aligned release cycles have been a source for issues.
#* I plan to integrate features addressing this lack of feedback directly in the Sugar control panel by making heavy use of various upstream projects. This proposal mentions a number of possible projects, which are all related, since they all partially address a certain area of these issues and would all have to be integrated in the control panel. This integration requires knowledge of Python, as well as of the general Sugar on a Stick build process using kickstart files.
#* The project I will tackle first is integrating Fedora's [https://fedorahosted.org/smolt/ Smolt] initiative in Sugar. Since Sugar on a Stick relies on the underlying distribution, understanding what hardware our users are using is crucial, especially when it comes to understanding and eventually fixing issues. By integrating this functionality, the process of fixing hardware related issues will improve significantly, as users will not need to execute cryptic commands and upload logs anymore, but will rather be able to post a link to their profile.
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
#* I'll be evaluating options of different options on file system usage for Sugar on a Stick, if time permits.
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
#* May 24 - 30: initial gathering of information, diving into python
#* May 31 - June 6: creation of first mockups
#* June 7 - 13: evaluation of upstream code base
#* June 14 - 20: further python knowledge gathering
#* June 21 - 27: attempt to integrate smolt into the control panel
#* June 28 - July 4: coding
#* July 5 - 11: evaluation of smolt integration, possible cleanups
#*--- mid-terms ---
#* July 12 - 18: creation of mockups for abrt
#* July 19 - 25: evaluation of upstream code base
#* July 26 - August 1: further python knowledge gathering
#* August 2 - 8: attempt to integrate abrt into the control panel
#* August 9 - 15: evaluation, possible cleanups and look at packagekit
# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
#* I've been part of the Sugar Labs community for probably two years now. However, my story starts earlier, when I was in high school and looking for an open source operating system. Somehow, I found my way into the Fedora Project and met people like Greg DeKoenigsberg. Suddenly I was not only leading the Fedora Education SIG, but also working on OLPC's operating system for the second G1G1 program. Later on, I worked on the Fedora Sugar Spin, which ultimately merged with the early Sugar on a Stick efforts, making the latter what it is now. I've been experienced several release cycles of open source software engineering thus far and am especially looking forward to work on coding over the summer.

=== You and the community ===

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
## Sugar on a Stick is a project that "enables children to reclaim computers". It's a project that reaches even further than other approaches seen before, as it significantly lowers the entry barrier for people to get their hands on their own personalized Sugar Learning Experience. By making this experience even better -- which is what this project aims for -- the general improvements arrive at one of Sugar's main ways of distribution. However, Sugar on a Stick is not just a distribution, it's a way of deploying Sugar. Successful pilots are taking off right now in Berlin and Boston and these kids there won't be the only ones to get their hands on the resulting improvements. Instead, the improvements will be included in the next iteration of Sugar on a Stick, enabling them to interact directly with our developers, resulting in a better product.
## ''[comment needed -- commenter 1]''
## ''[comment needed -- commenter 2]''
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
#* I've been leading and coordinating technical support for a small XO deployment in a school here. While this might be an option, there are also other Sugar on a Stick related deployments currently going on in Berlin (Simon) and Boston (Mel) -- cooperating with these might be a good way of getting actual results from the field.
# What will you do if you get stuck on your project and your mentor isn't around?
#* Generally, I'd either try to get in touch with people I know from previous work who are aware of the issues I'd be facing or simply attempt to ask for more help in the appropriate channels, such as #sugar for directly development related topics and #fedora-olpc or #fedora-devel for questions related to the distribution itself. In case the latter one wouldn't be successful, I'd send emails off to the mailing lists, asking for help with a specific issue.
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
#* My blog is currently aggregated on both the Fedora Project's and Sugar Labs' planets, which is also where I'm going to post continuously about the state of my project and its progress. For more concrete questions, I'll be using the mailing list and IRC channels to interact directly with other developers.

=== Miscellaneous ===

# We want to make sure that you can set up a development environment before the summer starts: [http://sdz.fedorapeople.org/sugar-emulator.png click here]
# What is your t-shirt size? '''L'''
# Describe a great learning experience you had as a child.
#* The experience I'm going to describe didn't exactly in my childhood, but rather when I was growing up, actually not too long ago. It was when a good friend of mine gave me a Dr. Seuss book: ''"Oh, the Places you'll go"''! It's one of the most wonderful books I ever read -- and so is its message. It encourages you to keep going, no matter what happens, no matter how hard or lonely the world may seem. Because in the end, you'll succeed - ''"Yes! You will, indeed! (98 and 3/4 percent guaranteed.)"''. So you'll move mountains. And that's what I learned.
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
#* I apparently like Mirabelles and Cloudberries.

Summer of Code/2010/Improved Sugar on a Stick

2010-04-05T20:51:50Z

Sdz: /* You and the community */

'''This page is a draft. Its content is being moved around and this is just a giant braindump!'''

=== About you ===

# What is your name? Sebastian Dziallas
# What is your email address? sebastian@when.com
# What is your Sugar Labs wiki username? [[User:Sdz|sdz]]
# What is your IRC nickname? sdziallas
# What is your primary language? German; English and French work fine, though.
# Where are you located, and what hours do you tend to work? Located close to Hannover in Germany with variable work hours; might be in different time zones during the summer.
# Have you participated in an open-source project before?
#* http://fedoraproject.org/wiki/User:Sdz
#* http://wiki.sugarlabs.org/go/User:Sdz

=== About your project ===

# What is the name of your project? Improving Sugar on a Stick
# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
#* I'm going to work on improving Sugar on a Stick by finding ways for users, no matter whether they are students or deployments, to interact with developers. One of the biggest issue Sugar on a Stick has been facing in recent times is a lack of specific feedback. This is especially of importance, since Sugar on a Stick unites the Sugar learning environment with the Fedora linux distribution. Different, not-entirely-aligned release cycles have been a source for issues.
#* I plan to integrate features addressing this lack of feedback directly in the Sugar control panel by making heavy use of various upstream projects. This proposal mentions a number of possible projects, which are all related, since they all partially address a certain area of these issues and would all have to be integrated in the control panel. This integration requires knowledge of Python, as well as of the general Sugar on a Stick build process using kickstart files.
#* The project I will tackle first is integrating Fedora's [https://fedorahosted.org/smolt/ Smolt] initiative in Sugar. Since Sugar on a Stick relies on the underlying distribution, understanding what hardware our users are using is crucial, especially when it comes to understanding and eventually fixing issues. By integrating this functionality, the process of fixing hardware related issues will improve significantly, as users will not need to execute cryptic commands and upload logs anymore, but will rather be able to post a link to their profile.
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
#* I'll be evaluating options of different options on file system usage for Sugar on a Stick, if time permits.
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
#* May 24 - 30: initial gathering of information, diving into python
#* May 31 - June 6: creation of first mockups
#* June 7 - 13: evaluation of upstream code base
#* June 14 - 20: further python knowledge gathering
#* June 21 - 27: attempt to integrate smolt into the control panel
#* June 28 - July 4: coding
#* July 5 - 11: evaluation of smolt integration, possible cleanups
#*--- mid-terms ---
#* July 12 - 18: creation of mockups for abrt
#* July 19 - 25: evaluation of upstream code base
#* July 26 - August 1: further python knowledge gathering
#* August 2 - 8: attempt to integrate abrt into the control panel
#* August 9 - 15: evaluation, possible cleanups and look at packagekit
# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
#* I've been part of the Sugar Labs community for probably two years now. However, my story starts earlier, when I was in high school and looking for an open source operating system. Somehow, I found my way into the Fedora Project and met people like Greg DeKoenigsberg. Suddenly I was not only leading the Fedora Education SIG, but also working on OLPC's operating system for the second G1G1 program. Later on, I worked on the Fedora Sugar Spin, which ultimately merged with the early Sugar on a Stick efforts, making the latter what it is now. I've been experienced several release cycles of open source software engineering thus far and am especially looking forward to work on coding over the summer.

=== You and the community ===

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
## Sugar on a Stick is a project that "enables children to reclaim computers". It's a project that reaches even further than other approaches seen before, as it significantly lowers the entry barrier for people to get their hands on their own personalized Sugar Learning Experience. By making this experience even better -- which is what this project aims for -- the general improvements arrive at one of Sugar's main ways of distribution. However, Sugar on a Stick is not just a distribution, it's a way of deploying Sugar. Successful pilots are taking off right now in Berlin and Boston and these kids there won't be the only ones to get their hands on the resulting improvements. Instead, the improvements will be included in the next iteration of Sugar on a Stick, enabling them to interact directly with our developers, resulting in a better product.
## ''[comment needed]''
## ''[comment needed]''
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
#* I've been leading and coordinating technical support for a small XO deployment in a school here. While this might be an option, there are also other Sugar on a Stick related deployments currently going on in Berlin (Simon) and Boston (Mel) -- cooperating with these might be a good way of getting actual results from the field.
# What will you do if you get stuck on your project and your mentor isn't around?
#* Generally, I'd either try to get in touch with people I know from previous work who are aware of the issues I'd be facing or simply attempt to ask for more help in the appropriate channels, such as #sugar for directly development related topics and #fedora-olpc or #fedora-devel for questions related to the distribution itself. In case the latter one wouldn't be successful, I'd send emails off to the mailing lists, asking for help with a specific issue.
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
#* My blog is currently aggregated on both the Fedora Project's and Sugar Labs' planets, which is also where I'm going to post continuously about the state of my project and its progress. For more concrete questions, I'll be using the mailing list and IRC channels to interact directly with other developers.

=== Miscellaneous ===

# We want to make sure that you can set up a development environment before the summer starts: [http://sdz.fedorapeople.org/sugar-emulator.png click here]
# What is your t-shirt size? '''L'''
# Describe a great learning experience you had as a child.
#* The experience I'm going to describe didn't exactly in my childhood, but rather when I was growing up, actually not too long ago. It was when a good friend of mine gave me a Dr. Seuss book: ''"Oh, the Places you'll go"''! It's one of the most wonderful books I ever read -- and so is its message. It encourages you to keep going, no matter what happens, no matter how hard or lonely the world may seem. Because in the end, you'll succeed - ''"Yes! You will, indeed! (98 and 3/4 percent guaranteed.)"''. So you'll move mountains. And that's what I learned.
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
#* I apparently like Mirabelles and Cloudberries.

Summer of Code/2010/Improved Sugar on a Stick

2010-04-05T20:51:22Z

Sdz: /* About your project */

'''This page is a draft. Its content is being moved around and this is just a giant braindump!'''

=== About you ===

# What is your name? Sebastian Dziallas
# What is your email address? sebastian@when.com
# What is your Sugar Labs wiki username? [[User:Sdz|sdz]]
# What is your IRC nickname? sdziallas
# What is your primary language? German; English and French work fine, though.
# Where are you located, and what hours do you tend to work? Located close to Hannover in Germany with variable work hours; might be in different time zones during the summer.
# Have you participated in an open-source project before?
#* http://fedoraproject.org/wiki/User:Sdz
#* http://wiki.sugarlabs.org/go/User:Sdz

=== About your project ===

# What is the name of your project? Improving Sugar on a Stick
# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
#* I'm going to work on improving Sugar on a Stick by finding ways for users, no matter whether they are students or deployments, to interact with developers. One of the biggest issue Sugar on a Stick has been facing in recent times is a lack of specific feedback. This is especially of importance, since Sugar on a Stick unites the Sugar learning environment with the Fedora linux distribution. Different, not-entirely-aligned release cycles have been a source for issues.
#* I plan to integrate features addressing this lack of feedback directly in the Sugar control panel by making heavy use of various upstream projects. This proposal mentions a number of possible projects, which are all related, since they all partially address a certain area of these issues and would all have to be integrated in the control panel. This integration requires knowledge of Python, as well as of the general Sugar on a Stick build process using kickstart files.
#* The project I will tackle first is integrating Fedora's [https://fedorahosted.org/smolt/ Smolt] initiative in Sugar. Since Sugar on a Stick relies on the underlying distribution, understanding what hardware our users are using is crucial, especially when it comes to understanding and eventually fixing issues. By integrating this functionality, the process of fixing hardware related issues will improve significantly, as users will not need to execute cryptic commands and upload logs anymore, but will rather be able to post a link to their profile.
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
#* I'll be evaluating options of different options on file system usage for Sugar on a Stick, if time permits.
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
#* May 24 - 30: initial gathering of information, diving into python
#* May 31 - June 6: creation of first mockups
#* June 7 - 13: evaluation of upstream code base
#* June 14 - 20: further python knowledge gathering
#* June 21 - 27: attempt to integrate smolt into the control panel
#* June 28 - July 4: coding
#* July 5 - 11: evaluation of smolt integration, possible cleanups
#*--- mid-terms ---
#* July 12 - 18: creation of mockups for abrt
#* July 19 - 25: evaluation of upstream code base
#* July 26 - August 1: further python knowledge gathering
#* August 2 - 8: attempt to integrate abrt into the control panel
#* August 9 - 15: evaluation, possible cleanups and look at packagekit
# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
#* I've been part of the Sugar Labs community for probably two years now. However, my story starts earlier, when I was in high school and looking for an open source operating system. Somehow, I found my way into the Fedora Project and met people like Greg DeKoenigsberg. Suddenly I was not only leading the Fedora Education SIG, but also working on OLPC's operating system for the second G1G1 program. Later on, I worked on the Fedora Sugar Spin, which ultimately merged with the early Sugar on a Stick efforts, making the latter what it is now. I've been experienced several release cycles of open source software engineering thus far and am especially looking forward to work on coding over the summer.

=== You and the community ===

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
## Sugar on a Stick is a project that "enables children to reclaim computers". It's a project that reaches even further than other approaches seen before, as it significantly lowers the entry barrier for people to get their hands on their own personalized Sugar Learning Experience. By making this experience even better -- which is what this project aims for -- the general improvements arrive at one of Sugar's main ways of distribution. However, Sugar on a Stick is not just a distribution, it's a way of deploying Sugar. Successful pilots are taking off right now in Berlin and Boston and these kids there won't be the only ones to get their hands on the resulting improvements. Instead, the improvements will be included in the next iteration of Sugar on a Stick, enabling them to interact directly with our developers, resulting in a better product.
## [comment needed] -- Mel?
## [comment needed] -- Walter?
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
#* I've been leading and coordinating technical support for a small XO deployment in a school here. While this might be an option, there are also other Sugar on a Stick related deployments currently going on in Berlin (Simon) and Boston (Mel) -- cooperating with these might be a good way of getting actual results from the field.
# What will you do if you get stuck on your project and your mentor isn't around?
#* Generally, I'd either try to get in touch with people I know from previous work who are aware of the issues I'd be facing or simply attempt to ask for more help in the appropriate channels, such as #sugar for directly development related topics and #fedora-olpc or #fedora-devel for questions related to the distribution itself. In case the latter one wouldn't be successful, I'd send emails off to the mailing lists, asking for help with a specific issue.
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
#* My blog is currently aggregated on both the Fedora Project's and Sugar Labs' planets, which is also where I'm going to post continuously about the state of my project and its progress. For more concrete questions, I'll be using the mailing list and IRC channels to interact directly with other developers.

=== Miscellaneous ===

# We want to make sure that you can set up a development environment before the summer starts: [http://sdz.fedorapeople.org/sugar-emulator.png click here]
# What is your t-shirt size? '''L'''
# Describe a great learning experience you had as a child.
#* The experience I'm going to describe didn't exactly in my childhood, but rather when I was growing up, actually not too long ago. It was when a good friend of mine gave me a Dr. Seuss book: ''"Oh, the Places you'll go"''! It's one of the most wonderful books I ever read -- and so is its message. It encourages you to keep going, no matter what happens, no matter how hard or lonely the world may seem. Because in the end, you'll succeed - ''"Yes! You will, indeed! (98 and 3/4 percent guaranteed.)"''. So you'll move mountains. And that's what I learned.
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
#* I apparently like Mirabelles and Cloudberries.

Summer of Code/2010/Improved Sugar on a Stick

2010-04-02T23:05:53Z

Sdz: Undo revision 50694 by Goo (Talk)

'''This page is a draft. Its content is being moved around and this is just a giant braindump!'''

=== About you ===

# What is your name? Sebastian Dziallas
# What is your email address? sebastian@when.com
# What is your Sugar Labs wiki username? [[User:Sdz|sdz]]
# What is your IRC nickname? sdziallas
# What is your primary language? German; English and French work fine, though.
# Where are you located, and what hours do you tend to work? Located close to Hannover in Germany with variable work hours; might be in different time zones during the summer.
# Have you participated in an open-source project before?
#* http://fedoraproject.org/wiki/User:Sdz
#* http://wiki.sugarlabs.org/go/User:Sdz

=== About your project ===

# What is the name of your project? Improving Sugar on a Stick
# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
#* I'm going to work on improving Sugar on a Stick by finding ways for users, no matter whether they are students or deployments, to interact with developers. One of the biggest issue Sugar on a Stick has been facing in recent times is a lack of specific feedback. This is especially of importance, since Sugar on a Stick unites the Sugar learning environment with the Fedora linux distribution. Different, not-entirely-aligned release cycles have been a source for issues.
#* I plan to integrate features addressing this lack of feedback directly in the Sugar control panel by making heavy use of various upstream projects. This proposal mentions a number of possible projects, which are all related, since they all partially address a certain area of these issues and would all have to be integrated in the control panel. This integration requires knowledge of Python, as well as of the general Sugar on a Stick build process using kickstart files.
#* The project I will tackle first is integrating Fedora's [https://fedorahosted.org/smolt/ Smolt] initiative in Sugar. Since Sugar on a Stick relies on the underlying distribution, understanding what hardware our users are using is crucial, especially when it comes to understanding and eventually fixing issues. By integrating this functionality, the process of fixing hardware related issues will improve significantly, as users will not need to execute cryptic commands and upload logs anymore, but will rather be able to post a link to their profile.
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
#* May 24 - 30: initial gathering of information, diving into python
#* May 31 - June 6: creation of first mockups
#* June 7 - 13: evaluation of upstream code base
#* June 14 - 20: further python knowledge gathering
#* June 21 - 27: attempt to integrate smolt into the control panel
#* June 28 - July 4: coding
#* July 5 - 11: evaluation of smolt integration, possible cleanups
#*--- mid-terms ---
#* July 12 - 18: creation of mockups for abrt
#* July 19 - 25: evaluation of upstream code base
#* July 26 - August 1: further python knowledge gathering
#* August 2 - 8: attempt to integrate abrt into the control panel
#* August 9 - 15: evaluation, possible cleanups and look at packagekit
# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
#* I've been part of the Sugar Labs community for probably two years now. However, my story starts earlier, when I was in high school and looking for an open source operating system. Somehow, I found my way into the Fedora Project and met people like Greg DeKoenigsberg. Suddenly I was not only leading the Fedora Education SIG, but also working on OLPC's operating system for the second G1G1 program. Later on, I worked on the Fedora Sugar Spin, which ultimately merged with the early Sugar on a Stick efforts, making the latter what it is now. I've been experienced several release cycles of open source software engineering thus far and am especially looking forward to work on coding over the summer.

=== You and the community ===

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
## Sugar on a Stick is a project that "enables children to reclaim computers". It's a project that reaches even further than other approaches seen before, as it significantly lowers the entry barrier for people to get their hands on their own personalized Sugar Learning Experience. By making this experience even better -- which is what this project aims for -- the general improvements arrive at one of Sugar's main ways of distribution. However, Sugar on a Stick is not just a distribution, it's a way of deploying Sugar. Successful pilots are taking off right now in Berlin and Boston and these kids there won't be the only ones to get their hands on the resulting improvements. Instead, the improvements will be included in the next iteration of Sugar on a Stick, enabling them to interact directly with our developers, resulting in a better product.
## [comment needed] -- Mel?
## [comment needed] -- Walter?
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
#* I've been leading and coordinating technical support for a small XO deployment in a school here. While this might be an option, there are also other Sugar on a Stick related deployments currently going on in Berlin (Simon) and Boston (Mel) -- cooperating with these might be a good way of getting actual results from the field.
# What will you do if you get stuck on your project and your mentor isn't around?
#* Generally, I'd either try to get in touch with people I know from previous work who are aware of the issues I'd be facing or simply attempt to ask for more help in the appropriate channels, such as #sugar for directly development related topics and #fedora-olpc or #fedora-devel for questions related to the distribution itself. In case the latter one wouldn't be successful, I'd send emails off to the mailing lists, asking for help with a specific issue.
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
#* My blog is currently aggregated on both the Fedora Project's and Sugar Labs' planets, which is also where I'm going to post continuously about the state of my project and its progress. For more concrete questions, I'll be using the mailing list and IRC channels to interact directly with other developers.

=== Miscellaneous ===

# We want to make sure that you can set up a development environment before the summer starts: [http://sdz.fedorapeople.org/sugar-emulator.png click here]
# What is your t-shirt size? '''L'''
# Describe a great learning experience you had as a child.
#* The experience I'm going to describe didn't exactly in my childhood, but rather when I was growing up, actually not too long ago. It was when a good friend of mine gave me a Dr. Seuss book: ''"Oh, the Places you'll go"''! It's one of the most wonderful books I ever read -- and so is its message. It encourages you to keep going, no matter what happens, no matter how hard or lonely the world may seem. Because in the end, you'll succeed - ''"Yes! You will, indeed! (98 and 3/4 percent guaranteed.)"''. So you'll move mountains. And that's what I learned.
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
#* I apparently like Mirabelles and Cloudberries.

User talk:Sdz

2010-04-02T23:05:31Z

Sdz: Undo revision 50692 by Goo (Talk)

==livecd-iso-to-disk==
Isn't the script file that comes on the iso disc, /mnt/LiveOS/livecd-iso-to-disk adequate for the instructions, [[Sugar_on_a_Stick/Linux]] --[[User:FGrose|FGrose]] 14:59, 6 April 2009 (UTC)

:yes and no at the same time. for reproducing an usb image, it might be sufficiant. but since you run the creation normally on another machine, you need to get a copy of that script. finally, we want the people to use the same incarnation of that script, to be able to better identify issues. this is the version which we're going to recommend, so I guess we should link to it somehow in the wiki. I'll probably put it up on dl.sl.o later today. [[User:Sdz|Sdz]] 15:14, 6 April 2009 (UTC)

User:Sdz

2010-04-02T23:05:15Z

Sdz: Undo revision 50691 by Goo (Talk)

Sebastian Dziallas is a student, mainly working on the [[Sugar_on_a_Stick| Sugar on a Stick]] project right now. He's also working on Fedora, where he has founded the Education SIG and has attended FOSDEM 2009 in Brussels and SugarCamp 2009 in Berlin. You can reach him on IRC (nick: ''sdziallas''), while his blog is available [http://sdziallas.blogspot.com/ here]. He's running for SLOBs in the upcoming election (for which he's working with Luke Faraone in the Membership Committee) to ensure a good connection and representation of SoaS.

Sugar on a Stick

2010-04-02T23:04:05Z

Sdz: Undo revision 50690 by Goo (Talk)

<noinclude>{{ Translations | [[Sugar_on_a_Stick|english]] | [[Sugar_on_a_Stick/lang-es|español]] | [[Sugar_on_a_Stick/lang-fr|français]]}}{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}
[[Category:Project]]
[[Category:Live USB]]</noinclude>

{{/Pancake page}}

{{TOCright}}
== Introduction ==
Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can starts any computer with the student's personalized Sugar environment. We would like to see [[Sugar]]'s presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. Sugar on a Stick starts up ("boots") the host computer directly, without touching the hard disk; however, it may be necessary to adjust the computer's settings to look for a USB device before the hard disk.

{| class="wikitable"
|[[Image:Soas-1.png|180px|link=0.86/Notes]]
|
'''What exactly is on the Stick?''': The Sugar Learning Platform and Sugar Activities for children over Fedora GNU/Linux. Taking advantage of [[wikipedia:Live USB|Live USB]] technology, it's possible to store everything you need to run Sugar on a single, [[wikipedia:USB flash drive|USB flash memory stick]]. Compressed file systems are used to save space, and persistent overlay files are used to save changes to the system and the learner's work. See our [[Sugar on a Stick/Resources| '''resources page''']] to learn about different component configurations we are designing to offer the option to use [[wikipedia:Virtual machine|virtual machines]] on existing computers to host Sugar from a portable Stick and save the [[Human Interface Guidelines/The Laptop Experience/The Journal|Sugar Journal]] (the learner's work) and personal settings on the Stick for use at another workstation - for example, a computer in the home.
|}

== Project Principles ==
* ''Portability'' - One's Sugar environment, saved Activities, and Journal are available wherever one has access to suitable computing devices, at home, school, library, clubhouse in order to permit resumable, extended, and deep exploration of concepts and phenomena.
* ''Customizability'' - Deployments, as well as users, can build their own SoaS easily.
* ''Deployability'' - SoaS is easy to deploy, both for individual sticks and for multiple-instances deployed in computer labs.

'''Would you like to help?''' ...this is entirely a volunteer-run effort. Please [[/Getting Involved| get involved]]!

== Getting Sugar on a Stick ==
Follow the instructions for our new [[Sugar on a Stick/Blueberry| v2 Blueberry release]]. Our previous stable version is the [[Sugar on a Stick/Strawberry| v1 Strawberry release]].

Developers and testers can help us debug Beta test builds. See [[Sugar on a Stick/Beta]].

Please let us know how it goes. You can always [[Sugar on a Stick/Contacts| get in touch]] with us!

== E-Books ==

For licensing reasons, Sugar on a Stick does not contain e-books with NC (noncommercial) licensing. To get teachers and parents started with finding, downloading, and reading e-books with Sugar, see our [[Sugar on a Stick/E-Books| E-Books page]].

== More information ==

For general questions, please see the [[/FAQ|Frequently Asked Questions (FAQ) page for Sugar on a Stick]]. You can learn more from [http://www.xconomy.com/boston/2009/02/05/sugar-beyond-the-xo-laptop-walter-bender-on-olpc-sucrose-084-and-sugar-on-a-stick/ Walter Bender's interview with Xconomy], [http://www.olpcnews.com/software/sugar/sugar_on_a_stick_netbooks.html Wayan Vota's video] and [http://www.flickr.com/photos/curiouslee/sets/72157613785006745/ Mike Lee's pictures].

== Problems? ==

Please file bug reports in [http://bugs.sugarlabs.org The Sugar on a Stick bug tracker].
* Here are [[Talk:Sugar_on_a_Stick/Getting_Involved|some instructions for using the bug tracker]].
* This link will [https://bugs.sugarlabs.org/query?component=SoaS&status=accepted&status=assigned&status=new&status=reopened query the database for all tickets designated with the SoaS component/tag].
* You must [https://bugs.sugarlabs.org/register register an account] to enter new bugs.
* This link will take you to a [http://bugs.sugarlabs.org/newticket?component=SoaS new bug/ticket form for SoaS] (once you are logged in).

Sugar developers can often be found in IRC at irc.freenode.net, channel #sugar

Or, send e-mail to feedback AT sugarlabs DOT org.

See the '''Get Help!''' section of the [[Sugar_on_a_Stick/Blueberry|Blueberry release notes page]] for further information.

== Related work ==

See these other [[:Category:Live USB|portable Sugar distributions]] that share some of these goals.

Summer of Code/2010/Improved Sugar on a Stick

2010-04-02T23:03:41Z

Sdz: Undo revision 50689 by Goo (Talk)

'''This page is a draft. Its content is being moved around and this is just a giant braindump!'''

=== About you ===

# What is your name? Sebastian Dziallas
# What is your email address? sebastian@when.com
# What is your Sugar Labs wiki username? [[User:Sdz|sdz]]
# What is your IRC nickname? sdziallas
# What is your primary language? German; English and French work fine, though.
# Where are you located, and what hours do you tend to work? Located close to Hannover in Germany with variable work hours; might be in different time zones during the summer.
# Have you participated in an open-source project before?
#* http://fedoraproject.org/wiki/User:Sdz
#* http://wiki.sugarlabs.org/go/User:Sdz

=== About your project ===

# What is the name of your project? Improving Sugar on a Stick
# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
#* I'm going to work on improving Sugar on a Stick by finding ways for users, no matter whether they are students or deployments, to interact with developers. One of the biggest issue Sugar on a Stick has been facing in recent times is a lack of specific feedback. This is especially of importance, since Sugar on a Stick unites the Sugar learning environment with the Fedora linux distribution. Different, not-entirely-aligned release cycles have been a source for issues.
#* I plan to integrate features addressing this lack of feedback directly in the Sugar control panel by making heavy use of various upstream projects. This proposal mentions a number of possible projects, which are all related, since they all partially address a certain area of these issues and would all have to be integrated in the control panel. This integration requires knowledge of Python, as well as of the general Sugar on a Stick build process using kickstart files.
#* The project I will tackle first is integrating Fedora's [https://fedorahosted.org/smolt/ Smolt] initiative in Sugar. Since Sugar on a Stick relies on the underlying distribution, understanding what hardware our users are using is crucial, especially when it comes to understanding and eventually fixing issues. By integrating this functionality, the process of fixing hardware related issues will improve significantly, as users will not need to execute cryptic commands and upload logs anymore, but will rather be able to post a link to their profile.
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
#* May 24 - 30: initial gathering of information, diving into python
#* May 31 - June 6: creation of first mockups
#* June 7 - 13: evaluation of upstream code base
#* June 14 - 20: further python knowledge gathering
#* June 21 - 27: attempt to integrate smolt into the control panel
#* June 28 - July 4: coding
#* July 5 - 11: evaluation of smolt integration, possible cleanups
#*--- mid-terms ---
#* July 12 - 18: creation of mockups for abrt
#* July 19 - 25: evaluation of upstream code base
#* July 26 - August 1: further python knowledge gathering
#* August 2 - 8: attempt to integrate abrt into the control panel
#* August 9 - 15: evaluation, possible cleanups and look at packagekit
# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
#* I've been part of the Sugar Labs community for probably two years now. However, my story starts earlier, when I was in high school and looking for an open source operating system. Somehow, I found my way into the Fedora Project and met people like Greg DeKoenigsberg. Suddenly I was not only leading the Fedora Education SIG, but also working on OLPC's operating system for the second G1G1 program. Later on, I worked on the Fedora Sugar Spin, which ultimately merged with the early Sugar on a Stick efforts, making the latter what it is now. I've been experienced several release cycles of open source software engineering thus far and am especially looking forward to work on coding over the summer.

=== You and the community ===

# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
## Sugar on a Stick is a project that "enables children to reclaim computers". It's a project that reaches even further than other approaches seen before, as it significantly lowers the entry barrier for people to get their hands on their own personalized Sugar Learning Experience. By making this experience even better -- which is what this project aims for -- the general improvements arrive at one of Sugar's main ways of distribution. However, Sugar on a Stick is not just a distribution, it's a way of deploying Sugar. Successful pilots are taking off right now in Berlin and Boston and these kids there won't be the only ones to get their hands on the resulting improvements. Instead, the improvements will be included in the next iteration of Sugar on a Stick, enabling them to interact directly with our developers, resulting in a better product.
## [comment needed] -- Mel?
## [comment needed] -- Walter?
# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
#* I've been leading and coordinating technical support for a small XO deployment in a school here. While this might be an option, there are also other Sugar on a Stick related deployments currently going on in Berlin (Simon) and Boston (Mel) -- cooperating with these might be a good way of getting actual results from the field.
# What will you do if you get stuck on your project and your mentor isn't around?
#* Generally, I'd either try to get in touch with people I know from previous work who are aware of the issues I'd be facing or simply attempt to ask for more help in the appropriate channels, such as #sugar for directly development related topics and #fedora-olpc or #fedora-devel for questions related to the distribution itself. In case the latter one wouldn't be successful, I'd send emails off to the mailing lists, asking for help with a specific issue.
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
#* My blog is currently aggregated on both the Fedora Project's and Sugar Labs' planets, which is also where I'm going to post continuously about the state of my project and its progress. For more concrete questions, I'll be using the mailing list and IRC channels to interact directly with other developers.

=== Miscellaneous ===

# We want to make sure that you can set up a development environment before the summer starts: [http://sdz.fedorapeople.org/sugar-emulator.png click here]
# What is your t-shirt size? '''L'''
# Describe a great learning experience you had as a child.
#* The experience I'm going to describe didn't exactly in my childhood, but rather when I was growing up, actually not too long ago. It was when a good friend of mine gave me a Dr. Seuss book: ''"Oh, the Places you'll go"''! It's one of the most wonderful books I ever read -- and so is its message. It encourages you to keep going, no matter what happens, no matter how hard or lonely the world may seem. Because in the end, you'll succeed - ''"Yes! You will, indeed! (98 and 3/4 percent guaranteed.)"''. So you'll move mountains. And that's what I learned.
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
#* I apparently like Mirabelles and Cloudberries.

Sugar on a Stick

2010-04-02T22:59:50Z

Sdz: Undo revision 50682 by Goo (Talk)

SoaS Blueberry Notes

2009-11-27T14:54:32Z

Sdz: add video link

__NOTOC__

{|
|-
| style="border: 0px;" | [[Image:Soas-blueberry-logo.png|left]] [[File:Soas-blueberry-notes-text.png]] || style="border: 0px;" | [[Image:Logo_white_04.png|350px|right]]
|}

 

'''Sugar on a Stick v2 Blueberry''' contains a number of new features that improve the overall user and learning experience. Here is an overview of the most notable ones:

== Sugar 0.86 ==

[[Image:0.86_Browse_new_toolbar.png|left|200px]]

Sugar on a Stick v2 Blueberry ships the latest '''Sugar''' release, 0.86.3. It features:

* a redesigned toolbar;
* support for tabbed browsing (Browse);
* epub file support for ebooks (Read);
* and an easy way to update to the latest activities (Control Panel).

 

== ZYX-Liveinstaller ==

[[Image:zyx-liveinstaller.png|right|200px]]

A frequent request we received concerned a means of installing Sugar to a hard disk.
We teamed up with the '''zyx-liveinstaller''' developer in order to provide:

* a seamless way of installing your personalized environment onto your computer's hard disk
* that saves any changes that you made to your Sugar on a Stick system
* without even requiring a reboot!

 

== E-Books ==

[[Image:read-alice.png|left|200px]]

Sugar on a Stick v2 Blueberry features a number of well-selected e-books in the increasingly popular .epub file format. Historical classicals and interesting literature for young readers have found their way onto this release.
Thousands of additional e-books can even be easily accessed through the included '''Get Internet Archive Books''' Activity.
A demonstration of Sugar's sharing features with e-books is available here: http://people.sugarlabs.org/sayamindu/shared_read.ogv

 

== Activities ==

[[Image:social-calc-activity.png|right|200px]]

Sugar on a Stick v2 Blueberry also includes many new Sugar Activities as well as updates to old favorites like '''Physics''' and '''TurtleArt'''. Activities shipping for the first time on Sugar on a Stick v2 Blueberry include '''SocialCalc''', a spreadsheet activity that allows users to do complex mathematical calculations, and '''TamTam''' activity suite, which takes the learner on a journey through sound and music, beginning with a simple musical toy and progressing up to a sophisticated sound synthesizer.

 

== Based On Fedora ==

[[Image:Fedora_remix_logo.png|left]]

Sugar on a Stick v2 Blueberry is based on the latest version of the Fedora operating system.

 

== For More Information ==

In case you encounter issues, please report them here 
https://launchpad.net/soas

Do not hesitate to e-mail us with any feedback at 
[mailto:feedback@sugarlabs.org feedback@sugarlabs.org]

For more information, please visit 
[http://www.sugarlabs.org www.sugarlabs.org]

== About This Document ==

A PDF layout of this file is available at http://people.sugarlabs.org/sdz/soas-v2-notes.pdf with SVG source at http://people.sugarlabs.org/sdz/soas-v2-notes.svg. Note that the wiki page version is likely to be more up-to-date.

SoaS Blueberry Notes

2009-11-27T14:28:49Z

Sdz: some content updates & screenshots

__NOTOC__

{|
|-
| style="border: 0px;" | [[Image:Soas-blueberry-logo.png|left]] [[File:Soas-blueberry-notes-text.png]] || style="border: 0px;" | [[Image:Logo_white_04.png|350px|right]]
|}

 

'''Sugar on a Stick v2 Blueberry''' contains a number of new features that improve the overall user and learning experience. Here is an overview of the most notable ones:

== Sugar 0.86 ==

[[Image:0.86_Browse_new_toolbar.png|left|200px]]

Sugar on a Stick v2 Blueberry ships the latest '''Sugar''' release, 0.86.3. It features:

* a redesigned toolbar;
* support for tabbed browsing (Browse);
* epub file support for ebooks (Read);
* and an easy way to update to the latest activities (Control Panel).

 

== ZYX-Liveinstaller ==

[[Image:zyx-liveinstaller.png|right|200px]]

A frequent request we received concerned a means of installing Sugar to a hard disk.
We teamed up with the '''zyx-liveinstaller''' developer in order to provide:

* a seamless way of installing your personalized environment onto your computer's hard disk
* that saves any changes that you made to your Sugar on a Stick system
* without even requiring a reboot!

 

== E-Books ==

[[Image:read-alice.png|left|200px]]

Sugar on a Stick v2 Blueberry features a number of well-selected e-books in the increasingly popular .epub file format. Historical classicals and interesting literature for young readers have found their way onto this release.
Thousands of additional e-books can even be easily accessed through the included '''Get Internet Archive Books''' Activity.

 

== Activities ==

[[Image:social-calc-activity.png|right|200px]]

Sugar on a Stick v2 Blueberry also includes many new Sugar Activities as well as updates to old favorites like '''Physics''' and '''TurtleArt'''. Activities shipping for the first time on Sugar on a Stick v2 Blueberry include '''SocialCalc''', a spreadsheet activity that allows users to do complex mathematical calculations, and '''TamTam''' activity suite, which takes the learner on a journey through sound and music, beginning with a simple musical toy and progressing up to a sophisticated sound synthesizer.

 

== Based On Fedora ==

[[Image:Fedora_remix_logo.png|left]]

Sugar on a Stick v2 Blueberry is based on the latest version of the Fedora operating system.

 

== For More Information ==

In case you encounter issues, please report them here 
https://launchpad.net/soas

Do not hesitate to e-mail us with any feedback at 
[mailto:feedback@sugarlabs.org feedback@sugarlabs.org]

For more information, please visit 
[http://www.sugarlabs.org www.sugarlabs.org]

== About This Document ==

A PDF layout of this file is available at http://people.sugarlabs.org/sdz/soas-v2-notes.pdf with SVG source at http://people.sugarlabs.org/sdz/soas-v2-notes.svg. Note that the wiki page version is likely to be more up-to-date.