The following documents the roadmap for the Testdays project in 2015.

Key Objectives

Improving accessibility and discoverability of events

• Develop a global events calendar that showcases testdays alongside all other Mozilla events
• Organize events in a local space whenever possible
• Conduct events in a local language whenever possible
• Improve documentation of the program (testdays/bugdays) and develop a long-term roadmap
• Experiment with using different engagement mechanisms (Tiles, Snippets, etc)

Improving diversity of projects organizing events

• Develop a metric and establish a baseline for projects involved with testdays
• Collect feedback from past organizers to identify strengths and weaknesses of testdays
• Identify projects who could benefit from new contributors and design a testday for them

Improving participation following events

• Develop a metric and establish a baseline for testday participants contributing after events
• Collect feedback from past participants to identify strengths and weaknesses of testdays (draft survey)
• Document the various skills, tools, and processes required to participate in testing
• Create an inventory of skills and use this to teach/match people to projects
  • for projects, what skills do they value/need
  • for contributors, what skills do they want to learn

Improving recognition of participants and organizers

• Collect feedback from the community to paint a clear picture of QA's recognition story
• Engage with the Community Education group (ie. Emma Irwin) to collaborate on improving recognition

Address concerns and successes with agility

• Create a feedback loop mechanism for event organizers
• Create a feedback loop mechanism for event participants
• Create a feedback loop mechanism for event non-participants
• Create a feedback loop mechanism for event beneficiaries

January to March

April to June

July to September

October to December