Community testing meetings/2008-11-13: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 4: Line 4:
This is a [[Community testing meeting]]. '''This meeting is over.''' Location is in '''#olpc-meeting''' on [[Start date::November 13, 2008 22:00]] (time is in UTC, [http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=6&year=2008&hour=22&min=0&sec=0&p1=0 click here] to find the meeting time for your time zone.)
This is a [[Community testing meeting]]. '''This meeting is over.''' Location is in '''#olpc-meeting''' on [[Start date::November 13, 2008 22:00]] (time is in UTC, [http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=6&year=2008&hour=22&min=0&sec=0&p1=0 click here] to find the meeting time for your time zone.)


Meeting logs are [http://meeting.laptop.org/olpc-meeting.log.20081113_1659.html here]. Notes coming soon!
Meeting logs are [http://meeting.laptop.org/olpc-meeting.log.20081113_1659.html here].


== Previous meeting's action items ==
== Previous meeting's action items ==

Revision as of 06:31, 14 November 2008

  This page is part of the OLPC Community testing Project. How to test an Activity | Reporting test results | Meetings
XO Checkbox

This is a Community testing meeting. This meeting is over. Location is in #olpc-meeting on Start date::November 13, 2008 22:00 (time is in UTC, click here to find the meeting time for your time zone.)

Meeting logs are here.

Previous meeting's action items

See Community testing meetings/2008-11-06

Exciting updates since:

  • Gary got in contact with Sugarbot's developer, Zach!
  • Great thoughts from Greg re: Activity ownership and upstream
  • Anna from the Birmingham deployment edited Talk:Dsh with XS setup instructions

G1G1: What can we do to help?

  • Caryl's Test Jam idea

Activity testing instructions

Feedback on How to test an Activity? Volunteers to help build/test/maintain?

Excellent point brought up by Caryl and Greg via email: We are building a community of testers who are dedicated to keeping their individual Activities well-tested and properly functioning, and one part of this is making sure that the documentation matches with the product under test, and that they're both ridiculously good. ("High-quality" might be the, ah, more proper term.) The product under test includes documentation.

Test result reporting instructions

Feedback on Reporting test results? Volunteers to help build/test/maintain?

Activity testing automation

See Activity testing automation

Mission/scope/focus of Community testing

What are our goals? See Community Testing#Introduction for the current strawman. After we agree on goals, we can figure out how to measure whether we're meeting them. We're already working towards these goals (or a very similar set), and should continue to - it's just sometimes useful to state these things explicitly.

Action items

  • mchua to talk with sj, kimquirk, and others about what kinds of brib^H^H^H^H resources we can offer to motivate and reward testers, both tangible and intangible. (Deferred from last week on account of SJ and Kim's G1G1 workload.)