QA/Community/QMO Design/Design Doc: Difference between revisions

From MozillaWiki
< QA‎ | Community‎ | QMO Design
Jump to navigation Jump to search
(New page: Target Audience Frontpage Content Required Features P2 Features)
 
Line 1: Line 1:
Target Audience
== 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


Frontpage Content
* 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


Required Features
* 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


P2 Features
* Todo List
** QA Blog - redirect permanently
** mozilla.org - update pages and start migration of some content to QMO
** Prepare QMO brownbag for team
 
== Design Doc ==
'''Target Audience'''
 
'''Frontpage Content'''
 
'''Required Features'''
 
'''P2 Features'''

Revision as of 15:17, 20 August 2007

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
  • 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

Design Doc

Target Audience

Frontpage Content

Required Features

P2 Features