QA/Community/Bug Day/Planner: Difference between revisions

From MozillaWiki
< QA‎ | Community‎ | Bug Day
Jump to navigation Jump to search
No edit summary
(Outdated)
 
(22 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<small>[[QA/Community/Bug Day|&laquo; QA/Community/Bug Day]]</small>
{{outdated}}


= Preparing for Bug Day =
== Preparing for Bug Day ==
== Topics ==
=== Topics ===
* Good topics for bug days allow for steady progress when tackled collaboratively.
* Good topics for bug days allow for steady progress when tackled collaboratively.
** For Bugzilla: Try to focus bug queries such that bug lists are reasonable in length. Mix up the purpose from week to week. (don't just triage bugs every week)
** For Bugzilla: Try to focus bug queries such that bug lists are reasonable in length. Mix up the purpose from week to week. (don't just triage bugs every week)
Line 9: Line 9:
*** Verification
*** Verification
*** etc
*** etc
** Public input tools: Attempt to map reports to bugs
 
*** Talkback
*** Reporter
*** Hendrix
*** Forums
*Suggestions for future topics:
*Suggestions for future topics:
** ???
** ???
** ???
** ???


== Schedule ==
=== Schedule ===


{| border="1"
Moderators tracking page for scheduling [https://wiki.mozilla.org/QA/Bug_Day/Schedule Bug Day planning schedule]
|-
! Date
! Topic
|-
||March 20
||Hendrix mining
|-
||March 27
||Map Hendrix items to bugs
|-
||April 3
|| Thunderbird 2 Unconfirmed Bug Triage and Testing
|-
||April 10
|| Firefox 3 Unconfirmed Bug Triage and Testing
|-
||April 17
|| tbd
|-
||April 24
|| tbd
|-
||May 1
|| tbd
|}


''note: don't forget to check the [[QA/Community/Bug Day/Archive|Bug Day Archive page]] for previously done topics. It's perfectly fine to revisit past topics.  The archives page is out of date. I will be working on pulling topics out of the bug day wiki history to accurately complete that archive.
''note: don't forget to check the [[QA/Community/Bug Day/Archive|Bug Day Archive page]] for previously done topics. It's perfectly fine to revisit past topics.  The archives page is out of date. We'll start filling it in as we go again.


=== Changes to the Wiki ===  
=== Changes to the Wiki ===
*Adjust the following items on the [[QA/Community/Bug Day|Bug Day wiki page]] as appropriate:
*Adjust the following items on the [[QA/Community/Bug Day|Bug Day wiki page]] as appropriate:
** Topic of the day
** Topic of the day
*** Move the old topic, if it's a unique topic, to the [[QA/Community/Bug Day/Archive|Bug Day Archive page]]
*** Copy the last topic, to the [[QA/Community/Bug Day/Archive|Bug Day Archive page]]
*** Replace the old topic with the new topic
*** Replace the last topic with the new topic
*** Include links to bugzilla queries (tinyurls)
*** Include links to bugzilla queries (tinyurls)
** Update status report for the last bugday
** Update status report for the last bug day
** Note who is moderating each session
** Note who is moderating each session
** Release being targeted: Update links to the builds to be tested (usually trunk)
** Release being targeted: Update links to the builds to be tested (usually trunk)
* Update this page with potential topics and schedule them
* Update this page with potential topics and schedule them


== Promote Bug Days for increased participation ==
=== Promote Bug Days for increased participation ===
Post announcements to the following areas Thursday and Monday prior to each Tuesday Bugday:
Post announcements to the following areas Tues and Friday prior to each every other Tuesday Bugday:
* Mozilla QA blog
 
* MozillaZine Firefox build Forum
* [http://quality.mozilla.org/ QMO Frontpage]
* moz.dev.quality newsgroup
* [http://quality.mozilla.org/events QMO Event Calendar]
* Submit a story to MozillaZine (this won't work on short notice)
* [http://groups.google.com/group/mozilla.dev.quality mozilla.dev.quality newsgroup]
* Pass the word around on irc: #qa, #firefox, #developers, etc.
* [http://forums.mozillazine.org/ MozillaZine forums]
* Update link to the Bug Day under [[QA/Community#Hot_Events|Hot Events]]
 
* Get prominent ad on QMO for when it goes live.
== Specific Instructions ==
 
=== QMO Frontpage ===
Create an "Event" after deciding on a date for the next Bug Day. Even if the exact bug list is not set, getting this information out starts the community dialog and gives people enough warning to rearrange their schedule (if necessary).  Creating an event will display it under "Upcoming Events".
 
The "Event" from above should be updated with the following information:
 
* The date and time of the bug day;
* What's the purpose of the bug day;
** Links to instructional documentation.
* links to bug queries;
* links to specific instructions on the [http://wiki.mozilla.org/QA/Community/Bug_Day Bug Day wiki page]. (See above)
 
A reminder blog post should be made right before (one or two days) the actual test day.
 
=== QMO Bug Day Article ===
Create the qmo page for a particular bug day.
 
Be sure to double-check the new test day page to make sure that:
* all dates are '''current''' and accurate;
* links docs are accurate;
* links to bug queries are working and accurate;
* task specifics and instructions are accurate.
* Preview to ensure the layout looks good
 
== mozilla.dev.quality newsgroup & Mailings Lists ==
* Post the announcement to the mozilla.dev.quality Newsgroup and to our 3 Community Mailing Lists
** macqa@mozilla.org
** vistaqa@mozilla.org
** communityqateam@mozilla.org
 
=== MozillaZine forums ===
Post also an article to [http://forums.mozillazine.org/ the MozillaZine forums] to publicize our test days. Also use other Community Forums like the German Firefox Community Forum.


= Misc =  
== Misc ==  
* When appropriate, invite developer(s) to participate
* When appropriate, invite developer(s) to participate
* Adjust plan for regional interests if necessary
* Give responsibility to community members


= Needs =
== Needs ==
* hosts for the Asian and Americas sessions
* hosts/volunteers to help out
* a simple to implement rewards program
* Bug Day topics

Latest revision as of 23:06, 31 January 2024

Ambox outdated.png THIS PAGE MAY BE OUTDATED
This article is in parts, or in its entirety, outdated. Hence, the information presented on this page may be incorrect, and should be treated with due caution until this flag has been lifted. Help by editing the article, or discuss its contents on the talk page.

Preparing for Bug Day

Topics

  • Good topics for bug days allow for steady progress when tackled collaboratively.
    • For Bugzilla: Try to focus bug queries such that bug lists are reasonable in length. Mix up the purpose from week to week. (don't just triage bugs every week)
      • Triage Unconfirmed
      • Dupes
      • Verification
      • etc
  • Suggestions for future topics:
    • ???
    • ???

Schedule

Moderators tracking page for scheduling Bug Day planning schedule

note: don't forget to check the Bug Day Archive page for previously done topics. It's perfectly fine to revisit past topics. The archives page is out of date. We'll start filling it in as we go again.

Changes to the Wiki

  • Adjust the following items on the Bug Day wiki page as appropriate:
    • Topic of the day
      • Copy the last topic, to the Bug Day Archive page
      • Replace the last topic with the new topic
      • Include links to bugzilla queries (tinyurls)
    • Update status report for the last bug day
    • Note who is moderating each session
    • Release being targeted: Update links to the builds to be tested (usually trunk)
  • Update this page with potential topics and schedule them

Promote Bug Days for increased participation

Post announcements to the following areas Tues and Friday prior to each every other Tuesday Bugday:

Specific Instructions

QMO Frontpage

Create an "Event" after deciding on a date for the next Bug Day. Even if the exact bug list is not set, getting this information out starts the community dialog and gives people enough warning to rearrange their schedule (if necessary). Creating an event will display it under "Upcoming Events".

The "Event" from above should be updated with the following information:

  • The date and time of the bug day;
  • What's the purpose of the bug day;
    • Links to instructional documentation.
  • links to bug queries;
  • links to specific instructions on the Bug Day wiki page. (See above)

A reminder blog post should be made right before (one or two days) the actual test day.

QMO Bug Day Article

Create the qmo page for a particular bug day.

Be sure to double-check the new test day page to make sure that:

  • all dates are current and accurate;
  • links docs are accurate;
  • links to bug queries are working and accurate;
  • task specifics and instructions are accurate.
  • Preview to ensure the layout looks good

mozilla.dev.quality newsgroup & Mailings Lists

  • Post the announcement to the mozilla.dev.quality Newsgroup and to our 3 Community Mailing Lists
    • macqa@mozilla.org
    • vistaqa@mozilla.org
    • communityqateam@mozilla.org

MozillaZine forums

Post also an article to the MozillaZine forums to publicize our test days. Also use other Community Forums like the German Firefox Community Forum.

Misc

  • When appropriate, invite developer(s) to participate
  • Give responsibility to community members

Needs

  • hosts/volunteers to help out
  • Bug Day topics
Retrieved from "https://wiki.allizom.org/index.php?title=QA/Community/Bug_Day/Planner&oldid=1249866"