From MozillaWiki
< QA‎ | Testdays‎ | Strategy
Jump to: navigation, search

Meeting Information


  • Anthony Hughes
  • Aaron Train
  • Gabriela Montagu
  • Syd Polk

Previous Actions


e.g, & Anthony/Aaron

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



  • 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)


  • 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
  • MDN Documentation
  • Getting better at soliciting support


Anthony - Loop back with Liz on her action items Anthony - File P1 testdaybot issues in github Anthony - Work with Liz on Loop testday to try out some new testday ideas