QA/Community/QMO Design/Dev Specs

From MozillaWiki
Jump to navigation Jump to search

« QA/Community/QMO_Design

As of 8/14/08, the QMO2 theme is almost complete. Progress can be viewed at http://mozilla.advomatic.com.

During theme and module development a number of questions have come up about how some of the features of the QMO2 might work. This document is to go over some of the basic functionality we are looking for.


Project Work Flow

  • Creating a new project
    • Require user to fill out:
      • Title, Summary, Details for content area
      • Objective and Tasks for side block
      • Getting Started message for membership emails
    • Other stuff:
      • Make it an option to create blocks "More Tips & Info" and "Tool Box" for each project.
      • Add "Do More" and "Mozilla QA Companion" blocks to bottom of content area
  • Joining a project
    • User clicks "Join Project" button
      • User gets added to "Members" list in side block and project is added to user profile
      • User gets "Getting Started" email message with more info and link to project
  • Project team interact through project page
    • Need to add "Discuss Project" button below "Join Project" that takes user to the project forum thread
    • Top 5 topics should appear in the "Discussion" section of side block AND/OR at the bottom of the content area (if at bottom, include summaries as well)

Events Work Flow

  • Creating a new event
    • Require user to fill out:
      • Title, Dates, Summary for top of content
      • "How to get Started" content or reuse an existing block; should have info about builds to download, IRC channel, and feedback channels.
      • Details related to event; provide user with template that include: Goals, Bug Lists, Test Case, etc
      • Getting Started message for membership emails; should create a template for these emails so users can just enter a few fields for event specific details.
    • Other stuff:
      • Make it an option to create blocks "More Tips & Info" and "Tool Box" for each project.
      • Add "Do More" and "Mozilla QA Companion" blocks to bottom of content area
  • Joining a project
    • User clicks "Join Event" button
      • User gets added to "Participants" list in side block (this block is new and needs to be created for each event) and event is added to user profile
      • User gets "Getting Started" email message with more info and link to event
  • Event participants interact through project page
    • Need to add "Discuss Event" button in side block that takes user to the project forum thread at bottom of content area.
    • Top 5 topics should appear in the "Discussion" section at the bottom of the content area

Badges System

  • Creating badges
    • Allow us to define name, tags, description, and images (preferably some standard size that works well with Drupal profiles)
    • Set points requirements for each type of badge (eg. 1000pts for Bugzilla badge)
  • Getting badges
    • Allow privileged users (TBD) to give out badges to other users (we can have an offer/accept system, or we can just push the badge into their profile without prompting... depends on how much time you have)
    • If user collects enough points for a particular badge, reward him that badge (need to keep track of points for various tags associated with points and badge mapping)
  • Displaying badges
    • On user profile page (default)
    • Next to or under name in any blog, forum, or comment posts (if user decides to do so in profile settings)
    • Community page/Gallery (default)

Points System

  • Giving out points
    • Allow privileged users to give out points to any user; they must specify the amount of points and associate them with one or more tags
    • Do it through user profiles or through a custom point admin page (select 1+ users and fill in points and tags)
  • Earning points
    • QA team members will often give out points manually for various accomplishments
    • Ideally we would automate some of the point earning by monitoring the user's activity on Bugzilla and Litmus (perhaps add in hooks to MozillaZine and Newsgroups at some point)
    • For Bugzilla points:
      • Query Bugzilla for activity based on comments posted, resolutions updated, patches submitted, flags set, etc and generate some numerical value to convert into points (run weekly or monthly)
      • Still need to sort this out, but it might be worth adding in the APIs so we can just plug in queries and grab the counts we get back.
      • URL: http://bugzilla.mozilla.org
    • For Litmus points:
      • Query Litmus for tests run, test cases created/edited/updated
      • Still need to sort this out, but it might be worth adding in the APIs so we can just plug in queries and grab the counts we get back.
      • URL: http://litmus.mozilla.org
  • Displaying points
    • On user profile page (default)
    • Community page/Gallery (default)
    • Mozilla QA Points Top 10 page?

Docs Page

Tools Page

User Profiles

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Community/QMO_Design/Dev_Specs&oldid=104352"