MozillaWiki

QA/Community/QMO Design: Difference between revisions

< QA‎ | Community
(Undo revision 214913 by Term Papers (Talk))
 
(50 intermediate revisions by 11 users not shown)
Line 1: Line 1:
== '''What is QMO?''' ==
<small>[[QA/Community|&laquo; QA/Community]]</small>
'''Why?'''
* With so many different channels of communication, '''new (and sometime veteran) mozilla contributors can sometimes get lost.'''  Developers hang out in #developers, testers use litmus.mozilla.org, everyday users submit Talkback reports and browse the mozillaZine forums...there are just so many places to be. 
* Since '''QA is often the entry point for people interested in the mozilla project''', it is critical to provide them with a place to go to get started.  In the early days, http://www.mozilla.org/quality/ was that place, but over the years it has become outdated as people migrated over to the forums, newsgroups, and wikis.  So most of the information there, although still useful (and mostly relevant), is no longer enough to help someone get started with the mozilla project as a tester.
* QMO will fix both problems mentioned above by providing a '''central portal for everything related to software quality, Mozilla QA, and the mozilla community'''.


'''How?'''
== Current QMO Redesign Project ==
* '''Start with pretty UI and a blog.'''  The website will be blog based so that we can post regularly as we have been doing with the QA blog, but also will provide us with a URL that will be easy for people to remember and get to... and from there, we plan to design that site such that every type of user and contributor will be able to find what they are looking for.  By customizing the design of the site, we hope to create a unique identity for the QA team and community so we all have our own place in the mozilla project community. <font color=red>We have decided to go with Joomla! CMS for QMO and work has begun on building the basic site.  It will be made public as soon as we have enough content there for it to be useful. :-)</font>
* Phase 1: Visual Design (February - March 2008)
* '''Consolidate and update old documents.'''  By finding and cleaning up pages from mozilla.org and the wiki, we hope to convert important docs into static pages, and provide links to certain wiki pages.
** [[QA/Community/QMO_Design/Design Doc | Design Document (to pass on to design team)]]
* '''Make things quick and easy.'''  Whether you want to look up a crash incident with your Talkback ID, find a list of bugs the need to be verified for Firefox 2.0, or see photos of some of our QA volunteers, you will be able to do so quickly and easily from QMO.
** [[QA/Community/QMO_Design/Airbag | QMO Redesign with Airbag Industries]]
* '''Create a launch pad for various QA tools/projects.'''  With a portal like QMO, we will be able to promote important events and tools that will help everyone.  By providing access to Talkback, Reporter, Hendrix, and Litmus, we hope new people will be able to find what they're interested in and start helping out.
** [http://people.mozilla.com/~jpatel/qmo/templates/ Final QMO design templates from Airbag]
* Phase 2a: Content Creation (May - August 2008)
** Outline template pages and relevant content
** Create site sections for assignment
** Gather QA related content links and resources
** Review new content
** Migrate all content to staged QMO site
* Phase 2b: Drupal Development (June - August 2008)
** Bidding process in April/May, decided to go with [http://www.advomatic.com/ Advomatic].
** Delay in development process due to lengthy contract negotiation with Advomatic (5/13 - 6/20)
** Development schedule ([[QA/Community/QMO_Design/Dev_Specs|Spec Document]])
*** Drupal 6 config (July - August)
*** Theme development (August - September)
*** Module development (September)
*** Alpha testing and bug fixing (September)
*** QMO beta release (September - October)


== '''Site Layout''' ==
=== Content & Development links ===
'''Documentation'''
'''Here are some links with what's been worked on. (PaulC and Jay)'''
* Guides & Howtos
* https://intranet.mozilla.org/User:PaulC
* Testing Tips
** The future QMO (QMO2) -- http://people.mozilla.com/~jpatel/qmo/templates/
* Tech Docs
** Glossary of QA terms -- http://quality.mozilla.org/docs/qmo2-glossary
* Mozilla.org Archive
** List of helpful docs -- http://quality.mozilla.org/docs/qmo2
** Readme/Intro for Getting involved with QA -- http://quality.mozilla.org/docs/qmo2-intro
** List of tools -- http://quality.mozilla.org/tools/qmo2
* http://wiki.mozilla.org/QA/Community/QMO_Bugzilla


'''Community'''
'''Staging Sites:'''
* Get Involved
* Advomatic Development Site: http://mozilla.advomatic.com (Public)
** Buzilla Triage
* Mozilla Staging Site: http://quality.authstage.mozilla.com (username: qmo, password: quality)
** Testing
** Crash/Feedback Analysis
** Writing Test Cases
** QMO Design and Maintenance


* Events
== QMO2 Content Creation Assignments ==
** Bug Days
* Below are the assignment for getting data/docs together from various sources and getting them ready to import/migrate/add to QMO2 when the site is ready.  Each group of people should think about what content is relevant for their area and decide where they might want to put it.  ''Site pages and URL paths would be nice as well so we can architect the site properly.''
** Test Days
** BUGS: Stephen, Juan, Aakash
** MUGs (Mozilla User Groups)
*** Focus: Bugzilla queries, triaging, logging, regression finding, etc
** DATA: Sam, Al, Henrik
*** Focus: Metrics, crash analysis, hendrix feedback, bug stats, etc
** CODE: Clint, Tomcat, Martijn, Bob
*** Focus: QA tools, applications, test automation, test development, community projects, etc
** TEST: Marcia, Tracy, Tony
*** Focus: Test case writing, Litmus related stuff, release testing, exploratory testing, etc


* People
General Contact for Questions:
** MoCo QA
* '''Marcia''': Content Creation
** Testers/Members
* '''Tomcat''': Technical Administration
** Users/Fans


* Connect
== Old Stuff ==
** IRC
'''What is QMO?'''
** mozillaZine Forums
* [[QA/Community/QMO_Design/Thinking | Original Thinking]]
** Newsgroups
* [[QA/Community/QMO_Design/Goals | Current Goals]]
** QMO/QA Blog
* [[QA/Community/QMO_Design/Planning | Planning]]
* [[QA/Community/QMO_Design/Branding Brainstorm | Branding Brainstorm]]


'''Tools'''
'''Website Design'''
* Bugzilla
* [[QA/Community/QMO_Design/Navigation | Navigation & Menus]]
* Litmus
* [[QA/Community/QMO_Design/Layout | Layout & Content]]
* Talkback
* [[QA/Community/QMO_Design/UI & Graphics | UI & Graphics]]
* Reporter
* [[QA/Community/QMO_Design/Examples | Inspiration and Examples]]


'''Projects'''
* Litmus Extension
* Talkback Tools & Reporting
* Airbag
* Test Harness


'''Blogroll'''
'''External Docs'''
 
* [[QA/Community/QMO_Design/External Docs/mozilla.org | mozilla.org]]
'''Feedback'''
* [[QA/Community/QMO_Design/External Docs/mozilla wiki | mozilla wiki]]
 
* [[QA/Community/QMO_Design/External Docs/other | Other]]
== '''External Docs''' ==
 
== '''mozilla.org and mozilla wiki Archives''' ==
'''Sites that would be helpful to integrate into QMO'''
* http://www.mozilla.org/newlayout/bugathon.html (sample of what a good bug day page should look like... with plenty of help, bugzilla queries, etc)
* http://www.mozilla.org/quality/help/ (nice list of general info about how to get involved, should be updated and organized for easier browsing)
* http://www.mozilla.org/support/firefox/tips (might be a nice way to get regular users to try "hacking" Firefox and learn more about how things work... for advanced users only)
* http://wiki.flock.com/index.php?title=Verifying_a_bug (needs to be updated to reflect Mozilla community, contributed/maintained by Eli Goldberg)
* http://www.mozilla.org/support/firefox/keyboard (one of many support docs we should probably link to in a general usage FAQ)
* http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day (most of the links in the FAQ section, as well as a general "Bug Day" page)
* http://wiki.mozilla.org/Mozilla_QA (Lots of general information about QA activities, could be updated and organized better)
* http://developer.mozilla.org/en/docs/Bug_Writing_Guidelines (Easy to follow guidelines to make effective bug reports, could link to in a testing FAQ)
* http://wiki.mozilla.org/MozillaQualityAssurance:Triage (work in progress for a newer guide to triaging bugs on BMO)
* http://www.gerv.net/hacking/before-you-mail-gerv.html (need to convert it to before mailing qa doc)
 
'''Sites that need updating and should be added to QMO'''
 
'''Sites that are obsolete and need to be removed from mozilla.org and not added to QMO'''
 
== '''Wiki?''' ==

Latest revision as of 18:19, 12 April 2010

« QA/Community

Current QMO Redesign Project

  • Phase 1: Visual Design (February - March 2008)
  • Phase 2a: Content Creation (May - August 2008)
    • Outline template pages and relevant content
    • Create site sections for assignment
    • Gather QA related content links and resources
    • Review new content
    • Migrate all content to staged QMO site
  • Phase 2b: Drupal Development (June - August 2008)
    • Bidding process in April/May, decided to go with Advomatic.
    • Delay in development process due to lengthy contract negotiation with Advomatic (5/13 - 6/20)
    • Development schedule (Spec Document)
      • Drupal 6 config (July - August)
      • Theme development (August - September)
      • Module development (September)
      • Alpha testing and bug fixing (September)
      • QMO beta release (September - October)

Content & Development links

Here are some links with what's been worked on. (PaulC and Jay)

Staging Sites:

QMO2 Content Creation Assignments

  • Below are the assignment for getting data/docs together from various sources and getting them ready to import/migrate/add to QMO2 when the site is ready. Each group of people should think about what content is relevant for their area and decide where they might want to put it. Site pages and URL paths would be nice as well so we can architect the site properly.
    • BUGS: Stephen, Juan, Aakash
      • Focus: Bugzilla queries, triaging, logging, regression finding, etc
    • DATA: Sam, Al, Henrik
      • Focus: Metrics, crash analysis, hendrix feedback, bug stats, etc
    • CODE: Clint, Tomcat, Martijn, Bob
      • Focus: QA tools, applications, test automation, test development, community projects, etc
    • TEST: Marcia, Tracy, Tony
      • Focus: Test case writing, Litmus related stuff, release testing, exploratory testing, etc

General Contact for Questions:

  • Marcia: Content Creation
  • Tomcat: Technical Administration

Old Stuff

What is QMO?

Website Design


External Docs

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