Thunderbird/StatusMeetings/2008-04-01: Difference between revisions
Jump to navigation
Jump to search
m (→Bug Day) |
mNo edit summary |
||
| Line 36: | Line 36: | ||
** advice has been: be more inviting, simple as possible (reduce barriers), attention to first timers, provide "training" before bugday? | ** advice has been: be more inviting, simple as possible (reduce barriers), attention to first timers, provide "training" before bugday? | ||
** [http://wiki.mozilla.org/Thunderbird:Bugdays2 draft schedule] (compare to [http://quality.mozilla.org/events/bug-days#Schedule QMO]) | ** [http://wiki.mozilla.org/Thunderbird:Bugdays2 draft schedule] (compare to [http://quality.mozilla.org/events/bug-days#Schedule QMO]) | ||
** solicit feedback from participants | ** solicit feedback from participants | ||
* statistics | * statistics | ||
** what items do we want to track/graph over time? | ** what items do we want to track/graph over time? | ||
** [http://spreadsheets.google.com/ccc?key=p5s-HZTtle5tmH9YD612eEA&hl=en Draft Google Spreadsheet] | ** [http://spreadsheets.google.com/ccc?key=p5s-HZTtle5tmH9YD612eEA&hl=en Draft Google Spreadsheet] | ||
* | * Which bugs to focus for future bugdays? and query | ||
* weekly until further notice? | * weekly until further notice? | ||
* | * participation / international | ||
** issue-dates: session 1 is evening of bugday-1 for PTD/Americas | |||
** issue-evenings: Americas have no evening session (session 1 starts 11pm PTD) - solutions add session 4 or move session 1 by N hours? (Clint "volunteers I've met and talked to all work on Mozilla after work") | |||
** need list of '''why''' we need intl participation .. | ** need list of '''why''' we need intl participation .. | ||
*** to address bugs with intl issues (which are probably not easily testable or of interest to English-speaking participants) | *** to address bugs with intl issues (which are probably not easily testable or of interest to English-speaking participants) | ||
*** | *** broaden the base of participation | ||
*** ... | *** ... | ||
** and work at how we get there | ** and work at how we get there (some relevant also to non-intl community) | ||
*** made some key contacts before first bugday, and some more since then | *** made some key contacts before first bugday, and some more since then | ||
*** L10N team? | *** L10N team. Contacts? | ||
*** Blog | *** Blog periodically ("helped us a lot in Calendar world") | ||
=== Roundtable === | === Roundtable === | ||
| Line 58: | Line 59: | ||
__NOTOC__ | __NOTOC__ | ||
* | * Strategize improved QA environment - what direction(s) should we go? Examples | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=193873 Bug 193873 – Add Mozilla logging to UI.] | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=193873 Bug 193873 – Add Mozilla logging to UI.] | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=257942 Bug 257942 – need connection / communication Activity Log] | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=257942 Bug 257942 – need connection / communication Activity Log] | ||
=== Attendees === | === Attendees === | ||
Revision as of 14:05, 1 April 2008
last week | index | next week »
Thunderbird Meeting Details
- Tuesday, April 1, 16:30 UTC (9:30am Pacific, 12:30pm Eastern)
- How to dial-in
Agenda
Action Items
Pending
- nth10sd & wsmWK: Bug day on Thursday 27 March 2008.
- nth10sd will be present for all three timeslots.
- wsmWK will be on for the American timeslot.
- Triage old bug review queues
- Feel free to get back to the reviewers within a reasonable timeframe
- A day or two is reasonable
- Some reviewers may not have read the bugmail regarding the review request.
- Ping the reviewer on IRC, or send a personal email
- Feel free to get back to the reviewers within a reasonable timeframe
- Feed reader progress
- No updates
- dmose will ping myk
- No idea if Callek pinged either
Thunderbird:Thunderbird_3.0a1
- Driving
- meeting schedule?
Bug Day
- Improve doc and process
- advice has been: be more inviting, simple as possible (reduce barriers), attention to first timers, provide "training" before bugday?
- draft schedule (compare to QMO)
- solicit feedback from participants
- statistics
- what items do we want to track/graph over time?
- Draft Google Spreadsheet
- Which bugs to focus for future bugdays? and query
- weekly until further notice?
- participation / international
- issue-dates: session 1 is evening of bugday-1 for PTD/Americas
- issue-evenings: Americas have no evening session (session 1 starts 11pm PTD) - solutions add session 4 or move session 1 by N hours? (Clint "volunteers I've met and talked to all work on Mozilla after work")
- need list of why we need intl participation ..
- to address bugs with intl issues (which are probably not easily testable or of interest to English-speaking participants)
- broaden the base of participation
- ...
- and work at how we get there (some relevant also to non-intl community)
- made some key contacts before first bugday, and some more since then
- L10N team. Contacts?
- Blog periodically ("helped us a lot in Calendar world")
Roundtable
- Strategize improved QA environment - what direction(s) should we go? Examples