Sugar Labs - User contributions [en]

Archive/Current Events/2009-03-17

2009-05-10T11:13:02Z

Jcarroll: Fixed a handful of minor errors.

<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>{{TOCright}}
=== Sugar Digest ===

1. Now that the Sugar community and the Release Team have wrapped up 0.84, it is time to talk about our “Big Overarching Vision Goals for 2009” I've written some notes in order to kick off the discussion.

'''What are our objectives?'''

In an era of ''limited resources'' there is still pressure to equate 21st Century skills with learning to use Microsoft Office™; it is more important than ever to promote the use of free software that encourages learners to acquire critical-thinking skills, and to further the development of diverse communities of development and support around the needs of teachers and learnings. Children are not office workers and nothing in their future will resemble office work from 30-years ago. Our collective future is dependent on our children's ability to develop creative problem-solving and collaboration skills, which is not the same as “excelling” in the use of one word processor versus another.

'''What are our strategies for achieving these objectives?'''

While there are hundreds of instances of powerful learning tools, there are only a handful of efforts to create learning platforms. Sugar is such a platform. It is not a one-size-fits-all solution to learning—the one right way; rather is about a change in culture: computing as a resource employed by the learner as opposed to a service provided to the learner.

Sugar is new; it is incomplete; it has its rough edges. Over time, it will become more refined. But Sugar will always be demanding: We impose a level of discomfort because we demand a level of engagement missing from most educational software: Sugar is about the “hard fun” of learning as opposed to the facility of empty consumption.

It takes time to make a deep, systemic impact that results in a change in culture. Our collective efforts at Sugar Labs have influence, but the many challenges posed by the economic crisis, budget cuts, the energy crisis, global communication, “clash of civilizations”, etc. are mandating real change to the status quo. We have to be cognizant of these external influences.

'''What are our short- and long-term (measurable) goals?'''

Growth is an ambitious goal during a global recession; nonetheless, the goals for Sugar Labs in 2009 are to grow its community, broaden its code base, and most important, increase the number of children using Sugar.

While the core of the Sugar software development community is tremendously dedicated, tireless and talented, we are always going to be in need of more hands. While we have been growing this community incrementally—your enthusiasm is infectious—step-wise growth will occur when local Sugar Labs start coming on line. The launch of a half-dozen “labs” that engage local high-school and university students in making real contributions to global free software project is not an unreasonable goal for 2009 and it would easily double the size of development community.

Coupled with growing the software development community is growing the Sugar education community. We are beginning to cultivate a climate where the teachers who have been using Sugar in their classrooms are comfortable engaging in discussions among themselves and in some cases, with the development community. This trend is especially evident on the Sur list and in the blog sphere. Their feedback has been of tremendous value. But most teachers not actually part of a Sugar deployment are hardly aware of Sugar and until they make the transition from awareness to giving it their attention, they will not be engaged. Building a Sugar presence in the forums that teachers habituate is an important goal for 2009.

Sugar is a learning platform, so it is only relevant when it is in the hands of learners. By the end of 2009, we'll have reached over one-million children through Sugar deployments on OLPC-XO-1 computers. It is an ambitious but reasonable goal to reach as many children through other means of distributing Sugar as well: Sugar on netbooks; Sugar on a Stick; Sugar deployed through a terminal server. We have laid the ground-work over the past six months, working with the packaging teams of a number of GNU/Linux distributions; now is the time to leverage those efforts.

'''What are the means of getting there?'''

Getting our message out—also known as marketing—is a key to our growth. We've been living under the shadow of One Laptop per Child, which has meant that we have been able to focus on creating great tools, arguably without (many) distractions. This has changed and in response, our marketing team has stepped up the clarity and quality of its efforts. (I am particular excited about the possibility of the viral marketing of Sugar.) However, we are being diligent about not over promising—we will stand behind our message.

On the technical front, we will be spending the next few months setting the goals for Sucrose-0.86. High on my list are better integration of SWF, Javascript, and non-Sugarized applications in general. I think we can do more to bring the gap between Sugar and other approaches, both so that we can invite more people under our tent and also let Sugar be a part of other efforts. Sugar on a Stick v1.0, will be launched in 2009 as well.

In terms of teacher outreach, we are exploring more formal and informal means of engagement. The proposal to the US National Science Foundation that we submitted last week focuses on a global assessment of Sugar deployments. The survey we are putting together for the teachers in Uruguay this week will be a vehicle for data gathering, but also a means to bring to the attention of teachers the importance of feedback. I expect that this by-product will result in a more in-depth, on-going channel. Local Sugar Labs will help in this regard as well.

'''Let the debate begin'''

These are my thoughts about our 2009 goals. I haven't mentioned important topics such as support and documentation. And I am sure that we'll find lots disagreement on the technical front. And as we are always going to be shorthanded, we'll always have to make trade-offs regarding competing goals and means. But by adhering to the principles of free and open debate, we'll continue to be able to leverage the benefits of our differences and our diversity. We will accomplish great things this year.

2. The new "static" website is live. Please visit and enjoy http://www.sugarlabs.org. Many thanks to Christian Schmidt for his great efforts. This new landing site promises to be much more accessible to parents and teachers than the wiki.

3. Dave Farning was the Sugar Labs representative at the Winter Camp meeting of FLOSS Manuals in Amsterdam last week. The FLOSS Manual effort continues to build momentum around community publishing. Anne Gentle just sent out a call for volunteers to help refresh the Sugar Manual in light of 0.84.

“Ideally we can complete revisions and screenshot updates by March 16th to coordinate with the software release itself.”

