Confirm
14,525
edits
Changes
Created page with "= 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..."
= 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.
* When: September 22-26, 2014 (various times)
* Where: #qa channel on irc.mozilla.org
* What: Mentorship (various topics to be determined)
= Requirements =
== Organizers ==
At a minimum we require 5 people to organize a testing activity (one for each day of the week).
Responsibilities:
* identifying a topic to oversee
* identifying a day/time period for your activity
* ensuring a very basic tutorial exists for participants to reference
Suggestions:
* put a time limit on your activity (2 hours is recommended)
*
== Mentors ==
At a minimum we require one person per testing activity, in addition to the organizer, willing to provide mentorship.
Responsibilities:
* being on IRC during the time dictated by the activity
* providing 1:1 mentorship to anyone who needs it by whatever means is most effective for you
* encourage your contributor to register a Mozillians account (be willing to walk them through if necessary)
Suggestions:
* use Vidyo (or some other medium) so you can have more productive 1:1 interactions and screenshare if necessary
= Topic Suggestions =
* teaching our tools and methods to testing
* how to file a bug
* how to submit a crash report and get that into bugzilla
* how to use IRC
* how to use one & done
* signing up for Mozillians (potentially use to funnel people into QA, QA Events groups)
Requirements:
* mentors should encourage and assist mentees with registering a Mozillians account and tag so we can contact them later
* survey to people who participated (testers, mentors, and organizers) (leeway into future events)
** https://docs.google.com/a/mozilla.com/forms/d/1ZPa-0g_jqfRQdhBLOJFLms9VudvjLjVGKOHeHpJNLyk/edit
* have information available to people showing up in off-hours (requirement in primary event notice/blog)
* Listing mentors by irc name (requirement in the primary event notice/blog)
* have information available and let everyone in #qa channel "act" as moderators
** if you're in channel and see someone who needs help, help them
** both during the event activity and outside of the event activity
* Mentors (minimum of 5 mentors - one for each day)
* Checklist https://wiki.mozilla.org/QA/Test_Days/Checklist
** new checklist needs to be created based on the above requirements -- each organizer will be responsible for checking off their items
** get feedback on the new checklist and cross-reference it after to modernize the old checklist
* Tracking
** whiteboard tagging if your activity is bugzilla focused
** bugs filed, test-cases ran, etc
** who completed what -- mentors can track this whatever way they feel is best
Definition of Success:
* retention of people (bugzilla, one and done tasks, coming back to a testday, etc)
* positive feedback from participants
Potential Hurdles to Success:
* not enough people signing up to own/mentor
* people not honouring commitments to mentor, honoring this is crucial for the testday to be successful -- add something to your calendar as a reminder -- don't sign up if you cannot commit
* new forms of broadcasting event notice & continuing to follow our traditoinal checklist
Questions:
*
Next Steps:
* dev-quality post & qa-staff notice on the structure of the event, what we need from people (topics, owners, mentors, etc) [ashughes]
** be sure to reiterate in the Discussions section of the staff meeting
* develop a feedback survey for the event [aaronmt]
** need topics from mentors so this can be added to the survey
* Figure out if Mozillian tags can be emailed [ashughes] --> pending response from William Reynolds
* Forward channel traffic to #qa [ashughes] --> Gavin suggested "set /mode #lL #testday 1", I'll have to look into this
* Move Testdaybot over to #qa [ashughes] --> pending response from David Burns
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.
* When: September 22-26, 2014 (various times)
* Where: #qa channel on irc.mozilla.org
* What: Mentorship (various topics to be determined)
= Requirements =
== Organizers ==
At a minimum we require 5 people to organize a testing activity (one for each day of the week).
Responsibilities:
* identifying a topic to oversee
* identifying a day/time period for your activity
* ensuring a very basic tutorial exists for participants to reference
Suggestions:
* put a time limit on your activity (2 hours is recommended)
*
== Mentors ==
At a minimum we require one person per testing activity, in addition to the organizer, willing to provide mentorship.
Responsibilities:
* being on IRC during the time dictated by the activity
* providing 1:1 mentorship to anyone who needs it by whatever means is most effective for you
* encourage your contributor to register a Mozillians account (be willing to walk them through if necessary)
Suggestions:
* use Vidyo (or some other medium) so you can have more productive 1:1 interactions and screenshare if necessary
= Topic Suggestions =
* teaching our tools and methods to testing
* how to file a bug
* how to submit a crash report and get that into bugzilla
* how to use IRC
* how to use one & done
* signing up for Mozillians (potentially use to funnel people into QA, QA Events groups)
Requirements:
* mentors should encourage and assist mentees with registering a Mozillians account and tag so we can contact them later
* survey to people who participated (testers, mentors, and organizers) (leeway into future events)
** https://docs.google.com/a/mozilla.com/forms/d/1ZPa-0g_jqfRQdhBLOJFLms9VudvjLjVGKOHeHpJNLyk/edit
* have information available to people showing up in off-hours (requirement in primary event notice/blog)
* Listing mentors by irc name (requirement in the primary event notice/blog)
* have information available and let everyone in #qa channel "act" as moderators
** if you're in channel and see someone who needs help, help them
** both during the event activity and outside of the event activity
* Mentors (minimum of 5 mentors - one for each day)
* Checklist https://wiki.mozilla.org/QA/Test_Days/Checklist
** new checklist needs to be created based on the above requirements -- each organizer will be responsible for checking off their items
** get feedback on the new checklist and cross-reference it after to modernize the old checklist
* Tracking
** whiteboard tagging if your activity is bugzilla focused
** bugs filed, test-cases ran, etc
** who completed what -- mentors can track this whatever way they feel is best
Definition of Success:
* retention of people (bugzilla, one and done tasks, coming back to a testday, etc)
* positive feedback from participants
Potential Hurdles to Success:
* not enough people signing up to own/mentor
* people not honouring commitments to mentor, honoring this is crucial for the testday to be successful -- add something to your calendar as a reminder -- don't sign up if you cannot commit
* new forms of broadcasting event notice & continuing to follow our traditoinal checklist
Questions:
*
Next Steps:
* dev-quality post & qa-staff notice on the structure of the event, what we need from people (topics, owners, mentors, etc) [ashughes]
** be sure to reiterate in the Discussions section of the staff meeting
* develop a feedback survey for the event [aaronmt]
** need topics from mentors so this can be added to the survey
* Figure out if Mozillian tags can be emailed [ashughes] --> pending response from William Reynolds
* Forward channel traffic to #qa [ashughes] --> Gavin suggested "set /mode #lL #testday 1", I'll have to look into this
* Move Testdaybot over to #qa [ashughes] --> pending response from David Burns
