This guide helps moderators run Patch Testing Scrub sessions. Use the structure and example phrases below as a reference to assign tickets to everyone in attendance.<\/p>\n
Before the session: Announce meeting start:<\/strong><\/p>\n \n \/here We are starting today\u2019s Welcome message<\/strong><\/p>\n \n Hello everyone \ud83d\udc4b\n<\/p><\/blockquote>\n Share any relevant announcements (e.g. a new WordPress version, a beta release, a release candidateRelease Candidate<\/span> A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.<\/span><\/span><\/span>)<\/strong><\/p>\n \n Before we start, WordPress 7.0 RC 2<\/a> is now available for testing. Feel free to try it out and share your feedback.\n<\/p><\/blockquote>\n Invite Participant<\/strong><\/p>\n \n If you\u2019re around, we\u2019d love your help with testing and sharing reports.\n<\/p><\/blockquote>\n Call for testers<\/strong><\/p>\n \n If you\u2019re ready to start patch testing, please reply in this thread so I can assign you a ticket. \ud83e\uddf5\n<\/p><\/blockquote>\n When a participant replies and is ready to test<\/strong><\/p>\n \n Thank you @[YOUR_USERNAME]<\/strong>, for joining us today. You can start working on #[TICKET_NUMBER]<\/strong>\n<\/p><\/blockquote>\n When assigning a follow-up ticket to someone already testing<\/strong><\/p>\n \n @[USERNAME]<\/strong> Thank you for adding a report. You could give this a try #[TICKET_NUMBER]<\/strong>\n<\/p><\/blockquote>\n Tips for choosing tickets<\/strong><\/p>\n Acknowledge test reports as they come in<\/strong><\/p>\n \n Great work @[USERNAME]<\/strong>, thanks for the report!\n<\/p><\/blockquote>\n If a participant finishes early and wants another ticket<\/strong><\/p>\n \n Thanks @[USERNAME]<\/strong>! Here\u2019s another one you can try: #[TICKET_NUMBER]<\/strong>\n<\/p><\/blockquote>\n When ready to wrap up<\/strong><\/p>\n \n Well, this marks the end of today\u2019s Reassure participants they can continue<\/strong><\/p>\n \n Feel free to pingPing<\/span> The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it\u2019s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of \u201cPing me when the meeting starts.\u201d<\/span><\/span><\/span> me if you need to comment on anything, and also if you have not finished with your patch testing, you can continue for as long as you want, and ping me if you have any trouble finishing.\n<\/p><\/blockquote>\n Thank all participants by their SlackSlack<\/span> Slack is a Collaborative Group Chat Platform https:\/\/slack.com\/<\/a>. The WordPress community has its own Slack Channel at https:\/\/make.wordpress.org\/chat\/<\/a><\/span><\/span><\/span> username<\/strong><\/p>\n \n Thanks @[USERNAME1]<\/strong>, @[USERNAME2]<\/strong>, and @[USERNAME3]<\/strong> for coming today. \ud83c\udf89\n<\/p><\/blockquote>\n Total Duration:<\/strong> ~55-60 minutes<\/p>\n If a participant is stuck on a ticket<\/strong><\/p>\n If a ticket has already been tested by someone else<\/strong><\/p>\n \n [18.00] Moderator: \/here We are starting today\u2019s [18:02] Moderator: Hey everyone \ud83d\udc4b<\/p>\n [18:02] Moderator: Before we start, WordPress 7.0 RCRelease Candidate<\/span> A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.<\/span><\/span><\/span> 2 is now available for testing. Feel free to try it out and share your feedback.<\/p>\n [18:02] Moderator: If you\u2019re around, we\u2019d love your help with testing and sharing reports.<\/p>\n [18:02] Moderator: If you\u2019re ready to start patch testing, please reply in this thread so I can assign you a ticket. \ud83e\uddf5<\/p>\n [18:05] Moderator: Thank you @participant1, for joining us today. You can start working on #65007<\/a><\/p>\n [18:08] Moderator: Thank you @participant2, for joining us today. You can start working on #65031<\/a><\/p>\n [18:22] Moderator: Thank you @participant3, for joining us today. You can get started on #64762<\/a><\/p>\n [18:35] Moderator: @participant3 Thank you for adding a report. You could give this a try #65005<\/a><\/p>\n [19:00] Moderator: Well, this marks the end of today\u2019s [19:00] Moderator: Feel free to ping me if you need to comment on anything, and also if you have not finished with your patch testing, you can continue for as long as you want, and ping me if you have any trouble finishing.<\/p>\n [19:00] Moderator: Thanks @participant1, @participant3, and @participant2 for coming today.\n<\/p><\/blockquote>\n
\n1. Review and have TracTrac<\/span> Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https:\/\/core.trac.wordpress.org\/<\/a>.<\/span><\/span><\/span> ticket queue open and ready (Patch Testing Tickets<\/a>). Also, prepare a shortlist of tickets to assign
\n2. Check for any recent WordPress releases, betaBeta<\/span> A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.<\/span><\/span><\/span> releases or release candidates to announce
\n3. Note the scheduled start time and be prepared to monitor the thread throughout<\/p>\nSession Structure & Script<\/h2>\n
1. Opening \/ Welcome (Start Time)<\/h3>\n
<patch-testing-scrub><\/code>\n<\/p><\/blockquote>\n\/here<\/code> notifies only active\/online members in the channel.\n<\/div>\n2. Assigning Tickets<\/h3>\n
\n
3. Monitoring the Session<\/h3>\n
4. Closing<\/h3>\n
<\/patch-testing-session><\/code>\n<\/p><\/blockquote>\nQuick Reference Meeting FlowFlow<\/span> Flow is the path of screens and interactions taken to accomplish a task. It\u2019s an experience vector. Flow is also a feeling. It\u2019s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it.<\/span><\/span><\/span><\/h2>\n
\n
Moderator Tips<\/h2>\n
Assigning & Tracking Tickets<\/h3>\n
\n
Encouraging Participation<\/h3>\n
\n
Handling Common Situations<\/h3>\n
\n
\n
Time Management<\/h3>\n
\n
Resources & Links<\/h2>\n
Essential Pages<\/h3>\n
\n
Example Full Opening Sequence<\/h2>\n
<patch-testing-scrub><\/code><\/p>\n<\/patch-testing-session><\/code><\/p>\n