incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1202908 [1/9] - in /incubator/ooo/ooo-site/trunk/content/qa: __modules/ css/ images/ issue_handling/ issue_handling/FAQ/ issue_handling/policies/ issue_handling/workflowcharts/ issue_handling/workflowcharts/.inv/ issues/ wwwstaging/ wwwsta...
Date Wed, 16 Nov 2011 22:14:54 GMT
Author: kschenk
Date: Wed Nov 16 22:14:47 2011
New Revision: 1202908

kls -- updated qa area

    incubator/ooo/ooo-site/trunk/content/qa/__modules/left_sidebar_topics.htmlx   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/css/qa.css   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/images/handling_RFEs_overview.gif   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/images/qatrack_menu_logo.gif   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/basic_rules.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/bug_writing_guidelines.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/handling_RFEs.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/index.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/issues.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/policies/regressions.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/pre_submission.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/project_issues.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/submission_gateway.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/.inv/taskhandling_workflow_feature_QA.gif   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/.inv/taskhandling_workflow_feature_implementation.gif   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/.inv/taskhandling_workflow_feature_specification.gif   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/.inv/taskhandling_workflow_issuezilla_confirm.jpg   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/.inv/taskhandling_workflow_issuezilla_fix.jpg   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/.inv/taskhandling_workflow_issuezilla_fix_close.jpg   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/RFE_issues_by_QA.sxd   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/defect_triaging.pdf   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/evaluating_RFEs.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/taskhandling_workflow_feature_QA.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/taskhandling_workflow_feature_implementation.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/taskhandling_workflow_feature_specification.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/taskhandling_workflow_issuetracker_confirm.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/taskhandling_workflow_issuetracker_fix.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/taskhandling_workflow_issuetracker_fix_close.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/workflow_for_RFE_issues_by_QA.gif   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/workflow_for_RFE_issues_by_RFE_engineers.gif   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/css/default.css   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/docs/definitions.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/docs/tools.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/docs/valgrind.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/issue_handling.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izaddcomment.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izaddcomment_thumb.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izattachment.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izattachment_thumb.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izattachmentfile.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izattachmentfile_thumb.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izcomment.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izcomment_thumb.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izcomponent.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izcomponent_thumb.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izconfirmnew.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izconfirmnew_thumb.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izkeyword.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izkeyword_thumb.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izlist.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izlist_thumb.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izpriority.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izpriority_thumb.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izqacontact.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/izqacontact_thumb.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/qalogo.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/thumbs_up.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/images/wink.png   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/index.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/info/events.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/info/news.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/izhelperlinks/members.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/izhelperlinks/thismonth.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/izhelperlinks/thismonthnew.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/join/izprivileges.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/join/mailinglists.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/join/quickref.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/join/useraccounts.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/join/whereishelp.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/APITeamsite/ooQA-TeamAPI.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/APITeamsite/ooQA-TeamAPILinks.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/APITeamsite/ooQA-TeamAPIMS.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/APITeamsite/ooQA-TeamAPIMisc.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/APITeamsite/ooQA-TeamAPIResp.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/APITeamsite/ooQA-TeamAPIToDo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomation.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationLinks.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationMS.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationMisc.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationResp.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationToDo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/CalcTeamsite/ooQA-TeamCalc.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/CalcTeamsite/ooQA-TeamCalcLinks.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/CalcTeamsite/ooQA-TeamCalcMS.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/CalcTeamsite/ooQA-TeamCalcMisc.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/CalcTeamsite/ooQA-TeamCalcResp.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/CalcTeamsite/ooQA-TeamCalcToDo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabaseLinks.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabaseMS.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabaseMisc.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabaseResp.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabaseToDo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/FrameworkTeamsite/ooQA-TeamFramework.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/FrameworkTeamsite/ooQA-TeamFrameworkLinks.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/FrameworkTeamsite/ooQA-TeamFrameworkMS.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/FrameworkTeamsite/ooQA-TeamFrameworkMisc.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/FrameworkTeamsite/ooQA-TeamFrameworkResp.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/FrameworkTeamsite/ooQA-TeamFrameworkToDo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/GraphicsTeamsite/ooQA-TeamGraphics.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/GraphicsTeamsite/ooQA-TeamGraphicsLinks.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/GraphicsTeamsite/ooQA-TeamGraphicsMS.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/GraphicsTeamsite/ooQA-TeamGraphicsMisc.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/GraphicsTeamsite/ooQA-TeamGraphicsResp.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/GraphicsTeamsite/ooQA-TeamGraphicsToDo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/Local-DocuTeamsite/ooQA-TeamLocal-Docu.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/Local-DocuTeamsite/ooQA-TeamLocal-DocuCountry.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/Local-DocuTeamsite/ooQA-TeamLocal-DocuLinks.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/Local-DocuTeamsite/ooQA-TeamLocal-DocuMS.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/Local-DocuTeamsite/ooQA-TeamLocal-DocuMisc.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/Local-DocuTeamsite/ooQA-TeamLocal-DocuResp.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/Local-DocuTeamsite/ooQA-TeamLocal-DocuToDo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/SpecialTeamsite/ooQA-TeamSpecial.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/WriterTeamsite/ooQA-TeamWriter.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/WriterTeamsite/ooQA-TeamWriterLinks.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/WriterTeamsite/ooQA-TeamWriterMS.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/WriterTeamsite/ooQA-TeamWriterMisc.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/WriterTeamsite/ooQA-TeamWriterResp.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/WriterTeamsite/ooQA-TeamWriterToDo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/dba.css   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/index.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/ooQA-IssueHandlingOverview.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/ooQA-IssueRules.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/ooQA-JoinQA.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/ooQA-ManualTesting.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/ooQA-Misc.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/ooQA-ReportBugs.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/ooQA-TeamDatabase.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/ooQA-TeamDatabaseMS.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/ooQA-TeamDatabaseResp.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/ooQA-TeamDatabaseToDo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/tasks/basic_rules.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/tasks/bug_writing_guidelines.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/tasks/pre_submission.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/tasks/project_issues.html   (with props)
    incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/tasks/quickstart.html   (with props)

Added: incubator/ooo/ooo-site/trunk/content/qa/__modules/left_sidebar_topics.htmlx
--- incubator/ooo/ooo-site/trunk/content/qa/__modules/left_sidebar_topics.htmlx (added)
+++ incubator/ooo/ooo-site/trunk/content/qa/__modules/left_sidebar_topics.htmlx Wed Nov 16 22:14:47 2011
@@ -0,0 +1,31 @@
+<dl id="linksbox" class="navgroup"> 
+      <dt><a href="">QA links</a></dt>
+  <dd>
+  <ul>
+<li style="margin: 0 0 0 0"><a href="">&raquo;How to start </a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; Issue handling</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; Report bugs</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; Manual Testing</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; Join QA Team</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; Team Sites</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; Misc</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; Dev Builds</a></li>
+  </ul>
+  </dd>
+<dl id="toolsbox" class="navgroup">
+      <dt>Project tools</dt>
+  <dd>
+  <ul>
+<li style="margin: 0 0 0 0"><a href="">&raquo; Enter issues</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; Query issues</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; Track issues</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; EIS</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; QATrack</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; QUASTe</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; WIKI</a></li>
+<li style="margin: 0 0 0 0"><a href="">&raquo; TCM</a></li>
+  </ul>
+  </dd>

Propchange: incubator/ooo/ooo-site/trunk/content/qa/__modules/left_sidebar_topics.htmlx
    svn:executable = *

Added: incubator/ooo/ooo-site/trunk/content/qa/css/qa.css
--- incubator/ooo/ooo-site/trunk/content/qa/css/qa.css (added)
+++ incubator/ooo/ooo-site/trunk/content/qa/css/qa.css Wed Nov 16 22:14:47 2011
@@ -0,0 +1,34 @@ tr.MainTableHeader
+    background-color: #003399;
+    color: #ffffff;
+    font-weight:bold;
+    font-family:Helvetica;
+    text-align:center;
+    font-size:large;
+ tr.InnerTableHeader
+    background-color: #BBBBBB;
+    color: #000000;
+    font-weight:bold;
+    font-family:Helvetica;
+ tr.TableRow
+    background-color: #f0f0f0;
+    font-family:Helvetica;
+ td.RowHeader
+    font-weight:bold;
+    border:solid 1px !important;

