User:Ashughes/Status/2013/12

Previous (March 11-15)

Status for March 18 to 22, 2013

Goals

Monday

Professional Development

• Create a page to track quarterly accomplishments
• Take next steps toward finding a mentor
• Catalog and challenge my assumptions
• Develop a role for a community manager in my team vision
  • Need to fill position for a community manager (someone to wrangle people, foster accountability, steer team along a road map) -- Tracy???
  • Also add need to be more proactive and vocal, don't wait for someone to grant us a voice, lessons learned from B2G QA

Automation

• [DONE] Update status on mozmill-ci l10n expansion (issue 211)
  • Now includes en-US, fr, de, and it

Community

• [DONE] Update testday metrics and contributors
• [DONE] Create a page to track QA Contribute progress

Tuesday

• N/A - PTO - Travelling to Vancouver

Wednesday

Desktop Firefox

• [DONE] Find regression range for bug 851630

Community Engagement

• [DONE] Reach out to QA-Contribute contributors who've not responded in several days
• [DONE] Add a Get Involved section to the Firefox 21 test plan

Softvision Standup

• [DONE] Review status of Firefox 19 post-mortem action items

Social API

• [DONE] Activate and dogfood mixi support
• Develop a mapping of user stories to test cases and dependencies for multi-provider
• Develop a mapping of user stories to test cases and dependencies for Mixi
• Develop a mapping of user stories to test cases and dependencies for MSN Now
• Develop a mapping of user stories to test cases and dependencies for Weibo
• Develop a mapping of user stories to test cases and dependencies for Cliqz

Thursday

Rapid Betas

• Update and review Rapid Betas QA strategy with Juan, Marcia, Otilia, and Ioana

Firefox 21

• QAWANTED bug triage
• [ON TRACK] Dogfood MSN Now support for SocialAPI [wiki]

Documentation

• Revise and simplify Bug Triage document, integrate with B2G Triage document

Friday

Blocklisting

• [ON TRACK] Click-to-Play blocklist for Firefox 21+ [bug 851198]

Firefox 21

• [ON TRACK] mozilla-aurora pushlog triage

Documentation

• Create a document on QMO for testing throttled/unthrottled updates manually
• Create a document on QMO for testing blocklists
• Create a document on QMO for using mozregression (maybe a video too)

Testdays

• Create a document on QMO to showcase contributors [wiki]
• Organize a memshrink for add-ons testday [wiki]
• Create a draft proposal for Testday and Release QA contributor conversion points
• Create a draft proposal for a Testday Framework
  • Ideas include: add a testday component to bugzilla for people to request and vote on testdays, evaluate role of existing tools (wiki, qmo, mailing list, etherpad, irc, moztrap, testdaybot), speak to team leads about testday fatigue, geo-distributed 2h sprints, community leadership, documentation days, bug days, rewards/recognition, conversion points, look at what other teams are doing (fedora, ubuntu, bugmasters, etc), identify and resolve pain points, promote leaders, improve accessibility, learning days, dashboarding/metrics, developer engagement, hours of operation, mentors and moderators, improve clarity of instructions/expectations, improve accountability

Community

• Reach out to lost contributors and develop an exit interview [spreadsheet]

Upcoming

Monday

Automation

• Update status on mozmill metro tests (bug 845079)
• Identify SocialAPI tests for automation

Firefox Desktop

• [ON TRACK] bug 852211 Add automated checks for desupported platforms [RelEng]

Desktop QA Meeting

• Suggest updating Wiki team docs (1, 2) and possibly move them over to QMO

Wednesday

• [ON TRACK] Click-to-Play blocklist for Firefox 21+ [bug 851198]