QA/QA Services/Meetings/2010-08-25

From MozillaWiki
Jump to: navigation, search

« previous mtg | QA Services Home | next mtg »

QA Services Team Meeting

  • August 25, 2010
  • Attendees: Matt, Marco, Marcia, Henrik, Tomcat, Anthony

Discussion Items

Project Status

CrashKill [tomcat/marcia]

  • was the first time it was annoucent on planning and got feedback from others! (Tomcat)

Accessibility Status Update [marco]

  • Serious regressions were fixed shortly after last week's staff meeting, but still remaining bug 580464 and bug 580535, which both depend on bug 570275, which received a breakthrough information last night and can commence.
  • Am going to be involved in HTML5 forms enhancements now that they have landed. Need to make sure these are all accessible.
  • Also evaluating the initial MozMill a11y/l10n API work.
  • Firefox 3.6.9/Thunderbird 3.1.3 are good to go from the a11y side. Two important fixes landed in the 1.9.2.9 platform which have a positive impact on user experience on both supported platforms.

Community Building (ideas and progress) [marcia/tomcat]

  • Tomcat
    • Announced my role as QA L10n Coordinator in the l10n newsgroup
    • Nightly Tester list is up and running - subscribe (so far only a few people from the QA Team are on the list)
    • Sent email to Matt about some interesting events in Berlin and SE Asia
  • Community Events [marcia]
  • Resent mail to Mark Surman asking if we can leverage some of the Drumbeat events.
  • Adding a session to the QA Work Week to talk about Community Event Planning for the remainder of this year and into 2011.
    • Three different sources for events:
      • William Quiviger - European Events
      • Gen Kanai - Asia events
      • Sarah Doherty - US/South America events

QA Videos [marcia]

  • Rollup of videos we need to shoot during Work Week
    • Reshoot Tomcat, Martijn and Henrik with soccer ball.
    • Henrik MozMill video
    • Marco video
  • Need to figure out when we will do this during work week
  • Matt had an idea to do a QA Science Fair video
    • We would use the robot to connect Dave, and then follow the robot around as various QAers do demos.

QMO [aakashd]

  • Al and I are working on mock-ups for QMO 3.0
  • We'll have a PRD finished by the end of this week
  • Development time should start either next week or the week after

Roundtable

  • QMO Newsletter
    • Mozilla is switching to a new system
    • Only change we would have to make on QMO would be a link to the sign-up form
    • Quesition is what we want to ask on the sign up form beside emailadress and newsletter format (html/text). We could also ask in what QA Area are interested in.
  • Planning in-litmus? Bugday during QA work week [ashughes]
    • Toying with idea of a week-long "bugday" to clean up in-litmus? queue
    • Call it something like "Mozilla's September Bugzilla Challenge Week"
    • Will be looking for internal signups in different roles (leaders, triagers, educators, etc)
    • Opportunity to learn about triaging, good bug language, and test case writing
    • Prizes for tiers of contribution with a grand prize for the top contributor(s)
    • Finalized Bugday to be posted by end-of-week
    • Any suggestions/ideas/thoughts/questions from the team?
  • QMO Community Leaderboard [ashughes]
    • I'd like to propose adding a leaderboard to QMO
    • Different categories: Overall, Triage, Test Case writer, etc
    • Have a 1st, 2nd, and 3rd place prize on a quarterly basis for top contributor(s)
    • Makes contributing a bit competitive and more fun
    • I'd like to draft up a proposal for the QA work week
    • Any suggestions/ideas/thoughts/questions from the team?
  • Post-crash User Engagement

Action Items/Takeaways

Notes and Action Items:

  • Matt: Reminder for all of QA to Sign up for the nightly tester list
  • Meetups
  • Berlin event - end of September - good event to target

*Videos:

    • What is the difference between the video Matt proposed and what Henrik is doing for MozMill?
      • Introduction of the teams - team leads say who they are
      • Any instructional types of videos that you want to put - outside community members would benefit from
      • Example could be Henrik's talk from the Summit or "What is Brasstacks?"
      • We should take advantage of the fact we are together for work week
      • Rainer can show people how to put a good screencast together
      • All hands in December would be a good time to do new videos

*QMO.next session at Work Week

*QMO newsletter

    • Still in development phase
    • QA needs to figure out:
      • Review what it is our parameters.
      • What is available to us - content management system would it use and who would be responsible for designing it - copy edit.
      • Marcia to set a Meeting for this during the Work Week.
  • Some ideas about what the newsletter could contain:
    • Bug Section
    • Community Member of the Month
    • Conferences
    • First iteration sent it out to nightly and beta testers, types of advertisements that we do - make a link on Facebook - advertise that we do this monthly newsletter. Define what kind of content - what kinds of articles

ashughes - Bug Week and Leadership Board

  • Offering prizes for top contributors
  • Matt - Get it published and advertise - how do they get involved
  • Define what tasks need owners - ownership question.
  • Over the next week or two gets defined.
  • Targeting proposal by Thursday of Friday
  • Separate email - participation will be mandatory and also asking for ideas
  • Leadership Board
    • Achievements plugin for wordpress plugin for Buddypress
    • What is the value of these badges - what do they represent -
    • Automated ways to get tallies - otherwise overhead on admin side
    • Be Careful about how we implementation
    • What are the maintenance requirements to ensure its proper operation over time.
    • Definition of currency
    • Anthony to create the working document and present to team
  • marcia to follow up with David Tenser re: post-crash User Engagement Goal. We need to clarify QA's role and see what can be done in B5 timeframe.