Confirm
14,525
edits
Changes
no edit summary
This page details the plan of action for a week-long event to relaunch the Testdays program. Instead of a single day focused on completing work, we'll have a week with multiple smaller events geared towards mentorship in very specific areas. The ultimate goal is to experiment, to attract and retain more contributors, and to generate more feedback on test events.
= Details =
* When: September 22-26, 2014 (various times)
* Where: #qa channel on irc.mozilla.org
* What: Mentorship (various topics to be determined)
= Success Criteria =
We will succeed if:
* we have multiple committed volunteers
* we retain people and see them active in other areas following the event
* we get feedback from participants and volunteers
= Requirements =
== Before the Event Communication ==
We need the following before the event can be advertised:
* 5 or more volunteer [[#Organizers|organizers]]* 5 or more volunteer [[#Mentors|mentors]]
* 5 or more topics for mentorship
* if a checklist of requirements for each activity* {{done|}} a survey to collect feedback from participants [Aaron Train] == Volunteers =='''Do not volunteer unless you 're 100% committed!''' If you do volunteer, add something to your calendar as a reminder -- '''don't volunteer unless you can commit'''.
=== Organizers ===At a minimum we We require 5 or more people to organize a testing activity (, and at least one for each day of the week).
; Responsibilities:
* identifying a topic to oversee
* identifying a day/time period for your activity (a two hour time limit is recommended)
* create an etherpad, wiki page, or whatever way works for you to record contributors and their contributions during your activity (this way we can loop back with you to evaluate)
=== Mentors ===At a minimum we We require 5 or more volunteers to mentor, and at least one person per testing activity, in addition to the activity organizer, willing to provide mentorship.
; Responsibilities:
* be on IRC during the time dictated by the activity
* provide 1:1 mentorship to anyone who needs it by whatever means is most effective for you (Vidyo is recommended for productive 1:1 interactions and screensharing)
* create an etherpad, wiki page, or whatever way works for you to record people you've mentored and their contributions during your activity (this way we can loop back with you to evaluate)
=== Moderators ===
Unlike in the past, there will be no set moderators in the channel. Instead, everyone who is in the channel will be considered a moderator. In other words, ''if you see someone needs help, help them!''
; Responsibilities:
* Welcome new people who've joined the channel
* Ping activity organizers and mentors to help connect potential contributors
* Suggested documented instructions/tutorials/mentors for contributors showing up after-hours
== Topic Suggestions ==
* teaching our tools and methods to testing
* how to file a bug
* how to use one & done
* signing up for Mozillians (potentially use to funnel people into QA, QA Events groups)
= Next Steps =
