openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1010077 [24/31] - in /websites/staging/ooo-site/trunk: cgi-bin/ content/ content/pl/ content/pl/Archive/ content/pl/Archive/apps/ content/pl/Archive/apps/hr5000/ content/pl/Archive/grafika/ content/pl/Archive/info/ content/pl/Archive/marke...
Date Sat, 08 Apr 2017 23:00:14 GMT
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issue_lifecycle.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issue_lifecycle.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issue_lifecycle.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,253 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Issue Life Cycle</title>
+
+
+<!--#include virtual="/google-analytics.js" --> 
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/pl/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/pl/">pl</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/">Archive</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/">trans</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/">docs</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+
+<!--
+     The contents of this file are subject to the Mozilla Public
+     License Version 1.1 (the "License"); you may not use this file
+     except in compliance with the License. You may obtain a copy of
+     the License at http://www.mozilla.org/MPL/
+    
+     Software distributed under the License is distributed on an "AS
+     IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
+     implied. See the License for the specific language governing
+     rights and limitations under the License.
+    
+     The Original Code is the Issuezilla Issue Tracking System.
+    
+     The Initial Developer of the Original Code is Netscape Communications
+     Corporation. Portions created by Netscape are
+     Copyright (C) 1998 Netscape Communications Corporation. All
+     Rights Reserved.
+    
+     Contributor(s): 
+     Contributor(s): Terry Weissman <terry@mozilla.org>
+-->
+ <span class="Header" nowrap>An Issue's Life Cycle</span>
+<p>  
+ <span class="PlainText"><strong>Additional resources about issues: Index</strong>
+<ul>
+  <dl>
+  <dt><a href="ProjectIssues.html">Project Issues help</a>
+    <dd><strong>You are here: <a href="#lifecycle_table">The issue life cycle</a>
+       <ul>
+           <li><a href="#issuesequence">More about the sequence of an issue's status</a>
+           <li><a href="#verifyissues">Verifying issues</a>
+          </ul></strong>
+    <dd><a href="issuewritinghelp.html">Issue writing guidelines</a>
+    <dd><a href="issuezilla_tipsandtricks.html"> IssueZilla tips and tricks</a> 
+    <dd><a href="contributing_patches.html">Contributing patches</a>
+  <dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+  </dl>
+</ul>
+
+ 
+     
+ 
+<a name="lifecycle_table"></a><table border="1" cellspacing="2" cellpadding="2" border="0" width="100%">
+   <tr>
+    <td valign="top"><h3>STATUS</h3></td> 
+    <td valign="top"><h3>RESOLUTION</h3></td>
+  </tr>
+  <tr valign=top>
+    <td class="PlainText">The <b>status</b> field indicates the general health of an issue. Only certain status transitions are allowed.</td>
+    <td class="PlainText" valign="top">The <b>resolution</b> field indicates what happened to this issue.</td>
+  </tr>
+  <tr valign=top>
+    <td class="PlainText">
+      <dl>
+        <dt><b><a href="issues_unconfirmedhelp.html">UNCONFIRMED</a></b> 
+        <dd> This issue has recently been added to the database.  Nobody has
+     validated that this issue is true.  Users who have the "canconfirm"
+     permission set may confirm this issue, changing its state to <b>NEW</b>.
+     Or, it may be directly resolved and marked <b>RESOLVED</b>.
+        <dt><b>NEW</b> 
+        <dd> This issue has recently been added to the assignee's list of issues
+     and must be processed. Issues in this state may be accepted, and
+     become <b>STARTED</b>, passed on to someone else, and remain
+     <b>NEW</b>, or resolved and marked <b>RESOLVED</b>.
+        <dt><b>STARTED</b> 
+        <dd> This issue is not yet resolved, but is assigned to the proper
+     person. From here issues can be given to another person and become
+     <b>NEW</b>, or resolved and become <b>RESOLVED</b>.
+        <dt><b>REOPENED</b>
+        <dd>This issue was once resolved, but the resolution was deemed
+     incorrect.  For example, a <b>WORKSFORME</b> issue is
+     <b>REOPENED</b> when more information shows up and the issue is now
+     reproducible.  From here issues are either marked <b>STARTED</b>
+     or <b>RESOLVED</b>.
+      </dl>
+    </td>
+    <td class="PlainText">
+      <dl>
+        <dd> No resolution yet. All issues which are in one of these "open" states have the resolution set to blank. All other issues will be marked with one of the resolutions below.
+      </dl>
+    </td>
+  </tr>
+  <tr valign=top>
+    <td class="PlainText">
+      <dl>
+        <dt><b>RESOLVED</b> 
+        <dd> A resolution has been taken, and it is awaiting verification by
+     QA. From here issues are either re-opened and become
+     <b>REOPENED</b>, are marked <b>VERIFIED</b>, or are closed for good
+     and marked <b>CLOSED</b>.
+        <dt><b>VERIFIED</b>
+        <dd> QA has looked at the issue and the resolution and agrees that the
+     appropriate resolution has been taken.  Issues remain in this state
+     until the product they were reported against is actually released, at
+     which point they become <b>CLOSED</b>.
+        <dt><b>CLOSED</b> 
+        <dd> The issue is considered dead, the resolution is correct. Any zombie
+     issues who choose to walk the earth again must do so by becoming
+     <b>REOPENED</b>.
+      </dl>
+    </td>
+    <td class="PlainText">  
+      <dl>
+        <dt><b>FIXED</b>
+        <dd> A fix for this issue is checked into the source code repository and tested.
+        <dt><b>INVALID</b>
+        <dd> The problem described is not an issue 
+        <dt><b>WONTFIX</b>
+        <dd> The problem described is an issue which will never be fixed.
+        <dt><b>LATER</b>
+        <dd> The problem described is an issue which will not be fixed in this
+     version of the product.
+        <dt><b>REMIND</b>
+        <dd> The problem described is an issue which will probably not be fixed in this
+     version of the product, but might still be.
+        <dt><b>DUPLICATE</b>
+        <dd> The problem is a duplicate of an existing issue. Marking an issue
+     duplicate requires the issue number of the duplicating issue and will at
+     least put that issue number in the description field.
+        <dt><b>WORKSFORME</b>
+        <dd> All attempts at reproducing this issue were futile, reading the
+     code produces no clues as to why this behavior would occur. If
+     more information appears later, please re-assign the issue, for
+     now, file it.
+      </dl>
+      <p>
+    </td>
+  </tr>
+</table>
+
+<table border="0" cellspacing="2" cellpadding="2" border="0" width="100%">
+  <tr>
+    <td class="PlainText" valign="top">
+      <p><span class="InputHeader"><a name="issuesequence">More about the sequence of an issue's status</a></span>
+
+      <p>What happens to an issue when it is first reported depends on
+      who reported it. By default, issues reported (that is, entered)
+      into IssueZilla are assigned a status of <span
+      class="TypewriterBold">UNCONFIRMED</span>. This means that a QA
+      (Quality Assurance) person -- or whoever has the appropriate
+      permissions on your project -- needs to confirm that this issue
+      is legitimate before changing its status to <span
+      class="TypewriterBold">NEW</span>. By sending mail to <!-- is
+      this the right alias?
+      -->issues-subscribe@&lt;projectname&gt;.domain.com, you can be
+      notified of all changes to an issue. You then use issue tracking
+      to view and further &quot;workflow&quot; the issue.
+
+      <p>If you are a project member who is a developer/user/tester,
+      you can create <span class="TypewriterBold">NEW</span> issues
+      and assign them to other developers. When an issue's status
+      becomes <span class="TypewriterBold">NEW</span>, the developer
+      assigned the issue either accepts it or reassigns it to someone
+      else. If the issue remains new and inactive for more than a
+      week, IssueZilla nags the issue's owner with email until action
+      is taken. Whenever a issue is reassigned or has its component
+      changed, its status is set back to <span
+      class="TypewriterBold">NEW</span>. The <span
+      class="TypewriterBold">NEW</span> status means that the issue is
+      newly added to a particular developer's plate, not that the
+      issue is newly reported. Think of <span
+      class="TypewriterBold">NEW</span> as an important e-mail you
+      need to answer, except you respond through IssueZilla, and you
+      can use this tool to track the issue's progress more efficiently
+      than e-mail.
+
+      <p>Some project members with additional permissions have the
+      ability to change all the fields of a issue. (Default
+      permissions only allow limited fields to be changed. (<a
+      href="/docs/ProjectIssues.html#permissions">Read
+      more about IssueZilla permissions</a>). Whenever you change a
+      field in a issue it's a good idea to add additional comments to
+      explain what you are doing and why. Make a note in the comments
+      field whenever you:
+      <ul>
+        <li>change the component
+        <li>reassign the issue
+        <li>create an attachment
+        <li>add a dependency, or
+        <li>add someone to the CC list.
+      </ul>
+
+      <p>Whenever someone else makes a change to an issue or adds a
+      comment, they are added to the CC list and the owner, reporter,
+      and CC list receive an email announcing changes to the
+      issue. This email reports the change using a "diff" format,
+      marking which lines have changed and including any new comments.
+      <dl>
+
+      <p>
+<span class="InputHeader"><a name="verifyissues"></a>Verifying issues</span>
+
+      <p>When issues are marked resolved, project/component owners
+      look at these to make sure the appropriate action has been
+      taken. If they agree, the issue is marked <span
+      class="TypewriterBold">VERIFIED</span>. Issues remain in this
+      state until the product or version is released, then the issue
+      is marked <span class="TypewriterBold">CLOSED</span>. Issues may
+      come back to life by becoming 
+      <span class="TypewriterBold">REOPENED</span>.  <p>Be careful about
+      changing the status of someone else's issues. Instead of making
+      the change yourself, it's usually best to make a note of your
+      proposed change as a comment <i>first</i> and to let the issue's
+      owner review this and make the change themselves. For example,
+      if you think one issue is a duplicate of another, make a note of
+      it in the "Additional Comments" section of the issue.
+
+      <p>If you make a lot of useful comments to others' issues, you
+      gain their trust in your judgement and you may be given
+      permissions to go ahead and make the changes yourself. Unless
+      and until this happens, exercise discretion by using the
+      "Additional Comments" section.
+
+    </td>
+  </tr>
+</table>
+
+ <hr noshade size=1>
+<span class="PlainText">
+<a href="ProjectIssues.html">Back to Project Issues help</a><br>
+<a href="/servlets/HelpTOC">Back to main Help index</a>
+</span>
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issue_lifecycle.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issue_lifecycle.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issue_lifecycle.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,145 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+  <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+  <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+  <title>Issue lifecycle</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="issuelifecycle">
+   <!--
+                The contents of this file are subject to the Mozilla Public
+                License Version 1.1 (the "License"); you may not use this file
+                except in compliance with the License. You may obtain a copy of
+                the License at http://www.mozilla.org/MPL/
+               
+                Software distributed under the License is distributed on an "AS
+                IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
+                implied. See the License for the specific language governing
+                rights and limitations under the License.
+               
+                The Original Code is the Issuezilla Issue Tracking System.
+               
+                The Initial Developer of the Original Code is Netscape Communications
+                Corporation. Portions created by Netscape are
+                Copyright (C) 1998 Netscape Communications Corporation. All
+                Rights Reserved.
+               
+                Contributor(s): 
+                Contributor(s): Terry Weissman <terry@mozilla.org>
+           -->
+
+   <h2>An Issue's Life Cycle</h2>
+
+   <div id="toc">
+    <ul>
+     <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+    </ul>
+
+    <ul>
+     <li>
+      <a href="/nonav/docs/ProjectIssues.html">Project Issues help</a> 
+
+      <ul>
+       <li>The issue life cycle</li>
+
+       <li><a href="/nonav/docs/issuewritinghelp.html">Issue writing guidelines</a></li>
+
+       <li><a href="/nonav/docs/issuezilla_tipsandtricks.html">IssueZilla tips and tricks</a></li>
+
+       <li><a href="/nonav/docs/contributing_patches.html">Contributing patches</a></li>
+      </ul>
+     </li>
+    </ul>
+   </div>
+
+   <h3><a id="lifecycle_table" name="lifecycle_table">Status</a></h3>
+   The <b>status</b> field indicates the general health of an issue. Only certain status transitions are allowed. The <b>resolution</b> field indicates what happened to this issue. 
+
+   <p><b>Open State issues</b>: The following status values are in an "open" state; they have no resolution.</p>
+
+   <ul>
+    <li><a href="/nonav/docs/issues_unconfirmedhelp.html">UNCONFIRMED</a>: This issue has recently been added to the database. Nobody has validated that this issue is true. Users who have the "canconfirm" permission set may confirm this issue, changing its state to <b>NEW</b>. Or, it may be directly resolved and marked <b>RESOLVED</b>.</li>
+
+    <li>NEW: This issue has recently been added to the assignee's list of issues and must be processed. Issues in this state may be accepted, and become <b>STARTED</b>, passed on to someone else, and remain <b>NEW</b>, or resolved and marked <b>RESOLVED</b>.</li>
+
+    <li>STARTED: This issue is not yet resolved, but is assigned to the proper person. From here issues can be given to another person and become <b>NEW</b>, or resolved and become <b>RESOLVED</b>.</li>
+
+    <li>REOPENED: This issue was once resolved, but the resolution was deemed incorrect. For example, a <b>WORKSFORME</b> issue is <b>REOPENED</b> when more information shows up and the issue is now reproducible. From here issues are either marked <b>STARTED</b> or <b>RESOLVED</b>.</li>
+   </ul>
+
+   <p><b>Resolved State issues</b>: The following status values are in an "resolved" state; they have no resolution.</p>
+
+   <ul>
+    <li>RESOLVED: A resolution has been taken, and it is awaiting verification by QA. From here issues are either re-opened and become <b>REOPENED</b>, are marked <b>VERIFIED</b>, or are closed for good and marked <b>CLOSED</b>.</li>
+
+    <li>VERIFIED: QA has looked at the issue and the resolution and agrees that the appropriate resolution has been taken. Issues remain in this state until the product they were reported against is actually released, at which point they become <b>CLOSED</b>.</li>
+
+    <li>CLOSED: The issue is considered dead, the resolution is correct. Any zombie issues who choose to walk the earth again must do so by becoming <b>REOPENED</b>.</li>
+   </ul>
+
+   <p>NOTE: Resolved state issues can have the following resolution values:</p>
+
+   <ul>
+    <li>FIXED: A fix for this issue is checked into the source code repository and tested.</li>
+
+    <li>INVALID: The problem described is not an issue</li>
+
+    <li>WONTFIX: The problem described is an issue which will never be fixed.</li>
+
+    <li>LATER: The problem described is an issue which will not be fixed in this version of the product.</li>
+
+    <li>REMIND: The problem described is an issue which will probably not be fixed in this version of the product, but might still be.</li>
+
+    <li>DUPLICATE: The problem is a duplicate of an existing issue. Marking an issue duplicate requires the issue number of the duplicating issue and will at least put that issue number in the description field.</li>
+
+    <li>WORKSFORME: All attempts at reproducing this issue were futile, reading the code produces no clues as to why this behavior would occur. If more information appears later, please re-assign the issue, for now, file it.</li>
+   </ul>
+
+   <h3><a id="issuesequence" name="issuesequence">More about the sequence of an issue's status</a></h3>
+
+   <p>What happens to an issue when it is first reported depends on who reported it. By default, issues reported (that is, entered) into IssueZilla are assigned a status of <code>UNCONFIRMED</code>. This means that a QA (Quality Assurance) person -- or whoever has the appropriate permissions on your project -- needs to confirm that this issue is legitimate before changing its status to <code>NEW</code>. By sending mail to <!-- is
+                    this the right alias?
+                    -->issues-subscribe@&lt;projectname&gt;.domain.com, you can be notified of all changes to an issue. You then use issue tracking to view and further "workflow" the issue.</p>
+
+   <p>If you are a project member who is a developer/user/tester, you can create <code>NEW</code> issues and assign them to other developers. When an issue's status becomes <code>NEW</code>, the developer assigned the issue either accepts it or reassigns it to someone else. If the issue remains new and inactive for more than a week, IssueZilla nags the issue's owner with email until action is taken. Whenever a issue is reassigned or has its component changed, its status is set back to <code>NEW</code>. The <code>NEW</code> status means that the issue is newly added to a particular developer's plate, not that the issue is newly reported. Think of <code>NEW</code> as an important e-mail you need to answer, except you respond through IssueZilla, and you can use this tool to track the issue's progress more efficiently than e-mail.</p>
+
+   <p>Some project members with additional permissions have the ability to change all the fields of a issue. (Default permissions only allow limited fields to be changed. (<a href="/nonav/docs/ProjectIssues.html#permissions">Read more about IssueZilla permissions</a>). Whenever you change a field in a issue it's a good idea to add additional comments to explain what you are doing and why. Make a note in the comments field whenever you:</p>
+
+   <ul>
+    <li>change the component</li>
+
+    <li>reassign the issue</li>
+
+    <li>create an attachment</li>
+
+    <li>add a dependency, or</li>
+
+    <li>add someone to the CC list.</li>
+   </ul>
+
+   <p>Whenever someone else makes a change to an issue or adds a comment, they are added to the CC list and the owner, reporter, and CC list receive an email announcing changes to the issue. This email reports the change using a "diff" format, marking which lines have changed and including any new comments.</p>
+
+   <h3><a id="verifyissues" name="verifyissues">Verifying issues</a></h3>
+
+   <p>When issues are marked resolved, project/component owners look at these to make sure the appropriate action has been taken. If they agree, the issue is marked <code>VERIFIED</code>. Issues remain in this state until the product or version is released, then the issue is marked <code>CLOSED</code>. Issues may come back to life by becoming <code>REOPENED</code>.</p>
+
+   <p>Be careful about changing the status of someone else's issues. Instead of making the change yourself, it's usually best to make a note of your proposed change as a comment <i>first</i> and to let the issue's owner review this and make the change themselves. For example, if you think one issue is a duplicate of another, make a note of it in the "Additional Comments" section of the issue.</p>
+
+   <p>If you make a lot of useful comments to others' issues, you gain their trust in your judgement and you may be given permissions to go ahead and make the changes yourself. Unless and until this happens, exercise discretion by using the "Additional Comments" section.</p>
+
+   <div class="courtesylinks">
+    <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+   </div>
+  </div>
+ </body>
+</html>
+
+

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issues_unconfirmedhelp.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issues_unconfirmedhelp.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issues_unconfirmedhelp.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,139 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<TITLE>Understanding the UNCONFIRMED Issue State</TITLE>
+
+
+<!--#include virtual="/google-analytics.js" --> 
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/pl/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/pl/">pl</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/">Archive</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/">trans</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/">docs</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+<!-- style/format note: Headings/fonts should be updated to conform to scast style -->
+
+<!--
+     The contents of this file are subject to the Mozilla Public
+     License Version 1.1 (the "License"); you may not use this file
+     except in compliance with the License. You may obtain a copy of
+     the License at http://www.mozilla.org/MPL/
+    
+     Software distributed under the License is distributed on an "AS
+     IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
+     implied. See the License for the specific language governing
+     rights and limitations under the License.
+    
+     The Original Code is the IssueZilla Issue Tracking System.
+    
+     The Initial Developer of the Original Code is Netscape Communications
+     Corporation. Portions created by Netscape are
+     Copyright (C) 2000 Netscape Communications Corporation. All
+     Rights Reserved.
+    
+     Contributor(s): Terry Weissman <terry@mozilla.org>
+-->
+<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
+  <TR>
+    <TD class="Header" nowrap>Understanding the UNCONFIRMED issue state</TD>  
+  </TR>
+</TABLE>
+<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
+  <TR>
+    <TD class="PlainText" VALIGN="top">
+
+<P>[This document is aimed primarily at people who may have used
+IssueZilla before the <span class="TypewriterBold">UNCONFIRMED</span>
+state was implemented. It might be helpful for newer users as well.]
+
+<P>
+
+New issues in some products will now show up in a new state, <span
+class="TypewriterBold">UNCONFIRMED</span>.  This means that nobody has
+confirmed that the issue is real. Very busy developers generally
+ignore <span class="TypewriterBold">UNCONFIRMED</span> that have been
+assigned to them, until they have been confirmed in one way or
+another.  (Developers with more time will hopefully glance over their
+<span class="TypewriterBold">UNCONFIRMED</span> issues regularly.)
+
+<P>
+
+There are two basic ways that an issue can become confirmed (and thus
+enter the <span class="TypewriterBold">NEW</span>) state.
+
+<UL>
+
+  <LI> A user with the appropriate permissions (see below for more on
+       permissions) decides that the issue is a valid one, and confirms
+       it.
+<P>
+
+  <LI> The issue gathers a certain number of votes. <B>Any</B> valid
+  IssueZilla user may vote for issues (each user gets a certain number
+  of issues); any <span class="TypewriterBold">UNCONFIRMED</span>
+  issue which gets enough votes becomes automatically confirmed, and
+  enters the <span class="TypewriterBold">NEW</span> state.
+
+</UL>
+
+That's why it is worthwhile to search the issue database for
+duplicates of your issue to vote on them <B><I>before</I></B>
+submitting your own issue. This helps to prevent issue duplication in
+the database.
+
+<P><span class="InputHeader">Permissions and the UNCONFIRMED issue state</span>
+
+<P>
+If you have the "Can confirm an issue" permission, then you will be
+able to change <span class="TypewriterBold">UNCONFIRMED</span> issues
+to the <span class="TypewriterBold">NEW</span> state.
+
+<P>
+If you not have the "Can confirm an issue" permission, you can still
+<span class="TypewriterBold">ACCEPT</span> or <span
+class="TypewriterBold">RESOLVE</span> all issues assigned to
+you. IssueZilla keeps track of this. If this issue gets <span
+class="TypewriterBold">REOPENED</span> or reassigned to someone else,
+it reverts back to the <span class="TypewriterBold">UNCONFIRMED</span>
+state. If such an issue <i>has</i> been confirmed, then reassigning
+changes its status to <span class="TypewriterBold">NEW</span> or <span
+class="TypewriterBold">REOPENED</span>.
+
+<P>
+If you have the "Can edit all aspects of any issue" permission, when
+you submit issues, these start out in the <span
+class="TypewriterBold">NEW</span> state rather than the <span
+class="TypewriterBold">UNCONFIRMED</span> state. You can override this
+feature, however, when you want to submit an issue as <span
+class="TypewriterBold">UNCONFIRMED</span>.
+
+
+    </TD>
+  </TR>
+</TABLE>
+
+
+
+
+
+
+
+
+
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issues_unconfirmedhelp.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issues_unconfirmedhelp.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issues_unconfirmedhelp.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,69 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+  <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+  <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+  <title>Understanding the unconfirmed issue state</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="issuesunconfirmedhelp">
+   <!--
+               The contents of this file are subject to the Mozilla Public
+               License Version 1.1 (the "License"); you may not use this file
+               except in compliance with the License. You may obtain a copy of
+               the License at http://www.mozilla.org/MPL/
+              
+               Software distributed under the License is distributed on an "AS
+               IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
+               implied. See the License for the specific language governing
+               rights and limitations under the License.
+              
+               The Original Code is the IssueZilla Issue Tracking System.
+              
+               The Initial Developer of the Original Code is Netscape Communications
+               Corporation. Portions created by Netscape are
+               Copyright (C) 2000 Netscape Communications Corporation. All
+               Rights Reserved.
+              
+               Contributor(s): Terry Weissman <terry@mozilla.org>
+          -->
+
+   <h2>Understanding the UNCONFIRMED issue state</h2>
+
+   <p>[This document is aimed primarily at people who may have used IssueZilla before the <code>UNCONFIRMED</code> state was implemented. It might be helpful for newer users as well.]</p>
+
+   <p>New issues in some products will now show up in a new state, <code>UNCONFIRMED</code>. This means that nobody has confirmed that the issue is real. Very busy developers generally ignore <code>UNCONFIRMED</code> that have been assigned to them, until they have been confirmed in one way or another. (Developers with more time will hopefully glance over their <code>UNCONFIRMED</code> issues regularly.)</p>
+
+   <p>There are two basic ways that an issue can become confirmed (and thus enter the <code>NEW</code>) state.</p>
+
+   <ul>
+    <li>A user with the appropriate permissions (see below for more on permissions) decides that the issue is a valid one, and confirms it.</li>
+
+    <li>The issue gathers a certain number of votes. <b>Any</b> valid IssueZilla user may vote for issues (each user gets a certain number of issues); any <code>UNCONFIRMED</code> issue which gets enough votes becomes automatically confirmed, and enters the <code>NEW</code> state.</li>
+   </ul>
+
+   <p>That's why it is worthwhile to search the issue database for duplicates of your issue to vote on them <b><i>before</i></b> submitting your own issue. This helps to prevent issue duplication in the database.</p>
+
+   <h3>Permissions and the UNCONFIRMED issue state</h3>
+
+   <p>If you have the "Can confirm an issue" permission, then you will be able to change <code>UNCONFIRMED</code> issues to the <code>NEW</code> state.</p>
+
+   <p>If you not have the "Can confirm an issue" permission, you can still <code>ACCEPT</code> or <code>RESOLVE</code> all issues assigned to you. IssueZilla keeps track of this. If this issue gets <code>REOPENED</code> or reassigned to someone else, it reverts back to the <code>UNCONFIRMED</code> state. If such an issue <i>has</i> been confirmed, then reassigning changes its status to <code>NEW</code> or <code>REOPENED</code>.</p>
+
+   <p>If you have the "Can edit all aspects of any issue" permission, when you submit issues, these start out in the <code>NEW</code> state rather than the <code>UNCONFIRMED</code> state. You can override this feature, however, when you want to submit an issue as <code>UNCONFIRMED</code>.</p>
+
+   <div class="courtesylinks">
+    <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+   </div>
+  </div>
+ </body>
+</html>
+
+

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuewritinghelp.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuewritinghelp.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuewritinghelp.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,312 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>IssueZilla Issue Writing Guide</title>
+
+
+<!--#include virtual="/google-analytics.js" --> 
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/pl/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/pl/">pl</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/">Archive</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/">trans</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/">docs</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+
+    <span class="Header" nowrap>Issue writing guidelines</span>  
+<p> 
+ <span class="PlainText"><strong>Additional resources about issues: Index</strong>
+<ul>
+  <dl>
+  <dt><a href="ProjectIssues.html">Project Issues help</a>
+    <dd><a href="issue_lifecycle.html">The issue life cycle</a> 
+    <dd><strong>You are here: Issue writing guidelines</strong>
+    <dd><a href="issuezilla_tipsandtricks.html"> IssueZilla tips and tricks</a> 
+    <dd><a href="contributing_patches.html">Contributing patches</a>
+  <dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+  </dl>
+</ul>
+
+
+ 
+     <p>
+ <hr noshade size=1>
+     <span class="InputHeader">Why you should read this</span>
+
+   <span class="PlainText">
+     <p>Simply put, the more effectively you report an issue, the more
+     likely an engineer will actually fix it. <br> 
+     <a href="http://IssueZilla.mozilla.org"></a><br> These issue writing
+     guidelines are an attempt at a general tutorial on writing
+     effective issue reports for novice issue writers; not every
+     sentence may precisely apply to your software project.
+
+     <p>
+ <hr noshade size=1>
+     <span class="InputHeader">How to write a useful issue report</span>
+     <p>Useful issue reports are ones that get issues fixed. A useful issue report normally has two qualities:
+     <ol>
+
+      <li><span class=inputheader>Reproducible.</span> If an engineer
+      can't see it or conclusively prove that it exists, the engineer
+      will probably stamp it &quot;WORKSFORME&quot; or
+      &quot;INVALID&quot;, and move on to the next issue. Every detail
+      you can provide helps. <p>
+
+      <li><span class=inputheader>Specific.</span> 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.)
+
+     </ol>
+
+     <p>Let's say the application you're testing is a web browser. You
+     crash at foo.com, and want to write up an issue report:
+
+
+     <p><span class="InputHeader">BAD:</span> &quot;My browser
+     crashed. I think I was on foo.com. 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
+     home page doesn't look right, either, it's all messed up. Good
+     luck.&quot;
+
+<br>
+<br>
+
+     <span class="InputHeader">GOOD: </span>&quot;I crashed each time
+     when I went to foo.com, using the 10.28.99 build on a Win NT 4.0
+     (Service Pack 5) system. I also rebooted into Linux, and
+     reproduced this problem using the 10.28.99 Linux build.<br><br>
+     It again crashed each time upon drawing the Foo banner at the top
+     of the page. I broke apart the page, and discovered that the
+     following image link will crash the application reproducibly,
+     unless you remove the &quot;border=0&quot; attribute:
+     <br>
+     <br>
+     &lt;IMG
+     SRC=&quot;http://foo.com/images/topics/topicfoos.gif&quot;
+     width=34 height=44 border=0 alt=&quot;News&quot;&gt;&quot;
+
+<br>
+<br>
+
+     <p><span class=inputheader>How to Enter your Useful Issue Report into IssueZilla:</span>
+
+
+<blockquote>
+    <p>Before you enter your issue, use the IssueZilla 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.)<br><br>
+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 IssueZilla:
+</blockquote>
+
+
+     <ol>
+      <ol>
+
+      <li>From your IssueZilla main page, choose &quot;Enter a new issue&quot;.
+
+      <li>Select the product that you've found an issue in.
+
+      <li>Enter your e-mail address, password, and press the
+      &quot;Login&quot; button.  (If you don't yet have a password,
+      leave the password text box empty, and press the &quot;E-mail me
+      a password&quot; button instead. You'll receive an E-mail
+      message with your password shortly.)
+
+     </ol>
+    <p>Now, fill out the form. Here's what it all means:
+     </ol>
+
+
+
+<blockquote>
+    <p><span class=inputheader>Where did you find the issue?</span>
+
+<blockquote>
+    <p><span class="InputHeader">Product: In which product did you find the issue?</span><br>
+You just filled this out on the last page.</p>
+    <p><span class="InputHeader">Version: In which product version did you find the issue?</span><br>
+If applicable.
+    <p><span class="InputHeader">Component: In which component does the issue exist?</span><br>
+IssueZilla 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.)</p>
+    <p><span class="InputHeader">Platform:&#160;On which hardware platform did you find this issue?</span>
+(e.g. Macintosh, SGI, 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 &quot;Other&quot; if your platform isn't
+listed.</p>
+    <p><span class="InputHeader">OS: On which Operating System (OS) did you find this issue?</span> (e.g.Linux, Windows NT, Mac OS 8.5.)<br>
+If you know the issue happens on all operating systems, choose 'All'. Otherwise, select the OS that
+you found the issue on, or &quot;Other&quot; if your OS isn't listed.</p>
+</blockquote>
+    <p><span class="InputHeader"><br>How important is the issue?</span>
+<blockquote>
+    <p><span class="InputHeader">Issue Type: Is this a defect, enhancement,
+feature-request, or task?</span><br> 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>
+    <p><span class="InputHeader"><br>Who will be following up on the issue?</span>
+<blockquote>
+    <p><span class="InputHeader">Assigned To: Which engineer should be responsible for fixing this issue?</span><br>
+IssueZilla 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.)</p>
+    <p><span class="InputHeader">Cc: Who else should receive e-mail updates on changes to this issue? </span><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>
+    <p><span class="InputHeader"><br>What else can you tell the engineer about the issue?</span></p>
+<blockquote>
+    <p><span class="InputHeader">URL: On what URL did you discover this issue?</span><br>
+If you encountered the issue on a particular URL, please provide it (or, them) here.
+If you've isolated the issue to a specific HTML snippet, please also provide a URL
+for that, too.
+
+    <p><span class="InputHeader">Summary:</span> <span
+    class="InputHeader">How would you describe the issue, in
+    approximately 60 or fewer characters?</span><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
+    &quot;PCMCIA install fails on Tosh Tecra 780DVD w/ 3c589C&quot; is
+    a useful title. &quot;Software fails&quot; or &quot;install
+    problem&quot; would be examples of a bad title.
+
+    <p><br>
+
+     <span class="InputHeader">Description: What else can you tell the engineer about this issue? </span><br>
+Please provide as detailed of a problem diagnosis in this field as possible. <br>
+<br>
+Where applicable, using the following issue report template will help ensure that all
+relevant information comes through:
+
+
+    <blockquote>
+      <p><span class=inputheader>Overview Description:</span> More detailed expansion of summary.
+
+      <blockquote>
+        <pre><font size="2">Drag-selecting any page crashes Mac builds in NSGetFactory</font></pre>
+
+      </blockquote>
+      <p><span class=inputheader>Steps to Reproduce: </span>The minimal set of steps necessary to trigger the issue.
+      Include any special setup steps. 
+
+      <blockquote>
+        <pre><font size="2">1) View any web page. (I used the default sample page, 
+   resource:/res/samples/test0.html)
+2) Drag-select the page. (Specifically, while holding down the 
+   mouse button, drag the mouse pointer downwards from any point in 
+   the browser's content region to the bottom of the browser's 
+   content region.)</font></pre>
+
+      </blockquote>
+      <p><span class=inputheader>Actual Results:</span> What the application did after performing the above steps.
+
+      <blockquote>
+        <pre><font size="2">The application crashed. Stack crawl appended below from MacsIssue.</font></pre>
+
+      </blockquote>
+      <p><span class=inputheader>Expected Results:</span> What the application should have done, were the issue not
+      present.
+
+      <blockquote>
+        <pre><font size="2">The window should scroll downwards. Scrolled content should 
+be selected. (Or, at least, the application should not crash.)</font></pre>
+
+      </blockquote>
+      <p><span class=inputheader>Build Date &amp; Platform:</span> Date and platform of the build that you first
+      encountered the issue in.
+
+      <blockquote>
+        <pre><font size="2">11/2/99 build on Mac OS (Checked Viewer &amp; Apprunner)</font></pre>
+
+      </blockquote>
+      <p><span class=inputheader>Additional Builds and Platforms:</span> Whether or not the issue takes place on
+      other platforms or browsers.
+
+      <blockquote>
+        <pre><font size="2"> - Occurs On
+        Seamonkey (11/2/99 build on Windows NT 4.0)
+
+ - Doesn't Occur On
+        Seamonkey (11/4/99 build on Red Hat Linux; feature not supported)
+        Internet Explorer 5.0 (RTM build on Windows NT 4.0)
+        Netscape Communicator 4.5 (RTM build on Mac OS)</font>
+</pre>
+
+      </blockquote>
+      <p><span class=inputheader>Additional Information:</span> Any other distinguishing information. For crashing issues:
+
+      <ul>
+  <li><span class=inputheader>Win32:</span> if you receive a Dr. Watson error, please note the type of the
+  crash, and the module that the application crashed in. (e.g. access violation in
+  apprunner.exe)
+  <li><span class=inputheader>Mac OS:</span> if you're running MacsIssue, please provide the results of a <span class=inputheader><tt>how</tt></span>
+  and an <span class=inputheader><tt>sc</tt></span>.
+  <li><span class=inputheader>Unix: </span>please provide a minimized stack trace, which can be generated by
+  typing <span class=inputheader><tt>gdb apprunner core</tt></span> into a shell prompt.
+      </ul>
+
+
+      <blockquote>
+        <p>
+        <pre><font size="2">*** MACSISSUE STACK CRAWL OF CRASH (Mac OS)
+
+Calling chain using A6/R1 links
+ Back chain  ISA  Caller
+ 00000000    PPC  0BA85E74  
+ 03AEFD80    PPC  0B742248  
+ 03AEFD30    PPC  0B50FDDC  NSGetFactory+027FC
+PowerPC unmapped memory exception at 0B512BD0 NSGetFactory+055F0</font></pre>
+
+      </blockquote>
+
+    </blockquote>
+
+  </blockquote>
+  <p>You're done! <br>
+  <br>
+  After double-checking your entries for any possible errors, press the &quot;Commit&quot;
+  button, and your issue report will now be in the IssueZilla database.<br>
+  <i><br>
+  <br>
+  </i><font size="2">(Thanks to Claudius Gayle, Peter Mock, Chris Pratt, Tom Schutter,
+  and Chris Yeh for contributing to this document. Constructive </font><a href="mailto:eli@prometheus-music.com"><font
+  size="2">suggestions</font></a><font size="2"> welcome.)</font>
+  </blockquote>
+
+ <hr noshade size=1>
+<a href="ProjectIssues.html">Back to Project Issues help</a><br>
+<a href="/servlets/HelpTOC">Back to main Help index</a>
+
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuewritinghelp.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuewritinghelp.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuewritinghelp.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,198 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+  <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+  <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+  <title>Issue writing guidelines</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="issuewritinghelp">
+   <h2>Issue writing guidelines</h2>
+
+   <div id="toc">
+    <ul>
+     <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+    </ul>
+
+    <ul>
+     <li>
+      <a href="/nonav/docs/ProjectIssues.html">Project Issues help</a> 
+
+      <ul>
+       <li><a href="/nonav/docs/issue_lifecycle.html">The issue life cycle</a></li>
+
+       <li>Issue writing guidelines</li>
+
+       <li><a href="/nonav/docs/issuezilla_tipsandtricks.html">IssueZilla tips and tricks</a></li>
+
+       <li><a href="/nonav/docs/contributing_patches.html">Contributing patches</a></li>
+      </ul>
+     </li>
+    </ul>
+   </div>
+   <b>Why you should read this</b> 
+
+   <p>Effective issue reports assist in the process of refining projects and reaching the ultimate goal of completion. This document is designed to provide a brief tutorial in writing effective issue reports.</p>
+   <b>How to write a useful issue report</b> 
+
+   <p>A useful issue report normally has two qualities:</p>
+
+   <ol>
+    <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>
+
+    <li><b>Specific.</b> The quicker the engineer can isolate the issue to a specific problem, the faster the issue can be addressed.</li>
+   </ol>
+
+   <p>For example: you're testing is a web browser. You crash at foo.com, and want to write up an issue report:</p>
+
+   <p><b>Inappropriate:</b> "My browser crashed. I think I was on foo.com. 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 home page doesn't look right, either, it's all messed up. Good luck."</p>
+
+   <p><b>More appropriate:</b> "I crashed each time when I went to foo.com, using the 10.28.99 build on a Win NT 4.0 (Service Pack 5) system. I also rebooted into Linux, and reproduced this problem using the 10.28.99 Linux build.</p>
+
+   <p>It again crashed each time upon drawing the Foo banner at the top of the page. I broke apart the page, and discovered that the following image link will crash the application reproducibly, unless you remove the "border=0" attribute:</p>
+
+   <p>&lt;IMG SRC="http://foo.com/images/topics/topicfoos.gif" width=34 height=44 border=0 alt="News"&gt;"</p>
+   <b>How to Enter your Useful Issue Report into IssueZilla:</b> 
+
+   <p>Before you enter your issue, use the IssueZilla 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.)</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.)</p>
+
+   <p>If you've discovered a new issue using a current build, report it in IssueZilla:</p>
+
+   <ol>
+    <li>From your IssueZilla main page, choose "Enter a new issue".</li>
+
+    <li>Select the product that you've found an issue in.</li>
+
+    <li>Enter your e-mail address, password, and press the "Login" button. (If you don't yet have a password, leave the password text box empty, and press the "E-mail me a password" button instead. You'll receive an E-mail message with your password shortly.)</li>
+   </ol>
+
+   <p>Now, fill out the form. Here's what it all means:</p>
+
+   <p><b>Where did you find the issue?</b> <b>Product</b>: In which product did you find the issue?</p>
+
+   <p>Data for this field was entered on the previous screen.</p>
+   <b>Version</b>: In which product version did you find the issue? 
+
+   <p>Enter, if applicable.</p>
+   <b>Component</b>: In which component does the issue exist? 
+
+   <p>IssueZilla 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.)</p>
+   <b>Platform</b>: On which hardware platform did you find this issue? 
+
+   <p>(e.g., Macintosh, SGI, 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.</p>
+   <b>OS:</b> On which Operating System (OS) did you find this issue? 
+
+   <p>(e.g., Linux, Windows NT, Mac OS 8.5.) If you know the issue happens on all operating systems, choose 'All'. Otherwise, select the OS that you found the issue on, or "Other" if your OS isn't listed.</p>
+
+   <p>How important is the issue?</p>
+   <b>Issue Type</b>: Is this a defect, enhancement, feature-request, or task? 
+
+   <p>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.)</p>
+
+   <p>Who will be following up on the issue?</p>
+
+   <p><b>Assigned To</b>: Which engineer should be responsible for fixing this issue?</p>
+
+   <p>IssueZilla 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.)</p>
+
+   <p><b>NOTE</b>: the assigned to field can be configured as either a drop down box or a text box in which you can manually type the name of the user to be assigned. As a drop down box, the user names listed have direct roles in the project.</p>
+
+   <p><b>Cc</b>: Who else should receive e-mail updates on changes to this issue?</p>
+
+   <p>List the user id of other individuals who should receive an e-mail update upon every change to the issue report. You can enter as many user ids as needed; user ids must be separated by commas, with no spaces between the addresses.</p>
+
+   <p>What else can you tell the engineer about the issue?</p>
+
+   <p><b>URL:</b> On what URL did you discover this issue?</p>
+
+   <p>If you encountered the issue on a particular URL, please provide it (or, them) here. If you've isolated the issue to a specific HTML snippet, please also provide a URL for that, too.</p>
+   <b>Summary</b>: How would you describe the issue, in approximately 60 or fewer characters? 
+
+   <p>A good summary should <em>quickly and uniquely identify an issue report</em>. 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.</p>
+
+   <p>A summary of "PCMCIA install fails on Tosh Tecra 780DVD w/ 3c589C" is a useful title. "Software fails" or "install problem" would be examples of a bad title.</p>
+   <b>Description</b>: What else can you tell the engineer about this issue? 
+
+   <p>Please provide as detailed of a problem diagnosis in this field as possible.</p>
+
+   <p>Where applicable, using the following issue report template will help ensure that all relevant information comes through:</p>
+   <b>Overview Description</b>: More detailed expansion of summary. 
+<pre>
+Drag-selecting any page crashes Mac builds in NSGetFactory
+</pre>
+   <b>Steps to Reproduce</b>: The minimal set of steps necessary to trigger the issue. Include any special setup steps. 
+<pre>
+1) View any web page. (I used the default sample page, 
+   resource:/res/samples/test0.html)
+2) Drag-select the page. (Specifically, while holding down the 
+   mouse button, drag the mouse pointer downwards from any point in 
+   the browser's content region to the bottom of the browser's 
+   content region.)
+</pre>
+   <b>Actual Results:</b> What the application did after performing the above steps. 
+<pre>
+The application crashed. Stack crawl appended below from MacsIssue.
+</pre>
+   <b>Expected Results:</b> What the application should have done, were the issue not present. 
+<pre>
+The window should scroll downwards. Scrolled content should 
+be selected. (Or, at least, the application should not crash.)
+</pre>
+   <b>Build Date &amp; Platform:</b> Date and platform of the build that you first encountered the issue in. 
+<pre>
+11/2/99 build on Mac OS (Checked Viewer &amp; Apprunner)
+</pre>
+   <b>Additional Builds and Platforms:</b> 
+
+   <p>Whether or not the issue takes place on other platforms or browsers.</p>
+<pre>
+- Occurs On
+        Seamonkey (11/2/99 build on Windows NT 4.0)
+
+ - Doesn't Occur On
+        Seamonkey (11/4/99 build on Red Hat Linux; feature not supported)
+        Internet Explorer 5.0 (RTM build on Windows NT 4.0)
+        Netscape Communicator 4.5 (RTM build on Mac OS)
+</pre>
+
+   <h4>Additional Information:</h4>
+
+   <p>Any other distinguishing information. For crashing issues:</p>
+
+   <ul>
+    <li><b>Win32</b>: if you receive a Dr. Watson error, please note the type of the crash, and the module that the application crashed in. (e.g. access violation in apprunner.exe)</li>
+
+    <li><b>Mac OS:</b> if you're running MacsIssue, please provide the results of a <code>how</code> and an <code>sc</code>.</li>
+
+    <li>Unix: please provide a minimized stack trace, which can be generated by typing <code>gdb apprunner core</code> into a shell prompt.</li>
+   </ul>
+<pre>
+*** MACSISSUE STACK CRAWL OF CRASH (Mac OS)
+
+Calling chain using A6/R1 links
+ Back chain  ISA  Caller
+ 00000000    PPC  0BA85E74  
+ 03AEFD80    PPC  0B742248  
+ 03AEFD30    PPC  0B50FDDC  NSGetFactory+027FC
+PowerPC unmapped memory exception at 0B512BD0 NSGetFactory+055F0
+</pre>
+
+   <p>After double-checking your entries for any possible errors, press the "Commit" button, and your issue report will now be in the IssueZilla database.</p>
+
+   <div class="courtesylinks">
+    <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+   </div>
+  </div>
+ </body>
+</html>
+
+

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuezilla_tipsandtricks.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuezilla_tipsandtricks.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuezilla_tipsandtricks.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,129 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Issuezilla Tips and Tricks</title>
+
+
+<!--#include virtual="/google-analytics.js" --> 
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/pl/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/pl/">pl</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/">Archive</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/">trans</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/">docs</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+
+<span class="Header" nowrap>IssueZilla tips and tricks</span>  
+<p>
+    <span class="PlainText"><strong>Additional resources about issues: Index</strong>
+<ul>
+  <dl>
+  <dt><a href="ProjectIssues.html">Project Issues help</a>
+    <dd><a href="issue_lifecycle.html">The issue life cycle</a> 
+    <dd><a href="issuewritinghelp.html">Issue writing guidelines</a>
+    <dd><strong>You are here: IssueZilla tips and tricks</strong> 
+    <dd><a href="contributing_patches.html">Contributing patches</a>
+  <dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+  </dl>
+</ul>
+<hr noshade size=1>
+     <p>
+Here are a few guidelines to help you effectively make use of issue tracking in your collaborative development projects.
+
+     <ul>
+
+      <li>When you see an issue come through email channels, this is
+      an indication that you have either been assigned or cc'd on a
+      particular issue. Don't ignore it!
+
+      <p>
+
+  <li>Make frequent use of the "My issues" option in the
+  IssueZilla tool bar. This list displays all project issues
+  assigned to you.
+
+  <p>
+
+      <li>If you are assigned an issue and you have the bandwith,
+      <strong>it is your responsibility to investigate
+      the issue</strong>. If it has been given a milestone, is also your
+      responsibility to "fix" the issue in the proper order by the
+      designated date, <i>or</i> to communicate the reasons for not
+      meeting the milestone date using the issue "comments" field.
+
+      <p>
+
+      <li>If you are assigned an issue and you do <i>not</i> have enough time to do the work, it is your responsibility to communicate (through the
+      description field) your inability to complete the assignment.
+
+      <p>
+
+      <li>Don't just go and fix issues that have not been given a
+      milestone. It is extremely important for the project leader to
+      carefully consider the impact the milestone's changes might have
+      on the codebase. An issue without a milestone indicates that
+      other factors have yet to be determined.
+
+      <p>
+
+      <li>Proceed through your issues in order sorted by milestone,
+      then by priority. If it makes sense to modify the sequence
+      that's fine, just don't blow the milestone!
+
+      <p>
+
+      <li>When an issue is completed (you've written the code, etc.),
+      if applicable check it into CVS and mark the issue "fixed."
+      Include a comment on how you did it. Fixed=Checked In!
+
+      <p>
+
+      <li>Try not to batch up a bunch of issue fixes and check them in
+      all at once. This wreaks havoc on the project administrator's
+      ability to track status and prohibits granular roll backs, etc.
+
+      <p>
+
+      <li>Feel absolutely positively free to add more issues to the
+      list as you realize them. <strong>Just be sure
+      to query the issue database first to avoid entering duplicate
+      issues!</strong>
+
+      <p>
+
+      <li>Post any and all comments/notes pertaining to a particular
+      issue using the description field. This way anyone who is
+      handling an issue can easily see its history and get to work on it.
+      The issue tracker <strong>must</strong>
+      reflect all of your changes for project release notes to be
+      accurate.
+
+      <p>
+
+      <li>Refer to the issue tracker on an almost constant basis. In
+      practice you'll find that this is a very efficient way of seeing
+      what is expected of you rather than sifting through emails.
+
+     </ul>
+ 
+<p>
+ <hr noshade size=1>
+<a href="ProjectIssues.html">Back to Project Issues help</a><br>
+<a href="/servlets/HelpTOC">Back to main Help index</a>
+
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuezilla_tipsandtricks.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuezilla_tipsandtricks.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/issuezilla_tipsandtricks.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,74 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+  <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+  <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+  <title>IssueZilla tips and tricks</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="issuezillatipsandtricks">
+   <h2>IssueZilla tips and tricks</h2>
+
+   <div id="toc">
+    <ul>
+     <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+    </ul>
+
+    <ul>
+     <li>
+      <a href="/nonav/docs/ProjectIssues.html">Project Issues help</a> 
+
+      <ul>
+       <li><a href="/nonav/docs/issue_lifecycle.html">The issue life cycle</a></li>
+
+       <li><a href="/nonav/docs/issuewritinghelp.html">Issue writing guidelines</a></li>
+
+       <li>IssueZilla tips and tricks</li>
+
+       <li><a href="/nonav/docs/contributing_patches.html">Contributing patches</a></li>
+      </ul>
+     </li>
+    </ul>
+   </div>
+
+   <p>Here are a few guidelines to help you effectively make use of issue tracking in your collaborative development projects.</p>
+
+   <ul>
+    <li>When you see an issue come through email channels, this is an indication that you have either been assigned or cc'd on a particular issue. Don't ignore it!</li>
+
+    <li>Make frequent use of the "My issues" option in the IssueZilla tool bar. This list displays all project issues assigned to you.</li>
+
+    <li>If you are assigned an issue and you have the bandwith, <strong>it is your responsibility to investigate the issue</strong>. If it has been given a milestone, is also your responsibility to "fix" the issue in the proper order by the designated date, <i>or</i> to communicate the reasons for not meeting the milestone date using the issue "comments" field.</li>
+
+    <li>If you are assigned an issue and you do <i>not</i> have enough time to do the work, it is your responsibility to communicate (through the description field) your inability to complete the assignment.</li>
+
+    <li>Don't just go and fix issues that have not been given a milestone. It is extremely important for the project leader to carefully consider the impact the milestone's changes might have on the codebase. An issue without a milestone indicates that other factors have yet to be determined.</li>
+
+    <li>Proceed through your issues in order sorted by milestone, then by priority. If it makes sense to modify the sequence that's fine, just don't blow the milestone!</li>
+
+    <li>When an issue is completed (you've written the code, etc.), if applicable check it into CVS and mark the issue "fixed." Include a comment on how you did it. Fixed=Checked In!</li>
+
+    <li>Try not to batch up a bunch of issue fixes and check them in all at once. This wreaks havoc on the project administrator's ability to track status and prohibits granular roll backs, etc.</li>
+
+    <li>Feel absolutely positively free to add more issues to the list as you realize them. <strong>Just be sure to query the issue database first to avoid entering duplicate issues!</strong></li>
+
+    <li>Post any and all comments/notes pertaining to a particular issue using the description field. This way anyone who is handling an issue can easily see its history and get to work on it. The issue tracker <strong>must</strong> reflect all of your changes for project release notes to be accurate.</li>
+
+    <li>Refer to the issue tracker on an almost constant basis. In practice you'll find that this is a very efficient way of seeing what is expected of you rather than sifting through emails.</li>
+   </ul>
+
+   <div class="courtesylinks">
+    <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+   </div>
+  </div>
+ </body>
+</html>
+
+

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/notargetmilestone.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/notargetmilestone.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/notargetmilestone.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,27 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html>
+ <head>
+  <title>No target milestones</title>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+  <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+  <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs">
+   <h2>Target milestones</h2>
+
+   <p>Milestones are checkpoints within the development process used to track progress of the project. Selecting a milestone helps determine where in the life of the project isseus are found as well as the level of project completion.</p>
+
+   <div class="courtesylinks">
+    <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+   </div>
+  </div>
+ </body>
+</html>
+
+

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/print.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/print.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/print.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,28 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+  <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+  <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+  <title>Print</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="printpages">
+   <h2>Print</h2>
+
+   <p>You can use your browser's print function to capture a hardcopy of any page within the site. With most browsers, the print function will omit frame information, such as banners and navigation bars. Netscape 4.x and earlier browsers are not capable of omitting these elements.</p>
+
+   <div class="courtesylinks">
+    <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+   </div>
+  </div>
+ </body>
+</html>
+
+



Mime
View raw message