10,513
edits
Changes
Jump to navigation
Jump to search
Line 7:
Line 7: − + − So, don't throw away those old flash drives: donate them!+ − 2. It was great to hear from Bill Kerr, who has some of his students trialling Sugar on a Stick. Check out [http://xo-whs2009.blogspot.com/ Bill's blog] (which also appears in our Planet) and read up on his students impressions of Sugar, which are linked from the sidebar.+ − 3. I forget how exhausting teaching can be, even part time. I've been teaching five Sugar classes per week this summer: two for second graders, one for third graders, and one for middle-school youth. The [[Gardner_Pilot_Academy#Class_notes|reports from the Gardner School]] describe much of what I have been doing. The demands of the children being what they are, I keep biting off more and more as the summer has progressed. (One of the dangers of putting developers and teachers in the same room.) Lately, I have been exploring how the children might use Turtle Art to create some geography games similar to [http://activities.sugarlabs.org/en-US/sugar/addon/4199 Conozco Uruguay]. Without too much effort, I managed to create a simple framework that I used to sketch out a few games (See [http://www.dailymotion.com/user/sugarlabs/video/x9yrxj_continent-game_tech Continent Game] and [http://www.dailymotion.com/user/sugarlabs/video/x9xz9o_stategame_tech State Game].) This morning, I made [http://www.dailymotion.com/user/sugarlabs/video/x9zy4v_where-is-the-gardner-schooly_tech a game specific to the Gardner School], leveraging the work they had been doing with maps and pictures of their neighborhood. We played all the games as a group--the kids were animated and engaged. Then I shared the Gardner Game with their Sugar neighborhood and asked them to launch it. + − Here is where the trouble began. First of all, the version of Turtle Art I used to build the game is newer than the version they had installed on their machines. Normally, this wouldn't be an issue, but I had used a block that they didn't have, so the sharing halted part way through. The good news is that Sebastian Dziallias pushed a change for Sugar on a Stick to contain all activities packaged as XO files, meaning that all activities can update. (Presently, it is non-trivial to update activities that had been distributed as RPM.) The bad news is, Turtle Art, being part of Fructose, had been distributed as RPM on the Gardner School sticks. So I will have to update them by hand.+ + − But had sharing worked, I still would have run into some problems, since once, shared, always shared. I discussed the problem with Ben Schwartz in IRC:+ − :'''<walterbender>''' bemasc: here is my use scenario: the current sharing mechanism with its automatic resume doesn't work...+ − :'''<walterbender>''' I designed a game template for the kids to use in Turtle Art. − − :'''<walterbender>''' So far so good. − :'''<walterbender>''' (of course, I had a version mismatch that caused the sharing to fail part way through, which I have subsequently fixed.) − :'''<walterbender>''' but the problem is, once shared, always shared. − :'''<walterbender>''' I want the kids to each modify the template their own way, not as a group. − :'''<walterbender>''' and then share their individual results with the group at check points. So the feature is that sharing is punctuated. But also involves explicit forking. the merge is perhaps the least important. − :'''<walterbender>''' but the current model is always merging all the time... − :'''<walterbender>''' (I suppose I could make TA share in only one direction, using the current model). − :'''<walterbender>''' but then how would a kid share her cool innovation? − :'''<bemasc>''' walterbender: hmm. Why not use object transfer? − :'''<bemasc>''' walterbender: as I've suggested with my mockups, we could have a system in which every time a user launches a previously shared activity, they have the option to work privately. − :'''<bemasc>''' I haven't implemented this, mostly because I'm not much a GUI programmer, but it's a possibility. − :'''<walterbender>''' bemasc: Does object transfer work for objects other than text? − :'''<bemasc>''' walterbender: I mean the Journal-based object transfer. You can send any journal item to anyone in 0.84. − :'''<bemasc>''' The problem in 0.84 is that this is "push only", so you have to click N times to send it to N people. − :'''<walterbender>''' bemasc: I hadn't tried it lately, but I wasn't able to get to work for TA objects. − :'''<bemasc>''' Also, I think you have to make them all "friends" first. − :'''<bemasc>''' walterbender: well, that's certainly mysterious. − :'''<walterbender>''' bemasc: I'll try again. − :'''<walterbender>''' bemasc: but I still like the idea of doing this through the collaboration model so that they results and be shared/merged more directly... − :'''<bemasc>''' walterbender: If everyone is working independently on separate projects that will not be merged, then I have difficulty seeing in what sense they are working collaboratively, even if they all forked from a common template. − :'''<bemasc>''' I think, as a rule, we should only show people "collaborating" in a single session in the Neighborhood if they are actually working together on a single "document". − :'''<walterbender>''' bemasc: they plan to work in small teams − :'''<walterbender>''' for example, each adding a question to a quiz show − :'''<bemasc>''' walterbender: ok. So each team can get a session. That much makes sense; the question is how to seed the sessions. − :'''<bemasc>''' If we had a copy function in the Journal, I would say "make a template, copy it once for each team, and share each copy" − :'''<walterbender>''' bemasc: I think that makes the most sense in the short term. Thanks. − :'''<walterbender>''' but I look forward to trying your framework. − :'''<bemacs>''' walterbender: if you get object transfers working, you could transfer to a "team initiator" for each team, who would then share, and the others would join. − :'''<bemacs>''' This should be workable in 0.84, with a smallish number of clicks, except for bugs. − I'll report back how things work out tomorrow with the third graders.+ + + + + + + + + + + + + + + − 4. We are a still [[Sugar_Labs/Governance/Oversight_Board/2009-2010-candidates|soliciting candidates]] for the Sugar Oversight Board. Luke Faraone has been looking into whether or not [http://www.spi-inc.org SPI] might be able to run the election for us, which would guarantee some level of distance and transparency to the process. Meanwhile, we also have to get our membership list in order. I've asked the Membership Team to get moving, but we need your help as well. Please add yourself to the [[Sugar_Labs/Initial_Members_List|Membership List]] if you are not already listed. (We have a seemingly intimidating [[Sugar_Labs/Sugar_contributors|membership criteria]], but remember that there are many ways to contribute and that asking even a single question represents a contribution.+ − 5. Gonzalo Odiard reports that there will be a Sugar Day in Argentina on 8 August 2009 beginning at 13:30 on the first floor of the Radio FM La Tribu Lambaré 873 Buenos Aires, Almagro. + + + + + + + − 6. Gary Martin has generated a SOM from the past week of discussion on the IAEP mailing list (Please see [[:File:2009-July-18-24-som.jpg|SOM]]). +
→What's new
===Sugar Digest===
===Sugar Digest===
1. Greg Morris from Nexcopy, the company that donated one of their USB Duplicators to Sugar Labs, has been busy with another generous effort. Check out [http://recycleusb.com http://recycleusb.com], a website "dedicated to turning used flash drives into portable learning devices for children, schools and education institutions." They are featuring "Sugar On A Stick" and offer to load Sugar onto recycled USB flash drives and sending them to Sugar Labs for global deployment.
1. As Caroline Meeks and I are wrapping up the Sugar-on-a-Stick summer programs, it has been a time to reflect upon what we have learned and what challenges face us in September (Many thnaks to Greg, Anurag, Jennifer, et al. for their help). The goal of our pilots was to identify any issues we might face with a school-wide rollout of Sugar on a Stick and to work through many unknowns regarding the logisitics of deployment.
We learned a great deal, e.g., replication of custom keys: be sure to remove any owner keys in the .sugar/default directory before copying. And we experimented with a number of different workflows regarding how to prepare for a class: use USB extension cables if possible; preload helper boot CDs; have the children turn on their computers and then gather for a discussion of the lesson plan while the machines are booting; have a cache of hot spares since some keys inevitably will not boot (more on this in a moment); have the children shutdown the computers and then gather for a wrap-up discussion while the machines power off; etc. And we uncovered some bugs in our sharing logic (See my post from last week); and experienced some issues regarding robustness of the USB images.
It is this latter topic that was the subject of much debate on the Sugar mailing lists this week and which I would like to touch upon today.
While we did experience some "failures", given the circumstances, we were not able to do a very systemic analysis of the situation. We know that some sticks fail to boot and some have corrupted user data. We don't have an actionable characterization of the circumstances under which these problems occur.
James Cameron summed up the situation:
:If any state is preserved by the children on the USB sticks, and there is no copy of the state kept elsewhere, and there is a possibility of power failure, premature removal, or other interruptions, then every software component that uses the saved state must be either capable of detecting corruption of the saved state, or graceful recovery from apparently invalid state.
Meeting this challenge is not trivial; the more clarity we can bring to the use cases, the more likely we will be able to engineer solutons.
In the meanwhile, we need to: experiment with more USB manufacturers; be more careful about characterizing the different failure modes; do some workflow experiments to see if we can minimize failures; try different file formats; and come up with simple and robust backup/restore mechanism so that we can end run failures.
:'''<walterbender>''' I then shared my construction with them.
Greg Dekoenigsberg has suggested we take advantage of [https://fedoraproject.org/wiki/QA/Fedora_12_test_days Fedora Test Days] to put a more rigorous analysis together. But we need a testing plan which means we need to first come to consensus on what it is we are trying to test.
Variables include:
Which Sugar-on-a-Stick image is being tested?
What customizations have been made?
What process was used to create the key?
What size and brand of key is being tested?
What hardware the key is being tested on?
What is the nature of the failure? (no boot, corrupted data, etc.?)
What was the history of use prior to failure?
Let's get a plan together and take avantage of this generous offer from the Fedora community.
2. Jeff Elkner reports that Jamie Boisture completed his summer project: using GASP with 15 middle-school summer-enrichment students, and it worked wonderfully! Jamie also submitted a merge request with Pippy to have GASP included in Pippy. (Jamie was sponsored by Jeff in a program modeled after Google Summer of Code. We should try to do more such programs.
===Help wanted===
===Help wanted===
3. It is not too late to sign up as a [[Sugar_Labs/Governance/Oversight_Board/2009-2010-candidates|candidate]] for the Sugar Oversight Board. Also, please add yourself to the [[Sugar_Labs/Initial_Members_List|Membership List]] if you are not already listed.
===In the community===
===In the community===
4. Werner Westermann reported that "Patricio Acevedo left the audience shocked after [http://prezi.com/139914/ presenting Sugar] in the 2nd Innovation Workshop: The Creative Teacher, held in the Metropolitan Educational University, in Santiago, Chile." It was the first official activiuty of the newly formed Sugar Labs Chile.
5. [http://squeakland.org/squeakfest/usa/schedule/ Squeakfest USA] is next week in Los Angeles.
===tech talk===
6. Sebastian Dziallas announced the availability of a new [http://download.sugarlabs.org/soas/snapshots/3/SoaS3-200908021950.iso SoaS snapshot] that includes the latest Sugar Release 0.85.3. It is a developer release--any testing would be greatly appreciated.
===Sugar Labs===
===Sugar Labs===
7. Gary Martin has generated a SOM from the past week of discussion on the IAEP mailing list (Please see [[:File:2009-July-25-31-som.jpg|SOM]]).
=== Community News archive ===
=== Community News archive ===