Community testing meetings/2008-11-06

This is a pre-meeting agenda.The meeting is in #olpc-meeting on Start date::November 11, 2008 17:00 (Eastern standard time in the USA).

Previous meeting's action items

See Testing meetings/20081030#Action items.

Activity testing

Current Activity prep-for-test procedure feedback (lfaraone, mchua)

We'll have a portal page with the current procedure up, so it's a little easier to discuss.

Status of current Activities being tested (mchua, frandog)

To cover:

• Analyze (Mchua and Frances looking for someone to hand this off to)
• Speak (Gregdek)
• Paint? (Bjordan?)

Prioritizing Activities to test (gregdek)

What options/tools are out there?

The below is from Cjl, via email (posted with permission)

I'm not 100% sure that a whole lot of time thinking it through will yield significantly better results than taking list of activities in images used for large deployments (including both countries and G1G1) and ordering those by which activity author steps up first. Ideally all activities hosted on dev get tested at some point, I don't know that there is a lot of meaningful distinction in which order they get their "first testing".

After a first round, events that would merit a second round of testing would include significant version change (e.g. rebasing on a changed upstream element abiword, xulrunner, etc.), significant build change or new inclusion by a significant deployment e.g. (Conozco uruguay). Ideally community testing is something tha a new user can just jump into solo (after the hard work of building test cases and infrastructure is done), but there are distinct advantages of scheduled joint cooperative activity on that inital round of test case creation and testing. Activity author involvement seems critical to me during this phase.

If there is indeed some interest in gathering real data about usage from users, I do not think any covert means could or should be employed, on the otherhand, there is theoretically a "Poll Builder" activity that could possibly be leveraged to this end. A "customer survey" using it would also serve the purpose of providing a demonstrable use case for this activity to users.

There is some distinction between building the tools for enabling meaningful community testing and efforts to build *community* for community testing, but they are inter-related efforts and done well, these are mutually reinforcing.

Displaying testing metrics in motivating ways (cjl, from notes)

What options/tools are out there?

Test Activity brainstorming (cjb)

What kind(s) of Sugar Activities could we make for community testing?

Some notes on infrastructure

• How are these meetings working out for people?
• Feedback on meeting time/place/format?
• Are there any ground rules/procedures we should obviously set? (Answer will probably be no this time - that's great, we'll keep an eye out and bring this up again in a few weeks)