Sugar Labs - User contributions [en]

Deployments/HolyMotherSchool

2010-02-27T05:29:05Z

Jpritikin: /* Summary */

<noinclude>{{TOCright}}
[[Category:Deployment|Holy Mother School]]
</noinclude>





== Summary ==

Small deployment in Nashik, India

== Contact ==
* Name: [[USER:Jpritikin|Joshua Pritikin]]

* Email: mailto:jpritikin@pobox.com

== Location ==
Nashik, Maharashtra, India

== Language ==
en_US, hi_IN

== Size ==

We have about 100 students. We would like to try child ownership of the laptops, but lack the necessary funds. The laptops are only used at school. There is no IT staff. My wife and I visit during the summer and try to patch things together as best as possible for the rest of the year. It is not clear to me how much the teachers or students are learning, but the parents are impressed.

== Hardware ==

We have a relatively stable electrical supply for India. The power is off for only 3-4 hours per day. We invested in a tubular battery and inverter large enough to handle the 30 laptops. We also have a single school server (P-3 class) running the XS distribution with moodle and an Acer projector for presentations.

== Technical Details ==
* Sugar version: 0.82 and a few machines with early SoaS builds

* OS distribution: mostly 8.2.1 (build 802)

== Activity Usage ==

Not sure.

== Curriculum ==
It is fairly haphazard, as far as I know.

== History ==
My wife and I started an English medium elementary school in 2004. Being a software engineer, I was eager to try OLPC laptops when they became available in India.

== Links ==

http://wiki.laptop.org/go/OLPC_India/Nashik

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

Deployments/HolyMotherSchool

2010-02-27T05:28:41Z

Jpritikin:

<noinclude>{{TOCright}}
[[Category:Deployment|Holy Mother School]]
</noinclude>





== Summary ==
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

== Contact ==
* Name: [[USER:Jpritikin|Joshua Pritikin]]

* Email: mailto:jpritikin@pobox.com

== Location ==
Nashik, Maharashtra, India

== Language ==
en_US, hi_IN

== Size ==

We have about 100 students. We would like to try child ownership of the laptops, but lack the necessary funds. The laptops are only used at school. There is no IT staff. My wife and I visit during the summer and try to patch things together as best as possible for the rest of the year. It is not clear to me how much the teachers or students are learning, but the parents are impressed.

== Hardware ==

We have a relatively stable electrical supply for India. The power is off for only 3-4 hours per day. We invested in a tubular battery and inverter large enough to handle the 30 laptops. We also have a single school server (P-3 class) running the XS distribution with moodle and an Acer projector for presentations.

== Technical Details ==
* Sugar version: 0.82 and a few machines with early SoaS builds

* OS distribution: mostly 8.2.1 (build 802)

== Activity Usage ==

Not sure.

== Curriculum ==
It is fairly haphazard, as far as I know.

== History ==
My wife and I started an English medium elementary school in 2004. Being a software engineer, I was eager to try OLPC laptops when they became available in India.

== Links ==

http://wiki.laptop.org/go/OLPC_India/Nashik

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

Deployments/HolyMotherSchool

2010-02-27T05:15:52Z

