Meeting Information

When: Tuesday @ 1pm PDT (UTC -7)
Video conference: https://v.mozilla.com/flex.html?roomdirect.html&key=WBuu8ks3P4IZ
Vidyo room: Anthony Hughes (or click the link above ^)
Telephone: +1 (800) 707-2533 p369 x99007
IRC: irc.mozilla.org #qa
Notes from previous meeting: https://wiki.mozilla.org/QA/Testdays/Strategy/Meetings/2014-10-07

Attendees

Aaron

Anthony

create a page to collect ideas for the Bot
- https://wiki.mozilla.org/QA/Testdays/Strategy/Testdaybot
- I think we should prioritize the feedback we have so far, create a roadmap, then solicit future ideas through the github repo
Reach out to organizers of events last week to collect feedback
- emailed each organizer, waiting for response
Invite Michelle to one of our next meetings so we can discuss potential solutions to some of the problems we've been having
- let's brainstorm and prioritize the problems so I have something more concrete to ask of Michelle

Liz

Contacting Reps re: general info
Think about asserting against a checklist to make sure all requirements are information is needed for a testday before holding one, 24 hours in advance (e.g, mentorship sign-up, backup staff are available)

Team

Start thinking of what we want to try to be impactful in Q4
- (Aaron) I think if we get suggested tips and ideas from community managers on where to find new attendees for our events we'll be in a better position to running a successful program. I think we have a great program as is but we need to find people through better outreach. How do we reach the people and go to where the people are? If we have a general idea we should put our focus on that for the quarter and continue to experiment
- (Aaron) Getting organizers to start running their own events and see how they run following our developed strategy
- (Aaron) Integrating Mozilla Reps into our program for regional outreach

Testday bot discussion, need to prioritize list and scrap what is nice to have; identifying a base bot for starting work
- https://quality.mozilla.org/docs/testdays/ documentation, what is worth keeping, trashing
- https://quality.mozilla.org/docs/testdays/ Port to MDN (ashughes)
- https://quality.mozilla.org/docs/testdays/organizing-a-testday/ Port to MDN
- https://quality.mozilla.org/docs/testdays/roles-and-tips/ Port to MDN
- https://quality.mozilla.org/category/events/month Link from top-level MDN doc
- https://quality.mozilla.org/category/events/past Wiki - link from top-level MDN
  - should act as an artifact of past events
  - should also include tasks for how to participate after the event
- http://quality.mozilla.org/docs/testdays/testdays-faq/ Port to MDN (aaron)
- MDN: https://developer.mozilla.org/en-US/docs/Mozilla/QA
- Aaron will port over one document at a time and Anthony will review/revise once ported
Prioritizing problems to solicit help from Michelle (and or Larissa, or even Amy Tsay) with:
- How to attract new people to our efforts?
- Seeking new areas of the internet or at events to raise awareness of our program
- I think it worked well to get registrations from people and send several reminders. 1 day in advance, plus a couple of hours in advance works well.

Anthony

Invite Jennie to the Testday weekly meeting - create a document to form the agenda based on identified problem areas (re: strategy, etc) - consider Thu@9 as the meeting for this so Ioana can attend
File issues for P1 testdaybot usecases from https://wiki.mozilla.org/QA/Testdays/Strategy/Testdaybot#Use_Cases

Aaron

Anthony/Aaron

Solidify thoughts from all past discussions into formal documentation to feed into the new doc