User:Mchua/Braindumps/getting feedback for builds

From OLPC
< User:Mchua‎ | Braindumps
Revision as of 14:11, 16 October 2008 by 18.85.49.184 (talk) (New page: == what == An open community feedback session (or sessions) for gathering feedback from all the deployments using XOs, particularly end-user/community/non-technical feedback. This feedbac...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

what

An open community feedback session (or sessions) for gathering feedback from all the deployments using XOs, particularly end-user/community/non-technical feedback. This feedback will be translated afterwards into items that developers can implement. It is intended to be before the 9.1.0 design discussion in Boston in mid-November.

why

Greg Smith is making heroic efforts to keep everyone in the feedback loop in terms of what deployments need and what developers should implement for the XO build.

We need to help.

goal

the artifact we should create together is not a product (9.1.0) but the process we're going to use to get there, in terms of:

  • how feedback loops work
  • how people find out about these feedback loops and how to use them

what groups should have at the end

  • Each group/should have a public statement of what it needs, and why, and how they're going to make it happen.
  • Each group should have a public statement of what help it can offer - over and above what it immediately needs.
  • Each group should have a publicly posted way to modify the above. As little bottlenecking as possible.


The goal is for groups to leave with the feeling that they have been heard (because they have been heard), and that they understand what is happening with the things that they asked for, and why.

Even more important is for groups to know that they are empowered to fix their own problems, which problems are solvable with them without 1cc's intervention, and that they can see a clear path to making it happen with the resources available.

More concretely

So that's a lot of highfalutin' talk so far, very abstract. More concrete questions:

  • It's a month after 9.1.0 launch date. What do you want to have happening in your programs?
  • How are you going to know that this is happening? (Criteria of declaring this "success"?)
  • Ok. What features, exactly, in the system do you need to have that happen? Technically?
  • What is the first step that you need to take to implement this? (How far out this line of planning can you go - how far do you need to go to know if it is possible?)

Who do we want in on this conversation? (How do we filter?)

Virtual or in person? How do we get past cultural, linguistic differences?