Meeting Notes, June 26th 2007

Topic : Building QA community around Preview

Attendees : Ted, Mikeal, Aparna

• The main question is : Do we point people to the right area when they come to our website with an intention to help or contribute to the project? Currently the answer is between no and maybe but we know that we don't have very clear instructions to guide them on how to help and become valuable contributors.
• There are many different areas that people can help even though they may not be developers.
  • They can help execute testcases from the test spec and put down the platform and revision they ran them on. Update the spec with the ones that passed and file bugs for the ones that didn't.
  • They can add additional testcases from their own usecases (after having them approved by a member of the QA team).
  • They can help execute the testcases on other platforms like Linux where we have lesser coverage or various browsers for cosmo UI.
  • They can help verify resolved bugs
  • They can help resolve duplicate bugs (mark new bugs dup of existing ones)
  • They can help add reproduction steps to hard to reproduce bugs
  • They can help test areas that they genuinely use for their workflows for e.g. sorting in the Dashboard, Search etc
  • They can help with interop testing. Helping test our app against other servers and clients.
  • The more advanced helpers can help us add additional python tests for Chandler and windmill tests for Cosmo.

• The objective is to have very clear and precise instructions from an easily accessible page on how contributors can help.
• We will revamp the QA area on the wiki to add links to the 'Help Us' page right on the top. The Help Us page will then guide them through the different projects/tasks they can help with with clear instructions.
• We should also put the time of the IRC QA session on the Help Us as well as the main QA page so people coming to the site can know when we do these collaborative QA sessions that they can participate in.
• We should engage the existing dogfooders like Andre and Davor to get their feedback on specific features they use and are willing to help test.
• Also all the relevant pages should be linked from a single page for e.g. 'Projects.ReportABug', 'CommunityQA', 'InstructionsForDogfooders' etc
• Also make sure we blog actively about our projects within OSAF and personal blogs.

-- AparnaKadakia - 26 Jun 2007