Changes

* 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 Suggestions:* provide instructions on how to contribute after-hours* put a time limit on create an etherpad, wiki page, or whatever way works for you to record contributors and their contributions during your activity (2 hours is recommendedthis way we can loop back with you to evaluate)*

* being be on IRC during the time dictated by the activity* providing 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/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!''

SuggestionsResponsibilities:* use Vidyo (or some other medium) so you can have more productive 1:1 interactions Welcome new people who've joined the channel* Ping activity organizers and screenshare if necessarymentors to help connect potential contributors* Suggested documented instructions/tutorials/mentors for contributors showing up after-hours

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* survey = Hurdles to people who participated (testers, mentors, and organizers) (leeway into future events)Success =** httpsWe will not succeed if://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 youwe don'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** t 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 bestDefinition of Success:* retention of people (bugzilla, one and done tasks, coming back to a testday, etc)* positive feedback from participantsPotential Hurdles to Success:* not enough people signing up to own/organize and mentor* people not honouring commitments who volunteer to organize/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 do not follow our traditoinal checklistthrough on their commitmentsQuestions:* = Next Steps:=