You can register for a login with FLOSS Manuals at [http://en.flossmanuals.net/bin/view/Main/UserRegistration?origurl=/bin/view/Main/WebHome User Registration].

Once these updates are completed, FLOSS Manuals will offer a printed book for sale on Amazon (once we get the process ironed out) and Lulu. PDF and HTML versions are always available for free.

4. Recommended reading. Bernie Innocenti circulated a link to some interesting reading about software projects. Don't be put off by the title—there are some good ideas here ([http://www.kalzumeus.com/2009/03/07/how-to-successfully-compete-with-open-source-software/ How to successfully compete with open-source software]).

=== Community jams, meet-ups, and meetings ===

5. Fernando da Rosa is hosting a workshop for teachers ([http://www.fedaro.info/ Jornadas de Educación y TIC]) this week in Montevideo. We hope to [[Education_Team/Survey_questions|survey]] the attendees about their Sugar experience.

=== Help Wanted / Help Received ===

6. We need to clean up the [[Development Team/Project Ideas|Project Ideas]] page for our Google Summer of Code application. Please add any pet idea that they would like an intern to tackle.

7. Bastien Guerry has set up a [[Translation|translation wish-list page]] in the wiki.

8. We would very much like to include some photographs of children using Sugar (as opposed to generic child with computer) for the website. If you have any such pictures (or can take some this week), please contact the Marketing Team.

=== Tech Talk ===

9. In addition to the update to the FLOSS Manual, the Release Team is pulling together notes for Sucrose 0.84. They are requesting help from Activity maintainers. Please use the [[Development Team/Release/Releases/Sucrose/0.84/Activity Template|Template]] to create a page and link it appropriately
on the [[Development Team/Release/Releases/Sucrose/0.84#Fructose_2|0.84 release notes page]]. As an example, see the [[Development Team/Release/Releases/Sucrose/0.84/Browse|Browse release notes]].

10. Daniel Drake has been doing some great testing of the School Server in Paraguay.

11. Michael Stone is working on a new version of Rainbow that will work wherever Sugar works. He is looking for feedback and testing (See http://wiki.laptop.org/go/Rainbow).

=== Sugar Labs ===

12. Gary Martin has generated another SOM from the past week of discussion on the IAEP mailing list (Please see [[:Image:2009-Feb-28-Mar-6-som.jpg|SOM]]).

[[Category:Sugar Digest]]

Oversight Board/2008/Meeting Minutes-2008-06-30

2008-07-08T03:51:25Z

Jcarroll: /* Governance and the Software Freedom Conservancy */

'''DRAFT'''

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

==Sugar Labs meeting, Monday, 30 June 2008==

Via Monte Napoleone, Milano, IT

Attending in person: Marco Pesenti Gritti, Paul Noja, Tomeu Vizoso, Walter Bender, Carlo Falciola, Franco Lodato, Luca Ferrari, Karen Sandler

Participating by [[Sugar_Labs/Meeting_Minutes-30-06-2008/irc-log|IRC (See log)]]: bernie, mostro, mk8, BryanWB, arjs, shenki, jg, cjb, reed, dwmw2, mtd, walter, marcopg

===Governance and the Software Freedom Conservancy===

Karen led a discussion about the implications of Sugar Labs joining the Conservancy. The SFC is a home for FOSS projects as an umbrella organization: FOSS projects become part of the Conservancy; they get tax-free status in the US; and the projects set up a day-to-day governance structure that is generally autonomous.

Shenki asked a question regarding any downsides. While there is always a unilateral mechanism to spin out from the Conservancy, by joining,

# We would be making a commitment to remain a non-profit organization in regard to any project assets (funds that we might raise, any copyrights or trademarks we might own);
# No projects have ever spun out on their own, so there may be some unknown obstacles; and
# There would be some administrative oversight (but we need it from somewhere).

The Conservancy has some concern that Sugar Labs might get so big as to incur too big of a burden for the Conservancy to pick up all administrative expenses without some mutually agreed mechanism of help from Sugar Labs.

Sugar Labs must designate one or two people to be the central point for communicating with the Conservancy regarding expenditures, reimbursements, etc. handled by the Conservancy on our behalf.

Joining the Conservancy means a commitment to both FOSS and non-profit status. However, there is and should be room for for-profit entities to grow up around Sugar Labs, offering support, extra services, such as ports, etc.

A question was raised in regard to working outside of the United States (the Conservancy is a US-based 501(c)(3)); while it hasn't been a problem, if necessary, projects within the Conservancy can work with organizations elsewhere—e.g., the Conservancy could help with administration of non-US programs without having to be involved in the funding—money can be raised and stay local, under local laws.

Karen made some in-line edits (mostly in the form of questions) to the Governance page in the wiki. We need to achieve a bit more clarity about a few topics, such as [[Sugar Labs/initial members list|initial membership]], terms of office, voting mechanics, etc. as part of the process of joining the Conservancy.

===What are we (Sugar Labs) trying to accomplish?===

Sugar Labs is the focal point for a community project that is providing the engineering and support for Sugar, a FOSS project that is designed to facilitate a collaborative and reflective set of learning activities. Sugar Labs is the upstream maintainer for the work and helps to promote it, but the development work itself is done downstream, in the community, both by volunteers and groups that want to offer services, in some cases for profit. There was consensus that Sugar Labs should manage the release process and the review process.

Bryan posited that the “conceptual integrity” and quality control of Sugar as a product needs to be maintained by Sugar Labs, but that Sugar Labs shouldn't try to constrain the educational approaches used by schools.

Shenki asked how OLPC and RedHat fit in. OLPC (and other platform providers) are downstream and should be pushing patches up to Sugar Labs, making their needs and point of view known to the community. We (the Sugar community) should strive to make our code work for everyone, not just OLPC, so that there is a broader context for support.

It was suggested that we set up a page in the wiki to let people advertise engineering and support services.

===Sugar distributions: what are the issues?===

The bulk of the discussion revolved around what are the best forms of distribution to facilitate people trying Sugar (and if they like it, installing it). We discussed targeting old Windows computers that might be in a school, for example—a version that teachers and students can use.

Carlo suggested that we make a matrix that explains more clearly what you get/don't get from different distribution models, such as a LiveCD, QEMU, etc. It was suggested that distributing Sugar on a USB image is perhaps the best option, since it lets you install additional activities, save files, etc.

Another topic was the need for better documentation: for example, the Sugar session on Ubuntu: Lot of undocumented little details, such as you cannot log out, so you need to either restart X (Ctrl-Alt-Backspace) or do a reboot (from the shell or the Homepage menu); and that you can copy activities directly into ~/Activities. The FLOSS Manuals project has offered to help with documentation; we are considering using the existing Trac system for documentation requests, bug reports, etc.

===Sugar Labs look and feel: a graphic design review===

Luca Ferrari and Franco Lodato presented some designs for a “corporate identity” for Sugar Labs. The designs are [[UITeam/Logo-ideas|posted in the wiki]] for feedback. (Karen pointed out the importance of trademarks with in the context of FOSS projects.)

===Sugar on mobile phones: is it possible? does it make sense?===

We also had a discussion about mobile devices. This is a topic that has been raised repeatedly in recent months and, while it doesn't seem to have a direct connection to Sugar's educational goals, it does seemingly broaden the developer community for Sugar (“growing the community”) and bring more people into the circle of collaboration with learners using Sugar-enabled devices.

Further, Sugar would probably make a pretty decent phone interface, especially in light of its clarity of design and its collaborative model.

Still, it was argued that a cellphone screen is a bad environment for learning and that it would not be a substitute for a laptop. Chris Ball asked, “What are the minimum requirements for expressiveness and learning when we work on a port of Sugar?”

We had some discussions about what would be involved in such a port and whom might be interested in doing it. (The Nokia N800 was suggested as a possible point of departure.)

===Sugar Labs: models of support===

This was in part a continuation of the discussion about purpose. The issue of long-term stability—both perception and reality were discussed: up-take of Sugar will be increased if there is a sense that it is going to be here and supported for the long run. It was argued that we need to help establish local and regional champions, ownership, and support.

:In “biologically inspired” architectures one is much more interested in how the organism and ecologies of them are to be sustained, and how the dynamical systems can be understood, fixed, changed, evolved, reformulated, etc., while they are running and with the help of tools that work within them. Just as a cell, and especially e. g. a human baby, is not made by hand, we are more interested in making growth processes that can be influenced with far more ease than direct construction. So, most objects are made by other objects acting under conditions that include the dynamic state in which they will become part of the ecology. —Alan Kay

What are the Sugar growth processes?

===Fund-raising: how much and from whom?===

We didn't really get into this topic in any detail accept to agree that order 10s of thousands of dollars would probably be adequate for currently anticipated needs: meeting support, outreach, etc.

We do need to discuss what venues would be useful in light of reaching both the developer and user (primarily learning) communities.

Oversight Board/2008/Meeting Minutes-2008-06-30

2008-07-08T03:50:34Z

Jcarroll: /* Governance and the Software Freedom Conservancy */

'''DRAFT'''

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

==Sugar Labs meeting, Monday, 30 June 2008==

Via Monte Napoleone, Milano, IT

Attending in person: Marco Pesenti Gritti, Paul Noja, Tomeu Vizoso, Walter Bender, Carlo Falciola, Franco Lodato, Luca Ferrari, Karen Sandler

Participating by [[Sugar_Labs/Meeting_Minutes-30-06-2008/irc-log|IRC (See log)]]: bernie, mostro, mk8, BryanWB, arjs, shenki, jg, cjb, reed, dwmw2, mtd, walter, marcopg

===Governance and the Software Freedom Conservancy===

Karen led a discussion about the implications of Sugar Labs joining the Conservancy. The SFC is a home for FOSS projects as an umbrella organization: FOSS projects become part of the Conservancy; they get tax-free status in the US; and the projects set up a day-to-day governance structure that is generally autonomous.

Shenki asked a question regarding any downsides. While there is always a unilateral mechanism to spin out from the Conservancy, by joining,

# We would be making a committed to remain a non-profit organization in regard to any project asset (funds that we might raise, any copyrights or trademarks we might own);
# No projects have ever spun out on their own, so there may be some unknown obstacles; and
# There would be some administrative oversight (but we need it from somewhere).

The Conservancy has some concern that Sugar Labs might get so big as to incur too big of a burden for the Conservancy to pick up all administrative expenses without some mutually agreed mechanism of help from Sugar Labs.

Sugar Labs must designate one or two people to be the central point for communicating with the Conservancy regarding expenditures, reimbursements, etc. handled by the Conservancy on our behalf.

Joining the Conservancy means a commitment to both FOSS and non-profit status. However, there is and should be room for for-profit entities to grow up around Sugar Labs, offering support, extra services, such as ports, etc.

A question was raised in regard to working outside of the United States (the Conservancy is a US-based 501(c)(3)); while it hasn't been a problem, if necessary, projects within the Conservancy can work with organizations elsewhere—e.g., the Conservancy could help with administration of non-US programs without having to be involved in the funding—money can be raised and stay local, under local laws.

Karen made some in-line edits (mostly in the form of questions) to the Governance page in the wiki. We need to achieve a bit more clarity about a few topics, such as [[Sugar Labs/initial members list|initial membership]], terms of office, voting mechanics, etc. as part of the process of joining the Conservancy.

===What are we (Sugar Labs) trying to accomplish?===

Sugar Labs is the focal point for a community project that is providing the engineering and support for Sugar, a FOSS project that is designed to facilitate a collaborative and reflective set of learning activities. Sugar Labs is the upstream maintainer for the work and helps to promote it, but the development work itself is done downstream, in the community, both by volunteers and groups that want to offer services, in some cases for profit. There was consensus that Sugar Labs should manage the release process and the review process.

Bryan posited that the “conceptual integrity” and quality control of Sugar as a product needs to be maintained by Sugar Labs, but that Sugar Labs shouldn't try to constrain the educational approaches used by schools.

Shenki asked how OLPC and RedHat fit in. OLPC (and other platform providers) are downstream and should be pushing patches up to Sugar Labs, making their needs and point of view known to the community. We (the Sugar community) should strive to make our code work for everyone, not just OLPC, so that there is a broader context for support.

It was suggested that we set up a page in the wiki to let people advertise engineering and support services.

===Sugar distributions: what are the issues?===

The bulk of the discussion revolved around what are the best forms of distribution to facilitate people trying Sugar (and if they like it, installing it). We discussed targeting old Windows computers that might be in a school, for example—a version that teachers and students can use.

Carlo suggested that we make a matrix that explains more clearly what you get/don't get from different distribution models, such as a LiveCD, QEMU, etc. It was suggested that distributing Sugar on a USB image is perhaps the best option, since it lets you install additional activities, save files, etc.

Another topic was the need for better documentation: for example, the Sugar session on Ubuntu: Lot of undocumented little details, such as you cannot log out, so you need to either restart X (Ctrl-Alt-Backspace) or do a reboot (from the shell or the Homepage menu); and that you can copy activities directly into ~/Activities. The FLOSS Manuals project has offered to help with documentation; we are considering using the existing Trac system for documentation requests, bug reports, etc.

===Sugar Labs look and feel: a graphic design review===

Luca Ferrari and Franco Lodato presented some designs for a “corporate identity” for Sugar Labs. The designs are [[UITeam/Logo-ideas|posted in the wiki]] for feedback. (Karen pointed out the importance of trademarks with in the context of FOSS projects.)

===Sugar on mobile phones: is it possible? does it make sense?===

We also had a discussion about mobile devices. This is a topic that has been raised repeatedly in recent months and, while it doesn't seem to have a direct connection to Sugar's educational goals, it does seemingly broaden the developer community for Sugar (“growing the community”) and bring more people into the circle of collaboration with learners using Sugar-enabled devices.

Further, Sugar would probably make a pretty decent phone interface, especially in light of its clarity of design and its collaborative model.

Still, it was argued that a cellphone screen is a bad environment for learning and that it would not be a substitute for a laptop. Chris Ball asked, “What are the minimum requirements for expressiveness and learning when we work on a port of Sugar?”

We had some discussions about what would be involved in such a port and whom might be interested in doing it. (The Nokia N800 was suggested as a possible point of departure.)

===Sugar Labs: models of support===

This was in part a continuation of the discussion about purpose. The issue of long-term stability—both perception and reality were discussed: up-take of Sugar will be increased if there is a sense that it is going to be here and supported for the long run. It was argued that we need to help establish local and regional champions, ownership, and support.

:In “biologically inspired” architectures one is much more interested in how the organism and ecologies of them are to be sustained, and how the dynamical systems can be understood, fixed, changed, evolved, reformulated, etc., while they are running and with the help of tools that work within them. Just as a cell, and especially e. g. a human baby, is not made by hand, we are more interested in making growth processes that can be influenced with far more ease than direct construction. So, most objects are made by other objects acting under conditions that include the dynamic state in which they will become part of the ecology. —Alan Kay

What are the Sugar growth processes?

===Fund-raising: how much and from whom?===

We didn't really get into this topic in any detail accept to agree that order 10s of thousands of dollars would probably be adequate for currently anticipated needs: meeting support, outreach, etc.

We do need to discuss what venues would be useful in light of reaching both the developer and user (primarily learning) communities.

Marketing Team/TODO

2008-07-07T20:46:29Z

Jcarroll:

<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|MarketingTeam}}</noinclude>

# Establish context
#* Role
#* Purpose
#* Resources
#* Responsibilities
# Establish goals

[[Category:MarketingTeam]]
</noinclude>

Talk:Marketing Team/FAQ

2008-07-07T20:44:15Z

Jcarroll: What is the Marketing Team?

== What is the Marketing Team? ==

Within the context of Sugar Labs, what are the roles and responsibilities of the Marketing Team?

User:Jcarroll

2008-07-07T20:43:19Z

Jcarroll:

I've been watching OLPC since 2005. I look forward to Sugar gaining acceptance in mainstream educational institutions.

Current Projects:
* Outlining goals for the [[MarketingTeam]]
* Misc. help with the wiki

See also:
* [http://en.wikipedia.org/wiki/User:Jcarroll My user page] on English Wikipedia
* [http://www.linkedin.com/in/jfcarroll My public profile] on LinkedIn

User:Jcarroll

2008-07-07T14:57:35Z

Jcarroll:

I've been watching OLPC since 2005. I look forward to Sugar gaining acceptance in mainstream educational institutions.

Current Projects:
* [[MarketingTeam]]
* Misc. help with the wiki

See also:
* [http://en.wikipedia.org/wiki/User:Jcarroll My user page] on English Wikipedia
* [http://www.linkedin.com/in/jfcarroll My public profile] on LinkedIn

Marketing Team/Contacts

2008-07-07T14:45:30Z

Jcarroll:

<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|MarketingTeam}}</noinclude>
== Mailing List ==
tbd

== IRC Channel ==
tbd

== Team Members ==
{|
! Area of Specialty''' !! '''Wiki Username'''
|-
| "I'm willing to help; what needs to be done?" || [[user:jcarroll]]
|-
| Everything || Your name here!
|}
[[Category:MarketingTeam]]

Marketing Team/Contacts

2008-07-07T14:45:08Z

Jcarroll: /* Team Members */

<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|MarketingTeam}}</noinclude>
== Mailing List ==
tbd

== IRC Channel ==
tbd

== Team Members ==
{|
! Area of Specialty''' !! '''Wiki Username'''
|-
| Everything || None
|-
| "I'm willing to help; what needs to be done?" || [[user:jcarroll]]
|}
[[Category:MarketingTeam]]

Supported systems

2008-05-25T10:37:52Z

Jcarroll: /* GLUCOSE */ added more OS's

==A matrix of Sugar "solutions"==

===STARCH===
{|border=1
|+ '''A complete disk image for Sugar'''
|-
!Name
!Sugar Version
!Tested
!Notes
|-
|[http://wiki.laptop.org/go/LiveBackup_XO-LiveCD LiveBackup XO-LiveCD]
|0.75.13-1
|Yes
|This is a Live CD of the OLPC system
|}

===SUCROSE===
{|border=1
|+ '''The interface, plus a set of demonstration activities'''
|-
!Sugar Version
!Tested
!Notes
|}

===GLUCOSE===
{|border=1
|+ '''The base Sugar environment'''
|-
!Operating System !! Version !! Sugar Version !!Tested !! Notes
|-
|Debian||4.0|| ||Yes||[http://wiki.laptop.org/go/Sugar_on_Debian Sugar on Debian]
|-
|Fedora||7,8,9|| || ||[http://wiki.laptop.org/go/Sugar_on_Fedora Sugar on Fedora]
|-
|Gentoo||"[amd64] as of 2007-12-13"[http://wiki.laptop.org/go/Sugar_on_Gentoo_Linux]|| ||Yes||[http://wiki.laptop.org/go/Sugar_on_Gentoo_Linux Sugar on Gentoo]
|-
|MacOS X|| || || ||[http://wiki.laptop.org/go/Sugar_on_MacOS_X Sugar on MacOS X]
|-
|Slackware||12|| || ||[http://wiki.laptop.org/go/Sugar_on_Slackware Sugar on Slackware]
|-
|Ubuntu||8.04 (Hardy)||0.79.0-0ubuntu3||Yes||[http://wiki.laptop.org/go/Sugar_on_Ubuntu_Linux Sugar on Ubuntu]
|-
|Windows||XP|| ||No.||[http://wiki.laptop.org/go/Sugar_on_Windows Sugar on Windows]
|}

===SYSTEMS===
{|border=1
|+ '''Complete Sugar Solutions'''
|-
!Manufacturer
!Model
!Operating System
!Tested
!Notes
|-
| [http://www.laptop.org OLPC]
| XO-1
| Fedora-7
| Yes
| Standard distribution
|-
| [http://www.asus.com ASUSTeK]
| Eee PC
|
| In initial testing phase
|
|}

Supported systems

2008-05-25T10:34:36Z

Jcarroll: /* GLUCOSE */

==A matrix of Sugar "solutions"==

===STARCH===
{|border=1
|+ '''A complete disk image for Sugar'''
|-
!Name
!Sugar Version
!Tested
!Notes
|-
|[http://wiki.laptop.org/go/LiveBackup_XO-LiveCD LiveBackup XO-LiveCD]
|0.75.13-1
|Yes
|This is a Live CD of the OLPC system
|}

===SUCROSE===
{|border=1
|+ '''The interface, plus a set of demonstration activities'''
|-
!Sugar Version
!Tested
!Notes
|}

===GLUCOSE===
{|border=1
|+ '''The base Sugar environment'''
|-
!Operating System !! Version !! Sugar Version !!Tested !! Notes
|-
|Debian||4.0|| ||Yes||[http://wiki.laptop.org/go/Sugar_on_Debian Sugar on Debian]
|-
|Fedora||7,8,9|| || ||[http://wiki.laptop.org/go/Sugar_on_Fedora Sugar on Fedora]
|-
|Gentoo||"[amd64] as of 2007-12-13"[http://wiki.laptop.org/go/Sugar_on_Gentoo_Linux]|| ||Yes||[http://wiki.laptop.org/go/Sugar_on_Gentoo_Linux Sugar on Gentoo]
|-
|Slackware||12|| || ||[http://wiki.laptop.org/go/Sugar_on_Slackware Sugar on Slackware]
|-
|Ubuntu||8.04 (Hardy)||0.79.0-0ubuntu3||Yes||[http://wiki.laptop.org/go/Sugar_on_Ubuntu_Linux Sugar on Ubuntu]
|-
|Windows||XP|| ||No.||
|}

===SYSTEMS===
{|border=1
|+ '''Complete Sugar Solutions'''
|-
!Manufacturer
!Model
!Operating System
!Tested
!Notes
|-
| [http://www.laptop.org OLPC]
| XO-1
| Fedora-7
| Yes
| Standard distribution
|-
| [http://www.asus.com ASUSTeK]
| Eee PC
|
| In initial testing phase
|
|}

Supported systems

2008-05-25T10:33:24Z

Jcarroll: /* GLUCOSE */

==A matrix of Sugar "solutions"==

===STARCH===
{|border=1
|+ '''A complete disk image for Sugar'''
|-
!Name
!Sugar Version
!Tested
!Notes
|-
|[http://wiki.laptop.org/go/LiveBackup_XO-LiveCD LiveBackup XO-LiveCD]
|0.75.13-1
|Yes
|This is a Live CD of the OLPC system
|}

===SUCROSE===
{|border=1
|+ '''The interface, plus a set of demonstration activities'''
|-
!Sugar Version
!Tested
!Notes
|}

===GLUCOSE===
{|border=1
|+ '''The base Sugar environment'''
|-
!Operating System !! Version !! Sugar Version !!Tested !! Notes
|-
|Debian||4.0|| ||Yes||[http://wiki.laptop.org/go/Sugar_on_Debian Sugar on Debian]
|-
|Fedora||7,8,9|| ||[http://wiki.laptop.org/go/Sugar_on_Fedora Sugar on Fedora]||
|-
|Gentoo||"[amd64] as of 2007-12-13"[http://wiki.laptop.org/go/Sugar_on_Gentoo_Linux]|| ||Yes||[http://wiki.laptop.org/go/Sugar_on_Gentoo_Linux Sugar on Gentoo]
|-
|Slackware||12|| ||[http://wiki.laptop.org/go/Sugar_on_Slackware Sugar on Slackware]||
|-
|Ubuntu||8.04 (Hardy)||0.79.0-0ubuntu3||Yes||[http://wiki.laptop.org/go/Sugar_on_Ubuntu_Linux Sugar on Ubuntu]
|-
|Windows||XP|| ||No.|| ||
|}

===SYSTEMS===
{|border=1
|+ '''Complete Sugar Solutions'''
|-
!Manufacturer
!Model
!Operating System
!Tested
!Notes
|-
| [http://www.laptop.org OLPC]
| XO-1
| Fedora-7
| Yes
| Standard distribution
|-
| [http://www.asus.com ASUSTeK]
| Eee PC
|
| In initial testing phase
|
|}

Taxonomy

2008-05-25T10:21:05Z

Jcarroll: /* The SUGAR stack: block diagram view */

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

''(the taste of sugar)''

Description: "Sweet" is the abstract design of the interface's appearance
and behavior, independent of any code actually implementing this style.
The mockups at http://wiki.laptop.org/go/Designs represent this
component's second major release, or perhaps 2.0-alpha.

==Glucose: The base Sugar environment==

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

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

==Fructose: A set of demonstration activities==

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

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

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

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

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

==Ribose: The base Linux distribution being used by Sugar==

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

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

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

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

Description: We often distribute complete disk images for Sugar, ready to
boot. These images are composed of multiple elements of the above stack.
~ For example, the current Joyride images are composed of Ribose (the
non-graphical work) and Glucose (the shell) but not Fructose (the activity
package). Each image series should be named separately, to minimize
confusion. For cutesy codenames, we could have a development build
("glycogen", a starch used to produce Glucose) and a stable build
("cellulose", an extremely stable starch).

== The SUGAR stack: block diagram view==


+---------------------------------------------------------------+
| SWEET: The abstract design of the interface |
| |
+---------------------------------------------------------------+

+---------------------------------------------------------------+
| STARCH: A complete disk image for Sugar |
| |
| +---------------------------------------------------------+ |
| | SUCROSE: The interface, plus a set | |
| | of demonstration activities | |
| | | |
| | +------------------------------+ +--------------------+ | |
| | | FRUCTOSE: A set of demo | | | | |
| | | activities | | | | |
| | | | | | | |
| | +------------------------------+ | | | |
| | +--------------------------------+ | | |
| | | GLUCOSE: The base Sugar environment | | |
| | | | | |
| | +-----------------------------------------------------+ | |
| +---------------------------------------------------------+ |
| |
| +--------------------------------------------------------+ |
| | OPERATING SYSTEM +-----------------+ | |
| | | RIBOSE | | |
| | | | | |
| | +-----------------+ | |
| +--------------------------------------------------------+ |
+---------------------------------------------------------------+

+---------------------------------------------------------------+
| HARDWARE |
| |
+---------------------------------------------------------------+

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

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

==Deepening the concept==
===Lead acetate: An implementation of Sweet on Windows===

''(often called '''[http://en.wikipedia.org/wiki/Sugar_of_lead sugar of lead]''', lead acetate tastes better than sugar but isn't good for children)''

Description: "Lead acetate" is the proposed implementation
of Sweet on Windows XP. Lead acetate may provide better performance
than Glucose, but it is obsolete and
[http://www.healthychildrenproject.org/pdf/PPLEAD.pdf toxic to young brains].
It causes learning disability, behavioral tendencies
toward violence, and even brain damage.

:I know this is tongue-in-cheek, but how about [http://en.wikipedia.org/wiki/Aspartame_controversy aspartame] - once thought better than sugar, but possibly connected with brain tumors... --[[User:Morgs|Morgs]] 11:44, 17 May 2008 (UTC)

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

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

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

===One-liners===
* ''So you're saying Sugar is now suite? ''Kevin Cole
* ''Caramel: a "feature freeze" on Sucrose''
* ''Diabetic OS: an OS that cannot handle Sugar yet'' Yama Ploskonka
* ''Molasses: a beta, unfinished release of Sugar''
* ''High Fructose Corn Syrup: Apparently similar, but made of patented materials'' Morgan Collett
* ''How sweet it is!'' Jackie Gleason
* ''Insulin: what Microsoft needs to make Sugar go away.'' davewa

Taxonomy

2008-05-25T10:19:42Z

Jcarroll: /* One-liners */

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

''(the taste of sugar)''

Description: "Sweet" is the abstract design of the interface's appearance
and behavior, independent of any code actually implementing this style.
The mockups at http://wiki.laptop.org/go/Designs represent this
component's second major release, or perhaps 2.0-alpha.

==Glucose: The base Sugar environment==

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

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

==Fructose: A set of demonstration activities==

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

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

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

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

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

==Ribose: The base Linux distribution being used by Sugar==

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

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

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

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

Description: We often distribute complete disk images for Sugar, ready to
boot. These images are composed of multiple elements of the above stack.
~ For example, the current Joyride images are composed of Ribose (the
non-graphical work) and Glucose (the shell) but not Fructose (the activity
package). Each image series should be named separately, to minimize
confusion. For cutesy codenames, we could have a development build
("glycogen", a starch used to produce Glucose) and a stable build
("cellulose", an extremely stable starch).

== The SUGAR stack: block diagram view==

+---------------------------------------------------------------+
| SWEET: The abstract design of the interface |
| |
+---------------------------------------------------------------+

+---------------------------------------------------------------+
| STARCH: A complete disk image for Sugar |
| |
| +---------------------------------------------------------+ |
| | SUCROSE: The interface, plus a set | |
| | of demonstration activities | |
| | | |
| | +------------------------------+ +--------------------+ | |
| | | FRUCTOSE: A set of demo | | | | |
| | | activities | | | | |
| | | | | | | |
| | +------------------------------+ | | | |
| | +--------------------------------+ | | |
| | | GLUCOSE: The base Sugar environment | | |
| | | | | |
| | +-----------------------------------------------------+ | |
| +---------------------------------------------------------+ |
| |
| +--------------------------------------------------------+ |
| | OPERATING SYSTEM +-----------------+ | |
| | | RIBOSE | | |
| | | | | |
| | +-----------------+ | |
| +--------------------------------------------------------+ |
+---------------------------------------------------------------+

+---------------------------------------------------------------+
| HARDWARE |
| |
+---------------------------------------------------------------+

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

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

==Deepening the concept==
===Lead acetate: An implementation of Sweet on Windows===

''(often called '''[http://en.wikipedia.org/wiki/Sugar_of_lead sugar of lead]''', lead acetate tastes better than sugar but isn't good for children)''

Description: "Lead acetate" is the proposed implementation
of Sweet on Windows XP. Lead acetate may provide better performance
than Glucose, but it is obsolete and
[http://www.healthychildrenproject.org/pdf/PPLEAD.pdf toxic to young brains].
It causes learning disability, behavioral tendencies
toward violence, and even brain damage.

:I know this is tongue-in-cheek, but how about [http://en.wikipedia.org/wiki/Aspartame_controversy aspartame] - once thought better than sugar, but possibly connected with brain tumors... --[[User:Morgs|Morgs]] 11:44, 17 May 2008 (UTC)

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

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

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

===One-liners===
* ''So you're saying Sugar is now suite? ''Kevin Cole
* ''Caramel: a "feature freeze" on Sucrose''
* ''Diabetic OS: an OS that cannot handle Sugar yet'' Yama Ploskonka
* ''Molasses: a beta, unfinished release of Sugar''
* ''High Fructose Corn Syrup: Apparently similar, but made of patented materials'' Morgan Collett
* ''How sweet it is!'' Jackie Gleason
* ''Insulin: what Microsoft needs to make Sugar go away.'' davewa

Taxonomy

2008-05-25T10:19:17Z

Jcarroll: /* One-liners */

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

''(the taste of sugar)''

Description: "Sweet" is the abstract design of the interface's appearance
and behavior, independent of any code actually implementing this style.
The mockups at http://wiki.laptop.org/go/Designs represent this
component's second major release, or perhaps 2.0-alpha.

==Glucose: The base Sugar environment==

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

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

==Fructose: A set of demonstration activities==

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

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

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

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

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

==Ribose: The base Linux distribution being used by Sugar==

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

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

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

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

Description: We often distribute complete disk images for Sugar, ready to
boot. These images are composed of multiple elements of the above stack.
~ For example, the current Joyride images are composed of Ribose (the
non-graphical work) and Glucose (the shell) but not Fructose (the activity
package). Each image series should be named separately, to minimize
confusion. For cutesy codenames, we could have a development build
("glycogen", a starch used to produce Glucose) and a stable build
("cellulose", an extremely stable starch).

== The SUGAR stack: block diagram view==

+---------------------------------------------------------------+
| SWEET: The abstract design of the interface |
| |
+---------------------------------------------------------------+

+---------------------------------------------------------------+
| STARCH: A complete disk image for Sugar |
| |
| +---------------------------------------------------------+ |
| | SUCROSE: The interface, plus a set | |
| | of demonstration activities | |
| | | |
| | +------------------------------+ +--------------------+ | |
| | | FRUCTOSE: A set of demo | | | | |
| | | activities | | | | |
| | | | | | | |
| | +------------------------------+ | | | |
| | +--------------------------------+ | | |
| | | GLUCOSE: The base Sugar environment | | |
| | | | | |
| | +-----------------------------------------------------+ | |
| +---------------------------------------------------------+ |
| |
| +--------------------------------------------------------+ |
| | OPERATING SYSTEM +-----------------+ | |
| | | RIBOSE | | |
| | | | | |
| | +-----------------+ | |
| +--------------------------------------------------------+ |
+---------------------------------------------------------------+

+---------------------------------------------------------------+
| HARDWARE |
| |
+---------------------------------------------------------------+

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

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

==Deepening the concept==
===Lead acetate: An implementation of Sweet on Windows===

''(often called '''[http://en.wikipedia.org/wiki/Sugar_of_lead sugar of lead]''', lead acetate tastes better than sugar but isn't good for children)''

Description: "Lead acetate" is the proposed implementation
of Sweet on Windows XP. Lead acetate may provide better performance
than Glucose, but it is obsolete and
[http://www.healthychildrenproject.org/pdf/PPLEAD.pdf toxic to young brains].
It causes learning disability, behavioral tendencies
toward violence, and even brain damage.

:I know this is tongue-in-cheek, but how about [http://en.wikipedia.org/wiki/Aspartame_controversy aspartame] - once thought better than sugar, but possibly connected with brain tumors... --[[User:Morgs|Morgs]] 11:44, 17 May 2008 (UTC)

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

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

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

===One-liners===
* ''So you're saying Sugar is now suite? ''
Kevin Cole
* ''Caramel: a "feature freeze" on Sucrose''
* ''Diabetic OS: an OS that cannot handle Sugar yet''
Yama Ploskonka
* ''Molasses: a beta, unfinished release of Sugar''
* ''High Fructose Corn Syrup: Apparently similar, but made of patented materials''
Morgan Collett
* ''How sweet it is!'' Jackie Gleason
* ''Insulin: what Microsoft needs to make Sugar go away.'' davewa

Sugar Labs/FAQ

2008-05-25T10:10:41Z

Jcarroll: Added the obligatory: "What is Sugar" question; revised "post your questions here"

:''This page contains many frequently-asked questions along with some answers. To ask a new question, please '''post your question(s) [[Talk:FAQ|here]]'''. We encourage you to answer questions and keep these pages organized.''

==About Sugar==

=== What is Sugar? ===
Sugar is an educational software platform built with the python programming language and based on the principles of cognitive and social constructivism.

=== What makes Sugar different from other educational software platforms? ===

The Sugar interface, in its departure from the desktop metaphor for computing, is the first serious attempt to create a user interface that is based on both cognitive and social constructivism: learners should engage in authentic exploration and collaboration. It is based on three very simple principles about what makes us human: (1) everyone is a teacher and a learner; (2) humans by their nature are social beings; and (3) humans by their nature are expressive. These are the pillars of a user experience for learning.

Sugar also considers two aphorisms: (1) you learn through doing, so if you want more learning you want more doing; and (2) love is a better master than duty—you want people to engage in things that are authentic to them, things that they love.

The presence of other people is always present in the Sugar interface: collaboration is a first-order experience. Students and teachers engage in a dialog with each other, support each other, critique each other, and share ideas.

Sugar is also discoverable: it can accommodate a wide variety of users, with different levels of skill in terms of reading, language, and different levels of experience with computing. It is easy to approach and yet it doesn't put an upper bound on personal expression; one can peel away layers and go deeper and deeper, with no restrictions.

Sugar is based on Python, an interpreted language, allowing the direct appropriation of ideas: in whatever realm the learner is exploring—music, browsing, reading, writing, programming, graphics, etc.—they are able to drill deeper; they are not going to hit a wall, since they can, at every level, engage in debugging both their personal expression and the very tools that they use for that expression.

==Using Sugar==

=== Is there an image of the OS that can be run on a PC? ===

* You can download a LiveCD version of Sugar (Please see http://wiki.laptop.org/go/LiveCd).

* Also, if you are using Ubuntu Hardy, it is one of the included packages (Please see http://wiki.laptop.org/go/Sugar_on_Ubuntu_Linux#Option_3_-_Hardy_included_packages).

=== Sugar on an ASUS Eee PC ===

Q: I have an ASUS Eee p.c. and i was wondering if sugar has been ported to it yet.
if so has an image of a boot-able USB key been produced?
and if so what is the URL of the image that i can drag and drop to a blank drive and reboot sugar from?
and if not.... how much longer?

A: There is a thread on the mailing list about success stories: http://lists.lo-res.org/pipermail/its.an.education.project/2008-May/000282.html Another pointer is: ftp://rohrmoser-engineering.de/pub/XO-LiveCD/XO-LiveCD_080321.pdf

==About Sugar Labs==

=== What is Sugar Labs? ===

Sugar Labs, a (soon to be established) non-profit foundation, serves as a support base and gathering place for the community of educators and software developers who want to extend the Sugar platform and who have been creating Sugar-compatible applications.

=== What is the mission of Sugar Labs? ===

The overarching mission of Sugar Labs is to support the Sugar platform through software development, and community outreach and support. The purpose of the Sugar platform is provide a software and content environment that enhances learning. Towards this end, Sugar is designed to facilitate learners to “explore, express, debug, and critique.”

=== What are the principles that guide Sugar Labs? ===

Sugar Labs subscribes to principle that learning thrives within a culture of freedom of expression, hence it has a natural affinity with the free and open-source software movement (Please see [[Sugar_Labs#Principles|Principles]] page in this wiki for more details). The core Sugar platform has been developed under a GNU General Public License (GPL); individual activities may be under different licenses.

=== What is the relationship of Sugar Labs to One Laptop per Child? ===

Sugar was originally developed as the user interface (UI) for the One Laptop per Child (OLPC) XO-1 laptop. Sugar Labs was established as an independent entity in order to facilitate the growth of Sugar beyond any single hardware platform. While Sugar Labs has a cooperative working relationship with OLPC, it is by no means an exclusive or proprietary relationship. Sugar Labs is not bound to any specific hardware platform or Linux distribution (Please see [[Supported systems]]).

=== Who is Sugar Labs? ===

Sugar is a community project, so it is the sum of those of you who participate. Sugar Labs was started by some Sugar-community members: [[User:Walter|Walter Bender]], [[User:ChristophD|Christoph Derndorfer]], [[User:Bert|Bert Freudenberg]], [[User:Marcopg|Marco Pesenti Gritti]], [[User:Bernie|Bernardo Innocenti]], Aaron Kaplan, [[User:Erikos|Simon Schampijer]], and [[User:Tomeu|Tomeu Vizoso]]. We are in the process of designing an initial set of rules of governance that will be refined and ratified in a process of public discussion.

=== How do I get involved? ===

Please see the [[GetInvolved|Getting Involved]] page in this wiki.

=== How do I learn more about Sugar Labs? ===

Please add new questions to the [[Talk:FAQ|discussion]] page or send email to press at sugarlabs.org.

[[Category:General public]]

User:Jcarroll

2008-05-25T08:09:14Z

Jcarroll: New page: I've been watching OLPC for over two years now. I recently subscribed to the OLPC News RSS feed. Current Projects: * Maintaing this wiki (See TODO) * Testing Sucrose

I've been watching OLPC for over two years now. I recently subscribed to the OLPC News RSS feed.

Current Projects:
* Maintaing this wiki (See [[TODO]])
* Testing [[Sucrose]]

Talk:Sugar Labs/About

2008-05-19T13:53:02Z

Jcarroll: New page: Why is there a big logo of "develer" in the corner? Is Sugar Labs sponsored by them? Are we offering advertising on this website? --~~~~

Why is there a big logo of "develer" in the corner? Is Sugar Labs sponsored by them? Are we offering advertising on this website? --[[User:Jcarroll|Jcarroll]] 13:53, 19 May 2008 (UTC)

0.82/Roadmap

2008-05-15T17:16:06Z

Jcarroll: /* Schedule */

== Schedule ==

{| cellpadding="10" cellspacing="0" border="1"
!Date
!Task
!Notes
|-
|May 8 2008
|Development start
|New features proposal
|-
|May 21
|Sugar 0.81.1 Tarballs Due
|
|-
|May 22
|Sugar 0.81.1 Development Release
|
|-
|June 5
|Sugar 0.81.2 Tarballs Due
|
|-
|June 6
|Sugar 0.81.2 Development Release
|
|-
|June 19
|Sugar 0.81.3 Tarballs Due
|
|-
|June 20
|Sugar 0.82 Beta 1 (0.81.3)
|Feature, ABI, String freeze
|-
|July 7
|Sugar 0.81.4 Tarballs Due
|
|-
|July 8
|Sugar 0.82 Beta 2 (0.81.4)
|
|-
|July 21
|Sugar 0.81.5 Tarballs Due
|
|-
|July 22
|Sugar 0.82 Release Candidate 1 (0.81.5)
|
|-
|July 31
|Sugar 0.81.6 Tarballs Due
|
|-
|August 1
|Sugar 0.82 Release Candidate 2 (0.81.6)
|Hard Code Freeze
|-
|August 7
|Sugar 0.82 Tarballs Due
|
|-
|August 8
|Sugar 0.82 Final Release
|
|}

== Moduleset ==

* [[Modules#sugar|sugar]]
* [[Modules#sugar-base|sugar-base]]
* [[Modules#sugar-datastore|sugar-datastore]]
* [[Modules#sugar-presence-service|sugar-presence-service]]
* [[Modules#sugar-toolkit|sugar-toolkit]]
* [[Modules#sugar-artwork|sugar-artwork]]
* [[Modules#journal-activity|journal-activity]]

== Proposed Modules ==
* [[Modules#chat-activity|chat-activity]]
* [[Modules#web-activity|web-activity]]
* [[Modules#read-activity|read-activity]]
* [[Modules#log-activity|log-activity]]
* [[Modules#write-activity|write-activity]]
* [[Modules#calculate-activity|calculate-activity]]
* [[Modules#terminal-activity|terminal-activity]]
* [[Modules#tamtam-activity|tamtam-activity]]

== Dependencies ==

* hippo-canvas
* telepathy-glib
* telepathy-gabble
* telepathy-salut
* telepathy-python

== Tickets ==

* [http://dev.laptop.org/query?status=assigned&status=new&status=reopened&component=sugar&component=datastore&component=presence-service&component=datastore&component=journal-activity&order=priority&milestone=Update.2&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=keywords Sugar core tickets] on laptop.org

== New features ==

[[Category:Developer]]

Talk:Sugar Labs/Announcing Sugar Labs

2008-05-15T17:15:26Z

Jcarroll: New page: Please add section headers.

Please add section headers.