Jpritikin: Created page with '<noinclude>{{TOCright}} Holy Mother School </noinclude> '''Comments and Explanations:''' There are comments (in italic) providing guidance to fill out e…'

<noinclude>{{TOCright}}
[[Category:Deployment|Holy Mother School]]
</noinclude>

'''Comments and Explanations:'''

There are comments (in italic) providing guidance to fill out each section, see also the [[Deployments/Policy|Deployment Policy Page]] for a more detailed explanation of the deployment documentation process. '''Copy the source to a ''new page'' named Deployments/''Your Deployment Name'' before making changes! DO NOT EDIT THIS TEMPLATE.'''





== Summary ==
''A sentence or two summarizing this Sugar deployment. This information is used for the deployment summary page.''

== Contact ==
''This should link to one or more people who are willing to act as ambassadors between Sugar Labs and this deployment.''
* Name: [[User:AcountName| Your Name]]

''Include your email address that you can be reached should people want to make contact with this deployment''
* Email: <your email address so we can contact you, invite you to meetings, etc.>

== Location ==
''Describe the location of the deployment''

== Language ==
''What language does the deployment use? Include the language code, e.g. en_US, if possible.''

== Size ==
''Describe the number of students, teachers, and IT staff using Sugar.''

== Hardware ==
''Describe the number and type of computers Sugar is running on, e.g. 150 OLPC XO-1 Laptops. Also describe any servers used and what software they run. Additional equipment, like solar power generators, can also be included.''

== Technical Details ==
''This should list which version of Sugar is being used, e.g. 0.82 or SoaS Blueberry.''
* Sugar version: 0.82 and a few machines with early SoaS builds

''Describe the base operating system being used, e.g. Fedora 12.''
* OS distribution: mostly 8.2.1 (build 802)

== Activity Usage ==
''Describe which Sugar activities are used in the classroom.''
* <ACTIVITY 1>
* <ACTIVITY 2>

== Curriculum ==
''Provide any notes about how Sugar is being used in the classroom.''

== History ==
''Describe how and when the deployment got started, its growth and changes, etc.''

== Links ==
''Provide links to deployment websites, additional wiki pages, studies, papers, etc.''

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

Deployment Team/Places

2010-02-27T05:13:24Z

Jpritikin:

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Deployment Team}}{{TOCright}}</noinclude>
=== Introduction ===

This page lists the places in the world where Sugar is used along with a contact person that will facilitate communication between the global and the local communities.

The column "# of members" is intended to give a rough estimation of the size of the local community and may include children, educators, parents, volunteers, etc

=== Asia ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Maharashtra, India
| English, Hindi, Marathi
| 32
| [[USER:Jpritikin|Joshua Pritikin]]
|-
| Nepal
| Nepali
| 50
| Subir Pradhanang, Rabi Karmacharya
|-
| Quezon City, Philippines
| Filipino, English
| 30
| [[USER:Jgotangco|Jerome Gotangco]]
|-
| BanSamka, Thailand
| Thai
| ~30 OLPC XO (beta-2 machines?)
| Arnan Sipitakiat?
|}

=== Africa ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! Software
! Hardware
! # of members
! Contact
|-
| Ethiopia
| Amharic
| ?
| OLPC XO-1
| ?
| ?
|-
| Rwanda
| English?
| ?
| OLPC XO-1
| ?
| David Cavallo?
|-
| [http://bethstepsup.blogspot.com São Tomé e Príncipe]
| Portuguese
| ?
| OLPC XO-1
| ?
| [mailto:elizabeth.ann.santos@gmail.com Beth Santos]
|-
| Nigeria
| English?
| ?
| OLPC XO-1
| ?
| Schumberger?
|}

=== America ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! Software
! Hardware
! # of members
! Contact
|-
| Colombia
| Spanish
| Fedora 11/Sugar - LiveCDs - SOAS
| Desktop PCs
| 7
| RafaelOrtiz
|-
| Peru
| Spanish
| ?
| OLPC XO-1
| ?
| Hernan Pachas?
|-
| Uruguay
| Spanish
| Build 802
| OLPC XO-1
| 360.000
| Pablo Flores?; [[User:Dcastelo|Daniel Castelo]]; [[User:earias|Esteban Arias]]
|-
| Paraguay
| Spanish
| ?
| OLPC XO-1
| 4500
| Raul Gutierrez S.
|-
| Chiapas, Mexico
| Spanish, Tzotzil
| SoaS Strawberry on SD cards + ejabberd server
| Classmate Convertible
| 44, three rural classrooms
| [[User:Jose Icaza|Jose I. Icaza]]; [http://sites.google.com/site/tecnotzotzil TecnoTzotzil] project site in English
|-
| Bermingham, AL, USA
| English
| ?
| OLPC XO-1
| ?
| ?
|-
| Boston, MA, USA
| English
| SoaS Strawberry (0.84)
| HP EVO 500 desktops
| ?
| Caroline Meeks
|}

=== Europe ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of Sugar installations
! Hardware used
! Software version
! Project blog/wiki
! Contact
|-
| Graz, Austria
| German
| 25
| XO-1
| build 767
| [http://elearningblog.phst.at/?cat=32 blog] (in German)
| David Van Assche, [[User:ChristophD|Christoph Derndorfer]]
|-
| London, United Kingdom
| English
| 30
| XO-1
| build 802
| [http://olpc.org.uk/ blog], [http://lists.laptop.org/listinfo/olpc-uk mailing list], [http://wiki.laptop.org/go/OLPC_UK wiki]
| [[User:PeterRobinson|Peter Robinson]], [[User:MartinDengler|Martin Dengler]]
|-
| Brescia, Italy
| Italian
| ?
| XO-1
| ?
| [http://escuola.provincia.brescia.it/olpc/ website] (in Italian)
| ?
|-
| Milan, Italy
| Italian
| 30
| XO-1
| build 802
| none
| Comunità Nuova/Barrio's - Mario Lenelli (?)
|}

=== Oceania ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Solomon Islands
| Pijin, Marovo
| ?
| David Leeming?
|}

=== See also ===

See also [[OLPC:Deployments]]

Development Team/Project Ideas

2009-09-22T09:30:39Z

Jpritikin: /* Port LopArt to Sugar */

<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>
==Introduction==
This page contains a list of project ideas. For now, the focus is on giving [[GSoC]] students an idea of the kind of thing we're looking for. Summer of Code applicants should also visit '''[[Summer of Code/Resources]]'''.

At the bottom of this page is a section for less-explicitly-explained & wild ideas.

==[[Summer of Code]]==

'''Priorities''': see the [http://lists.sugarlabs.org/archive/iaep/2009-March/004592.html ongoing discussion of priorities] on our mailing list. To summarize that thread: the highest priority is for you to have a successful GSoC, which should bias you towards easier projects such as [[#Stand-alone activities]]. But, if we had to rank this list in terms of priorities for Sugar, the [[#AJAX Sugar aka Karma]] and [[#Versioned Datastore]] ideas are probably our highest priorities, followed by the rest of the [[#Toolkits / Frameworks for developers]]. These are generally hard, though, so we would need you to give us evidence that you are capable, in order for us to accept you for these ideas.

* There is a similar, project-ideas page on the [[OLPC:Summer_of_Code/Ideas | OLPC wiki]] (and a related [[OLPC:Category:GSoC_proposals | category]]). OLPC-specific projects, including hardware- <s>and schoolserver-</s>related projects, should go there. ''Update: since OLPC did not get into GSoC this year, we would consider mentoring school-server related projects.'' Feel free to add below relevant projects from that list - perhaps <s>80%</s> 95% of these could be appropriate Sugar Labs applications.

===See something that interests you? (steps to apply)===
To get in, you will need to design your project and find a mentor. On irc (#sugar on freenode) or the sugar-devel mailing list, you can briefly introduce yourself, state your interest, and ask relevant and specific questions about the state of the existing code. You should also do your own research for other open-source code that might help you. Get a [[Development Team#Development_systems|development environment]] installed. We definitely appreciate it if you can show your readiness to help out - either joining [[BugSquad|bug squad]] and [[BugSquad/Meetings|helping]] to [[BugSquad/Triage Guide|triage]], or actually helping fix some small [http://tinyurl.com/ctfkjl bug] (we've categorized [http://tinyurl.com/sugar-love some bugs as "sugar-love"], which means, not that they are easy to fix, but that they are good for beginners because they don't require much expert knowledge).

When you're ready, figure out a very basic, preliminary design (where does your new UI fit in? what about the code - what talks to what?) and post that to the [[Sugar_Labs/Contacts#Developer_Lists|mailing list]], asking if anybody would be willing to mentor you. You will almost certainly get some response, but you may not find a prospective mentor right away. That's OK. If your idea is really not a good fit for us, we will let you know; otherwise, remember that several mentors are holding back for now to see which projects show the most feasibility, clarity, and creativity in their design ideas. Persistence should pay off.

'''Want to apply with an idea not on this list?''' That's fine. Read the thread linked above about priorities - and remember, our highest priority is for you to have a successful GSoC, and we hope that you will want to continue to contribute afterwards. Do the steps above, paying particular attention to getting some community members' opinions on whether your idea would be valuable. The [[Sugar_Labs/Contacts#General_List|"iaep" mailing list]] may be the best venue for this. We will not all agree with each other about how important your idea is - that's normal - but our feedback will almost certainly help you refine your idea.

<div style="float:right;">
__TOC__
</div>

===Template for well-explained ideas===

If a project that interests you lacks a "potential mentor" here, or you want to know more about the current status of the related code, we would be happy to help guide you on irc (#sugar on freenode) or mailing lists (technical questions to sugar-devel@lists.laptop.org, educational/general ones to iaep@lists.laptop.org).

:<tt> '''==== Project title ====''' </tt>
:
:A quick explanation of the project idea
:
: * Priority for Sugar: Low/Medium/High
:
: * Difficulty (as a GSoC project): Easy/Medium/Advanced
:
: * Skills needed: Experience with WikiCode and copy-paste.

==Project Ideas==
=== Core Software ===
==== Versioned Datastore ====

* To add [[Development Team/Datastore Rewrite#Versioned_entries_.28not_fulfilled_yet.29|Version support]] for [[Journal]] / [[Development Team/Almanac/sugar.datastore.datastore|DataStore]]: Start with (old) [http://wiki.laptop.org/go/Olpcfs Olpcfs] and (newer; less-documented; based on an RCS backend and a relatively small amount of fuse magic) [http://dev.laptop.org/git/users/cscott/olpcfs2/ olpcfs2]. Get Sugar to mount OLPCFS2, a working virtual versioned filesystem, and keep its datastore there. Get datastore to create a new version for each save (automatic or manual). Modify journal UI to use these versions, fork from old versions, etc. Keep with the same name / tags, create a branch if metadata was changed. Allow the user to access "older" versions (Keeping and "old" version will create a branch) and view ancestry (tree of branches).

We would not expect a GSoC project to be necessarily ready to check into our trunk. For instance, you could avoid facing the issue of automated pruning of old versions for disk space, or not have a converter for existing datastores. However, it should work as a proof-of-concept with a variety of activities.

Note: the work for this idea is ''more than halfway done''. The olpcfs2 virtual file system linked above is ''working'', supporting versions and metadata; all you need to do is a UI and an index/searching mechanism on top of that. And even if your indexing mechanism is just brute-force-search each-time, sure, it will be too slow for real use, but we can take it from there, as long you have a working proof-of-concept UI.

*Priority for Sugar: High

*Coolness factor:++

*Difficulty: Hard

*Skills needed: primarily Python UI (pygtk); also FUSE/file systems (this part is mostly done); and Packaging and building.

====Implement existing UI design proposal====
Look at [[Design_Team/Designs]] and [[Design_Team/Proposals]], choose a proposal in one of those, and implement it. Obviously, you need to investigate existing work on these by testing/playing with a current jhbuild and by talking on #sugar.

*Priority for Sugar: Medium

*Difficulty: easy-medium

*Skills needed: Python, PyGTK

==== Registry for people ====
Extend the interaction model to include real people beyond the user–laptop couple. This would extend the virtual network to include some very significant entities, such as family members, who may not have a physical computing device. See the [[Request_New_Features#Support for family interaction | suggestion]] submitted by [[User:Skua]]. The [[olpc:Record]] Activity could be used as a fun, instance-of-person creator and embellisher, by capturing an image or video of the person, and linking it to a new registry.
* Integration of a person object into the Sugar architecture
* Extension of the User/Group model to realistically capture the actual Person entity
* Modification of at least one activity (Record ?) to support the new API
* Extension of School Server registration model
* Extension of an Internet person model to support a Person entity (e.g., to support a missing-person registry in the [http://sahana.rit.edu/ Sahana] Disaster Management System)
Lots of extensions are possible, following a good, fundamental design
* Difficulty: Medium - Hard (depending on scope chosen)
* Skills needed: Data modeling, Core system programming
* Potential mentor: [[User:FGrose]] for data modeling, collaborators needed for Core systems and Internet architectures

==== Toolkit for dissimilar activity collaboration ====
Extend the collaboration model to include interconnection between different activity types. People are trying to share data collected with Measure with spreadsheets or Write or TamTam or Colors! Allow one user's activity to feed a community of collaborators performing different processes on the broadcast output. Allow different activities to run simultaneously in a distributed multi-tasking model, on one or more computers. See [[OLPC:Activity sharing]] and [[OLPC:Low-level Activity API]] for some essentials.

The toolkit would encapsulate the low-level interface to allow activity developers to easily deploy distributed task collaboration.

Extra extra credit for extending the model to general web browsers and web-enabled cell phones. Sugar web collaboration—a '''Honeycomb'''.

* Value to Sugar: High
* Difficulty: Hard
* Skills: low-level API mastery
* Potential mentors:
See this thread for a discussion of the need and some issues, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg02870.html

==== Speech Synthesis for Sugar ====
Integrate speech synthesis with all activities, not just [[olpc:Speak| Speak]], and provide for karaoke coloring. See [[User:Mokurai|Mokurai]]'s [http://www.olpcnews.com/content/ebooks/effective_adult_literacy_program.html article] on adapting [[olpc:Same Language Subtitling]] for literacy to the XO.

Desirable Features for Sugar Speech Synthesis Plugin:

* Provide Sugar Speech Synthesis Configuration Management Tool
* Karaoke Style Coloring in Sugar Environment
* UI for configuration Control
* Accent gets set on the basis of locale

*Priority for Sugar: Medium

*Difficulty (as a GSoC project): Advanced

*Skills needed: Experience with GTK, decent Python ability, ability to integrate with existing code.

*Existing Technical Documentation & Work that can be leveraged: Interested developers can refer to [http://google-summer-of-code-2008-olpc.googlecode.com/files/Hemant_Goyal.tar.gz GSOC 08 Project Status Report].

==== Print Support ====
Print support in Sugar would be useful in many scenarios. The ideal project deliverables would include
* Integration of a printing infrastructure (CUPS ??) into the XO-1 software images
* Modification of Sugar Control Panel to set up the printer (add/select default printer?)
* Modification of at least one activity (Write ?) to support printing
* Making a printing activity, that follows sugar GUI guidelines?
* Extra credit: integrating a server, including permissions and quota management, into the XS image.

*Priority for Sugar: High

*Difficulty (as a GSoC project): Medium-high

*Skills needed: Python programming, API design, some communications

==== Sugar Toolbar submenu support ====

The Sugar Human Interface Guidelines have a toolbar design that includes submenus (See [[Design Team/Designs/Toolbars|Toolbar designs]]). The project would be to extend the existing Toolbar widget to include this new feature and then to work with a few Activity developer to incorporate the new design into their Activities. Possible candidate activities include Paint and [[Activities/Turtle Art|Turtle Art]].

*Priority for Sugar: Medium

*Difficulty (as a GSoC project): Easy-Medium

*Skills needed: intermediate GTK and python skillz

==== Port of Sugar to Pyjamas-Desktop ====

A platform-independent reimplementation of PyGTK and PyGObject which utilises Pyjamas-Desktop to implement (near-)identical PyGTK widgets. A proof-of-concept which can be used as the basis has already been completed - the [http://code.google.com/p/pyjamas/wiki/GsocLlpamies Llpamies branch of pyjamas] and merged into the current pyjamas infrastructure. A transparent split of the SUGAR Activity infrastructure from the GUI front-end display code (along MVC lines) by using overrides of the python "__import__" method, adding in an RPC mechanism (JSONRPC recommended). Again, the Llpamies branch has already achieved this and provides the basis and inspiration. For example, any pyjamas applications which had "import md5": in the llpamies branch actually resulted in JSONRPC calls of any "md5" module methods, which were actually executed SERVER-SIDE.

The consequences of providing this level of abstraction are quite startling: not only would it be conveniently and easily possible to install Sugar onto Win32 platforms (thanks to the MSHTML Pyjamas-Desktop port) but also it would be possible to have all the benefits of a client-server architecture. Thanks to the nature of the Pyjamas API, that would be an extremely _rich_ "client", including being a web browser client. Also, you get "remote desktop" functionality "for free". i.e. thanks to the client-server architecture, a student can publish their work via the server (running on their

The work involves:

* writing alternative infrastructure, replacing the c code gtk widgets with pyjamas widgets (e.g. the sugar menu gtk widget can go, and can subclass the pyjamas MenuBar widget. Icon can subclass pyjamas Image class. etc. etc.)
* the Llpamies GTK browser port, containing the reimplementation of gtk and gobject, needs to be extended and improved
* some serious discussion needs to take place on how SVG Canvas support is to be done. Pyjamas now has a port of GWTCanvas (which uses VML on MSHTML and IE6,7 and 8, but uses 2D SVG on all other browsers and all other brower engines) so there is an abstracted API which could be used to create vector graphics in a platform-independent fashion.
* writing a special importers.py (similar to setuptools zip-archives) which notices module imports such as activity and profile imports, and seamlessly creates a JSONRPC service to farm the function call out to a server (even if it's running on 127.0.0.1). pyjamas-desktop already has example code that performs module import overrides, and the llpamies branch already has example code that performs JSONRPC function call farming.

* Priority for Sugar: TBD
* Difficulty (as a GSoC project): Advanced
* Skills needed: JSONRPC, Web Framework(s), PyGTK, PyGobject, Python, HTML, CSS, [http://pyjs.org Pyjamas].

=== Toolkits / Frameworks for developers ===

==== AJAX Sugar aka [[Karma]] ====

Create a proof-of-concept learning multimedia Sugar activity using javascript and html5 (for instance, Titanium-made apps). This activity should have animation, audio, persistent storage of user progress, and at least basic integration with the Sugar environment. For more information see the [[Karma]] wiki page.

JavaScript/Sugar Communication through the following strategies: PyXPCom, hulahop, xulrunner or [http://www.titaniumapp.com/ Titanium]. see also [http://lists.sugarlabs.org/archive/sugar-devel/2009-March/012829.html the mailing list discussion]. The preferred solution should use a minimalist rendering engine like Webkit and a toolset for local file access like Google Gears. Such a solution would have much less overhead than embedding all of mozilla. For the moment we are focusing on Titanium.

* Ideally, develop a demo activity which could be used as a template for sugarizing AJAX activities. The GSoC participant doesn't have to create her own activity but could simply recreate an existing activity such as one of [http://www.pustakalaya.org/external-content/static/epaath/E-Paath-2.activity/activity/Activity/MenuStage.html OLE Nepal's flash activities].
* This demo should have the following features:
** Simple interactive animation and audio using html5 tags like <canvas> and <audio>
** An assessment section that stores results of student's progress and gives them suggestions on improvement. Assessment info should be persistent.
** Has embedded pdf for lesson plan that can be viewed w/in the activity
** Integrates with datastore
** Navigation and Help elements, ideally reusing widgets from popular javascript libraries like Jquery, Prototype, Mootools
** Some element of collaboration using telepathy (This could be really hard, depending on the state of javascript bindings to dbus)

There is some discussion of the prior work on this question at [[User:Wade/Web_Activity_Spec]].

*Priority for Sugar: Very High ("never bet against the browser")

*Difficulty (as a GSoC project): medium/hard Note: integrating w/ the datastore likely won't be too hard but utilizing Sugar's collaboration features could be very hard

*Skills needed: Javascript/Python integration (PyXPCom, hulahop), CSS, knowlege of SQL

*potential mentors: Wade Brainerd (wadetb at gmail dot com), Bryan Berry (bryan at olenepal dot org) can serve as project manager, define requirements and project deliverables

==== SWF Sugar ====

* Integrate SWF (Flash/Gnash) applications into Sugar.
* Ideally, develop a demo activity which could be used as a template for sugarizing Flash/Gnash activities.

*Priority for Sugar: Very High ("never bet against the browser")

*Difficulty (as a GSoC project): hard

*Skills needed: SWF/Python integration

==== Improve Develop activity ====

There are several improvements that would make the Develop activity a more attractive IDE. Any ONE of these would be a good GSoC project.

* Make a WYSIWIG GUI editor, like Glade. Note that GTK natively supports loading Glade-format interface definitions, although there would be some work involved making the Sugar interface elements available through this method.
* Integrate Sugarbot and auto-testing facilities.
* Integrate a debugger, based on pdb or other.

*Priority for Sugar: Medium-High

*Difficulty: Medium - Hard

*Skills needed: Good python skills.

*Potential mentor; Jameson Quinn (firstname dot lastname at gmail dot com)

==== "Translate Activity" activity ====

We will never finish localizing all our activities and base software for all our deployments - especially for places with high linguistic diversity like Afghanistan, Peru, Guatemala. So it would be great if there were an easy, discoverable way to translate any string on your machine; have the translation appear on your own machine immediately; and, assuming the activity has a link to a Pootle project, upload that translation to a Pootle server later. (For real-world use, these uploads would probably have to be cached at the school server level, but that is more complexity than we'd expect from a GSoC project.) [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] might be a good starting point for the UI.

*Priority for Sugar: Medium-High

*Difficulty: Medium to Hard

*Skills needed: at least some experience localizing, to know what's involved; ability to do minor hacks on gettext in C and Python; work with localization formats (.po, etc.); Python for activity UI; some simple communications, to upload proposed translations to pootle.

*potential mentor: Sayamindu Dasgupta (sayamindu at gmail)

==== SugarGames Pygame wrapper ====
The [http://wiki.laptop.org/go/OLPCGames OLPCGames] wrapper allows [http://pygame.org Pygame] to run inside of GTK in Sugar, making Pygame based Activities possible. However, the wrapper is geared specifically for use on the XO-1, and does not necessarily reflect the modern reality of running Sugar on diverse hardware. It also does not allow for the use of other GTK Widgets in the Activity, restricting developers from adding UI features like pop up query boxes. This project would involve porting OLPCGames or writing a Pygame wrapper from scratch that would allow Pygame to run in GTK while still enabling the use of GTK UI elements. It would also involve making GTK events and other relevant parts of the Sugar API available to Pygame Activities.

* Priority for Sugar: Medium-High (Activity development is limited between the graphics limitations of PyGTK and the UI limitations of Pygame)
* Difficulty (as a GSoC project): Medium-Advanced
* Skills needed: Requires a fair amount of knowledge of both Pygame and PyGTK.
* Potential Mentor: Nirav Patel (nrpatel at gmail, nrp on freenode)

==== Generic linux application wrapper ====
Improve the ability to launch legacy Linux applications (or Windows applications in WINE) from inside Sugar. The issues are our window manager, our datastore/file system, and our security model (Rainbow). Basically, you'd have to fake all of these from one side or the other so that an average legacy app could live with Sugar.

This is a priority for sugar, and there is significant prior art and design thought. The first part of your job would be to search this wiki, the laptop.org wiki, and old mailing list archives for OLPC and Sugarlabs, and talk on IRC, to settle on a good design. Because of this, we'd consider accepting a strong application even if it left some design questions open; but it would have to at least suggest some basic shortcuts you'd take to make the task feasible, and argue why these shortcuts would leave acceptable usability.

* Priority for Sugar: High-Very High
* Difficulty (as a GSoC project): Advanced
* Skills needed: Creative ability to use and quickly learn various tools, ability to focus on critical path (ie, build something quick-and-dirty that accomplishes the main goals rather than getting distracted by ideal solutions), experience with window manager and windowing systems (Gnome, KDE, etc.).

=== Stand-alone activities ===

==== Improved Read activity ====
Use Gecko to implement a reader for [http://www.openebook.org/ epub] format ebooks. This is superior to PDF because such books can be reflowed to better fit the screen and user preferences. Also, (although it would break the standard) it would make it very simple to include AJAX-style active features to books.

Extra credit if you support textual and graphical annotation. Deployments have also asked for a page-turn animation. See also [http://lists.sugarlabs.org/archive/sugar-devel/2009-March/012821.html ml].

*Priority for Sugar: High

*Difficulty (as a GSoC project): Medium (w/o annotation); very hard (w/annotation)

*Skills needed: Strong Javascript/DOM skills, some interlanguage integration (Python/Javascript), ability to adapt Read activity's communications code (Python).

*Potential mentor: Sayamindu Dasgupta (sayamindu at gmail) (already has some code to start with)

==== [[Activities/Listen Spell|Listen Spell]] activity ====

This activity has been last year GSoC project. Its code can be found [http://code.google.com/p/google-summer-of-code-2008-olpc/downloads/detail?name=Assim_Deodia.tar.gz here]. Extending it activity wrt to following points

* Supporting Speech Synthesis model of sugar (speech synthesis model of sugar is not designed yet and is again a gsoc project this year. This task would involve either using speech-dispatcher or [[Activity_Team/gst-plugins-espeak | GST-Plugin]] as of now and later adding the support for sugar model)
* Multi player game over mesh network
* User Defined word list. (Adding support to add new words to dictionary)
* Test Mode: A teacher can feed the pre-defined word list on the network and activity is being used to conduct test/exam
* Speaking sentences to make student learn grammar (this as a higher level)

*Priority for Sugar: Medium

*Difficulty (as a GSoC project): Medium

*Skills needed: Python, GTK, Understanding of sugar mesh network
*Potential mentor: [[Summer_of_Code/Mentors#Assim_Deodia | Assim Deodia]] (assim.deodia at gmail dot com)

==== KDEEdu ====

Sugarize any [http://edu.kde.org/ KDEEdu] activity, especially the ones which have no corresponding Sugar activity. The issue is that Kdeedu uses qt, while sugar uses gtk; the student would propose a reasonable solution to this issue (see [[Talk:KDEEdu]] for one idea). It is doubtful that the whole sugarization process could be automated, so you'd probably just do one activity.

*Priority for Sugar: High

*Difficulty (as a GSoC project): easy-hard

*Skills needed: C/C++, GTK.

==== Educational Toolkit ====

Either based on the existing educational toolkit, or starting from scratch, enable XO use in classroom scenarios. Such scenarios could include

* Teacher shows slides, reproduced on child's screens
* Teacher asks questions - either pre-prepared or on-the-fly
* Students give answers via collaboration
* Teacher or student chooses - explicitly or randomly - an answer for further discussion
* Students split in groups and go from their individual answers to a collaborative answer
* Teacher can review all answers later
* Teacher gives individual or group feedback (offline) which will be shared with appropriate students when they come online
* Teacher checks what's on a child's screen - (experience on other platforms shows this "look over shoulder" ability reduces goofing off even though it is rarely used.)

The low-hanging fruit on [http://wiki.laptop.org/go/Educational_toolkit Educational Toolkit] is the following:

* Enable collaboration scenarios
* Work on the GUI to provide support for multiple types of questions.
* Add API to make it easy to add new question types.

*Priority for Sugar: High

*Difficulty (as a GSoC project): medium-hard

*Skills needed: intermediate ability with Python and communications

==== Improved Imageviewer ====

Implement missing bits in Imageviewer, some of which are

* Sharing support
* Basic image effects support (grayscale, sepia effects, colorize, etc)
* Exif support

There are more things that can be implemented, but the above are the basic minimum one should try to implement.

*Priority for Sugar: High

*Difficulty (as a GSoC project): easy-medium

*Skills needed: Python, GTK. the Sugar collaboration framework

==== EduKT ====

Simple content - history creation tool that needs:
* Re-design drag and drop features
* Add audio support
* Simplify the interface for little people
* Better the saving projects process.

A lot of new features that simplifies to any level the building of interactive contents...

*Priority for Sugar: Medium

*Difficulty (as a GSoC project): medium

*Skills needed: Python, Glade, GTK. the Sugar collaboration framework

==== Port [http://www.lopart.org LopArt] to Sugar ====

<pre>
Subject: humbly introducing... LopArt: a Visual Arts Software that would fit perfectly with the XO
Date: Tue, 29 Jan 2008 12:39:34 -0500
From: ariel savion-lemieux <ariel@loplop.com>

Hello,

We have recently made the purchase of an XO Laptop. We believe in the
project and would like to contribute to it in our own way.

LopLop Inc. has worked in the software industry for more than a decade, and
has developed a couple of drawing applications geared toward children.

LopArt is a visual arts software that emulates real drawing strokes and
styles (it beats TuxPaint out of the water J). Those who work with children
are seduced by the simplicity of LopArt, as well as by the originality and
creativity it allows. Whether it is used during free-time or for structured
learning activities and projects, LopArt is a highly stimulating learning
tool. It is present in more the 500 schools in Quebec alone. Examples of
LopArt artworks can be seen on the LopArt Virtual Museum it contains more
than 40,000 artworks (www.lopart.org). LopArt was developed for all
platforms, and is in open-source on Linux.

For these reasons and plenty more, we would like a chance to present LopArt
to XO members, since we believe it would be a great fit in the XO software
family.

If possible, please direct our request to the appropriate party. If you have
questions or comments, do not hesitate to contact us.

Regards,

The LopLop Team

----------------------

Ariel Savion-Lemieux, LopLop
Project Manager / Chargé de projet
Telephone: 514.543.5849
</pre>

*Difficulty: easy

==== Bug report activity ====

[http://dev.sugarlabs.org/ticket/340 activity for bug reports]

*Priority for Sugar: High

*Difficulty: Easy

*Skills needed: Python, GTK, maybe some simple web forms from both client and server side (ie, PHP or similar)

==== Etc., Etc. ====
It should not be hard at all to imagine educational activities or games which would be useful for primary or secondary school education. Let your imagination run wild!

*Priority for Sugar: Medium

*Difficulty: Medium

*Skills needed: Python, GTK, Sugar collaboration framework

== Brainstorm / unexplained ideas ==

==== Sugar adaption for the Nasa ====
One of the 91 indigenous cultures that still exist in Colombia is the [http://en.wikipedia.org/wiki/Paez_people Paez people] (aka '''Nasa'''). They have their own traditions, customs, world view, mother tongue (Nasa Yuwe), i.e. their own culture. It could be possible to take cultural elements into the Sugar Interface, not only language, to provide Nasa children a suitable and familiar interface. [[User:Santiago|Santiago]] 18:01, 8 March 2008 (EST)

=== Core Software ===

* Accessibility Support: Sugar currently doesn't have anything available for the visually impaired.
* Improve automatic testing across the system. This would improve our check-in and build process immensely. Very high priority which nobody is addressing head-on.
==== Homework turn-in ====
* "Homework turn-in" support: Certain metadata on a file causes new versions to be pushed out over the net (via SMTP, rss, or other; note that Moodle already has [http://docs.moodle.org/en/Email_processing support] for routing from special email addresses to a "location"). No new UI in Sugar, and a trivial amount of changes to Moodle.

[10:18] <homunq> If you'd rather something with PHP in it, I'd recommend the homework turn-in one. That one's really poorly documented. Basically, the steps are:

[10:18] <homunq> 1. figure out a plan for including sugar metadata in the html download links from moodle

[10:19] <homunq> 2. when downloading an assignment, put metadata of "send this back to adress xxx in server"

[10:20] <homunq> 3. When saving new, worked-on versions of the assignment, mark them for upload to the server

[10:22] <homunq> 4. when you see the server, and the homework deadline is not past, the sugar core automatically uploads the latest version. You could decide to use SMTP upload (already somewhat implemented in moodle) or something else like rss or REST or whatever.

[10:22] <homunq> any questions, happy to clarify.

==== Research projects: unpolished code ====
* There is also [http://wiki.laptop.org/go/Journal%2C_reloaded Journal, reloaded], another research project with real code behind it that is promising but languishing. In this case, the idea is to make the journal "tagging" view transparently compatible with a traditional hierarchical directory structure.
* bemasc's [http://dev.laptop.org/git/users/bemasc/groupthink/ groupthink], expanded: The idea is to have a data structure which keeps itself in sync across many laptops "behind the scenes", thus providing drop-in collaboration as long as the structure in question provides the needed functionality. The problem is that the existing code is unpolished, and only supports some pretty limited data structures. I have some ideas of [[how groupthink could be more general]]. [[User:Homunq|Homunq]] 00:43, 11 March 2009 (UTC)

==== Java ====
Package and integrate the IcedTea open source bootstrap of OpenJDK Java with browser plugin for the XO. Deliverables would include:
* Binary, source and rpm dependencies for icedtea and icedtea browser plugin
* Java enabled os image
* Integration of packages into autobuild branch

(This is just to get Java into the build. Creating an application framework would come later.)

==== Graphical toolkit ====
Important work left to do:
* Give focus feedback by showing a rounded rectangle in gtk buttons and HippoCanvas icons.
* Implement keyboard navigation in HippoCanvas.
* Implement accessibility hooks in HippoCanvas.
* Improve keyboard shortcuts - make them easier to create and implement a UI to make them more discoverable, such as transparent letters which appear when you hold <ctrl>

=== Frameworks/Toolkits ===
==== Mono/.NET ====
The use of Mono could really enhance the number of Sugar developers due to the huge existing .NET community.
Thanks to Torello Querci, developing a Sugar activity in Mono is already possible using the Mono/Sugar bindings Sugar.dll (more on Mono on Sugar [[Mono|here]]).

The idea for this GSOC project is to greatly enhance this binding:
* Better integration with the Sugar look & feel and HippoCanvas,
* Binding to telepathy API,
* WinForm compatibility,
* MonoDevelop integration.

More on this idea:
* Priority for Sugar: Low
* Difficulty (as a GSoC project): Medium-Advanced
* Skills needed: C# programming, Linux programming
* Potential mentor: Lionel Laské and/or Torello Querci

=== Activities ===
* See also ideas at [[Activity Team/Project Ideas]].
* A better, more fun, Paint option for small children - One way - Use eToys - http://lists.laptop.org/pipermail/etoys/2008-November/002770.html

==== VideoChat activity ====
telepathy-python has support for audio and video streaming and has recently gained support for using gstreamer, which means that we could easily do efficient videoconferencing using fully open source codecs.

So a really nice project would be to do a proper Sugar activity for video conferencing.

==== Language Trainer ====
A language trainer with text to speech support would be very nice. Something that could start with letters and then teach words.

==== Thesaurus ====
Working together with openthesaurus -- someone could create a thesaurus for kids to learn different words (synonyms and antonyms)

==== Logo Activity ====
:Logo is a computer programming language used for functional programming. It is an adaptation and dialect of the Lisp language; some have called it Lisp without the parentheses. Today, it is known mainly for its turtle graphics, but it also has significant facilities for handling lists, files, I/O, and recursion.

:Logo was created for educational use, more so for constructivist teaching, by Daniel G. Bobrow, Wally Feurzeig and Seymour Papert. It can be used to teach most computer science concepts, as UC Berkeley Lecturer Brian Harvey does in his Computer Science Logo Style trilogy. — [http://en.wikipedia.org/wiki/Logo_(programming_language) Wikipedia article on the Logo programming language]

There is a "[[Running_Linux_Applications_Under_Sugar|Sugarized]]" Logo—[http://www.eecs.berkeley.edu/~bh/usermanual UCB Logo]—but it does not record data into the Journal or use the standard Sugar toolbar.

There are two possible approaches we could take: (1) digging deeper into UCB Logo and (2) working with another Logo, possibly [http://pylogo.org/ PyLogo].

* Priority: high as Logo is an important tool engaging children in programming
* Difficultly: moderate to high, depending upon the approach chosen
** Integrating Pylogo would be relatively easy, but it is a very limited implementation of Logo that would need enhancing
* Experience: some Python and C if the UCB Logo approach is taken

====twext====
Twext es un idea para ayudarnos a aprender lenguajes.
twext is an idea to help us to learn languages
El software Twexter ya tiene un demo que maneja
twexter software now has ¡alpha! that works with
el UniCode para que twexteamos en muchas idiomas.
global text so that we can twext in many languages
* [http://olpcnews.com/content/localization/learning_language.html kids teach kids]
* [http://test.twext.com alpha demo]
* [http://moodle.org moodle me]
* [http://more.read.fm/wiki_test mediawixi]
* [http://twext.com twext]
* [http://github.com/tudisco/twexter code]
this fixed font twext 'roughly' aligns when you CTL+ or CTL- to adjust font size :)

[[Category:Idea]]

== Other ideas for improving Sugar Activities ==

=== Broad project ideas ===
*See [[Marketing Team/Events/Sugarcamp_Boston_2008/Minutes#Items_from_the_roadmap_brainstorm|a list of project ideas]] from a brainstorming session at Sugar Camp.

=== Activities Site (addons) ===

* The activities http://activities.sugarlabs.org, is in need of a serious ''sugarization'', a GSOC project could be giving some love to the dressing and coding of the underlaying activities site (based on mozilla's addons).

=== Packaging for specific distros ===

'''Debian'''
* Help in maintaining and packaging sugar and activities in debian.
* Including/adapting debian-edu .debs to sugar

Hello there, I am quite interested in Debian and want to help with this and all other projects. Please contact me (bjoern AT xruby DOT net) if I can be of assistance to the XO project or other things. I will start my PhD studies in April and have previously studied Computer Science. I am highly interested in helping where I can and want to bring the necessary technology to kids around the world.
: from olpcwiki 2008

=== Preeti's list ===

Hi, I am Preeti, from New Delhi. I would like to get myself involved in this very interesting aspect of the OLPC software development. I have jotted some of my views on the same at:

http://wiki.laptop.org/go/User_talk:59.178.99.172

[[Category:Participate]]
[[Category:GSoC]]
[[Category:Idea]]

Development Team/Project Ideas

2009-09-22T09:06:04Z

Jpritikin: /* Stand-alone activities */

<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>
==Introduction==
This page contains a list of project ideas. For now, the focus is on giving [[GSoC]] students an idea of the kind of thing we're looking for. Summer of Code applicants should also visit '''[[Summer of Code/Resources]]'''.

At the bottom of this page is a section for less-explicitly-explained & wild ideas.

==[[Summer of Code]]==

'''Priorities''': see the [http://lists.sugarlabs.org/archive/iaep/2009-March/004592.html ongoing discussion of priorities] on our mailing list. To summarize that thread: the highest priority is for you to have a successful GSoC, which should bias you towards easier projects such as [[#Stand-alone activities]]. But, if we had to rank this list in terms of priorities for Sugar, the [[#AJAX Sugar aka Karma]] and [[#Versioned Datastore]] ideas are probably our highest priorities, followed by the rest of the [[#Toolkits / Frameworks for developers]]. These are generally hard, though, so we would need you to give us evidence that you are capable, in order for us to accept you for these ideas.

* There is a similar, project-ideas page on the [[OLPC:Summer_of_Code/Ideas | OLPC wiki]] (and a related [[OLPC:Category:GSoC_proposals | category]]). OLPC-specific projects, including hardware- <s>and schoolserver-</s>related projects, should go there. ''Update: since OLPC did not get into GSoC this year, we would consider mentoring school-server related projects.'' Feel free to add below relevant projects from that list - perhaps <s>80%</s> 95% of these could be appropriate Sugar Labs applications.

===See something that interests you? (steps to apply)===
To get in, you will need to design your project and find a mentor. On irc (#sugar on freenode) or the sugar-devel mailing list, you can briefly introduce yourself, state your interest, and ask relevant and specific questions about the state of the existing code. You should also do your own research for other open-source code that might help you. Get a [[Development Team#Development_systems|development environment]] installed. We definitely appreciate it if you can show your readiness to help out - either joining [[BugSquad|bug squad]] and [[BugSquad/Meetings|helping]] to [[BugSquad/Triage Guide|triage]], or actually helping fix some small [http://tinyurl.com/ctfkjl bug] (we've categorized [http://tinyurl.com/sugar-love some bugs as "sugar-love"], which means, not that they are easy to fix, but that they are good for beginners because they don't require much expert knowledge).

When you're ready, figure out a very basic, preliminary design (where does your new UI fit in? what about the code - what talks to what?) and post that to the [[Sugar_Labs/Contacts#Developer_Lists|mailing list]], asking if anybody would be willing to mentor you. You will almost certainly get some response, but you may not find a prospective mentor right away. That's OK. If your idea is really not a good fit for us, we will let you know; otherwise, remember that several mentors are holding back for now to see which projects show the most feasibility, clarity, and creativity in their design ideas. Persistence should pay off.

'''Want to apply with an idea not on this list?''' That's fine. Read the thread linked above about priorities - and remember, our highest priority is for you to have a successful GSoC, and we hope that you will want to continue to contribute afterwards. Do the steps above, paying particular attention to getting some community members' opinions on whether your idea would be valuable. The [[Sugar_Labs/Contacts#General_List|"iaep" mailing list]] may be the best venue for this. We will not all agree with each other about how important your idea is - that's normal - but our feedback will almost certainly help you refine your idea.

<div style="float:right;">
__TOC__
</div>

===Template for well-explained ideas===

If a project that interests you lacks a "potential mentor" here, or you want to know more about the current status of the related code, we would be happy to help guide you on irc (#sugar on freenode) or mailing lists (technical questions to sugar-devel@lists.laptop.org, educational/general ones to iaep@lists.laptop.org).

:<tt> '''==== Project title ====''' </tt>
:
:A quick explanation of the project idea
:
: * Priority for Sugar: Low/Medium/High
:
: * Difficulty (as a GSoC project): Easy/Medium/Advanced
:
: * Skills needed: Experience with WikiCode and copy-paste.

==Project Ideas==
=== Core Software ===
==== Versioned Datastore ====

* To add [[Development Team/Datastore Rewrite#Versioned_entries_.28not_fulfilled_yet.29|Version support]] for [[Journal]] / [[Development Team/Almanac/sugar.datastore.datastore|DataStore]]: Start with (old) [http://wiki.laptop.org/go/Olpcfs Olpcfs] and (newer; less-documented; based on an RCS backend and a relatively small amount of fuse magic) [http://dev.laptop.org/git/users/cscott/olpcfs2/ olpcfs2]. Get Sugar to mount OLPCFS2, a working virtual versioned filesystem, and keep its datastore there. Get datastore to create a new version for each save (automatic or manual). Modify journal UI to use these versions, fork from old versions, etc. Keep with the same name / tags, create a branch if metadata was changed. Allow the user to access "older" versions (Keeping and "old" version will create a branch) and view ancestry (tree of branches).

We would not expect a GSoC project to be necessarily ready to check into our trunk. For instance, you could avoid facing the issue of automated pruning of old versions for disk space, or not have a converter for existing datastores. However, it should work as a proof-of-concept with a variety of activities.

Note: the work for this idea is ''more than halfway done''. The olpcfs2 virtual file system linked above is ''working'', supporting versions and metadata; all you need to do is a UI and an index/searching mechanism on top of that. And even if your indexing mechanism is just brute-force-search each-time, sure, it will be too slow for real use, but we can take it from there, as long you have a working proof-of-concept UI.

*Priority for Sugar: High

*Coolness factor:++

*Difficulty: Hard

*Skills needed: primarily Python UI (pygtk); also FUSE/file systems (this part is mostly done); and Packaging and building.

====Implement existing UI design proposal====
Look at [[Design_Team/Designs]] and [[Design_Team/Proposals]], choose a proposal in one of those, and implement it. Obviously, you need to investigate existing work on these by testing/playing with a current jhbuild and by talking on #sugar.

*Priority for Sugar: Medium

*Difficulty: easy-medium

*Skills needed: Python, PyGTK

==== Registry for people ====
Extend the interaction model to include real people beyond the user–laptop couple. This would extend the virtual network to include some very significant entities, such as family members, who may not have a physical computing device. See the [[Request_New_Features#Support for family interaction | suggestion]] submitted by [[User:Skua]]. The [[olpc:Record]] Activity could be used as a fun, instance-of-person creator and embellisher, by capturing an image or video of the person, and linking it to a new registry.
* Integration of a person object into the Sugar architecture
* Extension of the User/Group model to realistically capture the actual Person entity
* Modification of at least one activity (Record ?) to support the new API
* Extension of School Server registration model
* Extension of an Internet person model to support a Person entity (e.g., to support a missing-person registry in the [http://sahana.rit.edu/ Sahana] Disaster Management System)
Lots of extensions are possible, following a good, fundamental design
* Difficulty: Medium - Hard (depending on scope chosen)
* Skills needed: Data modeling, Core system programming
* Potential mentor: [[User:FGrose]] for data modeling, collaborators needed for Core systems and Internet architectures

==== Toolkit for dissimilar activity collaboration ====
Extend the collaboration model to include interconnection between different activity types. People are trying to share data collected with Measure with spreadsheets or Write or TamTam or Colors! Allow one user's activity to feed a community of collaborators performing different processes on the broadcast output. Allow different activities to run simultaneously in a distributed multi-tasking model, on one or more computers. See [[OLPC:Activity sharing]] and [[OLPC:Low-level Activity API]] for some essentials.

The toolkit would encapsulate the low-level interface to allow activity developers to easily deploy distributed task collaboration.

Extra extra credit for extending the model to general web browsers and web-enabled cell phones. Sugar web collaboration—a '''Honeycomb'''.

* Value to Sugar: High
* Difficulty: Hard
* Skills: low-level API mastery
* Potential mentors:
See this thread for a discussion of the need and some issues, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg02870.html

==== Speech Synthesis for Sugar ====
Integrate speech synthesis with all activities, not just [[olpc:Speak| Speak]], and provide for karaoke coloring. See [[User:Mokurai|Mokurai]]'s [http://www.olpcnews.com/content/ebooks/effective_adult_literacy_program.html article] on adapting [[olpc:Same Language Subtitling]] for literacy to the XO.

Desirable Features for Sugar Speech Synthesis Plugin:

* Provide Sugar Speech Synthesis Configuration Management Tool
* Karaoke Style Coloring in Sugar Environment
* UI for configuration Control
* Accent gets set on the basis of locale

*Priority for Sugar: Medium

*Difficulty (as a GSoC project): Advanced

*Skills needed: Experience with GTK, decent Python ability, ability to integrate with existing code.

*Existing Technical Documentation & Work that can be leveraged: Interested developers can refer to [http://google-summer-of-code-2008-olpc.googlecode.com/files/Hemant_Goyal.tar.gz GSOC 08 Project Status Report].

==== Print Support ====
Print support in Sugar would be useful in many scenarios. The ideal project deliverables would include
* Integration of a printing infrastructure (CUPS ??) into the XO-1 software images
* Modification of Sugar Control Panel to set up the printer (add/select default printer?)
* Modification of at least one activity (Write ?) to support printing
* Making a printing activity, that follows sugar GUI guidelines?
* Extra credit: integrating a server, including permissions and quota management, into the XS image.

*Priority for Sugar: High

*Difficulty (as a GSoC project): Medium-high

*Skills needed: Python programming, API design, some communications

==== Sugar Toolbar submenu support ====

The Sugar Human Interface Guidelines have a toolbar design that includes submenus (See [[Design Team/Designs/Toolbars|Toolbar designs]]). The project would be to extend the existing Toolbar widget to include this new feature and then to work with a few Activity developer to incorporate the new design into their Activities. Possible candidate activities include Paint and [[Activities/Turtle Art|Turtle Art]].

*Priority for Sugar: Medium

*Difficulty (as a GSoC project): Easy-Medium

*Skills needed: intermediate GTK and python skillz

==== Port of Sugar to Pyjamas-Desktop ====

A platform-independent reimplementation of PyGTK and PyGObject which utilises Pyjamas-Desktop to implement (near-)identical PyGTK widgets. A proof-of-concept which can be used as the basis has already been completed - the [http://code.google.com/p/pyjamas/wiki/GsocLlpamies Llpamies branch of pyjamas] and merged into the current pyjamas infrastructure. A transparent split of the SUGAR Activity infrastructure from the GUI front-end display code (along MVC lines) by using overrides of the python "__import__" method, adding in an RPC mechanism (JSONRPC recommended). Again, the Llpamies branch has already achieved this and provides the basis and inspiration. For example, any pyjamas applications which had "import md5": in the llpamies branch actually resulted in JSONRPC calls of any "md5" module methods, which were actually executed SERVER-SIDE.

The consequences of providing this level of abstraction are quite startling: not only would it be conveniently and easily possible to install Sugar onto Win32 platforms (thanks to the MSHTML Pyjamas-Desktop port) but also it would be possible to have all the benefits of a client-server architecture. Thanks to the nature of the Pyjamas API, that would be an extremely _rich_ "client", including being a web browser client. Also, you get "remote desktop" functionality "for free". i.e. thanks to the client-server architecture, a student can publish their work via the server (running on their

The work involves:

* writing alternative infrastructure, replacing the c code gtk widgets with pyjamas widgets (e.g. the sugar menu gtk widget can go, and can subclass the pyjamas MenuBar widget. Icon can subclass pyjamas Image class. etc. etc.)
* the Llpamies GTK browser port, containing the reimplementation of gtk and gobject, needs to be extended and improved
* some serious discussion needs to take place on how SVG Canvas support is to be done. Pyjamas now has a port of GWTCanvas (which uses VML on MSHTML and IE6,7 and 8, but uses 2D SVG on all other browsers and all other brower engines) so there is an abstracted API which could be used to create vector graphics in a platform-independent fashion.
* writing a special importers.py (similar to setuptools zip-archives) which notices module imports such as activity and profile imports, and seamlessly creates a JSONRPC service to farm the function call out to a server (even if it's running on 127.0.0.1). pyjamas-desktop already has example code that performs module import overrides, and the llpamies branch already has example code that performs JSONRPC function call farming.

* Priority for Sugar: TBD
* Difficulty (as a GSoC project): Advanced
* Skills needed: JSONRPC, Web Framework(s), PyGTK, PyGobject, Python, HTML, CSS, [http://pyjs.org Pyjamas].

=== Toolkits / Frameworks for developers ===

==== AJAX Sugar aka [[Karma]] ====

Create a proof-of-concept learning multimedia Sugar activity using javascript and html5 (for instance, Titanium-made apps). This activity should have animation, audio, persistent storage of user progress, and at least basic integration with the Sugar environment. For more information see the [[Karma]] wiki page.

JavaScript/Sugar Communication through the following strategies: PyXPCom, hulahop, xulrunner or [http://www.titaniumapp.com/ Titanium]. see also [http://lists.sugarlabs.org/archive/sugar-devel/2009-March/012829.html the mailing list discussion]. The preferred solution should use a minimalist rendering engine like Webkit and a toolset for local file access like Google Gears. Such a solution would have much less overhead than embedding all of mozilla. For the moment we are focusing on Titanium.

* Ideally, develop a demo activity which could be used as a template for sugarizing AJAX activities. The GSoC participant doesn't have to create her own activity but could simply recreate an existing activity such as one of [http://www.pustakalaya.org/external-content/static/epaath/E-Paath-2.activity/activity/Activity/MenuStage.html OLE Nepal's flash activities].
* This demo should have the following features:
** Simple interactive animation and audio using html5 tags like <canvas> and <audio>
** An assessment section that stores results of student's progress and gives them suggestions on improvement. Assessment info should be persistent.
** Has embedded pdf for lesson plan that can be viewed w/in the activity
** Integrates with datastore
** Navigation and Help elements, ideally reusing widgets from popular javascript libraries like Jquery, Prototype, Mootools
** Some element of collaboration using telepathy (This could be really hard, depending on the state of javascript bindings to dbus)

There is some discussion of the prior work on this question at [[User:Wade/Web_Activity_Spec]].

*Priority for Sugar: Very High ("never bet against the browser")

*Difficulty (as a GSoC project): medium/hard Note: integrating w/ the datastore likely won't be too hard but utilizing Sugar's collaboration features could be very hard

*Skills needed: Javascript/Python integration (PyXPCom, hulahop), CSS, knowlege of SQL

*potential mentors: Wade Brainerd (wadetb at gmail dot com), Bryan Berry (bryan at olenepal dot org) can serve as project manager, define requirements and project deliverables

==== SWF Sugar ====

* Integrate SWF (Flash/Gnash) applications into Sugar.
* Ideally, develop a demo activity which could be used as a template for sugarizing Flash/Gnash activities.

*Priority for Sugar: Very High ("never bet against the browser")

*Difficulty (as a GSoC project): hard

*Skills needed: SWF/Python integration

==== Improve Develop activity ====

There are several improvements that would make the Develop activity a more attractive IDE. Any ONE of these would be a good GSoC project.

* Make a WYSIWIG GUI editor, like Glade. Note that GTK natively supports loading Glade-format interface definitions, although there would be some work involved making the Sugar interface elements available through this method.
* Integrate Sugarbot and auto-testing facilities.
* Integrate a debugger, based on pdb or other.

*Priority for Sugar: Medium-High

*Difficulty: Medium - Hard

*Skills needed: Good python skills.

*Potential mentor; Jameson Quinn (firstname dot lastname at gmail dot com)

==== "Translate Activity" activity ====

We will never finish localizing all our activities and base software for all our deployments - especially for places with high linguistic diversity like Afghanistan, Peru, Guatemala. So it would be great if there were an easy, discoverable way to translate any string on your machine; have the translation appear on your own machine immediately; and, assuming the activity has a link to a Pootle project, upload that translation to a Pootle server later. (For real-world use, these uploads would probably have to be cached at the school server level, but that is more complexity than we'd expect from a GSoC project.) [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] might be a good starting point for the UI.

*Priority for Sugar: Medium-High

*Difficulty: Medium to Hard

*Skills needed: at least some experience localizing, to know what's involved; ability to do minor hacks on gettext in C and Python; work with localization formats (.po, etc.); Python for activity UI; some simple communications, to upload proposed translations to pootle.

*potential mentor: Sayamindu Dasgupta (sayamindu at gmail)

==== SugarGames Pygame wrapper ====
The [http://wiki.laptop.org/go/OLPCGames OLPCGames] wrapper allows [http://pygame.org Pygame] to run inside of GTK in Sugar, making Pygame based Activities possible. However, the wrapper is geared specifically for use on the XO-1, and does not necessarily reflect the modern reality of running Sugar on diverse hardware. It also does not allow for the use of other GTK Widgets in the Activity, restricting developers from adding UI features like pop up query boxes. This project would involve porting OLPCGames or writing a Pygame wrapper from scratch that would allow Pygame to run in GTK while still enabling the use of GTK UI elements. It would also involve making GTK events and other relevant parts of the Sugar API available to Pygame Activities.

* Priority for Sugar: Medium-High (Activity development is limited between the graphics limitations of PyGTK and the UI limitations of Pygame)
* Difficulty (as a GSoC project): Medium-Advanced
* Skills needed: Requires a fair amount of knowledge of both Pygame and PyGTK.
* Potential Mentor: Nirav Patel (nrpatel at gmail, nrp on freenode)

==== Generic linux application wrapper ====
Improve the ability to launch legacy Linux applications (or Windows applications in WINE) from inside Sugar. The issues are our window manager, our datastore/file system, and our security model (Rainbow). Basically, you'd have to fake all of these from one side or the other so that an average legacy app could live with Sugar.

This is a priority for sugar, and there is significant prior art and design thought. The first part of your job would be to search this wiki, the laptop.org wiki, and old mailing list archives for OLPC and Sugarlabs, and talk on IRC, to settle on a good design. Because of this, we'd consider accepting a strong application even if it left some design questions open; but it would have to at least suggest some basic shortcuts you'd take to make the task feasible, and argue why these shortcuts would leave acceptable usability.

* Priority for Sugar: High-Very High
* Difficulty (as a GSoC project): Advanced
* Skills needed: Creative ability to use and quickly learn various tools, ability to focus on critical path (ie, build something quick-and-dirty that accomplishes the main goals rather than getting distracted by ideal solutions), experience with window manager and windowing systems (Gnome, KDE, etc.).

=== Stand-alone activities ===

==== Improved Read activity ====
Use Gecko to implement a reader for [http://www.openebook.org/ epub] format ebooks. This is superior to PDF because such books can be reflowed to better fit the screen and user preferences. Also, (although it would break the standard) it would make it very simple to include AJAX-style active features to books.

Extra credit if you support textual and graphical annotation. Deployments have also asked for a page-turn animation. See also [http://lists.sugarlabs.org/archive/sugar-devel/2009-March/012821.html ml].

*Priority for Sugar: High

*Difficulty (as a GSoC project): Medium (w/o annotation); very hard (w/annotation)

*Skills needed: Strong Javascript/DOM skills, some interlanguage integration (Python/Javascript), ability to adapt Read activity's communications code (Python).

*Potential mentor: Sayamindu Dasgupta (sayamindu at gmail) (already has some code to start with)

==== [[Activities/Listen Spell|Listen Spell]] activity ====

This activity has been last year GSoC project. Its code can be found [http://code.google.com/p/google-summer-of-code-2008-olpc/downloads/detail?name=Assim_Deodia.tar.gz here]. Extending it activity wrt to following points

* Supporting Speech Synthesis model of sugar (speech synthesis model of sugar is not designed yet and is again a gsoc project this year. This task would involve either using speech-dispatcher or [[Activity_Team/gst-plugins-espeak | GST-Plugin]] as of now and later adding the support for sugar model)
* Multi player game over mesh network
* User Defined word list. (Adding support to add new words to dictionary)
* Test Mode: A teacher can feed the pre-defined word list on the network and activity is being used to conduct test/exam
* Speaking sentences to make student learn grammar (this as a higher level)

*Priority for Sugar: Medium

*Difficulty (as a GSoC project): Medium

*Skills needed: Python, GTK, Understanding of sugar mesh network
*Potential mentor: [[Summer_of_Code/Mentors#Assim_Deodia | Assim Deodia]] (assim.deodia at gmail dot com)

==== KDEEdu ====

Sugarize any [http://edu.kde.org/ KDEEdu] activity, especially the ones which have no corresponding Sugar activity. The issue is that Kdeedu uses qt, while sugar uses gtk; the student would propose a reasonable solution to this issue (see [[Talk:KDEEdu]] for one idea). It is doubtful that the whole sugarization process could be automated, so you'd probably just do one activity.

*Priority for Sugar: High

*Difficulty (as a GSoC project): easy-hard

*Skills needed: C/C++, GTK.

==== Educational Toolkit ====

Either based on the existing educational toolkit, or starting from scratch, enable XO use in classroom scenarios. Such scenarios could include

* Teacher shows slides, reproduced on child's screens
* Teacher asks questions - either pre-prepared or on-the-fly
* Students give answers via collaboration
* Teacher or student chooses - explicitly or randomly - an answer for further discussion
* Students split in groups and go from their individual answers to a collaborative answer
* Teacher can review all answers later
* Teacher gives individual or group feedback (offline) which will be shared with appropriate students when they come online
* Teacher checks what's on a child's screen - (experience on other platforms shows this "look over shoulder" ability reduces goofing off even though it is rarely used.)

The low-hanging fruit on [http://wiki.laptop.org/go/Educational_toolkit Educational Toolkit] is the following:

* Enable collaboration scenarios
* Work on the GUI to provide support for multiple types of questions.
* Add API to make it easy to add new question types.

*Priority for Sugar: High

*Difficulty (as a GSoC project): medium-hard

*Skills needed: intermediate ability with Python and communications

==== Improved Imageviewer ====

Implement missing bits in Imageviewer, some of which are

* Sharing support
* Basic image effects support (grayscale, sepia effects, colorize, etc)
* Exif support

There are more things that can be implemented, but the above are the basic minimum one should try to implement.

*Priority for Sugar: High

*Difficulty (as a GSoC project): easy-medium

*Skills needed: Python, GTK. the Sugar collaboration framework

==== EduKT ====

Simple content - history creation tool that needs:
* Re-design drag and drop features
* Add audio support
* Simplify the interface for little people
* Better the saving projects process.

A lot of new features that simplifies to any level the building of interactive contents...

*Priority for Sugar: Medium

*Difficulty (as a GSoC project): medium

*Skills needed: Python, Glade, GTK. the Sugar collaboration framework

==== [http://www.lopart.org Port LopArt to Sugar] ====

(INSERT HERE)

*Difficulty: easy

==== Bug report activity ====

[http://dev.sugarlabs.org/ticket/340 activity for bug reports]

*Priority for Sugar: High

*Difficulty: Easy

*Skills needed: Python, GTK, maybe some simple web forms from both client and server side (ie, PHP or similar)

==== Etc., Etc. ====
It should not be hard at all to imagine educational activities or games which would be useful for primary or secondary school education. Let your imagination run wild!

*Priority for Sugar: Medium

*Difficulty: Medium

*Skills needed: Python, GTK, Sugar collaboration framework

== Brainstorm / unexplained ideas ==

==== Sugar adaption for the Nasa ====
One of the 91 indigenous cultures that still exist in Colombia is the [http://en.wikipedia.org/wiki/Paez_people Paez people] (aka '''Nasa'''). They have their own traditions, customs, world view, mother tongue (Nasa Yuwe), i.e. their own culture. It could be possible to take cultural elements into the Sugar Interface, not only language, to provide Nasa children a suitable and familiar interface. [[User:Santiago|Santiago]] 18:01, 8 March 2008 (EST)

=== Core Software ===

* Accessibility Support: Sugar currently doesn't have anything available for the visually impaired.
* Improve automatic testing across the system. This would improve our check-in and build process immensely. Very high priority which nobody is addressing head-on.
==== Homework turn-in ====
* "Homework turn-in" support: Certain metadata on a file causes new versions to be pushed out over the net (via SMTP, rss, or other; note that Moodle already has [http://docs.moodle.org/en/Email_processing support] for routing from special email addresses to a "location"). No new UI in Sugar, and a trivial amount of changes to Moodle.

[10:18] <homunq> If you'd rather something with PHP in it, I'd recommend the homework turn-in one. That one's really poorly documented. Basically, the steps are:

[10:18] <homunq> 1. figure out a plan for including sugar metadata in the html download links from moodle

[10:19] <homunq> 2. when downloading an assignment, put metadata of "send this back to adress xxx in server"

[10:20] <homunq> 3. When saving new, worked-on versions of the assignment, mark them for upload to the server

[10:22] <homunq> 4. when you see the server, and the homework deadline is not past, the sugar core automatically uploads the latest version. You could decide to use SMTP upload (already somewhat implemented in moodle) or something else like rss or REST or whatever.

[10:22] <homunq> any questions, happy to clarify.

==== Research projects: unpolished code ====
* There is also [http://wiki.laptop.org/go/Journal%2C_reloaded Journal, reloaded], another research project with real code behind it that is promising but languishing. In this case, the idea is to make the journal "tagging" view transparently compatible with a traditional hierarchical directory structure.
* bemasc's [http://dev.laptop.org/git/users/bemasc/groupthink/ groupthink], expanded: The idea is to have a data structure which keeps itself in sync across many laptops "behind the scenes", thus providing drop-in collaboration as long as the structure in question provides the needed functionality. The problem is that the existing code is unpolished, and only supports some pretty limited data structures. I have some ideas of [[how groupthink could be more general]]. [[User:Homunq|Homunq]] 00:43, 11 March 2009 (UTC)

==== Java ====
Package and integrate the IcedTea open source bootstrap of OpenJDK Java with browser plugin for the XO. Deliverables would include:
* Binary, source and rpm dependencies for icedtea and icedtea browser plugin
* Java enabled os image
* Integration of packages into autobuild branch

(This is just to get Java into the build. Creating an application framework would come later.)

==== Graphical toolkit ====
Important work left to do:
* Give focus feedback by showing a rounded rectangle in gtk buttons and HippoCanvas icons.
* Implement keyboard navigation in HippoCanvas.
* Implement accessibility hooks in HippoCanvas.
* Improve keyboard shortcuts - make them easier to create and implement a UI to make them more discoverable, such as transparent letters which appear when you hold <ctrl>

=== Frameworks/Toolkits ===
==== Mono/.NET ====
The use of Mono could really enhance the number of Sugar developers due to the huge existing .NET community.
Thanks to Torello Querci, developing a Sugar activity in Mono is already possible using the Mono/Sugar bindings Sugar.dll (more on Mono on Sugar [[Mono|here]]).

The idea for this GSOC project is to greatly enhance this binding:
* Better integration with the Sugar look & feel and HippoCanvas,
* Binding to telepathy API,
* WinForm compatibility,
* MonoDevelop integration.

More on this idea:
* Priority for Sugar: Low
* Difficulty (as a GSoC project): Medium-Advanced
* Skills needed: C# programming, Linux programming
* Potential mentor: Lionel Laské and/or Torello Querci

=== Activities ===
* See also ideas at [[Activity Team/Project Ideas]].
* A better, more fun, Paint option for small children - One way - Use eToys - http://lists.laptop.org/pipermail/etoys/2008-November/002770.html

==== VideoChat activity ====
telepathy-python has support for audio and video streaming and has recently gained support for using gstreamer, which means that we could easily do efficient videoconferencing using fully open source codecs.

So a really nice project would be to do a proper Sugar activity for video conferencing.

==== Language Trainer ====
A language trainer with text to speech support would be very nice. Something that could start with letters and then teach words.

==== Thesaurus ====
Working together with openthesaurus -- someone could create a thesaurus for kids to learn different words (synonyms and antonyms)

==== Logo Activity ====
:Logo is a computer programming language used for functional programming. It is an adaptation and dialect of the Lisp language; some have called it Lisp without the parentheses. Today, it is known mainly for its turtle graphics, but it also has significant facilities for handling lists, files, I/O, and recursion.

:Logo was created for educational use, more so for constructivist teaching, by Daniel G. Bobrow, Wally Feurzeig and Seymour Papert. It can be used to teach most computer science concepts, as UC Berkeley Lecturer Brian Harvey does in his Computer Science Logo Style trilogy. — [http://en.wikipedia.org/wiki/Logo_(programming_language) Wikipedia article on the Logo programming language]

There is a "[[Running_Linux_Applications_Under_Sugar|Sugarized]]" Logo—[http://www.eecs.berkeley.edu/~bh/usermanual UCB Logo]—but it does not record data into the Journal or use the standard Sugar toolbar.

There are two possible approaches we could take: (1) digging deeper into UCB Logo and (2) working with another Logo, possibly [http://pylogo.org/ PyLogo].

* Priority: high as Logo is an important tool engaging children in programming
* Difficultly: moderate to high, depending upon the approach chosen
** Integrating Pylogo would be relatively easy, but it is a very limited implementation of Logo that would need enhancing
* Experience: some Python and C if the UCB Logo approach is taken

====twext====
Twext es un idea para ayudarnos a aprender lenguajes.
twext is an idea to help us to learn languages
El software Twexter ya tiene un demo que maneja
twexter software now has ¡alpha! that works with
el UniCode para que twexteamos en muchas idiomas.
global text so that we can twext in many languages
* [http://olpcnews.com/content/localization/learning_language.html kids teach kids]
* [http://test.twext.com alpha demo]
* [http://moodle.org moodle me]
* [http://more.read.fm/wiki_test mediawixi]
* [http://twext.com twext]
* [http://github.com/tudisco/twexter code]
this fixed font twext 'roughly' aligns when you CTL+ or CTL- to adjust font size :)

[[Category:Idea]]

== Other ideas for improving Sugar Activities ==

=== Broad project ideas ===
*See [[Marketing Team/Events/Sugarcamp_Boston_2008/Minutes#Items_from_the_roadmap_brainstorm|a list of project ideas]] from a brainstorming session at Sugar Camp.

=== Activities Site (addons) ===

* The activities http://activities.sugarlabs.org, is in need of a serious ''sugarization'', a GSOC project could be giving some love to the dressing and coding of the underlaying activities site (based on mozilla's addons).

=== Packaging for specific distros ===

'''Debian'''
* Help in maintaining and packaging sugar and activities in debian.
* Including/adapting debian-edu .debs to sugar

Hello there, I am quite interested in Debian and want to help with this and all other projects. Please contact me (bjoern AT xruby DOT net) if I can be of assistance to the XO project or other things. I will start my PhD studies in April and have previously studied Computer Science. I am highly interested in helping where I can and want to bring the necessary technology to kids around the world.
: from olpcwiki 2008

=== Preeti's list ===

Hi, I am Preeti, from New Delhi. I would like to get myself involved in this very interesting aspect of the OLPC software development. I have jotted some of my views on the same at:

http://wiki.laptop.org/go/User_talk:59.178.99.172

[[Category:Participate]]
[[Category:GSoC]]
[[Category:Idea]]

Sugar on a Stick/Installation/OLPC

2009-08-10T07:14:09Z

Jpritikin: /* Option 2: Install a v0.84 SoaS-XO image on the XO-1 NAND flash drive */

<noinclude>{{ Translations | [[Sugar_on_a_Stick/Installation/OLPC|english]] | [[Sugar_on_a_Stick/Installation/OLPC/lang-es|español]] | [[Sugar_on_a_Stick/Installation/OLPC/lang-fr|français]] }} {{GoogleTrans-en}}</noinclude>

==Do you have an OLPC XO-1?==

[[image:OLPCXO.png]]


Sugar 0.84 has a number of improvements above and beyond 0.82. And we have a version working on the OLPC XO-1, but because of the changes in process at OLPC (see [[olpc:Future releases]]), there is a new short-term strategy for updates. Until OLPC issues its next official release, we are recommending that XO-1 users who would like to try 0.84 use Sugar on a Stick. The XO-1 can be booted from an external USB or SD card storage device, [[#Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB|Option 1]] below.

----

There are four main options for OLPC XO users:
# Run v0.84 Sugar on a Stick from a USB flash drive or SD card
# Install v0.84 Sugar on a Stick-XO on the XO-1's internal NAND flash memory
# Convert a v0.84 Sugar on a Stick .iso image to one suitable to install on the XO-1's internal NAND flash memory
# Use <tt>olpc-update</tt> to update to the latest software release from OLPC (which is currently 8.2.0 incorporating Sugar v0.82).

'''Note:''' The OLPC XO-1 has some built-in protections which lock the computer down in order to prevent haphazard software changes. In order to use either [[#Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB|Option 1]], [[#Option 2: Install a v0.84 SoaS-XO image on the XO-1 NAND flash drive|Option 2]], or [[#Option 3: Convert a v0.84 Sugar on a Stick .iso image|Option 3]], XO-1 owners must [http://wiki.laptop.org/go/Activation_and_developer_keys request a developer key from OLPC]; it's a simple process but takes up to 24 hours.

'''Warning:''' Options 2 & 3 will wipe /security directory, with any leases or devkeys there.

===Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB===

(Requires a [http://wiki.laptop.org/go/Activation_and_developer_keys developer key for your OLPC-XO-1] and access to a Windows or Fedora computer)

====On Windows:====

Create the USB stick as described on the [[Sugar on a Stick/Windows]] page in the "Windows Instructions" section.

Do '''not''' boot this stick on your Windows machine. Make sure the first boot is on your XO. If you do boot the stick on another machine first, the X server setup needed for the XO will not be done.

====On Fedora:====
Type the following commands in a terminal window:
[[wikipedia:Wget|wget]] {{SoaS release path}}
 
sudo yum install livecd-tools
 
wget -O livecd-iso-to-disk.sh "http://git.fedoraproject.org/git/?p=hosted/livecd;a=blob_plain;f=tools/livecd-iso-to-disk.sh;hb=HEAD"
 
sudo ./livecd-iso-to-disk.sh --format --xo --xo-no-home {{SoaS release image}} /dev/sd''X''1

Where <code>/dev/sdX1</code> is the device associated with your removable media.

The livecd-iso-to-disk.sh script needs to be a current version with XO support (not what you get by default in Fedora 10, though Fedora 11's should be fine). You can find an up-to date version in the SoaS disk image /LiveOS/livecd-iso-to-disk.sh .

===Option 2: Install a v0.84 SoaS-XO image on the XO-1 NAND flash drive===
See http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg05231.html and https://www.redhat.com/archives/fedora-olpc-list/2009-June/msg00063.html

This build feels substantially faster than 802 (the last stable release). Serious issues:

* No sound
* No automounting of USB keys.

More recent builds are better: http://lists.sugarlabs.org/archive/sugar-devel/2009-August/017775.html

===Option 3: Convert a v0.84 Sugar on a Stick .iso image===

'''WARNING''': This option is wishful thinking until the [https://bugzilla.redhat.com/show_bug.cgi?id=500196 jffs2 mount bug] is fixed.

'''Note''': Requires a [http://wiki.laptop.org/go/Activation_and_developer_keys developer key for your OLPC-XO-1] and access to a GNU/Linux computer) It also requires a recent OFW version (Q2E28 has been reported as working. [http://wiki.laptop.org/go/Manual_Firmware_Install Instructions for updating your firmware]).

'''WARNING''': this will overwrite all data on your OLPC-XO-1 NAND!!

On a Fedora10 system:

sudo yum -y install crcimg mtd-utils

On Debian or Ubuntu:

sudo apt-get install mtd-utils

:(On some older Debian/Ubuntu builds, you may need to install mtd-tools instead.)

:crcimg is not packaged for Debian so you'll have to build it:

wget http://dev.laptop.org/~mstone/releases/SOURCES/crcimg-1.1.tar.bz2
tar xvf crcimg-1.1.tar.bz2
sudo make -f Makefile.build install

NB: Of course, if you do not have the packages of the program [[wikipedia:Wget| wget]], install them by the command “yum install wget”

Next:

wget http://download.sugarlabs.org/soas/releases/livecd-iso-to-disk.sh
wget {{SoaS release path}}

run this command (or something similar depending on the version number of your .iso file)

sudo sh livecd-iso-to-xo.sh {{SoaS release image}} Soas.img

and then copy Soas.img and Soas.crc to a USB key or SD card

On the OLPC-XO-1, boot with the USB key plugged in and the four game keys press to get to the OK prompt in Open Firmware (OFW).

Type the following commands:

disable-security
copy-nand u:\Soas.img

Note: depending upon the file system on your USB key, the names maybe truncated:

dir u:\
copy-nand u:\SOAS-2~1.img

You should see an animation of the blocks being written to the NAND. When it is complete, you will be back at the OK prompt. Type:

reboot

and the OLPC-XO-1 will reboot and you should be running Sugar 0.84.

===Option 4: Update to the official OLPC v0.82 Sugar build===
(This does ''not'' give you a '''Sugar on a Stick''' image.)

You run ''olpc-update'' from the Terminal activity, ''e.g.'',:

sudo olpc-update 802

where 802 is the build number of the [[OLPC:OS images | latest stable image]] from OLPC. This is OLPC release 8.2.1, incorporating Sugar v0.82.

[[Supported_systems#Fedora_on_an_OLPC_XO]] has some more details on upgrading OLPC software.

== Notes on running Sugar on a Stick on XO-1 ==
* You must hold down the XO-1's '''✓''' ("check") gamepad key during boot, otherwise boot will hang at the gray "XO" logo. You should see dots appear under the USB flash drive icon indicating the XO is booting from that drive.

* SoaS images are based on Fedora "Rawhide" spins; [[olpc:Rawhide-XO]] describes many of the known issues running these on an XO-1.

* Also make sure you got a dev-key before booting with the SoaS using the check button..

----
[[Downloads|back to downloads page]]
__NOTOC__

[[Category:HowTo]]

Sugar on a Stick/Installation/OLPC

2009-08-10T01:03:05Z

Jpritikin: /* Option 3: Convert a v0.84 Sugar on a Stick .iso image */

<noinclude>{{ Translations | [[Sugar_on_a_Stick/Installation/OLPC|english]] | [[Sugar_on_a_Stick/Installation/OLPC/lang-es|español]] | [[Sugar_on_a_Stick/Installation/OLPC/lang-fr|français]] }} {{GoogleTrans-en}}</noinclude>

==Do you have an OLPC XO-1?==

[[image:OLPCXO.png]]


Sugar 0.84 has a number of improvements above and beyond 0.82. And we have a version working on the OLPC XO-1, but because of the changes in process at OLPC (see [[olpc:Future releases]]), there is a new short-term strategy for updates. Until OLPC issues its next official release, we are recommending that XO-1 users who would like to try 0.84 use Sugar on a Stick. The XO-1 can be booted from an external USB or SD card storage device, [[#Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB|Option 1]] below.

----

There are four main options for OLPC XO users:
# Run v0.84 Sugar on a Stick from a USB flash drive or SD card
# Install v0.84 Sugar on a Stick-XO on the XO-1's internal NAND flash memory
# Convert a v0.84 Sugar on a Stick .iso image to one suitable to install on the XO-1's internal NAND flash memory
# Use <tt>olpc-update</tt> to update to the latest software release from OLPC (which is currently 8.2.0 incorporating Sugar v0.82).

'''Note:''' The OLPC XO-1 has some built-in protections which lock the computer down in order to prevent haphazard software changes. In order to use either [[#Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB|Option 1]], [[#Option 2: Install a v0.84 SoaS-XO image on the XO-1 NAND flash drive|Option 2]], or [[#Option 3: Convert a v0.84 Sugar on a Stick .iso image|Option 3]], XO-1 owners must [http://wiki.laptop.org/go/Activation_and_developer_keys request a developer key from OLPC]; it's a simple process but takes up to 24 hours.

'''Warning:''' Options 2 & 3 will wipe /security directory, with any leases or devkeys there.

===Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB===

(Requires a [http://wiki.laptop.org/go/Activation_and_developer_keys developer key for your OLPC-XO-1] and access to a Windows or Fedora computer)

====On Windows:====

Create the USB stick as described on the [[Sugar on a Stick/Windows]] page in the "Windows Instructions" section.

Do '''not''' boot this stick on your Windows machine. Make sure the first boot is on your XO. If you do boot the stick on another machine first, the X server setup needed for the XO will not be done.

====On Fedora:====
Type the following commands in a terminal window:
[[wikipedia:Wget|wget]] {{SoaS release path}}
 
sudo yum install livecd-tools
 
wget -O livecd-iso-to-disk.sh "http://git.fedoraproject.org/git/?p=hosted/livecd;a=blob_plain;f=tools/livecd-iso-to-disk.sh;hb=HEAD"
 
sudo ./livecd-iso-to-disk.sh --format --xo --xo-no-home {{SoaS release image}} /dev/sd''X''1

Where <code>/dev/sdX1</code> is the device associated with your removable media.

The livecd-iso-to-disk.sh script needs to be a current version with XO support (not what you get by default in Fedora 10, though Fedora 11's should be fine). You can find an up-to date version in the SoaS disk image /LiveOS/livecd-iso-to-disk.sh .

===Option 2: Install a v0.84 SoaS-XO image on the XO-1 NAND flash drive===
See http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg05231.html and https://www.redhat.com/archives/fedora-olpc-list/2009-June/msg00063.html

This build feels substantially faster than 802 (the last stable release). Serious issues:

* No sound
* No automounting of USB keys.

===Option 3: Convert a v0.84 Sugar on a Stick .iso image===

'''WARNING''': This option is wishful thinking until the [https://bugzilla.redhat.com/show_bug.cgi?id=500196 jffs2 mount bug] is fixed.

'''Note''': Requires a [http://wiki.laptop.org/go/Activation_and_developer_keys developer key for your OLPC-XO-1] and access to a GNU/Linux computer) It also requires a recent OFW version (Q2E28 has been reported as working. [http://wiki.laptop.org/go/Manual_Firmware_Install Instructions for updating your firmware]).

'''WARNING''': this will overwrite all data on your OLPC-XO-1 NAND!!

On a Fedora10 system:

sudo yum -y install crcimg mtd-utils

On Debian or Ubuntu:

sudo apt-get install mtd-utils

:(On some older Debian/Ubuntu builds, you may need to install mtd-tools instead.)

:crcimg is not packaged for Debian so you'll have to build it:

wget http://dev.laptop.org/~mstone/releases/SOURCES/crcimg-1.1.tar.bz2
tar xvf crcimg-1.1.tar.bz2
sudo make -f Makefile.build install

NB: Of course, if you do not have the packages of the program [[wikipedia:Wget| wget]], install them by the command “yum install wget”

Next:

wget http://download.sugarlabs.org/soas/releases/livecd-iso-to-disk.sh
wget {{SoaS release path}}

run this command (or something similar depending on the version number of your .iso file)

sudo sh livecd-iso-to-xo.sh {{SoaS release image}} Soas.img

and then copy Soas.img and Soas.crc to a USB key or SD card

On the OLPC-XO-1, boot with the USB key plugged in and the four game keys press to get to the OK prompt in Open Firmware (OFW).

Type the following commands:

disable-security
copy-nand u:\Soas.img

Note: depending upon the file system on your USB key, the names maybe truncated:

dir u:\
copy-nand u:\SOAS-2~1.img

You should see an animation of the blocks being written to the NAND. When it is complete, you will be back at the OK prompt. Type:

reboot

and the OLPC-XO-1 will reboot and you should be running Sugar 0.84.

===Option 4: Update to the official OLPC v0.82 Sugar build===
(This does ''not'' give you a '''Sugar on a Stick''' image.)

You run ''olpc-update'' from the Terminal activity, ''e.g.'',:

sudo olpc-update 802

where 802 is the build number of the [[OLPC:OS images | latest stable image]] from OLPC. This is OLPC release 8.2.1, incorporating Sugar v0.82.

[[Supported_systems#Fedora_on_an_OLPC_XO]] has some more details on upgrading OLPC software.

== Notes on running Sugar on a Stick on XO-1 ==
* You must hold down the XO-1's '''✓''' ("check") gamepad key during boot, otherwise boot will hang at the gray "XO" logo. You should see dots appear under the USB flash drive icon indicating the XO is booting from that drive.

* SoaS images are based on Fedora "Rawhide" spins; [[olpc:Rawhide-XO]] describes many of the known issues running these on an XO-1.

* Also make sure you got a dev-key before booting with the SoaS using the check button..

----
[[Downloads|back to downloads page]]
__NOTOC__

[[Category:HowTo]]

User:Jpritikin

2009-08-04T01:20:10Z

Jpritikin: Created page with 'Check out our [http://wiki.laptop.org/go/OLPC_India/Nashik our laptop.org page]. You may contact me at jpritikin@pobox.com'

Check out our [http://wiki.laptop.org/go/OLPC_India/Nashik our laptop.org page]. You may contact me at jpritikin@pobox.com

Deployment Team/Places

2009-08-04T01:17:18Z

Jpritikin: /* Asia */

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
=== Introduction ===

This page lists the places in the world where Sugar is used along with a contact person that will facilitate communication between the global and the local communities.

The column "# of members" is intended to give a rough estimation of the size of the local community and may include children, educators, parents, volunteers, etc

=== Asia ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| India
| English, Hindi, Marathi
| 32
| [[USER:Jpritikin|Joshua Pritikin]]
|-
| Nepal
| Nepali
| 40
| [[USER:BryanWB|Bryan Berry]], Rabi Karmacharya
|-
| Quezon City, Philippines
| Filipino, English
| 30
| [[USER:Jgotangco|Jerome Gotangco]]
|}

=== Africa ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Ethiopia
| Amharic
| ?
| ?
|}

=== America ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Colombia
| Spanish
| 7
| RafaelOrtiz
|-
| Peru
| Spanish
| ?
| Hernan Pachas?
|-
| Uruguay
| Spanish
| ?
| Pablo Flores?
|-
| Paraguay
| Spanish
| 4500
| Raul Gutierrez S.
|-
| Boston, USA
| English
| ?
| Caroline Meeks?
|}

=== Europe ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Graz, Austria
| German
| 7
| David Van Assche, [[User:ChristophD|Christoph Derndorfer]]
|}

=== Oceania ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Solomon Islands
| Pijin, Marovo
| ?
| David Leeming?
|}

Deployment Team/Places

2009-08-04T01:16:30Z

Jpritikin: /* Asia */

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
=== Introduction ===

This page lists the places in the world where Sugar is used along with a contact person that will facilitate communication between the global and the local communities.

The column "# of members" is intended to give a rough estimation of the size of the local community and may include children, educators, parents, volunteers, etc

=== Asia ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| India
| English
| 32
| [[USER:Jpritikin|Joshua Pritikin]]
|-
| Nepal
| Nepali
| 40
| [[USER:BryanWB|Bryan Berry]], Rabi Karmacharya
|-
| Quezon City, Philippines
| Filipino, English
| 30
| [[USER:Jgotangco|Jerome Gotangco]]
|}

=== Africa ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Ethiopia
| Amharic
| ?
| ?
|}

=== America ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Colombia
| Spanish
| 7
| RafaelOrtiz
|-
| Peru
| Spanish
| ?
| Hernan Pachas?
|-
| Uruguay
| Spanish
| ?
| Pablo Flores?
|-
| Paraguay
| Spanish
| 4500
| Raul Gutierrez S.
|-
| Boston, USA
| English
| ?
| Caroline Meeks?
|}

=== Europe ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Graz, Austria
| German
| 7
| David Van Assche, [[User:ChristophD|Christoph Derndorfer]]
|}

=== Oceania ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Solomon Islands
| Pijin, Marovo
| ?
| David Leeming?
|}

Sugar Labs/Members/List

2009-07-29T02:48:08Z

Jpritikin:

Sugar on a Stick/Installation/OLPC

2009-07-16T10:36:34Z

Jpritikin: /* Option 2: Install a v0.84 SoaS-XO image on the XO-1 NAND flash drive */

<noinclude>{{ Translations | [[Sugar_on_a_Stick/Installation/OLPC|english]] | [[Sugar_on_a_Stick/Installation/OLPC/lang-es|español]] | [[Sugar_on_a_Stick/Installation/OLPC/lang-fr|français]] }} {{ 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>

==Do you have an OLPC XO-1?==

[[image:OLPCXO.png]]


Sugar 0.84 has a number of improvements above and beyond 0.82. And we have a version working on the OLPC XO-1, but because of the changes in process at OLPC (see [[olpc:Future releases]]), there is a new short-term strategy for updates. Until OLPC issues its next official release, we are recommending that XO-1 users who would like to try 0.84 use Sugar on a Stick. The XO-1 can be booted from an external USB or SD card storage device, [[#Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB|Option 1]] below.

----

There are four main options for OLPC XO users:
# Run v0.84 Sugar on a Stick from a USB flash drive or SD card
# Install v0.84 Sugar on a Stick-XO on the XO-1's internal NAND flash memory
# Convert a v0.84 Sugar on a Stick .iso image to one suitable to install on the XO-1's internal NAND flash memory
# Use <tt>olpc-update</tt> to update to the latest software release from OLPC (which is currently 8.2.0 incorporating Sugar v0.82).

'''Note:''' The OLPC XO-1 has some built-in protections which lock the computer down in order to prevent haphazard software changes. In order to use either [[#Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB|Option 1]], [[#Option 2: Install a v0.84 SoaS-XO image on the XO-1 NAND flash drive|Option 2]], or [[#Option 3: Convert a v0.84 Sugar on a Stick .iso image|Option 3]], XO-1 owners must [http://wiki.laptop.org/go/Activation_and_developer_keys request a developer key from OLPC]; it's a simple process but takes up to 24 hours.

'''Warning:''' Options 2 & 3 will wipe /security directory, with any leases or devkeys there.

===Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB===

(Requires a [http://wiki.laptop.org/go/Activation_and_developer_keys developer key for your OLPC-XO-1] and access to a Windows or Fedora computer)

====On Windows:====

Create the USB stick as described on the [[Sugar on a Stick/Windows]] page in the "Windows Instructions" section.

Do '''not''' boot this stick on your Windows machine. Make sure the first boot is on your XO. If you do boot the stick on another machine first, the X server setup needed for the XO will not be done.

====On Fedora:====
Type the following commands in a terminal window:
wget {{SoaS-2 path}}
 
sudo yum install livecd-tools
 
wget -O livecd-iso-to-disk.sh "http://git.fedoraproject.org/git/?p=hosted/livecd;a=blob_plain;f=tools/livecd-iso-to-disk.sh;hb=HEAD"
 
sudo ./livecd-iso-to-disk.sh --format --xo --xo-no-home {{SoaS-2 image}} /dev/sd''X''1

Where <code>/dev/sdX1</code> is the device associated with your removable media.

The livecd-iso-to-disk.sh script needs to be a current version with XO support (not what you get by default in Fedora 10, though Fedora 11's should be fine). You can find an up-to date version in the SoaS disk image /LiveOS/livecd-iso-to-disk.sh .

===Option 2: Install a v0.84 SoaS-XO image on the XO-1 NAND flash drive===
See http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg05231.html and https://www.redhat.com/archives/fedora-olpc-list/2009-June/msg00063.html

This build feels substantially faster than 802 (the last stable release). Serious issues:

* No sound
* No automounting of USB keys.

===Option 3: Convert a v0.84 Sugar on a Stick .iso image===

'''Note''': Requires a [http://wiki.laptop.org/go/Activation_and_developer_keys developer key for your OLPC-XO-1] and access to a GNU/Linux computer) It also requires a recent OFW version (Q2E28 has been reported as working. [http://wiki.laptop.org/go/Manual_Firmware_Install Instructions for updating your firmware]).

'''WARNING''': this will overwrite all data on your OLPC-XO-1 NAND!!

On a Fedora10 system:

sudo yum -y install crcimg mtd-utils

On Debian or Ubuntu:

sudo apt-get install mtd-utils

:(On some older Debian/Ubuntu builds, you may need to install mtd-tools instead.)

:crcimg is not packaged for Debian so you'll have to build it:

wget http://dev.laptop.org/~mstone/releases/SOURCES/crcimg-1.1.tar.bz2
tar xvf crcimg-1.1.tar.bz2
sudo make -f Makefile.build install

NB:Of course, if you do not have the packages of the order wget, to install them by the order “yum install wget”

Next:

wget http://dev.laptop.org/~cjb/rawhide-xo/livecd-iso-to-xo.sh
wget {{SoaS-2 path}}

run this command (or something similar depending on the version number of your .iso file)

sudo sh livecd-iso-to-xo.sh {{SoaS-2 image}} Soas.img

and then copy Soas.img and Soas.crc to a USB key or SD card

On the OLPC-XO-1, boot with the USB key plugged in and the four game keys press to get to the OK prompt in Open Firmware (OFW).

Type the following commands:

disable-security
copy-nand u:\Soas.img

Note: depending upon the file system on your USB key, the names maybe truncated:

dir u:\
copy-nand u:\SOAS-2~1.img

You should see an animation of the blocks being written to the NAND. When it is complete, you will be back at the OK prompt. Type:

reboot

and the OLPC-XO-1 will reboot and you should be running Sugar 0.84.

===Option 4: Update to the official OLPC v0.82 Sugar build===
(This does ''not'' give you a '''Sugar on a Stick''' image.)

You run ''olpc-update'' from the Terminal activity, ''e.g.'',:

sudo olpc-update 802

where 802 is the build number of the [[OLPC:OS images | latest stable image]] from OLPC. This is OLPC release 8.2.1, incorporating Sugar v0.82.

[[Supported_systems#Fedora_on_an_OLPC_XO]] has some more details on upgrading OLPC software.

== Notes on running Sugar on a Stick on XO-1 ==
* You must hold down the XO-1's '''✓''' ("check") gamepad key during boot, otherwise boot will hang at the gray "XO" logo. You should see dots appear under the USB flash drive icon indicating the XO is booting from that drive.

* SoaS-2 images are based on Fedora "Rawhide" spins; [[olpc:Rawhide-XO]] describes many of the known issues running these on an XO-1.

* Also make sure you got a dev-key before booting with the SoaS using the check button..

----
[[Downloads|back to downloads page]]
__NOTOC__

[[Category:HowTo]]

Sugar on a Stick/Installation/OLPC

2009-07-08T04:17:14Z

Jpritikin: /* Do you have an OLPC XO-1? */

<noinclude>{{ Translations | [[Sugar_on_a_Stick/Installation/OLPC|english]] | [[Sugar_on_a_Stick/Installation/OLPC/lang-es|español]] | [[Sugar_on_a_Stick/Installation/OLPC/lang-fr|français]] }} {{ 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>

==Do you have an OLPC XO-1?==

[[image:OLPCXO.png]]


Sugar 0.84 has a number of improvements above and beyond 0.82. And we have a version working on the OLPC XO-1, but because of the changes in process at OLPC (see [[olpc:Future releases]]), there is a new short-term strategy for updates. Until OLPC issues its next official release, we are recommending that XO-1 users who would like to try 0.84 use Sugar on a Stick. The XO-1 can be booted from an external USB or SD card storage device, [[#Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB|Option 1]] below.

----

There are four main options for OLPC XO users:
# Run v0.84 Sugar on a Stick from a USB flash drive or SD card
# Install v0.84 Sugar on a Stick-XO on the XO-1's internal NAND flash memory
# Convert a v0.84 Sugar on a Stick .iso image to one suitable to install on the XO-1's internal NAND flash memory
# Use <tt>olpc-update</tt> to update to the latest software release from OLPC (which is currently 8.2.0 incorporating Sugar v0.82).

'''Note:''' The OLPC XO-1 has some built-in protections which lock the computer down in order to prevent haphazard software changes. In order to use either [[#Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB|Option 1]], [[#Option 2: Install a v0.84 SoaS-XO image on the XO-1 NAND flash drive|Option 2]], or [[#Option 3: Convert a v0.84 Sugar on a Stick .iso image|Option 3]], XO-1 owners must [http://wiki.laptop.org/go/Activation_and_developer_keys request a developer key from OLPC]; it's a simple process but takes up to 24 hours.

'''Warning:''' Options 2 & 3 will wipe /security directory, with any leases or devkeys there.

===Option 1: Run v0.84 of Sugar on a Stick from an SD card or external USB===

(Requires a [http://wiki.laptop.org/go/Activation_and_developer_keys developer key for your OLPC-XO-1] and access to a Windows or Fedora computer)

====On Windows:====

Create the USB stick as described on the [[Sugar on a Stick/Windows]] page in the "Windows Instructions" section.

Do '''not''' boot this stick on your Windows machine. Make sure the first boot is on your XO. If you do boot the stick on another machine first, the X server setup needed for the XO will not be done.

====On Fedora:====
Type the following commands in a terminal window:
wget {{SoaS-2 path}}
 
sudo yum install livecd-tools
 
wget -O livecd-iso-to-disk.sh "http://git.fedoraproject.org/git/?p=hosted/livecd;a=blob_plain;f=tools/livecd-iso-to-disk.sh;hb=HEAD"
 
sudo ./livecd-iso-to-disk.sh --format --xo --xo-no-home {{SoaS-2 image}} /dev/sd''X''1

Where <code>/dev/sdX1</code> is the device associated with your removable media.

The livecd-iso-to-disk.sh script needs to be a current version with XO support (not what you get by default in Fedora 10, though Fedora 11's should be fine). You can find an up-to date version in the SoaS disk image /LiveOS/livecd-iso-to-disk.sh .

===Option 2: Install a v0.84 SoaS-XO image on the XO-1 NAND flash drive===
See http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg05231.html and https://www.redhat.com/archives/fedora-olpc-list/2009-June/msg00063.html

===Option 3: Convert a v0.84 Sugar on a Stick .iso image===

'''Note''': Requires a [http://wiki.laptop.org/go/Activation_and_developer_keys developer key for your OLPC-XO-1] and access to a GNU/Linux computer) It also requires a recent OFW version (Q2E28 has been reported as working. [http://wiki.laptop.org/go/Manual_Firmware_Install Instructions for updating your firmware]).

'''WARNING''': this will overwrite all data on your OLPC-XO-1 NAND!!

On a Fedora10 system:

sudo yum -y install crcimg mtd-utils

On Debian or Ubuntu:

sudo apt-get install mtd-utils

:(On some older Debian/Ubuntu builds, you may need to install mtd-tools instead.)

:crcimg is not packaged for Debian so you'll have to build it:

wget http://dev.laptop.org/~mstone/releases/SOURCES/crcimg-1.1.tar.bz2
tar xvf crcimg-1.1.tar.bz2
sudo make -f Makefile.build install

NB:Of course, if you do not have the packages of the order wget, to install them by the order “yum install wget”

Next:

wget http://dev.laptop.org/~cjb/rawhide-xo/livecd-iso-to-xo.sh
wget {{SoaS-2 path}}

run this command (or something similar depending on the version number of your .iso file)

sudo sh livecd-iso-to-xo.sh {{SoaS-2 image}} Soas.img

and then copy Soas.img and Soas.crc to a USB key or SD card

On the OLPC-XO-1, boot with the USB key plugged in and the four game keys press to get to the OK prompt in Open Firmware (OFW).

Type the following commands:

disable-security
copy-nand u:\Soas.img

Note: depending upon the file system on your USB key, the names maybe truncated:

dir u:\
copy-nand u:\SOAS-2~1.img

You should see an animation of the blocks being written to the NAND. When it is complete, you will be back at the OK prompt. Type:

reboot

and the OLPC-XO-1 will reboot and you should be running Sugar 0.84.

===Option 4: Update to the official OLPC v0.82 Sugar build===
(This does ''not'' give you a '''Sugar on a Stick''' image.)

You run ''olpc-update'' from the Terminal activity, ''e.g.'',:

sudo olpc-update 802

where 802 is the build number of the [[OLPC:OS images | latest stable image]] from OLPC. This is OLPC release 8.2.1, incorporating Sugar v0.82.

[[Supported_systems#Fedora_on_an_OLPC_XO]] has some more details on upgrading OLPC software.

== Notes on running Sugar on a Stick on XO-1 ==
* You must hold down the XO-1's '''✓''' ("check") gamepad key during boot, otherwise boot will hang at the gray "XO" logo. You should see dots appear under the USB flash drive icon indicating the XO is booting from that drive.

* SoaS-2 images are based on Fedora "Rawhide" spins; [[olpc:Rawhide-XO]] describes many of the known issues running these on an XO-1.

* Also make sure you got a dev-key before booting with the SoaS using the check button..

----
[[Downloads|back to downloads page]]
__NOTOC__

[[Category:HowTo]]

Sugar on a Stick/Strawberry

2009-06-25T04:49:53Z

Jpritikin: /* Sugar on a Stick - Strawberry */

<noinclude>{{ GoogleTrans-en2 | es =show | sq =show | bg =show | ca =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | et =show | tl =show | fi =show | fr =show | gl =show | de =show | el =show | hi =show | hu =show | id =show | it =show | ja =show | ko =show | lv =show | lt =show | mt =show | no =show | pl =show | pt =show | ro =show | ru =show | sr =show | sk =show | sl =show | sv =show | th =show | tr =show | uk =show | vi =show | ar =show | iw =show | fa =show }}</noinclude>
[[Image:SugarLabs3x.jpg|right]]

== Sugar on a Stick - Strawberry ==

'''Release Notes - last update: 2009/06/24'''

This document provides instructions for preparing a Sugar on a Stick (SoaS) installation. It also contains a list of known issues and sources of further information, for example how to use a Boot Helper CD for very old PCs. For more detailed information, please check the [[Sugar_on_a_Stick|SoaS wiki page]].

The Sugar on a Stick Strawberry release is based on Fedora 11 with the latest updates as of June 22. It also features the latest Sugar learning environment, namely [[DevelopmentTeam/Release/Releases/Sucrose/0.84| version 0.84]], including 40 Activities to enrich the learning experience. Hundreds of Activities are available for download from the [http://activities.sugarlabs.org/ Sugar Activity Library]. This release is a step forward from the [[Sugar_on_a_Stick/Beta| beta release]]; in addition to Fedora updates, it includes supplementary sample content, which is available in the Journal. Apart from the default [[Sugar_on_a_Stick/Roadmap#Fructose_modules_.28F11.29|Fructose]] activities, additional Activities are included in this release. (See the Sugar [[Taxonomy]] for an explanation of these codenames.)
{{TOCright}}

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
| '''Fructose Activity''' || || '''Honey Activity''' || '''Honey Activity'''
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4024 Browse] || || [http://activities.sugarlabs.org/en-US/sugar/addon/4037 CartoonBuilder] || [http://activities.sugarlabs.org/en-US/sugar/addon/4063 Memorize]
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4076 Calculate] || || [http://activities.sugarlabs.org/en-US/sugar/addon/4050 Colors] || [http://activities.sugarlabs.org/en-US/sugar/addon/4034 Moon]
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4069 Chat] || || [http://activities.sugarlabs.org/en-US/sugar/addon/4044 FlipSticks] || [http://activities.sugarlabs.org/en-US/sugar/addon/4082 Paint]
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4030 Etoys] || || [http://activities.sugarlabs.org/en-US/sugar/addon/4054 FreeCell] || [http://activities.sugarlabs.org/en-US/sugar/addon/4193 Physics]
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4032 Image Viewer] || || [http://activities.sugarlabs.org/en-US/sugar/addon/4042 InfoSlicer] || [http://activities.sugarlabs.org/en-US/sugar/addon/4074 Poll]
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4045 Jukebox] || || [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC] || [http://activities.sugarlabs.org/en-US/sugar/addon/4081 Record]
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4056 Log] || || [http://activities.sugarlabs.org/en-US/sugar/addon/4046 JigsawPuzzle] || [http://activities.sugarlabs.org/en-US/sugar/addon/4047 SliderPuzzle]
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4041 Pippy] || || [http://activities.sugarlabs.org/en-US/sugar/addon/4064 JokeMachine] || [http://activities.sugarlabs.org/en-US/sugar/addon/4038 Speak]
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4028 Read] || || [http://activities.sugarlabs.org/en-US/sugar/addon/4078 Labyrinth] || [http://activities.sugarlabs.org/en-US/sugar/addon/4073 StoryBuilder]
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4043 Terminal] || || [http://activities.sugarlabs.org/en-US/sugar/addon/4089 Library] || [http://activities.sugarlabs.org/en-US/sugar/addon/4039 ViewSlides]
|-
| [http://activities.sugarlabs.org/en-US/sugar/addon/4027 Turtle Art] || || ||
|-
| Write || || ||
|}

=== Get it! ===

When downloading, please pick a download server close to your current location! Here is a list with possible locations.

(The download is a CD-ROM disc image .iso file (380 MiB) that could be burned to and booted from a CD drive like a LiveCD—but no work or changes will be saved after shutdown.)

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
| '''Location''' || '''Link'''
|-
| U.S. ''master'' || http://download.sugarlabs.org/soas/releases/soas-strawberry.iso
|-
| Netherlands ''mirror'' || http://ftp.snt.utwente.nl/pub/software/sugarlabs/soas/releases/soas-strawberry.iso
|-
| Netherlands ''mirror'' || http://ftp.nluug.nl/pub/os/Linux/distr/Sugar/soas/releases/soas-strawberry.iso
|-
|}

==== Windows Users ====

# Download the latest version of Fedora ''LiveUSB Creator'' from http://fedorahosted.org/liveusb-creator/ and extract it;
# Plug a target USB flash drive into your computer (minimum 1-gigabyte);
# Use the ''Format'' dialog to rename your USB ''Volume'' to FEDORA;
# Launch ''LiveUSB Creator'';
# Select ''Sugar on a Stick v1 Strawberry'' in the drop-down menu on the upper-right side of the ''LiveUSB Creator'' window;
# Set the ''Persistent Storage'' slider to at least 160 MB (use more if you have a drive with more space);
# Select your USB flash drive as the target;
# Click the ''Create Live USB'' button and then wait for the process to finish (about 5 minutes);
# Eject the USB flash drive using the ''Safely Remove Hardware'' dialog.
: More information is available [[Sugar on a Stick/Windows|here]].

==== Linux Users ====

# Download the SoaS iso image from http://download.sugarlabs.org/soas/releases/soas-strawberry.iso
# Install these three packages: ''syslinux'', ''isomd5sum'', and ''cryptsetup''
# Download this script: http://download.sugarlabs.org/soas/releases/livecd-iso-to-disk.sh
# Plug your target USB flash drive into your computer;
# Unmount the USB flash drive (e.g., <code>sudo umount /dev/sdb1</code>);
# Execute the script with the following command:
#:<code>sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-strawberry.iso /dev/sdb</code>

:'''Note:''' In this example, your USB device would be sdb! Adjust this before confirming the command, if necessary. Also, you might want to increase the home or overlay size if you have more than 1 GB of space.
: More detailed information is available [[Sugar on a Stick/Linux|here]].
==== Mac Users ====

Mac users will need to have access to a Linux or Windows machine to prepare their USB flash drive.
# Create your SoaS as described above;
# Download the boot helper disk: http://download.sugarlabs.org/soas/releases/soas-boot.iso
# Put both the CD and the USB flash drive into the machine;
# Turn the Mac on and press at the chime the "C" key;
# It should boot from the CD and continue to use the USB flash drive from this point.
:'''Note:''' This is an experimental method to run SoaS on a Mac. Not all hardware configurations might be supported, as it is also noted in the [[#Known Issues]] section below. If you run into issues, you might want to consider using a virtual machine. See [[#XO-1 & Virtual Machines]] section below.
: More information is available [[Sugar on a Stick/Mac|here]].
==== XO-1 & Virtual Machines ====

The use of SoaS on the OLPC XO-1, as well as in virtual machines, is currently in an experimental state. Instructions for both categories are being developed here for [[Sugar on a Stick/Installation/OLPC|XO-1]], [[VirtualBox]], & [[VMware#Soas-Strawberry.iso_installed_to_VM_Hard_Disk|VMware]]. In the meantime, you might want to refer to the information on the general SoaS [[Sugar_on_a_Stick| wiki page]].

=== Boot it! ===

* Set the option to boot from USB in your machine's BIOS and let it come up.
* If your machine doesn't support booting from USB devices, then download and burn http://download.sugarlabs.org/soas/releases/soas-boot.iso.
** Make sure to name your USB flash drive FEDORA, as it won't be recognized otherwise.
** Put both the boot-support CD and the USB flash drive in your computer and let it boot from the CD.

=== Use it! ===

Once you have successfully launched Sugar on a Stick, you should explore the Sugar Learning Platform. There is a [http://en.flossmanuals.net/sugar guide to Sugar] and help pages dedicated to most activities. (Do try running Sugar on more than one machine so you can enjoy its collaboration features.)

== Help Us ==

Please share your feedback with us; it will help us to improve Sugar in subsequent versions of SoaS. You can always send an e-mail to [mailto:feedback@sugarlabs.org feedback@sugarlabs.org] or join the ''<nowiki>It's an Education Project</nowiki>'' mailing list: http://lists.sugarlabs.org/listinfo/iaep. See all our [[Sugar Labs/Contacts|'''communication channels''']] and our [[Sugar Labs/Getting Involved|'''Getting Involved''']] pages.

If you encounter any hardware-related issues besides the ones [[#Known Issues|listed below]], please consider joining our [[Sugar_on_a_Stick/Hardware| hardware effort]]. Please submit the specifications of your hardware so that we work together with 'upstream' to resolve any issues.

Finally, you might also consider submitting bug reports at our [http://dev.sugarlabs.org/ bug tracker] (you would need to create an account).

=== Known Issues ===

Sugar on a Stick Strawberry is based on [http://www.fedoraproject.org/ Fedora 11], the latest release. Consequently, it contains a number of known issues with Fedora images that should be mentioned.
* Recently, problems with ATI graphics hardware, as well as various Mac models have been reported. This was resolved by adding the ''nomodeset'' parameter to the kernel arguments.
* If you encounter image flickering or are not able to get past a black screen, it might be worth pressing the <Escape> key at the blue screen, which appears for a second before the normal boot process starts. You'll be presented a short menu, at which you can directly press tab, then just add the ''nomodeset'' argument in the appearing line, and then boot by pressing the <Enter> key.
For more information, please refer to the [http://fedoraproject.org/wiki/Common_F11_bugs#Hardware-related_issues list of common F11 bugs].

=== Custom Builds ===

Preliminary instructions how to customize and compose an image can be found [[Sugar_on_a_Stick/Customization| here]].

Education Team/Resources

2008-09-30T17:36:16Z

Jpritikin:

<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 }}
{{TeamHeader|EducationTeam}}</noinclude>
The knowledge base for Education will include links to a variety of materials that are important for understanding where we are and where we might be going.

==Resources==
* [[EducationTeam/Education Biblographies]]
* Libraries
* Journals
* [[EducationTeam/Evaluation Studies]]
* Popular press
* Book publishers
* Organizations
* Ministries of Education: Curricula, textbook standards, teacher training
* Teacher training: Schools of Education, On-the-job training, continuing education
**[[EducationTeam/Lesson Plan resources]]

==Theories of Knowledge and Understanding==
* Epistemologies: How do we know, or do we?
* Ontologies
* Ethics
* Psychology
* Neurology

==History of Educational Thought and Practice==
* Traditional cultures: rites of passage, formal and informal learning, ...
* Ancient civilizations: Greece, China, India...
* The Catholic Church: Dark Ages, Carolingian schools, teaching orders, the rise of the Universities, the Counter-Reformation
* Other Christian theories: Lutheran, Calvinist, Quaker (Friends), Anabaptist...
* Scientific study: William James, John Dewoy, Montessori, Gattegno, Piaget...
* Computers in education: Omar Khayyam Moore (sic), Ken Iverson, Howard Peelle, Seymour Papert and Constructionism, Alan Kay

==Studies of Educational Methods==
* Saul Rockman
* Larry Cuban, Oversold and Underused
* Tom Russell, [http://nosignificantdifference.wcet.info/ No Significant Difference Phenomenon] Web site and [https://www.arello.org/store/default.cfm?prodlistid=16-17 book]
* Richard Rorty

==Theories of Education==

* Tradition
* Plato
* Aristotle
* Dogma
* Craft guilds: Apprentices, journeymen, and masters
* Social control
* Liberal education
* Prussia
* Dewey
* Montessori
* Piaget and Vygotsky
* John Holt
* Papert and Kay

==Child Development==

* Physical development
* Languages
* Social development
* Learning disabilities and talents
* Understanding of the world

==Subject matter==
* Agriculture
* Hunting
* Combat and command
* Religion
* Conflict and negotiation
* Business, finance
* Economics
* Math
* Science
* Logic
* Speaking
* Physical sciences
* Biology
* Social sciences
* History
* Geography
* Languages and literature
* Art
* Music

==Educational Technology==
* Reading and writing, print, online
* Lectures (originally dictation)
* Film and video
* Photographs
* Sound recordings
* Computers and software tools: programming languages, content creation, human language support, standards, Free/Open Source Software
* Distance learning
* [http://peeredit.us Peer Editing Exchange]

Sugar Labs/Current Events

2008-09-30T17:32:11Z

Jpritikin:

Sugar Labs/Background

2008-05-10T15:44:53Z

Jpritikin:

The past two-to-three years has seen the advent of a number of efforts to bring about a global transformation of education through the provision of connected '''“ultra-low-cost” laptop computers''', notably the OLPC XO-1 laptop, the Intel Classmate, the ASUS EEE; the One2OneMate StudentMate, and, most recently, the HP Mini-Note and Elonex ONE. While there are distinctions between these various hardware offerings in terms of display quality, MIPS, power consumption, etc., each provides an agency through which positively impact learning, and consequently, everything that learning impacts, in particular, economic development.

These efforts, by both for-profit and not-for-profit organizations, are ultimately about giving children who don't have the opportunity for learning that opportunity: it's about access; it's about equity; and it's about giving the next generation of children in the developing world a bright and open future.

These efforts are predicated on the fact that '''children lack opportunity, not capability''':
# High-quality education for every child is essential to facilitate an equitable and viable society;
# A connected laptop computer is the most powerful tool for knowledge creation;
# Access on a sufficient scale provides real benefits for learning because critical mass is necessary to establish a sustainable community.

A connected laptop is ''not in itself'' a cure to the problems of poverty and ignorance, but it is an agency through which children, their teachers, their families, and their communities can ''manufacture a cure''. Computers are tools with which to think, sufficiently inexpensive to be used for work and play, drawing, writing, measuring, composing, editing, mathematical thinking, programming, communication, and sustainable economic development.

'''How big an opportunity is this?''' In just its first six months of mass production, One Laptop per Child Association shipped 0.5 million laptops. Other vendors are claiming sales at a similar volume. Unequivocally, a market for an ultra-low-cost laptop computer is only just emerging and with it comes an opportunity to impact learning. The challenge now is to engage more people in participating in this '''global learning initiative''' and to shape the initiative such that it has not just maximum reach, but also maximum impact.

[[Learning learning]]

Development Team/Jhbuild

2007-02-16T09:43:12Z

Jpritikin: /* Build sugar base system and its dependencies */

One of the easiest ways to install [[Sugar]] is to use sugar-jhbuild.

Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale. Below are generic instructions on how to use sugar-jhbuild to get up and running with Sugar.

'''Note:''' Some Linux distributions may need or have special procedures; you can check the pages on [[:Category:Installing Sugar|installing Sugar]] to see if they are available.

==Checkout sugar-jhbuild==

git-clone git://dev.laptop.org/sugar-jhbuild

==Build sugar base system and its dependencies==

Change directory and start the build.

cd sugar-jhbuild
./sugar-jhbuild build

For the base packages (i.e. <tt>build-base</tt>),
you should be able to use the binary packages from your GNU distribution
instead of building them from scratch. Distribution specific hints here:
[[Suger-base:Debian]]

==Run Sugar==

./sugar-jhbuild run

== Other commands ==

JHBuild has several other commands that can be useful for development. You can get an overview with:

./sugar-jhbuild --help-commands

A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]:

./sugar-jhbuild update
./sugar-jhbuild build-base
./sugar-jhbuild build
./sugar-jhbuild run

== Customize ==

To customize the build create a configuration file, named .olpc.jhbuildrc, in your home directory.

=== Write access to the repositories ===

If you have write access to the repositories you can add:
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'
repos['git.laptop.org'] = 'git+ssh://dev.laptop.org/git/artwork'

==External links==

* [http://www.gnome.org/~jamesh/jhbuild.html JHBuild manual]

[[Category:Installing Sugar]]

Development Team/Jhbuild

2007-02-16T08:59:06Z

Jpritikin: /* Build sugar base system and its dependencies */

One of the easiest ways to install [[Sugar]] is to use sugar-jhbuild.

Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale. Below are generic instructions on how to use sugar-jhbuild to get up and running with Sugar.

'''Note:''' Some Linux distributions may need or have special procedures; you can check the pages on [[:Category:Installing Sugar|installing Sugar]] to see if they are available.

==Checkout sugar-jhbuild==

git-clone git://dev.laptop.org/sugar-jhbuild

==Build sugar base system and its dependencies==

Change directory and start the build.

cd sugar-jhbuild
./sugar-jhbuild build

You should be able to use the binary packages from your GNU distribution
instead of building them from scratch. Distribution specific hints here:
[[Suger-base:Debian]]

==Run Sugar==

./sugar-jhbuild run

== Other commands ==

JHBuild has several other commands that can be useful for development. You can get an overview with:

./sugar-jhbuild --help-commands

A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]:

./sugar-jhbuild update
./sugar-jhbuild build-base
./sugar-jhbuild build
./sugar-jhbuild run

== Customize ==

To customize the build create a configuration file, named .olpc.jhbuildrc, in your home directory.

=== Write access to the repositories ===

If you have write access to the repositories you can add:
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'
repos['git.laptop.org'] = 'git+ssh://dev.laptop.org/git/artwork'

==External links==

* [http://www.gnome.org/~jamesh/jhbuild.html JHBuild manual]

[[Category:Installing Sugar]]