QA/Goals/Q4/CommunityGoals

From MozillaWiki
< QA‎ | Goals‎ | Q4
Jump to: navigation, search

Below are the Q4 2011 Community Goals for the Mozilla QA organization.

Q4 QA Team Community Goals

Desktop Firefox QA Community Goals

Browser Technology QA Community Goals

  • Mobile
    • [ON TRACK] Host 3 Mobile Firefox Testdays
    • [ON TRACK] Posting weekly mobile Testing newsletter
    • [NEW] Work closely with Mobile Dogfood team for internal MoCo outreach
    • [NEW] Present on browser Technologies QA at MozCampAsia
    • [NEW] Update QMO BT page with Mobile projects/How to Get Involved
    • [DONE] Create a DeviceAnywhere public account
  • Services
    • [ON TRACK] Post a series of Sync Tips and Tricks Videos to QMO (targeting 5)
    • [NEW] Host 1 Sync Testday
    • [NEW] Recruit at least one member of the (Mozilla) community to actively participate in BrowserID testing, tools development, and/or client site creation.
    • [NEW] Blogging on Sync Improvements features for desktop and mobile
    • [NEW] Update QMO BT page with Services projects/How to Get Involved
  • Labs
    • [ON TRACK] Host 2 BrowserID Testdays
    • [NEW] Host 1 WebAPI Testday
    • [NEW] Blogging on BrowserID and WebAPI projects
    • [NEW] Recruit at least one member of the (Mozilla) community to actively participate in BrowserID testing, tools development, and/or client site creation.
    • [NEW] [Stretch] Implementing Browser ID sign on to QMO

WebQA Team Goals

  • Community
    • [NEW] Improve onramp for building AMO Selenium/Webdriver tests locally (marlenac) (P1)
    • [NEW] Audit our community contribution paths What are we doing well, what can we improve upon? Implement two of the recommendations by end of the quarter (P1)
    • [NEW] SUMO Community building/Forum Testdays [rbillings] (P2)
    • [NEW] Assist mluna in creating SUMO Volunteer Guidelines [rbillings] (P2)

QA Automation Services Goals

[NEW] Enhance new members and mentors pages to actively gain and retain new contributors

Individual Team Member Q4 Community Goals

Raymond Etornam Agbeame

  • Attend MozCampEU; identify problems they have marketing our products, any Firefox product related bugs contributors have found.

Al Billings

  • Craft blog post for QMO about feedback on QMO experience.
    • Voluntary survey to accompany blog post.

Rebecca Billings

  • [NEW] SUMO Community building/Forum Testdays [rbillings] (P2)
  • [NEW] Assist mluna in creating SUMO Volunteer Guidelines [rbillings] (P2)

Juan Becerra

James Bonacci

  • Community:
    • [NEW] Work with Tracy on two Test Days for Sync.
    • [NEW] Schedule two Test Days for Browser ID.
    • [NEW] Recruit at least one member of the (Mozilla) community to actively participate in Sync Server testing, tools development, and/or server site creation.
    • [NEW] Recruit at least one member of the (Mozilla) community to actively participate in BrowserID testing, tools development, and/or client site creation.
    • [NEW] Update QMO Teams and Docs sites with current, relevant information about and for Browser Technologies and Services QA.

Matt Brandt

    • [DONE] Create a proposed test plan that highlights community involvement that takes into account the bandwidth challenges of webqa.
    • [DONE] Engage and onboard a new community member to assist in creating this test plan.

Kevin Brosnan

David Burns

  • [ON TRACK] Have a working Proof of concept for Powerball

Zac Campbell

Tony Chung

  • present QA talk at MozcampAsia
  • target 1-3 folks from the event for mobile testing outreach

David Clarke

  • [DONE] Create slides for Mozcamp
  • [TODO] Hold a Web Apps test day (Tentatively Dec 2nd)

Marlena Compton

  • [DONE] Improve onramp for building AMO Selenium/Webdriver tests locally
  • [DONE] Help 1 new community member get started writing AMO Automated tests

Mohamed Dabbagh

  • Create several blogs about our Apps testing effort and how to get involved

Cameron Dawson

    • [DONE] Create a google group to gather user feedback
    • [DONE] Blog posts about new releases and future of the product
    • [ON TRACK] Work closely with at least 1 community installation of CC to gather feedback and experiences

Stephen Donner

  • Do a brownbag on how WebQA responds to, plans for, and executes on, new projects, and then have the video archived/streamed on Air Mozilla

Matt Evans

  • Work with CaseConductor team to establish Case Conductor as the premier community based test management tool
  • Participate as a tester and moderator for at least 2 test days

John Hammink

Community Goals - 5%

  • [NEW] Update blog at least tree times this quarter (approx. once a month)
    • [NEW] Get syndicated to QMO and planet
  • [NEW] Drive one testday this quarter

Naoki Hirata

  • Community 20 %
    • [NEW] Stewardship
      • [NEW] maintain and add to QMO for getting started
    • [CARRY OVER] newsletter
      • continue releasing mobile newsletter biweekly.
    • represent QA in MozAsia
    • hold a brown bag to talk about exploratory testing

Anthony Hughes

Dave Hunt

* Release version 1.0 of WebQA's pytest plugin and blog about it.

Marcia Knous

  • Community
    • Work with MozReps at Mozilla Festival and MozCamp events to expand QA presence abroad
    • Evangelize QA contribute opportunities at Mozilla Festival
    • Present a community themed talk at MozCamp event in Berlin
    • Work with Italian community to spur new community involvement and a planned event in 2012
  • Stretch

Geo Mealer

  • Community
    • Get tech blog functional again after domain change, make two high quality posts
    • Organize a test day.

Krupa Raj

  • Setup/Update the firstrun flow for contributors who are new to AMO.

Henrik Skupin

  • Work with the l10n community to strengthen the l10n Mozmill tests

Aaron Train

  • [NEW] Hold a Toronto mobile testers meetup

Martijn Wargers

Tracy Walker

  • Community
    • [NEW] hold at least one test day for Sync
    • [NEW] hook up with the Kansas City QA community, hold/host a casual meet up
    • [NEW] get one person involved with QA