Sugar Labs - User contributions [en]

News

2016-03-25T21:14:31Z

Patrol: undo

<noinclude>* The latest community news flashes are published on the [[Main Page#Community news|main page]].

* See our community news weekly '''[[Sugar Labs/Current Events|Sugar Digest]]''' and the '''[[Archive/Current Events| Sugar Digest archive]]'''.
== Community News ==
</noinclude>
[[File:SugaronastickAvocado-320px.png|320px|right|link=Sugar on a Stick|Click Me!]]
* The application period for Google Summer of Code 2016 has ended. We have 62 project proposals, which we will vet over the next few weeks. Thanks to the applicants and community mentors.
* Congratulations to our two Google Code-in grand-prize winners: Piotr Antosz (from Poland) and Ezequiel Pereira Lopez (from Uruguay).
* The Fedora 23 release of [[Sugar on a Stick]] is available with [[0.106/Notes|Sugar 0.106]]. This release of Sugar (v 0.106) is dedicated to the memory of Marco Gritti Presenti. Marco was a member of the original Sugar team and the lead Red Hat engineer on the project over its first three years of development. Soft-spoken but determined, Marco was a founding member of Sugar Labs and one of the original members of the Sugar Labs oversight board. Beyond the code he contributed to the project—he was a gifted software engineer; Marco shared with us his vision that Sugar ultimately belongs to its users. It is the clarity of this vision that is still reflected in the Sugar code-base and the spirit of the Sugar Labs community.
* [[0.106/Notes|Sugar 106]] has been released!! See [https://www.youtube.com/watch?v=PXFaXAGIw04&feature=youtu.be] for a quick video summary of the new features.
* Are you a developer who is new to Sugar? Consider helping us with our [http://developer.sugarlabs.org/web-architecture.md.html HTML5/Javascript framework].
* Celebrate [http://turtleartday.org Turtle Art Day].
* Donate your used USB sticks at [http://recycleusb.com Recycle USB.com]; they'll be turned into Sugar sticks and distributed to schools.
* Watch some [http://www.overstream.net/view.php?oid=i2ueryser0rz videos] of children in Uruguay explaining how they use Sugar and [http://olpc-ceibal.blogspot.com/2009/01/anecdotes-of-plan-ceibal-in-durazno.html stories from the field].<BR CLEAR=RIGHT>
<noinclude>


== Archival entries ==
* We are participating in [https://developers.google.com/open-source/gci/ Google Code In 2015]. If you have projects you'd like to suggest or would be willing to mentor, please contact walter --AT-- sugarlabs.org.
* Google Summer of Code 2015 is wrapping up. The students have been writing their final blog reports, submitting last-minute patches, and uploading their code to Google. I want to take this opportunity to thank all of our students and their mentors for all their hard work this summer. (Also, thanks once more to Google for supporting this program.) Great strides along many fronts were made. Specifically, Michaël Ohayon worked on Web versions of some core activities for the Sugarizer project: Calculate, Paint (with collaboration, Record, and Memorize. He also submitted patches to Turtle Blocks to make it compatible with Sugarizer. Mentor: Lionel Laske) Yash Khandelwal worked on Music Blocks AKA Mouse Music. This is a powerful, playful model for music in a block language. (Mentors: Devin Ulibarri and Marnen Laibow-Koser) Ishan Sharma revisited the Turtle 3D concept, rewriting it in Javascript. (Mentor: Walter) Amit Kumar Jha worked on extensions to Turtle programming this summer. He added argument passing and return values to procedures, passing arguments to and returning values from Turtle programs so that Turtle Blocks can be used for in-line programming by all Javascript activities, and he developed a unit=test framework for Turtle Blocks JS that can be extended to all of our Javascript activities. (Mentor: Walter) Richa Sehgal worked on a framework to support off-line Web programming, an interactive Javascript shell. She's submitted patches to the upstream Browse activity. (Mentor: Tony Anderson) Vibhor Sehgal and Utkarsh Dhawan, although not officially GSoC students, worked with Tony and Richa on a parallel project, Web Confusion, a series of programming challenges in the spirit of Turtle Confusion to encourage students. (Mentor: Tony Anderson) Abhinav Anurag made some progress on a Web collaboration framework for our Javascript activities. (Mentors: Martin Abente and Lionel Laske)
* Our Google Summer of Code interns are: Abhinav, Ishan, Yash, Michaël, Richa, and Amit. Looking forward to a fun and productive summer.
* [[0.104/Notes|Sugar 104]] has been released. Many thanks to our release manager, Martin Abente. Note that well over 50% of the patches to Sugar Activities came from youths in the Sugar community and just under 50% of the patches to Sugar core libraries came from youths in the Sugar community.
* Congratulations to Ignacio Rodríguez and Sam Parkinson, the grand-prize winners from Sugar Labs in [http://google-opensource.blogspot.com/2015/02/google-code-in-2014-welcome-to-winners.html Google Code-in]. Our finalists are Cristian Garcia, Daksh Shah, and Jae Eun (Jasmine) Park.
* We've been accepted into Google Summer of Code 2015. Potential students and mentors, please go to our [[Summer_of_Code/2015|GSoC 2015]] page in the wiki.
* [[Google Code In 2014]] has begun. Sugar Labs is participating. We hope you do as well.
* Trisquel 7 Sugar ([[Trisquel On A Sugar Toast]]) has been released with Sugar 0.102.
* We are excited to announce that Sugar 0.102.0 (stable) is released. See [[0.102/Notes]] for details. And please help us with [[0.102/Testing|Testing]].
* We just received hundreds more [[Sugar on a Stick]] USB keys from the [http://recycleusb.com Recycle USB] program sponsored by [http://www.nexcopy.com NexCopy].
* Sugar on a Stick 10 is out with the just released Fedora 20 and [[0.100/Notes|Sugar 0.100]]. Please [[Sugar_on_a_Stick/10#Contributing_to_Sugar_on_a_Stick|participate]].
* Sugar Labs has been accepted into [[Summer of Code/2014|Google Summer of Code for 2014]]!! Potential students should start working on their proposals (See [[Summer of Code/Template]]).
* Congratulations to Ignacio and Jorge, winners of [http://google-opensource.blogspot.com/2014/01/google-code-in-2013-drumroll-please.html Google Code In]!!
* Google Code In 2013 has concluded. The five remarkable finalists from Sugar Labs are:
**'''Ignacio Rodríguez''' (wrote 2 new webservices -- PutLocker and GDrive -- and 4 new Sugar activities)
**'''Jorge Gómez''' (numerous enhancements to Turtle Art, et al. and wrote a first pass of Turtle Art in Javascript)
**'''Sai Vineet''' (added pen and rope objects to Physics, developed unit tests for Sugar activities, and numerous enhancements to Pippy)
**'''Emil Dudev''' (converted Sugar to gsettings, added a microphone volume control)
**'''SAMdroid''' (added an icon viewer to the Sugar Journal, made an amazing how-to video for view source, enabled recording to external devices)
* Enter the Sugar Labs '''Background Design Contest'''. See http://contest.sugarlabs.org for details.
* Sugar Labs has been selected to participate in [[Google Code In 2013]]. Mentors, please sign up at [http://www.google-melange.com/gci/homepage/google/gci2013 GCI2013]
* Congratulations to Aguz and Aneesh, the two winners of the Sugar Labs/Google Code In contest. Thanks also to all the participants and to Google.
* Sugar on a Stick '''[[Sugar on a Stick/Avocado|Avocado]]''' is out with the just released Fedora 19 and [[0.98/Notes|Sugar 0.98.8]]. Please [[Sugar_on_a_Stick/Quandong#Contributing_to_Sugar_on_a_Stick|participate]].
* '''[[0.98/Notes|Sugar 0.98]]''' has been released!!!
* Congratulations to Claudia Urrea, Gonzalo Odiard and Daniel Francis, the newest members of the Sugar Labs [[Oversight Board]].
* Daniel Narvaez has made a number of improvements to [http://sugarlabs.org/~buildbot/docs/build.html sugar-build], which has by-and-large replaced sugar-jhbuild as the preferred development environment for Fedora and Ubuntu.
* Twas the season. But still please consider making a [[Sugar Labs/Donate|donation to Sugar Labs]].
* [http://wiki.sugarlabs.org/go/File:Using_Sugar_in_the_Classroom_in_Arabic.pdf الكمبيوتر المحمول إكس أو في الفص] Sdenka Salas's book, ''Using the XO in the Classroom'' is now available in Arabic, thanks to the work of Dr. Rashid Ismael Hag Ibrahim.
* [[Nick-MTV|Concurso Internacional de One Laptop Per Child (OLPC) y Nickelodeon / MTV]]
* [http://en.flossmanuals.net/como-hacer-una-actividad-sugar/ Como Hacer Una Actividad Sugar] (''Make Your Own Sugar Activities!'') is now available.
* Listen to Walter Bender talk about Sugar on [http://twit.tv/floss134 FLOSS Weekly].
* [http://wiki.laptop.org/go/Recursos_en_espanol Recursos en espanol]
* Jim Simmons has written a [http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction FLOSS manual ''Beginner's Guide''] to writing Sugar Activities. ([http://www.archive.org/details/MakeYourOwnSugarActivities pdf])
* Download a [http://www.scribd.com/doc/20189623/The-XO-Laptop-in-the-Classroom guide to using Sugar in the classroom], written by a teacher working in rural Peru.
* Sugar on a Stick '''[[Sugar on a Stick/Quandong|Quandong]]''' is out with the just released Fedora 17 and [[0.96/Notes|Sugar 0.96.1]]. Please [[Sugar_on_a_Stick/Quandong#Contributing_to_Sugar_on_a_Stick|participate]].
* Google Code In 2012-13 is over. Many thanks to our >50 participants and our community mentors who worked on almost [[Google_Code-In_2012/GCI2012_followup|200 projects]] over six weeks in December and January.
* We are one of the projects selected for [[Google Code-In 2012]]. Please participate.
* Congratulations to Chris Leonard and Gerald Ardito, the two newest members of the Sugar Labs [[Oversight Board]].
* '''[[0.96/Notes|Sugar 0.96]]''' is released: many improvements and new features.
* [http://wiki.laptop.org/go/Release_notes/11.2.0 11.2.0] has just been released by OLPC (for those of you who run Sugar on XO hardware). Congratulations to everyone involved in the effort, with a special tip of the hat to Daniel Drake, who led this effort.
* Sugar on a Stick '''[[Sugar on a Stick/Pineapple|Pineapple]]''' is out with the just released Fedora 16 and [[0.94/Notes|Sugar 0.94]]. Please [[Sugar_on_a_Stick/Pineapple#Contributing_to_Sugar_on_a_Stick|participate]].
* Google Summer of Code is soon to be accepting applications. Please see [[Summer of Code/2012]] if you are interested in being a mentor or participant.
* We are seeking candidates for the [[Oversight_Board/2011-2012-candidates#Candidates|2011 Sugar Labs Oversight Board.]] Please consider running. If you do decide to run, please add your name to the list of candidates.
* In anticipation of the upcoming election, we are updating our [[Sugar_Labs/Members/List|membership list]]. If you are not yet a member of Sugar Labs, please send your name and an explanation of your contribution to Sugar Labs in an email to '''members at sugarlabs dot org'''.
* Sugar on a Stick '''[[Sugar on a Stick/Coconut|Coconut]]''' has finally ripened and ''fallen from the tree''. It features Fedora 15 and [[0.92/Notes|Sugar 0.92]]. It won't be long before the next version, '''[[Sugar on a Stick/Pineapple|Pineapple]]''', with Fedora 16 and Sugar 0.94 is ready.
* [[Sugar on a Stick/Mango Lassi |Sugar on a Stick '''Mango Lassi''']] has been released. It features the Sugar Learning Environment version 0.90, a small collection of core Activities, and is aimed to encourage customization and collaboration between deployments and developers.
* Our new release '''Sugar 0.92''' is available in [[OLPC:11.2.0|OLPC Release 11.2.0 test builds]] and in [[Sugar on a Stick/Beta]]. Release notes will be posted soon.
* We elected four members to the Sugar Labs [[Oversight Board]]: Sebastian Silva, Aleksey Lim, Chris Ball, and Adam Holt. They join Bernie Innocenti, Mel Chua, and Walter Bender on the board.
* Interested in Google Summer of Code? Visit our [[Summer of Code]] page.
* (SoaS Mango Lassi) The project seeks contributions for the upcoming, '''25 January 2011''' Feature submission deadline [[Features/Soas V5/| Feature submission deadline]].
* Our new release (Sugar 0.90) is out. Read about it here.
* Sugar Labs announces the availability of [[Sugar on a Stick |Sugar on a Stick "Mirabelle"]]. It features the Sugar Learning Environment version 0.88, support for 3G or 3rd generation mobile telecommunications networks, a reduced collection of core Activities, and is aimed to encourage customization and collaboration between deployments and developers.
* [[SugarWorldCup2010|Sugar World Cup 2010]]
* Our new release ([[0.88/Notes|'''Sugar 0.88''']]) is out. Read about it [[0.88/Notes|here]].
* Sugar Labs announces the availability of [[Sugar on a Stick/Blueberry|Sugar on a Stick v2, codenamed "Blueberry"]]. It features the Sugar learning environment—Version 0.86—and a number of additional Activities for children, providing a great experience for new and experienced learners. For more information and instructions—how to put SoaS on your USB key or how to deploy it—please refer to our [[Sugar_on_a_Stick/Blueberry|release notes]].
* Read about what is new in our latest release, [[0.86/Notes|Sugar 0.86]].
* Try our '''[http://launchpad.net/soas community-powered support site]''' for the Sugar on a Stick project.
* Sugar Labs announces the availability of Sugar on a Stick, codenamed "Strawberry". It features the Sugar learning environment—Version 0.84—and a number of additional activities, providing a great experience for new and experienced learners. For more information and instructions—how to put SoaS on your USB key or how to deploy it—please refer to our [[Sugar_on_a_Stick/Strawberry|release notes]].
* 08 Aug 2009 - Try our new, '''[http://getsatisfaction.com/sugarlabs community-powered support site]'''
* Read the latest [http://wiki.laptop.org/go/Education_and_Psychology memo on learning] by [http://en.wikipedia.org/wiki/Marvin_Minsky Marvin Minsky]
* Consider [http://morgancollett.wordpress.com/2009/01/19/the-status-of-sugar-post-olpc/ the status of Sugar] after OLPC
* Take a look at the [[Development Team/Release/Releases/Sucrose/0.84|latest Sugar features]] in version 0.84
* Join our [[Activity Team|activity team]].
* [[Activity Team]] formed. Our goal is to ensure that Sugar provides a complete set of high quality educational, collaborative, constructivist activities.
* [http://arstechnica.com/news.ars/post/20090107-olpc-downsizes-half-of-its-staff-cuts-sugar-development.html OLPC downsizes half of its staff, cuts Sugar development], but "OLPC's decision to end its participation in Sugar's evolution doesn't mean that Sugar itself will be coming to an end any time soon. Former OLPC president of software, Walter Bender, who left the organization last year, launched Sugar Labs to facilitate ongoing community-driven development of the Sugar project. Sugar Labs has done well for itself—it recently joined the GNOME Foundation and is currently in informal talks with some hardware vendors."
* Sugar Labs is [http://www.gnome.org/press/releases/2008-12-sugarlabs.html joining the GNOME Foundation] as part of the GNOME Advisory Board.
* Sugar Labs officially [http://conservancy.softwarefreedom.org/news/2008/dec/09/sugar/ joins the Software Freedom Conservancy].
* Sugar Labs will be participating in FUDCon, which will be held at MIT (Cambridge, MA) 9–11 January. If you can attend, please ''sign up'' on the [http://fedoraproject.org/wiki/FUDCon/FUDConF11 FUDConF11 wiki page].
* Walter Bender gave the keynote at the <span class="plainlinks">[http://www.netbookworldsummit.org/ Netbook World Summit]</span> in Paris on 1 December 2008. His notes from the conference are [[Sugar_Labs/Current_Events#Sugar_Digest|here]].
* [[Marketing Team/Events/Sugarcamp Boston 2008|SugarCamp]] was held 17–21 November in Cambridge. Notes for most of the meetings are linked from [[Marketing Team/Events/Sugarcamp Boston 2008/Schedule|here]].
* We continue to make progress on the [[Supported_systems#Starch|LiveCD and LiveUSB]] versions of Sugar.
* Read a Sugar community member's take on [http://opensource.sfsu.edu/node/562 Sugar vs XP] and the [http://www.groklaw.net/article.php?story=20080920181151638 Groklaw] take.
* Check out the [http://en.flossmanuals.net FLOSS manual] for [http://en.flossmanuals.net/write_activity Write] and write a manual for your favorite Activity.
* [[User:Aaron|Aaron Kaplan]] has ported Sugar to the Intel Classmate 2. You can read about it [http://www.olpcnews.com/software/operating_system/sugarizing_it_intel_classmate_2.html here].
* [[Development Team/Release/Releases/Sucrose/0.82|Sucrose 0.82]] has been released.
* Sugar wins a silver medal in the [http://www.idsa.org/IDEA_Awards/gallery/2008/award_details.asp?ID=772 International Design Excellence Awards '08].
</noinclude>

News

2016-03-25T21:10:48Z

Patrol: Alter word & hyphen to avoid double i

News

2016-03-25T21:06:30Z

Patrol: Alter word to avoid double i

<noinclude>* The latest community news flashes are published on the [[Main Page#Community news|main page]].

* See our community news weekly '''[[Sugar Labs/Current Events|Sugar Digest]]''' and the '''[[Archive/Current Events| Sugar Digest archive]]'''.
== Community News ==
</noinclude>
[[File:SugaronastickAvocado-320px.png|320px|right|link=Sugar on a Stick|Click Me!]]
* The application period for Google Summer of Code 2016 has ended. We have 62 project proposals, which we will vet over the next few weeks. Thanks to the applicants and community mentors.
* Congratulations to our two Google_Code-in grand-prize winners: Piotr Antosz (from Poland) and Ezequiel Pereira Lopez (from Uruguay).
* The Fedora 23 release of [[Sugar on a Stick]] is available with [[0.106/Notes|Sugar 0.106]]. This release of Sugar (v 0.106) is dedicated to the memory of Marco Gritti Presenti. Marco was a member of the original Sugar team and the lead Red Hat engineer on the project over its first three years of development. Soft-spoken but determined, Marco was a founding member of Sugar Labs and one of the original members of the Sugar Labs oversight board. Beyond the code he contributed to the project—he was a gifted software engineer; Marco shared with us his vision that Sugar ultimately belongs to its users. It is the clarity of this vision that is still reflected in the Sugar code-base and the spirit of the Sugar Labs community.
* [[0.106/Notes|Sugar 106]] has been released!! See [https://www.youtube.com/watch?v=PXFaXAGIw04&feature=youtu.be] for a quick video summary of the new features.
* Are you a developer who is new to Sugar? Consider helping us with our [http://developer.sugarlabs.org/web-architecture.md.html HTML5/Javascript framework].
* Celebrate [http://turtleartday.org Turtle Art Day].
* Donate your used USB sticks at [http://recycleusb.com Recycle USB.com]; they'll be turned into Sugar sticks and distributed to schools.
* Watch some [http://www.overstream.net/view.php?oid=i2ueryser0rz videos] of children in Uruguay explaining how they use Sugar and [http://olpc-ceibal.blogspot.com/2009/01/anecdotes-of-plan-ceibal-in-durazno.html stories from the field].<BR CLEAR=RIGHT>
<noinclude>


== Archival entries ==
* We are participating in [https://developers.google.com/open-source/gci/ Google Code In 2015]. If you have projects you'd like to suggest or would be willing to mentor, please contact walter --AT-- sugarlabs.org.
* Google Summer of Code 2015 is wrapping up. The students have been writing their final blog reports, submitting last-minute patches, and uploading their code to Google. I want to take this opportunity to thank all of our students and their mentors for all their hard work this summer. (Also, thanks once more to Google for supporting this program.) Great strides along many fronts were made. Specifically, Michaël Ohayon worked on Web versions of some core activities for the Sugarizer project: Calculate, Paint (with collaboration, Record, and Memorize. He also submitted patches to Turtle Blocks to make it compatible with Sugarizer. Mentor: Lionel Laske) Yash Khandelwal worked on Music Blocks AKA Mouse Music. This is a powerful, playful model for music in a block language. (Mentors: Devin Ulibarri and Marnen Laibow-Koser) Ishan Sharma revisited the Turtle 3D concept, rewriting it in Javascript. (Mentor: Walter) Amit Kumar Jha worked on extensions to Turtle programming this summer. He added argument passing and return values to procedures, passing arguments to and returning values from Turtle programs so that Turtle Blocks can be used for in-line programming by all Javascript activities, and he developed a unit=test framework for Turtle Blocks JS that can be extended to all of our Javascript activities. (Mentor: Walter) Richa Sehgal worked on a framework to support off-line Web programming, an interactive Javascript shell. She's submitted patches to the upstream Browse activity. (Mentor: Tony Anderson) Vibhor Sehgal and Utkarsh Dhawan, although not officially GSoC students, worked with Tony and Richa on a parallel project, Web Confusion, a series of programming challenges in the spirit of Turtle Confusion to encourage students. (Mentor: Tony Anderson) Abhinav Anurag made some progress on a Web collaboration framework for our Javascript activities. (Mentors: Martin Abente and Lionel Laske)
* Our Google Summer of Code interns are: Abhinav, Ishan, Yash, Michaël, Richa, and Amit. Looking forward to a fun and productive summer.
* [[0.104/Notes|Sugar 104]] has been released. Many thanks to our release manager, Martin Abente. Note that well over 50% of the patches to Sugar Activities came from youths in the Sugar community and just under 50% of the patches to Sugar core libraries came from youths in the Sugar community.
* Congratulations to Ignacio Rodríguez and Sam Parkinson, the grand-prize winners from Sugar Labs in [http://google-opensource.blogspot.com/2015/02/google-code-in-2014-welcome-to-winners.html Google Code-in]. Our finalists are Cristian Garcia, Daksh Shah, and Jae Eun (Jasmine) Park.
* We've been accepted into Google Summer of Code 2015. Potential students and mentors, please go to our [[Summer_of_Code/2015|GSoC 2015]] page in the wiki.
* [[Google Code In 2014]] has begun. Sugar Labs is participating. We hope you do as well.
* Trisquel 7 Sugar ([[Trisquel On A Sugar Toast]]) has been released with Sugar 0.102.
* We are excited to announce that Sugar 0.102.0 (stable) is released. See [[0.102/Notes]] for details. And please help us with [[0.102/Testing|Testing]].
* We just received hundreds more [[Sugar on a Stick]] USB keys from the [http://recycleusb.com Recycle USB] program sponsored by [http://www.nexcopy.com NexCopy].
* Sugar on a Stick 10 is out with the just released Fedora 20 and [[0.100/Notes|Sugar 0.100]]. Please [[Sugar_on_a_Stick/10#Contributing_to_Sugar_on_a_Stick|participate]].
* Sugar Labs has been accepted into [[Summer of Code/2014|Google Summer of Code for 2014]]!! Potential students should start working on their proposals (See [[Summer of Code/Template]]).
* Congratulations to Ignacio and Jorge, winners of [http://google-opensource.blogspot.com/2014/01/google-code-in-2013-drumroll-please.html Google Code In]!!
* Google Code In 2013 has concluded. The five remarkable finalists from Sugar Labs are:
**'''Ignacio Rodríguez''' (wrote 2 new webservices -- PutLocker and GDrive -- and 4 new Sugar activities)
**'''Jorge Gómez''' (numerous enhancements to Turtle Art, et al. and wrote a first pass of Turtle Art in Javascript)
**'''Sai Vineet''' (added pen and rope objects to Physics, developed unit tests for Sugar activities, and numerous enhancements to Pippy)
**'''Emil Dudev''' (converted Sugar to gsettings, added a microphone volume control)
**'''SAMdroid''' (added an icon viewer to the Sugar Journal, made an amazing how-to video for view source, enabled recording to external devices)
* Enter the Sugar Labs '''Background Design Contest'''. See http://contest.sugarlabs.org for details.
* Sugar Labs has been selected to participate in [[Google Code In 2013]]. Mentors, please sign up at [http://www.google-melange.com/gci/homepage/google/gci2013 GCI2013]
* Congratulations to Aguz and Aneesh, the two winners of the Sugar Labs/Google Code In contest. Thanks also to all the participants and to Google.
* Sugar on a Stick '''[[Sugar on a Stick/Avocado|Avocado]]''' is out with the just released Fedora 19 and [[0.98/Notes|Sugar 0.98.8]]. Please [[Sugar_on_a_Stick/Quandong#Contributing_to_Sugar_on_a_Stick|participate]].
* '''[[0.98/Notes|Sugar 0.98]]''' has been released!!!
* Congratulations to Claudia Urrea, Gonzalo Odiard and Daniel Francis, the newest members of the Sugar Labs [[Oversight Board]].
* Daniel Narvaez has made a number of improvements to [http://sugarlabs.org/~buildbot/docs/build.html sugar-build], which has by-and-large replaced sugar-jhbuild as the preferred development environment for Fedora and Ubuntu.
* Twas the season. But still please consider making a [[Sugar Labs/Donate|donation to Sugar Labs]].
* [http://wiki.sugarlabs.org/go/File:Using_Sugar_in_the_Classroom_in_Arabic.pdf الكمبيوتر المحمول إكس أو في الفص] Sdenka Salas's book, ''Using the XO in the Classroom'' is now available in Arabic, thanks to the work of Dr. Rashid Ismael Hag Ibrahim.
* [[Nick-MTV|Concurso Internacional de One Laptop Per Child (OLPC) y Nickelodeon / MTV]]
* [http://en.flossmanuals.net/como-hacer-una-actividad-sugar/ Como Hacer Una Actividad Sugar] (''Make Your Own Sugar Activities!'') is now available.
* Listen to Walter Bender talk about Sugar on [http://twit.tv/floss134 FLOSS Weekly].
* [http://wiki.laptop.org/go/Recursos_en_espanol Recursos en espanol]
* Jim Simmons has written a [http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction FLOSS manual ''Beginner's Guide''] to writing Sugar Activities. ([http://www.archive.org/details/MakeYourOwnSugarActivities pdf])
* Download a [http://www.scribd.com/doc/20189623/The-XO-Laptop-in-the-Classroom guide to using Sugar in the classroom], written by a teacher working in rural Peru.
* Sugar on a Stick '''[[Sugar on a Stick/Quandong|Quandong]]''' is out with the just released Fedora 17 and [[0.96/Notes|Sugar 0.96.1]]. Please [[Sugar_on_a_Stick/Quandong#Contributing_to_Sugar_on_a_Stick|participate]].
* Google Code In 2012-13 is over. Many thanks to our >50 participants and our community mentors who worked on almost [[Google_Code-In_2012/GCI2012_followup|200 projects]] over six weeks in December and January.
* We are one of the projects selected for [[Google Code-In 2012]]. Please participate.
* Congratulations to Chris Leonard and Gerald Ardito, the two newest members of the Sugar Labs [[Oversight Board]].
* '''[[0.96/Notes|Sugar 0.96]]''' is released: many improvements and new features.
* [http://wiki.laptop.org/go/Release_notes/11.2.0 11.2.0] has just been released by OLPC (for those of you who run Sugar on XO hardware). Congratulations to everyone involved in the effort, with a special tip of the hat to Daniel Drake, who led this effort.
* Sugar on a Stick '''[[Sugar on a Stick/Pineapple|Pineapple]]''' is out with the just released Fedora 16 and [[0.94/Notes|Sugar 0.94]]. Please [[Sugar_on_a_Stick/Pineapple#Contributing_to_Sugar_on_a_Stick|participate]].
* Google Summer of Code is soon to be accepting applications. Please see [[Summer of Code/2012]] if you are interested in being a mentor or participant.
* We are seeking candidates for the [[Oversight_Board/2011-2012-candidates#Candidates|2011 Sugar Labs Oversight Board.]] Please consider running. If you do decide to run, please add your name to the list of candidates.
* In anticipation of the upcoming election, we are updating our [[Sugar_Labs/Members/List|membership list]]. If you are not yet a member of Sugar Labs, please send your name and an explanation of your contribution to Sugar Labs in an email to '''members at sugarlabs dot org'''.
* Sugar on a Stick '''[[Sugar on a Stick/Coconut|Coconut]]''' has finally ripened and ''fallen from the tree''. It features Fedora 15 and [[0.92/Notes|Sugar 0.92]]. It won't be long before the next version, '''[[Sugar on a Stick/Pineapple|Pineapple]]''', with Fedora 16 and Sugar 0.94 is ready.
* [[Sugar on a Stick/Mango Lassi |Sugar on a Stick '''Mango Lassi''']] has been released. It features the Sugar Learning Environment version 0.90, a small collection of core Activities, and is aimed to encourage customization and collaboration between deployments and developers.
* Our new release '''Sugar 0.92''' is available in [[OLPC:11.2.0|OLPC Release 11.2.0 test builds]] and in [[Sugar on a Stick/Beta]]. Release notes will be posted soon.
* We elected four members to the Sugar Labs [[Oversight Board]]: Sebastian Silva, Aleksey Lim, Chris Ball, and Adam Holt. They join Bernie Innocenti, Mel Chua, and Walter Bender on the board.
* Interested in Google Summer of Code? Visit our [[Summer of Code]] page.
* (SoaS Mango Lassi) The project seeks contributions for the upcoming, '''25 January 2011''' Feature submission deadline [[Features/Soas V5/| Feature submission deadline]].
* Our new release (Sugar 0.90) is out. Read about it here.
* Sugar Labs announces the availability of [[Sugar on a Stick |Sugar on a Stick "Mirabelle"]]. It features the Sugar Learning Environment version 0.88, support for 3G or 3rd generation mobile telecommunications networks, a reduced collection of core Activities, and is aimed to encourage customization and collaboration between deployments and developers.
* [[SugarWorldCup2010|Sugar World Cup 2010]]
* Our new release ([[0.88/Notes|'''Sugar 0.88''']]) is out. Read about it [[0.88/Notes|here]].
* Sugar Labs announces the availability of [[Sugar on a Stick/Blueberry|Sugar on a Stick v2, codenamed "Blueberry"]]. It features the Sugar learning environment—Version 0.86—and a number of additional Activities for children, providing a great experience for new and experienced learners. For more information and instructions—how to put SoaS on your USB key or how to deploy it—please refer to our [[Sugar_on_a_Stick/Blueberry|release notes]].
* Read about what is new in our latest release, [[0.86/Notes|Sugar 0.86]].
* Try our '''[http://launchpad.net/soas community-powered support site]''' for the Sugar on a Stick project.
* Sugar Labs announces the availability of Sugar on a Stick, codenamed "Strawberry". It features the Sugar learning environment—Version 0.84—and a number of additional activities, providing a great experience for new and experienced learners. For more information and instructions—how to put SoaS on your USB key or how to deploy it—please refer to our [[Sugar_on_a_Stick/Strawberry|release notes]].
* 08 Aug 2009 - Try our new, '''[http://getsatisfaction.com/sugarlabs community-powered support site]'''
* Read the latest [http://wiki.laptop.org/go/Education_and_Psychology memo on learning] by [http://en.wikipedia.org/wiki/Marvin_Minsky Marvin Minsky]
* Consider [http://morgancollett.wordpress.com/2009/01/19/the-status-of-sugar-post-olpc/ the status of Sugar] after OLPC
* Take a look at the [[Development Team/Release/Releases/Sucrose/0.84|latest Sugar features]] in version 0.84
* Join our [[Activity Team|activity team]].
* [[Activity Team]] formed. Our goal is to ensure that Sugar provides a complete set of high quality educational, collaborative, constructivist activities.
* [http://arstechnica.com/news.ars/post/20090107-olpc-downsizes-half-of-its-staff-cuts-sugar-development.html OLPC downsizes half of its staff, cuts Sugar development], but "OLPC's decision to end its participation in Sugar's evolution doesn't mean that Sugar itself will be coming to an end any time soon. Former OLPC president of software, Walter Bender, who left the organization last year, launched Sugar Labs to facilitate ongoing community-driven development of the Sugar project. Sugar Labs has done well for itself—it recently joined the GNOME Foundation and is currently in informal talks with some hardware vendors."
* Sugar Labs is [http://www.gnome.org/press/releases/2008-12-sugarlabs.html joining the GNOME Foundation] as part of the GNOME Advisory Board.
* Sugar Labs officially [http://conservancy.softwarefreedom.org/news/2008/dec/09/sugar/ joins the Software Freedom Conservancy].
* Sugar Labs will be participating in FUDCon, which will be held at MIT (Cambridge, MA) 9–11 January. If you can attend, please ''sign up'' on the [http://fedoraproject.org/wiki/FUDCon/FUDConF11 FUDConF11 wiki page].
* Walter Bender gave the keynote at the <span class="plainlinks">[http://www.netbookworldsummit.org/ Netbook World Summit]</span> in Paris on 1 December 2008. His notes from the conference are [[Sugar_Labs/Current_Events#Sugar_Digest|here]].
* [[Marketing Team/Events/Sugarcamp Boston 2008|SugarCamp]] was held 17–21 November in Cambridge. Notes for most of the meetings are linked from [[Marketing Team/Events/Sugarcamp Boston 2008/Schedule|here]].
* We continue to make progress on the [[Supported_systems#Starch|LiveCD and LiveUSB]] versions of Sugar.
* Read a Sugar community member's take on [http://opensource.sfsu.edu/node/562 Sugar vs XP] and the [http://www.groklaw.net/article.php?story=20080920181151638 Groklaw] take.
* Check out the [http://en.flossmanuals.net FLOSS manual] for [http://en.flossmanuals.net/write_activity Write] and write a manual for your favorite Activity.
* [[User:Aaron|Aaron Kaplan]] has ported Sugar to the Intel Classmate 2. You can read about it [http://www.olpcnews.com/software/operating_system/sugarizing_it_intel_classmate_2.html here].
* [[Development Team/Release/Releases/Sucrose/0.82|Sucrose 0.82]] has been released.
* Sugar wins a silver medal in the [http://www.idsa.org/IDEA_Awards/gallery/2008/award_details.asp?ID=772 International Design Excellence Awards '08].
</noinclude>

News

2016-03-25T21:04:06Z

Patrol: hyphen code to avoid double i

Sugar Labs/Current Events

2016-03-25T20:49:12Z

Patrol: typos

== What's new ==

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

== Sugar Digest ==

1. I promised to share the occasional Marvin Minsky story. I heard many that were new to me at his memorial service at MIT last week, one of which I'd like to share here. Cynthia Solomon, one of the co-inventors of Logo and co-author of the classic paper from 1971, [https://dspace.mit.edu/bitstream/handle/1721.1/5836/AIM-248.pdf "Twenty Things to Do with a Computer"], was one of the speakers at the service. She recalled the many contributions Marvin made to Logo, the language, and to the pedagogy we associate with Seymour. What I didn't realize was the extent to which Marvin (and his students) were responsible for broadening the scope of computational thinking beyond the desktop. Cynthia shared some before and after slides of children using Logo in the late 1960s and early 1970s, after Marvin's influence had manifest itself. The excitement of using programming in the context of graphics, robotics, and music was palpable. We at Sugar Labs are very much standing on Minsky's shoulders.

2. The application period for Google Summer of Code (GSoC) has ended. We have 62 applications this year, exceeding our total from last year. Over the next week, community mentors will vet the applications and we will apply for slots from Google based on both the quality of the applications (quite high from my sampling) and the ability of the community to support the summer interns. If you are interested in being a mentor, it is not too late. Please contact me.

=== In the Community ===

3. Devin Ulibarri and I had the opportunity to speak at [https://libreplanet.org/2016/ LibrePlanet]. Our topic was [https://wiki.sugarlabs.org/images/c/c7/Education-needs-free-software.pdf "Education needs Free/Libre Software needs education."]

<blockquote>ABSTRACT: The bad news is that educational technology has largely failed to deliver on its promise. Its focus on efficiency rather than on learning has resulted in a further reinforcement of education as a system of instruction to curricula rather than one of student-driven construction of knowledge.

The good news is that Free/Libre Software is the starting point towards a solution—not just because it tends to focus on putting powerful tools into the hands of its end-users, but also because Free/Libre Software espouses a culture of doing and sharing in a context of critique, reflection, and personal responsibility.

In this session, we will review some tangible ways in which Free/Libre Software is having and can have a positive impact on education and some things we can and should be doing better. We will then discuss strategies for advocating for Free/Libre Software in education systems both in the US and globally. The next generation of computer users are in school today. We need to ensure that the next generation is empowered to take advantage of the opportunities afforded by Free/Libre Software.</blockquote>

Unlike the session on Free/Libre Software at EdFoo, which was sparsely attended, there was standing-room only for our session. The recording should be on line within a few weeks.

It occured to me afterwards that one simple call to action would be for every member of the Free/Libre Software community to adopt a teacher (or be open to being adopted, e.g., Devin, a music teacher, has adopted me). We need to make our voices heard.

4. David Crossland, whom I had the pleasure of meeting at LibrePlanet, has been busy recruiting GSoC students to write a Sugar Font Editor activity (a project that has long been on both my and Gonzalo Odiard's wish list).

David said out loud what many of us have been thinking: our wiki is a mess. He has issued a call to action to do some gardening. Specifically, he and I will be leading a two-day sprint on the weekend of May 14/15 in the Boston area (USA). The goal is to begin cleaning up the wiki content and other parts of Sugar Labs web properties, making them ready for the GSoC project to start.

If you'd like to participate, in person or remotely, please let Walter know. The final time and location details (most likely somewhere on the MIT campus) will be shared on the IAEP list nearer the time.

=== Tech Talk ===

5. Many thanks to Samuel Cantero, a member of the Sugar Labs systems team, who has been quietly maintaining and upgrading our servers behind the scenes. He recently fixed the breakage with our Trac system; our Wordpress instance; and some problems with the Sugar Activity portal. (Tip of the hat to alsroot for his help regarding ASLO as well).

=== Sugar Labs ===

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

== Community News archive ==

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

==Planet==

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

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

==Press releases==
[http://www.sugarlabs.org/index.php?template=press See our Press Page]

[[Category:General public]]

Request New Features

2016-03-25T11:57:22Z

Patrol: Reverted edits by KarolinePage (talk) to last revision by FGrose

<noinclude>[[Category:Wish list]][[Category:General public]][[Category:Idea]]

'''Please describe new feature requests by one of the methods below:'''

'''Note:''' We periodically review these requests, generating ''enhancement tickets'' in [http://bugs.sugarlabs.org our tracking system].
* Developers: please continue to file feature requests directly in the [http://bugs.sugarlabs.org tracking system] and develop proposals through the [[Features/Policy]] process.
* You may edit this and other pages of the wiki.
* See also [[Wish list]] and [[:Category:Wish list]].
</noinclude>

== Change default Mesh settings for greater security ==
We were very excited to try Sugar on a Stick (Mirabelle). However, I was very surprised to find lots of users with whom I could "make friends," some of whom seemed to have included their real names (given name and surname!).

It took some digging in this Wiki to find out that I just had to delete the Mesh entry (i.e., the reference to jabber.sugarlabs.org) so that only Sugar users on our Wi-Fi would show up.

There may be a genuine security concern here. We simply have no way of knowing who the other users are with whom a child can "make friends." All it would take is for one bad thing to happen for the Sugar project to suffer.

While we love the idea of children from all over the world collaborating on-line, perhaps pragmatic concerns about the security of all children should lead us, at the very least, to have the default setting on the Mesh entry as a blank. Parents and teachers will then be responsible for enabling this feature, if they so wish.
: This request has been posted to the Sugar developers mailing list at http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024190.html. You may want to watch or participate in the discussion there. --[[User:FGrose|FGrose]] 14:09, 26 May 2010 (EDT)

== Maintain applications throughout updates ==
I am running Joyride updates and really am liking the newest versions. However, it drives me crazy that some user data is maintained (ie, friends) but other data, such as applications I install, are obliterated. This is a really serious issue in terms of the viability of this OS. Can something be done? -- [[User:Graham|Graham]]

:Unfortunately, OLPC is no longer maintaining the Joyride builds, so to some extent, this request is no longer something we can address. But <code>olpc-update</code> should preserve any activities you have installed in /home/olpc/Activities.

==easier bug reporting==
I am very impressed with KDE's bug reporting mechanism and as well Ubuntu's. I think it would be of great assistance to users and coders if there was an automatic error detection and prompt for reporting the bug. I've made [http://www.youtube.com/watch?v=BbUmk8Rk80c a video of the KDE bug reporting experience] which is exceptionally easy and user friendly... and if for no other reason kids will be using Sugar, so Sugar should be kid easy for bug reporting.--[[User:Dennis Daniels|Dennis Daniels]] 00:05, 11 August 2009 (UTC)

== OS Updates ==

It would be great if there was a Sugar OS auto-update tool in the Sugar interface (or a graphical control panel, as detailed below) to make keeping up-to-date easy.

:This feature is being tracked in [http://trac.sugarlabs.org/ticket/105 Ticket #105].

==Download Page==

If this wiki is the go to place for all things Sugar related then you need a download page with installation instructions and a getting started guide linked prominently from the front page.

This should have details for downloading sugar packages to install on top of lots of different OSs (even Windows!) as well Live CD images. That way folks like me with little programming experience can try before they buy, can help with tasks like translation, documentation.
:See [[Downloads]].

==Python tutorial==

I get the impression that python is central to sugar. How about a page of general Python resources. Basic tutorials Sugar customisation info etc.[[Special:Contributions/81.187.181.168|81.187.181.168]] 10:35, 28 June 2008 (UTC)

:See the [[Activity_Team/Resources#Python_Reference_.26_Tutorials|Python tutorial list]]

== File System ==

I love the Journal function. It's great. But it's near impossible to store and find files in Sugar, and name/locate files on other devices. We need a drag & drop system, and the ability to move files between storage devices easily. Give people the choice of either (Journal is very handy to track activity and, similar to the _open recent_ function in many OS X/Windows apps, lets you find recent stuff easily. I think this needs to be a new icon on the home view, alongside journal, and when you access it, or Journal, it's intuitive and easy to move between either view.

:The new journal design call for some of what you described above: http://wiki.laptop.org/go/Designs#Journal [[User:Tomeu|Tomeu]] 10:47, 23 May 2008 (UTC)

Yes, it's better. But I still want to see the files I have created/saved in a list, by storage device. File name. Type. Size. Date last used.

I recently gave my 4 year old an OX and it has been interesting working through things with her. On problem I have with the file system is highlighted when using the memory game, I want to open a game we created earlier, fine but the journal opens and shows everything not just things that can be opened by that activity making it very hard to find stuff.

:The [[Development_Team/Release/Releases/Sucrose/0.84#Journal|Journal in v0.84]] has a number of features that may help, including the ability to search for starred items (★) and by activity type. Also, the new [[Development_Team/Release/Releases/Sucrose/0.84#Resume_Activity|Resume feature]] should reduce "Journal spam".

== Usability ==
7/18/2008

I've been writing an activity on an XO using only XO resources. After all, the target community members are people for whom the XO is the only computer to which they have access. If you realistically want to serve that community, you have to walk a mile in their shoes.

I have had some success, but there are many frustrations, the Journal interface being the most egregious. Some notable troubles:

* I spend an inordinate amount of time deleting Journal clutter. It should be possible to turn automatic logging off, since not all activity will necessarily be worth tracking. Better yet, include a GUI for setting filter options for what will be logged, and what will not be logged.
::We took [[Development_Team/Release/Releases/Sucrose/0.84#Resume_Activity|a different approach]] to the Journal spam issue.

* The flat file display of directories on USB or SD devices also clutters the Journal. Especially annoying is when a complete web page is saved on another computer and viewed on an XO (for example tutorial information about the XO). The detail data in the subdirectory makes it hard to find the root HTML file to view the page. Moreover, as nearly as I can tell, it is not possible to save a complete web page using only the XO. Something is saved, but it displays incorrectly when viewed later. This is of fundamental importance for areas with little or unreliable internet service. A child finds something at school, he saves it so he can read it later at home where there is no internet, and what he gets is some partially readable glop.
::This feature request is being tracked in [http://trac.sugarlabs.org/ticket/584 Ticket 584].

* The OLPC developers guide extols the Journal as a replacement for file hierarchies, and suggests that such hierarchies are unnatural. This is not true: containers are very intuitive, especially for children. Even in the most primitive hut, there is an area for cooking, which contains a larder which contains food items. The cooking area also contains a storage area for utensils and an area for food preparation. The hut itself contains a sleeping area, a cooking area, a latrine area and a social area, even if it is only one room. Moreover, the hut is contained in a community, itself contained in a nation. To assert that hierarchical organization is unnatural borders on blind hubris. Hierarchical organization of information is no exception: bearing witness are the containers library, collection, shelf, volume, and page within the volume. Indeed, the entire internet, the new global library, is intrinsically and irretrievably hierarchical. Depriving children of these fundamental organizational tools is tantamount to crippling them.
::Arguably this request is overstated–"crippling them"–but [http://trac.sugarlabs.org/ticket/584 Ticket 584] presumably will address this.

* With reference to the previous point, it would be nice to have something like the triangle by directories on Macs, or in the example listings in pippy: click on the triangle, and the contained information is toggled between hidden and expanded states. A child could create a container in the Journal, and drag different Journal entries into it to organize the log of his activities according to his own choosing, and then click on the triangle to hide those that are distracting to the activity at hand. This is conceptually no different than putting toys away in a toy box, and it ''is'' perfectly natural to all human beings, children or otherwise. Moreover, this functionality is already present, but only for 'hard' containers like USB and SD devices. Is it such a stretch to allow 'soft' user created containers as journal entries?
::See above.

* I have discovered that a journal entry is really a saving of the state of an activity comprising data, activity, view state (not always restored properly), etc. This notion of a saved state that may be identically resumed is very good, and very convenient, when it has been fully implemented by an activity. It should extend to power cycles. When I turn the machine back on, all my running activities should be resumed and the clipboard should have all my clips, and the machine view should be restored to the most recent active activity before power cycling.
::This feature request is being tracked in [http://trac.sugarlabs.org/ticket/585 Ticket 585].

* With reference to the previous point, this distinction between what a journal entry really is and a file or directory (which are very useful containers, not at all obsolete) should be made clearer. Downloads are implicitly files (documents or data if you prefer), not activities. Often, there is no natural activity for working with a download, or the default activity may be cumbersome or unworkable. The only workable means for accessing a download that I have discovered is to copy it to a USB or SD device, and then use the command line to manipulate it. The rudimentary task of managing development files has required me to repeatedly resort to the command line, which I detest, being a primitive legacy of the days in the 1970's when 64kbyte mini-computers ruled. It should be possible to copy, delete, rename, and execute files from the browser activity. This is the 21st century after all.
::This is being worked through in a slightly different way as discussed in [http://trac.sugarlabs.org/ticket/574 Ticket 574].

* The simple task of saving a module created with Pippy into a suitable library directory turns into an ordeal because of these limitations on necessary functionality which ultimately serves not to educate, but to handicap children.
::Please provide a more detailed description of this problem.

As a final remark, I am very aware that this is not a laptop project, nor is it a developer project, but an education project. Consider: children get older. They become more sophisticated. They begin to desire to express themselves and collaborate in more complicated ways, and engage in more complicated activities, which can not be linearized temporally. Activity development is just one instance of those possible future activities. Temporal state saving at the GUI level is a new and useful idea, but it is not sufficient. Usability will ultimately make or break this project.
::Thank you for your detailed and thoughtful comments. Sugar Labs is busy implementing many of them, and could use more of your help in implementing these types of ideas. We agree that usability is a paramount success factor—possibly second only to participation. Join us. --[[User:FGrose|FGrose]] 04:17, 20 March 2009 (UTC)

== Sugarize Firefox ==

It would be greatly appreciated if someone can develop a Sugarized version of Firefox! I don't think the collaboration tools are necessary (since the built in browser already does this), but people keep bringing it up as an issue why they don't like Sugar. Help, someone! That, or add tabs to the browse activity and a better Bookmarking mechanism.

* I use a "sugar coated" version of SeaMonkey; which is a full suite (browser, email, etc). Might Seamonkey be a better option due to its (as I understand) smaller footprint & greate number of options? -- [[User:AuntiMame]] 22 May 2008 16:05

AuntiMame - Can this be added to [[Activities]] where we can compile a list of all available applications, installation instructions, and links to download? -- [[User:Graham|Graham]]

: Can we have installation instructions for SeaMonkey?? -- [[User:Graham|Graham]]

* The Sugar Browser is actually based on the Firefox guts (xulrunner), but the UI has been developed for Sugar. You can find more details [http://wiki.laptop.org/go/Browse#Summary here.] There have been many requests, like yours, to improve it by supporting more features that "normal" browsers have. I agree that tabs and bookmarks would be welcome additions and useful for children. -- [[User:Ridderman|Ridderman]] 20:53, 22 May 2008 (UTC)

* Point of information for Ridderman but Browse already has bookmarks which work fine. [[User:Tinker|Tinker]] 05:59, 5 July 2008 (UTC)

== Sugar Control Panel ==

I would like to see a GUI control panel... I am discovering new features to customize through terminal, however, a lot of them could be easily accessible through a simple control panel GUI. I think this would help newer users a great deal.

<ol>
*Date, Time & Timezone
*Language
*User Accounts
*WiFi settings
*Jabber server(s) - ability to input multiple servers for different user groups (schools, cities, countries, etc.).
*Add/Remove Programs
*System Updates
*Desktop GUI settings
*Name SD card and USB media drives, etc.
*Running Linux Applications Under Sugar - A script has been written to Sugar Coat Linux apps to make them run under Sugar desktop (i.e. making them to run in the Sugar interface, without the collaboration and other Sugar integration programmed into them). Can this be made more user-friendly and incorporated into a Sugar Control Panel GUI, to make adding applications easier?
*What else?
*How about also getting latitude and longitude from the "nearby city" selected in the timezone setting dialog? -- [[User:Davewa|davewa]] 19:23, 23 May 2008 (UTC)
*Adding AccessX support - [http://wiki.laptop.org/go/AccessX AccessX] allows accessibility enhancements, like sticky keys, mouse keys, repetition speed. It works in Sugar but requires root access to be installed. The Tk config interface doesn't fit well into Sugar, too. -- [[User:andrea.mangiatordi|Andrea]] 16:41, 21 May 2009 (UTC)

</ol>

-- [[User:Graham|Graham]]

:This is a great idea, and it's actually already being developed. You can find more details [http://wiki.laptop.org/go/Sugar_Control_Panel#GUI_for_the_command_line_tool_.28work_in_progress.29 here] or in the sugar mailing lists. I'm not sure whether this will be available for the next Sucrose release, 0.82. -- [[User:Ridderman|Ridderman]] 21:02, 22 May 2008 (UTC)

*Ability to turn off/on Jabber in GUI Control panel so multiple users can transfer files and collaborate on a local wireless or wired network

: What is Sucrose, exactly?
:: See [[Taxonomy#Sucrose:_The_interface.2C_plus_a_set_of_demonstration_activities|Sucrose]]; which suggests we may want a [[Documentation_Team/Glossary|Glossary]] of (un)common terms. --[[User:Walter|Walter]] 23:12, 22 May 2008 (UTC)

== Chat (Jabber) ==

Ability to add multiple Jabber servers (connect with functionality detailed above) and switch between them in the chat program.

:From Wiki:

:But what if you wish to connect to one of several jabber servers because you belong to several communities/SIGs? I can live with one-at-a-time, but it would be wonderful if I could pick from a list I've created. Or at least a list of jabber servers I've previously connected to. How about a syntax for "choice <n> from file <x>" and "show me choices in file <x>"? -- davewa
:This feature request is being tracked in [http://trac.sugarlabs.org/ticket/587 Ticket 587]

== Browse ==

I cannot copy a link, I can't save a jpg, the Sugar OS changes the filename of a file which it does not recognise, the directory system is hidden, there is no predictive text when typing URL's or usernames, there's no tabbed browsing, there's no cookie, proxy or popup control.
:Browse 100 support copying/downloading images and links. (Wait for the hover menu or use the right mouse button on the object you are interested in.) The other feature requests are being tracked in [http://trac.sugarlabs.org/ticket/591 Ticket 591].

== Printer Support ==

I don't need to detail this very much - it's self evident. Support for generic USB printer drivers, and School Server printing? -- [[User:Graham|Graham]]
:<tt>yum install cups</tt> works out of the box so you can easily add network printers. But printing is not exposed in the Sugar UI. There was work going on at the OSU Open Systems labs... I'll ping them to find out if they have been making headway. --[[User:Walter|Walter]] 12:19, 23 May 2008 (UTC)

Thanks. We await news with baited breath. -- [[User:Graham|Graham]]
:This is being proposed as a [[Development Team/Project Ideas#Print_Support|Google Summer of Code project.]]

==Support for learning languages==

The Internet provides unprecedented access to materials in many languages, and to speakers of many languages. There are numerous aids to [[learning languages]], including dictionaries of some languages, textbooks, reference grammars, and flash card software for studying vocabulary and inflections. We need more of this kind of material, and we also need

* Graded materials for language learners, written and spoken
* Text-to-speech with text coloring in the manner of [[SLS]] (in progress)
* [[Speech recognition]], including speech-to-text
* Improved translation software
* Software that can carry out grammatical transformations, and create interactive drills on language structure
* Curricula and teaching/learning guides for languages

These materials fall into the categories of [[Education_Team/language content]], [[textbooks]] in a more advanced form incorporating software, and [[computational linguistics]]. Information on culture and other aspects of language communities is also essential.

==Support for family interaction==

Would it be possible to add collaborators that are people without laptops? for example my child is 4 and some of the activities need help from me to get her going, if I could put my self in the group view with the activities that she does with me. When I am invited to play with her then more activities could show, and perhaps the icon in the center of the screen could change slightly to show she is playing with dad or mum? Again the journal would also note when we were playing together.
:This suggests a wonderful use for the [[olpc:Record | Record]] (Camera) Activity. It would also crystallize the concept of a person, apart from a person's laptop. One could start recording people in their life by capturing an image or video of them. Once they register the person in a new registry, the images, videos, and all sorts of events and objects could be associated with the person. Sugar could extend their API to support the integration of real people with the laptop and school network. As you say, the Journal could then become an even more descriptive, connected, and complete learning record, and permit even more advanced learning and collaboration models. Great suggestion! --[[User:FGrose|FGrose]] 18:04, 16 March 2009 (UTC) I've entered it as a [[Development Team/Project Ideas#Registry for people | Development Team project idea]]. --[[User:FGrose|FGrose]] 19:00, 16 March 2009 (UTC)

==Better Support for Screencasting==
I have read the [[Activities/Screencast| Activity Screencast page]].
===training for Soas/ Sugar===
As a teacher with a little technical background, I can say that SoaS will have a lot of trouble getting traction into the schools without a lot more training. That training could easily be generated with Screencasts by volunteers IF screencasting was _better supported_ in SoaS. If screencasting was better implemented students could show, maybe even STREAM their videos, to their teachers, parents, friends and show how SMART they are by letting them make their own movies of same...

Look at these tutorials on the wiki:--[[User:Satellit|Satellit]] 12:08, 5 March 2012 (EST)
====How to use Sugar====
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Introduction_to_Sugar_Interface
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Connecting_to_the_Internet
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Drag-Drop
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/How_to_use_IRC
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Backup-restore
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Send_to_a_friend#Send_file_from_sugar-journal
====Installation====
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/liveinst
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/netinstall

===better bug reports===
Furthermore, bug reports become much clearer when recorded _and_ the users knows to pull up the logs too. And the whole process of making a good bug report could be demonstrated in its entirety with a screencast... the vast numbers of users don't know a zillionth of what the devs know or need to know about the bug a user is experiencing... and as most of the users don't speak English, and most devs do, you've got a serious disconnect between what your users need to tell you... enter the 'screencast' and most of the big problem description becomes evident.
===PR for Soas/Sugar===
With more 'evidence' of the coolness of Sugar, people will get excited about SoaS perhaps like what happened around the Phun Physics package... [http://www.phunland.com/wiki/Home Phun] became one of the physics games of choice, for those without money, because of the tremendous number of naive users/kids producing Phun demonstrations on [http://www.youtube.com/results?search_query=phun&search_type=&aq=f Youtube]. --[[User:Dennis Daniels|dgd]] 3Aug9

==Embedded Predictive text==
Despite the emphasis on a non text environment there are numerous areas of education that rely on learners writing text.
The integration of a predictive text system similar to that used in the windows 'Typing Assistant' and the Co:Writer software used on the specialist hardware text editor the Alpasmart 3000, Alphasmart Neo, and Neo2.
Such an integration would provide sugar with an environment that would support those with learning difficulties e.g dyslexia and additionally extend the learners vocabulary as such systems give several numbered options to choose from as you type a given word, when the writer sees the word, selecting with the cursor or typing the number or word then utilises the selected word within the text entry dialog or document.A simple Function key combination switches the system on and off for free typing. --[[User:R Draycott|dgd]] 20Nov2009

:Erikos's recent work on a system-wide spell-checker might be a reasonable model to base such an intervention on. --[[User:Walter|Walter]] 14:06, 20 November 2009 (UTC)

==sugar-emulator==
*satellit 03/15/2011
#install sugar-emulator with command "sugar-emulator -f" as default
:This would allow sugar emulator to match screen size of hardware it is running on and always be full screen
: alternately provide a modal button on top frame of emulator window to switch to full screen and back at will.
:[[Emulator/Full Screen|how to configure full screen]].

==Chatbot Terminal==
I think it would be very valuable for children to have a terminal emulator that they could have a conversation with, but also one that can teach some useful linux commands.

Some examples:
$Hello
#Hi, how are you
$what is the weather like?
#inside a computer it can be as hot as 150 degrees, but it's only a mild 110 degrees today. How about where you are?
$how do I find a file on my computer?
#well, there is a command called 'find' which you can use to find a file by name. try find / test.txt

etc.

The challenge that I face is that the terminal is intimidating in comparison to IOS. I think a specialized conversation bot could do wonders for making children more comfortable in the CLI
--[[User:Micheal Breathnach|MPB]] 10Dec2012

Wiki Team/Guide/Collapsible content

2013-11-03T22:34:35Z

Patrol: Created page with "See https://www.mediawiki.org/wiki/Manual:Collapsible_elements. The default toggle text is Expand/Collapse. {| class="mw-collapsible mw-collapsed wikitable" ! The Header || r..."

See https://www.mediawiki.org/wiki/Manual:Collapsible_elements.

The default toggle text is Expand/Collapse.
{| class="mw-collapsible mw-collapsed wikitable"
! The Header || remains visible
|-
| This content || is hidden
|-
| at first || load time
|}

If one wishes something different, data-collapsetext= and data-expandtext= may be set as in this example:

{| class="mw-collapsible mw-collapsed wikitable" data-collapsetext="hide ▲" data-expandtext="show ▼"
! The Header || remains visible
|-
| This content || is hidden
|-
| at first || load time
|}

Wiki Team/Resources

2013-11-03T22:18:07Z

Patrol: /* Advanced */

<noinclude>{{TeamHeader|Wiki Team}}
[[Category:Wiki]]
[[Category:Help]]
[[Category:Resource]]
</noinclude>

=Finding help=
For general help with Sugar, please see

'''→''' '''[[Find help]]''', and '''[[Getting Started | Getting started]]'''

'''→''' '''[[Sugar Labs/FAQ | Sugar Labs FAQ]]''', for a compilation of the team FAQs

'''→''' '''[[:Category:FAQ]]''' - an index to all FAQ pages ('''with links for new questions''')

'''→''' '''[[:Category:Help]]''', for pages tagged as 'Help'

'''→''' '''[[:Category:HowTo]]''', for pages tagged as 'HowTo'

'''→''' '''[[Service]]''' - an index to Sugar Labs infrastructure services

'''→''' '''[[Sugar_Labs/Communication channels#Forums|Community Forums]]''' - on-line forums with lots of topics

If you can't find your answer, please request one or ''supply one!''
: '''[[Request help | New Help Requests & Answers]]'''
<br>
----
=====OLPC Project and XO laptop Help and Information=====
For general help and information about the OLPC Project, please see these links at their wiki:
: [[OLPC:Official OLPC FAQ | Official OLPC FAQ]], [[OLPC:Support FAQ]], for questions about the XO laptop and its use, [[OLPC:Support]], for more support mechanisms, [[OLPC::Category:OLPC FAQ]], and [[OLPC:Ask OLPC a Question | Ask OLPC a Question]] (in roughly that order).

=Setting Wiki Preferences=
Visit your [[Special:Preferences|preferences page]] to adjust a variety of viewing and editing options for the wiki.
* If you prefer not to experience the Sugar cursors, see [[Wiki Team/Resources/Remove Sugar Cursors]].

<div style="font-size: 1.7em; background: #ffffff; padding: 0px;" align=left>'''Help on Using (building) the Sugar Labs wiki'''</div>
=Sugar Labs Wiki Guide=
The Sugar Labs wiki is a standard installation of [http://www.mediawiki.org/wiki/MediaWiki MediaWiki] software for collaborative website building.
* For a video introduction to wikis, see http://www.commoncraft.com/video/wikis.
* See also [[wikipedia:Wiki]].

See the [[Sugar Labs]] page for an overview of the organization and [[Wiki Team/Guide/Wiki Structure| wiki structure]] for how this wiki models the organization.
==Navigation==
* [[Wiki Team/Guide/Navigation | Navigation]]
* [[Wiki Team/Guide/Searching | Searching]]
* [[Wiki Team/Guide/Discussion | Discussion]]
* [[Wiki Team/Guide/Recentchanges | Recentchanges]], a [[Special:Specialpages]] that tracks page changes.
* [[Wiki Team/Guide/Allpages | Allpages]], another Special page.

==Editing==
===Basics===
* [[Wiki Team/Guide/Overview | Overview]] - A generic wiki overview
* [[Wiki Team/Guide/Page Creation|Page Creation]] - Guidance on creating pages on this wiki
* [[Wiki Team/Guide/Style Guide|Style Guide]] - Writing style and conventions that are encouraged on the wiki
* [[Wiki Team/Guide/Wiki Structure|Wiki Structure]] - Sugar Labs wiki organization
* [[Wiki Team/Guide/Editing Pages | Editing Pages]]
* [[Wiki Team/Guide/Formatting | Formatting]]
* [[Wiki Team/Guide/Links | Links]]
* [[Wiki Team/Guide/Talkpages | Talkpages]]
* [[:Category:Video Widget]] - How to embed videos
* [[:Category:Page flagging template]] - How to flag pages in special categories
* [[:Category:Highlighting template]] - How to highlight information on pages

===Intermediate===
* [[Wiki Team/Guide/Categories | Categories]]
* [[Wiki Team/Guide/Images | Images]]
* [[Wiki Team/Guide/File Upload | File Upload]]
* [[Wiki Team/Guide/Citations | Citations]]
* [[Wiki Team/Guide/User Links | User Links]]
* [[Wiki Team/Guide/Watchlist | Watchlist]]
* hover explanations, such as, <abbr title="abbreviation">abbr</abbr> are encoded like this: {{Code|<nowiki><abbr title="abbreviation">abbr</abbr></nowiki>}}

===Advanced===
*[[Special:PrefixIndex/Template:]]
*[[Wiki Team/Guide/Interwiki Linking | Interwiki Linking]]
*[[:Template:Transclude]]
*[[Wiki Team/Guide/Collapsible content|Collapsible content]]
*[[MediaWiki:Sidebar]]
*[[Wiki Team/Guide/Patrolled Edits | Patrolled Edits]]
*[[MediaWiki:Titleblacklist]]
*[[Wiki Team/Guide/Rollback | Rollback]]
*[[Wiki Team/Guide/Redirect | Redirect]]
*[[Special:AllPages | Namespace searching]] through AllPages
*[[Special:Disambiguations | Disambiguation]]
*[[wikipedia:Help:Tables]]
*[[Special:Version]]

==Guide pages==
{{Special:PrefixIndex/Wiki Team/Guide}}

==Policies==
*Create documented process for requesting sysop priv, for now model on [[OLPC:Administrators]]

Administrative privs are generally granted based on a need to use them to do "something good" for the wiki. At present, this is accomplished in a fairly informal manner, leaving a message on the [[Talk:Wiki Team/Contacts|discussion]] page or contacting one or more bureaucrats via wiki-mail would be a good place to start.

==Further Reading==
The best way to get involved in the wiki team is to monitor new content as it is added through the Recent Changes link in the Sugar Labs menu. Check to see:

* Is the new information correct?
* Is the new information in the correct place?
* Should the new information be merged with an existing page?

==Wiki Infrastructure==
* [[Service/wiki]]
* Wiki-barnraising, harmonization of familiar and useful templates, plug-ins, extensions (e.g. traclink,etc.) from OLPC wiki.
* It would be good to get some countervandalism software (bot) running. [[User:Cjl]] has done some analysis of the vandalism (and countervandalism) actions on wiki.l.o and is interested in [http://wiki.laptop.org/go/OLPC:Bot_Interest_Group coordinating an effort] that would cover both wikis with some automated countervandalism tools
===Pages under construction===
* To aid collaborators, please use the [[:Template:Under construction]] to signal that the page content is not stable and to avoid unintentional overwriting.
* [[:Category:Under construction]] will show pages in this state

===Test wikis===
: {{Highlight|'''Note:''' The following two wikis share the same page database, but have separate server configurations. Please observe http://wiki-devel.sugarlabs.org/go/Category:Under_construction before overwriting the page database.}}
* http://wiki-devel.sugarlabs.org is set up for experimentation (Installed on Sunjammer at /srv/www-sugarlabs/wiki-devel/)
* http://wiki-testing.sugarlabs.org is set up for testing (Installed on Sunjammer at /srv/www-sugarlabs/wiki-testing/)

==Synchronize plug ins and templates==
*Trac related
*Iframe
*Semantic MediaWiki

==Other Community Wikis==
Example of how other communities are using their Wikis.

* http://en.wikipedia.org/wiki/Community_portal
* https://wiki.ubuntu.com/DocumentationTeam/WikiTeam
* http://www.communitywiki.org/

User talk:FGrose/sandbox2

2013-11-03T21:59:39Z

Patrol:

{{TOCright}}
{| class="mw-collapsible mw-collapsed" data-collapsetext="hide ▲" data-expandtext="show ▼"
!align="left"| 0.84
|-
|{{Transclude|0.84/Write}}
|}
{| class="collapsible"
!align="left"| 0.86
|-
|{{Transclude|0.86/Write}}
|}

WebServices

2013-09-28T16:22:33Z

Patrol: Patrol moved page WebServices to Web Services: deCamel case

#REDIRECT [[Web Services]]

Web Services

2013-09-28T16:22:33Z

Patrol: Patrol moved page WebServices to Web Services: deCamel case

As of Sugar 0.100, there is a mechanism for using web services from Sugar.

There is new section to the Sugar Control Panel to manage online accounts and some interventions to the Sugar Journal toolbars and palettes in order to expose any installed online services, adding Copy-to and Refresh capabilities to the journal.

We have implemented three examples:
# support specific to Facebook: to share Journal entries on Facebook and to retrieve comments on those entries from Facebook (walter and rgs);
# support specific to Twitter: to share Journal entries as tweets and to retrieve comments on those entries from Twitter (tch);
# support for uploading Journal entries to a local server (tch).

We are working with community members on other extensions based on the framework and encourage other community members to work with us on additional services.

For now, web services implementations are welcome to handle their retrieval of tokens on their own. In the future we might want to delegate that to Gnome Online Accounts or a similar auth/token provider.

== Installing web services ==

We don't yet have a simple installer for web services, so for the time being:

=== Using git ===
# cd ~/.sugar/default
# git clone <MY WEBSERVICE>.git

=== Using gunzip and tar ===
# cd ~/.sugar/default
# wget <MY WEBSERVICE>
# gunzip <MY WEBSERVICE>.tar.gz
# tar xvf <MY WEBSERVICE>.tar

== Web services ==

=== Facebook ===
* tar file: [http://people.sugarlabs.org/walter/facebook.tar.gz]
* git repo: [https://github.com/walterbender/facebook]

You should end up with the following directory structure:
<pre>
~/.sugar/default/extensions/webservice/
├── __init__.py
└── facebook
   ├── __init__.py
   ├── account.py
   ├── facebook
   │   ├── __init__.py
   │   └── facebook.py
   └── icons
      ├── facebook-like-insensitive.svg
      ├── facebook-like.svg
      ├── facebook-refresh-insensitive.svg
      ├── facebook-refresh.svg
      ├── facebook-share-insensitive.svg
      └── facebook-share.svg

~/.sugar/default/extensions/cpsection/
├── __init__.py
└── webaccount
├── __init__.py
└── services
   ├── __init__.py
   └── facebook
      ├── __init__.py
      └── service.py
</pre>

Taxonomy

2011-06-01T01:47:00Z

Patrol: formatting

<noinclude>{{Translations}}</noinclude>

==Sweet: The abstract design of the experience==

''(the taste of sugar)''

Description: "Sweet" is the abstract design of the interface's appearance
and behavior, independent of any code actually implementing this design, and by extension—the learner experience.
The mockups at [[Design Team/Designs]] represent this
component's second major release, or perhaps 2.0-alpha.

==Glucose: The base Sugar environment==

''(the fundamental, simple sugar used by all life forms)''

Description: Glucose is the minimal system that must be added to a
standard GNU/Linux distribution in order to enable Activities to run. This
includes all the python code and graphics files that implement the shell,
as well as the Journal. Glucose's dependencies may include xorg-server,
xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be
marked optional by distributions. Glucose does not include any Activities
except those like the Journal that are non-optional.

==Fructose: The set of demonstration activities==

''(the main sugar in fruit, which is how we're supposed to get our sugar)''

Description: The Sugar developers will need some example set of
activities with which to demonstrate Sugar. This set is Fructose. The
packages in Fructose should be selected to make the resulting environment
as impressive as possible for a potential client or user. Packages should
therefore be stable, polished, and exercise the widest possible range of
features. Fructose may also serve as an example for people constructing
their own Activity sets.

==Sucrose: The interface, plus a set of demonstration activities==

''("table sugar", the kind you buy in the store. It consists of glucose and fructose, combined)''

Description: Sucrose consists of both Glucose and Fructose. It therefore
represents a complete example Sugar environment, ready to be installed
through a package manager. The purpose of Sucrose is so that prospective
deployers can install the "sugar-sucrose" package, and immediately say
"Wow! Look at all the cool capabilities that this system has!".

==Ribose: The operating system components developed for Sugar==

''(the sugar used by all life forms to control their hardware, in the form of RNA. It's important, but not sweet)''

Description: Ribose is the set of hardware-centric software components
that have been developed throughout this project. It includes the XO
kernels, OHM, any init-script customizations, etc. Ribose should be
construed as including all components necessary to boot the system, enough
to install Glucose if it has not yet been installed.

==Galactose: a future Sugar base designed for alternate computing forms==

''(an [[wikipedia:epimer|epimer]] of Glucose, a component of lactose, milk sugar, for the Milky Way galaxy of computing forms searching for something sweet)''

Description: A hypothetical new Sugar variation that begins to support Learner collaboration with the super nova of new computing forms, especially the [[wikipedia:Template:Mobile_operating_systems|mobile operating systems]], such as, [[wikipedia:Android_(operating_system)#Linux_compatibility|Android]], [[wikipedia:WebOS#Platform|webOS]], [[wikipedia:MeeGo#Technical_foundations|MeeGo]], [[wikipedia:IOS_(Apple)#Development|iOS]], [[wikipedia:Windows_Phone_7#Development|Phone 7]], etc. There is trend towards ubiquitous computing that inspires Learners to great expectations. It will require us to develop clever new [[wikipedia:Monosaccharide_nomenclature|aldoses]], like our XO's Ribose, to meet our children's demand for seamless collaboration without discrimination in their [[wikipedia:J._C._R._Licklider#Global_computer_network |Galactic Neighborhood]].

: See these threads: [http://www.mail-archive.com/fonc@vpri.org/msg01775.html Fundamentals of New Computing] & [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg10877.html It's An Education Project (For Sugar Everywhere, ...)]

==Starch(es): A complete disk image for Sugar==

''(starch is composed of multiple sugars bonded together)''

Description: We often distribute complete disk images for Sugar, ready to
boot. These images are composed of multiple elements of the above stack.

Each image series should be named separately, to minimize
confusion. For cutesy codenames, we could have a development build
("glycogen", a starch used to produce Glucose) and a stable build
("cellulose", an extremely stable starch).
* In July 2010, Paraguay Educa chose the name '''[[Dextrose|Dextrose]]''' (approximately acronymized from "DEployments' Xo OS") for their release of Sugar 0.88 on Fedora 11 for XO laptops ([http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01213.html announcement]). The molecule [[wikipedia:Dextrose|Dextrose]] is the dextrorotatory form of glucose or D-glucose, the sugar in blood and other living systems. So, it represents a vital infusion for the project.

== The SUGAR stack: ==

[[Image:Sugar Taxonomy.png|400px]]


*''Note: See discussion for details about the OS/Ribose stacking''

*Current implementations of Sugar elements can be found at [[Supported systems]]

==Deepening the concept==

===Honey: activities developed by 'in the wild' vendors===

''a sweet fluid made by bees, mostly Fructose''

Description: Activities that are packaged by outside developers, sometimes ports of activities to Sugar from other OS. It might enhance Sugar and the Sweet experience, but "honey frequently contains dormant endospores of the bacterium Clostridium botulinum, which can be dangerous to infants" [http://en.wikipedia.org/wiki/Honey Wikipedia].
~ For example, Skype, printer capability, IM software
: as a former beekeeper I can tell you that not all honey is organic, though we all wish it were so (antibiotics taint a lot of it, especially in developing countries) [[User:Yamaplos|Yamaplos]] 15:04, 17 May 2008 (UTC)

==One-liners==

* Lead acetate: An implementation of Sweet on Windows. Sweeter than sugar, but [http://www.healthychildrenproject.org/pdf/PPLEAD.pdf toxic to young brains].
* ''[http://en.wikipedia.org/wiki/Aspartame_controversy aspartame] - once thought better than sugar, but possibly connected with brain tumors''<sub>[[User:Morgs|Morgs]] 11:44, 17 May 2008 (UTC)</sub>
* ''So you're saying Sugar is now suite? ''<sub>Kevin Cole</sub>
* ''Caramel: a "feature freeze" on Sucrose''
* ''Diabetic OS: an OS that cannot handle Sugar yet'' <sub>Yama Ploskonka</sub>
* ''Molasses: a beta, unfinished release of Sugar''
* ''High Fructose Corn Syrup: Apparently similar, but made of patented materials'' <sub>Morgan Collett</sub>
* ''How sweet it is!'' <sub>Jackie Gleason</sub>
* ''Insulin: what Microsoft needs to make Sugar go away.'' <sub>davewa</sub>

== Glossary ==

See [[Glossary]].

Taxonomy

2011-06-01T01:38:22Z

Patrol: /* Galactose: a future Sugar base designed for alternate computing forms */

<noinclude>{{Translations}}</noinclude>

==Sweet: The abstract design of the experience==

''(the taste of sugar)''

Description: "Sweet" is the abstract design of the interface's appearance
and behavior, independent of any code actually implementing this design, and by extension—the learner experience.
The mockups at [[Design Team/Designs]] represent this
component's second major release, or perhaps 2.0-alpha.

==Glucose: The base Sugar environment==

''(the fundamental, simple sugar used by all life forms)''

Description: Glucose is the minimal system that must be added to a
standard GNU/Linux distribution in order to enable Activities to run. This
includes all the python code and graphics files that implement the shell,
as well as the Journal. Glucose's dependencies may include xorg-server,
xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be
marked optional by distributions. Glucose does not include any Activities
except those like the Journal that are non-optional.

==Fructose: The set of demonstration activities==

''(the main sugar in fruit, which is how we're supposed to get our sugar)''

Description: The Sugar developers will need some example set of
activities with which to demonstrate Sugar. This set is Fructose. The
packages in Fructose should be selected to make the resulting environment
as impressive as possible for a potential client or user. Packages should
therefore be stable, polished, and exercise the widest possible range of
features. Fructose may also serve as an example for people constructing
their own Activity sets.

==Sucrose: The interface, plus a set of demonstration activities==

''("table sugar", the kind you buy in the store. It consists of glucose and fructose, combined)''

Description: Sucrose consists of both Glucose and Fructose. It therefore
represents a complete example Sugar environment, ready to be installed
through a package manager. The purpose of Sucrose is so that prospective
deployers can install the "sugar-sucrose" package, and immediately say
"Wow! Look at all the cool capabilities that this system has!".

==Ribose: The operating system components developed for Sugar==

''(the sugar used by all life forms to control their hardware, in the form of RNA. It's important, but not sweet)''

Description: Ribose is the set of hardware-centric software components
that have been developed throughout this project. It includes the XO
kernels, OHM, any init-script customizations, etc. Ribose should be
construed as including all components necessary to boot the system, enough
to install Glucose if it has not yet been installed.

==Galactose: a future Sugar base designed for alternate computing forms==

''(an [[wikipedia:epimer|epimer]] of Glucose, a component of lactose, milk sugar, for the Milky Way galaxy of computing forms searching for something sweet)''

Description: A hypothetical new Sugar variation that begins to support Learner collaboration with the super nova of new computing forms, especially the [[wikipedia:Template:Mobile_operating_systems|mobile operating systems]], such as, [[wikipedia:Android_(operating_system)#Linux_compatibility|Android]], [[wikipedia:WebOS#Platform|webOS]], [[wikipedia:MeeGo#Technical_foundations|MeeGo]], [[wikipedia:IOS_(Apple)#Development|iOS]], [[wikipedia:Windows_Phone_7#Development|Phone 7]], etc. There is trend towards ubiquitous computing that inspires Learners to great expectations. It will require us to develop clever new [[wikipedia:Monosaccharide_nomenclature|aldoses]], like our XO's Ribose, to meet our children's demand for seamless collaboration without discrimination in their [[wikipedia:J._C._R._Licklider#Global_computer_network |Galactic Neighborhood]].

: See these threads: [http://www.mail-archive.com/fonc@vpri.org/msg01775.html Fundamentals of New Computing] & [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg10877.html It's An Education Project (For Sugar Everywhere, ...)]

==Starch(es): A complete disk image for Sugar==

''(starch is composed of multiple sugars bonded together)''

Description: We often distribute complete disk images for Sugar, ready to
boot. These images are composed of multiple elements of the above stack.
Each image series should be named separately, to minimize
confusion. For cutesy codenames, we could have a development build
("glycogen", a starch used to produce Glucose) and a stable build
("cellulose", an extremely stable starch).
* In July 2010, Paraguay Educa chose the name '''[[Dextrose|Dextrose]]''' (approximately acronymized from "DEployments' Xo OS") for their release of Sugar 0.88 on Fedora 11 for XO laptops ([http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01213.html announcement]). The molecule [[wikipedia:Dextrose|Dextrose]] is the dextrorotatory form of glucose or D-glucose, the sugar in blood and other living systems. So, it represents a vital infusion for the project.

== The SUGAR stack: ==

[[Image:Sugar Taxonomy.png|400px]]


*''Note: See discussion for details about the OS/Ribose stacking''

*Current implementations of Sugar elements can be found at [[Supported systems]]

==Deepening the concept==

===Honey: activities developed by 'in the wild' vendors===

''a sweet fluid made by bees, mostly Fructose''

Description: Activities that are packaged by outside developers, sometimes ports of activities to Sugar from other OS. It might enhance Sugar and the Sweet experience, but "honey frequently contains dormant endospores of the bacterium Clostridium botulinum, which can be dangerous to infants" [http://en.wikipedia.org/wiki/Honey Wikipedia].
~ For example, Skype, printer capability, IM software
: as a former beekeeper I can tell you that not all honey is organic, though we all wish it were so (antibiotics taint a lot of it, especially in developing countries) [[User:Yamaplos|Yamaplos]] 15:04, 17 May 2008 (UTC)

==One-liners==

* Lead acetate: An implementation of Sweet on Windows. Sweeter than sugar, but [http://www.healthychildrenproject.org/pdf/PPLEAD.pdf toxic to young brains].
* ''[http://en.wikipedia.org/wiki/Aspartame_controversy aspartame] - once thought better than sugar, but possibly connected with brain tumors''<sub>[[User:Morgs|Morgs]] 11:44, 17 May 2008 (UTC)</sub>
* ''So you're saying Sugar is now suite? ''<sub>Kevin Cole</sub>
* ''Caramel: a "feature freeze" on Sucrose''
* ''Diabetic OS: an OS that cannot handle Sugar yet'' <sub>Yama Ploskonka</sub>
* ''Molasses: a beta, unfinished release of Sugar''
* ''High Fructose Corn Syrup: Apparently similar, but made of patented materials'' <sub>Morgan Collett</sub>
* ''How sweet it is!'' <sub>Jackie Gleason</sub>
* ''Insulin: what Microsoft needs to make Sugar go away.'' <sub>davewa</sub>

== Glossary ==

See [[Glossary]].

Sugar on a Stick

2011-05-29T04:41:51Z

Patrol: Reverted edits by Milkya (talk) to last revision by FGrose

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

== What is Sugar on a Stick? ==

{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickMirabelle.png |300px|left|link=http://spins.fedoraproject.org/soas]]
| style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [http://fedoraproject.org Fedora-based] [[wikipedia:Live USB|Live USB]] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]] and designed to fit on an ordinary USB thumbdrive ("stick"). Learn more about [http://spins.fedoraproject.org/soas/#home the project] and the [http://spins.fedoraproject.org/soas/#about principles] behind it at our [http://spins.fedoraproject.org/soas Spin webpage]. The most recent version is version 4, code-named '''[[Sugar on a Stick/Mango Lassi|Mango Lassi]]''' and was released on '''November 2, 2010.'''

'''Turn your computer into a Sugar on a Stick Creation Station:''' A related project is the [[Sugar Creation Kit]], a downloadable DVD which includes the materials you need to create Mango Lassi sticks and install additional Activities on it, along with documentation and previous versions of Sugar on a Stick.
|}
You can purchase Sugar on a Stick pre-installed in a branded USB flash drive from [http://on-disk.com/product_info.php/products_id/908 On-Disk] for $26.99.

{{Highlight|'''Note''': This site is not detailing (as of 15 May 2011) the version of Sugar on a Stick that they will supply, so be advised to confirm this before you order.}}

__NOTOC__

=== Want to use Sugar on a Stick? ===

{|
|-
| rowspan="3" style="border: 0; border-width: 0; width: 350px;" | [[File:Cici-maze.jpg |300px|left|link=http://spins.fedoraproject.org/soas]]
|-
|
|style="border: 0; border-width: 0;" align="center" | <span class="linkgroup">[[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]</span>
|-
|
|If you'd like to try out Sugar on a Stick, check out the [http://spins.fedoraproject.org/soas Sugar on a Stick Spin Page] - it's where our software downloads, usage instructions, and support information lives. You will also need the [[Sugar on a Stick/Installation|installation instructions]].

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

{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]
| style="border: 0; border-width: 0;" |
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. 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]].

== 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, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].

=== Get Activities on the Stick ===

{|
|-
| style="border: 0; border-width: 0;" |

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:

* [[Sugar on a Stick QA|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, [[How to file a ticket|file a ticket!]] ''No technical experience required.''
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''
* [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 [[SoaS 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.''
* 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]].

| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]
|}

=== Get Sticks into Schools ===

{|
|-
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]
| style="border: 0; border-width: 0;" |
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 [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ 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 [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|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 [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ 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 [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.
|}

=== Get Contributors ===

{|
|-
| style="border: 0; border-width: 0;" |

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]]/
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.
* [http://lists.sugarlabs.org/listinfo/soas 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: [http://webchat.freenode.net?channels=sugar #sugar]. This is where the [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity] starts off. Help new joiners past initial questions and provide instant help!

| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]
|}

== What's happening? ==

=== Meetings ===

We have weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings. Attending a meeting is a great way for newcomers to get started.

=== Release schedule ===

Our release schedule is based on the [[fedora:Releases/Schedule | Fedora release schedule]]. The most recent release was v.4, code-named '''[[Sugar on a Stick/Mango Lassi|Mango Lassi]]''', shipped on '''November 2, 2010''' and based on the Fedora 14 release schedule. The next Sugar on a Stick version will be based on the [[fedora:Releases/15/Schedule | Fedora 15 release schedule]].

{|border="1" cellspacing="0" width="100%"
|-
|rowspan="2"| 2010-11-01 || Sugar on a Stick v.4.0 Mango Lassi released
|-
| Planning & Development Begins
|-
| 2010-07-27 || Feature Freeze (all features have to be ''approved'' and in a satisfying state.)
|-
| 2010-08-03 || Alpha Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)
|-
| 2010-08-17 || Alpha Release
|-
| 2010-09-07 || Beta Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)
|-
| 2010-09-21 || Beta Release
|-
| 2010-10-12 || Final Freeze (all changes have to be ''pushed''. no further changes permitted.)
|-
| 2010-10-14 || Compose Release Candidate
|-
| 2010-11-01 || Sugar on a Stick v.4.0 Final Release
|-
|}

=== Contributor stories ===

To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].

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

* [[Talk:Sugar_Creation_Kit#Introduction_to_Soas-v3_Mirabelle|Introduction to SoaS]]
* [[Sugar_on_a_Stick/Installation/Variations#SugarCreationKit_DVD|SugarCreationKit DVD]] - Complete DVD containing all the resources required to create all 3 versions of Sugar-on-a-Stick without requiring Internet access
* Other [[:Category:Live USB|portable Sugar distributions]] - Live USB work 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 subpage index ==
{{Show|Earlier versions of Sugar on a Stick can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick}}}}

: Fedora wiki: : https://fedoraproject.org/wiki/Sugar_on_a_Stick

*[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Linux/openSUSE#openSUSE_Sugar-Desktop_on_a_stick openSUSE_Sugar-Desktop_on_a_stick]

Activities

2011-04-05T16:28:20Z

Patrol: Reverted edits by Maxgriber (talk) to last revision by Walter

<noinclude>{{Translations}}{{TOCright}}</noinclude>
== Learners ==
(Sugar users are '''learners'''.)

Learner applications in Sugar are called '''[[Human Interface Guidelines/Activities | Activities]]'''. They are software packages that automatically save your work—producing specific instances of the Activity that can be resumed at a later time. A specific Activity instance is a [[Human_Interface_Guidelines/The_Laptop_Experience/The_Journal| Journal]] event (see this discussion of [[Human_Interface_Guidelines/The_Laptop_Experience/The_Journal#The_Notion of "Keeping"|The Notion of "Keeping"]]). Many Activities support learner [[Collaboration|collaboration]], where multiple learners may be invited to join a collective Activity session.

Please see the [http://activities.sugarlabs.org Sugar Activity Library] for a nearly complete list of activities which are available for Sugar.
===[[Activity Team/FAQ | Questions]]===
The [[Activity Team]]'s [[Activity Team/FAQ]] has many developer-oriented questions, but Sugar Learners should post their general Activity-related questions to the team [[Talk:Activity Team/FAQ |at this page]]. Questions about a specific Activity should be posted on the discussion page for that Activity available below.
== Developers ==
Please see the [[Activity Team]] for developer information.

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

=== Native Sugar Activities ===
See [[:Category:Activities]] for wiki pages of actual activities.

Below is a list of activity developer pages.
{{Special:PrefixIndex/{{PAGENAME}}/}}

=== Running GNU/Linux Applications Under Sugar ===

There are two ways to run GNU/Linux applications as Activities under Sugar (meaning you don't need to use Terminal to load them):
*'''Sugar Coating''' - Making Linux apps run under Sugar, but not modifying them to take advantage of Sugar's collaborative capabilities
*'''Sugarizing''' - A fully integrated Linux application, re-engineered to take advantage of Sugar's advanced collaboration abilities
*: See these instructions: How to sugarize an application: [http://people.sugarlabs.org/Tgillard/sugarize/wiki-sugarize.txt]
==== Sugar Coating Activities ====

To run Linux apps under Sugar (''i.e.'', making them to run in the Sugar interface, without the collaboration and other Sugar integration programmed into them), read these instructions on [[Running Linux Applications Under Sugar]].

In the future, we hope that Sugar will be able to run Linux applications natively without these steps.

==== Sugarizing Activities ====

See [[Activity Team]] for information on porting regular applications to run as native Sugar Activities.

===Useful GNU/Linux Applications===

====VLC Media Player====
The VLC media player is a highly portable multimedia player for various audio and video formats (MPEG-1, MPEG-2, MPEG-4, DivX, mp3, flv, avi, ogg, ...) as well as DVDs, VCDs, and various streaming protocols. It can also be used as a server to stream in unicast or multicast in IPv4 or IPv6 on a high-bandwidth network.; the VLC Player is considered to be better by some users then MPlayer because it offer more settings, options and features. There is also no need to run it from Terminal. Read [[Activities/VLC]] to learn how to install it.

====Seamonkey====
SeaMonkey has inherited the successful all-in-one concept of the original Netscape Communicator and continues that product line based on the modern, cross-platform architecture provided by the Mozilla project.

* The Internet browser at the core of the SeaMonkey suite uses the same rendering engine as its sibling Mozilla Firefox, with popular features like tabbed browsing, popup blocking, find as you type and a lot of other functionality for a smooth web experience.
* SeaMonkey's Mail and Newsgroups client shares lots of code with Mozilla Thunderbird and features adaptive Junk mail filtering, labels and mail views, multiple accounts, S/MIME, address books with LDAP support and is ready for both private and corporate use.
* Additonal components include an easy-to-use HTML Editor, the ChatZilla IRC chat application and web development tools like a DOM Inspector and a JavaScript debugger.
* If that's still not enough, SeaMonkey can be extended with numerous Add-Ons that provide additional functionality and customization for a complete Internet experience.

Seamonkey can be Sugar-coated.

====Midnight Commander====
Midnight Commander is a text-mode file manager and visual command shell. It is easily Sugar-coated for access from the Activities panel. [http://www.ibiblio.org/mc/images/mc-panels.png Screenshot] You can also run it directly in Terminal. ([http://www.research-service.com Paper Writers])

====Totem Media Player====
The Totem media player is already installed in the OLPC XO-1. It is the engine that supports media on the system. Out of the box it does not support MP3 music or MPEG-4 video. A free driver can be downloaded to add MP3 compatability. A Sugar-coating can be applied to easily access the program from the Activities panel.

====[http://tux4kids.alioth.debian.org/ Tux4Kids]====
;TuxType2: [http://tuxtype.sourceforge.net/ TuxType] is a touch typing tutorial/game than can be installed on the OLPC XO-1 using the yum command. A Sugar-coating can be applied to easily access the program from the Activities panel.
;TuxMath: [http://tux4kids.alioth.debian.org/tuxmath.php TuxMath] is an arcade game that helps kids practice their math facts. A Sugar-coating can be applied to easily access the program from the Activities panel.
;TuxPaint: [http://www.tuxpaint.org/ Tux Paint] is a drawing program for children ages 3 to 12. It combines an easy-to-use interface, fun sound effects, and an encouraging cartoon mascot who guides children as they use the program. A Sugar-coating can be applied to easily access the program from the Activities panel.

-----

(Let's try to organize this page based on some criteria of completion as per the discussion in [[Talk:{{PAGENAME}}]].)
[[Category:Activity Team]]

Features/New Toolbar Design

2011-03-10T19:34:29Z

Patrol: /* Documentation */

<noinclude>{{GoogleTrans-en}}{{TOCright}}
[[Category:Feature|New Toolbar Design]]
[[Category:Feature Accepted 0.86]]</noinclude>





== Summary ==
Redesign the activity toolbar to not use tabs and use toolbar buttons that can reveal secondary functionality instead.

== Owner ==

* Name: [[User:alsroot| Aleksey Lim]]
* Email: [[Special:Emailuser/alsroot|send an email]]

== Current status ==
* Targeted release: 0.86
* Last updated: 19 Sep 2009
* Percentage of completion: 100%

== Detailed Description ==

sugar.graphics.toolbar module consists of 2 widgets:
* ''Toolbar'' main widget which represents toolbar itself
* ''ToolbarButton'' tool button to insert to ''Toolbar'', which could be expanded to sub-widget

NOTE: Toolbar was designed to have only one level of sub-widgets.

==== Toolbar ====

sugar.graphics.toolbar.Toolbar extends gtk.VBox:
* ''top'' property to access to gtk.Toolbar interface
* ''padding'' horizontal padding for ''top'' toolbar and all sub-widgets
* ''modify_bg'' method to modify background color of toolbar itself and all sub-widgets

==== ToolbarButton ====

sugar.graphics.toolbar.ToolbarButton extends sugar.graphics.toolbutton.ToolButton:
* ''toolbar'' RO property, if parent of button is sugar.graphics.toolbar.Toolbar
* ''page'' RW GObject property, sub-widget to expand
* ''expanded'' RW property, if ''page'' expanded

If sugar.graphics.toolbar.Toolbar.palette property wasn't set manually it will contain palette with ''page''.

==== Example ====

from sugar.graphics.toolbar import Toolbar, ToolbarButton

toolbar = Toolbar()

tollbarbutton_1 = ToolbarButton(
page=gtk.Button('sub-widget #1'),
icon_name='computer-xo')
toolbar.top.insert(tollbarbutton_1, -1)

tollbarbutton_2 = ToolbarButton(
page=gtk.Button('sub-widget #2'),
icon_name='button_cancel',
tooltip='with custom palette instead of sub-widget')
toolbar.top.insert(tollbarbutton_2, -1)

== Benefit to Sugar ==

Make process of switching between toolbars more clear, use tool buttons that are showing all the time (in main toolbar), i.e., having Close/Help buttons visible all the time could be very useful.

== Scope ==

* implementation in sugar-toolkit
* provide API in sugar.activity.activity for new toolbars

One option for new API is supporting bunch of methods to create most useful toolitems/sub-toolbars. (see [http://git.sugarlabs.org/projects/write/repos/toolbars/blobs/master/AbiWordActivity.py#line58] for example usage).
* ''activity.toolbar()'' toolbutton with activity sub-toolbar
* ''activity.stop_button()''
* ''activity.undo_button()''
* ''activity.redo_button()''
* ''activity.copy_button()''
* ''activity.paste_button()''

=== Implementation ===

* [http://git.sugarlabs.org/projects/sugar-toolkit/repos/toolbars sugar-toolkit]
* Example implementation in [http://git.sugarlabs.org/projects/write/repos/toolbars Write]
* Example implementation in [http://git.sugarlabs.org/projects/terminal/repos/toolbars Terminal]
* Example implementation in [http://git.sugarlabs.org/projects/log/repos/toolbars Log]
* Example implementation in [http://git.sugarlabs.org/projects/read/repos/toolbars Read]

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''

== Dependencies ==

* only sugar-toolkit

== Contingency Plan ==

None necessary, revert to previous release behaviour.

== Documentation ==
Gary's [[Design_Team/Proposals/Toolbars/Activity-wide_Toolbar_mock-ups]] proposal.
Eben's initial [[Design Team/Designs/Toolbars]] mockups.

== Release Notes ==
''Solution for the stop activity issue, pointed out at http://dev.sugarlabs.org/ticket/452''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Submit Bugs/Problems

2011-03-09T07:12:35Z

Patrol: Reverted edits by Alice-thomas222 (talk) to last revision by FGrose

__TOC__

<big>'''Please Describe Bugs & Problems Here'''</big>
* Communicate directly with the [[Development Team]]'s work ticket system by using the [http://bugs.sugarlabs.org Sugar Labs '''trac''' instance] to report bugs you find with Sugar on the various distributions.
* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.
{{Iframe|     → Click the [show ▼] link to see recent ticket activity:
|http://bugs.sugarlabs.org/timeline|900|500|1}}
* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.
* In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem.
: See [[BugSquad/Bug Report]] for reporting guidance.
: You may also [[Sugar_on_a_Stick/Getting_Involved/Testing#Report_your_hardware_profile| report your hardware profile]] and upload log files as described in [[BugSquad/Get Logs]].
* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.

Email sent to feedback AT sugarlabs.org will be forwarded to the IAEP mailing list, which is used for general discussion of the Sugar Labs education project.

===Journal comes and goes===
Sugar on Ubuntu doesn't always preserve the Journal between sessions.
:It seems that the index is occasionally broken and the datastore is thus copied to a timestamped entry in .sugar/default/ and empty datastore is opened.
::Is this still a problem with 0.84? If so, could you [http://trac.sugarlabs.org please file a ticket]?

===.84 sugar===
Apps won't load in Fedora 11 emulating sugar under root.
Video of behavior: http://www.youtube.com/watch?v=1Lvvjvi3yE0
===Colors on Ubuntu===
The Colors activity canvas is only half the width of the screen and the aspect ratio is compressed.
:This bug is being tracked in [http://trac.sugarlabs.org/ticket/592 Ticket 592]

===Turtle Art===
Turtle Art on a non-1200x900 screen doesn't scale display.
:Resolved since Version 17.

===Hover menus from the Frame on Ubuntu===
They appear in the upper-left corner.
:Resolved in 0.84

===Can't Shutdown Sugar Spin===
I am using the Sugar Spin on a CD and nothing happens when I click on shutdown.
:The Sugar LiveCD and LiveUSB releases are going through a lot of testing and newer versions are more reliable. Please try again at [[Downloads]].

===WPA/WEP Connectivity Problems===

Hi I still have problems connecting to WPA, even with build 703 installed. I enter a password and nothing happens. Any advice?
:Hmmm. This one falls between the crack of Sugar and the OLPC network stack. Have you asked for help from the OLPC support team? --[[User:Walter|Walter]] 19:57, 22 May 2008 (UTC)
::Looks like a place where more feedback should be given in the UI. Any concrete ideas? [[User:Tomeu|Tomeu]] 09:31, 23 May 2008 (UTC)

No, I haven't. Maybe we should explain what questions should go to OLPC team and what goes here.
:Good point. --[[User:Walter|Walter]] 20:15, 22 May 2008 (UTC)

===UI Element sizes===
This is more of an issue than a bug. But I don't know where else to put it for now.

As Sugar is ported to other systems, they will have screens with dimensions significantly different than the XO laptop. On the XO the assumption is made of 1200 x 900 pix, with Sugar occupying a grid of 12 x 16 elements 75 pixels square.

How will we deal with issues like screens in other aspect ratios, or where the 75-pixel element is not a practical size?
[[User:Rmyers|Rmyers]] 20:51, 22 May 2008 (UTC)

:Much of this is ameliorated by the extensive use of SVG for the graphics. --[[User:Walter|Walter]] 21:10, 22 May 2008 (UTC)
:There is active development on this issue. See, for example, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg02712.html. --[[User:FGrose|FGrose]] 04:56, 20 March 2009 (UTC)

===Sonata===

I cannot access MP3 files I transfer to my SD card through Sonata. It does not let me select source directories/devices. Any advice? Is there a better player for Sugar/XO?
:perhaps you'll have better luck with [http://activities.sugarlabs.org/en-US/sugar/addon/4045 Jukebox]? If not, please [http://dev.sugarlabs.org file a bug report]

[[Category:General public]]

===Login fail on Fedora 9===

I have sugar installed on Fedora 9. The first session I start allows me to give my name and choose my colour. After that the session aborts with no further communication. Every subsequent session aborts with no error message. The only useful looking message is in the .xsession-errors file and looks like this.

*** PULSEAUDIO: Unable to connect: Connection refused
*** Is your sound server running?
*** See: http://www.pulseaudio.org/wiki/Troubleshooting

** (sugar-shell:12977): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion `GST_IS_MIXER (self->obj)' failed

I checked over the fedora bug tracker and found some missing dependencies mentioned, but those were all installed (e.g. gstreamer). When doing this I was using a second X session to my main one, but previously I have had the same problem in the main X session. Any suggestions?

:I'll see if someone from the Fedora team can offer some help. --[[User:Walter|Walter]] 22:49, 21 September 2008 (UTC)
::What I have learned so far (from Marco)
::The Fedora 9 packages are basically untested :( Rawhide is getting much better. Perhaps we should spend a bit of time one of these days and push the latest packages in Fedora 9.
::There is a sugar component on http://bugzilla.redhat.com which can be used for distribution specific issues. Upstream issues should be reported to dev.laptop.org. Yeah, it can be hard/impossible for the user to know if it's distribution or upstream. I suggest to always give priority to upstream when unsure. --[[User:Walter|Walter]] 12:57, 22 September 2008 (UTC)
::This resolved in the F11 release. --[[User:Walter|Walter]] 13:54, 20 March 2009 (UTC)

===XOlympics activity fails if python-elements package installed on Fedora 12===

XOlympics uses a custom local "elements" module, but if python-elements is installed, XOlympics can't find box2d because it looks it finds the site-wide elements module first. The Physics activity seems to require that python-elements is installed, so the only workaround I found was to add:

import sys
sys.path.insert(0, ".")

to the top of "XOlympics.activity/tools.py"

--[[User:DeanBrettle|DeanBrettle]] 13:12, 6 February 2010

Request New Features

2011-03-09T07:11:58Z

Patrol: Reverted edits by Alice-thomas222 (talk) to last revision by FGrose

<noinclude>[[Category:Wish list]]

'''Please describe new feature requests by one of the methods below:'''

'''Note:''' We periodically review these requests, generating ''enhancement tickets'' in [http://bugs.sugarlabs.org our tracking system].
* Developers: please continue to file feature requests directly in the [http://bugs.sugarlabs.org tracking system] and develop proposals through the [[Features/Policy]] process.
* You may edit this and other pages of the wiki.
* See also [[Wish list]] and [[:Category:Wish list]].
</noinclude>

== Change default Mesh settings for greater security ==
We were very excited to try Sugar on a Stick (Mirabelle). However, I was very surprised to find lots of users with whom I could "make friends," some of whom seemed to have included their real names (given name and surname!).

It took some digging in this Wiki to find out that I just had to delete the Mesh entry (i.e., the reference to jabber.sugarlabs.org) so that only Sugar users on our Wi-Fi would show up.

There may be a genuine security concern here. We simply have no way of knowing who the other users are with whom a child can "make friends." All it would take is for one bad thing to happen for the Sugar project to suffer.

While we love the idea of children from all over the world collaborating on-line, perhaps pragmatic concerns about the security of all children should lead us, at the very least, to have the default setting on the Mesh entry as a blank. Parents and teachers will then be responsible for enabling this feature, if they so wish.
: This request has been posted to the Sugar developers mailing list at http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024190.html. You may want to watch or participate in the discussion there. --[[User:FGrose|FGrose]] 14:09, 26 May 2010 (EDT)

== Maintain applications throughout updates ==
I am running Joyride updates and really am liking the newest versions. However, it drives me crazy that some user data is maintained (ie, friends) but other data, such as applications I install, are obliterated. This is a really serious issue in terms of the viability of this OS. Can something be done? -- [[User:Graham|Graham]]

:Unfortunately, OLPC is no longer maintaining the Joyride builds, so to some extent, this request is no longer something we can address. But <code>olpc-update</code> should preserve any activities you have installed in /home/olpc/Activities.

==easier bug reporting==
I am very impressed with KDE's bug reporting mechanism and as well Ubuntu's. I think it would be of great assistance to users and coders if there was an automatic error detection and prompt for reporting the bug. I've made [http://www.youtube.com/watch?v=BbUmk8Rk80c a video of the KDE bug reporting experience] which is exceptionally easy and user friendly... and if for no other reason kids will be using Sugar, so Sugar should be kid easy for bug reporting.--[[User:Dennis Daniels|Dennis Daniels]] 00:05, 11 August 2009 (UTC)

== OS Updates ==

It would be great if there was a Sugar OS auto-update tool in the Sugar interface (or a graphical control panel, as detailed below) to make keeping up-to-date easy.

:This feature is being tracked in [http://trac.sugarlabs.org/ticket/105 Ticket #105].

==Download Page==

If this wiki is the go to place for all things Sugar related then you need a download page with installation instructions and a getting started guide linked prominently from the front page.

This should have details for downloading sugar packages to install on top of lots of different OSs (even Windows!) as well Live CD images. That way folks like me with little programming experience can try before they buy, can help with tasks like translation, documentation.
:See [[Downloads]].

==Python tutorial==

I get the impression that python is central to sugar. How about a page of general Python resources. Basic tutorials Sugar customisation info etc.[[Special:Contributions/81.187.181.168|81.187.181.168]] 10:35, 28 June 2008 (UTC)

:See the [[Activity_Team/Resources#Python_Reference_.26_Tutorials|Python tutorial list]]

== File System ==

I love the Journal function. It's great. But it's near impossible to store and find files in Sugar, and name/locate files on other devices. We need a drag & drop system, and the ability to move files between storage devices easily. Give people the choice of either (Journal is very handy to track activity and, similar to the _open recent_ function in many OS X/Windows apps, lets you find recent stuff easily. I think this needs to be a new icon on the home view, alongside journal, and when you access it, or Journal, it's intuitive and easy to move between either view.

:The new journal design call for some of what you described above: http://wiki.laptop.org/go/Designs#Journal [[User:Tomeu|Tomeu]] 10:47, 23 May 2008 (UTC)

Yes, it's better. But I still want to see the files I have created/saved in a list, by storage device. File name. Type. Size. Date last used.

I recently gave my 4 year old an OX and it has been interesting working through things with her. On problem I have with the file system is highlighted when using the memory game, I want to open a game we created earlier, fine but the journal opens and shows everything not just things that can be opened by that activity making it very hard to find stuff.

:The [[Development_Team/Release/Releases/Sucrose/0.84#Journal|Journal in v0.84]] has a number of features that may help, including the ability to search for starred items (★) and by activity type. Also, the new [[Development_Team/Release/Releases/Sucrose/0.84#Resume_Activity|Resume feature]] should reduce "Journal spam".

== Usability ==
7/18/2008

I've been writing an activity on an XO using only XO resources. After all, the target community members are people for whom the XO is the only computer to which they have access. If you realistically want to serve that community, you have to walk a mile in their shoes.

I have had some success, but there are many frustrations, the Journal interface being the most egregious. Some notable troubles:

* I spend an inordinate amount of time deleting Journal clutter. It should be possible to turn automatic logging off, since not all activity will necessarily be worth tracking. Better yet, include a GUI for setting filter options for what will be logged, and what will not be logged.
::We took [[Development_Team/Release/Releases/Sucrose/0.84#Resume_Activity|a different approach]] to the Journal spam issue.

* The flat file display of directories on USB or SD devices also clutters the Journal. Especially annoying is when a complete web page is saved on another computer and viewed on an XO (for example tutorial information about the XO). The detail data in the subdirectory makes it hard to find the root HTML file to view the page. Moreover, as nearly as I can tell, it is not possible to save a complete web page using only the XO. Something is saved, but it displays incorrectly when viewed later. This is of fundamental importance for areas with little or unreliable internet service. A child finds something at school, he saves it so he can read it later at home where there is no internet, and what he gets is some partially readable glop.
::This feature request is being tracked in [http://trac.sugarlabs.org/ticket/584 Ticket 584].

* The OLPC developers guide extols the Journal as a replacement for file hierarchies, and suggests that such hierarchies are unnatural. This is not true: containers are very intuitive, especially for children. Even in the most primitive hut, there is an area for cooking, which contains a larder which contains food items. The cooking area also contains a storage area for utensils and an area for food preparation. The hut itself contains a sleeping area, a cooking area, a latrine area and a social area, even if it is only one room. Moreover, the hut is contained in a community, itself contained in a nation. To assert that hierarchical organization is unnatural borders on blind hubris. Hierarchical organization of information is no exception: bearing witness are the containers library, collection, shelf, volume, and page within the volume. Indeed, the entire internet, the new global library, is intrinsically and irretrievably hierarchical. Depriving children of these fundamental organizational tools is tantamount to crippling them.
::Arguably this request is overstated–"crippling them"–but [http://trac.sugarlabs.org/ticket/584 Ticket 584] presumably will address this.

* With reference to the previous point, it would be nice to have something like the triangle by directories on Macs, or in the example listings in pippy: click on the triangle, and the contained information is toggled between hidden and expanded states. A child could create a container in the Journal, and drag different Journal entries into it to organize the log of his activities according to his own choosing, and then click on the triangle to hide those that are distracting to the activity at hand. This is conceptually no different than putting toys away in a toy box, and it ''is'' perfectly natural to all human beings, children or otherwise. Moreover, this functionality is already present, but only for 'hard' containers like USB and SD devices. Is it such a stretch to allow 'soft' user created containers as journal entries?
::See above.

* I have discovered that a journal entry is really a saving of the state of an activity comprising data, activity, view state (not always restored properly), etc. This notion of a saved state that may be identically resumed is very good, and very convenient, when it has been fully implemented by an activity. It should extend to power cycles. When I turn the machine back on, all my running activities should be resumed and the clipboard should have all my clips, and the machine view should be restored to the most recent active activity before power cycling.
::This feature request is being tracked in [http://trac.sugarlabs.org/ticket/585 Ticket 585].

* With reference to the previous point, this distinction between what a journal entry really is and a file or directory (which are very useful containers, not at all obsolete) should be made clearer. Downloads are implicitly files (documents or data if you prefer), not activities. Often, there is no natural activity for working with a download, or the default activity may be cumbersome or unworkable. The only workable means for accessing a download that I have discovered is to copy it to a USB or SD device, and then use the command line to manipulate it. The rudimentary task of managing development files has required me to repeatedly resort to the command line, which I detest, being a primitive legacy of the days in the 1970's when 64kbyte mini-computers ruled. It should be possible to copy, delete, rename, and execute files from the browser activity. This is the 21st century after all.
::This is being worked through in a slightly different way as discussed in [http://trac.sugarlabs.org/ticket/574 Ticket 574].

* The simple task of saving a module created with Pippy into a suitable library directory turns into an ordeal because of these limitations on necessary functionality which ultimately serves not to educate, but to handicap children.
::Please provide a more detailed description of this problem.

As a final remark, I am very aware that this is not a laptop project, nor is it a developer project, but an education project. Consider: children get older. They become more sophisticated. They begin to desire to express themselves and collaborate in more complicated ways, and engage in more complicated activities, which can not be linearized temporally. Activity development is just one instance of those possible future activities. Temporal state saving at the GUI level is a new and useful idea, but it is not sufficient. Usability will ultimately make or break this project.
::Thank you for your detailed and thoughtful comments. Sugar Labs is busy implementing many of them, and could use more of your help in implementing these types of ideas. We agree that usability is a paramount success factor—possibly second only to participation. Join us. --[[User:FGrose|FGrose]] 04:17, 20 March 2009 (UTC)

== Sugarize Firefox ==

It would be greatly appreciated if someone can develop a Sugarized version of Firefox! I don't think the collaboration tools are necessary (since the built in browser already does this), but people keep bringing it up as an issue why they don't like Sugar. Help, someone! That, or add tabs to the browse activity and a better Bookmarking mechanism.

* I use a "sugar coated" version of SeaMonkey; which is a full suite (browser, email, etc). Might Seamonkey be a better option due to its (as I understand) smaller footprint & greate number of options? -- [[User:AuntiMame]] 22 May 2008 16:05

AuntiMame - Can this be added to [[Activities]] where we can compile a list of all available applications, installation instructions, and links to download? -- [[User:Graham|Graham]]

: Can we have installation instructions for SeaMonkey?? -- [[User:Graham|Graham]]

* The Sugar Browser is actually based on the Firefox guts (xulrunner), but the UI has been developed for Sugar. You can find more details [http://wiki.laptop.org/go/Browse#Summary here.] There have been many requests, like yours, to improve it by supporting more features that "normal" browsers have. I agree that tabs and bookmarks would be welcome additions and useful for children. -- [[User:Ridderman|Ridderman]] 20:53, 22 May 2008 (UTC)

* Point of information for Ridderman but Browse already has bookmarks which work fine. [[User:Tinker|Tinker]] 05:59, 5 July 2008 (UTC)

== Sugar Control Panel ==

I would like to see a GUI control panel... I am discovering new features to customize through terminal, however, a lot of them could be easily accessible through a simple control panel GUI. I think this would help newer users a great deal.

<ol>
*Date, Time & Timezone
*Language
*User Accounts
*WiFi settings
*Jabber server(s) - ability to input multiple servers for different user groups (schools, cities, countries, etc.).
*Add/Remove Programs
*System Updates
*Desktop GUI settings
*Name SD card and USB media drives, etc.
*Running Linux Applications Under Sugar - A script has been written to Sugar Coat Linux apps to make them run under Sugar desktop (i.e. making them to run in the Sugar interface, without the collaboration and other Sugar integration programmed into them). Can this be made more user-friendly and incorporated into a Sugar Control Panel GUI, to make adding applications easier?
*What else?
*How about also getting latitude and longitude from the "nearby city" selected in the timezone setting dialog? -- [[User:Davewa|davewa]] 19:23, 23 May 2008 (UTC)
*Adding AccessX support - [http://wiki.laptop.org/go/AccessX AccessX] allows accessibility enhancements, like sticky keys, mouse keys, repetition speed. It works in Sugar but requires root access to be installed. The Tk config interface doesn't fit well into Sugar, too. -- [[User:andrea.mangiatordi|Andrea]] 16:41, 21 May 2009 (UTC)

</ol>

-- [[User:Graham|Graham]]

:This is a great idea, and it's actually already being developed. You can find more details [http://wiki.laptop.org/go/Sugar_Control_Panel#GUI_for_the_command_line_tool_.28work_in_progress.29 here] or in the sugar mailing lists. I'm not sure whether this will be available for the next Sucrose release, 0.82. -- [[User:Ridderman|Ridderman]] 21:02, 22 May 2008 (UTC)

*Ability to turn off/on Jabber in GUI Control panel so multiple users can transfer files and collaborate on a local wireless or wired network

: What is Sucrose, exactly?
:: See [[Taxonomy#Sucrose:_The_interface.2C_plus_a_set_of_demonstration_activities|Sucrose]]; which suggests we may want a [[Documentation_Team/Glossary|Glossary]] of (un)common terms. --[[User:Walter|Walter]] 23:12, 22 May 2008 (UTC)

== Chat (Jabber) ==

Ability to add multiple Jabber servers (connect with functionality detailed above) and switch between them in the chat program.

:From Wiki:

:But what if you wish to connect to one of several jabber servers because you belong to several communities/SIGs? I can live with one-at-a-time, but it would be wonderful if I could pick from a list I've created. Or at least a list of jabber servers I've previously connected to. How about a syntax for "choice <n> from file <x>" and "show me choices in file <x>"? -- davewa
:This feature request is being tracked in [http://trac.sugarlabs.org/ticket/587 Ticket 587]

== Browse ==

I cannot copy a link, I can't save a jpg, the Sugar OS changes the filename of a file which it does not recognise, the directory system is hidden, there is no predictive text when typing URL's or usernames, there's no tabbed browsing, there's no cookie, proxy or popup control.
:Browse 100 support copying/downloading images and links. (Wait for the hover menu or use the right mouse button on the object you are interested in.) The other feature requests are being tracked in [http://trac.sugarlabs.org/ticket/591 Ticket 591].

== Printer Support ==

I don't need to detail this very much - it's self evident. Support for generic USB printer drivers, and School Server printing? -- [[User:Graham|Graham]]
:<tt>yum install cups</tt> works out of the box so you can easily add network printers. But printing is not exposed in the Sugar UI. There was work going on at the OSU Open Systems labs... I'll ping them to find out if they have been making headway. --[[User:Walter|Walter]] 12:19, 23 May 2008 (UTC)

Thanks. We await news with baited breath. -- [[User:Graham|Graham]]
:This is being proposed as a [[Development Team/Project Ideas#Print_Support|Google Summer of Code project.]]

==Support for learning languages==

The Internet provides unprecedented access to materials in many languages, and to speakers of many languages. There are numerous aids to [[learning languages]], including dictionaries of some languages, textbooks, reference grammars, and flash card software for studying vocabulary and inflections. We need more of this kind of material, and we also need

* Graded materials for language learners, written and spoken
* Text-to-speech with text coloring in the manner of [[SLS]] (in progress)
* [[Speech recognition]], including speech-to-text
* Improved translation software
* Software that can carry out grammatical transformations, and create interactive drills on language structure
* Curricula and teaching/learning guides for languages

These materials fall into the categories of [[Education_Team/language content]], [[textbooks]] in a more advanced form incorporating software, and [[computational linguistics]]. Information on culture and other aspects of language communities is also essential.

==Support for family interaction==

Would it be possible to add collaborators that are people without laptops? for example my child is 4 and some of the activities need help from me to get her going, if I could put my self in the group view with the activities that she does with me. When I am invited to play with her then more activities could show, and perhaps the icon in the center of the screen could change slightly to show she is playing with dad or mum? Again the journal would also note when we were playing together.
:This suggests a wonderful use for the [[olpc:Record | Record]] (Camera) Activity. It would also crystallize the concept of a person, apart from a person's laptop. One could start recording people in their life by capturing an image or video of them. Once they register the person in a new registry, the images, videos, and all sorts of events and objects could be associated with the person. Sugar could extend their API to support the integration of real people with the laptop and school network. As you say, the Journal could then become an even more descriptive, connected, and complete learning record, and permit even more advanced learning and collaboration models. Great suggestion! --[[User:FGrose|FGrose]] 18:04, 16 March 2009 (UTC) I've entered it as a [[Development Team/Project Ideas#Registry for people | Development Team project idea]]. --[[User:FGrose|FGrose]] 19:00, 16 March 2009 (UTC)

==Better Support for Screencasting==
I have read the [[Activities/Screencast| Activity Screencast page]].
===training for Soas/ Sugar===
As a teacher with a little technical background, I can say that SoaS will have a lot of trouble getting traction into the schools without a lot more training. That training could easily be generated with Screencasts by volunteers IF screencasting was _better supported_ in SoaS. If screencasting was better implemented students could show, maybe even STREAM their videos, to their teachers, parents, friends and show how SMART they are by letting them make their own movies of same...
===better bug reports===
Furthermore, bug reports become much clearer when recorded _and_ the users knows to pull up the logs too. And the whole process of making a good bug report could be demonstrated in its entirety with a screencast... the vast numbers of users don't know a zillionth of what the devs know or need to know about the bug a user is experiencing... and as most of the users don't speak English, and most devs do, you've got a serious disconnect between what your users need to tell you... enter the 'screencast' and most of the big problem description becomes evident.
===PR for Soas/Sugar===
With more 'evidence' of the coolness of Sugar, people will get excited about SoaS perhaps like what happened around the Phun Physics package... [http://www.phunland.com/wiki/Home Phun] became one of the physics games of choice, for those without money, because of the tremendous number of naive users/kids producing Phun demonstrations on [http://www.youtube.com/results?search_query=phun&search_type=&aq=f Youtube]. --[[User:Dennis Daniels|dgd]] 3Aug9

==Embedded Predictive text==
Despite the emphasis on a non text environment there are numerous areas of education that rely on learners writing text.
The integration of a predictive text system similar to that used in the windows 'Typing Assistant' and the Co:Writer software used on the specialist hardware text editor the Alpasmart 3000, Alphasmart Neo, and Neo2.
Such an integration would provide sugar with an environment that would support those with learning difficulties e.g dyslexia and additionally extend the learners vocabulary as such systems give several numbered options to choose from as you type a given word, when the writer sees the word, selecting with the cursor or typing the number or word then utilises the selected word within the text entry dialog or document.A simple Function key combination switches the system on and off for free typing. --[[User:R Draycott|dgd]] 20Nov2009

:Erikos's recent work on a system-wide spell-checker might be a reasonable model to base such an intervention on. --[[User:Walter|Walter]] 14:06, 20 November 2009 (UTC)

[[Category:General public]]
[[Category:Idea]]
[[Category:Feature]]

Welcome to the Sugar Labs wiki

2011-03-09T07:11:18Z

Patrol: Reverted edits by Alice-thomas222 (talk) to last revision by FGrose

<center><div style="background:#efefef;border:1px solid #cdf; padding:0px; align:center;font-size:100%" class="linkgroup">
'''[[Sugar Labs/Current Events | Weekly News]]'''   ·  
'''[[Sugar Labs/Getting Involved | Join]]'''   ·  
'''[[Downloads]]'''   ·  
'''[[Sugar Labs/Contacts | Contact]]'''   ·  
'''[[Sugar Labs | About Us]]'''
</div>
</center><noinclude>
__NOEDITSECTION__
__NOTOC__

The Sugar Labs wiki is where our community comes together to develop and support the [[What is Sugar? | Sugar Learning Platform]].

{| border="0" 
|- row1
|<span class="linkgroup">[[File:Download_Mirabell.png|center|link=Downloads/Landing_page]]</span><br>[[Image:Sugarlabs_mainpage_01.png|link=Sugar Labs/Getting Involved]]
| 
== New Learners, Parents, Teachers, and Students ==
Sugar users are Learners. If you are visiting for the first time, please see [http://www.sugarlabs.org www.sugarlabs.org] for an introduction to Sugar.

Want to help? Visit the '''[[Sugar Labs/Getting Involved| Getting Involved ]]''' page, and find out how you can join in the fun of learning. We have some [[Vacancies]] and are always looking for maintainers and testers.

== Current Learners ==
If you have Sugar and are looking for new Activities, please see the [http://activities.sugarlabs.org Sugar Activity Library].

== New and Current Community Members ==
Please take a look around the wiki. Explore the menus along the left side of the page. If you ever get lost, just click on the ''Wiki'' link at the top of every page and you will return to this page. Please also visit the [[Local Labs]].
|- row2

|}
==Community News==

{{:News}}

For more news about Sugar Labs, please see the [[Sugar Labs/Current Events|Current Events page]] and the [[Archive/Current Events|Sugar Digest archive]]. Press releases are on our [http://www.sugarlabs.org/index.php?template=press Press page]. There is also an [[News|archive of news links]], which were on this front page.

<div style="background-color:#a0ff93; border:1px solid #cdf; padding:5px; padding-left: 1.0em; font-size:100%">[[Sugar_Labs/Governance/Trademark|Sugar Labs<sup>®</sup>]] is a non-profit association, a member project of the [http://conservancy.softwarefreedom.org/ Software Freedom Conservancy], and is supported by our generous [[Sugar Labs/Getting Involved|contributors]] and [[Sugar Labs/Thank You|sponsors]].
</div>

[[Category:General public]]

<noinclude>
{{Translations | [[Sugar Labs/Welcome to Sugar Labs|english]] | [[Sugar Labs/Welcome to Sugar Labs/lang-es|español]] | [[Sugar Labs/Welcome to Sugar Labs/lang-pt_BR|português brasil]] | [[Sugar Labs/Welcome to Sugar Labs/lang-ps|پښتو]] | [[Sugar Labs/Welcome to Sugar Labs/lang-ru_RU|русский]] |}}
</noinclude>
__NOTOC__
__NOEDITSECTION__

Welcome to the Sugar Labs wiki

2010-08-12T14:27:02Z

Patrol: Reverted edits by Mary Ann Estorgio (talk) to last revision by FGrose

<center><div style="background:#efefef;border:1px solid #cdf; padding:0px; align:center;font-size:100%" class="linkgroup">
'''[[Sugar Labs/Current Events | Weekly News]]'''   ·  
'''[[Sugar Labs/Getting Involved | Join]]'''   ·  
'''[[Downloads]]'''   ·  
'''[[Sugar Labs/Contacts | Contact]]'''   ·  
'''[[Sugar Labs | About Us]]'''
</div>
</center><noinclude>
__NOEDITSECTION__
__NOTOC__

The Sugar Labs wiki is where our community comes together to develop and support the [[What is Sugar? | Sugar Learning Platform]].

{| border="0" 
|- row1
|[[Image:Sugarlabs_mainpage_01.png|link=Sugar Labs/Getting Involved]]
| 
== New Learners, Parents, Teachers, and Students ==
Sugar users are Learners. If you are visiting for the first time, please see [http://www.sugarlabs.org www.sugarlabs.org] for an introduction to Sugar.

Want to help? Visit the '''[[Sugar Labs/Getting Involved| Getting Involved ]]''' page, and find out how you can join in the fun of learning. We have some [[Vacancies]] and are always looking for maintainers and testers.

== Current Learners ==
If you have Sugar and are looking for new Activities, please see the [http://activities.sugarlabs.org Sugar Activity Library].

== New and Current Community Members ==
Please take a look around the wiki. Explore the menus along the left side of the page. If you ever get lost, just click on the ''Wiki'' link at the top of every page and you will return to this page. Please also visit the [[Local Labs]]:<br>{{!}} [http://co.sugarlabs.org/go/Laboratorios_Azúcar_Colombia Sugar Labs Colombia] {{!}} [http://cl.sugarlabs.org/go/Página_Principal Sugar Labs Chile] {{!}} [[Sugar Labs DC]] {{!}} [http://pe.sugarlabs.org/ Sugar Labs Peru]<br>{{!}} [http://ar.sugarlabs.org/ Sugar Labs Argentina] {{!}}
|- row2

|}
==Community News==
{| border="0"
|-
|{{:News}}
|[[File:SugaronastickMirabelle.png|300px|link=Sugar on a Stick/Mirabelle]]
|}

For more news about Sugar Labs, please see the [[Sugar Labs/Current Events|Current Events page]] and the [[Archive/Current Events|Sugar Digest archive]]. Press releases are on our [http://www.sugarlabs.org/index.php?template=press Press page]. There is also an [[News|archive of news links]], which were on this front page.

<div style="background-color:#a0ff93; border:1px solid #cdf; padding:5px; padding-left: 1.0em; font-size:100%">[[Sugar_Labs/Governance/Trademark|Sugar Labs<sup>®</sup>]] is a non-profit association, a member project of the [http://conservancy.softwarefreedom.org/ Software Freedom Conservancy], and is supported by our generous [[Sugar Labs/Getting Involved|contributors]] and [[Sugar Labs/Thank You|sponsors]].
</div>

[[Category:General public]]

<noinclude>
{{Translations | [[Sugar Labs/Welcome to Sugar Labs|english]] | [[Sugar Labs/Welcome to Sugar Labs/lang-es|español]] | [[Sugar Labs/Welcome to Sugar Labs/lang-pt_BR|português brasil]] | [[Sugar Labs/Welcome to Sugar Labs/lang-ps|پښتو]] | [[Sugar Labs/Welcome to Sugar Labs/lang-ru_RU|русский]] |}}
</noinclude>
__NOTOC__
__NOEDITSECTION__

MediaWiki:Login

2010-07-14T00:01:33Z

Patrol: message moved to loginprompt message

MediaWiki:Loginprompt

2010-07-14T00:00:27Z

Patrol:

<span style="background:#ffb732;">**'''Notice:''' New user account creation has been inhibited temporarily for site maintenance.**

<span style="background:lightgreen;">New OpenID accounts are available.</span>

You must have cookies enabled to log in to {{SITENAME}}.

MediaWiki:Sitenotice

2010-07-13T23:35:02Z

Patrol: message moved to login line message

<div class="plainlinks linkgroup" style="font-size:100%; word-spacing:9px; text-align:left; font-weight:normal">[http://www.sugarlabs.org/ Web] [http://wiki.sugarlabs.org/ ''Wiki'']
[http://activities.sugarlabs.org/ Activities] [[Downloads]] [http://planet.sugarlabs.org/ Blog] [http://lists.sugarlabs.org/ Lists] [http://meeting.sugarlabs.org/ Meetings] [http://schools.sugarlabs.org/ Schools] [http://bugs.sugarlabs.org/ Bugs] [http://patchwork.sugarlabs.org/ Patches] [http://git.sugarlabs.org/ Git] [http://api.sugarlabs.org/ API] [http://translate.sugarlabs.org/ Translate] [http://buildbot.sugarlabs.org/ Buildbot] [http://people.sugarlabs.org/ People] [[Sugar_Labs/Donate|Donate]]</div>

MediaWiki:Login

2010-07-13T23:33:19Z

Patrol:

**New account creation has been inhibited temporarily for site maintenance.**

Log in

MediaWiki:Login

2010-07-13T23:30:17Z

Patrol: Created page with '&42;&42;New account creation has been inhibited temporarily for site maintenance.** Log in'

&42;&42;New account creation has been inhibited temporarily for site maintenance.**

Log in

MediaWiki:Sitenotice

2010-07-13T23:19:00Z

Patrol:

<div style="border:2px solid #ff7800; background-color:#ffd732; padding-top:10px;">
'''Notice:''' New user account creation has been inhibited temporarily for site maintenance.
</div>
<div class="plainlinks linkgroup" style="font-size:100%; word-spacing:9px; text-align:left; font-weight:normal">[http://www.sugarlabs.org/ Web] [http://wiki.sugarlabs.org/ ''Wiki'']
[http://activities.sugarlabs.org/ Activities] [[Downloads]] [http://planet.sugarlabs.org/ Blog] [http://lists.sugarlabs.org/ Lists] [http://meeting.sugarlabs.org/ Meetings] [http://schools.sugarlabs.org/ Schools] [http://bugs.sugarlabs.org/ Bugs] [http://patchwork.sugarlabs.org/ Patches] [http://git.sugarlabs.org/ Git] [http://api.sugarlabs.org/ API] [http://translate.sugarlabs.org/ Translate] [http://buildbot.sugarlabs.org/ Buildbot] [http://people.sugarlabs.org/ People] [[Sugar_Labs/Donate|Donate]]</div>

MediaWiki:Sitenotice

2010-07-13T22:55:06Z

Patrol:

<div style="border:2px solid #ff7800; background-color:#ffd732; padding-top:10px;">
'''Notice:''' User account creation has been inhibited temporarily for site maintenance.
</div>
<div class="plainlinks linkgroup" style="font-size:100%; word-spacing:9px; text-align:left; font-weight:normal">[http://www.sugarlabs.org/ Web] [http://wiki.sugarlabs.org/ ''Wiki'']
[http://activities.sugarlabs.org/ Activities] [[Downloads]] [http://planet.sugarlabs.org/ Blog] [http://lists.sugarlabs.org/ Lists] [http://meeting.sugarlabs.org/ Meetings] [http://schools.sugarlabs.org/ Schools] [http://bugs.sugarlabs.org/ Bugs] [http://patchwork.sugarlabs.org/ Patches] [http://git.sugarlabs.org/ Git] [http://api.sugarlabs.org/ API] [http://translate.sugarlabs.org/ Translate] [http://buildbot.sugarlabs.org/ Buildbot] [http://people.sugarlabs.org/ People] [[Sugar_Labs/Donate|Donate]]</div>

Fedora

2010-06-15T14:18:14Z

Patrol:

<noinclude>{{TOCright}}
[[Category:Supported systems]]
</noinclude>

[[Image:Fedora.jpg]]

== Fedora 13 ==
The Sugar Learning Environment is packaged in Fedora 13.
* From the System -> Administration -> Add/Remove Software menu, search for Sugar.
* Among all the packaged Activities select,
{|
|-
|width="15"|
|[[File:XO_buddy.png|40px]]
|width="10"|
|'''The emulator for the Sugar Learning Environment'''<br> sugar-emulator-0.88.1-1.fc13 (no arch)
|}
: and any or all of the Activities.
: Sugar will be available in your Applications -> Education menu.

Sugar will run in a [[wikipedia:Xephyr|Xephyr]] window within your current environment. You will have full access to the Sugar features, and may even run multiple instances to simulate a local collaboration group.
: Adjust the default window size for Sugar by editing the menu item for Sugar to<br>{{Code|/usr/bin/sugar-emulator -i 1200x900}}
:: to match the XO screen proportions
:{{Code|/usr/bin/sugar-emulator -i 600x500}}
:: fits the screen for a 10-inch netbook

You may also collaborate with others in the jabber.sugarlabs.org server Neighborhood (Press <F1> to see the Neighborhood view.)

==Sugar on a Stick ==

With this spin, you'll be able to run Sugar, which is developed by Sugar Labs and is the desktop environment used on the OLPC, directly from a Live CD or Live USB!

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

[[File:Soas-mirabelle-logo.png|200px|link=Sugar_on_a_Stick/Beta]], v4 alpha with Sugar 0.88.1 and Fedora 14 (Rawhide)

==Make a custom Fedora image==
''' or Live DVD/CD'''

(revised march 14 2010)

*f11 will build 0.84.x Sugar
*f12 will build 0.86.x Sugar *(does not see USB in frame, on insertion, when running Virtualbox.)

* In Terminal:

yum install revisor
yum install kickstart

*start '''kickstart''' and follow instructions/ save the kickstart file

*Sugar Desktop is one of the selections offered.

* Hint: select Gnome desktop and then deselect it if you do not want it (this sets graphical dependencies like X for you)

*start '''revisor''' select DVD-CD 0r Live / select your KS.cfg (in you /home/(user) directory) / select options and start.

* takes about 1-2 hrs to build .iso files
* '''Important: copy completed .iso files from /srv/revisor/f11(12) i386/*** subdirectories; and paste them onto your Desktop.'''
* burn DVD/CD .iso and use it in VMworkstation or Virtualbox to test; or use to '''install to USB/SD or your Hard-Disk''' (with Anaconda in your new DVD/CD)

Build System setup:
*500/250 GB Seagate FreeAgent GO external usb HD's (easily switched and portable)
*f11/f12 installed with f11/f12 netinstall.CD's
*Hp Pavillion tx 1000 AMd Turion 64 Laptop (with Hard-Disk removed);Booted from netinstall CD's
*Wired Cat5 Network Connection to HS Cable Modem

== Fedora-12-i686-Live-Edu ==
Gnome + Sugar-Desktop in a 1.6Gb .iso

Installs to a 8GB USB nicely

torrent:[http://torrent.fedoraproject.org/spins/Fedora-12-i686-Live-Edu.torrent]

== Fedora OLPC ==
The Fedora OLPC SIG, http://fedoraproject.org/wiki/OLPC, will be importing further activities into Fedora, which might later be installed using

yum install sugar-*
:: Here's a video of the process [http://www.youtube.com/watch?v=QKmrtlyyCFo http://www.youtube.com/watch?v=QKmrtlyyCFo]
::CJB suggests: as root, run: yum -y groupinstall "Sugar Desktop Environment"
The command to run Sugar is as root otherwise you may get this [http://www.youtube.com/watch?v=azKbRqr60Og behavior].

sugar-emulator

For more information on the new release, please refer to the announcement here:

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

==Mailing list ==

* http://admin.fedoraproject.org/mailman/listinfo/olpc

Sugar on a Stick/Sugar Clone

2010-06-14T03:21:23Z

Patrol:

<noinclude>{{TOCright}}
[[Category:Live USB]]
</noinclude>

'''Sugar Clone''' is, at this point in time (May 2010), a Bash script that aids in the copying of a customized [[LiveOS image]], such as [[Sugar on a Stick]], to a secondary device. It works from within a booted LiveOS image to copy that image. Or it may be used to copy a LiveOS image between 2 attached USB/SD storage devices. It is intended to support the Sugar customization kit projects.

A small, utility script, '''Sugar Cellar''', is available in the bundle, or separately. It is used to report on the storage space available on the persistent overlay, home directory, and other file spaces attached to the running image.

* http://people.sugarlabs.org/fgrose/SugarClone
* http://people.sugarlabs.org/fgrose/SugarCellar

See this announcement post, {{Iframe|[http://www.mail-archive.com/soas@lists.sugarlabs.org/msg01018.html You scream, I scream, we all scream for Mirabelle ice cream in a Sugar Clone]. |http://www.mail-archive.com/soas@lists.sugarlabs.org/msg01018.html|900|336|1}}
And this follow-on discussion thread, {{Iframe|[http://www.mail-archive.com/soas@lists.sugarlabs.org/msg01138.html <nowiki>[SugarClone]</nowiki> -was: You scream, I scream, ...]. |http://www.mail-archive.com/soas@lists.sugarlabs.org/msg01138.html|900|336|1}}
==Introduction==
* See the embedded help documentation in the script [[#Source|displayed below]].
===Test Usage===

Test Usage:

# Obtain the SugarClone script at http://people.sugarlabs.org/fgrose/SugarClone.
# Before booting the SoaS device that will be the source of the new SugarClone, copy the SugarClone script to the root '/' folder at the base of the filesystem for the device, or to /mnt/live (from the perspective of a running LiveOS image).
# Boot the USB stick into SoaS and insert a second USB device into the computer running that SoaS image.
# In the Terminal Activity of that running SoaS image, enter the command,

::<big><code>/mnt/live/SugarClone</code></big>

If there is more than one USB/SD storage device available, a menu of the devices will appear for selection of the target device.

The scripts will copy the currently running image to the target device. When that device is booted, a new, Sugar Learner sign-in will be triggered. The previously customized Journal and operating system will be present on the SugarClone image.

On a running LiveOS image, the root folder of the USB/SD device is available at the /mnt/live mount point. The SugarClone script can be obtained (assuming Internet connectivity) as follows:

In the Terminal Activity, change the working directory, and get the file:<big>
: <code>cd /mnt/live</code>
: <code>wget http://people.sugarlabs.org/fgrose/SugarClone</code>
</big>
At this point,<big>
: <code>SugarClone</code>
</big>
will launch the script.

===Possible Use Cases===
====Curriculum packaging====
# A teacher wants to prepare a SoaS image with a custom set of installed Activity bundles or a Journal of Activity instances for an upcoming class term.
# The teacher modifies their current working image by adding or deleting Activity bundles from their Home view and adding or removing Journal entries with specific content, even saving distributable ebooks, or bookmarks in Browse instances that are named for specific sets of local web destinations (a class portal perhaps for deployments lacking Internet connectivity).
# The teacher scrubs out any personal passwords or other history that should not be shared in the new copies.
# Following customization, a fresh or recycled USB stick that is inserted into the computer running the customized SoaS image can become the SugarClone.

Step 4 assumes that Usage step 1 has been performed either directly or by the SoaS packagers.
====Full image backup or sharing====
# A Learner has modified their environment, perhaps adding Activity bundles and prepared specific instances such as a [[Activities/Physics]] simulation.
# Their modifications include changes to their operating system installed through [[wikipedia:Yellowdog_Updater,_Modified|yum]] or [[wikipedia:RPM_Package_Manager|RPM]] to obtain some new core functionality.
# The Learner wants to archive or share this image with friends or for a backup.
# Personal or private information is scrubbed from the Journal or Browse history and other potential stores.
# The User creates one or more Sugar Clones.

This method of backup has the advantage that it copies Learner changes to the core operating system as well as the Journal.
A LiveOS image using a separate persistent home folder could be partially cloned with either the operating system overlay or home folder without the other should that be desired.

====See also====
* Other [[Talk:Sugar_on_a_Stick/Sugar_Clone |neat uses]] for the modified_livecd-iso-to-disk script.

===Notes===

These scripts have been tested with SoaS-Mirabelle (available at http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/) but should work with other versions of SoaS.

The current version of the script has the /bin/bash shell specified without the -x (xtrace) option. Set this option, #!/bin/bash -x in the first line of the script to aid testing. When set, the script will show a lot of output on the screen as it runs.

The script is copied to any new SugarClone devices prepared with this script so that SugarClone images can easily propagate themselves. This also applies to all new SoaS installations that are prepared with these scripts (using --image <source> options).

==Needed:==

# More review and testing.
#* SD cards
ONE PROBLEM on Acer Aspire One 532H:
"Turns out the SD adapter uses the PCIe bus"
and is not recognized by Sugar or your Script
anyway to detect this in the script? (It is being used in test deployments now.)
The SD slot is NOT bootable on this model but could be used to make clone custom SD's for use on other netbooks (EeePC900)
satellit 04/26/2010
# Submission of the modified_livecd-iso-to-disk script upstream.
#* https://bugzilla.redhat.com/show_bug.cgi?id=448030
# Modifications for XOs.
# Modifications for Intel Macintosh computers.
#* https://answers.edge.launchpad.net/soas/+question/95622
# <s>Extraction of the Learner's Sugar image name for labeling the Clone.</s> (available 14 April 2010)
# A Sugar Activity that calls or controls the scripts. See [[Activities/Toaster]].
# A way to automatically identify extra partitions on devices with more than one available partition.
# A way to automatically identify live media images on secondary devices and partitions that could be used as sources for a Sugar Clone.
# <s>Bundling of the scripts for convenience until they are included in SoaS.</s> (available 23 April 2010)
# Extend the capability to write CD-ROM image files for inexpensive distribution.
# Extend the facility to any Sugar image.

These all should help us better prepare a SoaS customization kit.

==Source==
===Sugar Clone===
The script is available at http://people.sugarlabs.org/fgrose/SugarClone and is displayed from there below.<br>
Embedded help, which describes the script and its usage in greater detail, is available (just after the stock header) in the script below.
{{Iframe|collapsed=|http://people.sugarlabs.org/fgrose/SugarClone|http://people.sugarlabs.org/fgrose/SugarClone|800|342|1}}
===Sugar Cellar===
{{Iframe|collapsed=|http://people.sugarlabs.org/fgrose/SugarCellar|http://people.sugarlabs.org/fgrose/SugarCellar|800|200|1}}
===Bundle===
{{Iframe|collapsed=|http://people.sugarlabs.org/fgrose/bundle|http://people.sugarlabs.org/fgrose/bundle|800|200|1}}

Development Team/Release

2010-06-09T13:37:37Z

Patrol: Reverted edits by Rebeca123 (talk) to last revision by Patrol

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>
{{TOCright}}
== Goals and modules proposal ==

At the beginning of each release cycle, maintainers will work on a set of goals, document them and assign owners. (These goals typically involve major interventions or the addition of new components, e.g., someone develops a speech engine specially for his mother tongue and wants it in Sugar. Hence, the process described below is primarily for module maintainers. If you are a developer with a feature or bug fix, you may want to refer to the [[Features/Feature Template|new feature process]].)

=== New modules proposal ===

The time period available to make a proposal is indicated on the schedule. To propose a new activity send mail to the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], providing the following information:

(See [[Features/Feature Template]].)

* Short description of the features.
* Screenshots or screencasts.
* Are you willing to follow the [[Development Team/Release/Roadmap#Schedule|Schedule]]?
* Are you willing to provide regular source releases? (releases need to be done as well when there are only changes in translations)
* System components the activity depends on.
* Maintainer and members of the developer team, with links to a User page on the wiki or their homepage on the web.
* Status of internationalization.
* Code repository.
* Bug tracking system.
* Homepage.

Criteria for approval will be:

* Supports internationalisation and localisation.
* Does not duplicate the functionalities of other activities.
* Provide functionality that the community judges as important for reaching the goals of the project.
* Maintainer responsiveness and willingness to provide regular releases.



== Module release ==

For both intermediates and final releases module maintainers are responsible to announce the module release and make the sources available. Note that the release number of the module does not need to match the Sucrose release number.
More in detail:

=== Glucose ===
* Build a source tarball

make distcheck

* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v0.81.9).

* test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there. The preferred location for glucose modules is:
shell.sugarlabs.org:/upload/sources/sucrose/glucose/(module_name)/
which translates to:
http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/

* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.

=== Fructose ===
* Build a source tarball
If your activity uses bundlebuilder you can use the dist_source command to generate a source tarball. Note, use a clean checkout of the repository - due to how bundlebuilder works at the moment files you would place in the directory e.g. x.patch would be included in the tarball as well.

python setup.py dist_source

The tarball will be generated inside the dist directory.

* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20).

* Test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there.

The preferred location for fructose components is:
shell.sugarlabs.org:/upload/sources/sucrose/fructose/(module_name)/
which translates to:
http://download.sugarlabs.org/sources/sucrose/fructose/(module_name)/

* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.

=== Using the release script ===
For both, fructose and glucose components you can use the release script in [http://git.sugarlabs.org/projects/sugar-tools sugar-tools] to do the above tasks in one go.

You can check out the available commands (Note, the script does try to release the software of the directory you are currently in):

./release --help

== Sugar release ==

Each release cycle will include development, beta, release candidate and final releases. The release team is responsible to coordinate with module maintainers, pull the updated modules together, perform basic QA and announce it. More in detail:

* Ensure that all the module releases are available by the scheduled date.
* Construct a sugar-jhbuild moduleset out of them. Run automatic and manual QA on it.
* If issues arise coordinate with the relevant module maintainers to solve them.
* Announce the release on sugar-devel@lists.sugarlabs.org, including a reference to the sugar-jhbuild moduleset, references to each source module and a global list of changes.

== Feature freeze ==
No new modules or features will be accepted for this release period. "Feature" should be interpreted as "Functionality" or "Ability". Bug fixes of existing features are not affected.

This allows developers to concentrate on refining the new features instead of adding yet more functionality.

The feature freeze affects all the modules included in the release and comprise also ABI for public libraries. Exceptions might be considered by the release team but they will be extremely rare. To request an exception send mail to [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], referencing the patches you would like to land. It will have to be granted by two [[Development Team/Release/Contacts|members]] of the release team, on the base of community feedback.

== UI Freeze ==
Major UI revisions or changes must be done before this date. You can still make string changes (e.g. changing a sentence in a window) before the String Freeze.

This encourages developers to focus on stability and bug-fixing rather than UI changes. At this point, documentation writers do not have to worry that their work will become outdated.

If you really need to do an UI change you have to ask an exception from the release team and must notify the documentation team when accepted.

== String cooling==
String changes have to be announced, but no exceptions have to be requested. As soon as the change is committed in git, notify the [[http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] about it.

== String Freeze==
Every string change has to be requested and to be approved. Please send an exception to the [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] and [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] if you need to break the string freeze and ask for an exception. The localization team lead and two members of the release team need to approve such a break.

== Stabilizing ==
In the stabilizing phase we request every bug fix to be tied to a ticket including a testing plan. Please add the testcase in the ticket comment field. You need to mark it with |TestCase|. This adds better readability and our script that pulls together the test cases for each release is able to find it as well. For example:
|TestCase|
Click on Browse, Read, Pippy icons in the homepage and make sure all of them starts correctly.

== Hard code freeze ==
When the hard code freeze is in effect, each and every code change should be approved by the release team. Only critical fixes will be considered. To request approval send mail to sugar-devel@lists.sugarlabs.org, including the patch and a detailed description of the changes, the benefits and the risks. Approval will have to be granted by two [[Development Team/Release/Contacts#People|members]] of the team.

== Branching ==

After the final release of a module, a branch should be created to host further stable development. Please use a name in the form: sucrose-XXX (for example sucrose-0.84). Each module maintainer is responsible to inform the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] and [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org] lists about the branch.

A new branch is created on the Pootle server, e.g., Fructose-0.82 and Fructose-0.84. The Localization team (the coordinator of a translation team) may push translations to any or all of the corresponding branches of your project. Changes to your master branch are not necessarily intended for the release branches as well.

You can create a remote branch like this (in your repository):

git branch sucrose-0.84
git push origin sucrose-0.84

And to work on it (in your repository):

git checkout -b sucrose-0.84 origin/sucrose-0.84
git pull

== Roadmap ==

The [[Development Team/Release/Roadmap]] is updated at the beginning of each release cycle by the release team. It includes:

* Detailed schedule of release dates and freeze points.
* List of modules and external dependencies.
* Reference to all the tickets considered for the release.
* References to the new feature proposals.

== Bug triaging ==

Module maintainers should ensure that their plans for the release are clearly reflected in the bug tracking system. They are responsible to set milestones and priorities accordingly, in cooperation with the release and the QA teams.

Each commit or set of commit should have a ticket associated. The ticket number should be always mentioned in the git log and is used to automatically build the list of module changes for the releases.

== Automation ==

TBD Many of the steps described in this document can be easily automated for maintainers which are using the Sugar Labs infrastructure and for the release team. Though as a first pass we want to get the workflow right, even if it involves more manual step than strictly required.

==Subpages==
{{Special:PrefixIndex/{{PAGENAME}}/}}
See [[:Category:Release Notes]]
[[Category:Development Team/Release]]

Marketing Team/Logo

2010-05-20T22:09:04Z

Patrol: /* Sugar logo variations */

{{TOCright}}
===Wiki page cross-reference===

See also the related page [[Design Team/Logo Ideas]]

===Sugar Graphic Identity===

The Sugar Labs logo exists in the color combinations shown below. The logo can sit either on a white or black background, and the color combinations change order based on the background--against a white background the outline color around "sugar" is always lighter than the fill color, while against a black background the outline color is darker than the fill color.

==Sugar logo variations==

[[File:logo_alt_3.png|240px]]

Sugar logo | primary colors | [[:File:logo_alt_3.svg| SVG]] | [[:File:logo_alt_3.png| PNG]]

[[File:logo_alt_1.png|400px]]

Sugar Labs logo | primary colors | [[:File:logo_alt_1.svg| SVG]] | [[:File:logo_alt_1.png| PNG]]

[[File:Logo_alt_1(R).png|400px]]

Sugar Labs logo | primary colors w/ registration mark | [[:File:Logo_alt_1(R).svg| SVG]] | [[:File:Logo_alt_1(R).png| PNG]]

[[File:logo_alt_2.png|240px]]

Sugar Labs logo (alternate, usage discouraged) | primary colors | [[:File:logo_alt_2.svg| SVG]] | [[:File:logo_alt_2.png| PNG]]

[[File:logo_SoaS_01.png|540px]]

Sugar on a Stick Strawberry logo | [[:File:logo_SoaS_01.svg| SVG]] | [[:File:logo_SoaS_01.png| PNG]]

[[File:logo_SoaS_02.png|540px]]

Sugar on a Stick Blueberry logo | [[:File:logo_SoaS_02.svg| SVG]] | [[:File:logo_SoaS_02.png| PNG]]

[[File:logo_SoaS_03.png|540px]]

Sugar on a Stick logo | [[:File:logo_SoaS_03.svg| SVG]] | [[:File:logo_SoaS_03.png| PNG]]

[[File:Soas-mirabelle-logo.png|540px]]

Sugar on a Stick Mirabelle logo | [[:File:Soas-mirabelle-logo.svg| SVG]] | [[:File:Soas-mirabelle-logo.png| PNG]]

==Logo usage==
*The logo should be used '''only on a black or white background'''
*Make sure there is '''generous space surrounding the logo''', as shown in the PNG and SVG files.
*Don't use any other color combinations than the ones shown below.
*'''Don't alter the logo''' in any other way--don't stretch, rotate, or change the letter spacing and size.
*Scale down only as long as the color outline around "sugar" is still clearly visible.
*While the Sugar Labs logo also exists as a stacked version for use in space-confined situations, the '''single line logo is the primary treatment''' and should be used wherever possible.
*'''Prefixes or suffixes should not be incorporated into the logo'''. This also accounts for country names, e.g. "[Sugar Labs Logo] CountryName". The logo needs to stand on its own. Prefixes or suffixes should not be handled as a part of the logo, but instead in regular text, such as when writing about a country specific Sugar Labs entity, e.g. "Sugar Labs CountryName". Note: There may be exceptions that should be discussed case by case, such as the Sugar on a Stick logo above.
*The logo font is [[wikipedia:VAG Rounded|VAG Rounded]]. The font Modata, in the MgOpen package, is closely based on this font (individual [http://www.zvr.gr/typo/mgopen/index Modata] ttf files).

If you have any questions about correct logo usage, contact [http://sugarlabs.org/go/User:Christianmarcschmidt Christian Marc Schmidt] at anything [at] christianmarcschmidt.com.

==Sugar Labs logo for white backgrounds==

{|
|[[Image:logo_white_01.png|300px|http://www.sugarlabs.org/go/Image:logo_white_01.png]]
[http://www.sugarlabs.org/go/Image:logo_white_01.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_01.png PNG]
|[[Image:logo_white_02.png|300px|http://www.sugarlabs.org/go/Image:logo_white_02.png]]
[http://www.sugarlabs.org/go/Image:logo_white_02.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_02.png PNG]
|[[Image:logo_white_03.png|300px|http://www.sugarlabs.org/go/Image:logo_white_03.png]]
[http://www.sugarlabs.org/go/Image:logo_white_03.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_03.png PNG]
|-
|[[Image:logo_white_04.png|300px|http://www.sugarlabs.org/go/Image:logo_white_04.png]]
[http://www.sugarlabs.org/go/Image:logo_white_04.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_04.png PNG]
|[[Image:logo_white_05.png|300px|http://www.sugarlabs.org/go/Image:logo_white_05.png]]
[http://www.sugarlabs.org/go/Image:logo_white_05.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_05.png PNG]
|[[Image:logo_white_06.png|300px|http://www.sugarlabs.org/go/Image:logo_white_06.png]]
[http://www.sugarlabs.org/go/Image:logo_white_06.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_06.png PNG]
|-
|[[Image:logo_white_07.png|300px|http://www.sugarlabs.org/go/Image:logo_white_07.png]]
[http://www.sugarlabs.org/go/Image:logo_white_07.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_07.png PNG]
|[[Image:logo_white_8.png|300px|http://www.sugarlabs.org/go/Image:logo_white_8.png]]
[http://www.sugarlabs.org/go/Image:logo_white_8.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_8.png PNG]
|[[Image:logo_white_09.png|300px|http://www.sugarlabs.org/go/Image:logo_white_09.png]]
[http://www.sugarlabs.org/go/Image:logo_white_09.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_09.png PNG]
|-
|[[Image:logo_white_10.png|300px|http://www.sugarlabs.org/go/Image:logo_white_10.png]]
[http://www.sugarlabs.org/go/Image:logo_white_10.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_10.png PNG]
|[[Image:logo_white_11.png|300px|http://www.sugarlabs.org/go/Image:logo_white_11.png]]
[http://www.sugarlabs.org/go/Image:logo_white_11.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_11.png PNG]
|[[Image:logo_white_12.png|300px|http://www.sugarlabs.org/go/Image:logo_white_12.png]]
[http://www.sugarlabs.org/go/Image:logo_white_12.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_white_12.png PNG]
|}

==Sugar Labs logo for black backgrounds==

{|
|[[Image:logo_black_01.png|300px|http://www.sugarlabs.org/go/Image:logo_black_01.png]]
[http://www.sugarlabs.org/go/Image:logo_black_01.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_01.png PNG]
|[[Image:logo_black_02.png|300px|http://www.sugarlabs.org/go/Image:logo_black_02.png]]
[http://www.sugarlabs.org/go/Image:logo_black_02.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_02.png PNG]
|[[Image:logo_black_03.png|300px|http://www.sugarlabs.org/go/Image:logo_black_03.png]]
[http://www.sugarlabs.org/go/Image:logo_black_03.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_03.png PNG]
|-
|[[Image:logo_black_04.png|300px|http://www.sugarlabs.org/go/Image:logo_black_04.png]]
[http://www.sugarlabs.org/go/Image:logo_black_04.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_04.png PNG]
|[[Image:logo_black_05.png|300px|http://www.sugarlabs.org/go/Image:logo_black_05.png]]
[http://www.sugarlabs.org/go/Image:logo_black_05.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_05.png PNG]
|[[Image:logo_black_06.png|300px|http://www.sugarlabs.org/go/Image:logo_black_06.png]]
[http://www.sugarlabs.org/go/Image:logo_black_06.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_06.png PNG]
|-
|[[Image:logo_black_07.png|300px|http://www.sugarlabs.org/go/Image:logo_black_07.png]]
[http://www.sugarlabs.org/go/Image:logo_black_07.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_07.png PNG]
|[[Image:logo_black_08.png|300px|http://www.sugarlabs.org/go/Image:logo_black_08.png]]
[http://www.sugarlabs.org/go/Image:logo_black_08.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_08.png PNG]
|[[Image:logo_black_09.png|300px|http://www.sugarlabs.org/go/Image:logo_black_09.png]]
[http://www.sugarlabs.org/go/Image:logo_black_9.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_09.png PNG]
|-
|[[Image:logo_black_10.png|300px|http://www.sugarlabs.org/go/Image:logo_black_10.png]]
[http://www.sugarlabs.org/go/Image:logo_black_10.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_10.png PNG]
|[[Image:logo_black_11.png|300px|http://www.sugarlabs.org/go/Image:logo_black_11.png]]
[http://www.sugarlabs.org/go/Image:logo_black_11.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_11.png PNG]
|[[Image:logo_black_12.png|300px|http://www.sugarlabs.org/go/Image:logo_black_12.png]]
[http://www.sugarlabs.org/go/Image:logo_black_12.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_black_12.png PNG]
|}

==Sugar Labs logo (alt) for white backgrounds==

(use only in space-confined situations)

{|
|[[Image:logo_square_white_01.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_01.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_01.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_01.png PNG]
|[[Image:logo_square_white_02.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_02.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_02.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_02.png PNG]
|[[Image:logo_square_white_03.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_03.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_03.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_03.png PNG]
|[[Image:logo_square_white_04.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_04.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_04.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_04.png PNG]
|-
|[[Image:logo_square_white_05.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_05.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_05.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_05.png PNG]
|[[Image:logo_square_white_06.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_06.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_06.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_06.png PNG]
|[[Image:logo_square_white_07.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_07.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_07.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_07.png PNG]
|[[Image:logo_square_white_8.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_8.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_08.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_8.png PNG]
|-
|[[Image:logo_square_white_09.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_09.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_09.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_09.png PNG]
|[[Image:logo_square_white_10.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_10.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_10.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_10.png PNG]
|[[Image:logo_square_white_11.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_11.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_11.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_11.png PNG]
|[[Image:logo_square_white_12.png|180px|http://www.sugarlabs.org/go/Image:logo_square_white_12.png]]
[http://www.sugarlabs.org/go/Image:logo_square_white_12.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_white_12.png PNG]
|}

==Sugar Labs logo (alt) for black backgrounds==

(use only in space-confined situations)

{|
|[[Image:logo_square_black_01.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_01.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_01.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_01.png PNG]
|[[Image:logo_square_black_02.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_02.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_02.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_02.png PNG]
|[[Image:logo_square_black_03.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_03.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_03.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_03.png PNG]
|[[Image:logo_square_black_04.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_04.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_04.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_04.png PNG]
|-
|[[Image:logo_square_black_05.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_05.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_05.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_05.png PNG]
|[[Image:logo_square_black_06.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_06.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_06.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_06.png PNG]
|[[Image:logo_square_black_07.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_07.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_07.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_07.png PNG]
|[[Image:logo_square_black_08.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_08.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_08.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_08.png PNG]
|-
|[[Image:logo_square_black_09.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_09.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_09.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_09.png PNG]
|[[Image:logo_square_black_10.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_10.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_10.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_10.png PNG]
|[[Image:logo_square_black_11.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_11.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_11.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_11.png PNG]
|[[Image:logo_square_black_12.png|180px|http://www.sugarlabs.org/go/Image:logo_square_black_12.png]]
[http://www.sugarlabs.org/go/Image:logo_square_black_12.svg SVG] | [http://www.sugarlabs.org/go/Image:logo_square_black_12.png PNG]
|}

==Sugar Labs favicons==

{|
|[[Image:favicon_01.png|64|http://www.sugarlabs.org/go/Image:favicon_01.png]]
|[[Image:favicon_02.png|64|http://www.sugarlabs.org/go/Image:favicon_02.png]]
|[[Image:favicon_03.png|64|http://www.sugarlabs.org/go/Image:favicon_03.png]]
|[[Image:favicon_04.png|64|http://www.sugarlabs.org/go/Image:favicon_04.png]]
|-
|[[Image:favicon_05.png|64|http://www.sugarlabs.org/go/Image:favicon_05.png]]
|[[Image:favicon_06.png|64|http://www.sugarlabs.org/go/Image:favicon_06.png]]
|[[Image:favicon_07.png|64|http://www.sugarlabs.org/go/Image:favicon_07.png]]
|[[Image:favicon_08.png|64|http://www.sugarlabs.org/go/Image:favicon_08.png]]
|-
|[[Image:favicon_09.png|64|http://www.sugarlabs.org/go/Image:favicon_09.png]]
|[[Image:favicon_10.png|64|http://www.sugarlabs.org/go/Image:favicon_10.png]]
|[[Image:favicon_11.png|64|http://www.sugarlabs.org/go/Image:favicon_11.png]]
|[[Image:favicon_12.png|64|http://www.sugarlabs.org/go/Image:favicon_12.png]]
|}

==Color Palette==
[[Image:Color_palette.png|http://www.sugarlabs.org/go/Image:Color_palette.png]]

==SoaS Banners==
[[File:Sugar-on-a-Stick-Strawberry.png|400px]]
[[File:Sugar-on-a-Stick-Blueberry.png|400px]]
[[File:Sugar-on-a-Stick-Grape.png|400px]]
[[File:Sugar-on-a-Stick-Mirabelle.png|400px]]

==Documentation==
Sugar Labs logo PDF (2009-01-31)
http://www.sugarlabs.org/go/Image:090131_sugarlabs_logo.pdf

Sugar Labs certification badges PDF (2008-10-22)
http://www.sugarlabs.org/go/Image:081022_badges.pdf

VirtualBox

2010-05-12T07:14:19Z

Patrol:

<noinclude>{{TOCright}}
[[Category:HowTo]]
</noinclude>
With [[wikipedia:VirtualBox|VirtualBox<sup>®</sup>]] one can run [[Emulator image files|Sugar]] on Microsoft Windows, Intel-based Apple Macintosh, or Linux host computers from within a virtual machine window.

The following instructions are intended for new Learners.

(See [[VirtualBox/Technical]] for some collected details, and the [http://www.virtualbox.org/ VirtualBox.org] Web site.)
==Sugar disc images==
===Sugar on a Stick===
These are instructions for using a copy of [[Sugar on a Stick]], configured to run in a VirtualBox<sup>®</sup> virtual appliance (a virtual machine disc image ready to run in the VirtualBox host application).

* Download http://www.sugarlabs.org/static/soas/soas-strawberry-vdi.zip (dated: 24 June 2009)
* Unzip the file you just downloaded and remember where you put it - you'll get a .vdi file.
* Follow the instructions below to download and configure the VirtualBox host application.

Please be aware that this is still beta quality and not at all ready for production use. You might want to create your own VirtualBox disc image from another snapshot or iso disc file. Instructions to do so are located here, [[VirtualBox/Preparing a disk image]].

==Install VirtualBox==
=== on OS X - the Apple Macintosh operating system ===

# Download VirtualBox for OS X from here, http://www.virtualbox.org/wiki/Downloads
# If you haven't done so yet, you should start the download of the [[VirtualBox#Sugar_on_a_Stick | Sugar on a Stick vdi zip file]] (above).
# Install it by opening the DMG.
# Follow the instructions in the window
## Double click VirtualBox.mpkg
## If you see a warning about running a program from the Internet, click OK to run it.
## Click continue until you see the license popup, click Agree.
## Choose location to install, probably something like Macintosh HD, then click Continue.
## Click Continue, then Install. Enter password, if required.
# Now you can run VirtualBox by opening the Applications folder and double clicking on the icon.
# Next Follow the instructions '''Setup a Virtual Machine for Sugar on a Stick'''
#:You can watch a screencast video of the rest of the process on a Mac below in the Setup section (click the [show] link.)

=== on Microsoft Windows ===

: Download from http://www.virtualbox.org/wiki/Downloads.

=== on GNU/Linux ===
:See http://www.virtualbox.org/wiki/Linux_Downloads
:For Ubuntu, it is available in Synaptic Package Manager, once you add the the URI, distribution & components to your 3rd-party software sources or enter the following in your /etc/apt/sources.list.
::{{Code|deb <nowiki>http://download.virtualbox.org/virtualbox/debian</nowiki> <distribution> non-free}}

:Install '''dkms''', as well, so upgrades to your system will update the kernel modules.

:(See the [[Talk:VirtualBox]] page for experimental installation variations.)

==Setup a Virtual Machine for Sugar on a Stick==
{{Iframe|You can watch a screencast video of the process on a Mac here: |http://www.screencast.com/users/solutiongrove/folders/Jing/media/2ab6e487-6bee-4517-b099-a96aab0e0098
|940|896|1}}
# In VirtualBox click New
# Click Next
# Enter a name "Sugar"
# Operating System: choose Linux
# Version: choose Fedora
# Click Next
# For memory leave 256 MB
# Click Next
# Virtual Hard Disk click Existing
# Click the little folder to the right of the selection box
## A new window pops up
## Click Add button in the toolbar
## Browse to the location where you extracted the .vdi disk image
## Click Open
## Click Select
# Click Next
# Click Finish
# Select Sugar on the left
# Click Start in the toolbar
# After a minute or two you should see the Sugar screen asking for you name
# Enter your name
# Click Done at the bottom of the window. You might have to scroll.
# From now on you can start VirtualBox and start the "Sugar" virtual machine

===Issues===

* Activating the Frame might be a little difficult. The lower 2 corners are easiest and you may want to configure edge activation in the My Settings > Frame panel. With VirtualBox Guest Additions installed (see [[VirtualBox/Preparing_a_disk_image#Installing_VirtualBox_Guest_Additions| here]]), only the bottom edge and corners are available for Frame activation.

* On Mac keyboards, you might wish to change the Virtual Box default key for switching the Sugar cursor to the normal one, as the default key (control right arrow on Mac keyboards) is trapped by Sugar. (Windows and Linux keyboards use Right Ctrl.) You may do this change in File/settings of the Virtual Box menu.

==Resources==
* http://www.virtualbox.org/
* [[OLPC:VirtualBox]]
* [http://fedorasolved.org/Members/realz/VB_Guest_Addition How To Install Virtualbox Guest Additions in Fedora Guest]

Development Team/Manual/Setup

2010-05-12T06:25:45Z

Patrol: Reverted edits by Empress09 (talk) to last revision by Patrol

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
{{Developers}}
[[Developers|Previous]] [[Developers/Stack|Next]]

[[Image:Sugar.png|right|thumb|Sugar GUI Shell (Our Goal)]]
The OLPC's software environment is a heavily modified [[Community/Distributions/Fedora| Fedora]] 11 Linux system running a custom [[Sugar|GUI shell]] (Sugar). To develop for the platform you will eventually need access to a platform which runs in a manner substantially similar to the OLPC environment. To put it simply, you will likely need to have Sugar running on a computer.

There are two major approaches to running Sugar, running it natively on your machine, and running it in an emulated environment. Which approach you choose will depend on a number of factors, including:

* whether you are just wanting to check the platform out, or are setting up for long-term development work (i.e how much time you want to invest in getting the best possible setup)
* what type of hardware you have available to you
* how comfortable you are with working with traditional Linux tools such as ssh, and vim/nano editors
* what type of development work you are interested in doing

=Recommended Environments=

For Activity Developers:

* if possible, use an [[Community/Distributions/Ubuntu]]
* if you are using MS Win32 and do not want to dual-boot to Linux, use the [[OLPC:Emulating_the_XO/Quick_Start/Windows#Really_Quick_Start|QEMU Quicker Start package for Win32]] (~5 minute setup on XP, ~10 minutes on Vista)

'''If you can use either of those environments''', you can skip down to the [[#Configuration and Usage|Configuration and Usage]] section once you've completed the installation.

If you can neither run an emulated machine or run Sugar natively, it is still possible that you may be able to develop for the platform by [[#Cross Coding|Cross Coding]]. Even if this isn't possible, you could consider working on one of the [[OLPC:Software components|software components]] we use.

= About Emulation =

There are a number of tools which allow you to run an image of one operating system in a window on another system. If you have the hardware and want to get started as fast as possible, choosing an emulated approach is probably for you.

Emulation is a computationally intensive operation, it requires a powerful (modern) host machine with lots of RAM and lots of storage space. Each official image you wish to use will require about 2GB of disk storage with ancillary files and unpacking requirements.

Emulation is also a 90% thing, that is, it normally gets about 90% of the emulation correct, but things such as peripherals, sound, cameras, keyboards and the like can be "slightly off" in an emulated environment. You should always keep this in mind when working with a emulator.

== Emulation Packages/Products ==

Emulation is a hot topic these days, there are lots of emulation systems available, some no-cost, some Open Source, some commercial. We cannot hope to support all of these systems, so we have focused our efforts on small subset of systems:

* [[OLPC:QEMU]] (with the KQemu Accelerator)
** Our best-supported emulation system
** With the KQemu package provides reasonably fast emulation
** Open Source and runs well on Linux and Windows machines
** Basic setup is reasonably easy
** Allows for working in "overlays"
** Command-line interface on Windows, Linux and Mac, GUI available for Windows and Mac
** Works directly with offical builds
* [[OLPC:VMware]] / [[OLPC:VirtualBox]]
** Commercial emulation packages with no-cost "players" for images
** Somewhat easier setup than Qemu, particularly for advanced networking on Linux hosts
** Require converted images, which are not always kept up-to-the-minute and do not include experimental/testing builds
** Beta version of VMWare (Fusion) available for Mac OS X
* [[OLPC:Emulating the XO/Parallels|Parallels Desktop]]
** Commercial emulation package
** Extremely difficult setup
** Mac friendly

Which emulation system you choose is mostly a matter of preference and suitability for your system.

See Also:

* [[OLPC:Emulating the XO]] -- has a handy chart outlining which system has been reported to work with which type of emulation task

== Emulation for Exploration ==

Want to just see what Sugar is like? Want to play with the activities and kick the tires? Downloading a Qemu or VMWare/VirtualBox image and running it is normally a matter of a half hour or so.

== Emulation for Development ==

It is possible to code software on an OLPC-XO running Sugar. One of our long-term goals is to make this an easy and straightforward process. The "Gear" key on the keyboard of the OLPC-XO will eventually hook up to an [[Develop|IDE]] activity for altering and creating new code. That IDE is not yet finished, however.

''Official Images''

The only "normal" code editing environments present on the OLPC-XO are all command-line environments available through the [[OLPC:Terminal]] activity. Official Sugar images include both the vim and nano editors, so users who know these editors can use them to write and modify software within the images.

Developers wishing to use the [[OLPC:Developers/Stack#Etoys|Etoys]] application stack can create new software from Etoys built-in development environment while running on an emulator.

''Developer's Desktops''

If you have a very powerful host machine, it is possible to run an entire "regular" Linux desktop with a sugar-jhbuild or package-based install of Sugar. This will tend to take a lot more memory, processing power and disk space than using an official image (which is, of course, intended to run on a relatively lightweight computer), but it gives you most of the benefits of the native Sugar approach.

See [[#Native Sugar]]

=== Emulation for Compilation/Experiments ===

One very useful feature of emulation systems is their ability to "snapshot" or "overlay" images. This feature allows you to leave a base image untouched while performing some messy or dangerous operation. When you are finished the operation, you can return to the unmodified base image.

For example:

If you want to support a piece of hardware that requires a kernel module, you can mount a Qemu copy-on-write or VMWare snapshot into which you install the whole kernel-compilation toolset (likely getting quite close to filling up the whole storage).

You can then [[OLPC:Kernel Building|compile the kernel]] and then the missing driver. When you are finished, you copy the driver to the host machine and can install the compiled driver into the base image.

== Emulation for Testing ==

If you are [[#Cross Coding]] or using a [[#Native Sugar]] environment, you will often want to use an emulated official image for testing. This is often far more convenient than loading the image onto a real XO and doesn't require hardware you might not have.

For support operations, it is often handy to be able to load exactly the operating system image that a user is using in order to be able to duplicate a bug. You can use an emulated version of the system instead of a real XO to save "wear and tear" on the XO's flash storage.

Emulation tools often have the ability to share folders with the emulated machines, this lets you work on your host machine, quickly see if the code works on the emulator, and only then package up and test on a real machine (or potentially have someone else test).

It should be noted that emulators often have difficulties with sound support and graphics resolutions. They also can wind up being much faster or slower than the target hardware. See [[Development Team/FAQ|the Developer's FAQ]] below for some pointers on how to simulate the special hardware. Testing in emulation is valuable, but ''eventually'' the software needs to be tested on real hardware.

== Getting Started (Emulation) ==

<div style="border: solid black thin">For a detailed exploration of emulation issues with a focus on using the official images, see [[OLPC:Emulating the XO]], which includes setup and configuration issues, tips and hints, and a grid of known-working approaches to emulating an OLPC-XO laptop.</div>

You will need to install one of the emulation systems and download an image:

* [[OLPC:QEMU]] + KQemu (recommended where possible)
** [http://xs-dev.laptop.org/~cscott/olpc/streams/ship.2 Ship.2] -- patch releases for Official Releases
** [http://xs-dev.laptop.org/~cscott/olpc/streams/joyride Joyride] -- Bleeding Edge/Development Releases
** [http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1 Update.1] -- release candidates for the Update.1 refresh
* [[OLPC:VMware]], [[OLPC:VirtualBox]] (good secondary choices, particularly if you already have one installed)
** [http://dev.laptop.org/pub/virtualbox/ All Builds] -- collection of all the pre-converted images (the same images work on either system)

More complete descriptions of the various [[OLPC:OS images#Build names and branches|Image Types]] are available. Follow the specific instructions on the emulation-system-specific pages linked to above to get started.

See Also:

* [[#Configuration and Usage]] -- instructions on how to setup and use Sugar once you have it installed

= Native Sugar =

If you are running a modern Linux Operating System (whether as your primary OS, as a Live CD, via dual-booting, or potentially even via emulation), it is quite possible that you can run Sugar directly on your Linux machine with its current OS.

Core developers, as opposed to Activity developers, will likely need to set up a sugar-jhbuild environment. sugar-jhbuild uses the bleeding edge version of each component, often checked directly out of the source-code-control for each project. It allows you to work with developers across many different projects, and it tends to be fragile as a result.

Activity developers without XO hardware can use pre-built sugar that is installed as packages. For Ubuntu and some other Linux distributions, developers can run the sugar emulator to create a separate, full screen X server.

''Sugar as Your Shell''

Sugar, though a bit exotic seeming compared to most GUI shells, such as KDE or Gnome, is really just a GUI shell. As such, you can run it either as the actual shell for a GUI login session, or in a virtual X session (that is, a window that mimics a whole X session/server).

The official OLPC images, of course, run Sugar as the GUI shell for the primary X server. So if you are running an official image (for example because you are working directly on an OLPC-XO) you will be running Sugar as your GUI shell. Similarly, the [[#Live CD|Live Backup Live CD]], which is based on an official image, boots directly into the Sugar shell. On Fedora 11, you can also (with recent versions of Sugar) choose a Sugar session from your GDM/KDM/XDM-based login manager.

''Virtual X Server''

In most other cases, you want to run Sugar in a virtual X session. This allows you to have multiple Sugar desktops running and visible simultaneously to test networking and the like. The virtual X sessions can be quickly shut down and restarted without needing to log out and back in again. Most core developers are using this type of setup using sugar-jhbuild.

== sugar-jhbuild ==

This is what the core development team uses and is one of the most pleasant ways to work (once set up). Compared with using an Emulated XO, installing sugar takes more time and space to set up, and can be difficult to maintain, but results in a more flexible environment.

The 'native' environment for sugar-jhbuild is [[Community/Distributions/Fedora|Fedora]], and this is by far the best supported development platform for sugar-jhbuild. [[Community/Distributions/Ubuntu|Ubuntu]] and [[Community/Distributions/Gentoo|Gentoo]] can also build the environment.

Currently sugar-jhbuild requires about 2.5 hours to complete building on a modern workstation (AMD4800+).

You can [[OLPC:Emulated Sugar-jhbuild|run sugar-jhbuild under emulation]]. This has the advantage of working on a wider range of Linux hosts (as well as Windows or Mac OS-X), and does not "pollute" your host machine with Sugar libraries. It requires a lot of disk space and processing power, however.

See [[Development Team/Jhbuild]] to get started.

See Also:

* [[#Configuration and Usage]] -- instructions on how to setup and use Sugar once you have it installed

== Native Sugar Packages on Linux ==

As Sugar stabilizes and is ported to more distributions, it should be possible to use your Linux distribution's package management system to install Sugar. Distributions with ports so far:

* [[Community/Distributions/Ubuntu]] -- These packages seem to work well and are extremely easy to set up. If you are running on Ubuntu Gutsy and are not working on Sugar's core software, this is very simple way to work.
* [[Community/Distributions/Debian]]-- Note that we need more testing of this package-set, please let us know your experiences

If you don't see your distribution here, ask your distribution maintainers, or if you have the skills, create the packages yourself and submit them.

See Also:

* [[#Configuration and Usage]] -- instructions on how to setup and use Sugar once you have it installed

== A Real OLPC-XO Laptop ==

Hardware Developer's Program - while there are only a small number of test units available for free, developers can [[OLPC:Contributors program|submit proposals]] to receive one of those units for testing and development.

A large number of units were distributed in the Give 1 Get 1 program throughout the US or Canada. If you have sufficient funds, you can acquire a production-run machine from a secondary market such as EBay.

If you would like to run a non-official (i.e. experimental, unstable) build on a Mass-Production/G1G1 machine you will need to acquire a [[OLPC:Activation and developer keys|developer key]] to allow your (locked) laptop to load the unsigned image. You probably ''do not'' need to run an experimental image for most activity development purposes.

See Also:

* [[#Emulation for Development]] -- discussions on the current limitations on using the official images as development environments
* [http://laptop.org/start Getting Started] -- guide to using a new OLPC-XO Laptop

=== Almost an OLPC ===

The introduction of the OLPC-XO has ignited the low-cost computer market. There are a large number of low-cost machines with approximately the same performance level as an OLPC-XO. As of right now, we don't have any reason to recommend that you should buy one of these "almost an OLPC" machines, while they may be superficially similar to an XO, they are not likely to be any closer than an emulated XO running an official image.

See: [[OLPC:Development Systems]]

== Live CDs ==

There are currently a number of projects underway to produce various types of [[OLPC:LiveCD]]. LiveCDs are not a "normal" part of the development process, normally being used for lightweight deployments, experimentation, testing, and potentially installation onto a dedicated machine to create a workstation.

See [[#Emulation for Development]] for considerations regarding installing LiveCD's based on official images for development.

= Cross Coding =

If you can neither run an emulated machine nor run Sugar natively, it is still possible that you may be able to develop for the platform by developing your code on one machine and then porting it to the platform when you are finished.

Cross coding generally works best when you are working in a relatively constrained and abstracted environment. Of the stacks available on the Sugar platform, the following are well suited to Cross Coding activities:

* [[OLPC:Developers/Stack#Browser|Browser]] -- Mozilla/Firefox-derived web browser
* [[OLPC:Developers/Stack#Etoys|Etoys]] -- Squeak/Smalltalk multimedia environment
* [[OLPC:Developers/Stack#OLPCGames|Pygame]] -- raster-graphics game development framework
* [[OLPC:Developers/Stack#Flash|Flash]] -- Gnash or Adobe-Flash engine

You may be able to install just the software involved in that stack in order to test and develop your game. You can then have a development partner do porting and testing to a Sugar environment.

= Configuration and Usage =

Now that you have either a native or emulated Sugar environment, you are likely wondering how to use and configure it for your needs:

* [[OLPC:Sugar Instructions]] -- how to get around inside Sugar (i.e. how to use it)
* [[OLPC:Support]] -- how to get help with running Sugar (on an OLPC-XO)

You can install new software in your Sugar environment in a couple of ways.

* [[Activities]] -- can be downloaded using the built-in browser or installed from the command line
* General Linux packages can be downloaded and installed using Yum (note, these changes will be wiped out on the next OS upgrade)

== Jabber Servers ==

By default your image may have been configured to connect to either an inaccessible or a non-existent Jabber server. You can see this by zooming out to the network view (Alt-F1 in an emulator). If there are no other XO icons in the view you are likely not connecting to a server.

At the moment (2007-12-17) we are in the middle of rebuilding the Jabber servers to support the much larger loads seen during deployment. Ask on the #olpc IRC channel which Jabber server you should use, then open a [[OLPC:Terminal]] activity and use the following command:

sugar-control-panel -s jabber jabber.server.url

and then restart the X server, either restart the machine or use ctrl-alt-backspace (erase), but do '''not''' do ctrl-alt-backspace on an emulator, or you will kill your entire GUI session!

== SSH Access ==

You will often want to be able to use file-transfer and remote-login operations to access your Sugar environment. We generally recommend using ssh-based access for working with your Sugar environment remotely.

Note: If you are using sugar-jhbuild you likely do '''not''' need to follow these instructions (since you're already using a running Linux desktop that shares its login and file-system with the Sugar instance).

See:

* ??? SSH user's guide
** ??? SFTP user's guide and tools

=== Password Based ===

Password-based SSH authentication is convenient and simple to set up, but it is far easier to crack than key-based access. Consider using key-based authentication unless you are absolutely sure that no-one can reach your Sugar environment from untrusted networks (and maybe even then).

Open a [[OLPC:Terminal]] activity and run:

passwd

which will prompt you to enter a password (and confirm it).

Note: you can also set a password on the root account by doing:

su root
passwd

in the terminal window. This is strongly recommended if you are going to allow remote access to your machine.

=== SSH Key Based ===

SSH Key based authentication provides strong public-key encrypted access control for your Sugar environment, but takes a bit more work than SSH Password base authentication.

In summary, you create a private key which will be stored on your remote system and encrypted with a strong password. You transfer the public key (think of it as a lock) that corresponds to that key to the Sugar environment and install it as an "authenticated key" which can be used to log into the Sugar environment.

On your remote system, install SSH (Linux and MacOS will already have it installed, on Windows use the PuTTY program) and generate a new ssh key pair (following is for Linux/MacOS, refer to PuTTY's documentation for details on Windows):

ssh-keygen

Usage notes:

* Accept the defaults for key-type and size.
* If ssh-keygen asks if you want to overwrite a key say '''No''', you are about to destroy your current ssh key!
* Use a strong pass-phrase that you can remember easily (the pass phrase will need to be entered frequently unless you make use of an ssh-agent such as offered by PuTTY or Gentoo's keychain)

This will normally create a file in your ~/.ssh/ directory named id_rsa.pub (if you accepted the defaults). You now need to copy this file to your Sugar environment and add it to the contents of your ~/.ssh/authorized_keys file (you may need to create the file).

mkdir ~olpc/.ssh
cat id_rsa.pub >> ~olpc/.ssh/authorized_keys

add your key to your keychain/ssh-agent application and you can now use SSH with just a single sign-on for many concurrent actions.

See: [[OLPC:Emulating the XO/Help_and_tips#SSH into qemu|SSH Into Qemu]] for Qemu-specific notes regarding port forwarding

= See Also =

* [[OLPC:Compiling C/C++ program for the OLPC]]

* [[OLPC:Building custom images]] -- how to create entirely custom Sugar OS images using Pilgrim

[[Developers|Previous]] [[Developers/Stack|Next]]

[[Category:Emulation]]

Supported systems

2010-05-09T17:07:04Z

Patrol:

<noinclude>{{TOCright}}</noinclude>

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

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

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

=== Computer labs ===

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

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

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

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

===Starch===

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

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

===Sucrose===

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

{| class="wikitable"
|+ '''The interface, plus a set of demonstration activities'''
|-
!Operating System !! Version !! Sugar Version !! Bundled !! Tested !! [[Packaging Team|Collaboration Links]] !! Notes
|-
|colspan=7 align=center|binary packages available
|-
|[[Image:Debian.jpg|30px]]Debian||4.0||0.82||Yes||Yes|| || [[Community/Distributions/Debian | Sugar on Debian]]
|-
|[[Image:Fedora.jpg|30px]]Fedora||7,8,9||0.82||Yes||Yes|| || [[Community/Distributions/Fedora | Sugar on Fedora]]
|-
|[[Image:Ubuntu.jpg|30px]]Ubuntu||8.04 (Hardy)||0.79.0-0ubuntu3||Yes||Yes||http://wiki.ubuntu.com/SugarTeam|| [[Community/Distributions/Ubuntu | Sugar on Ubuntu]]
|-
| ||8.10 (Intrepid)||0.82||Yes|| || || [[Community/Distributions/Ubuntu#Sucrose_0.82 | Sugar on Ubuntu]]
|-
| ||9.04 (Jackalope)<br>9.10 (Koala)||0.84||Yes|| || || [[Community/Distributions/Ubuntu#Sugar on Ubuntu 9.04 (jaunty) | Sugar on Jackalope or Koala]]
|-
|[[Image:Alt_linux_team_small.png|36px]]ALT Linux||4.1<br>Sisyphus||0.82<br>SugarPlatform-0.84||Yes|||| || [[Community/Distributions/ALTLinux | Sugar on ALT Linux]]
|-
|[[Image:mandriva.png|36px]]Mandriva||2009.1<br>Cooker||SugarPlatform-0.84<br>SugarPlatform-0.84||Yes<br>Yes|||| ||[[Community/Distributions/Mandriva | Sugar on Mandriva]]
|-
|[[Image:Caixa Mágica.png|36px]]Caixa Mágica||12||SugarPlatform-0.84||Yes|| || || [[Community/Distributions/Magalhães | Sugar on Magalhães]]
|-
|colspan=7 align=center|packages not pre-built
|-
|[[Image:Gentoo-logo.svg|36px]]Gentoo||2009-03-19||0.84<br>9999||Yes|| || || [[Community/Distributions/Gentoo | Sugar on Gentoo]]
|-
|[[Image:Suse-small.jpg|36px]]OpenSUSE||11.1||0.84||Yes|| ||http://en.opensuse.org/Sugar<br>IRC Freenode #opensuse-edu|| [http://en.opensuse.org/Sugar Sugar on OpenSUSE]]
|-
|[[Image:Apple.gif|36px]]|| || || || || || [[Supported_systems/Mac|Sugar on a Mac (in emulation)]]
|-
|[[Image:Slackware.png|65px]]||Slackware 12|| || || || ||[http://wiki.laptop.org/go/Sugar_on_Slackware Sugar on Slackware]
|-
|[[Image:XP.gif|78px]]||WindowsXP|| || ||No|| || [[Supported systems/Windows|Sugar on Windows (using QEMU)]]
|}

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

{| class="wikitable"
|+ '''Complete Sugar Solutions'''
|-
!Manufacturer
!Model
!Operating System
!Tested
!Notes
|-
| [http://www.laptop.org OLPC]
| XO-1
| Fedora 9
| Yes
| Standard (reference) distribution
|-
| [http://www.asus.com ASUSTeK]
| Eee PC
|
| In initial testing phase
|
|-
| [http://www.intel.com Intel]
| Classmate Gen 1 & Gen 2
|
| under development
|
|}

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

==Updating Sugar to the Latest Version==

<span class="plainlinks">
[http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu http://wiki.sugarlabs.org/images/e/e2/Ubuntu.jpg]
</span>

===Ubuntu===

The Sugar packages in
Ubuntu 9.04 and 8.10 [http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu#Using_sugar_PPAs.]

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

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

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

<span class="plainlinks">
[http://wiki.sugarlabs.org/go/Community/Distributions/Debian http://wiki.sugarlabs.org/images/a/a1/Debian.jpg]
</span>

===Debian===

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

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

<span class="plainlinks">
[http://wiki.sugarlabs.org/go/Community/Distributions/Fedora http://wiki.sugarlabs.org/images/1/1e/Fedora.jpg]
</span>

===Fedora===

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

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

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

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

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

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

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

For more information, please refer to the announcement here:

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

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

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

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

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

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

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

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

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

# sudo olpc-update 767

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

===OLPC Clean Install===

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

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

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

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

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

# olpc-update joyride-2469

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

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

==== Other Options ====

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

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

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

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

<span class="plainlinks">
[http://wiki.sugarlabs.org/go/Community/Distributions/Gentoo http://wiki.sugarlabs.org/images/5/5e/Gentoo-logo-small.jpg]
</span>

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

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

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

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

* [[Sugar_on_a_Stick/Installation/OLPC]]

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

<span class="plainlinks">
[http://wiki.sugarlabs.org/go/Community/Distributions/ALTLinux http://wiki.sugarlabs.org/images/5/55/Alt_linux_team_tiny.png]
</span>

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

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

<span class="plainlinks">
[http://wiki.sugarlabs.org/go/Community/Distributions/Mandriva http://wiki.sugarlabs.org/images/2/2b/Mandriva.png]
</span>

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

Template:TeamHeader

2010-05-09T05:19:39Z

Patrol:

<center><div style="background-color:#{{{xbgColor|a0ff93}}}; border:1px solid #cdf; padding:0px; align:center;font-size:100%">
'''[[{{{1}}}|{{{home|{{{1}}} Home}}}]]'''   ·  
'''[[{{{1}}}/Getting Involved|{{{join_label|Join}}}]]'''   ·  
'''[[{{{1}}}/Contacts|Contacts]]'''   ·  
'''[[{{{1}}}/Resources|Resources]]'''   ·  
'''[[{{{1}}}/FAQ|FAQ]]'''   ·  
'''[[{{{roadmap_link|{{{1}}}/Roadmap}}}|{{{roadmap_label|Roadmap}}}]]'''   ·  
'''[[{{{1}}}/TODO|To Do]]'''   ·  
'''[[{{{1}}}/{{{meeting_link|Meetings}}}|{{{meeting_label|Meetings}}}]]'''
</div>
</center><noinclude>{{TOCright}}
==Purpose==

* Provide a common navigation header for [[:Category:Team]], [[:Category:Project]], or [[:Category:Local Lab]] pages.
* Add color and distinguish the categories by adjusting the header backgroud, ''xbgColor''.

==Usage==

Usually at the top of the page, enter, minimally <code><nowiki>{{TeamHeader|<home page name>}}</nowiki></code>, such as, <code><nowiki>{{TeamHeader|Wiki Team}}</nowiki></code> to produce the following:{{TeamHeader|Wiki Team}}

===Options===
====xbgColor====
The ''xbgColor'' parameter controls the header's background color.
* a0ff93, designates [[:Category:Team]] pages (default),
* ffe792 is used for [[:Category:Project]] pages, and
* ffb673 is used for [[:Category:Local Lab]] pages, for example <code><nowiki>{{TeamHeader|Sugar Labs DC|xbgColor=ffb673}}</nowiki></code> produces the following:
{{TeamHeader|Sugar Labs DC|xbgColor=ffb673}}
====home====
The home page link label defaults to the '''<home page name> Home''', but may be adjusted, such as, <code><nowiki>{{TeamHeader|Sugar on a Stick|home=Sugar on a Stick Project Home|xbgColor=ffe792}}</nowiki></code> to change the label, to produce the following:{{TeamHeader|Sugar on a Stick|home=Sugar on a Stick Project Home|xbgColor=ffe792}}
====join_label====
The 'Getting Involved' subpage link label defaults to the verb '''Join'''; but may be adjusted, such as, <code><nowiki>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}</nowiki></code> to produce the following:{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}
====roadmap_link====
The '''Roadmap''' link subpage URI may be adjusted from that default by, for example, <code><nowiki>{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</nowiki></code> (where <code><nowiki>{{Upcoming Stable Release}}</nowiki></code> is another template retuning the 'upcoming stable release' version number) to produce the following:{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}
====roadmap_label====
The '''Roadmap''' subpage link label may be adjusted by, for example, <code><nowiki>{{TeamHeader|Design Team|roadmap_link=Design Team/Vision|roadmap_label=Vision}}</nowiki></code> to produce the following: {{TeamHeader|Design Team|roadmap_link=Design Team/Vision|roadmap_label=Vision}}
====meeting_link, meeting_label====
The '''Meetings''' link subpage URI and label may be adjusted from the defaults. For example, <code><nowiki>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</nowiki></code> to produce the following: {{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}

[[Category:PageFlaggingTemplate]]
</noinclude>

Activity Team/Obsolete/Services Toolkit

2010-05-08T14:27:37Z

Patrol:

<noinclude>{{TOCright}}
[[Category:Activity Team]]
</noinclude>

== Summary ==

Everything that developers need to start developing native sugar activities. Library depends on all other Polyol components and contains glue level code that simplify creating sugar activities from scratch. This library (and all its dependencies) is an analog of the python-based sugar-toolkit library.

Bindings for this library (in contrast with bindings for other Polyol components) could contain not only wrappers for the library itself, but also particular language-specific code that makes the process of creating sugar activities in this language more comfortable.

This library is a part of [[Activity_Team/Polyol|Polyol group]].

== Contacts ==

* [[User:alsroot]]

== Current status ==

''For regular services:''

''How many branches are stable for what Sugar Platforms, note that some activities could be stuck to a particular stable branch, so do not delete your stable branches if they still work in declared sugar environments. See [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|Versioning guide]].''

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Branch [http://wiki.sugarlabs.org/go/Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme]
! Sugar Platforms
! Support status/Notes
|-
| ''0''
| ''0.82''-''1.00''
| ''is comming''
|-
|}

''For wrappers to native packages:''

This service is a [[Documentation Team/Services/Native packages usage|wrapper]] for native package, thus its versions are versions of accessible packages in the current users' environment.

== Detailed Description ==
''Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.''

== Dependencies ==
''What other services or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does your service depend on completion of another service owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Documentation ==
''Is there upstream documentation on this service, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

''If auto-documentation field is set in [[Documentation_Team/Services/Service_Developers_Guide#service.info_file|service.info]] file, API documentation will be generated on this page:''
* [http://api.sugarlabs.org/services/{{SUBPAGENAME}} API documentation]

== How To Test ==
{{:{{PAGENAME}}/Testing}}

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this service]] 

== Sources ==

* http://git.sugarlabs.org/projects/toolkit

Karma:Anatomy of a Karma Lesson

2010-05-07T02:22:38Z

Patrol: Reverted edits by Paola09 (Talk) to last revision by Eme

== Subset of an Activity ==

The name "activity" in the Sugar context roughly refers to a program with the following attributes:

* It can be launched from the Activity Circle or journal
* Is installed through an XO bundle and can be removed with the "minus" icon

In contrast, a Karma "Lesson" is much more granular than a Sugar Activity. Related Karma lessons should be aggregated into individual Sugar Activities. Karma lesson are small, discrete learning units, that introduce important concepts and give the student an opportunity to work with those concepts. Additionally, a lesson plan and Teachers' Note should be included in each Karma Lesson. These documents help the instructor facilitate the lesson, whether in formal or informal settings.

A Karma Lesson consists of 5 sections

# Introduction - Identifies the lesson and has quick links to Teacher's Note and Lesson Plan
# Reading - Can be passive or interactive but no information is recorded for the Summary. The student learns about the basic concepts in this section.
# Game (optional) - This is a fun game. May be used as a reward for good results in the Exercise
# Exercise - The student can test her knowledge in this interactive exercise. Results are recorded for display in the Summary.
# Summary - Provides a summary report on how the student did on the exercise. Can provide suggestions on how the student can improve.

There are 4 widgets in a Karma Lesson that deserve special attention
* Main Navigation
* Help Dialogue
* Page navigation
* Scoreboard

The example provided here is an Epaath lesson created by [http://www.olenepal.org OLE Nepal] in partnership with the Nepali government. Dr. Saurav Dev Bhatta, Sunil Pokharel, Om Yadav, and Kamana Regmi designed this layout.

== Sections ==

=== Introduction ===

[[image:Karma-introduction-3.png]]

1. The Back button. To return to a main navigation page

2. Background image. This is more important than one might first realize. The organization or government providing the activities will likely want to put their own custom image to "brand" the lesson. Additionally, a government insignia may reassure teachers that the material has been approved by the government.

3. Class Name and Subject

4. Name of Lesson and one line description

5. Links to pdf documents for Teacher's Note and Lesson Plan. Both should be stored locally

The Teacher's Note explains what concepts the lesson teaches and where it fits in the curriculum. The Lesson Plan provides an example of how the teacher can facilitate the lesson in the classroom.

=== Reading ===

[[image:Karma-reading-1.png]]

1. Back button

2. Navigation to Teacher's Note and Lesson Plan

3. Section Navigation. These three icons allow the student to jump between the Reading, Game, and Exercise.

4. The Help button which opens an overlay

5. Navigation between "pages" in the Reading. The Reading section only has one page but most Reading sections have multiple pages.

6. Navigation by Page # rather than arrow buttons

=== Game ===

ToDo

=== Exercise ===

[[image:karma-exercise-1.png]]

1. Scoreboard tracking the results of the students answers. A correct answer should not only change the scoreboard but say "correct" or "incorrect" each time the student enters an answer.

2. Control buttons for the Exercise. The first button is "Play", the second "Play Again", and the third goes to the Summary section. The summary section should be disabled until the student has completed the exercise.

3. Navigation within the pages of the exercise.

=== Summary ===

[[Image:Karma-summary.png]]

The red bordered rectangle is the summary of what the lesson taught.

Translated from Nepali into English, it reads "In this lesson you learned the following things . . ."

The bold text between the red-bordered box and green bordered box reads "Your last five scores are . . ."

The green bordered rectangle lists the last five scores. The columns are:
# Level
# Score
# Date
# Time

The cheetah animation is a placeholder for supplemental materials

The two buttons on the bottom are "Restart Lesson" and "Restart Exercise"

== Widgets ==

=== Help Dialogue ===

[[image:Karma-help.png]]

Tabs
# 1st tab - Help text for the reading
# 2 tab - Help text for exercise w/ numbered entries for each level. Clicking on the Number displays the help text for a particular level in the exercise
# Last tab - Exit

The default tab displayed should correspond to which section the student is currently in

Format of Help file
* 1st line - Specifies what this help page applies to "Exercise Level 1", "Reading", "Exercise Level 2"
* 2nd line - Title of activity
* Objective of lesson
* About this activity
* How to use it

=== Main Navigation ===

[[image:Karma_main_navigation.png‎]]

Navigation to the Teacher's Note and Lesson Plan

[[image:Karma_docs_navigation.png]]

=== Page Navigation ===

[[image:Karma_page_navigation.png]]

=== Scoreboard ===

[[image:Karma_scoreboard.png]]

== ToDo ==

# Where to specify the license information? Perhaps on the Introduction?
# Is the Help Dialogue contextual? Does it provide different information depending whether you are in the Reading, Game, Exercise, or Summary?

[[Category:Activities]]

Talk:SoaS Blueberry Instructions

2010-05-07T02:03:50Z

Patrol:

<noinclude>{{TOCright}}
</noinclude>
==Persistent home directory==
See [[LiveOS image]] for a discussion of storage options with the LiveOS images.
A bug somewhere in Fedora 12/Soas Blueberry prevents booting with a persistent home directory. You need to leave out the options for a separate persistent home in SoaS Blueberry installations.
*download the script:[http://download.sugarlabs.org/soas/releases/livecd-iso-to-disk.sh]
*Use this script in Terminal for soas-v2-Blueberry.iso: (/dev/sd(x)1 is your USB device) use partition manager to determine what it is.

{{Code|sudo ./livecd-iso-to-disk.sh --overlay-size-mb 400 soas-2-blueberry.iso /dev/sd(x)1}}

==Sample install to USB/SD stick==

# ./livecd-iso-to-disk.sh --overlay-size-mb 400 --delete-home ./soas-2-blueberry.iso /dev/sd(x)1
Verifying image...
./livecd-iso-to-disk.sh: line 385: checkisomd5: command not found
Are you SURE you want to continue?
Press Enter to continue or ctrl-c to abort
Copying live image to USB stick
Updating boot config file
Initializing persistent overlay file
400+0 records in
400+0 records out
419430400 bytes (419 MB) copied, 48.6429 s, 8.6 MB/s
Installing boot loader
USB stick set up as live image!
#

==Prebuilt Virtualization .vmdk & .vmx files for Virtualbox and VMPlayer==

===Virtualbox===
Prebuilt:[http://people.sugarlabs.org/Tgillard/Blueberrycleared.vdi.tar.gz][http://people.sugarlabs.org/wadeb/soas-blueberry-vmdk-1.zip]
VirualBox Program:[http://www.sun.com/software/products/virtualbox/get.jsp][http://www.virtualbox.org/wiki/Downloads]
=== VMPlayer===
Prebuilt: [http://people.sugarlabs.org/Tgillard/Blueberry-vmx.tar.gz]VMPlayer Program:[http://www.vmware.com/products/player/]ReadMe: [http://people.sugarlabs.org/Tgillard/Blueberry-vmx.txt]

* Copy the uncompressed files to a 2 GB or larger USB/SD and run it from the KEY on any computer running VirtualBox or VMPlayer

NOTE:
*The older version of the script, shown below, will complete successfully, but the new installation startup process will have trouble finding the home folder and fail to complete.

=Older versions of SOAS:=
Normally,the livecd-iso-to-disk installation has the advantage over the liveusb-creator installation method by allowing a persistent /home/liveuser folder with the --home-size-mb NNN option.
This feature would allow you to update the OS image while keeping the user files (by running the script against your existing installation but leaving out the --home-size-mb NNN option).
* Run it as root, making sure to pass the correct USB device and to set overlay and home size appropriately, depending on the stick size.

{{Code|sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-strawberry.iso /dev/sd(x)1}}

* The --delete-home option is used to avoid an error message while requesting both a new home (with --home-size-mb) and a persistent home (indirectly with --unencrypted-home). You wouldn't use the --delete-home option on an upgrade of the operation system only.
Depending on the size of your USB stick, you may have to decrease --overlay-size-mb and --home-size-mb values (for example, for a 1-GB stick, use 200 for each).

* Watch out for errors in the output of the script, the script seems to ignore them! (and say all is fine on the last line).

:(The above was copied and revised from: [[Sugar_on_a_Stick/Linux]].)

==Using boot helper disk with blueberry usb on Intel Mac==
See [[Sugar on a Stick/Mac]].

Question #95622 on Sugar on a Stick changed:
https://answers.edge.launchpad.net/soas/+question/95622
* edited for clarity (04/08/2010)

lisfolks posted a new comment:
So, I didn't have to make any changes to the image on the USB. This is
what I do to make it work:

# Restart my MacBook Pro with the Blueberry imaged USB and the Boot Helper CD in place.
# Hold the 'C' key from the time the screen becomes black on the restart until the CD's boot screen comes up.
# At the boot screen, press Tab key to enter into the boot/kernel parameters screen.
*This screen shows default values as follow:
vmlinuz0 initrd=initrd0.img root=LABEL=FEDORA rootfstype=vfat rw liveimg overlay=LABEL=FEDORA quiet rhgb
*(note that there are actually two spaces between quiet and rhgb)
#Using the arrow keys, move the cursor to the end of 'root=LABEL=FEDORA', backspace out the 'FEDORA', and replace it with 'soas-2-blueberry' (without the quotes, of course).
# Arrow to the end of 'rootfstype=vfat', then press backspace to remove the 'vfat' portion. Replace it with 'iso9660' (again, without the quotes).
# Arrow to the end of the command line (one space after the 'rhgb' parameter). Add 'selinux=0' (that's a zero, and again, leave out the quotes).'
# Hit return and (hopefully) boot USB into sugar

==More Linux Information==
[[Sugar_on_a_Stick/Linux#Put_SoaS_onto_a_stick_using_Fedora_or_Ubuntu]]

Downloads

2010-05-07T01:04:29Z

Patrol:

<noinclude>{{ Translations | [[Downloads|english]] | [[Downloads/lang-es|español]] | [[Downloads/lang-fr|français]] | [[Downloads/lang-no|Norsk]] }}</noinclude>

{{:Sugar_on_a_Stick/Pancake page}}

==Are you a Windows, Macintosh, or GNU/Linux user?==
See specific instructions from the [[Sugar on a Stick/Blueberry|Sugar on a Stick, v2 Blueberry]] release for your operating system by clicking its icon below:

[[Image:Windows.gif|link=Sugar on a Stick/Blueberry#For_Windows_Users]]
[[Image:Gnulinux.png|link=Sugar_on_a_Stick/Blueberry#For_GNU.2FLinux_Users]]
[[Image:Apple.gif|link=Sugar_on_a_Stick/Blueberry#For_Mac_OS_X_Users]]

==Are you a developer or Beta tester?==

Please select your favorite distribution below for instructions on installing Sugar.

[[Image:Logo SoaS 03.png|120px|link=Sugar_on_a_Stick/Beta]], v3 Beta with Sugar 0.88 and Fedora 13 alpha

[[Image:Trisquel_icon.png|link=Trisquel On A Sugar Toast]] Trisquel on a Sugar Toast (Trisquel 3.0 ''Dwyn'')

[[Image:Fedora-small.jpg|link=Community/Distributions/Fedora]]
[[Image:Debian-small.jpg|link=Community/Distributions/Debian]]
[[Image:Ubuntu-small.jpg|link=Community/Distributions/Ubuntu]]
[[Image:Gentoo-small.png|link=Community/Distributions/Gentoo]]
[[Image:Altlinux-small.png|link=Community/Distributions/ALTLinux]]
[[Image:Mandriva-small.png|link=Community/Distributions/Mandriva]]
[[Image:Caixa_M%C3%A1gica-small.jpg|link=Community/Distributions/Magalhães]]
[[Image:Suse-small.jpg|link=http://en.opensuse.org/Sugar]]
[[Image:Suse-small.jpg|link=http://en.opensuse.org/Education/Live|Education/Live]]
[[Image:Trisquel_icon.png|link=Community/Distributions/Trisquel]]

==Do you have an OLPC XO-1?==
===Upgrade to Sugar 0.84 with Fedora 11 and Gnome ===
See [[Talk:Downloads#Upgrade an XO-1 to Sugar 0.84 with Fedora 11 and Gnome | these instructions]].

===Intrepid developers may experiment with [[Sugar_on_a_Stick/Installation/OLPC|Updating your XO]] to the latest Sugar release.===

[[Image:OLPCXO.png|link=Sugar on a Stick/Installation/OLPC]]

==Are you looking for Sugar Activities?==
Please visit our dedicated [http://activities.sugarlabs.org Sugar Activity Library].

[[Image:Sugarlabs_mainpage_02.png|link=http://activities.sugarlabs.org]]

==Are you a developer?==

Learn how to get setup on the [[Supported systems]] page.

[[Image:Gear.png|link=Supported_systems]]

Here are some additional references you may find useful:
* [[Development Team/Jhbuild | jhbuild]]
* [http://git.sugarlabs.org Gitorious source code repository]
* [[Emulator image files|Virtual machine or emulator image files]]

* Adding Sugar to your [[Supported systems|favorite distro...]]

__NOTOC__
__NOEDITSECTION__

Marketing Team/Events

2010-04-28T15:06:57Z

Patrol: /* Upcoming Events */

<noinclude>{{TeamHeader|Marketing Team}}{{TOCright}}
[[Category:Event]]</noinclude>

== Add an Event ==

Would you like to represent Sugar Labs at an event near you? Follow this simple process.

# Create a new page on the wiki, using [[User:Gdk/Events/PyCon2009]] as an example.
# Link to the event in the [[#Upcoming Events]] section, below.
# Send an email to '''events at sugarlabs dot org''' to have the event added to the official Google calendar of events.
#: ''mail.sugarlabs.org'' account holders may follow [[Sugar_Labs/Events/Instructions | these instructions]].

== Events: Google Calendar ==

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

== Upcoming Events ==

Sugar Labs has committed to having a presence at the following events.

{| class="schedule sortable" border="1"
! Date !! Event !! Location !! Owner !! Details
|-
| 2009-06-09 – 2009-06-12 || [http://www.linuxtag.org/2010/en.html LinuxTag 2010] || Berlin, Germany || [[User: Erikos| Simon Schampijer]] || [[Marketing Team/Events/LinuxTag2010|LinuxTag 2010]]
|-
| 2010-04-03 – 2010-04-17 || [http://www.sciencefestival.co.uk/ Science Fest 2010] || Edinburgh, UK || [[User:Garycmartin| Gary C Martin]] || [[Marketing Team/Events/ScienceFest2010|Science Fest 2010]]
|-
|2010-01-18 – 2010-01-23 || [http://www.lca2010.org.nz/ LCA2010 website] || Wellington, NZ || [[User:Tabitha| Tabitha Roder]] || [[User:Tabitha/Events/LCA2010 | LCA2010]]
|-
| 2009-11-22 || [http://www.nyscate.org/conferences.cfm?subpage=361 NYSCATE 2009] || Rochester, NY USA || Stephen Jacobs & Gerald Ardito || [http://www.nyscate.org/conferences.cfm?subpage=414 NYSCATE 2009 Session page]
|-
| 2009-11-07 – 2009-11-12 || [http://www.sfscon.it/2009 SFScon 2009] || Bolzano, Italy || || [[Marketing Team/Events/Sugarcamp_Bolzano_2009 |SugarCamp Bolzano 2009]]
|-
| 2009-11-06 – 2009-11-07 || [http://nz.pycon.org/ Kiwi PyCon 2009] || [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=200+Armagh+St,+Christchurch,+Canterbury+8011&sll=-41.305383,174.763281&sspn=0.037783,0.077162&ie=UTF8&hq=&hnear=200+Armagh+St,+Christchurch,+Canterbury+8011,+New+Zealand&z=16 Christchurch, New Zealand] || [[User:TimClicks | Tim McNamara]] || [[Marketing_Team/Events/KiwiPyCon | KiwiPyCon 2009 is New Zealand's general Python conference]]
|-
| 2009-10-27 – 2009-10-29 || [http://www.masscue.org/ MassCUE] || near Boston, MA, USA || || [[Marketing Team/Events/MassCUE2009|MassCUE 2009]]
|-
| 2009-06-28 – 2009-07-01 || [http://center.uoregon.edu/ISTE/NECC2009/ NECC 2009] || Washington DC, USA || || [[Marketing Team/Events/NECC2009|NECC 2009]]
|-
| 2009-06-24 – 2009-06-27 || [http://www.linuxtag.org/2009/en.html LinuxTag 2009] || Berlin, Germany || [[User: Erikos| Simon Schampijer]] || [[Marketing Team/Events/LinuxTag2009|LinuxTag 2009]]
|-
| 2009-03-25 – 2009-04-02 || [http://us.pycon.org/2009/about/ PyCon 2009] || Chicago, IL, USA || [[User:Gdk | Greg DeKoenigsberg]] || [[User:Gdk/Events/PyCon2009|PyCon 2009]]
|-
| 2009-02-07 – 2009-02-08 || [http://fosdem.org FOSDEM 2009] || Brussels, Belgium || [[User: ChristophD| Christoph Derndorfer]] || [[Marketing Team/Events/FOSDEM_2009|FOSDEM 2009]]
|-
| 2009-01-19 – 2009-01-24 || [http://linux.conf.au/ linux.conf.au 09] || Hobart, Tasmania || [[User:Walter | Walter Bender]] || [[User:Walter/Events/Linux.conf.au09|LCA 09]]
|-
| 2008-12-02 – 2008-12-05 || [http://osdc.com.au/2008/ Open Source Developers Conference (OSDC)] || Sydney, Australia || [[User:joel | Joel Stanley]] || [[User:Joel/Events/OSDC2008 | OSDC 2008]]
|-
| 2008-11-24 – 2008-11-26 || [http://www.vitta.org.au/conferenceinfo Victorian IT Teachers Association (VITTA) conference] || Melbourne, Australia || [[User:joel | Joel Stanley]] || [[User:Joel/Events/VITTA2008 | VITTA 2008]]
|-
| 2008-11-13 – 2008-11-14 || [http://www.sfscon.it/2008/ South Tyrol Free Software conference (SFScon)] || Bolzano, Italy || [[User:Walter | Walter Bender]] || [[User:Walter/Events/SFScon08|SFScon 08]]
|-
| 2008-10-27 – 2008-10-30 || [http://www.cmp-egevents.com/web/escb ESC 2008] || Boston, MA, USA || [[User:Bernie | Bernie Innocenti]] || [https://www.cmpevents.com/ESCe08/a.asp?option=C&V=11&SessID=8164 Constructionist learning with Sugar and the Beagle Board]
|-
| 2008-10-26 – 2008-10-28 || [http://www.sarasotadesignsummit.com Sarasota International Design Summit] || Sarasota, FL, USA || [[User:Walter | Walter Bender]] || [[User:Walter/Events/Sarasota-Design-Summit|Sarasota Design Summit]]
|}

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

Template:Block

2010-04-27T06:18:44Z

Patrol:

<big><pre>{{{1}}}</pre></big><noinclude>

==Usage==

{{Template:Block|<nowiki>{{Block|code block}}</nowiki>}}

Used to display a block of code in an enlarged, monospace typeface within a gray block like the following:

:{{Block|#!/bin/bash -x<br>
alskdjf<br>
alskjf
#
# The -x above and the export PS4 (debug prompt) assignment below will help in debugging
# long scripts by reporting the line number : script : effective userid : function names
# to the standard output by through the environment variables.
#
#
export PS4='+(${LINENO}:${BASH_SOURCE}:${EUID}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'
#
# script code to follow.
}}

See also [[:Template:Code]] for {{Code|code lines or words}}.
</noinclude>

Template:Block

2010-04-27T06:07:34Z

Patrol:

<big><pre>{{{1}}}</pre></big><noinclude>

==Usage==

{{Template:Block|<nowiki>{{Block|code block}}</nowiki>}}

Used to display a block of code in an enlarged, monospace typeface within a gray block like the following:

{{Block|#!/bin/bash -x
#
# The -x above and the export PS4 (debug prompt) assignment below will help in debugging
# long scripts by reporting the line number : script : effective userid : function names
# to the standard output by through the environment variables.
#
#
export PS4='+(${LINENO}:${BASH_SOURCE}:${EUID}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'
#
# script code to follow.
}}

See also [[:Template:Code]] for {{Code|code lines or words}}.
</noinclude>

Template:Code

2010-04-27T06:04:22Z

Patrol:

<big><code>{{{1}}}</code></big><noinclude>

==Usage==

{{Code|<nowiki>{{Code|code line}}</nowiki>}}

See also [[:Template:Block]] for code blocks.

Used to highlight code samples in an enlarged, monospace typeface that is easier to read than the default.
</noinclude>

Template:Block

2010-04-27T06:03:14Z

Patrol:

<big><pre>{{{1}}}</pre></big><noinclude>

==Usage==

{{Block|<nowiki>{{Block|code block}}</nowiki>}}

Used to display a block of code in an enlarged, monospace typeface within a gray block like the following:

{{Block|#!/bin/bash -x}}
#
# The -x above and the export PS4 (debug prompt) assignment below will help in debugging
# long scripts by reporting the line number : script : effective userid : function names
# to the standard output by through the environment variables.
#
#
export PS4='+(${LINENO}:${BASH_SOURCE}:${EUID}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'
#
# script code to follow.
}}

See also [[:Template:Code]] for {{Code|code lines or words}}.
</noinclude>

Template:Block

2010-04-27T05:57:49Z

Patrol: Created page with '<big><pre>{{{1}}}</pre></big><noinclude> ==Usage== {{Block|<nowiki>{{Block|code block}}</nowiki>}} Used to display a block of code in an enlarged, monospace typeface within a …'

<big><pre>{{{1}}}</pre></big><noinclude>

==Usage==

{{Block|<nowiki>{{Block|code block}}</nowiki>}}

Used to display a block of code in an enlarged, monospace typeface within a gray block like the following:

{{Block|
#!/bin/bash -x
#
# The -x above and the export PS4 (debug prompt) assignment below will help in debugging
# long scripts by reporting the line number : script : effective userid : function names
# to the standard output by through the environment variables.
#

export PS4='+(${LINENO}:${BASH_SOURCE}:${EUID}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'

# script code to follow.
}}

See also [[:Template:Code]] for {{Code|code lines or words}}.

Talk:Sugar on a Stick/Linux

2010-04-27T05:30:32Z

Patrol:

==SoaS Fedora matrix==
{|cellpadding=3 style="background: #fafafa; padding: 3px; border: 1px solid #cdcdcd"
! SoaS<br>version !! Release<br>name !! OS<br>version !! disc image files
|-
|align="center"| alpha
|align="center"| --
|align="center"| Fedora 10
| (unavailable as of 04 October 2009)
|-
|align="center"| alpha, beta
|align="center"| --
|align="center"| Fedora 11
| http://download.sugarlabs.org/soas/snapshots/1/
|-
|align="center"| beta
|align="center"| --
|align="center"| Fedora 11
| http://download.sugarlabs.org/soas/releases/soas-1-beta.iso
|-
|align="center"| v1
|align="center"| Strawberry
|align="center"| Fedora 11
| http://download.sugarlabs.org/soas/releases/soas-1-strawberry.iso
|-valign="top"
|align="center"| v2 alpha, beta
|align="center"| --
|align="center"| Fedora 12
| http://download.sugarlabs.org/soas/snapshots/2/<br>(includes builds for the XO-1 hardware<br>and the .zip file contains a .vmdk virtual appliance for VirtualBox or VMware)
|-
|align="center"| v2
|align="center"| Blueberry
|align="center"| Fedora 12
| http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso
|-
|align="center"| v3 alpha, beta
|align="center"| --
|align="center"| Fedora 12 (presently)
| http://download.sugarlabs.org/soas/snapshots/3/
|-
|align="center"| v3 Nightly Composes soas
|align="center"| --
|align="center"| Fedora 13 (Goddard)
|http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/
|-
|align="center"| v3
|align="center"| Mirabelle
|align="center"|
|}
* The snapshots subfolder number now matches the release lineage version number. Before 04 October 2009 it referred to the Fedora version since the original SoaS (1 = Fedora 10, 2 = Fedora 11, 3 = Fedora 12), but the subfolders have be repurposed (the older filenames, ''e.g.'', Soas2-YYYYMMDDHHMM.iso, still bear the original series number code).
* Beginning on 04 October 2009, SoaS and SoaS-XO-1 images share the same codebase. Image filesnames follow a simple numbering scheme beginning with soas01.* for Sugar on a Stick and soasxo01.* for that codebase with the XO-1-specific kernel.
* Nightly SoaS Spins are now being built on Fedora's nightly -composes page (If it is blank, the build did not complete)

== Page restructure needed==

Let us please use this SoaS/Linux page primarily to provide background support for the installation of the stable SoaS release reported on the main SoaS page, and provide links to sub pages for all the other distributions and experimental and exploratory variations.

This page would be more valuable if it provided more easy to follow detail and explanations for the Linux installation steps and an index to the other options advanced users or developers might want to investigate.

Sugar on a Stick

2010-04-27T05:28:13Z

Patrol:

<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 [[LiveOS image|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 [[BugSquad/Bug Report|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.

<div class="NavFrame collapsed"><div class="NavHead">'''Subpage index''' </div><div class="NavContent">{{Special:PrefixIndex/{{PAGENAME}}/}}</div></div>

LiveOS image

2010-04-27T05:23:25Z

Patrol: Created page with '<noinclude>{{TOCright}} Category:Live USB </noinclude> ==Introduction== Fedora has developed wikipedia:Live CD| USB DVD images for their GNU/Linux…'

<noinclude>{{TOCright}}
[[Category:Live USB]]
</noinclude>

==Introduction==
Fedora has developed [[wikipedia:Live CD|Live CD]] [[wikipedia:Live USB|USB]] DVD images for their GNU/Linux operating system. Since they store the image file systems on the devices in the /LiveOS folder, this is the name we'll use to reference their product.

This page shares some information about the LiveOS design that helps [[Sugar on a Stick]] Learners make better use of their resources.

==References==

* [[fedora:FedoraLiveCD|FedoraLiveCD]]
* [[fedora:How to create and use a Live CD|How to create and use a Live CD]]
* [[fedora:How to create and use Live USB|How to create and use Live USB]]

==Storage==
The Fedora LiveOS system allows for persistent storage in 3 ways:

# A general persistent overlay - a compressed, write-once, fixed-size file space that will save updates and changes the LiveOS image (Activities, operating system changes, anything written in the LiveOS file space.
# Persistent Home folder - a re-sizable (with difficulty), uncompressed, optionally-encryptable, file space for anything that goes in the Learner's /home/ folder (all the Sugar Activities, logs, and good stuff).
# The device's original partition file space - outside of the LiveOS file tree, but accessible through the /mnt/live folder mount point. There, one will find the boot configuration files and anything else one had on the device before loading SoaS. Any file one might want to carry on the stick, without consuming the other limited file spaces, may be saved here (limited by device capacity).

The standard persistent overlay is needed for operating system changes and updates.

But, one may find many advantages to installing Sugar on a Stick with a persistent home folder (--home-size-mb NN --delete-home) that
will hold all the Activities one wants to try and, perhaps later, throw away--all without consuming the write-once overlay that would
fill up very quickly.

Additionally, keeping some device disc storage space out of the LiveOS system will let you copy, carry, and delete large resource files, such as alternate image .iso files, or anything you might want to use or share. (We should adjust the Journal code to show
this root mount to facilitate file sharing.)

Sugar on a Stick may be installed on a 1-GB USB device using these options to livecd-iso-to-disk or modified_livecd-iso-to-disk (on one Terminal Activity or console command line, even though the wiki may wrap the following text according to your browser window size):

:{{Code|./livecd-iso-to-disk --overlay-size-mb 200 --home-size-mb 200 --delete-home --unencrypted-home /path/to/source/iso/or/device /dev/sd''A''1}}

:: where '{{Code|''A''}}' in the final parameter represents the target bootable device node, such as {{Code|sdb1}} or {{Code|sdc1}}, etc.
:: (You may use '\' line-continuation symbols followed by a newline [enter or return keypress] to break a long line visually on the terminal, but not logically to the script processing software.)

That would allow space for the home folder, the operating system, and a little on the device root.

But with a larger storage device, one can allocate the resources to suit the anticipated use as described above.

==File Systems==

The Fedora LiveOS uses the [[wikipedia:Device mapper|Device-mapper]] service of the Linux kernel to manage the file stores on the device. This is the same service that is used by [[wikipedia:Logical Volume Manager (Linux)|Logical Volume Manager]] to provide disc partition services.

One limitation, mentioned above, is that the LiveOS persistent overlay is a write-once file space. This is related to its use of device mapper snapshots to merge a read-only file system image with a [[wikipedia:Copy-on-write|Copy-on-write]] service that tracks only changed bits of data in the snapshot file and re-referencing any pointers to the updated bits. Any changes to the operating system files are stored as differences from the base. As such, "deletions" of files are saved as additional difference references, and the originals are hidden and physical storage space is consumed in the write-once file space rather than recovered.

To track the consumption of the space allocated for persistent storage, the snapshot overlay file, the device mapper service ''dmsetup'' provides a status report. '''Sugar Cellar''' is a small utility script that uses that service to allow for Learner testing and discovery. This will help Learners manage their storage resources and learn ways to economize limited resources.

* ''Sugar Cellar'' is available at http://people.sugarlabs.org/fgrose/SugarCellar and as a component of [[Sugar on a Stick/Sugar Clone]].

Template:Code

2010-04-27T05:10:23Z

Patrol:

<big><code>{{{1}}}</code></big><noinclude>

==Usage==

{{Code|<nowiki>{{Code|code text}}</nowiki>}}

Used to highlight code samples in an enlarged, monospace typeface that is easier to read than the default.
</noinclude>

Template:Code

2010-04-27T05:08:25Z

Patrol:

<big><code>{{{1}}}</code></big><noinclude>

==Usage==

<big><code><nowiki>{{Code:code text}}</nowiki></code></big>

{{Code:{{Code:code text}}}}

Used to highlight code samples in an enlarged, monospace typeface that is easier to read than the default.
</noinclude>