QA/QA Services/Meetings/2010-07-28

From MozillaWiki
Jump to: navigation, search

« previous mtg | QA Services Home | next mtg »

QA Services Team Meeting

  • July 28, 2010
  • Attendees: marcia, matt, juanb, anthony, marco, henrik, tomcat

Discussion Items

Project Status

CrashKill [tomcat/marcia]

Accessibility Status Update [marco]

  • Firefox 4
    • Still working on regressions from bug 574312, making headway.
    • I'm hammering on the nightlies to see if our recent perf fixes cause any more regressions, but looking good.
  • Firefox 3.6.x:
    • Dealing with some OOPP related issues from third-party vendors we didn't expect, like some anti-spyware that for some reason runs into trouble. It's most likely their issue that they can't deal with the OOPP architecture, but investigation is going on still.

Community Building (ideas and progress) [marcia]

  • Summary of Brainstorming Session
    • Matt is still adding detailed notes here
  • Next Steps?
  • Tomcat
    • Focus on expanding & coordinating the Nightly Tester Community
    • Also plans to expand and plan the L10n QA Community - starting in Europe, because i'm "local"

QA Videos [marcia]

Community Events [marcia/tomcat]

QMO2 [aakashd]

  • Dropped plans for Wordpress with Crowdsourcing as the implementation would be too difficult and not enough benefit
  • I'm delving in and planning to contribute to Mozilla Lab's Crowdsourcing Crowdsource project to determine ideas and implementation help on QMO

Roundtable

  • Coordinating Testdays, Bugdays through QA Services [marcia]

Action Items/Takeaways

Notes and Action Items:

CrashKill

  • Crashes that have been discussed

**Get visibility into new crashes and let the team know. Tomcat working on a crash dashboard schema

      • Be able to identify if something in crash stats if is a regression or this is a new issue -
      • Good lesson and something we can talk to the Socorro team about - maybe they can help us with a feature that would more easily flag information.

Accessibility

  • New issue - spyware installs a plugin into FF
  • FF 4 issues don't seem to have accessibility issues
    • App tabs - way to tell something is an app tab
    • Firefox button - not an accessibility issue
    • Context menu changes should not be an issue

+=Community==

  • Matt: Expansion and utilization of the community. Lot of that will be engagement - idea stage
  • what programs we can get in place
  • explore and talk with other groups
  • Next steps
    • QA newsletter
    • One more meeting between Tomcat, Marcia and Matt. Then we will probably take to the whole team for feedback

QA Video

  • marcia to schedule a meeting next week to discuss the QA international video

Roundtable

  • Devise checklists for meetups, bugdays and testdays
    • marcia to devise checklist for Meetups and Testdays, anthony to handle bugdays
  • Test Day
    • Were some things to look at - list of test cases
    • checklist -
    • whoever proposes it is leading the effort - with the Developer
    • Properly promoted and announced at Monday meeting - and other places
    • Create a Twitter account - Encompass Test Days, etc - juanb
      • Aakash already tweets using the QACommunity name, but we should all use our own accounts and retweet
  • Matt discussion with Mike Beltzner - enhance recognization of community members. Have a section in the Rel Notes that recognizes community members.

**Create a status whiteboard entry and communicate this to team - marcia

    • Community Giving Program - more memory, machine, training, define this
    • https://wiki.mozilla.org/Community:CommunityProgram
    • Finding out will motivate them to volunteer their time
      • Create a survey to send to the Summit invitees about why they have been contributing and what motivates them- marcia