QA/Testdays/Events/Relaunch v1: Difference between revisions

Jump to navigation Jump to search

QA/Testdays/Events/Relaunch v1 (view source)

Revision as of 22:10, 16 September 2014

346 bytes added ,  16 September 2014
no edit summary
No edit summary
Line 7: Line 7:


= Requirements =
= Requirements =
== Event Communication ==
We need the following before the event can be advertised:
* 5 or more volunteer organizers
* 5 or more volunteer mentors
* 5 or more topics for mentorship
* if you volunteer, add something to your calendar as a reminder -- '''don't volunteer unless you can commit'''
== Organizers ==
== Organizers ==
At a minimum we require 5 people to organize a testing activity (one for each day of the week).
At a minimum we require 5 people to organize a testing activity (one for each day of the week).
Line 12: Line 19:
Responsibilities:
Responsibilities:
* identifying a topic to oversee
* identifying a topic to oversee
* identifying a day/time period for your activity
* identifying a day/time period for your activity (a two hour time limit is recommended)
* ensuring a very basic tutorial exists for participants to reference
* ensuring a very basic tutorial exists for participants to reference  
 
* provide instructions on how to contribute after-hours
Suggestions:
* 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)
* put a time limit on your activity (2 hours is recommended)
*


== Mentors ==
== Mentors ==
Line 23: Line 28:


Responsibilities:
Responsibilities:
* being on IRC during the time dictated by the activity
* be 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
* 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)
* encourage your contributor to register a Mozillians account under the [https://mozillians.org/en-US/group/testdays-relaunch-v1/ Testdays-Relaunch-v1] group (be willing to walk them through if necessary)
* encourage your contributor(s) to register a Mozillians account under the [https://mozillians.org/en-US/group/testdays-relaunch-v1/ Testdays-Relaunch-v1] group (be willing to walk them through if necessary)
* encourage your contributor(s) to [https://docs.google.com/a/mozilla.com/forms/d/1ZPa-0g_jqfRQdhBLOJFLms9VudvjLjVGKOHeHpJNLyk fill out our survey] after they've finished participating (make sure you fill out this survey as well)
* 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!''


Suggestions:
Responsibilities:
* use Vidyo (or some other medium) so you can have more productive 1:1 interactions and screenshare if necessary
* 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 =
= Topic Suggestions =
Line 38: Line 50:
* signing up for Mozillians (potentially use to funnel people into QA, QA Events groups)
* signing up for Mozillians (potentially use to funnel people into QA, QA Events groups)


Requirements:
= Definition of Success =
We'll be looking to measure each individual activity and the week as a whole by several metrics. Here are just a couple of ideas:
* we'll retain people and see them active in other areas (bugzilla, one and done tasks, coming back to a testday, etc)
* we'll get feedback from participants


* mentors should encourage and assist mentees with registering a Mozillians account and tag so we can contact them later
= Hurdles to Success =
* survey to people who participated (testers, mentors, and organizers) (leeway into future events)
We will not succeed if:
** https://docs.google.com/a/mozilla.com/forms/d/1ZPa-0g_jqfRQdhBLOJFLms9VudvjLjVGKOHeHpJNLyk/edit
* we don't get enough people signing up to organize and mentor
* have information available to people showing up in off-hours (requirement in primary event notice/blog)
* people who volunteer to organize/mentor do not follow through on their commitments
* Listing mentors by irc name (requirement in the primary event notice/blog)
 
* have information available and let everyone in #qa channel "act" as moderators
= Next Steps =
** 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]
* 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
** be sure to reiterate in the Discussions section of the staff meeting
Line 73: Line 68:
* Forward channel traffic to #qa [ashughes] --> Gavin suggested "set /mode #lL #testday 1", I'll have to look into this
* 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
* Move Testdaybot over to #qa [ashughes] --> pending response from David Burns
* 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
Ashughes
Confirmed users
14,525

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1015603"

Navigation menu