svn commit: r849900 - in /websites/staging/openoffice/trunk/content: ./ orientation/intro-qa.html

[bu...@apache.org]

Author: buildbot
Date: Fri Feb  8 15:31:45 2013
New Revision: 849900

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/orientation/intro-qa.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Feb  8 15:31:45 2013
@@ -1 +1 @@
-1443733
+1444072

Modified: websites/staging/openoffice/trunk/content/orientation/intro-qa.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/intro-qa.html (original)
+++ websites/staging/openoffice/trunk/content/orientation/intro-qa.html Fri Feb  8 15:31:45 2013
@@ -214,7 +214,7 @@ generally every few weeks, are built in 
 <li>A guide for reporting a new bug: <a href="http://wiki.openoffice.org/wiki/QA/HowToFileIssue">How to file bug</a></li>
 </ul>
 <p>Everyone in QA needs a Bugzilla account, which you can get <a href="https://issues.apache.org/ooo/createaccount.cgi">here</a>.  Once 
-you have a Bugzilla account, you should send a note to the QA list asking to be added to the QA role in 
+you have a Bugzilla account, you should send a note to the QA list asking to be added to the "qa-team" group in 
 Bugzilla.  This will give you some additional permissions in Bugzilla.  Include your Bugzilla login ID in your request.</p>
 <h2 id="easy-qa-task-confirm-new-defect-reports">Easy QA Task: Confirm New Defect Reports</h2>
 <p>Most new volunteers start by reviewing incoming defect reports and attempting to "confirm" them.   The defect reports are 
@@ -225,7 +225,8 @@ in order to turn the raw report into a r
 step, since we'll try to give you easier reports to review at first.</p>
 <p>Here's what to do to confirm a new defect report:</p>
 <ol>
-<li>First, assign the report to yourself by setting your Bugzilla username (your email address) in the "QA Contact" field.</li>
+<li>First, assign the report to yourself by setting your Bugzilla username (your email address) in the "QA Contact" field.  If you are not able to
+add yourself, then send a note to the QA mailing list asking to be added to the "qa-team" group in Bugzilla.</li>
 <li>Then read over the report.  What are they really saying?  Are they reporting a bug?  Asking for a new feature?  Asking a support question?  Just because it is in Bugzilla
  does not mean that it is a defect report.<br />
 </li>