Return-Path: X-Original-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 745BF902D for ; Wed, 16 Nov 2011 22:15:35 +0000 (UTC) Received: (qmail 86676 invoked by uid 500); 16 Nov 2011 22:15:35 -0000 Delivered-To: apmail-incubator-ooo-commits-archive@incubator.apache.org Received: (qmail 86653 invoked by uid 500); 16 Nov 2011 22:15:35 -0000 Mailing-List: contact ooo-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-commits@incubator.apache.org Received: (qmail 86646 invoked by uid 99); 16 Nov 2011 22:15:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Nov 2011 22:15:35 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,WEIRD_PORT X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Nov 2011 22:15:21 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 1DAC12388860; Wed, 16 Nov 2011 22:14:59 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 -0000 To: ooo-commits@incubator.apache.org From: kschenk@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20111116221459.1DAC12388860@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: kschenk Date: Wed Nov 16 22:14:47 2011 New Revision: 1202908 URL: http://svn.apache.org/viewvc?rev=1202908&view=rev Log: kls -- updated qa area Added: incubator/ooo/ooo-site/trunk/content/qa/__modules/ incubator/ooo/ooo-site/trunk/content/qa/__modules/left_sidebar_topics.htmlx (with props) incubator/ooo/ooo-site/trunk/content/qa/css/ incubator/ooo/ooo-site/trunk/content/qa/css/qa.css (with props) incubator/ooo/ooo-site/trunk/content/qa/images/ 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/ incubator/ooo/ooo-site/trunk/content/qa/issue_handling/FAQ/ 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/create_submission_gateway.pl (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/ 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/submission_gateway.template incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/ incubator/ooo/ooo-site/trunk/content/qa/issue_handling/workflowcharts/.inv/ 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/issues/ incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/css/ incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/css/default.css (with props) incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/docs/ 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/ 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/ 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/ 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/ 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/ incubator/ooo/ooo-site/trunk/content/qa/wwwstaging/ooQAReloaded/APITeamsite/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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 URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/qa/__modules/left_sidebar_topics.htmlx?rev=1202908&view=auto ============================================================================== --- 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 @@ + + + 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 URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/qa/css/qa.css?rev=1202908&view=auto ============================================================================== --- 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 @@ +.qa tr.MainTableHeader +{ + background-color: #003399; + color: #ffffff; + font-weight:bold; + font-family:Helvetica; + text-align:center; + font-size:large; +} + +.qa tr.InnerTableHeader +{ + background-color: #BBBBBB; + color: #000000; + font-weight:bold; + font-family:Helvetica; +} + +.qa tr.TableRow +{ + background-color: #f0f0f0; + font-family:Helvetica; +} + +.qa td.RowHeader +{ + font-weight:bold; +} + +.with_border +{ + 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 URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/qa/images/handling_RFEs_overview.gif?rev=1202908&view=auto ============================================================================== 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 URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/qa/images/qatrack_menu_logo.gif?rev=1202908&view=auto ============================================================================== 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 URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/qa/issue_handling/basic_rules.html?rev=1202908&view=auto ============================================================================== --- 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 @@ + + + + + Basic IssueTracker rules + + +
+

Basic IssueTracker rules

+

Why you should read this

+

Imagine how many people later on will read your issue (means the +issue which you submitted, or which you participated in)

+
    +
  • community members who performe triage on defects
    • +
  • developers who finally fix the defect
    • +
  • sometimes developers who need to do preliminary work
    • +
  • QA engineer(s) who needs to verify the fix
    • +
  • everybody who has the same problem and tries to understand +whether
    • +
      +
    • your defect also +describes his/her problem.
      • +
    • or whether your issue is one they like to vote for
      • +
    +
  • possibly a user experience team member evaluating a feature +request
    • +
  • possibly a release team member evaluating whether the defect is +important enough to be included in some maintenance update such as +1.1.1.
    • +
