[Sugar-devel] GPA reports and target features
gregsmithpm at gmail.com
Wed Jul 22 15:34:02 EDT 2009
Wow! That sounds great. From the summer camp web page it looks like
you guys are having a lot of fun. Synch up with Caroline about
logistics at the school and related issues.
I'm sure we can find some menial tasks :-)
One thing that comes to mind is that you could help by getting in to
the bug database: http://dev.sugarlabs.org/
Then go over the class notes and make sure that everything which looks
like a bug or feature request has a bug associated with it. Either an
existing bug or create a new one as needed. Make sure to put GPA in
the keyword field. Then we can run a query and easily see where we
If something in the notes is not clear, don't hesitate to send an
e-mail asking for more info. You can also try to reproduce stuff if
you have time and access to the SW.
Also, add a note to the wiki page once you have reviewed a set of
notes so we don't redo any work.
Not sure if that is too hard but its on my to do list and your help
would be great.
In terms of interviews, we're not actually doing that. Its completely
different than the "fly people out to HQ, video tape them playing
w/the SW from behind smoked glass, then interview them for a few
hours" type usability study I have done in the past.
This is just watching over kids shoulders and noting what they try to
do. We have no time with the teachers or kids to really talk. I tried
asking the kids what they think but its was way to general and they
didn't know what to say.
One thing that happens while I watch is that the kids start asking me
what to do and poking me for attention and in general I get sucked in
to saying: "click here, then click there etc.". Its very hard to take
over mouse and just do it for them!
Any suggestions on questions or structure for analyzing the results of
this experience are appreciated. Just try to make it a set of
observations rather than an interview type exchange.
HTHs. Look forward to meeting you and the whole team.
FYI, Walter and Caroline own the engagement, I'm just the voluble
scribe/project pest, so be sure to align with them.
On Wed, Jul 22, 2009 at 11:19 AM, Frederick Grose<fgrose at sugarlabs.org> wrote:
> Hi Greg,
> The Rochester, NY Sugar Summer Program Co-ops will be in Boston,
> Massachusetts 10-16 August 2009 with a commitment to help with any needed
> tasks in the final week at Gardner.
> Our Massachusetts field trip is described here,
> I've asked our group of 6 to brief themselves with the project page and the
> class notes discussions in preparation for the field trip. We would be
> happy to pickup any menial tasks that you team identifies. As we will be
> there during the final week for the GPA summer school, we might also be able
> to act as interviewers and reduce familiarity bias with the local subjects,
> if exiting interviews were in your plans.
> Looking forward to meeting you and the team, --Fred
> On Tue, Jul 21, 2009 at 9:39 AM, Greg Smith <gregsmithpm at gmail.com> wrote:
>> Hi All,
>> I came up with a strategy to focus development on a successful Sugar
>> implementation in a single school.
>> On the reports:
>> I updated the Sugarlabs GPA wiki page with some more links to the
>> reports: http://wiki.sugarlabs.org/go/Gardner_Pilot_Academy#Class_notes
>> In the future I will try to write a short focused summary for the list
>> and post the full notes on the wiki.
>> On Development, Bugs, and Features:
>> I want to make a list of features and fixes focused on GPA. Once we
>> have a prioritized list we can sort them in to target releases. So
>> they wont be "target 0.86 for a while.
>> I will add GPA to the Keywords in Trac and list main features here:
>> I want to build the SW work list from the ground up. That is, define
>> the curriculum, the lesson plans and the interaction in class first.
>> Then list the barriers and enhancements based on that.
>> All other roadmap work is great, as long as there are no regressions
>> :-) I'm all for it but I'll focus on GPA impacting items for now. If
>> you are coding something you think will be used in GPA, let me know.
>> One exception is Gary's Toolbar idea. I'll study it and synch with
>> Caroline about options for testing it in class.
>> I added a link to the curriculum at GPA on the wiki:
>> http://wiki.sugarlabs.org/go/Gardner_Pilot_Academy#Curriculum \
>> And a list of "lesson plans" (work flow examples). I put in two from
>> classes I was in. Please add more if you have them. I will also ask
>> the Sur list and research lesson plans from XO deployments.
>> That's my strategy and work plan for the near term.
>> Any comments, additions or suggestions are welcome.
>> Next up is reading the bug db and asking for status of main Goals
>> (http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Goals). That plus
>> studying the curriculum and creating/finding more lesson plans.
>> If that looks like a good plan, is anyone up for working it with me?
>> I see four main roles:
>> 1 - Bug scrub, update and tracking. Help tag all GPA related bugs,
>> make sure developers understand them, get any added details needed,
>> get them assigned, and check for status.
>> 2 - Curriculum creators. Get up to speed on curriculum and goals of
>> the projects. Come up with and document new lesson plans.
>> 3 - Technical testing and support. People to reproduce bugs, get
>> latest software, try out and verify possible solutions and maintain a
>> test bed of what the class is doing. Could be the same person as 1.
>> 4 - Developers ready to resolve issues. Hopefully a few generalists
>> who can help fix any problem, be it activity or sugar core related.
>> Hopefully several people beyond the existing primary developers.
>> Unicast or reply on list if you want to chip on any of that. No hard
>> commitment needed, I'll take what I can get.
>> My time may become constrained again but my goal is a solid list of
>> classes with working code to support them, in place before the end of
>> Greg S
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
More information about the Sugar-devel