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

m
no edit summary
mNo edit summary
Line 3: Line 3:
''Work in progress - watch for falling wikicode...''
''Work in progress - watch for falling wikicode...''
= Preparing for Bug Day =
= Preparing for Bug Day =
 
== Topics ==
*Change the following items on the [http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day Bug Day wiki page] as appropriate:
** Topic of the day
*** Move the old topic, if it's a unique topic, to the [http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day:Archive Bug Day Archive page]
*** Replace the old topic with the new topic
*** Include links to bugzilla queries (tinyurls)
** Update status report for the last bugday
** 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
* Promoting Bug Days for increased participation - Announcements should be posted to the following areas Thursday and Monday prior to each Tuesday Bugday:
** Mozilla QA blog
** MozillaZine Firefox build Forum
** moz.dev.quality newsgroup
** Submit a story to MozillaZine (this won't work on short notice)
** Pass the word around on irc: #qa, #firefox, #developers, etc.
** Update link to the Bug Day under [http://wiki.mozilla.org/Mozilla_QA_Community#Hot_Events Hot Events]
** Get prominent ad on QMO for when it goes live.
 
* Misc.
** When appropriate, invite developer(s) to participate
** Adjust plan for regional interests if necessary
 
 
== Topic Planner==
*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 71: Line 47:


''note: don't forget to check the [http://wiki.mozilla.org/Mozilla_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 [http://wiki.mozilla.org/Mozilla_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.
=== Changes to the wiki ===
*Adjust the following items on the [http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day Bug Day wiki page] as appropriate:
** Topic of the day
*** Move the old topic, if it's a unique topic, to the [http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day:Archive Bug Day Archive page]
*** Replace the old topic with the new topic
*** Include links to bugzilla queries (tinyurls)
** Update status report for the last bugday
** 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 Thursday and Monday prior to each Tuesday Bugday:
* Mozilla QA blog
* MozillaZine Firefox build Forum
* moz.dev.quality newsgroup
* Submit a story to MozillaZine (this won't work on short notice)
* Pass the word around on irc: #qa, #firefox, #developers, etc.
* Update link to the Bug Day under [http://wiki.mozilla.org/Mozilla_QA_Community#Hot_Events Hot Events]
* Get prominent ad on QMO for when it goes live.
= Misc =
* When appropriate, invite developer(s) to participate
* Adjust plan for regional interests if necessary


= Needs =
= Needs =
* hosts for the Asian and Americas sessions
* hosts for the Asian and Americas sessions
* a simple to implement rewards program
* a simple to implement rewards program
Confirmed users
4,072

edits