+You see, there are a lot of  people who may read what you wrote. +Thus, the majority of the rules below focuses on making reading easier: Though they +sometimes take you some little time to follow, they often save others a +lot of time later on. +

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.
+Since not obeying them makes defect handling more difficult (sometimes much more difficult), people may +tend to not deal with your issues until they are in a shape to +reasonably do so.

+

The rules

+

For those of you who like it short and simple:

+ +

One problem - One issue

+

When you report a problem, please submit one issue per problem. +There are various reasons for this, amongst them:

+
    +
  • The more crowded an issue is, the more likely is it that some +problems may get lost over time.
    • +
  • 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.
    • +
+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.
+If you don't follow this rule, be prepared for people asking you to +split up your issue. +

Provide a meaningful summary

+

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
+

+
    +
  • easily recognize +an issue in a list of dozens of others
    • +
  • find 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.
    • +
  • judge the importance +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)"
    • +
+Thus, please avoid summaries like "Big Bug in OpenOffice.org" 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.
+

Provide step-by-step descriptions

+

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.

+

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 "Style|Bold" +from the context menu, by choosing "Format|Character" from the menu +or "Character" 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 +OpenOffice.org crashes" is of nearly no use, since it forces other people to ask back +what you meant.

+

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 +this:
+

+
    +
  • 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 "Bold" +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.
    +
    • +
  • Writing down exactly +what you did costs you some time once, +but every 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.
    • +
  • 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 you +implicitly know, but your reader +doesn't.
    • +
+You may be tempted to consider it stupid to write a description like
+
    +
  • open a new writer document
    • +
  • enter some arbitrary text
    • +
  • select the whole text via "Edit|Select +all"
    • +
  • from the context menu of the text, chose "Style|Bold"
    • +
  • => OpenOffice.org crashes
    • +
+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. +

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.

+

Provide sample documents, if possible

+

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.
+

+

If the description how to reproduce a defect (see Provide step-by-step descriptions) exceeds +a certain limit, ask yourself whether you can submit the result of the description as sample +document, and attach it to the issue.
+

+

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 +....

+ +

Use attachments where possible

+

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 attach +this file. If you have some Basic macro or Java code which triggers a +problem, copy it into a separate file, and attach this file.

+

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.

+ +

Put all relevant information into the issue

+

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. +

+ +

If there is some external resource describing your problem - fine, link it! But don't rely +on links as the only mean for bug descriptions - copy the information which is +necessary to reproduce the problem into the issue.

+ +
+The author of the original document is Frank Schönheit. Constructive +feedback is welcome. You may +also consider visiting the +mailing list dedicated to discussing issue handling. +
+Last change: $Date: 2008/06/20 08:20:33 $ / $Author: fs $
+
+
+ + + 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 URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/qa/issue_handling/bug_writing_guidelines.html?rev=1202908&view=auto ============================================================================== --- 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 @@ + + + + + Issue Writing Guidelines + + +
+

Issue Writing Guidelines

+

$Date: 2007/02/23 11:26:39 $

+

Consider the rules
+

+

We strongly encourage you to read the Basic +IssueTracker rules - for those who work with IssueTracker on a +day-by-day base, they have proven to immensely +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.
+

+

Thus, if you're new to OpenOffice.org's IssueTracker, please read the rules. 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.

+

And, please don't be offended if we ask you to follow some rules: 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.

+

How to Write a Useful Issue Report

+
+

Useful issue reports are ones that get issues fixed. A useful +issue report normally has two qualities:

+
+
    +
  1. Reproducible. 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.
    2. +
    +
  2. Specific. 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.)
    3. +
+
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:
+
Bad: "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."
+
+ Good: "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. +

When I removed the chart from the document I was able to load it +without any trouble."

+
+

How to enter a useful Issue Report into IssueTracker

+
In order to file an Issue, you must be a registered user +of OpenOffice.org. 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 "Bugs +and Issues" 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. +

Go to the IssueTracker Query Page 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.) +

