Difference between revisions of "Sugar on a Stick"

Revision as of 13:14, 26 November 2018

Project Home · Join · Contacts · Resources · FAQ · Roadmap · To Do · Meetings

What is Sugar on a Stick?

	Sugar on a Stick is a Fedora^® Spin operating system featuring the award-winning Sugar Learning Platform. Sugar on a Stick will run on any 64-bit Notebook, Laptop, or Desktop computer, with a minimum of 1GB RAM, that can run Linux, Windows or macOS, using a USB thumbdrive or stick, as a Live USB, a 32-bit computer with the TOAST version of Sugar (Trisquel on a Sugar Toast). See Trisquel On A Sugar Toast. a Raspberry Pi 2 or 3, using a microSD card, or; any computer as a virtual machine. You can use Sugar on a Stick to demo Sugar almost anywhere without disturbing the contents of the computer you use, and if people like what they see, you can install Sugar on a Stick to their hard drives or other sticks from the demo stick.
	x86_64 (64-bit)		armhfp Raspberry Pi 2 or 3, see How to install.
	How to quickly demonstrate: (English), (en español)

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

What's new in Sugar on a Stick?

Sugar version 0.112.0
More information about this version at 0.112/Notes.
The current release comes with Fedora 29, though Sugar on a Stick does not package all the software of other desktops.
See : Fedora 29 Release Notes.

Known bugs

Journal obscures Home screen on startup sugar#769 sugar-toolkit-gtk3#368 Fedora downstream bug #1519042
Fix by pressing the F1 (Neighborhood) key to connect to a wireless access point, if present.

Then press the F3 (Home) key.
Network control panel fails to open #4990 (Fedora downstream bug)
Try this repair from a Terminal window:
sudo sed -i s/NMClient/NM/ usr/share/sugar/extensions/cpsection/network/model.py

An update to the Sugar components, sugar-0.112-5.fc29, is available.
sudo dnf upgrade sugar*
Reboot returns to initial start Name screen sequence #4991
No neighbors in Neighborhood view with jabber.sugarlabs.org #4992
< additional bugs pending input from users >
See also Common Fedora 29 bugs

Want to use Sugar on a Stick?

After you've tried out Sugar on a Stick, we hope you'll come back here and join our community of contributors to help us make the next release even better.

Want to contribute to Sugar on a Stick?

You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.

New contributors start here!

Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the Joining Sugar on a Stick page for instructions on how to get started.

What can you do?

There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, Sugar Labs and the Fedora Project.

Get Activities on the Stick

We're always looking for help with all aspects of the Sugar on a Stick release process. Here are a few things you can do:

Test Sugar on a Stick and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, file a ticket! No technical experience required.
Help make it easier for others to test Sugar on a Stick by writing test cases. If you've run a test case, you can write a test case.
Fix a bug or add a feature to an existing Activity, to sugar-core itself, or to Sugar on a Stick. See How to fix an Activity bug and How to fix a sugar-core bug to get started. Basic Python programming skills - or the desire to learn - are all that's needed.
Package Sugar Activities for Fedora. If you're a Fedora Packager or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.
Review Activities for inclusion in the build - check submitted Activities against our Sugar on a Stick/Activity Criteria and help us choose what gets included in the next release! No prior experience needed.
Have an idea for a technical feature that isn't an Activity? Check out our feature process.

Get Sticks into Schools

Deployments all over the world need many different types of help as they work through the Sugar on a Stick deployment process - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.

Some things you can do to help:

"It's a wiki: Edit away!" is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible, just go for it!
We produce official documentation such as the Creation Kit or the Customization Guide. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the Documentation SOP.
Unofficial documentation for unsupported workarounds for installation and customization need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.
Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for Sugar Labs and One Laptop Per Child and we'll get you connected with some teachers on the ground.
We're looking for some people to help us assemble tools for our support team to use. Email the Sugar on a Stick mailing list if you're interested.

Get Contributors

Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is everyone's responsibility to help build our community, one person at a time.

Some things you can do:

Edit this page and Joining Sugar on a Stick. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!
Help us fill in our remaining task-starter pages: Sugar on a Stick release process, How to fix an Activity bug, How to fix a sugar-core bug, and Sugar on a Stick deployment process/
Point out starter tasks on OpenHatch - fill in questions and ideas for beginner jobs, and point newcomers towards them.
Watch for introductions on the mailing list, and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).
Hang out with us on IRC: #sugar. This is where the IRC Activity starts off. Help new joiners past initial questions and provide instant help!

What's happening?

Sugar on a Stick/Beta

Sugar Virtual Box Appliances

Import into VirtualBox

Contributor stories

To find out what other contributors are doing, check out Planet Sugar Labs, where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also add your own blog to the Planet.

Meetings

Communication through the Sugar on a Stick mailing list has replaced regular meetings.

We once had weekly meetings on IRC - see Sugar on a Stick meetings for more information, including logs from past meetings.

Related work

While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)

For deployments lacking easy Internet access, one can turn a computer into a Sugar on a Stick Creation Station. The Sugar Creation Kit includes the materials you need to create Live USB sticks sticks and to install additional Activities, along with documentation and previous versions of Sugar on a Stick.
Older portable Sugar distributions based on other Linux distributions .
The undiscoverable is an unofficial FAQ for tips, tricks, and solutions to common problems that may otherwise be tricky to find. These are being considered for inclusion in the official SoaS documentation.

Previous versions and other subpages index

Earlier versions of Sugar on a Stick and other project pages can be reviewed at these pages:

@@ Line 7: / Line 7: @@
 ==What is Sugar on a Stick?==
 {{:Sugar on a Stick/Downloads}}
