QA/Community/QMO Design/Design Doc

Target Audience

QMO serves as a portal for the Mozilla QA team and community. Each group will most likely use the site differently.

Mozilla QA Team

• Most of the team will be working on site content and functionality, as well as maintenance and monitoring. We plan to use QMO to:
  • Write articles and/or blog posts to keep the community updated on what we're working on and to ask for help with specific tasks.
  • Create new project pages for things we are working on, to track progress and provide the community a chance to learn more and get involved.
  • Promoting community events through the calendar and front page.
  • Moderating the forum discussions and comments.

Community

• We have identified a few categories of users that will be visiting and using QMO regularly:
  • Average users and new Mozilla community members (looking to learn more about the Mozilla project and how they can get involved)
  • Nightly testers (established contributors that use nightly builds and are fairly active across the Mozilla project's many sites/channels)
  • User-based/Blackbox Testers (anyone that wants to help by testing Firefox, whether it is an official release or nightlies)
  • Bugzilla contributors (people that live and breath bugs by writing, reproducing, and resolving them through Bugzilla)
  • Tools and Automation developers (looking to do a bit of programming and building out the test infrastructure)
  • Data/Information Analysts (for a lack of a better term, there will be people that are interested in just combing through user feedback, crash data, and bug info to get a better understanding of the quality of our products)

• The community will be focused on their particular interests, but everyone will be using QMO to:
  • Keep up with Mozilla QA news, events, and projects
  • Find ways to get involved in various quality assurance activities
  • Communicate and collaborate with Mozilla QA Team members via comments and forum posts.

Frontpage Content

• user login/status, search box, main menu at top of page
• 4 major blocks for each activity flow (test, bug, automate, analyze), with action word + description/links to individual pages near top/center
• monthly all-star contributor block
• main content area in middle/left column
• previous posts/events in middle/right column (2-3 rows)
• quick links menu
• navigation menu for site (projects, team, forums, events, get involved, etc)

References

Website Dev Flow - http://www.ibm.com/developerworks/ibm/library/i-osource2/sidefile1.html OS User/Personas - http://loki.lokislabs.org/weblog/archives/2003/06/25/personas_and_open_user_research.php

QMO Design Meeting Notes (8/17)

• What's working well
  • announcement platform for test days and beta testing
  • planet integration
  • sidebar vs front page, stories + quick links

• What do we need?
  • make event pages more visible
    • event nodes + static event pages
  • better integration with mozillazine
  • forums need to be more visible, need more participation
  • too many sections on front page
  • too many items under personal navigation
  • QA Team Update
    • What's going on with the QA team?
    • section to let community know what we're working on.
  • front page with blocks for each type of user/action items
  • personal touch with live help
  • mini-survey with guided questions as part of sign up process
  • facebook for qa team and community
  • user-customizable content (my yahoo, igoogle)
    • personal content box for links and notes
  • contributor showcase or member of the month box

• Who is using QMO? Who should we target?
  • nightly testers
    • keep nightly testers informed on development changes
  • first-timers
    • lot's of guidance, connect with folks, who we are, workflow for action
  • tools developers
    • direct them to ongoing projects for qa tools and automation

• Todo List
  • QA Blog - redirect permanently
  • mozilla.org - update pages and start migration of some content to QMO
  • Prepare QMO brownbag for team

Back to QMO Design Wiki