QA/QMO/team pages: Difference between revisions

From MozillaWiki
< QA‎ | QMO
Jump to navigation Jump to search
(Created page with "Team Pages Template")
 
No edit summary
Line 1: Line 1:
Team Pages Template
=Team Pages Template=
 
==Content==
    What we do
    Brief description of the teams responsiblities/relevant projects
    Appropriate Links
    Wiki Links
 
    Live links (where the project exists)
 
    How to get involved.
 
    Per Team
 
    We should have a generic "bootcamp" style document with how-to videos to get people familiar with practices common to all QA teams and to QA in general
 
    Per team pages should go into more specific details about what is unique to that team (ashughes)
 
    This section should have concrete steps about how to do something constructive for the team.
 
    Walk through of how to get started
 
    Need to be thourough enough to be completed without consulting resources not linked to in the walk through.
 
    Some things can be copy pasted or we can link to other how to's (eg. Download and install a new build, start a new profile)
 
    Some things may be more detailed sub-pages to explain
 
    eg. Finding appropriate bugs to test, how to triage them
 
    Somebody should be able to contribute something semi useful on a saturday afternoon
 
    This is not "find us on IRC"
 
    This is not "Email this person"
 
    Try to knock down portions of work into smaller chunks
 
    What can I contribute if I have 30 minutes of time? 1 hour?
 
    Integration Mechanism
 
    Ideally, once people have completed a few smaller tasks somebody can reach out to them and start transitioning them to a more regular community member
 
    This is where the badges might help. They can move from "newbie" status to something higher.
 
    Use QMO to track integration into the project
 
    Upcoming Events
 
    Relevant testdays (is it possible to filter by team?)
 
    Community events (eg. web qa might have links to upcoming selenium meet up)
 
    Contact Us
 
    Mailing list
 
    IRC
 
    Emai
 
    Team Wiki

Revision as of 17:53, 10 June 2011

Team Pages Template

Content

   What we do
   Brief description of the teams responsiblities/relevant projects
   Appropriate Links
   Wiki Links
   Live links (where the project exists)
   How to get involved.
   Per Team
   We should have a generic "bootcamp" style document with how-to videos to get people familiar with practices common to all QA teams and to QA in general
   Per team pages should go into more specific details about what is unique to that team (ashughes)
   This section should have concrete steps about how to do something constructive for the team.
   Walk through of how to get started
   Need to be thourough enough to be completed without consulting resources not linked to in the walk through.
   Some things can be copy pasted or we can link to other how to's (eg. Download and install a new build, start a new profile)
   Some things may be more detailed sub-pages to explain 
   eg. Finding appropriate bugs to test, how to triage them 
   Somebody should be able to contribute something semi useful on a saturday afternoon
   This is not "find us on IRC"
   This is not "Email this person"
   Try to knock down portions of work into smaller chunks
   What can I contribute if I have 30 minutes of time? 1 hour?
   Integration Mechanism
   Ideally, once people have completed a few smaller tasks somebody can reach out to them and start transitioning them to a more regular community member
   This is where the badges might help. They can move from "newbie" status to something higher.
   Use QMO to track integration into the project
   Upcoming Events
   Relevant testdays (is it possible to filter by team?)
   Community events (eg. web qa might have links to upcoming selenium meet up)
   Contact Us
    Mailing list
    IRC
    Emai
   Team Wiki