Changes

1. "The vision thing": There has been some discussion about the Sugar vision in regard to both its clarity and the degree to which it is being promoted (Please see [http://lists.sugarlabs.org/archive/iaep/2008-August/001425.html the email thread]). While there is some divergence of opinion about the breadth of the Sugar Labs mission—ranging from a strict focus on collaboration tools to a broad focus on everything necessary for successful one-laptop-per-child deployments—there was consensus that we are getting the message out that Sugar is alive and kicking; there is still a wide-spread impression that the FOSS community has abandoned Sugar because OLPC is working with Microsoft on Windows XP. We need to let the world know that: (a) there is a vibrant Sugar community; (b) that OLPC is still behind Sugar; (c) other hardware vendors are beginning to adopt Sugar; and (d) the FOSS Sugar learning platform offers encourages the direct appropriation of ideas in whatever realm the learner is exploring: music, browsing, reading, writing, programming, graphics, etc.—they are able to engage in debugging both their personal expression and the very tools that they use for that expression.

1. "The vision thing": There has been some discussion about the Sugar vision in regard to both its clarity and the degree to which it is being promoted (Please see [http://lists.sugarlabs.org/archive/iaep/2008-August/001425.html the email thread]). While there is some divergence of opinion about the breadth of the Sugar Labs mission—ranging from a strict focus on collaboration tools to a broad focus on everything necessary for successful one-laptop-per-child deployments—there was consensus that we are getting the message out that Sugar is alive and kicking; there is still a wide-spread impression that the FOSS community has abandoned Sugar because OLPC is working with Microsoft on Windows XP. We need to let the world know that: (a) there is a vibrant Sugar community; (b) that OLPC is still behind Sugar; (c) other hardware vendors are beginning to adopt Sugar; and (d) the FOSS Sugar learning platform offers encourages the direct appropriation of ideas in whatever realm the learner is exploring: music, browsing, reading, writing, programming, graphics, etc.—they are able to engage in debugging both their personal expression and the very tools that they use for that expression.

2. Try Sugar: An important aspect of Sugar outreach is easy access to Sugar itself. We are targeting grassroots adoption (in addition to top-down "sales" coupled to programs like One Laptop per Child or Intel regional or national initialives), so we need to make it easier for small groups to try Sugar. This includes community support of the existing LiveUSB, LiveCD, and Appliance efforts, but also further consideration (and documentation) of the various hardware one might find in the field and more detailed instructions on setting up classrooms (groups) of machines working together. Towards that end, we are beginning work on a "Try Sugar" section in the wiki (Please help us flesh out [[Documentation/Try_Sugar]]), which includes a matrix of "tried and ready" solutions from the field. To be able to say to a teacher, here is a step-by-step guide to how you can repurpose (or overlay) the computers you have access to in the classroom to run Sugar will go a long way towards fostering growth of Sugar.

2. Try Sugar: An important aspect of Sugar outreach is easy access to Sugar itself. We are targeting grassroots adoption (in addition to top-down "sales" coupled to programs like One Laptop per Child or Intel regional or national initialives), so we need to make it easier for small groups to try Sugar. This includes community support of the existing LiveUSB, LiveCD, and Appliance efforts, but also further consideration (and documentation) of the various hardware one might find in the field and more detailed instructions on setting up classrooms (groups) of machines working together. Towards that end, we are beginning work on a "Try Sugar" section in the wiki (Please help us flesh out [[DocumentationTeam/Try_Sugar]]), which includes a matrix of "tried and ready" solutions from the field. To be able to say to a teacher, here is a step-by-step guide to how you can repurpose (or overlay) the computers you have access to in the classroom to run Sugar will go a long way towards fostering growth of Sugar.

3. "Unexpected" suggestions: Michael Stone wrote up some suggestions regarding "the Work of Sugar", his reactions to sugar's architecture, design, and implementation. It was the basis of an in-depth discussion the Sugar mailing list (Please see [http://lists.laptop.org/pipermail/sugar/2008-July/007304.html]).

3. "Unexpected" suggestions: Michael Stone wrote up some suggestions regarding "the Work of Sugar", his reactions to sugar's architecture, design, and implementation. It was the basis of an in-depth discussion the Sugar mailing list (Please see [http://lists.laptop.org/pipermail/sugar/2008-July/007304.html]).