QA/Testdays/Strategy/Meetings/2014-11-18

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

Meeting Information

Attendees

Gaby, Jennierose, AaronMT, ashughes

Previous Actions

Aaron

  • Continue to port QMO docs over to MDN with Anthony's review

Anthony

  • Work with Liz on Loop testday to try out some new testday ideas
  • talk to Clint about having a resource to support testdaybot development

Agenda

(Jennie) Creating impact and soliciting support for testdays

  • evaluate your communication channels for effectiveness
  • evaluate communication channels you aren't using, OpenHatch for instance
  • audit who you're trying to reach and what skills you need
  • getting support from staff is a different problem to solve than getting support from contributors
  • weekly events can have deminishing returns
  • try holding a local event
  • try reducing frequency to once per month
  • be very aware of why the event is needed, how it benefits contributors, how contributors will be recognized (tshirt, meeting mentions, meeting invites), how you're encouraging people to come back, how you're integrating participants into the general QA org
  • focus on getting contributors with specific skill sets, not having a lot of contributors
  • develop a comms plan for hosting an event
  • identify reps who are willing to support running local events
  • KEY is identifying how you plan to recognize, reward, and integrate participants
  • https://openhatch.org/
  • http://guides.mozilla-communities.org
  • https://www.mozilla.org/en-US/contribute - we should be feeding QA events and contributor callouts to this page
  • Conduct an audit of the program, swat analysis then analyze how to build from there and a timeline
  • Jennie is willing to try running a local event, so is Gaby
  • Reps reaching out to reps works better than staff reaching out to reps a lot of the time

Actions

Jennie

  • discuss getting better staff support with my team
  • Testday analysis and then set up the next steps at the next meeting

Aaron

  • Continue to port QMO docs over to MDN with Anthony's review

Anthony

  • Work with Liz on Loop testday to try out some new testday ideas
  • talk to Clint about having a resource to support testdaybot development