Community testing meetings/2008-12-04: Difference between revisions
mNo edit summary |
|||
Line 7: | Line 7: | ||
See [[Community testing meetings/2008-11-20]]. Note that we're trying an experiment and ''not'' reviewing action items this meeting round. Read [http://lists.laptop.org/pipermail/testing/2008-December/000616.html the meeting announcement email] for an explanation why. |
See [[Community testing meetings/2008-11-20]]. Note that we're trying an experiment and ''not'' reviewing action items this meeting round. Read [http://lists.laptop.org/pipermail/testing/2008-December/000616.html the meeting announcement email] for an explanation why. |
||
== Law of two feet == |
|||
Everyone should read [http://www.deborahschultz.com/deblog/2006/07/the_law_of_two_.html The Law Of Two Feet]. |
|||
== Discussion: Developer/tester relationships == |
== Discussion: Developer/tester relationships == |
Revision as of 07:15, 4 December 2008
This is a Community testing meeting. Location is in #olpc-meeting on Start date::December 04, 2008 22:00 (time is in UTC, click here to find the meeting time for your time zone.)
Previous meeting's action items
See Community testing meetings/2008-11-20. Note that we're trying an experiment and not reviewing action items this meeting round. Read the meeting announcement email for an explanation why.
Law of two feet
Everyone should read The Law Of Two Feet.
Discussion: Developer/tester relationships
Open discussion time - bring your questions! What do you want to learn about developer/tester relationships or how to make them better? What are you thinking?
Brainstorm: What are the blockers on Activity testing?
See the Rules of brainstorming before we start.
Focus question: Assuming that we want the G1G1 Activities to look like this before December 25, 2008, what are the things that are (or might) prevent us from getting there?
What we'll be doing:
- Sanity-check the focus question
- Generate as many possible solutions to that question as we can
- Agree on a way to identify the most pressing blockers to fix (by default: excellence voting)
- Identify the most pressing blockers to fix.
- Make sure our top N (for some value of N) blockers will have good problem statements within 24 hours of the meeting end time.
Note: this may be fast - if it is, we'll do some quick lightning brainstorm rounds to generate possible solutions to our most pressing blockers/problems. If not, I'm happy leaving with a good understanding of what needs to be fixed and why.