Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectHomeView.html.en
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectHomeView.html.en
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectHomeView.html.en
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,56 @@
+<!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>About the Project Home page</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="projecthomeview">
+ <h2>About the Project Home page</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li>
+ <a href="/nonav/docs/Learning.html">Learning about projects</a>
+
+ <ul>
+ <li>Viewing project details</li>
+
+ <li><a href="/nonav/docs/ProjectMail.html#mailsubscribe">About
subscribing to mailing lists</a></li>
+
+ <li><a href="/nonav/docs/ProjectMembershipRequest.html">Joining a
project</a></li>
+
+ <li><a href="/nonav/docs/ProjectRoles.html">Learning about project
roles</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/ProjectMemberResources.html">Project resource
for members</a></li>
+
+ <li><a href="/nonav/docs/hostedtools.html">Hosted tools</a></li>
+
+ <li><a href="/nonav/docs/ProjectAdd.html">Creating a new project</a></li>
+ </ul>
+ </div>
+
+ <p>The <b>Project Home</b> page for any particular project is the project's
focal point with information that the project owner wishes to share with
members and nonmembers alike. Because project home pages can be customized,
these vary greatly, depending on the project owner's preferences. At a minimum,
the owner should include content describing the nature and goals of the
project. Interested users can also use the project's hyperlinks in the left
navigation bar to learn more about the project, including subscribing to that
project's mailing lists.</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/ProjectInvitationHelp.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectInvitationHelp.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectInvitationHelp.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,43 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+<!--#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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<div id="helptext">
+ <table border="0" cellspacing="0" cellpadding="3" width="100%">
+ <tr>
+ <th>How do I...?</th>
+ </tr>
+ <tr>
+ <td>
+ <div> <a href="/project/www/docs/print.html">Print this page</a>...</div>
+ <div></div>
+ </td>
+ </tr>
+ </table>
+</div>
+
+
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectInviteHelp.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectInviteHelp.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectInviteHelp.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,43 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+<!--#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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<div id="helptext">
+ <table border="0" cellspacing="0" cellpadding="3" width="100%">
+ <tr>
+ <th>How do I...?</th>
+ </tr>
+ <tr>
+ <td>
+ <div> <a href="/project/www/docs/print.html">Print this page</a>...</div>
+ <div></div>
+ </td>
+ </tr>
+ </table>
+</div>
+
+
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectIssues.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectIssues.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectIssues.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,206 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Project Resources for Project Members</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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+
+<p>
+<span class=header>Project Issues</span>
+<p>
+<span class="PlainText"><strong>Project resources for project members: Index
+ </strong>
+
+
+<p>
+<ul>
+ <dl>
+ <dt><a href="ProjectMemberResources.html">Project resources for
members</a></a>
+ <dd><a href="ProjectHome.html">Project Home Page</a>
+ <dd><a href="ProjectNews.html">Project News</a>
+ <dd><a href="ProjectDownload.html">Project Download</a>
+ <dd><a href="ProjectMemberList.html">Project Members</a>
+ <dd><a href="ProjectMail.html">Project Mailing Lists</a>
+ <dd><a href="ProjectDocuments.html">Project Documentation</a>
+ <dd><a href="ProjectSource.html">Project Source Code</a>
+ <dd><b>You are here: Project Issues
+ <ul>
+ <li><a href="#accessissues">Accessing project issues
+ <li><a href="#aboutIZ">About the IssueZilla tool</a>
+ <li><a href="#useraccounts">Setting your issue tracking user
preferences</a>
+ <li><a href="#permissions">About your issue tracking
permissions</a></li>
+ </ul></b>
+ <dt><a href="/servlets/HelpTOC">Back to main Help index</a></dt>
+ </dl>
+</ul>
+
+<p>
+<b>More help on issue tracking</b>
+<ul>
+ <dl>
+ <dt><a href="ddIssues_EnterModify.html">Entering and modifying issues</a>
+ <dt><a href="ddIssues_Query.html">Querying and tracking issues</a>
+ <dt><a href="ddIssues_Reports.html">Generating status reports about project
issues</a>
+ <dt><a href="#Moreinfo">More how-to information about issues and issue
tracking</a>
+ </dl>
+</ul>
+
+<p>
+<hr noshade size=1>
+<a name="accessissues"></a><span class="InputHeader">Accessing project
issues</span>
+<p>
+All development activities for each project hosted on
+ this site are tracked in a unique database.
+The <strong>Issue Tracking </strong> link in the Project Resources toolbar
displays the <b>Project Issues</b>
+ page, the entry point to that project's
+ issue database. Issue tracking provides the following benefits:
+ <ol><p><li> Ability to chart the progress of individuals and the
overall project
+
+
+ <li>Tracking and maintainance of project history
+ <li>Generation and reporting of ongoing to-do lists for all project
+ members.</li></ol>
+
+<p>The different sections appearing in the <b>Project Issues</b> page indicate
the following issue tracking options available to you:
+<blockquote>
+<dl>
+<dt><a href="ddIssues_Query.html"><b>Query Database of Issues</b></a>
<dd>Search project issues by number, keywords, assignee, or other criteria.
+<dt><a href="ddIssues_EnterModify.html"><b>Enter An Issue</b></a> <dd>Write
and commit an issue report to the database.
+<dt><a href="ddIssues_Query.html#trackissue"><b>My Issues</b></a> <dd>View a
list of project issues assigned to you.
+<dt><a href="#useraccounts"><b>My Preferences</b></a> <dd>Configure your issue
tracker user settings.</dd>
+</dl>
+</blockquote>
+
+<hr noshade size=1>
+<a name="aboutIZ"></a><span class="InputHeader">About IssueZilla</span>
+<p>
+IssueZilla is the issue tracking tool used on this
+ site. While it is a variant of BugZilla -- a bug tracking system you
+ may already be familiar with-- IssueZilla is a more generalized tool for
+ tracking many different kinds of activities in collaborative development
+ projects. Additionally, IssueZilla does not require a separate login as
BugZilla does. IssueZilla classifies issues into several types:
+ <ul><a href="ddIssues_EnterModify.html#issue_type">
+ <li>Defects (a.k.a. "bugs")
+ <li>Enhancements
+ <li>Features
+ <li>Tasks
+ <li>Patches</a> </li>
+ </ul>
+<p>
+Each hosted project on this site has it's own, unique
+ issues database. For open source projects in IssueZilla, all registered
+ users may query, view, and report issues, while proprietary projects limit
+ access to project members.
+ <p>
+Project members have additional permissions within IssueZilla to modify and
reassign issues, as well as generate reports. Project members are also notified
automatically by email whenever issues are assigned to them or there is
activity on issues affecting their work.
+<p>
+ Entering the tasks you're planning to work on as issues helps you devise and
follow a work plan. Because everyone is aware of each project member's
area of work, you can avoid duplicating efforts and even help out or offer
feedback to other project members. Effective issue tracking requires an
understanding of the IssueZilla tool and a working knowledge of what
constitutes a well-written issue report.
+<p>
+
+<hr noshade size=1>
+ <a name="useraccounts"><span class="InputHeader">Setting your issue
tracking user preferences</span></a><p>
+
+ <p>When you join a hosted development project on this site, you
automatically get an IssueZilla account for access to that project's issues.
+
+ <p>Information about your account is available either
+ by clicking the <strong>My Preferences</strong> link on the <b>Project
Issues</b> page. Once you have entered
+ the issue tracking area of the site you can click on the <strong>Edit
+ prefs </strong> link in the Issue Tracking toolbar, which appears in all
issue tracking screens. You have several options to change your user settings:
+ <p>
+ <dl>
+ <dt><b>Email settings</b>
+ <dd>Controls your automatic email notification settings.
+ <dt><b>Page footer</b>
+ <dd>Include/exclude "My issues" or your named, custom queries in every
IssueZilla page footer.
+ <dt><b>Permissions</b>
+ <dd>Displays your issue tracking permissions but
+ cannot be changed because permissions are assigned by the Project Owner.
+ (See next section.)</dd>
+ </dl>
+
+ <p>
+<hr noshade size=1>
+ <a name="permissions"><span class="InputHeader"> About issue tracking
permissions</span></a>
+<p>
+Once a user becomes a member of a project,
+ he or she is granted additional IssueZilla
+ permissions beyond the default database query capabilities. Permissions
can
+ be viewed by clicking on the <strong>My Preferences</strong>
link on the <b>Project Issues</b> page, or the <strong>Edit Prefs
+ </strong> link in the Issue Tracking toolbar.
+<p>
+ Issue tracking permissions depend upon project role:
+<ul>
+<li>Observers can create and modify issues,
+ but can make changes to only their own issues. Observers have
the ability to comment on any issue.
+<p></p>
+<li>Developers (code or content) can report and
+ modify their own and other project issues. If they have been
+ granted the "Can edit all aspects of any issue" permission, they
have the ability to alter all issue characteristics, including milestones and
issue assignments.
+<p></p>
+<li>Project initiators automatically are granted administrative level
IssueZilla permissions with additional rights to
+ configure issue tracking for the project. Project initiators
can also assign
+ IssueZilla-specific permissions to other project members.</li>
+</ul>
+ Additional permissions can be requested through the project
owner. You may need to request a new project role.
+ <p>
+ Permissions affect the lifecycle and resolution of issues. For
example, if you have the "Can confirm an issue" permission, then you can change
the status of any <b>UNCONFIRMED</b> issue to <b>NEW</b> . A change
in issue status sends an alert to the owner and all other project members
associated with the issue.To understand more about issue status, read more
about the
+ <a href="issue_lifecycle.html">lifecycle of issues</a>.
+ <p>
+
+<hr noshade size=1>
+<a name="Moreinfo"></a><span class="InputHeader">More resources about issues
and issue tracking</span>
+
+ <ul>
+ <li><a href="issue_lifecycle.html">The issue life cycle</a>
+ <li><a href="issuewritinghelp.html">Issue writing guidelines</a>
+ <li><a href="issuezilla_tipsandtricks.html">IssueZilla tips and
tricks</a>
+ <li><a href="contributing_patches.html">Contributing patches</a>
+ <li><a href="http://www.trilobyte.net/barnsons/FAQ.html";
target="_new">BugZilla FAQ</a>**
+ <li><a href="http://www.mozilla.org/quality/help/bugzilla-helper.html";
target="_new">Step-by-step help for bug entry</a>**
+ <li><a href="http://www.mozilla.org/quality/bug-writing-guidelines.html";
target="_new">BugZilla guide to writing good bug reports</a>**
+ <li><a href="http://scarab.tigris.org"; target="_new">Scarab</a>, an open
source issue tracking development
+ project</li>
+ </ul>
+
+ <p><font size="-1"><b><i>**</i></b> These links listed are associated
with BugZilla, but offer useful bug-writing guidelines that are applicable to
IssueZilla. Be aware that there are differences between the two tools. Parts of
BugZilla documentation may not apply or may not address certain features in
IssueZilla, and vice versa. Because IssueZilla is an open source derivative of
BugZilla (version 2.11), it is still a work in progress. For those who are
interested in more information about this, visit <a
href="http://mozilla.org/bugs/";>Mozilla.org</a>.</font>
+
+<p>If you are interested in finding out about other bug tracking systems being
developed, see the <a href="http://scarab.tigris.org"; target="_new">scarab</a>
open source project.
+
+ <p><font size="-1"><b><i>A note about IssueZilla and cookies</i></b> :
Cookies are a prerequisite for creating an account and logging in to
IssueZilla. If cookies are disabled on your system, you will at need to enable
the following cookies: "Issuezilla_login" or "Issuezilla_logincookie." Other
than logging in, IssueZilla uses cookies to cache an issue's current version
and for ordering the most recent query.cgi search during a session.</font>
+<p>
+
+<hr noshade size=1>
+<a href="/servlets/HelpTOC">Back to main Help index</a>
+</span>
+ <p></p>
+ <p></p>
+ <p></p>
+ <p></p>
+ <p></p>
+ <p></p></p>
+</tr>
+</table>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectIssues.html.en
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectIssues.html.en
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectIssues.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>Project File sharing</title>
+ </head>
+
+ <body class="docs" onLoad="self.focus()">
+ <div class="docs" id="projectissues">
+ <h2>Project Issues</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li>
+ <a href="/nonav/docs/ProjectMemberResources.html">Project resources for
members</a>
+
+ <ul>
+ <li><a href="/nonav/docs/Learning.html">Learning about projects</a></li>
+
+ <li><a href="/nonav/docs/ProjectHome.html">Project Home Page</a></li>
+
+ <li><a href="/nonav/docs/ProjectNews.html">Project News</a></li>
+
+ <li><a href="/nonav/docs/ProjectMemberList.html">Project
Membership</a></li>
+
+ <li><a href="/nonav/docs/ProjectMail.html">Project Mailing
Lists</a></li>
+
+ <li><a href="/nonav/docs/ProjectDocuments.html">Project File
sharing</a></li>
+
+ <li><a href="/nonav/docs/ProjectSource.html">Project Source
Code</a></li>
+
+ <li> Project Issue Tracking
+ <ul>
+ <li><a href="#accessissues">Accessing project issues</a></li>
+
+ <li><a href="#aboutIZ">About the IssueZilla tool</a></li>
+
+ <li><a href="#useraccounts">Setting your issue tracking user
preferences</a></li>
+
+ <li><a href="#permissions">About your issue tracking
permissions</a></li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/hostedtools.html">Hosted tools</a></li>
+
+ <li><a href="/nonav/docs/ProjectAdd.html">Creating a new project</a></li>
+ </ul>
+
+ <ul>
+ <li><a href="/nonav/docs/ddIssues_EnterModify.html">Entering and
modifying issues</a></li>
+
+ <li><a href="/nonav/docs/ddIssues_Query.html">Querying and tracking
issues</a></li>
+
+ <li><a href="/nonav/docs/ddIssues_Reports.html">Generating status reports
about project issues</a></li>
+
+ <li><a href="#Moreinfo">More how-to information about issues and issue
tracking</a></li>
+ </ul>
+ </div>
+
+ <h3><a id="accessissues" name="accessissues">Accessing issue
tracking</a></h3>
+
+ <p>All development activities for each project hosted on this site are
tracked in a unique database. The <strong>Issue tracking</strong> link on the
left navigation bar displays the <b>Issue tracking</b> page, the entry point to
that project's issue database. Issue tracking provides the following
benefits:</p>
+
+ <ol>
+ <li>Ability to chart the progress of individuals and the overall
project</li>
+
+ <li>Tracking and maintainance of project history</li>
+
+ <li>Generation and reporting of ongoing to-do lists for all project
members.</li>
+ </ol>
+
+ <p>The different sections appearing in the <b>Issue tracking</b> page
indicate the following issue tracking options available to you:</p>
+
+ <dl>
+ <dt><a href="/nonav/docs/ddIssues_Query.html"><b>Query Database of
Issues</b></a></dt>
+
+ <dd>Search project issues by number, keywords, assignee, or other
criteria.</dd>
+
+ <dt><a href="/nonav/docs/ddIssues_EnterModify.html"><b>Enter An
Issue</b></a></dt>
+
+ <dd>Write and commit an issue report to the database.</dd>
+
+ <dt><a href="/nonav/docs/ddIssues_Query.html#trackissue"><b>My
Issues</b></a></dt>
+
+ <dd>View a list of project issues assigned to you.</dd>
+
+ <dt><a href="#useraccounts"><b>My Preferences</b></a></dt>
+
+ <dd>Configure your issue tracker user settings.</dd>
+ </dl>
+
+ <h3><a id="aboutIZ" name="aboutIZ">About IssueZilla</a></h3>
+
+ <p>IssueZilla is the issue tracking tool used on this site. While it is a
variant of BugZilla -- a bug tracking system you may already be familiar with
-- IssueZilla is a more generalized tool for tracking many different kinds of
activities in collaborative development projects. Additionally, IssueZilla does
not require a separate login as BugZilla does. IssueZilla classifies issues
into several types:</p>
+
+ <ul>
+ <li>Defects (a.k.a. "bugs")</li>
+
+ <li>Enhancements</li>
+
+ <li>Features</li>
+
+ <li>Tasks</li>
+
+ <li>Patches</li>
+ </ul>
+
+ <p>Each hosted project on this site has it's own, unique issues database.
For open source projects in IssueZilla, all registered users may query, view,
and report issues, while proprietary projects limit access to project
members.</p>
+
+ <p>Project members have additional permissions within IssueZilla to modify
and reassign issues, as well as generate reports. Project members are also
notified automatically by email whenever issues are assigned to them or there
is activity on issues affecting their work.</p>
+
+ <p>Entering the tasks you're planning to work on as issues helps you devise
and follow a work plan. Because everyone is aware of each project member's area
of work, you can avoid duplicating efforts and even help out or offer feedback
to other project members. Effective issue tracking requires an understanding of
the IssueZilla tool and a working knowledge of what constitutes a well-written
issue report.</p>
+
+ <h3><a id="useraccounts" name="useraccounts">Setting your issue tracking
user preferences</a></h3>
+
+ <p>When you join a hosted development project on this site, you
automatically get an IssueZilla account for access to that project's issues.</p>
+
+ <p>Information about your account is available either by clicking the
<strong>My Preferences</strong> link on the <b>Issue Tracking</b> page. Once
you have entered the issue tracking area of the site you can click on the
<strong>Edit prefs</strong> link. You have several options to change your user
settings:</p>
+
+ <dl>
+ <dt>Email settings</dt>
+
+ <dd>Controls your automatic email notification settings.</dd>
+
+ <dt>Page footer</dt>
+
+ <dd>Include/exclude "My issues" or your named, custom queries in every
IssueZilla page footer.</dd>
+
+ <dt>Permissions</dt>
+
+ <dd>Displays your issue tracking permissions but cannot be changed because
permissions are assigned by the Project Owner. (See next section.)</dd>
+ </dl>
+
+ <h3><a id="permissions" name="permissions">About issue tracking
permissions</a></h3>
+
+ <p>Once a user becomes a member of a project, he or she is granted
additional IssueZilla permissions beyond the default database query
capabilities. Permissions can be viewed by clicking on the <strong>My
Preferences</strong> link on the <b>Issue tracking</b> page, or the <strong>My
preferences</strong> link on the Issues page.</p>
+
+ <p>Issue tracking permissions depend upon project role:</p>
+
+ <ul>
+ <li>Observers can create and modify issues, but can make changes to only
their own issues. Observers have the ability to comment on any issue.</li>
+
+ <li>Developers (code or content) can report and modify their own and other
project issues. If they have been granted the "Can edit all aspects of any
issue" permission, they have the ability to alter all issue characteristics,
including milestones and issue assignments.</li>
+
+ <li>Project initiators automatically are granted administrative level
IssueZilla permissions with additional rights to configure issue tracking for
the project. Project initiators can also assign IssueZilla-specific permissions
to other project members.</li>
+ </ul>
+
+ <p>Additional permissions can be requested through the project owner. You
may need to request a new project role.</p>
+
+ <p>Permissions affect the lifecycle and resolution of issues. For example,
if you have the "Can confirm an issue" permission, then you can change the
status of any <b>UNCONFIRMED</b> issue to <b>NEW</b> . A change in issue status
sends an alert to the owner and all other project members associated with the
issue.To understand more about issue status, read more about the <a
href="/nonav/docs/issue_lifecycle.html">lifecycle of issues</a>.</p>
+
+ <h3><a id="Moreinfo" name="Moreinfo">More resources about issues and issue
tracking</a></h3>
+
+ <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><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>
+
+ <li><a href="http://www.trilobyte.net/barnsons/FAQ.html";>BugZilla
FAQ</a>**</li>
+
+ <li><a
href="http://bugzilla.mozilla.org/enter_bug.cgi?format=guided";>Step-by-step
help for bug entry</a>**</li>
+
+ <li><a
href="http://www.mozilla.org/quality/bug-writing-guidelines.html";>BugZilla
guide to writing good bug reports</a>**</li>
+
+ <li><a href="http://scarab.tigris.org";>Scarab</a>, an open source issue
tracking development project</li>
+ </ul>
+
+ <p><b><i>**</i></b> These links listed are associated with BugZilla, but
offer useful bug-writing guidelines that are applicable to IssueZilla. Be aware
that there are differences between the two tools. Parts of BugZilla
documentation may not apply or may not address certain features in IssueZilla,
and vice versa. Because IssueZilla is an open source derivative of BugZilla
(version 2.11), it is still a work in progress. For those who are interested in
more information about this, visit <a
href="http://mozilla.org/bugs/";>Mozilla.org</a>.</p>
+
+ <p>If you are interested in finding out about other bug tracking systems
being developed, see the <a href="http://scarab.tigris.org";>scarab</a> open
source project.</p>
+
+ <p><b><i>A note about IssueZilla and cookies</i></b> : Cookies are a
prerequisite for creating an account and logging in to IssueZilla. If cookies
are disabled on your system, you will at need to enable the following cookies:
"Issuezilla_login" or "Issuezilla_logincookie." Other than logging in,
IssueZilla uses cookies to cache an issue's current version and for ordering
the most recent query.cgi search during a session.</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/ProjectIssuesHelp.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectIssuesHelp.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectIssuesHelp.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,133 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+<!--#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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<!-- Help Text Box -->
+<table border="0" cellspacing="0" cellpadding="3" border="0" width="100%">
+ <tr>
+ <td class="HelpText" bgcolor="#ffcc66"><img
src="/branding/images/pixel.gif" height="1" width="135"><br>
+<b>How do I...?</b></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc">
+
+ <table border="0" cellspacing="0" cellpadding="0" border="0"
width="100%">
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" class="HelpText"><a
href="/project/www/docs/ProjectIssues.html#accessissues">View issues...</a></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffcc66" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffcc66" height="1"><spacer type="block"
height="1"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+
+
+<tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" class="HelpText"><a
href="/project/www/docs/ddIssues_EnterModify.html">Enter an issue...</a></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffcc66" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffcc66" height="1"><spacer type="block"
height="1"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" class="HelpText"><a
href="/project/www/docs/ddIssues_Query.html">Search this project's
issues...</a></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffcc66" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffcc66" height="1"><spacer type="block"
height="1"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" class="HelpText"><a
href="/project/www/docs/ProjectIssues.html#aboutIZ">Learn more about
IssueZilla...</a></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffcc66" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffcc66" height="1"><spacer type="block"
height="1"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" class="HelpText"><a
href="/project/www/docs/ProjectIssues.html#useraccounts">Set my issue tracking
preferences...</a></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffcc66" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffcc66" height="1"><spacer type="block"
height="1"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" class="HelpText"><a
href="/project/www/docs/ProjectIssues.html#permissions">Find out about my issue
tracking permissions...</a></td>
+ </tr>
+ <tr>
+ <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td>
+ <td bgcolor="#ffffcc" height="2"><spacer type="block"
height="2"></td>
+ </tr>
+ </table>
+
+ </td>
+ </tr>
+</table>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectListHelp.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectListHelp.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectListHelp.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,43 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+<!--#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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<div id="helptext">
+ <table border="0" cellspacing="0" cellpadding="3" width="100%">
+ <tr>
+ <th>How do I...?</th>
+ </tr>
+ <tr>
+ <td>
+ <div> <a href="/project/www/docs/print.html">Print this page</a>...</div>
+ <div></div>
+ </td>
+ </tr>
+ </table>
+</div>
+
+
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectLockedHelp.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectLockedHelp.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectLockedHelp.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,43 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+<!--#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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<div id="helptext">
+ <table border="0" cellspacing="0" cellpadding="3" width="100%">
+ <tr>
+ <th>How do I...?</th>
+ </tr>
+ <tr>
+ <td>
+ <div> <a href="/project/www/docs/print.html">Print this page</a>...</div>
+ <div></div>
+ </td>
+ </tr>
+ </table>
+</div>
+
+
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMail.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMail.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMail.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,161 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Project Mailing Lists</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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+
+<p>
+<span class="Header">Project Mailing Lists</span>
+<p>
+<span class="PlainText" nowrap><b>Project resources for members: Index</b>
+<p>
+ <ul>
+ <dl>
+ <dt><a href="ProjectMemberResources.html">Project resources for members</a>
+ <dd><a href="ProjectHome.html">Project Home Page</a>
+ <dd><a href="ProjectNews.html">Project News</a>
+ <dd><a href="ProjectDownload.html">Project Download</a>
+ <dd><a href="ProjectMemberList.html">Project Members</a>
+ <dd><b>You are here: Project Mailing Lists
+ <ul>
+ <li><a href="#aboutmail">About project mailing lists</a>
+ <li><a href="#mailsubscribe">Subscribing and unsubscribing</a>
+ <li><a href="#mailfeatures">Other mailing list features</a>
+ <li><a href="#mailarchives">Mailing list archives</a>
+ </ul></b>
+ <dd><a href="ProjectDocuments.html">Project Documentation</a>
+ <dd><a href="ProjectSource.html">Project Source Code</a>
+ <dd><a href="ProjectIssues.html">Project Issues</a>
+ <dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+ </dl>
+</ul>
+<p>
+
+ <hr noshade size=1>
+<span class="InputHeader"><a name="aboutmail"></a>About project mailing
lists</span>
+<span class="PlainText">
+ <p>Mailing lists provide a way for developers and other interested
parties to communicate with one another about aspects of a project, and to
receive project announcements. In general, the way mailing lists work depends
upon the type of project:
+<ul>
+<li>Open source project mailing lists are available to any subscriber, but
may be granted limited membership by the project owners.
+<p></p>
+<li>Proprietary project mailing lists are always private; only approved
subscribers, usually project members, may join.</li>
+</ul>
+<p>
+Development projects on this site include one or more of the following mailing
lists:
+
+ <blockquote>
+ <dl>
+ <dt><b>[email protected]</b>
+<dd>The main list for developers to discuss specific project development
issues and requirements for version control in the project.
+<p>
+ <dt><b>[email protected]</b>
+<dd>Automated notifications of file version control changes and discussion of
those changes.
+<p>
+ <dt><b>[email protected]</b>
+<dd>Announcements of new releases and other major project events.
+<p>
+ <dt><b>issues@[email protected]</b>
+<dd>Automated notifications and discussions of the project's reported issues
(defects, enhancements, features, tasks, and patches) and changes made to
issues, such as reassignment, comments, or resolution.
+<p>
+ <dt><b>[email protected]</b>
+<dd>A more general discussion list for the project's end users.
+ </dl>
+ </blockquote>
+<p>
+
+<hr noshade size=1>
+<a name="mailsubscribe"></a><span class="InputHeader">Subscribing and
unsubscribing</span>
+
+<p>
+You can subscribe or unsubscribe to mailing lists for a particular project by
selecting "Mailing Lists" in the Project Resources tool bar.
+<p>
+The <b>Project Mail</b> page includes subscribe/unsubscribe links for either a
message-by-message or digest version of the list, as well as options to view
each project list's archives.
+<p>
+
+To begin the subscription process, click on the hyperlinked mailing list
address to which you want to subscribe and send the message from your email
client.
+<p>
+You should receive a response asking for a confirmation. After you reply as
indicated in the email, you will receive an email welcoming you and
acknowledging your successful mailing list subscription. </li>
+</ul>
+Follow the same process for unsubscribing, but substitute the
<strong>unsubscribe</strong> link.
+<p>
+Once on the <b>Mailing Lists</b> page, you can view the project mailing list
archives by clicking on the "view archive" link next to the mailing list title
for that list. Click on the date range and subject links to specify the sort of
messages you want to see.
+<p>
+All mailing lists associated with the project are listed here. The links on
this page allow you to subscribe (or unsubscribe) to the available mailing
lists.
+<p>
+Most lists also have a corresponding "digest" version -- if you subscribe to
this you receive a single daily email with all of that day's postings.
+
+<p>
+<hr noshade size=1>
+<span class="InputHeader"><a name="mailfeatures"></a>Other mailing list
features</span>
+
+ <dl>
+ <dt><b>Posting a message</b>
+<dd>To post a message to a mailing list for a project, send your message
to:<br>
+ <b>[email protected]</b><br>
+ For example, to post a message to the developer mailing list in project
platform, send email to:<br>
+ <b>[email protected]</b>
+<p>
+ <dt><b>Getting help</b>
+<dd>To get an automated help message for a mailing list, send a blank email
message to:<br>
+ <b>[email protected]</b><br>
+For example, for the dev mailing list in project platform, send email to:<br>
+ <b>[email protected]</b>
+<p>
+<dt><b>Contact list moderator</b>
+<dd>To communicate with the list moderator, send an email message to:<br>
+ <b>[email protected]</b>
+ </dl>
+
+ <p>
+<hr noshade size=1>
+<span class="InputHeader"><a name="mailarchives">Mailing list
archives</a></span>
+ <p>Project/component mailing list archiving is handled by <a
href="http://eyebrowse.tigris.org/"; target="_new">EyeBrowse</a>, an open source
tool that stores and
+ indexes list messages, providing multiple options for browsing, reading,
and
+ searching mailing list archives via a web browser. Beyond storing
messages,
+ EyeBrowse adds a database and text indexing engine to handle rapid message
+ search and retrieval.
+ <p>To view a mailing list's archives, select the <strong>Mailing
+ List</strong>
+ option in the Project Resources tool bar to see a list of all
+ mailing lists for that project. Click on the <strong>View Archive
+ </strong>link next to the list you want to
+ view. The default view for browsing mailing list archives is by date
+ summary. Other summary views available are: by <strong>Author</strong>, by
+ <strong>Subject</strong>, and by <strong>Thread</strong>.</p>
+ <p>You can use the <strong>Search Archive </strong>link to add filters to
+ your search criteria. You can enter a search text and choose to sort by
+ <strong>Subject</strong>, <strong>Author</strong>, or <strong>Body
+ </strong>by choosing one from the drop down box under the text box. You
can
+ also search text strings of the archived messages using simple
Boolean
+ operators. </p>
+<hr noshade size=1>
+ <a href="/servlets/HelpTOC">Back to main Help index</a>
+
+</span>
+</span>
+
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMail.html.en
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMail.html.en
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMail.html.en
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,160 @@
+<!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>Project Mailing Lists</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="projectmail">
+ <h2>Project Mailing Lists</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li><a href="/nonav/docs/Learning.html">Learning about projects</a></li>
+
+ <li>
+ <a href="/nonav/docs/ProjectMemberResources.html">Project resources for
members</a>
+
+ <ul>
+ <li><a href="/nonav/docs/ProjectHome.html">Project Home Page</a></li>
+
+ <li><a href="/nonav/docs/ProjectNews.html">Project News</a></li>
+
+ <li><a href="/nonav/docs/ProjectMemberList.html">Project
Membership</a></li>
+
+ <li>
+ Project Mailing Lists
+
+ <ul>
+ <li><a href="#aboutmail">About project mailing lists</a></li>
+
+ <li><a href="#mailsubscribe">Subscribing and unsubscribing</a></li>
+
+ <li><a href="#mailfeatures">Other mailing list features</a></li>
+
+ <li><a href="#mailarchives">Mailing list archives</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/ProjectDocuments.html">File sharing</a></li>
+
+ <li><a href="/nonav/docs/ProjectSource.html">Project Source
Code</a></li>
+
+ <li><a href="/nonav/docs/ProjectIssues.html">Issue Tracking</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/hostedtools.html">Hosted tools</a></li>
+
+ <li><a href="/nonav/docs/ProjectAdd.html">Creating a new project</a></li>
+ </ul>
+ </div>
+
+ <h3><a id="aboutmail" name="aboutmail">About project mailing lists</a></h3>
+
+ <p>Mailing lists provide a way for developers and other interested parties
to communicate with one another about aspects of a project, and to receive
project announcements. In general, the way mailing lists work depends upon the
type of project:</p>
+
+ <ul>
+ <li>Open source project mailing lists are available to any subscriber, but
may be granted limited membership by the project owners.</li>
+
+ <li>Proprietary project mailing lists are always private; only approved
subscribers, usually project members, may join.</li>
+ </ul>
+
+ <p>Development projects on this site include one or more of the following
mailing lists:</p>
+
+ <dl>
+ <dt>[email protected]</dt>
+
+ <dd>The main list for developers to discuss specific project development
issues and requirements for version control in the project.</dd>
+
+ <dt>[email protected]</dt>
+
+ <dd>Automated notifications of file version control changes and discussion
of those changes.</dd>
+
+ <dt>[email protected]</dt>
+
+ <dd>Announcements of new releases and other major project events.</dd>
+
+ <dt>issues@[email protected]</dt>
+
+ <dd>Automated notifications and discussions of the project's reported
issues (defects, enhancements, features, tasks, and patches) and changes made
to issues, such as reassignment, comments, or resolution.</dd>
+
+ <dt>[email protected]</dt>
+
+ <dd>A more general discussion list for the project's end users.</dd>
+ </dl>
+
+ <h3><a id="mailsubscribe" name="mailsubscribe">Subscribing and
unsubscribing</a></h3>
+
+ <p>You can subscribe or unsubscribe to mailing lists for a particular
project by selecting "Mailing Lists" on the left navigation bar.</p>
+
+ <p>The <b>Project Mail</b> page includes subscribe/unsubscribe links for
either a message-by-message or digest version of the list, as well as options
to view each project list's archives.</p>
+
+ <p>To begin the subscription process, click on the hyperlinked mailing list
address to which you want to subscribe and send the message from your email
client.</p>
+
+ <p>You should receive a response asking for a confirmation. After you reply
as indicated in the email, you will receive an email welcoming you and
acknowledging your successful mailing list subscription. Follow the same
process for unsubscribing, but substitute the <strong>unsubscribe</strong>
link.</p>
+
+ <p>Once on the <b>Mailing Lists</b> page, you can view the project mailing
list archives by clicking on the "view archive" link next to the mailing list
title for that list. Click on the date range and subject links to specify the
sort of messages you want to see.</p>
+
+ <p>All mailing lists associated with the project are listed here. The links
on this page allow you to subscribe (or unsubscribe) to the available mailing
lists.</p>
+
+ <p>Most lists also have a corresponding "digest" version -- if you
subscribe to this you receive a single daily email with all of that day's
postings.</p>
+
+ <h3><a id="mailfeatures" name="mailfeatures">Other mailing list
features</a></h3>
+
+ <dl>
+ <dt>Posting a message</dt>
+
+ <dd>To post a message to a mailing list for a project, send your message
to: <b>[email protected]</b>. For example, to post a message to the
developer mailing list in project platform, send email to:
<b>[email protected]</b></dd>
+
+ <dt>Getting help</dt>
+
+ <dd>To get an automated help message for a mailing list, send a blank
email message to: <b>[email protected]</b>. For example, for the
dev mailing list in project platform, send email to:
<b>[email protected]</b></dd>
+
+ <dt>Contact list moderator</dt>
+
+ <dd>To communicate with the list moderator, send an email message to:
<b>[email protected]</b></dd>
+ </dl>
+
+ <h3><a id="mailarchives" name="mailarchives">Mailing list archives</a></h3>
+
+ <p>Project/component mailing list archiving is handled by <a
href="http://eyebrowse.tigris.org/";>EyeBrowse</a>, an open source tool that
stores and indexes list messages, providing multiple options for browsing,
reading, and searching mailing list archives via a web browser. Beyond storing
messages, EyeBrowse adds a database and text indexing engine to handle rapid
message search and retrieval.</p>
+
+ <p>To view a mailing list's archives, select the <strong>Mailing
List</strong> link in the Project section of the left navigation bar to see a
list of all mailing lists for that project. Click on the <strong>View
Archive</strong> link next to the list you want to view. The default view for
browsing mailing list archives is by date summary. Other summary views
available are: by <strong>Author</strong>, by <strong>Subject</strong>, and by
<strong>Thread</strong>.</p>
+
+ <p>The <b>Date</b>, <b>Author</b>, <b>Subject</b>, and <b>Thread</b> views
use unique parameters to sort through and display mail items in the archive.</p>
+
+ <p>The <b>Date</b> parameter groups mail items by year and month; all mail
items received in the month of May 2001 will be grouped in one category, while
all items received in January of 2000 will be grouped in another category. A
group of all mail items is also provided for convenience. You have the option
of viewing all mail items or selecting a particular month and year for viewing.
By clicking on the link to your preferred grouping, mail items are presented
for that grouping in date order, with the eldest first and the newest last.</p>
+
+ <p>The <b>Author</b> parameter groups mail items by the author. Each author
is represented as a grouping. Mail items that are responses to another item are
included in the group attributeted to the respondent, and not by the original
message author. Clicking on the link attached to the author's name will provide
a list of all mail items generated by that author in ascending date order.</p>
+
+ <p>The <b>Subject</b> parameter groups mail items by the original subject.
Each subject is represented as a grouping of mail items. Clicking on link to a
subject will provide a list of all mail items pertaining to that subject in
ascending order of receipt.</p>
+
+ <p>The <b>Thread</b> parameter groups mail items by conversation. Each
thread is represented by a grouping of mail items. Clickin on the link to a
thread will provide a list of mail items pertaining to that thread in ascending
order of receipt.</p>
+
+ <p>A mail list conversation occurs when 1). there is one or more responses
to a mail item, and, 2). the mail program used to create the original item and
the responses are capable of tracking the "in-reply-to" or "references"
headers. If your mail application can support SMTP then any response you
generate to a mail item will be viewable in a thread sort.</p>
+
+ <p>The <b>Subject</b> and <b>Thread</b> parameters appear to be very
similar in function. The difference between them is that the <b>Subject</b>
parameter sorts specifically on the subject headers of all emails. That is, all
email messages with substantially similar subject headings will appear in the
same grouping. For example, the "this is it" and "RE: this is it" email
messages will appear in the same grouping. The <b>Thread</b> grouping, on the
other hand, relies on the "in-reply-to" or "references" headers of email
messages to establish appropriate groupings. Not all email applications are
capable of tracking either the "in-reply-to" or the "references" headers. This
results in messages that you might expect to be co-members of a <b>Thread</b>
grouping will not appear together. Further, since the <b>Thread</b> grouping is
intended to track conversations, more than one email message is required for a
grouping to be created. The email message with the subject heading "this is
not it" and nothing in the "in-reply-to" or "references" headers will not
appear in any <b>Thread</b> grouping. Two email messages with the same subject
header but with nothing in either the "in-reply-to" or the "references" headers
will, likewise, not be grouped. Determining which parameter to choose,
<b>Subject</b> or <b>Thread</b> will depend upon what your needs are. If you
are most interested in finding email with the same subject, the the
<b>Subject</b> parameter is appropriate. If you are most interested in tracking
a conversation taking place in email and are not concerned by missing some
email that are members of no conversations or were written using email software
that is incapable of tracking the "in-reply-to" or "references" headers, the
<b>Thread</b> parameter is appropriate.</p>
+
+ <p>You can use the <strong>Search Archive</strong> link to add filters to
your search criteria. You can enter a search text and choose to sort by
<strong>Subject</strong>, <strong>Author</strong>, or <strong>Body</strong> by
choosing one from the drop down box under the text box. You can also search
text strings of the archived messages using simple Boolean operators.</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/ProjectMailHelp.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMailHelp.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMailHelp.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,99 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+<!--#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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<!-- Help Text Box -->
+<TABLE BORDER="0" CELLSPACING="0" CELLPADDING="3" BORDER="0" WIDTH="100%">
+ <TR>
+ <TD CLASS="HelpText" BGCOLOR="#ffcc66"><IMG
SRC="/branding/images/pixel.gif" HEIGHT="1" WIDTH="135"><BR>
+<b>How do I...?</b></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc">
+
+ <TABLE BORDER="0" CELLSPACING="0" CELLPADDING="0" BORDER="0"
WIDTH="100%">
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMail.html#aboutmail">What is a mailing
list?</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffcc66" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffcc66" HEIGHT="1"><SPACER TYPE="block"
HEIGHT="1"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMail.html#mailsubscribe">How do I join a mailing
list?</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffcc66" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffcc66" HEIGHT="1"><SPACER TYPE="block"
HEIGHT="1"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMail.html#mailfeatures">What can I do with a
mailing list?</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffcc66" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffcc66" HEIGHT="1"><SPACER TYPE="block"
HEIGHT="1"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMail.html#mailarchives">How do I view old
messages in the list?</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ </TABLE>
+
+ </TD>
+ </TR>
+</TABLE>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMailingListListHelp.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMailingListListHelp.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMailingListListHelp.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,99 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+<!--#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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<!-- Help Text Box -->
+<TABLE BORDER="0" CELLSPACING="0" CELLPADDING="3" BORDER="0" WIDTH="100%">
+ <TR>
+ <TD CLASS="HelpText" BGCOLOR="#ffcc66"><IMG
SRC="/branding/images/pixel.gif" HEIGHT="1" WIDTH="135"><BR>
+<b>How do I...?</b></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc">
+
+ <TABLE BORDER="0" CELLSPACING="0" CELLPADDING="0" BORDER="0"
WIDTH="100%">
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMail.html#aboutmail">Learn about project mailing
lists...</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffcc66" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffcc66" HEIGHT="1"><SPACER TYPE="block"
HEIGHT="1"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMail.html#mailsubscribe">Join a mailing
list...</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffcc66" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffcc66" HEIGHT="1"><SPACER TYPE="block"
HEIGHT="1"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMail.html#mailfeatures">Use mailing
lists...</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffcc66" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffcc66" HEIGHT="1"><SPACER TYPE="block"
HEIGHT="1"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMail.html#mailarchives">View older messages in
lists...</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ </TABLE>
+
+ </TD>
+ </TR>
+</TABLE>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMailingListListTasks.html.en
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMailingListListTasks.html.en
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMailingListListTasks.html.en
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,7 @@
+Tasks :
+<div class="pipelinks">
+ #if( $acl.hasPermission("Mailing List - Add", $currentProject) )
+ <a href="$currentProject.getProjectPageURL("MailingListAdd")">Add
+ New Mailing List</a>
+ #end
+</div>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberList.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberList.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberList.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,68 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<TITLE>Project Members</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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
+ <TR>
+<P>
+<SPAN CLASS="Header">Project Members</SPAN>
+<P>
+<SPAN CLASS="PlainText"><B>Project resources for members: Index</B>
+<P>
+ <UL>
+ <DL>
+ <DT><A HREF="ProjectMemberResources.html">Project resources for members</A>
+ <DD><A HREF="ProjectHome.html">Project Home Page</A>
+ <DD><A HREF="ProjectNews.html">Project News</A>
+ <DD><A HREF="ProjectDownload.html">Project Download</A>
+ <DD><B>You are here: Project Members</B>
+ <DD><A HREF="ProjectMail.html">Project Mailing Lists</A>
+ <DD><A HREF="ProjectSource.html">Project Source Code</A>
+ <DD><A HREF="ProjectIssues.html">Project Issues</A>
+ <DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
+ </DL>
+</UL>
+<P>
+
+<HR NOSHADE SIZE=1>
+<SPAN CLASS="InputHeader">Project Members</SPAN>
+
+<P>The <B>Project Members</B> page lists all project members by name and their
roles within that project. Following the associated <I>View Issues</I> links
displays a listing of all project issues assigned to project members. Each
project is configured differently; depending on a particular project's
configuration, you can:
+
+<UL>
+<LI>View project issues assigned to yourself and to other members.
+<LI>Request a new project role.
+</UL>
+<P>
+Requests for new roles must be approved at the discretion of the Project
Owner. The nature of your participation in any project is predicated upon these
roles. If you have any questions about a role assignment, you should contact
the Project Owner directly. Your ability to conduct various project activities
is governed by certain permissions associated with different roles. To learn
about the meaning of any role, please see our documentation on <A
HREF="ProjectRoles.html">project roles.</A>
+<P>
+
+<HR NOSHADE SIZE=1>
+<A HREF="/servlets/HelpTOC">Back to main Help index</A>
+</SPAN>
+</TR>
+</TABLE>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberList.html.en
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberList.html.en
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberList.html.en
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,77 @@
+<!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>Project Membership</title>
+ </head>
+
+ <body class="docs" onLoad="self.focus()">
+ <div class="docs" id="projectmemberlist">
+ <h2>Project Membership</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li><a href="/nonav/docs/Learning.html">Learning about projects</a></li>
+
+ <li>
+ <a href="/nonav/docs/ProjectMemberResources.html">Project resources for
members</a>
+
+ <ul>
+ <li><a href="/nonav/docs/ProjectHome.html">Project Home Page</a></li>
+
+ <li><a href="/nonav/docs/ProjectNews.html">Project News</a></li>
+
+ <li>Project Membership</li>
+
+ <li><a href="/nonav/docs/ProjectMail.html">Project Mailing
Lists</a></li>
+
+ <li><a href="/nonav/docs/ProjectDocuments.html">Project File
Sharing</a></li>
+
+ <li><a href="/nonav/docs/ProjectSource.html">Project Source
Code</a></li>
+
+ <li><a href="/nonav/docs/ProjectIssues.html">Project Issue
Tracking</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/hostedtools.html">Hosted tools</a></li>
+
+ <li><a href="/nonav/docs/ProjectAdd.html">Creating a new project</a></li>
+ </ul>
+ </div>
+
+ <h3>Project Members</h3>
+
+
+ <p>The <b>Project Membership</b> page lists all project members by name and
+ their roles within that project. Following the associated <i>View
Issues</i>
+ links displays a listing of all project issues assigned to project
members.
+ Each project is configured differently; depending on a particular
project's
+ configuration, you can:</p>
+
+ <ul>
+ <li>View project issues assigned to yourself and to other members.</li>
+
+ <li>Request a new project role.</li>
+ </ul>
+
+ <p>Requests for new roles must be approved at the discretion of the Project
Owner. The nature of your participation in any project is predicated upon these
roles. If you have any questions about a role assignment, you should contact
the Project Owner directly. Your ability to conduct various project activities
is governed by certain permissions associated with different roles. To learn
about the meaning of any role, please see our documentation on <a
href="/nonav/docs/ProjectRoles.html">project roles.</a></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/ProjectMemberListTasks.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberListTasks.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberListTasks.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,68 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+<!--#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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+#set($myRoles = $loginUser.getRolesInProject($currentProject))
+#set($myRequestedRoles =
$loginUser.getRequestedRolesInProject($currentProject))
+
+#if($currentProject.isCategory())
+ #set($projectType = "Category" )
+#elseif($currentProject.isGroup())
+ #set($projectType = "Group" )
+#else
+ #set($projectType = "Project")
+#end
+
+Tasks :
+<div class="pipelinks">
+ #set ($displayPipe=false)
+ #if($acl.hasPermission("Project - Invite", $currentProject))
+ #set ($displayPipe=true)
+ <a href="$currentProject.getProjectPageURL("ProjectInvite")">Invite
+ New Members</a>
+ #end
+
+ #if($displayPipe) | #end
+
+ #if(!project.isCategory())
+ #set ($displayPipe=true)
+ #if($myRoles.isEmpty() && $myRequestedRoles.isEmpty())
+ #set ($joinMessage="Join This $projectType")
+ #else
+ #set ($joinMessage="Request New Role")
+ #end
+ <a
href="$currentProject.getProjectPageURL("ProjectMembershipRequest")">$joinMessage</a>
+ #end
+
+ #if($acl.hasPermission("Role - Grant", $currentProject))
+ #if ($displayPipe) | #end
+ <a href="$currentProject.getProjectPageURL("ProjectMemberAdd")">Add New
+ Members</a>
+ #end
+ #end
+</div>
+
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberResources.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberResources.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberResources.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,71 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Project resources for members</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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<span class="Header">Project resources for members</span>
+<p>
+<span class="PlainText">
+<p>
+<b>Project resources for members: Index</b>
+
+<ul>
+ <dl>
+ <dt><b>You are here: Project resources for members</b></dt>
+ <dd><a href="ProjectHome.html">Project Home Page</a>
+ <dd><a href="ProjectNews.html">Project News</a>
+ <dd><a href="ProjectDownload.html">Project Files</a>
+ <dd><a href="ProjectMembers.html">Project Members</a>
+ <dd><a href="ProjectMail.html">Project Mailing Lists</a>
+ <dd><a href="ProjectDocuments.html">Project Documentation</a>
+ <dd><a href="ProjectSource.html">Project Source Code</a>
+ <dd><a href="ProjectIssues.html">Project Issues</a>
+ <dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+ </dl>
+</ul>
+
+<hr noshade size=1>
+
+<p>
+Development activity for projects hosted on this site is handled through an
integrated set of tools. Project owners and members use these tools to
communicate with each other and coordinate their work. The <b>Project Home</b>
page serves as the project's focal point. The Project Resources tool bar
appears on all project pages, providing links to hosted tools and specific
project data including:
+<ul>
+<li>Developer participants and other project members
+<li>Project announcements and news
+<li>File downloads and project documents
+<li>Mailing list subscriptions and access to list archives
+<li>Source code browsing and repository access
+<li>Issue (bug) querying and reporting.
+</ul>
+<p>
+The help documents associated with each of these resources are generally
addressed to project members, but non-member users also have read-only access
to these same project resource screens for any hosted projects publicly listed
on this site. These users cannot, however, modify files or contribute source
code until being approved as members with specific project roles.
+<p>
+
+<hr noshade size=1>
+<a href="/servlets/HelpTOC">Back to main Help index</a></p>
+
+</span>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added:
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberResources.html.en
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberResources.html.en
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMemberResources.html.en
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,78 @@
+<!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>Project resources for members</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="projectmemberresources">
+ <h2>Project resources for members</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li><a href="/nonav/docs/Learning.html">Learning about projects</a></li>
+
+ <li>
+ Project resources for members
+
+ <ul>
+ <li><a href="/nonav/docs/ProjectHome.html">Project Home Page</a></li>
+
+ <li><a href="/nonav/docs/ProjectNews.html">Project News</a></li>
+
+ <li><a href="/nonav/docs/ProjectMemberList.html">Project
Membership</a></li>
+
+ <li><a href="/nonav/docs/ProjectMail.html">Project Mailing
Lists</a></li>
+
+ <li><a href="/nonav/docs/ProjectDocuments.html">File sharing</a></li>
+
+ <li><a href="/nonav/docs/ProjectSource.html">Project Source
Code</a></li>
+
+ <li><a href="/nonav/docs/ProjectIssues.html">Issue Tracking</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/hostedtools.html">Hosted tools</a></li>
+
+ <li><a href="/nonav/docs/ProjectAdd.html">Creating a new project</a></li>
+ </ul>
+ </div>
+
+ <p>Development activity for projects hosted on this site is handled through
an integrated set of tools. Project owners and members use these tools to
communicate with each other and coordinate their work. The <b>Project Home</b>
page serves as the project's focal point. The navigation bar appears on all
project pages, providing links to hosted tools and specific project data
including:</p>
+
+ <ul>
+ <li>Developer participants and other project members</li>
+
+ <li>Project announcements and news</li>
+
+ <li>File sharing</li>
+
+ <li>Mailing list subscriptions and access to list archives</li>
+
+ <li>Source code browsing and repository access</li>
+
+ <li>Issue (bug) querying and reporting.</li>
+ </ul>
+
+ <p>The help documents associated with each of these resources are generally
addressed to project members, but non-member users also have read-only access
to these same project resource screens for any hosted projects publicly listed
on this site. These users cannot, however, modify files or contribute source
code until being approved as members with specific project roles.</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/ProjectMembersHelp.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMembersHelp.html
(added)
+++
websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMembersHelp.html
Sat Apr 8 23:00:09 2017
@@ -0,0 +1,83 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+<!--#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> » <a
href="/pl/">pl</a> » <a
href="/pl/Archive/">Archive</a> » <a
href="/pl/Archive/trans/">trans</a> » <a
href="/pl/Archive/trans/docs/">docs</a> » <a
href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<!-- Help Text Box -->
+<TABLE BORDER="0" CELLSPACING="0" CELLPADDING="3" BORDER="0" WIDTH="100%">
+ <TR>
+ <TD CLASS="HelpText" BGCOLOR="#ffcc66"><IMG
SRC="/branding/images/pixel.gif" HEIGHT="1" WIDTH="135"><BR>
+<b>As project admin, you can...</b></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc">
+
+ <TABLE BORDER="0" CELLSPACING="0" CELLPADDING="0" BORDER="0"
WIDTH="100%">
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMembers.html">Check the members' roles</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffcc66" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffcc66" HEIGHT="1"><SPACER TYPE="block"
HEIGHT="1"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMembers.html">View their issues</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffcc66" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffcc66" HEIGHT="1"><SPACER TYPE="block"
HEIGHT="1"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a
href="/project/www/docs/ProjectMembers.html">Process membership
requests</a></TD>
+ </TR>
+ <TR>
+ <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD>
+ <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block"
HEIGHT="2"></TD>
+ </TR>
+ </TABLE>
+
+ </TD>
+ </TR>
+</TABLE>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