-====[[File:Soas-avacado.png|200px|link=http://wiki.sugarlabs.org/go/Fedora_19#Sugar_on_a_Stick_v9_Avocado]] Sugar on a Stick v9 Avacodo (Beta)====
+=== What's new in Sugar on a Stick? ===
-:Click ^ Link
+* '''Sugar version 0.112.0'''
-*Beta New 5/26/2013
+*: More information about this version at [[0.112/Notes]].
-:http://fedoraproject.org/get-prerelease
+* The current release comes with [[Fedora 29]], though Sugar on a Stick does not package all the software of other desktops.
+*: See : [https://docs.fedoraproject.org/en-US/fedora/f29/release-notes/ Fedora 29 Release Notes].
+==== Known bugs ====
+* Journal obscures Home screen on startup {{Issue|sugar|769}} {{Issue|sugar-toolkit-gtk3|368}} [https://bugzilla.redhat.com/show_bug.cgi?id=1519042 Fedora downstream bug #1519042]
+*: Fix by pressing the F1 (Neighborhood) key to connect to a wireless access point, if present.
+*: Then press the F3 (Home) key.
+* Network control panel fails to open {{Bug|4990}} ([https://bugzilla.redhat.com/show_bug.cgi?id=1642828 Fedora downstream bug])
+*: Try this repair from a Terminal window:
+*:: {{Code|sudo sed -i s/NMClient/NM/ usr/share/sugar/extensions/cpsection/network/model.py}}
+*: An update to the Sugar components, sugar-0.112-5.fc29, is available.
+*:: {{Code|sudo dnf upgrade sugar*}}
+* Reboot returns to initial start Name screen sequence {{Bug|4991}}
+* No neighbors in Neighborhood view with jabber.sugarlabs.org {{Bug|4992}}
+* < additional bugs pending input from users >
+* See also [[fedora:Common_F29_bugs|Common Fedora 29 bugs]]
 === Want to use Sugar on a Stick? ===
 {|
 |-
-| style="border: 0; border-width: 0; width: 350px;" | [[File:Cici-maze.jpg |300px|left|link=http://download.fedoraproject.org/pub/alt/releases/17/Spins/i686/Fedora-17-i686-Live-SoaS.iso]]
+| style="border: 0; border-width: 0; width: 350px;" | [[File:Cici-maze.jpg |300px|left|link=Sugar_on_a_Stick/Downloads]]
 |After you've tried out Sugar on a Stick, we hope you'll come back here and join our community of contributors to help us make the next release even better.
@@ Line 30: / Line 45: @@
 == New contributors start here! ==
-Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started. You may also want to check out the [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Sugar on a Stick project page] on [http://openhatch.org OpenHatch], or attend one of our [[Sugar on a Stick meetings]].
+Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started.
 == What can you do? ==
@@ Line 48: / Line 63: @@
 * [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''
 * [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''
-* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[Sugar on a Stick/Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed - we do reviews during our [[Sugar on a Stick meetings|weekly meetings]] and will teach you how.''
+* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[Sugar on a Stick/Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed.''
 * Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].
@@ Line 91: / Line 106: @@
 == What's happening? ==
+===[[Sugar on a Stick/Beta]]===
-====[[File:Soas-avacado.svg|200px|link=http://wiki.sugarlabs.org/go/Fedora_19]] Sugar on a Stick v9 Avocado (Beta)====
-:http://wiki.sugarlabs.org/go/Fedora_19
-*This version of f19 Beta-RC4 is a go for Beta release 05/23/213 released 05/26/2013
-:A Sugar on a stick version for f19 that boots and installs from a live cd to USB/HD/VirtualBox
- sugar 0.98.7
- fedora-release f19
-*Prerelease:
-:http://fedoraproject.org/get-prerelease
-*BetaRC4:
-:i686: https://dl.fedoraproject.org/pub/alt/stage/19-Beta-RC4/Live/i386/Fedora-Live-SoaS-i686-19-Beta-1.iso
-:x86_64: https://dl.fedoraproject.org/pub/alt/stage/19-Beta-RC4/Live/x86_64/Fedora-Live-SoaS-x86_64-19-Beta-1.iso
-*Beta from a mirror (May be Faster)
-::http://mirrors.kernel.org/fedora/releases/test/19-Beta/Live/i386/Fedora-Live-SoaS-i686-19-Beta-1.iso
-::http://mirrors.kernel.org/fedora/releases/test/19-Beta/Live/x86_64/Fedora-Live-SoaS-x86_64-19-Beta-1.iso
-====[[File:Logo_SoaS_01.png|200px|link=Fedora_18#Sugar_on_a_Stick_v8_.CA.BB.C5.8Chelo_.CA.BBai|'''Sugar on a Stick v8 ʻŌhelo ʻai''']]'''Sugar on a Stick v8 ʻŌhelo ʻai''' ====
-ʻŌhelo ʻai is the name of a native [[wikipedia:Vaccinium_reticulatum|Hawaiian berry]].
-*Current version of Sugar on a Stick
-:released 01/15/2013
-* When does this page get changed to Fedora 18? satellit 01/22/2013
-*: Please identify bugs and instabilities at [[Sugar on a Stick/ʻŌhelo ʻai#Known bugs]].  Peter usually prepares an announcement.
 ===[[Sugar_on_a_Stick/Virtual_machines| Sugar Virtual Box Appliances]]===
-*Import into VirtualBox
+* Import into VirtualBox
-===[[Tutorials/Installation/Install_using_Anaconda_f18_RC1_DVDx86_64|Tutorial: How to use new anaconda installer in f18]]===
 === Contributor stories ===
@@ Line 133: / Line 124: @@
 While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)
-* For deployments lacking easy Internet access, one can turn a computer into a '''Sugar on a Stick Creation Station'''. The [[Sugar Creation Kit]] is a downloadable DVD which includes the materials you need to create Pineapple sticks and to install additional Activities, along with documentation and previous versions of Sugar on a Stick.
+* For deployments lacking easy Internet access, one can turn a computer into a '''Sugar on a Stick Creation Station'''. The [[Sugar Creation Kit]] includes the materials you need to create Live USB sticks sticks and to install additional Activities, along with documentation and previous versions of Sugar on a Stick.
 * Older [[:Category:Live USB|portable Sugar distributions]] based on other Linux distributions .
 * [[The undiscoverable]] is an unofficial FAQ for tips, tricks, and solutions to common problems that may otherwise be tricky to find. These are being considered for inclusion in the official SoaS documentation.