+

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.)
+
+If you've discovered a new issue using a current build, report it in +IssueTracker:

+
    +
  1. If you're not already logged in, please enter your username +& password in the appropriate filds at the top of this page (or any +other page on this site)
    2. +
  2. From your IssueTracker main page, choose "Enter a new issue".
    3. +
  3. Select the product that you've found an issue in.
    4. +
+

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)

+
+

Now, fill out the form. Here's what it all means:

+
Where did you find the issue?
+
Product: In which product did you find the issue?
+You just filled this out on the last page.
+
Version: In which product version did you find the +issue?
+If applicable.
+
Component: In which component does the issue exist?
+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.)
+
+Platform: On which hardware platform did you find this issue? (e.g., +Sun, PC)
+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.
+
OS: On which Operating System (OS) did you find this +issue? (e.g. Linux, Windows NT)
+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.
+

+ How important is the issue?
+
+Issue Type: Is this a defect, enhancement, feature-request, task or +patch?
+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.)
+
+Priority: How much does the problem affect the product's overall +usefullness?
+Developers use this field as one measure how to priorize +their work.
+This item defaults to '3'. 1 is the highest (rarely used), 5 the lowest +priority.
+Please read the definition +of issue priorities carefully before attempting to use P2 or even +P1.
+

+ Who will be following up on the issue?
+
+Assigned To: Which engineer should be responsible for fixing this +issue?
+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.)
+
Cc: Who else should receive e-mail updates on changes +to this issue?
+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.
+

+ What else can you tell the engineer about the issue?
+
URL: On what URL did you discover this issue?
+If you encountered the issue on a particular URL, please provide it +(or, them) here.
+
Summary: How would you describe the issue, in +approximately 60 or fewer characters?
+A good summary should quickly and uniquely identify an issue report. +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.
+
+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.
+

+ Description: What else can you tell the engineer about this issue?
+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.
+For crashing issues it might help to have additional information in +case you're able to provide that:
+

+ Target +Milestone: Think of it as a deadline; targets are "not +determined" or "next build"--for most issues, stipulate "not +determined." +
    +
+

Attachments. 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:

+
Create a new attachment (proposed patch, testcase, etc.)
+

Note: You cannot add OpenOffice.org files +natively. They must be added as "binary" files. This is a temporary +problem.

+

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. +

+

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.
+

+
+

(These Bug Writing Guidelines were originally written for Mozilla +by Eli Goldberg. +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 dev@qa +mailing list.)

+
+
+ + 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/create_submission_gateway.pl URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/qa/issue_handling/create_submission_gateway.pl?rev=1202908&view=auto ============================================================================== --- incubator/ooo/ooo-site/trunk/content/qa/issue_handling/create_submission_gateway.pl (added) +++ incubator/ooo/ooo-site/trunk/content/qa/issue_handling/create_submission_gateway.pl 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 .= ''; + $toggle = 1; + for (my $item = 0; ( $item < $#element_keys / $element_cols ) && ( $element_index < $#element_keys ); ++$item, ++$element_index) { + $value .= '\n"; + } + $value .= "
"; + } + $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 .= ''; + my $toggle = 1; + for (my $item = 0; ( $item < $#element_keys / $element_cols ) && ( $element_index <= $#element_keys ); ++$item, ++$element_index) { + $value .= '\n"; + } + $value .= "
"; + } + $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 .= '\n"; + + $value .= "\n" if ($dir_idx == $directory_width); + } + $value .= "\n" if ($dir_idx != $directory_width); + + $subs->{'%% All modules %%'} = $value; +} + +my $template; +my %substitutions; +my $InFile; + +$template = shift @ARGV || die "create_submission_gateway.pl \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/create_submission_gateway.pl ------------------------------------------------------------------------------ svn:eol-style = native Added: incubator/ooo/ooo-site/trunk/content/qa/issue_handling/handling_RFEs.html URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/qa/issue_handling/handling_RFEs.html?rev=1202908&view=auto ============================================================================== --- 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 @@ + + + + + + + + + + + +