Propchange: incubator/ooo/ooo-site/trunk/content/qa/css/qa.css
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/qa/images/handling_RFEs_overview.gif
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/qa/images/handling_RFEs_overview.gif
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/qa/images/qatrack_menu_logo.gif
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/qa/images/qatrack_menu_logo.gif
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/basic_rules.html
--- incubator/ooo/ooo-site/trunk/content/qa/issue_handling/basic_rules.html (added)
+++ incubator/ooo/ooo-site/trunk/content/qa/issue_handling/basic_rules.html Wed Nov 16 22:14:47 2011
@@ -0,0 +1,207 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+  <meta http-equiv="content-type"
+ content="text/html; charset=ISO-8859-1">
+  <title>Basic IssueTracker rules</title>
+<div class="app">
+<h1>Basic IssueTracker rules</h1>
+<h3>Why you should read this</h3>
+<p> Imagine how many people later on will read your issue (means the
+issue which you submitted, or which you participated in) </p>
+  <li> community members who performe triage on defects</li>
+  <li> developers who finally fix the defect </li>
+  <li> sometimes developers who need to do preliminary work</li>
+  <li> QA engineer(s) who needs to verify the fix</li>
+  <li> everybody who has the same problem and tries to understand
+whether </li>
+  <ul>
+    <li> <span style="font-style: italic;">your</span> defect also
+describes <span style="font-style: italic;">his/her</span> problem.</li>
+    <li> or whether your issue is one they like to vote for</li>
+  </ul>
+  <li> possibly a user experience team member evaluating a feature
+  <li> possibly a release team member evaluating whether the defect is
+important enough to be included in some maintenance update such as
+You see, there are a lot of&nbsp; people who may read what you wrote.
+Thus, the majority of the rules below focuses on making <span
+ style="font-style: italic;">reading</span> easier: Though they
+sometimes take you some little time to follow, they often save others a
+<span style="font-style: italic;">lot</span> of time later on.
+<p> So please, not only when you submit new issues, but also when you
+add comments to existing issues, try to help others by obeying these
+simple rules.<br/>
+Since not obeying them makes defect handling more difficult (sometimes <span
+ style="font-style: italic;">much</span> more difficult), people may
+tend to not deal with your issues until they are in a shape to
+reasonably do so. </p>
+<h3>The rules</h3>
+<p> For those of you who like it short and simple: </p>
+  <li style="font-weight: bold;"> <a href="#one_per_issue">One problem - One issue</a></li>
+  <li style="font-weight: bold;"> <a href="#summary">Provide a meaningful summary</a></li>
+  <li style="font-weight: bold;"> <a href="#reproducibility">Provide step-by-step descriptions</a></li>
+  <li style="font-weight: bold;"> <a href="#bugdoc">Provide sample documents, if possible</a></li>
+  <li style="font-weight: bold;"> <a href="#attachments">Use Attachments where possible</a></li>
+  <li style="font-weight: bold;"> <a href="#complete">Put all relevant information into the issue</a></li>
+<h4><a name="one_per_issue"></a>One problem - One issue</h4>
+<p> When you report a problem, please submit <span
+ style="text-decoration: underline;">one issue per problem</span>.
+There are various reasons for this, amongst them: </p>
+  <li> The more crowded an issue is, the more likely is it that some
+problems may get lost over time.</li>
+  <li> Different problems are most likely to be handled by different
+people (both in engineering, where the problem is fixed, and in QA,
+where it's verified). The more problems you put into the issue, the
+more difficult is this issue to handle for all involved parties.</li>
+In particular, if you're going to write sentences like "Besides this, I
+noticed that ...." or "There are several problems with....", then
+please seriously ask yourself whether you should submit multiple issues
+instead of a single one.<br/>
+If you don't follow this rule, be prepared for people asking you to
+split up your issue.
+<h4><a name="summary"></a>Provide a meaningful summary</h4>
+<p> A lot of people have to deal with a high number of issues on a
+regular basis. Usually, this happens with generating reports about
+issues, where the summary of all issues, plus some additional data, is
+displayed. Thus, the summary of an issue is of very high importance: If
+properly chosen, it allows to<br/>
+  <li> easily <span style="text-decoration: underline;">recognize</span>
+an issue in a list of dozens of others</li>
+  <li> <span style="text-decoration: underline;">find</span> an issue.
+Since duplicate issues are draining a lot of work from engaged
+community members, we always ask people to look whether the problem,
+which they are going to submit as issue, is already known and reported.
+Of course this works best if the summaries of the existing issues are
+as descriptive as possible.</li>
+  <li> <span style="text-decoration: underline;">judge the importance</span>
+of an issue. "Spreadsheet problem" is less likely to be handled
+appropriately than "Spreadsheet: Data loss when ...." or "Label X in
+dialog Y has a wrong offset (2 pixels)"</li>
+Thus, please avoid summaries like "Big Bug in" or
+"Impress problem" - they are of no real help, and force people to waste
+time to actually browse to the issue (instead of seeing it in a report)
+to see what it is about.<br/>
+<h4><a name="reproducibility"></a>Provide step-by-step descriptions</h4>
+<p> You, as the submitter of a problem, know exactly what you were
+doing when you were hit by the problem. However, most other people
+probably don't. For instance, they may have a completely different
+workflow for doing the same things you are doing. </p>
+<p> Even an phrasing as innocent as "format the text as bold" bears the
+potential for a misunderstanding: You can get a bold text by assigning
+a style to it, by selecting it and pressing the respective button in
+the toolbox, by choosing "<span style="font-family: monospace;">Style|Bold</span>"
+from the context menu, by choosing "<span
+ style="font-family: monospace;">Format|Character</span>" from the menu
+or "<span style="font-family: monospace;">Character</span>" from the
+context menu and then doing the change in the dialog. Thus, a problem
+description such as "When I try to format the text as bold crashes" is of nearly no use, since it <span
+ style="font-style: italic;">forces</span> other people to ask back
+what you meant. </p>
+<p> This may be a trivial example, and you could argue that other
+people can simply try, and then they will eventually encounter the
+problem and thus know what you meant. But, there are reasons against
+  <li> Though the problem may seem simple to you, there may be deeper
+reasons which prevent others from trying. For instance, it may crash
+only if you customized the "<span style="font-family: monospace;">Bold</span>"
+icon into a non-standard toolbox. In such a case, people will try for
+no avail, without encountering your problem at all, and thus waste time.<br/>
+  </li>
+  <li> Writing down <span style="font-style: italic;">exactly</span>
+what you did costs you some time <span style="font-style: italic;">once</span>,
+but <span style="font-style: italic;">every</span> reader (there may
+be numerous during the lifetime of an issue!) needs time for guessing
+and trying. It's more efficient if you do it, and QA and engineering
+can concentrate on fixing the problem, instead of performing triage on it.</li>
+  <li> There are a lot of scenarios where the set of possibility is
+much larger. Formatting a text as bold may be simple and easy (though
+you've already seen that there are at least 5 ways to do so), but other
+tasks may require more steps which <span style="font-style: italic;">you</span>
+implicitly know, but <span style="font-style: italic;">your reader</span>
+You may be tempted to consider it stupid to write a description like<br/>
+  <li> open a new writer document</li>
+  <li> enter some arbitrary text</li>
+  <li> select the whole text via "<span style="font-family: monospace;">Edit|Select
+  <li> from the context menu of the text, chose "<span
+ style="font-family: monospace;">Style|Bold</span>"</li>
+  <li> =&gt; crashes</li>
+Indeed there may be cases where this level of detail is
+superfluous. But believe us, more often than not, it in the final
+consequences saves more time than it takes.
+<p> Please always be aware that often enough, the reader of your issue
+description does not have the same background, with respect to the
+particular task you're doing, that you yourself have. </p>
+<h4><a name="bugdoc"></a>Provide sample documents, if possible</h4>
+<p> If there is a problem with a particular document, then attach it.
+This most often allows people to really easily reproduce your problem
+by simply opening the attached document.<br/>
+<p> If the description how to reproduce a defect (see <a
+ href="#reproducibility">Provide step-by-step descriptions</a>) exceeds
+a certain limit, ask yourself whether you can submit the <span
+ style="font-style: italic;">result</span> of the description as sample
+document, and attach it to the issue.<br/>
+<p> Oh, and one thing: If there is a problem on page 3 of your
+1000-page diploma thesis, then please first try if the problem also
+occurs if you strip all pages except the third one. If so, then please
+simply attach the stripped version of the document, not all 1000 pages
+.... </p>
+<h4><a name="attachments"></a>Use attachments where possible</h4>
+<p> Don't paste large files into the description. For instance, if
+you're asked to provide a stack of a crash, copy this stack into a
+file, then <span style="text-decoration: underline;">attach</span>
+this file. If you have some Basic macro or Java code which triggers a
+problem, copy it into a separate file, and <span
+ style="text-decoration: underline;">attach</span> this file. </p>
+<p> The reason here is simple: A 3-pager within the description of an
+issue makes reading the issue really difficult. Everybody who wants to
+get an impression of the issue needs to scan through a lot of
+information which, though definitely important, is of only peripheral
+interest for them at the moment. </p>
+<h4><a name="complete"></a>Put all relevant information into the issue</h4>
+<p>Don't use (only) links to refer to the bug descriptions. Links tend to become outdated
+over time, so if half a year later, somebody looks at your issue, it has become meaningless.
+<p>If there is some external resource describing your problem - fine, link it! But don't rely
+on links as the <em>only</em> mean for bug descriptions - copy the information which is
+necessary to reproduce the problem into the issue.</p>
+The author of the original document is <a
+ href="">Frank Sch&ouml;nheit</a>. Constructive
+<a href="">feedback is welcome</a>. You may
+also consider visiting <a href=""> the
+mailing list</a> dedicated to discussing issue handling.
+Last change: $Date: 2008/06/20 08:20:33 $ / $Author: fs $<br/>
+<div> </div>

Propchange: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/basic_rules.html
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/bug_writing_guidelines.html
--- incubator/ooo/ooo-site/trunk/content/qa/issue_handling/bug_writing_guidelines.html (added)
+++ incubator/ooo/ooo-site/trunk/content/qa/issue_handling/bug_writing_guidelines.html Wed Nov 16 22:14:47 2011
@@ -0,0 +1,215 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+  <meta http-equiv="content-type" content="text/html; charset=UTF-8">
+  <title>Issue Writing Guidelines</title>
+<div class="app">
+<h2>Issue Writing Guidelines</h2>
+<p>$Date: 2007/02/23 11:26:39 $ </p>
+<h4>Consider the rules<br>
+<p>We strongly encourage you to read the <a href="basic_rules.html">Basic
+IssueTracker rules</a> - for those who work with IssueTracker on a
+day-by-day base, they have proven to <span style="font-style: italic;">immensely</span>
+reduce their work. It's really easy for you to report issues in a way
+which cost all others a lot of time, but if you invest a little more
+effort in the beginning, you save others a lot thereof afterwards.<br>
+<p>Thus, if you're new to's IssueTracker, please <a
+ href="basic_rules.html"> read the rules</a>. And, of course, please
+follow them :-), to make our all work easier, so we can concentrate on
+improving the product, instead of wasting time with bad issue reports.</p>
+<p>And, please don't be offended if we ask you to follow <a
+ href="basic_rules.html"> some rules</a>: Simply put, the more
+effectively you report an issue, the more likely an engineer will
+actually fix it, and this is what we all are interested in. </p>
+<h4>How to Write a Useful Issue Report</h4>
+  <p>Useful issue reports are ones that get issues fixed. A useful
+issue report normally has two qualities:</p>
+  <li> <b>Reproducible.</b> If an engineer can't see it or
+conclusively prove that it exists, the engineer will probably stamp it
+"WORKSFORME" or "INVALID", and move on to the next issue. Every detail
+you can provide helps. </li>
+  <br>
+  <li> <b>Specific.</b> The quicker the engineer can isolate the issue
+to a specific problem, the more likely it'll be expediently fixed. (If
+a programmer or tester has to decipher an issue, they spend more time
+cursing the submitter than fixing or testing the problem.) </li>
+<blockquote> Let's say the application you're testing is a spreadsheet
+application. You crash at when you open the file foo.sxc, and want to
+write up an issue report: </blockquote>
+<blockquote> <b>Bad:</b> "My spreadsheet crashed when I tried to open
+a document. I think it contained a chart. My computer uses Windows. I
+think that this is a really bad problem and you should fix it now. By
+the way, your icons really suck. Nobody will use your software if you
+keep those ugly icons. Oh, and my grandmother's has a problem with the
+word processor. Nothing works right, either. Good luck." <br>
+  <br>
+  <b>Good:</b> "I crashed each time when I opened the attached
+spreadsheet document using the 10.13.00 build on a Win NT 4.0 (Service
+Pack 5) system. I also rebooted into Linux (RedHat 6.2), and reproduced
+this problem using the 10.13.00 Linux build.
+  <p>When I removed the chart from the document I was able to load it
+without any trouble." </p>
+<h4>How to enter a useful Issue Report into IssueTracker</h4>
+<blockquote> In order to file an Issue, you must be a registered user
+of Registering is easy: simply click on the "Join" link
+in the left navbar and follow the instructions. It takes all of a few
+minutes. If you are a registered user, click on the "My Issues" link in
+the left navbar or on the <a href="project_issues.html" target="_blank">"Bugs
+and Issues"</a> link on the navbar. The latter is a more comprehensive
+page which provides a explanation of IssueTracker and also has some
+useful IssueTracker links, such as a query link.
+  <p> Go to the <a href=""
+ target="_blank">IssueTracker Query Page</a> to determine whether the
+defect you've discovered is a known issue and has already been
+reported. (If your issue is the 37th duplicate of a known issue, you're
+more likely to annoy the engineer. Annoyed engineers fix fewer issues.)
+  </p>
+  <p>Next, be sure that you've reproduced your issue using a recent
+build. (Engineers tend to be most interested in problems afflicting the
+code base that they're actively working on, rather than those in a code
+base that's hundreds of issue fixes obsolete.)<br>
+  <br>
+If you've discovered a new issue using a current build, report it in
+IssueTracker: </p>
+  <ol>
+    <li> If you're not already logged in, please enter your username
+&amp; password in the appropriate filds at the top of this page (or any
+other page on this site)</li>
+    <li> From your IssueTracker main page, choose "Enter a new issue".</li>
+    <li> Select the product that you've found an issue in.</li>
+  </ol>
+  <p>regarding 2., there is a link "File Issue" as well, accessible
+from the "My Pages"-tab (When logging in you're automatically directed
+to "My Pages", you can then access IssueTracker using the links in the
+"My Tools" box on the left side of your screen)</p>
+<h4>Now, fill out the form. Here's what it all means:</h4>
+<blockquote> <i>Where did you find the issue? </i></blockquote>
+<blockquote> <b>Product: In which product did you find the issue?</b><br>
+You just filled this out on the last page. </blockquote>
+<blockquote> <b>Version: In which product version did you find the
+If applicable. </blockquote>
+<blockquote> <b>Component: In which component does the issue exist?</b><br>
+IssueTracker requires that you select a component to enter an issue.
+(If they all look meaningless, click on the Component link, which links
+to descriptions of each component, to help you make the best choice.) </blockquote>
+<blockquote> <b><a
+ href="">
+Platform</a>:&nbsp;On which hardware platform did you find this issue? </b>(e.g.,
+Sun, PC)<br>
+If you know the issue happens on all hardware platforms, choose 'All'.
+Otherwise, select the platform that you found the issue on, or "Other"
+if your platform isn't listed. </blockquote>
+<blockquote> <b>OS: On which Operating System (OS) did you find this
+issue?</b> (e.g. Linux, Windows NT)<br>
+If you know the issue happens on all OSs, choose 'All'. Otherwise,
+select the OS that you found the issue on, or "Other" if your OS isn't
+listed. </blockquote>
+<blockquote> <br>
+  <i>How important is the issue? </i></blockquote>
+<blockquote> <b><a
+ href="">
+Issue Type</a>: Is this a defect, enhancement, feature-request, task or
+This item defaults to 'defect'. (To determine the most appropriate type
+of issue, click on the Issue Type link for a full explanation of each
+choice.) </blockquote>
+<blockquote> <b><a
+ href="">
+Priority</a>: How much does the problem affect the product's <em>overall</em>
+Developers use this field as <em>one</em> measure how to priorize
+their work.<br>
+This item defaults to '3'. 1 is the highest (rarely used), 5 the lowest
+Please read the <a
+ href="">definition
+of issue priorities</a> carefully before attempting to use P2 or even
+<blockquote> <br>
+  <i>Who will be following up on the issue?</i> </blockquote>
+<blockquote> <b><a
+ href="">
+Assigned To</a>: Which engineer should be responsible for fixing this
+IssueTracker will automatically assign the issue to a default engineer
+upon submitting an issue report; the text box exists to allow you to
+manually assign it to a different engineer. (To see the list of default
+engineers for each component, click on the Component link.) </blockquote>
+<blockquote> <b>Cc: Who else should receive e-mail updates on changes
+to this issue?</b><br>
+List the full e-mail addresses of other individuals who should receive
+an e-mail update upon every change to the issue report. You can enter
+as many e-mail addresses as you'd like; e-mail addresses must be
+separated by commas, with no spaces between the addresses. </blockquote>
+<blockquote> <br>
+  <i>What else can you tell the engineer about the issue? </i></blockquote>
+<blockquote> <b>URL: On what URL did you discover this issue?</b><br>
+If you encountered the issue on a particular URL, please provide it
+(or, them) here. </blockquote>
+<blockquote> <b>Summary:</b> <b>How would you describe the issue, in
+approximately 60 or fewer characters?</b><br>
+A good summary should <u>quickly and uniquely identify an issue report</u>.
+Otherwise, developers cannot meaningfully query by issue summary, and
+will often fail to pay attention to your issue report when reviewing a
+10 page issue list.<br>
+  <br>
+A summary of "Abort trying to install on RedHat 7.0, Kernel 2.2.14" is
+a useful title. "Software fails" or "install problem" would be examples
+of a bad title. </blockquote>
+<blockquote> <br>
+  <b>Description: What else can you tell the engineer about this issue?</b><br>
+Please provide as detailed of a problem diagnosis in this field as
+possible. A precise step-by-step description is the best way to do it.<br>
+For crashing issues it might help to have additional information in
+case you're able to provide that:</blockquote>
+  <b><a href="">Target
+Milestone</a>:</b> Think of it as a deadline; targets are "not
+determined" or "next build"--for most issues, stipulate "not
+  <ul>
+  </ul>
+  <p><strong>Attachments.</strong><em> </em>It may be the case you
+need to add an attachment(s) to an Issue, either the one you file or
+another one. You can do it; the limit is 10MB, but please keep any
+attachment small, as most people use 56K connections. Attaching a file
+to an issue is a two-step procedure and is not obvious. You must first
+submit the issue or locate the issue to which you wish to attach the
+file. Then, you can add the file as an attachment to that issue. There
+will be a link in the issue body that reads: </p>
+  <blockquote> Create a new attachment (proposed patch, testcase, etc.)</blockquote>
+  <p> <strong>Note</strong>: You cannot add files
+natively. They must be added as "binary" files. This is a temporary
+problem. </p>
+  <p> Hints: Reduce the size of your file as much as possible. And, if
+you are uploading an HTML document, be sure to compress it first (Zip
+or tar it), otherwise it gets corrupted when others try to download it.
+  </p>
+  <p>You're done! After double-checking your entries for any possible
+errors, press the "Commit" button, and your issue report will now be in
+the IssueTracker database.<br>
+  </p>
+  <hr>
+  <p>(These Bug Writing Guidelines were originally written for Mozilla
+by <a href=""> <b>Eli Goldberg</b></a>.
+Thanks to Claudius Gayle, Peter Mock, Chris Pratt, Louis Suarez-Potts,
+Tom Schutter, and Chris Yeh for contributing to this document.
+Constructive suggestions and feedback is welcome. In this case just
+post your suggestions to the <a
+ href="">dev@qa</a>
+mailing list.) </p>

Propchange: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/bug_writing_guidelines.html
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/
--- incubator/ooo/ooo-site/trunk/content/qa/issue_handling/ (added)
+++ incubator/ooo/ooo-site/trunk/content/qa/issue_handling/ Wed Nov 16 22:14:47 2011
@@ -0,0 +1,389 @@
+#!/usr/bin/perl -w
+%toplevels = ( 'api' => ['api','API','jsc'],
+          'dba' => ['Database%20access','Database Access','oj'],
+          'documentation' => ['documentation','Documentation','kcarr'],
+          'external' => ['external','External Sources','mh'],
+          'framework' => ['framework','Application Framework','mba'],
+          'graphics' => ['Drawing','Graphics Applications','ka'],
+          'gsl' => ['gsl','Graphic System Layer (GSL)','pl'],
+          'installation' => ['Installation','Installation','is'],
+          'l10n' => ['l10n','Localization and Internationalization (L10N/I18N)','pjanik'],
+          'porting' => ['porting','Porting','mh'],
+          'qa' => ['qa', 'Quality Assurance (QA)','ja'],
+          'sc' => ['Spreadsheet','Spreadsheet','nn'],
+          'script' => ['framework&subcomponent=scripting','Scripting Engines','kr'],
+          'sw' => ['Word%20processor','Word Processing','ama'],
+          'tools' => ['tools','Tools','mh'],
+          'ucb' => ['ucb','Universal Content Broker (UCB)','mhu'],
+          'udk' => ['udk','UNO Development Kit (UDK)','kr'],
+          'ui'  => ['ui','User Interface Design','os'],
+          'util' => ['framework','Utilities','cd'],
+          'xml' => ['xml','XML','mba']
+	     );
+%allmodules = (
+	       'accessibility' => ['gsl/accessibility', ''],
+	       'afms' => ['external/afms', 'pl'],
+               'agg' => ['external/agg', ''],
+               'animations' => ['graphics/animations', 'thb'],
+               'apache-commons' => ['external/apache-commons', ''],
+               'apple_remote' => ['gsl/apple_remote', ''],
+	       'autodoc' => ['tools/autodoc', ''],
+	       'automation' => ['util/automation', 'gh'],
+	       'avmedia' => ['graphics/avmedia', ''],
+	       'basctl' => ['script/basctl', ''],
+	       'basebmp' => ['gsl/basebmp', ''],
+	       'basegfx' => ['graphics/basegfx', 'thb'],
+	       'basic' => ['script/basic', ''],
+	       'bean' => ['api/bean', ''],
+	       'beanshell' => ['external/beanshell', ''],
+	       'berkeleydb' => ['external/berkeleydb', ''],
+	       'binfilter' => ['framework/binfilter', ''],
+	       'bitstream_vera_fonts' => ['external/addons/bitstream_vera_fonts', ''],
+	       'boost' => ['external/boost', ''],
+	       'bridges' => ['udk/bridges', ''],
+	       'cairo' => ['external/cairo', 'thb'],
+	       'canvas' => ['gsl/canvas', 'thb'],
+	       'chart2' => ['graphics/chart2', 'iha'],
+	       'cli_ure' => ['udk/cli_ure', ''],
+	       'codemaker' => ['udk/codemaker', ''],
+	       'comphelper' => ['util/comphelper', 'fs'],
+	       'configmgr' => ['util/configmgr', 'sb'],
+	       'configure' => ['tools/config_office', 'rene'],
+	       'connectivity' => ['dba/connectivity', ''],
+	       'cosv' => ['tools/cosv', ''],
+	       'cppcanvas' => ['gsl/cppcanvas', 'thb'],
+	       'cppu' => ['udk/cppu', ''],
+	       'cppuhelper' => ['udk/cppuhelper', ''],
+	       'cppunit' => ['external/cppunit', ''],
+	       'cpputools' => ['udk/cpputools', ''],
+	       'crashrep' => ['porting/crashrep', ''],
+	       'cui' => ['graphics/cui', ''],
+	       'curl' => ['external/curl', ''],
+	       'dbaccess' => ['dba/dbaccess', ''],
+	       'default_images' => ['ui/default_images', ''],
+	       'desktop' => ['framework/desktop', ''],
+	       'dictionaries' => ['external/addons/dictionaries', ''],
+	       'dmake' => ['tools/dmake', ''],
+	       'drawinglayer' => ['graphics/drawinglayer', ''],
+	       'dtrans' => ['gsl/dtrans', ''],
+	       'editengine' => ['graphics/editengine', 'tl'],
+	       'embeddedobj' => ['framework/embeddedobj', ''],
+	       'embedserv' => ['framework/embedserv', ''],
+	       'epm' => ['external/epm', ''],
+	       'eventattacher' => ['util/eventattacher', 'ab'],
+	       'expat' => ['external/expat', ''],
+	       'extensions' => ['util/extensions', 'mh'],
+	       'external' => ['util/external', 'mh'],
+	       'external_images' => ['external/external_images', ''],
+	       'extras' => ['installation/extras', ''],
+	       'fileaccess' => ['util/fileaccess', 'mav'],
+	       'filter' => ['framework/filter', ''],
+	       'fondu' => ['external/fondu', ''],
+	       'forms' => ['gsl/forms', ''],
+	       'formula' => ['sc/formula', ''],
+	       'fpicker' => ['gsl/fpicker', 'pl'],
+	       'framework' => ['framework/framework', ''],
+	       'goodies' => ['graphics/goodies', ''],
+	       'graphite' => ['external/graphite', 'hdu'],
+               'helpcontent2' => ['documentation/helpcontent2', ''],
+	       'hsqldb' => ['external/hsqldb', 'oj'],
+	       'hunspell' => ['external/hunspell', 'nemeth'],
+	       'hwpfilter' => ['sw/hwpfilter', ''],
+	       'hyphen' => ['external/hyphen', 'nemeth'],
+	       'i18npool' => ['l10n/i18npool', 'er'],
+	       'i18nutil' => ['l10n/i18nutil', 'er'],
+	       'icc' => ['external/icc', 'pl'],
+	       'icu' => ['external/icu', 'er'],
+	       'idl' => ['framework/idl', ''],
+	       'idlc' => ['udk/idlc', ''],
+	       'instsetoo_native' => ['installation/instsetoo_native', ''],
+	       'io' => ['util/io', 'sb'],
+	       'javainstaller2' => ['installation/javainstaller2', ''],
+	       'javaunohelper' => ['udk/javaunohelper', ''],
+	       'jfreereport' => ['external/jfreereport', ''],
+	       'jpeg' => ['external/jpeg', ''],
+	       'jurt' => ['udk/jurt', ''],
+	       'jvmaccess' => ['udk/jvmaccess', ''],
+	       'jvmfwk' => ['udk/jvmfwk', 'jl'],
+               'l10n' => ['l10n/l10n', ''],
+               'libegg' => ['external/libegg', 'mmeeks'],
+               'libtextcat' => ['external/libtextcat', ''],
+               'libwpd' => ['external/libwpd', 'fridrich_strba'],
+               'libxml2' => ['external/libxml2', ''],
+               'libxmlsec' => ['external/libxmlsec', 'jl'],
+               'libxslt' => ['external/libxslt', ''],
+               'lingucomponent' => ['lingucomponent', ''],
+	       'linguistic' => ['sw/linguistic', ''],
+               'lpsolve' => ['external/lpsolve', ''],
+               'lucene' => ['external/lucene', ''],
+	       'MathMLDTD' => ['external/MathMLDTD', ''],
+	       'migrationanalysis' => ['qa/qadevOOo', ''],
+	       'moz' => ['external/moz', ''],
+	       'neon' => ['external/neon', ''],
+	       'np_sdk' => ['external/np_sdk', ''],
+	       'nss' => ['external/nss', 'jl'],
+	       'o3tl' => ['util/o3tl', 'thb'],
+	       'odk' => ['api/odk', ''],
+	       'offapi' => ['api/offapi', ''],
+	       'officecfg' => ['util/officecfg', 'sb'],
+	       'offuh' => ['api/offuh', ''],
+	       'ooo_custom_images' => ['ui/ooo_custom_images', ''],
+	       'oovbaapi' => ['api/oovbaapi', 'npower'],
+	       'oox' => ['xml/oox', 'dr'],
+	       'openssl' => ['external/openssl', ''],
+	       'package' => ['xml/package', 'mav'],
+	       'packimages' => ['installation/packimages', ''],
+	       'padmin' => ['gsl/padmin', ''],
+               'postprocess' => ['installation/postprocess', ''],
+	       'psprint_config' => ['external/psprint_config', ''],
+	       'python' => ['external/python', ''],
+	       'pyuno' => ['udk/pyuno', 'jbu'],
+	       'qadevOOo' => ['qa/qadevOOo', ''],
+	       'rdbmaker' => ['udk/rdbmaker', ''],
+	       'readlicense_oo' => ['installation/readlicense', ''],
+	       'redland' => ['external/redland', ''],
+	       'regexp' => ['external/regexp', ''],
+	       'registry' => ['udk/registry', ''],
+	       'remotebridges' => ['udk/remotebridges', ''],
+	       'reportbuilder' => ['dba/reportbuilder', ''],
+	       'reportdesign' => ['dba/reportdesign', ''],
+	       'rhino' => ['external/rhino', ''],
+	       'ridljar' => ['udk/ridljar', ''],
+	       'rsc' => ['gsl/rsc', ''],
+	       'sal' => ['porting/sal', 'sb'],
+	       'salhelper' => ['udk/salhelper', ''],
+	       'sane' => ['external/sane', ''],
+	       'sax' => ['xml/sax', ''],
+	       'saxon' => ['external/saxon', ''],
+	       'sc' => ['sc/sc', ''],
+	       'scaddins' => ['sc/scaddins', ''],
+	       'sccomp' => ['sc/sccomp', ''],
+	       'scp2' => ['installation/scp2', ''],
+	       'scripting' => ['framework/scripting', 'kr'],
+	       'sd' => ['graphics/sd', ''],
+	       'sdext' => ['graphics/sdext', ''],
+	       'setup_native' => ['installation/setup_native', ''],
+	       'sfx2' => ['framework/sfx2', ''],
+	       'shell' => ['gsl/shell', ''],
+	       'slideshow' => ['graphics/slideshow', 'thb'],
+	       'smoketestoo_native' => ['installation/smoketestoo_native', ''],
+	       'soldep' => ['tools/soldep', ''],
+	       'solenv' => ['tools/solenv', ''],
+	       'soltools' => ['tools/soltools', ''],
+	       'sot' => ['util/sot', 'mav'],
+	       'splitbuild' => ['tools/splitbuild', ''],
+	       'starmath' => ['sw/starmath', ''],
+	       'stax' => ['external/stax', ''],
+	       'stlport' => ['external/stlport', ''],
+	       'stoc' => ['udk/stoc', ''],
+	       'store' => ['ucb/store', ''],
+	       'svl' => ['util/svl', 'cd'],
+	       'svtools' => ['util/svtools', 'cd'],
+	       'svx' => ['graphics/svx', ''],
+	       'sw' => ['sw/sw', ''],
+	       'swext' => ['sw/swext', ''],
+	       'sysui' => ['gsl/sysui', ''],
+               'test' => ['qa/test', 'sb'],
+	       'testautomation' => ['qa/testautomation', ''],
+	       'testshl2' => ['tools/testshl2', ''],
+	       'testtools' => ['udk/testtools', ''],
+	       'tomcat' => ['external/tomcat', ''],
+	       'toolkit' => ['gsl/toolkit', ''],
+	       'tools' => ['util/tools', 'cd'],
+	       'transex3' => ['l10n/transex3', ''],
+	       'twain' => ['external/twain', ''],
+	       'ucb' => ['ucb/ucb', ''],
+	       'ucbhelper' => ['ucb/ucbhelper', ''],
+	       'udkapi' => ['api/udkapi', ''],
+	       'udm' => ['tools/udm', ''],
+	       'unixODBC' => ['external/unixODBC', 'oj'],
+	       'UnoControls' => ['gsl/UnoControls', ''],
+               'unodevtools' => ['api/unodevtools', ''],
+	       'unoil' => ['udk/unoil', ''],
+	       'unotools' => ['util/unotools', 'fs'],
+	       'unoxml' => ['framework/unoxml', ''],
+	       'ure' => ['udk/ure', 'sb'],
+	       'uui' => ['ucb/uui', ''],
+	       'vbahelper' => ['api/vbahelper', 'npower'],
+	       'vcl' => ['gsl/vcl', ''],
+	       'vigra' => ['external/vigra', 'thb'],
+	       'vos' => ['udk/vos', ''],
+	       'wizards' => ['installation/wizards', ''],
+               'writerfilter' => ['sw/writerfilter', ''],
+               'writerperfect' => ['sw/writerperfect', 'fridrich_strba'],
+	       'x11_extensions' => ['external/x11_extensions', 'pl'],
+	       'xmerge' => ['xml/xmerge', ''],
+	       'xml2cmp' => ['tools/xml2cmp', ''],
+	       'xmlhelp' => ['util/xmlhelp', 'ab'],
+	       'xmloff' => ['xml/xmloff', ''],
+	       'xmlscript' => ['script/xmlscript', ''],
+	       'xmlsecurity' => ['xml/xmlsecurity', ''],
+	       'xpdf' => ['external/xpdf', ''],
+	       'xsltml' => ['external/xsltml', 'mav'],
+	       'zlib' => ['external/zlib', '']
+	      );
+# some projects are dead, but do still contain code
+%dead_projects = (
+           'oi' => 'oi',
+           'whiteboard' => 'whiteboard'
+          );
+%exceptions = (
+	       'sd' => 'Drawing',                       # graphics
+	       'chart2' => 'Chart',                        # graphics
+           'lingucomponent' => 'lingucomponent',    # whiteboard
+           'writerperfect' => 'wp',
+           'libwpd' => 'wp',
+	       );
+%languages = (
+	      'Brazilian(Pt)' => 'br-pt',
+	      'Catalan' => 'ca',
+	      'Czech' => 'cs',
+	      'Danish' => 'da',
+	      'German' => 'de',
+	      'Greek' => 'el',
+	      'Spanish' => 'es',
+	      'Basque' => 'eu',
+	      'Finnish' => 'fi',
+	      'French' => 'fr',
+	      'Hindi' => 'hi',
+	      'Hungarian' => 'hu',
+	      'Japanese' => 'ja',
+	      'Korean' => 'ko',
+	      'Laotian' => 'lo',
+          'Malaysian' => 'ms',
+          'Netherlands' => 'nl',
+          'Norwegian' => 'no',
+          'Portugese' => 'pt',
+          'Romanian' => 'ro',
+          'Russian' => 'ru',
+          'Serbian' => 'sr',
+          'Slovak' => 'sk',
+          'Slovenian' => 'sl',
+          'Swedish' => 'sv',
+          'Tamil' => 'ta',
+          'Thai' => 'th',
+          'Turkish' => 'tr',
+          'Vietnamese' => 'vi',
+          'Chinese' => 'zh',
+      );
+sub build_substitutions($)
+    my $value;
+    my $subs = shift;
+    ### languages ###
+    $value = '';
+    $element_cols = 5;
+    @element_keys = sort keys %languages;
+    $element_index = 0;
+    while ($element_index < $#element_keys ) {
+        $value .= '<td valign="top" align="left"><table border=0 cellspacing=1>';
+        $toggle = 1;
+        for (my $item = 0; ( $item < $#element_keys / $element_cols ) && ( $element_index < $#element_keys ); ++$item, ++$element_index) {
+        $value .= '<tr class="';
+        $value .= $toggle ? "a" : "b", $toggle = !$toggle;
+        $value .= '"><td><a href="/issues/enter_bug.cgi?component=';
+        $value .= $languages{$element_keys[$element_index]};
+        $value .= '">' . $element_keys[$element_index] . "</a></td></tr>\n";
+        }
+        $value .= "</table></td>";
+    }
+    $subs->{'%% All langs %%'} = $value;
+    ### projects ###
+    $value = '';
+    my $element_cols = 4;
+    my @element_keys = sort keys %toplevels;
+    my $element_index = 0;
+    while ($element_index <= $#element_keys ) {
+        $value .= '<td valign="top" align="left"><table>';
+        my $toggle = 1;
+        for (my $item = 0; ( $item < $#element_keys / $element_cols ) && ( $element_index <= $#element_keys ); ++$item, ++$element_index) {
+        $value .= '<tr class="';
+        $value .= $toggle ? "a" : "b", $toggle = !$toggle;
+        $value .= '"><td><a href="/issues/enter_bug.cgi?component=';
+        $value .= $toplevels{$element_keys[$element_index]}[0];
+        $value .= '">' . $toplevels{$element_keys[$element_index]}[1] . "</a></td></tr>\n";
+        }
+        $value .= "</table></td>";
+    }
+    $subs->{'%% Toplevels %%'} = $value;
+    ### modules ###
+    $value = '';
+    $toggle = 0;
+    my $directory_width = 6;
+    my $dir_idx = 0;
+    for my $item (sort keys %allmodules) {
+    my $module;
+    my $module_owner;
+    if (defined $exceptions{$item}) {
+        $module = $exceptions{$item};
+        if ($allmodules{$item}[1] eq '') {
+        }
+        else {
+            $module_owner = $allmodules{$item}[1];
+        }
+    } else {
+        my $name = $allmodules{$item}[0];
+        $name =~s/\/.*//;
+        $module = $toplevels{$name}[0];
+        $module = $dead_projects{$name} if !defined $module;
+        defined $module || die "No such module '$name'";
+        if ($allmodules{$item}[1] eq '') {
+            # module owner derived from project owner 
+	    $module_owner = $toplevels{$name}[2];
+	} else {
+            # other module owner
+	    $module_owner = $allmodules{$item}[1];
+	}
+    }
+	$dir_idx = $dir_idx % $directory_width;
+    if ($dir_idx == 0) {
+        $value .= '<tr class="';
+        $value .= $toggle ? "a" : "b", $toggle = !$toggle;
+        $value .= '">' . "\n";
+    }
+	$dir_idx++;
+	$value .= '<td><a href="/issues/enter_bug.cgi?component=';
+    $value .= $module;
+    $value .= '&subcomponent=code&issue_type=PATCH';
+    $value .= "&short_desc=$item:%20";
+    $value .= "&assigned_to=$module_owner\" if defined $module_owner;
+    $module =~ s/%20/ /g;
+	$value .= '">' . $item . "</td>\n";
+	$value .= "</tr>\n" if ($dir_idx == $directory_width);
+    }
+    $value .= "</tr>\n" if ($dir_idx != $directory_width);
+    $subs->{'%% All modules %%'} = $value;
+my $template;
+my %substitutions;
+my $InFile;
+$template = shift @ARGV || die " <template-file>\n";
+build_substitutions (\%substitutions);
+open $InFile, "$template" || die "Can't open $template";
+while (<$InFile>) {
+    for my $reg (keys %substitutions) {
+	s/$reg/$substitutions{$reg}/g;
+    }
+    print $_;
+close $InFile;

Propchange: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/handling_RFEs.html
--- incubator/ooo/ooo-site/trunk/content/qa/issue_handling/handling_RFEs.html (added)
+++ incubator/ooo/ooo-site/trunk/content/qa/issue_handling/handling_RFEs.html Wed Nov 16 22:14:47 2011
@@ -0,0 +1,219 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+  <head>
+    <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8">
+    <title></title>
+    <meta name="GENERATOR" content="StarOffice 7  (Linux)">
+    <meta name="CREATED" content="20040421;16480100">
+    <meta name="CHANGED" content="20040630;15235600">
+    <style type="text/css"> /* <![CDATA[ */
+    @import "/css/qa.css";
+    /* ]]> */</style>
+  </head>
+  <body lang="en-US" dir="ltr">
+    <h1 class="western">Proposed approach for consolidating IssueTracker RFEs
+      (request for enhancement) into product requirements</h1>
+    <h2 class="western">Introduction</h2>
+    <p>The goal of this exercise is to convert a huge number of unqualified
+      IssueTracker (formerly known as IssueZilla) RFEs into a smaller number of
+      cleaned-up (marketing) product requirements that can be understood both by
+      users and developers.</p>
+    <p>The goal of this exercise is to:</p>
+    <ol>
+      <li>
+        <p>Eliminate duplicate RFEs</p>
+      </li>
+      <li>
+        <p>Increase quality of RFEs</p>
+      </li>
+      <li>
+        <p>Get to a manageable number of requirements that the community can vote on and
+          that a commercial contributor (e.g. Sun) can handle as part of a product
+          definition process</p>
+      </li>
+    </ol>
+    <p>In this process description we distinguish between RFEs submitted by community
+      members and the (marketing) product requirements that are derived from the
+      original RFEs. The RFEs can be high-level or low-level, very detailed or vague,
+      can include examples or not, etc. The new requirements however should be easy
+      to understand and coherent.</p>
+    <p>All requirements should also include information about the importance of a
+      requirement to a specific user group as well as relevant market data. For
+      example, a specific use case how a feature would be used by a user would help
+      to understand why a feature is needed and what the significance to the market
+      is.</p>
+    <p>Since the implementation is up to the developer who eventually picks up a
+      requirement, it is more important to describe the desired functionality and
+      typical use cases instead of explaining how something should be implemented.</p>
+    <h2 class="western"><br>
+      <br>
+    </h2>
+    <h2 class="western" style="page-break-before: always;">Overview Diagram</h2>
+    <p><br>
+      <br>
+    </p>
+    <p><img src="/images/handling_RFEs_overview.gif" name="Graphic1" align="left" width="519" height="323" border="0"><br clear="left">
+      <br>
+      <br>
+    </p>
+    <h2 class="western">Query RFEs submitted by community members</h2>
+    <p>The various RFEs will be sorted, evaluated and consolidated by topic, i.e. by
+      component. A set of pre-defined queries will be provided by the QA and RFE
+      team, but in order to view all open RFEs, the following fields are important:</p>
+    <table width="100%" class="with_border" cellpadding="3" cellspacing="0">
+      <col width="128*">
+        <col width="128*">
+          <thead>
+            <tr valign="top">
+              <td width="10%">
+                <b> Field </b>
+              </td>
+              <td>
+                <b> Selection </b>
+              </td>
+            </tr>
+          </thead>
+          <tbody>
+            <tr valign="top">
+              <td width="50%">
+                Issuetype
+              </td>
+              <td width="50%">
+                  Enhancement and Feature
+              </td>
+            </tr>
+            <tr valign="top">
+              <td width="50%">
+                Status
+              </td>
+              <td width="50%">
+                Unconfirmed, New, Started and Reopened
+              </td>
+            </tr>
+            <tr>
+              <td colspan="2" width="100%" valign="top"/>
+            </tr>
+            <tr>
+              <td colspan="2" width="100%" valign="top">
+                IssueTracker queries can be saved. It is also possible to search for submitters
+                  using the fields Username and Reporter. The query can be narrowed down using
+                  the fields Component, Target Milestone, Date, etc.
+              </td>
+            </tr>
+          </tbody>
+    </table>
+    <p><br>
+      <br>
+    </p>
+    <h2 class="western">Convert low-level RFEs into high-level requirements</h2>
+    <p>Different IssueTracker RFEs that belong together because they talk about the
+      same requirement will be merged into one NEW requirement in IssueTracker, by
+      assigning the original RFE's to a completely new “meta” issue, i.e. the
+      requirement. The summary of the new requirement should summarize the key
+      elements of the old RFEs.</p>
+    <p>For example Writer RFE's like “implement styles preview in the Stylist”,
+      “dynamic styles” and “add default shortcuts to increase/decrease font size”
+      could be merged into a (summary) requirement like “Simplify formatting and font
+      handling in Writer”.</p>
+    <p>Users, developers and marketing project members should be able to understand
+      the requirement summary without having to read all the old RFEs. However, the
+      new requirement should contain links to the old RFEs (i.e. the RFE entries
+      should block the requirement entry in IssueTracker), because the old RFE's
+      provide more detailed information about the requirement and the use cases.</p>
+    <p>The Issuetype of the new requirement should be "Feature". It should be
+      assigned to someone from the requirements team, e.g. Erwin Tenhumberg (erwint).
+      Since this is a marketing task, the requirements should not be assigned to the
+      engineers directly.</p>
+    <p>The priority should be left at the default value (3), and the target milestone
+      will not be set for the new requirements. The priority will be determined
+      through the voting mechanism once all requirements are known.
+      The target milestone can only be set by the party/developer that promises to
+      work on the requirement.</p>
+    <p>The status has to be “New”. It will be set to “Started” as soon as someone
+      promises to implement a particular requirement. A special keyword "requirement"
+      has to be set. The description should also start with "Requirement:". It also
+      allows to search for the word "Requirement" in the description.
+    </p>
+    <p>Requirements ARE NOT the same as the regular RFEs submitted by the community
+      members as FEATUREs and ENHANCEMENTs. If an RFE is well written it should be
+      very easy to turn it into a requirement, but in many cases this will require
+      some clean-up work.</p>
+    <p>For the original/old RFEs the issue ID of the new requirement will be set in
+      the “Issue xxx blocks” field. This ensures that no data gets lost and that
+      progress can be monitored on a high level.</p>
+    <p>At this stage we have a list of requirements that is much shorter than the
+      original RFE's.
+    </p>
+    <h2 class="western">Prioritization of requirements</h2>
+    <p>Once all old RFEs have been converted into "clean and polished" requirements
+      the new requirements get a priority. This is a separate step because
+      prioritization is difficult or even impossible when the total number of
+      requirements is unknown. Due to the fact that engineering resources are
+      limited, a "first come first serve" approach does not work. In addition, using
+      something like voting on the original RFEs does not work because they are
+      either hard to understand by the people who are supposed to vote or there are
+      multiple RFEs for exactly the same product requirement. The prioritization will
+      happen through the IssueTracker voting mechanism.</p>
+    <p>At this stage we have a list of requirements that also include information
+      about the priority from a user point of view.</p>
+    <h2 class="western">Implementation of the requirements</h2>
+    <p>Sun as one of the key code contributors to the project will
+      decide to work on requirements that have a high priority and are aligned with
+      Sun's product and strategy goals. However, that also means that some
+      requirements will not be addressed by Sun. This can even happen with priorities
+      with a relatively high user priority if they don't fit into Sun's strategy.</p>
+    <p>For all requirements that Sun decides to implement, Sun will create a PCD item
+      in IssueTracker, i.e. the Summary contains the abbreviation “PCD” and also a
+      keyword “PCD” will be set (PCD is short for Product Concept Document). The
+      original requirement has to get a comment referring to the new PCD item.</p>
+    <p>A PCD item explains the concept what our engineering team will implement.
+      Thus, a PCD item does not talk about the “nitty gritty” implementation details,
+      but outlines the functionality that will get implemented.
+    </p>
+    <p>Since Sun might decide not to fully implement a product requirement, the
+      original requirement will stay open. The PCD item will however depend on the
+      requirement for tracking purposes.</p>
+    <p>The existence of a PCD item makes it possible to track the progress on a
+      particular requirement. The (potential) difference between a requirement and
+      its corresponding PCD item is the gap between the requirement and its
+      implementation.</p>
+    <p>Someone can either fill the gap by implementing the rest or creating a
+      completely independent second implementation that covers everything.</p>
+    <p>At this point we have a list of requirements and a list of PCD items. Every
+      PCD item must have a corresponding requirement, but there will also be
+      requirements that don't have a PCD item yet.</p>
+    <h2 class="western">Closing requirements</h2>
+    <p>Once the engineering work on the PCD items has been completed (i.e. a working
+      build can be downloaded and tested) the PCD item will be closed. If the PCD
+      item fully implements a requirement the requirement will also be closed. If the
+      PCD item only partly implemented the requirement, the original submitters have
+      to decide if the requirement should stay open or if the existing implementation
+      is sufficient.</p>
+    <p>Depending on the number, open requirements will stay open until the next
+      release cycle. If still nobody wants to address it, it will either get closed
+      or transferred to some kind of general to-do list.</p>
+    <h2 class="western">An example</h2>
+    <p>John submits an RFE with IssueTracker ID 00001 saying that “It should be easy to
+      exchange files in a well known and widely used read-only file format.”</p>
+    <p>Peter submits an RFE with IssueTracker ID 00002 demanding that “It should be
+      easier to generate PDF files”.</p>
+    <p>Jane creates yet another RFE with IssueTracker ID 00003 asking for “PDF export
+      solution that is 100% compatible with Acrobat Distiller”.</p>
+    <p>Finally, Susy opens an RFE with IssueTracker ID 00004 saying that “My friend
+      should be able to read my files without having to download”.</p>
+    <p>All these independent RFEs can be merged into just one product requirement.
+      Thus, the requirements team creates a new requirement that looks like this:
+      “ should have a PDF export feature that is 100% compatible with
+      Acrobat Distiller version XYZ”.</p>
+    <p>After some voting Sun would decide to work on the requirement and thus create
+      a PCD item. However, since Sun does not have enough resources, Sun decides not
+      to created a Distiller clone (at least not in the first step). Instead the PCD
+      item says “ will get basic PDF export support for all
+      applications. The functionality will cover X, Y, and Z, but not implement the
+      following Acrobat Distiller features: ....”</p>
+    <p>As a consequence, someone else can create a PCD item for the “rest
+      requirement”, create a completely independent additional implementation or just
+      live with the fact that the requirement might never get fully implemented.</p>
+  </body>

Propchange: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/handling_RFEs.html
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/index.html
--- incubator/ooo/ooo-site/trunk/content/qa/issue_handling/index.html (added)
+++ incubator/ooo/ooo-site/trunk/content/qa/issue_handling/index.html Wed Nov 16 22:14:47 2011
@@ -0,0 +1,172 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+  <head>
+    <meta name="generator" content="HTML Tidy, see">
+    <meta http-equiv="content-type" content=
+    "text/html; charset=UTF-8">
+    <style type="text/css"> /* <![CDATA[ */
+    @import "/css/qa.css";
+    /* ]]> */</style>
+  <title>Issue handling</title>
+  </head>
+  <body>
+    <div class="qa">
+      <h1>Issue Handling</h1>
+      <p>This page collects information around handling issues (Bugs, RFEs (requests for enhancements), etc.) in
+      IssueTracker. These documents look on worklow in more detail than our
+      <a href="">overview</a>
+      and the guidelines for <a href="">reporting issues</a>.</p>
+      <p>
+        <table width="100%" border="0" cellpadding="4" cellspacing="0">
+          <col width="76*">
+          <col width="175*">
+          <col width="5*">
+          <tr class="MainTableHeader">
+            <td colspan="2" width="100%"> Workflow charts </td>
+          </tr>
+          <tr class="InnerTableHeader">
+            <td width="20%"> Title </td>
+            <td> Description </td>
+          </tr>
+          <tr class="TableRow">
+            <td>
+              <a href="workflowcharts/defect_triaging.pdf"> <b>A Bug's life time</b> </a>
+            </td>
+            <td>
+              Describes the workflow for handling normal bugs - these is what you will probably encounter most in
+              IssueTracker.<br/>
+              If your're interested in what will happen to a bug you submitted, or if you want to help by triaging
+              bugs, you should look at this workflow.
+            </td>
+          </tr>
+          <tr class="TableRow">
+            <td>
+              <a href="workflowcharts/taskhandling_workflow_feature_specification.html"> <b>FEATURE: Specification Writing</b> </a>
+            </td>
+            <td>
+              Describes the workflow for specifying a feature, accompanied in IssueTracker.
+            </td>
+          </tr>
+          <tr class="TableRow">
+            <td>
+              <a href="workflowcharts/taskhandling_workflow_feature_implementation.html"> <b>FEATURE: Implementation</b> </a>
+            </td>
+            <td>
+              Describes the workflow for specifying a feature, accompanied in IssueTracker.
+            </td>
+          </tr>
+          <tr class="TableRow">
+            <td>
+              <a href="workflowcharts/taskhandling_workflow_feature_QA.html"> <b>FEATURE: Quality Assurance (QA)</b> </a>
+            </td>
+            <td>
+              Describes the workflow for QA'ing a feature, accompanied in IssueTracker.
+            </td>
+          </tr>
+          <tr class="TableRow">
+            <td>
+              <a href="workflowcharts/RFE_issues_by_QA.sxd"> <b>QA for RFEs</b> </a>
+            </td>
+            <td>
+              RFEs are "Requests for Enhancements" - these are those issues where people suggest new features
+              to be implemented, or existing features to be enhanced. This workflow describes how RFEs are handled by QA.<br/>
+              Note that QA is responsible for ensuring that RFEs are in a usable form before they're passed to
+              team which evaluates RFEs.
+            </td>
+          </tr>
+          <tr class="TableRow">
+            <td>
+              <a href="workflowcharts/evaluating_RFEs.html"><b>Evaluating RFEs</b></a>
+            </td>
+            <td>
+              This workflow describes how RFEs are handled by the user experience team.
+            </td>
+          </tr>
+        </table>
+      </p>
+      <p>
+        <table width="100%" border="0" cellpadding="4" cellspacing="0">
+          <col width="76*">
+          <col width="175*">
+          <col width="5*">
+          <tr class="MainTableHeader">
+            <td colspan="2" width="100%"> Policies </td>
+          </tr>
+          <tr class="InnerTableHeader">
+            <td width="20%"> Title </td>
+            <td> Description </td>
+          </tr>
+          <tr class="TableRow">
+            <td>
+              <a href="policies/regressions.html"> <b>Regressions</b> </a>
+            </td>
+            <td>
+              This document describes the policy with respect to regression issues, i.e. issues describing
+              broken functionality.
+            </td>
+          </tr>
+          <tr class="TableRow">
+            <td>
+              <a href="basic_rules.html"> <b>Basic IssueTracker Rules</b> </a>
+            </td>
+            <td>
+              This descument describes the very basic rules one should know - and respect - when submitting
+              issues, or adding comments to issues, in IssueTracker.
+            </td>
+          </tr>
+        </table>
+      </p>
+      <p>
+        <table width="100%" border="0" cellpadding="4" cellspacing="0">
+          <col width="76*">
+          <col width="175*">
+          <col width="5*">
+          <tr class="MainTableHeader">
+            <td colspan="2" width="100%"> Documents </td>
+          </tr>
+          <tr class="InnerTableHeader">
+            <td width="20%"> Title </td>
+            <td> Description </td>
+          </tr>
+          <tr class="TableRow">
+            <td>
+              <a href="handling_RFEs.html"> <b>Handling RFEs</b> </a>
+            </td>
+            <td>
+              This document proposes a handling for RFEs, to consolidate them (towards the planning of a new
+              release) into so-called requirements. This allows to get a better overview about requirements
+              people have to, and to decide, on a level which is more general than individual
+              issues, about the focus for the next release(s).
+            </td>
+          </tr>
+        </table>
+      </p>
+      <hr/>
+      <p align="right"> <em>Last modified: $Date: 2007/02/23 10:42:34 $</em> </p>
+    </div>
+  </body>

Propchange: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/index.html
    svn:eol-style = native

View raw message