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

From MozillaWiki
< QA‎ | Testdays
Jump to navigation Jump to search
(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...")
 
 
(41 intermediate revisions by 6 users not shown)
Line 2: Line 2:
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.
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)
* When: September 22-26, 2014 (various times)
* Where: #qa channel on irc.mozilla.org
* Where: #qa channel on irc.mozilla.org
* What: Mentorship (various topics to be determined)
* What: Mentorship (various topics to be determined)


= Requirements =
= Success Criteria =
== Organizers ==
We will succeed if:
At a minimum we require 5 people to organize a testing activity (one for each day of the week).
* 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


Responsibilities:
= Before the Event =
* identifying a topic to oversee
We need the following before the event can be advertised:
* identifying a day/time period for your activity
* 5 or more volunteer [[#Organizers|organizers]]
* ensuring a very basic tutorial exists for participants to reference
* 5 or more volunteer [[#Mentors|mentors]]
* {{ok|}} [[QA/Testdays/Guidelines|checklist]] of requirements/guidelines for organizing testdays
* {{done|}} [https://mozillians.org/en-US/group/testdays-relaunch-v1/ Mozillians group] to organize participants of the event [Anthony Hughes]
* {{done|}} [https://docs.google.com/forms/d/1ZPa-0g_jqfRQdhBLOJFLms9VudvjLjVGKOHeHpJNLyk/viewform survey] to collect feedback from participants [Aaron Train]


Suggestions:
= Volunteers =
* put a time limit on your activity (2 hours is recommended)
'''Do not volunteer unless you're 100% committed!''' If you do volunteer, add something to your calendar as a reminder.
*


== Mentors ==
'''Volunteering is for everyone'''. As long as have a testing knowledge you want to share (ex. tools, skills, etc) we need your help.
At a minimum we require one person per testing activity, in addition to the organizer, willing to provide mentorship.


Responsibilities:
== Organizers ==
* being on IRC during the time dictated by the activity
We require 5 or more people to organize a testing activity, and at least one for each day of the week.
* 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:
; Responsibilities
* use Vidyo (or some other medium) so you can have more productive 1:1 interactions and screenshare if necessary
* identifying a topic to oversee
* 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
* provide instructions on how to contribute after-hours
* 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)
* if you volunteer, add your name/activity to the [[#Sign-ups|sign-up sheet]]


= Topic Suggestions =
; Topic Suggestions
* teaching our tools and methods to testing
* teaching our tools and methods to testing
* how to file a bug
* how to file a bug
Line 38: Line 45:
* 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:
== Mentors ==
We require 5 or more volunteers to mentor, and at least one person per testing activity, in addition to the activity organizer.
 
; 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)
* 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/forms/d/1ZPa-0g_jqfRQdhBLOJFLms9VudvjLjVGKOHeHpJNLyk/viewform 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)
* if you volunteer, add your name to the [[#Sign-ups|sign-up sheet]]
 
== 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
 
= Mentor Sign-ups =
 
Please also link your Mozillians profile from your name
 
{| class="wikitable" width="100%"
|-
! When <br> ''(day/time - PDT)''
! Topic <br> ''(subject of mentorship)''
! Organizer <br> ''(your name/nick)''
! Mentors <br> ''(your name/nick)''
! Documentation <br> ''(links to docs/videos/etc)''
|-
| Monday, Thursday, Friday - 7:00 AM PDT (14:00 UTC) to 2:00 PM PDT (21:00 UTC)
| Learning about MozRegression, our regression range finder for Firefox builds
| [https://mozillians.org/en-US/u/AaronMT/ Aaron Train] (:AaronMT)
| [https://mozillians.org/en-US/u/AaronMT/ Aaron Train] (:AaronMT), Liz Henry (:lizzard)
| [https://quality.mozilla.org/docs/bugzilla/guide-to-triaging-bugs-for-firefox/finding-a-regression-window/ Finding a Regression Window]
|-
| Tuesday, Wednesday, Saturday, Sunday - 6:30 AM PDT (13:30 UTC) to 9:30 AM PDT (16:30 UTC)
| Learning about One and Done
| Swarnava Sengupta (:Swarnava)
| Swarnava Sengupta (:Swarnava)
| How to get Start with Mozilla One and Done
|-
| Tuesday, Wednesday, Saturday, Sunday - 6:30 AM PDT (13:30 UTC) to 9:30 AM PDT (16:30 UTC)
| Learning about Moztrap
| Swarnava Sengupta (:Swarnava)
| Swarnava Sengupta (:Swarnava)
| How to get Start with Moztrap
|
|-
| Monday, Thursday - 8:00 AM PDT (15:00 UTC) to 9:00 AM PDT (16:00 UTC)
|  Getting started with bugzilla.mozilla.org. How to read and understand bugs. Searching in Bugzilla. Filing good bugs, explanation of life cycle of a bug.
| Liz Henry (:lizzard)
| Liz Henry (:lizzard), Anthony Hughes (:ashughes)
| Bugzilla Guided Tour
|-
| Monday,Friday, Saturday, Sunday - 8:30 AM PDT (15:30 UTC) to 11:30 AM PDT (18:30 UTC)
| Getting started with One and Done
| Jayakumar Sadhasivam (:iamjayakumars)
| Jayakumar Sadhasivam (:iamjayakumars), Anthony Hughes (:ashughes)
| [https://wiki.mozilla.org/QA/Taskboard Driving through One and Done]
|-
| Monday,Friday, Saturday, Sunday - 8:30 AM PDT (15:30 UTC) to 11:30 AM PDT (18:30 UTC)
| Getting started with Moztrap
| Jayakumar Sadhasivam (:iamjayakumars)
| Jayakumar Sadhasivam (:iamjayakumars), Anthony Hughes (:ashughes)
| [https://wiki.documentfoundation.org/MozTrap How to get Start with Moztrap]
|-
| Monday, Wednesday - 12:30 PM PDT (19:30 UTC) to 14:30 PM PDT (21:30 UTC)
| Basic troubleshooting
| Gabriela Montagu (:gaby2300) [https://mozillians.org/en-US/u/gaby2300/]
| Gabriela Montagu (:gaby2300)
| Restarting with all addons disabled: https://docs.google.com/document/d/1arbMZtnaf80gtHRn_OQtAKMht1iJ8YMJcePQ7fJMrSg/edit?usp=sharing. How to create a new profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
|-
|}
 
= Schedule of Events =
== Monday ==
* 07:00 - 14:00 PDT (UTC -7): [https://quality.mozilla.org/docs/bugzilla/guide-to-triaging-bugs-for-firefox/finding-a-regression-window/ Finding a Regression Window] (AaronMT)
* 08:00 - 09:00 PDT (UTC -7): Bugzilla Guided Tour (lizzard)
* 08:30 - 11:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
* 12:30 - 14:30 PDT (UTC -7): Basic Troubleshooting (gaby2300)
 
== Tuesday ==
* 06:30 - 09:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
 
== Wednesday ==
* 06:30 - 09:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
* 12:30 - 14:30 PDT (UTC -7): Basic Troubleshooting (gaby2300)
 
== Thursday ==
* 07:00 - 14:00 PDT (UTC -7): [https://quality.mozilla.org/docs/bugzilla/guide-to-triaging-bugs-for-firefox/finding-a-regression-window/ Finding a Regression Window] (AaronMT)
* 08:00 - 09:00 PDT (UTC -7): Bugzilla Guided Tour (lizzard) (first step: [https://bugzilla.mozilla.org/ Create a bugzilla account])
 
== Friday ==
* 07:00 - 14:00 PDT (UTC -7): [https://quality.mozilla.org/docs/bugzilla/guide-to-triaging-bugs-for-firefox/finding-a-regression-window/ Finding a Regression Window] (AaronMT)
* 08:30 - 11:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
 
== Saturday ==
* 06:30 - 09:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
* 08:30 - 11:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
 
== Sunday ==
* 06:30 - 09:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
* 08:30 - 11:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)


* mentors should encourage and assist mentees with registering a Mozillians account and tag so we can contact them later
= Next Steps =
* 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]
* 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

Latest revision as of 15:23, 24 September 2014

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

Before the Event

We need the following before the event can be advertised:

  • 5 or more volunteer organizers
  • 5 or more volunteer mentors
  • [ON TRACK] checklist of requirements/guidelines for organizing testdays
  • [DONE] Mozillians group to organize participants of the event [Anthony Hughes]
  • [DONE] 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.

Volunteering is for everyone. As long as have a testing knowledge you want to share (ex. tools, skills, etc) we need your help.

Organizers

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)
  • ensuring a very basic tutorial exists for participants to reference
  • provide instructions on how to contribute after-hours
  • 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)
  • if you volunteer, add your name/activity to the sign-up sheet
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)

Mentors

We require 5 or more volunteers to mentor, and at least one person per testing activity, in addition to the activity organizer.

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)
  • encourage your contributor(s) to register a Mozillians account under the Testdays-Relaunch-v1 group (be willing to walk them through if necessary)
  • encourage your contributor(s) to 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)
  • if you volunteer, add your name to the sign-up sheet

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

Mentor Sign-ups

Please also link your Mozillians profile from your name

When
(day/time - PDT) 		Topic
(subject of mentorship) 		Organizer
(your name/nick) 		Mentors
(your name/nick) 		Documentation
(links to docs/videos/etc)
Monday, Thursday, Friday - 7:00 AM PDT (14:00 UTC) to 2:00 PM PDT (21:00 UTC) Learning about MozRegression, our regression range finder for Firefox builds Aaron Train (:AaronMT) Aaron Train (:AaronMT), Liz Henry (:lizzard) Finding a Regression Window
Tuesday, Wednesday, Saturday, Sunday - 6:30 AM PDT (13:30 UTC) to 9:30 AM PDT (16:30 UTC) Learning about One and Done Swarnava Sengupta (:Swarnava) Swarnava Sengupta (:Swarnava) How to get Start with Mozilla One and Done
Tuesday, Wednesday, Saturday, Sunday - 6:30 AM PDT (13:30 UTC) to 9:30 AM PDT (16:30 UTC) Learning about Moztrap Swarnava Sengupta (:Swarnava) Swarnava Sengupta (:Swarnava) How to get Start with Moztrap
Monday, Thursday - 8:00 AM PDT (15:00 UTC) to 9:00 AM PDT (16:00 UTC) Getting started with bugzilla.mozilla.org. How to read and understand bugs. Searching in Bugzilla. Filing good bugs, explanation of life cycle of a bug. Liz Henry (:lizzard) Liz Henry (:lizzard), Anthony Hughes (:ashughes) Bugzilla Guided Tour
Monday,Friday, Saturday, Sunday - 8:30 AM PDT (15:30 UTC) to 11:30 AM PDT (18:30 UTC) Getting started with One and Done Jayakumar Sadhasivam (:iamjayakumars) Jayakumar Sadhasivam (:iamjayakumars), Anthony Hughes (:ashughes) Driving through One and Done
Monday,Friday, Saturday, Sunday - 8:30 AM PDT (15:30 UTC) to 11:30 AM PDT (18:30 UTC) Getting started with Moztrap Jayakumar Sadhasivam (:iamjayakumars) Jayakumar Sadhasivam (:iamjayakumars), Anthony Hughes (:ashughes) How to get Start with Moztrap
Monday, Wednesday - 12:30 PM PDT (19:30 UTC) to 14:30 PM PDT (21:30 UTC) Basic troubleshooting Gabriela Montagu (:gaby2300) [1] Gabriela Montagu (:gaby2300) Restarting with all addons disabled: https://docs.google.com/document/d/1arbMZtnaf80gtHRn_OQtAKMht1iJ8YMJcePQ7fJMrSg/edit?usp=sharing. How to create a new profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Schedule of Events

Monday

  • 07:00 - 14:00 PDT (UTC -7): Finding a Regression Window (AaronMT)
  • 08:00 - 09:00 PDT (UTC -7): Bugzilla Guided Tour (lizzard)
  • 08:30 - 11:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
  • 12:30 - 14:30 PDT (UTC -7): Basic Troubleshooting (gaby2300)

Tuesday

  • 06:30 - 09:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)

Wednesday

  • 06:30 - 09:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
  • 12:30 - 14:30 PDT (UTC -7): Basic Troubleshooting (gaby2300)

Thursday

Friday

  • 07:00 - 14:00 PDT (UTC -7): Finding a Regression Window (AaronMT)
  • 08:30 - 11:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)

Saturday

  • 06:30 - 09:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
  • 08:30 - 11:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)

Sunday

  • 06:30 - 09:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)
  • 08:30 - 11:30 PDT (UTC -7): One & Done, Moztrap (Swarnava & iamjayakumars)

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
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Testdays/Events/Relaunch_v1&oldid=1017887"