From Sugar Labs
Jump to: navigation, search

1. Project Title & Shipment Detail

Name of Project: Sugar and Sugar Activity debugging Shipping Address You've Verified:

Number of Laptops (or other hardware) You Request to Borrow: 1 Loan Length—How Many Months: 3

2. Team Participants

Name(s) & Contact Info: (include all email addresses & phone numbers)

Teams of more than 1 person are not required, but favored!

Walter Bender

Employer and/or School: MIT Past Experience/Qualifications:

I have been contributing to the project since 2005; I've submitted numerous patches to Sugar and Sugar activities. I am the author/maintainer of more than one dozen Sugar activities.

3. Objectives

Project Objectives:

Concrete proposals with defined, measurable outcomes are much more likely to result in a laptop than "it would be cool to play with these and demo them".

My primary objective is to identify any issues with Sugar and Sugar activities and to try to resolve these issues. I am also working on some aggressive changes to Sugar (no-Hippo) that I would like to test in the new environment.

Specifically, since many of my activities (Measure, Turtle Blocks, et al.) exercise devices such as the camera, the microphone input (including sensor mode) USB ports, and other built-in sensors that will be available on the new hardware, this will be a testing area of more focus on my part.

4. Plan of Action

Plan and Procedure for Achieving the Stated Objectives:

Step 1: Get the latest Sugar bits onto the machine
Step 2: Do comprehensive testing of Fructose activities
Step 2a: Document test results
Step 2b: Come up with a plan of attacking any bugs encountered
Step 3: Investigate access to new devices (e.g., accelerometer)
Step 4: Integrate new devices into Measure and Turtle Blocks
Step 5: Test no-Hippo and other bleeding edge Sugar patches

5. Needs

Why is this project needed?

Fructose represents the core set of activities used in the classroom; these activities need to be tested; the 1.75 is more sensor-rich than its predecessors: we need software to leverage and show off the new capabilities.

Locally? In the greater OLPC/Sugar community?

Working with sensors has become a critical part of how the XO is being used in deployments. Further enrichment of this activity within the context of the new h'ware is a great way to encourage its rapid adoption.

Outside the community? Why can't this project be done in emulation using non-XO machines?


Why are you requesting the number of machines you are asking for?

Will you consider (1) salvaged/rebuilt or (2) damaged XO Laptops?

For testing sensors, I just need 1 laptop. I can test collaboration in conjunction with the XO 1.0 hardware I already have.

Rebuilt/damaged laptops are OK as long as it doesn't impact my ability to test Sugar activities.

6. Sharing Deliverables

Project URL—where you'll Blog specific ongoing progress:

Please web-publish this entire completed proposal, removing any sections affecting your personal privacy. Ask if you want help -- communicating with our OLPC/Sugar global community is core!

How will you convey tentative ideas & results back to the OLPC/Sugar community, prior to completion?

email to the devel lists on both and

How will the final fruits of your labor be distributed to children or community members worldwide?

commits to

Will your work have any possible application or use outside our community?


If yes, how will these people be reached?

Have you investigated working with nearby XO Lending Libraries or Project Groups?

N/A to this particular request

7. Quality/Mentoring

Would your Project benefit from Support, Documentation and/or Testing people?

I plan to work with the NZ and OZ testing teams.

Teachers' input into Usability?

I plan to work with Guzman Trindad, a teacher in .UY

How will you promote your work? Can we help you with an experienced mentor from the OLPC/Sugar community?

If YES: specify the kind of Ongoing Mentoring that will benefit you most.

Help with access to the new devices would be a big plus. As always I benefit from someone reviewing my patches.

If NO: specify who will help you share your progress, creations & results.

8. Timeline (Start to Finish)

Please include a Proposed timeline for your Project life-cycle: (this can be in the form of Month 1, Month 2, etc rather than specific dates)

Include a couple milestones, even if tentative.

Month 1: Testing/identification of any major issues
Month 2: Debugging sensor input
Month 3: Testing/Documentation

Specify how you prefer to communicate your ongoing progress and obstacles!

email, bug tracker (although my account on dev.l.o remains broken), irc

[x] I agree to pass on the laptop(s) to a local OLPC group or other interested contributors in case I do not have need for the laptop(s) anymore or in case my project progress stalls.