| Task
|
Description
|
| Testday Catalog
|
Develop a catalog of topics and lessons for testdays
|
| QA Leaderboard
|
Develop a leaderboard to showcase contributors
|
| Reconnect Ex-Organizers
|
Re-introduce people who used to run testdays to the new framework
|
| Brownbags
|
Organize some brownbag presentations to educate people about the new framework
|
| Connect Allies
|
Work with teams within and outside Mozilla aligned to our goals (eg. Mike Hoye)
|
| AMA
|
Run an AMA in the style of MozScience
- get event in front of many people quickly and regularly
- aim for 10% attendance
- have a pathway to allow participants to self-organize
- limit the time of the event to improve level activity
- have a "panel" of experienced/knowledgable people
|
| Collective Creativity
|
TED: Create an environment of creative thinking and experimentation to let ideas be tested and naturally proven.
- testdays & bugdays may continue in their current format but let it be self sustaining
- meetup style events
- mentorship style events
- outreach program to engage with different projects on what getting involved looks like
- revisit the swot analysis to refresh strengths and weaknesses
- documentation days to make sure all our documentation is up to par (perhaps convert these docs to video at some point)
- put much more energy into recognition of participants
- open discussion via discourse
|
| Participation Ladder
|
Define a participation ladder for testdays and integrate with the ladders of other teams
|
| Tutorials
|
Make sure all activities have an associated tutorial (get volunteers to make the tutorials).
|
