QA/QMO/team pages: Difference between revisions

From MozillaWiki
< QA‎ | QMO
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:


==Content==
==Content==
    What we do
===What we do===
    Brief description of the teams responsiblities/relevant projects
This section is aimed to provide somebody with a general jist of what this team does and what they work on. It should give anyone new a general jist of what is going on.
    Appropriate Links
    Wiki Links


    Live links (where the project exists)
This would include
* Brief description of the teams responsiblities/relevant projects
* Primary source links (documentation, ect.)
* Wiki Links (General background)
* Live links (Active Work)


    How to get involved.
===How to get involved===
This section should include concrete steps to get involved with a specific team. We are looking for links to easy to follow primary sources. Anything that takes too many clicks or is too complicated will not be read by users.


    Per Team
One guideline to think about is can somebody contribute something meaningful in a saturday afternoon?


    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
Things this page should <b>not</b> inclue:
* Handwaving
* General Knowledge Links
** Instructions to "read the wiki"
* Find us on IRC
* Email this person


    Per team pages should go into more specific details about what is unique to that team (ashughes)
Things this page <b>should</b> include:
* Walk through of how to get started with various tasks
** Step by step guide
*** This is a good guide to how to install mozmill. http://quality.mozilla.org/docs/mozmill/getting-started/
** Needs to be thourough enough to be completed without consulting resources not linked to in the walk through.
** Links to primary sources in MDC (eg. How to download and install a new build, start profile manger)


    This section should have concrete steps about how to do something constructive for the team.


    Walk through of how to get started
* Integration Mechanism (Next Steps)
** Talk about how to get involved further
** Refer people to the contact info
** Link to badges so they can learn how they can move from "newbie" status to something higher.
** Use QMO to track integration into the project


    Need to be thourough enough to be completed without consulting resources not linked to in the walk through.
===Upcoming Events===
* Relevant testdays
* Community events


    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)
===Contact Us===


    Some things may be more detailed sub-pages to explain
*Mailing list
 
** Ideally the page that show them how to join the mailing list
    eg. Finding appropriate bugs to test, how to triage them
* IRC
 
** mibbit link to channel
    Somebody should be able to contribute something semi useful on a saturday afternoon
** Names of key people
 
* Emails of key people
    This is not "find us on IRC"
* Team Wiki
 
    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 19:05, 10 June 2011

Team Pages Template

Content

What we do

This section is aimed to provide somebody with a general jist of what this team does and what they work on. It should give anyone new a general jist of what is going on.

This would include

  • Brief description of the teams responsiblities/relevant projects
  • Primary source links (documentation, ect.)
  • Wiki Links (General background)
  • Live links (Active Work)

How to get involved

This section should include concrete steps to get involved with a specific team. We are looking for links to easy to follow primary sources. Anything that takes too many clicks or is too complicated will not be read by users.

One guideline to think about is can somebody contribute something meaningful in a saturday afternoon?

Things this page should not inclue:

  • Handwaving
  • General Knowledge Links
    • Instructions to "read the wiki"
  • Find us on IRC
  • Email this person

Things this page should include:

  • Walk through of how to get started with various tasks
    • Step by step guide
    • Needs to be thourough enough to be completed without consulting resources not linked to in the walk through.
    • Links to primary sources in MDC (eg. How to download and install a new build, start profile manger)


  • Integration Mechanism (Next Steps)
    • Talk about how to get involved further
    • Refer people to the contact info
    • Link to badges so they can learn how they can move from "newbie" status to something higher.
    • Use QMO to track integration into the project

Upcoming Events

  • Relevant testdays
  • Community events

Contact Us

  • Mailing list
    • Ideally the page that show them how to join the mailing list
  • IRC
    • mibbit link to channel
    • Names of key people
  • Emails of key people
  • Team Wiki
Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=QA/QMO/team_pages&oldid=317800"