Proposed approach for consolidating IssueTracker RFEs + (request for enhancement) into product requirements

+

Introduction

+

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.

+

The goal of this exercise is to:

+
    +
  1. +

    Eliminate duplicate RFEs

    +
    2. +
  2. +

    Increase quality of RFEs

    +
    3. +
  3. +

    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

    +
    4. +
+

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.

+

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.

+

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.

+


+
+

+

Overview Diagram

+


+
+

+


+
+
+

+

Query RFEs submitted by community members

+

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:

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Field + + Selection +
+ Issuetype + + + Enhancement and Feature +
+ Status + + Unconfirmed, New, Started and Reopened +
+
+ 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. +
+


+
+

+

Convert low-level RFEs into high-level requirements

+

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.

+

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”.

+

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.

+

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.

+

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 OpenOffice.org 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.

+

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. +

+

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.

+

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.

+

At this stage we have a list of requirements that is much shorter than the + original RFE's. +

+

Prioritization of requirements

+

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.

+

At this stage we have a list of requirements that also include information + about the priority from a user point of view.

+

Implementation of the requirements

+

Sun as one of the key code contributors to the OpenOffice.org 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.

+

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.

+

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. +

+

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.

+

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.

+

Someone can either fill the gap by implementing the rest or creating a + completely independent second implementation that covers everything.

+

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.

+

Closing requirements

+

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.

+

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.

+

An example

+

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.”

+

Peter submits an RFE with IssueTracker ID 00002 demanding that “It should be + easier to generate PDF files”.

+

Jane creates yet another RFE with IssueTracker ID 00003 asking for “PDF export + solution that is 100% compatible with Acrobat Distiller”.

+

Finally, Susy opens an RFE with IssueTracker ID 00004 saying that “My friend + should be able to read my files without having to download OpenOffice.org”.

+

All these independent RFEs can be merged into just one product requirement. + Thus, the requirements team creates a new requirement that looks like this: + “OpenOffice.org should have a PDF export feature that is 100% compatible with + Acrobat Distiller version XYZ”.

+

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 “OpenOffice.org 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: ....”

+

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.

+ + 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 URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/qa/issue_handling/index.html?rev=1202908&view=auto ============================================================================== --- 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 @@ + + + + + + + + + Issue handling + + + +
+

Issue Handling

+

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 + overview + and the guidelines for reporting issues.

+ +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Workflow charts
Title Description
+ A Bug's life time + + Describes the workflow for handling normal bugs - these is what you will probably encounter most in + IssueTracker.
+ 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. +
+ FEATURE: Specification Writing + + Describes the workflow for specifying a feature, accompanied in IssueTracker. +
+ FEATURE: Implementation + + Describes the workflow for specifying a feature, accompanied in IssueTracker. +
+ FEATURE: Quality Assurance (QA) + + Describes the workflow for QA'ing a feature, accompanied in IssueTracker. +
+ QA for RFEs + + 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.
+ Note that QA is responsible for ensuring that RFEs are in a usable form before they're passed to + team which evaluates RFEs. +
+ Evaluating RFEs + + This workflow describes how RFEs are handled by the user experience team. +
+

+ +

+ + + + + + + + + + + + + + + + + + + + + + + +
Policies
Title Description
+ Regressions + + This document describes the policy with respect to regression issues, i.e. issues describing + broken functionality. +
+ Basic IssueTracker Rules + + This descument describes the very basic rules one should know - and respect - when submitting + issues, or adding comments to issues, in IssueTracker. +
+

+ +

+ + + + + + + + + + + + + + + + + + +
Documents
Title Description
+ Handling RFEs + + 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 OpenOffice.org, and to decide, on a level which is more general than individual + issues, about the focus for the next release(s). +
+

+ +
+

Last modified: $Date: 2007/02/23 10:42:34 $

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