openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1010077 [16/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/ProjectOwnerEdit.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerEdit.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerEdit.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,158 @@
+<!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>Editing and maintaining the Project Home page</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+<div class="docs" id="projectowneredit">
+  <h2>Editing and maintaining 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/ProjectOwnerAdmin.html">Project owner administration</a> 
+        <ul>
+          <li> Editing and maintaining the Project Home page 
+            <ul>
+              <li><a href="#updatehome">Maintaining project information</a></li>
+              <li><a href="#useindex">About the 'Use Project Home Page' option</a></li>
+              <li><a href="#ownersmessage">Updating the owner's message</a></li>
+              <li><a href="#other">About other operations</a></li>
+              <li><a href="#aboutlocking">About project locking</a></li>
+            </ul>
+          </li>
+          <li><a href="/nonav/docs/ProjectOwnerNews.html">Managing project site 
+            news</a></li>
+          <li><a href="/nonav/docs/ProjectOwnerMembers.html">Adding project members 
+            and approving roles</a></li>
+          <li><a href="/nonav/docs/ProjectOwnerMailingLists.html">Managing project 
+            mailing lists</a></li>
+          <li><a href="/nonav/docs/ProjectOwnerDocuments.html">Managing project 
+            documentation</a></li>
+          <li><a href="/nonav/docs/ProjectOwnerSource.html">Managing project source 
+            code</a></li>
+          <li><a href="/nonav/docs/ProjectOwnerIssues.html">Tracking and managing 
+            project issues</a></li>
+          <li><a href="/nonav/docs/ProjectOwnerCustomStyle.html">Managing custom 
+            HTML styling</a></li>
+        </ul>
+      </li>
+    </ul>
+  </div>
+  <h3><a id="updatehome" name="updatehome">Maintaining project information</a></h3>
+  <p>The <strong>Project Home</strong> page is the entry point for all project 
+    users, members as well as potential contributors. The primary role of the 
+    <strong>Project Home</strong> page is to highlight the project's mission, 
+    primary goals, current status, and ongoing needs.</p>
+  <p><strong>NOTE</strong>: For a good example of summarizing project goals and 
+    status, see the open source <a href="http://subversion.tigris.org/">Subversion 
+    project home page</a>.</p>
+  <p>Project information can be modified through the <strong>Edit Project</strong> page. 
+    By clicking on the <strong>Edit this Project</strong> link on the <strong>Project 
+    Home </strong>you can modify the information in each of these fields:</p>
+
+<ul>
+  <li> 
+   <strong>Parent project</strong>: Use this field 
+      to assign a new parent project for your project. 
+  </li>
+  <li><strong>Summary</strong>: This text appears in project listings viewed by registered 
+    users. </li>
+  <li><strong>Description:</strong> Because the description field accommodates html formatting 
+    and graphics, you can use this to customize and add information to your project 
+    home page.</li>
+  <li><strong>Public project</strong>: Make your project visible or invisible to other users 
+    in this domain.</li>
+  <li><strong>Use project index: </strong>Use to assign an alternative home page for your 
+    project. See the <a href="#useindex">About the 'Use Project Home Page' option 
+    section</a> for further information on this option.</li>
+  <li><strong>Owner message</strong>: Communicate with your project members and 
+    potential members using this field. See the <a href="#ownersmessage">Updating 
+    the owner's message section</a> for tips on using this section.</li>
+  <li><strong>Addtional operations</strong>: These options allow you to manage additional 
+    project resources. See the <a href="#other">About other operations section</a> 
+    for an explanaition of each operation.</li>
+</ul>
+
+  <h3><a id="useindex" name="useindex">About the 'Use Project Home Page' option</a></h3>
+  <p>Your <strong>Project Home</strong> page by default displays the content that you entered 
+    in the Description field in the <strong>Edit Project</strong> page.</p>
+  <p>Because some projects require more complex home pages, however, you have 
+    the option to store and display special home page content from a different 
+    file. The "Use Index" flag in the <strong>Edit Project</strong> page indicates that 
+    your project home page should display the contents of the "index.html" file 
+    instead of displaying description field information from the database. This 
+    file is located in:</p>
+  <p>http://yourprojectname.this domain/www/index.html</p>
+  <p>This file is part of the project's source code repository under CVS version 
+    control. If you check the "Use Index" flag, this means you must update your 
+    home page content by editing the index.html file, saving it, and then committing 
+    it into CVS to display the newest file revision in your project's home page. 
+    When you use the index.html file, you can include HTML formatting, graphics, 
+    and other more complex elements for your project's home page.</p>
+  <h3><a id="ownersmessage" name="ownersmessage">Updating the owner's message</a></h3>
+  <p>Initially you use the field to identify yourself as the project owner and 
+    convey project goals. As the project progresses, use the Owner's Message to 
+    highlight project milestones, list changing requirements, and identify particular 
+    resource needs. For example, you may advertise the types of development expertise 
+    currently being sought:</p>
+  <blockquote> 
+    <p>"Desperately seeking experienced Java servlet developers with a passion 
+      for creating apps that will change the world."</p>
+  </blockquote>
+  <p>Or, you can give updates about the current status of development and what's 
+    coming up next.</p>
+  <p>However you use this field, your Owner's Message should be updated frequently: 
+    usually once a week, but no less than monthly. Fresh messages convey a sense 
+    of excitement and momentum; critical perceptions to the growth of development 
+    projects.</p>
+  <h3><a name="other" id="other"></a>About other operations</h3>
+  <p><strong>Tool configuration</strong>: This link allows you to view and, if you have 
+    the appropriate permission, to edit configuration options that affect your 
+    project. Use this area to determine how project tools are configured.</p>
+  <p><strong>Edit project roles</strong>: Allows you to view and manage roles 
+    specific to this project. More information on project roles is available in 
+    the <a href="/nonav/docs/ProjectOwnerMembers.html#addroles">Manage project 
+    roles</a> document.</p>
+  <p><strong>Edit project resource patterns</strong>: Like the project roles, 
+    this allows you to view and manage resources attached to roles in this project. 
+    For more information, review the <a href="/nonav/docs/ProjectOwnerMembers.html#addroles">Manage 
+    project roles</a> document.</p>
+  <p><strong>Lock and Delete project</strong>: Allows you to remove the project from view 
+    on the domain. For more information on locking projects please see <a href="#aboutlocking">About 
+    project locking</a>. </p>
+  <h3><a id="aboutlocking" name="aboutlocking">About project locking</a></h3>
+  <p>If you have received email notification that your project is locked, you 
+    should contact a site administrator immediately for further information. Project 
+    locking means that site administrators have temporarily disabled your project. 
+    This may be due to site policy matters, technical issues, or other reasons.</p>
+  <p>When you load your <strong>Project Home</strong> or <strong>Project Edit</strong> page, you encounter 
+    the "Locked" flag in red at the top. All site-related project activity is 
+    suspended in locked projects. Your project pages can still be accessed and 
+    all existing project data is intact, however <strong><i>you and your project members 
+    temporarily have read-only access</i></strong> to the source code repository, email 
+    archives, issue database, project files, and documents. No one -- including 
+    you -- can commit source code, enter issues, upload or download files and 
+    documents, change web content, or subscribe to or modify mailing lists. If 
+    your locked project is a public project, other site users can still view your 
+    project's home page but the project is flagged as "locked."</p>
+  <p>A site administrator must unlock your project to reactivate it. You will 
+    receive email notification when this action is taken also.</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/ProjectOwnerFiles.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerFiles.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerFiles.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,112 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title>Managing project files and documents</title>
+
+<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>&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">Managing project files</span>
+
+<p><span class="PlainText"><b>Project help for project owner administration: Index</b>
+<ul>
+<dl>
+  <dt><a href="ProjectOwnerAdmin.html">Project Owner Administration</a>
+  <dd><a href="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a>
+    <dd><a href="ProjectOwnerNews.html">Managing project site news</a>  
+    <dd><b>You are here: Managing project files
+      <ul>
+      <li><a href="#downloading">Downloading project files</a>
+      <li><a href="#adding">Uploading project files</a>
+        <li><a href="#files" target="Files">About file types</a>
+    </ul></b>
+  <dd><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a>
+  <dd><a href="ProjectOwnerMailingLists.html">Managing project mailing lists</a>
+  <dd><a href="ProjectOwnerDocumentation.html">Managing project documentation</a>
+  <dd><a href="ProjectOwnerSource.html">Managing project source code with CVS version control</a>
+  <dd><a href="ProjectOwnerIssues.html">Tracking and managing project issues</a>
+  <dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+</dl>
+</ul>
+<p>
+<hr noshade size=1>
+
+<span class=inputheader>Managing project files</span> 
+<p>This section focuses on uploading, or posting, files and documents on your project site for later downloading. We will first explain the page features and then, in the section titled "<a href="#files">About file types</a>" suggest some tips for project owners on how to place and maintain files for maximum ease of use by your developer community. 
+
+<p>As project owner, the columns you see when you access this page will differ from those seen by other users who are not project owners, and you will see the following column headings:
+<ul>
+<li>Size</li>  
+<li>File Name</li>  
+<li>Date Posted</li>  
+<li>Posted By </li> 
+<li>MD5 Checksum</li> 
+</ul>
+
+
+<p>These headings for the columns are fairly self-explanatory. The "Size" heading relates to the size of the file, and the "File Name" to the file name. "Date Posted," and "Posted By" refer to the date on which the file was placed on the project site and who posted it there. 
+<p>"MD5 Checksum" refers to a commonly accepted protocol for verifying a file's integrity. The numbers uniquely identify a file, and are automatically generated by the page every time a file is uploaded to the page. Upon downloading a file, you can verify the integrity and authenticity of the file by checking the numbers you generate using the protocol's algorithm against those on the site. MD5 checksum thus safeguards against any form of corruption (including the malicious insertion of viruses or Trojan horses) encountered while downloading.
+<p>
+Generating the MD5 code generally requires that use an operating system based on Unix, such as Linux, though there are increasingly more implementations available. But for now, unless you are using Linux, you will not be able to fully use the MD5 checksum functionality of the site. (For more information about MD5, please see Lance Spitzner's useful account of MD5, "<a href="http://www.enteract.com/~lspitz/md5.html" "target=_new">What is MD5 and why do I care?</a>"
+<p>
+
+<hr noshade size=1>
+<a name="downloading"><span class="InputHeader">How do I download a file?</span>
+<p>Under each heading, there may be files that you can download by clicking on them. If your browser supports file downloads, the download will immediately commence. The file will be downloaded to your default download directory on your workstation. 
+<p>
+
+<hr noshade size=1>
+<p><a name="adding"></a><span class="InputHeader">How do I upload a file? (Adding or replacing a download)</span>
+<p>You can add to and replace files already on the page by using the "Add or Replace a Download" field. To select a file you want added to the page, click on the "Browse..." button.  This button works with all browsers that support file uploads, regardless of the underlying operating system.  If you are using Windows, and you do not see the file you wish to upload, try setting the "Files of type:" setting to "All Files" in your browser's window.
+<p>There are a few caveats about uploading files:
+<ul>
+<li>The upload field does not support spaces in file names. Thus, if you are uploading a file whose name is, for instance, "Java Specifications," you will have to rename it on your computer to something like, "Java_Specifications."</li> 
+<p>
+<li>The field does not support the addition of directories; and adding many files at once could end up being counterproductive.</li>
+<p>
+<li>The maximum file size allowed per upload is 25 MB. Larger files will not be accepted.</li>
+</ul>
+<p>Once you have selected the file, you should describe the file. This description should be short and to the point. The idea is to provide the viewer with enough information to choose whether she needs to download the file or not. For instance, if you want to make available the the project's latest milestone, you might describe it using the date, or if it is a component, the version and function name.
+
+<p>The last field on the page, the "Public" checkbox, allows you to stipulate whether you want the file to be publicly available. Checking the box indicates that anyone who as accessed your downloads page can retrieve the file; they need not be members of your project. In contrast, an empty box denotes that only project <i>members</i> can retrieve the file. By default, the box is left unchecked.  
+<p>
+
+
+<hr noshade size=1>
+<a name="files"></a><span class="InputHeader">About file types</span>
+
+<p>You can post a variety of file types for later download:  binaries, tarballs, zip files, text files, even graphic files. Since the point of this page is to provide members (and the public) an central place from which to download final (or major milestone) releases, you do not want to add files which are in flux.  In short, files which require some form of concurrent version control. 
+<p>Note: We do not recommend that you post source code to this page. Consequently, this page does not support CVS (Concurrent Versioning Control). If you are interested in posting source and wish to use concurrent version control, please see the <a href="ProjectSource.html">CVS</a> help information.
+
+
+
+<hr noshade size=1>
+<a href="ProjectOwnerAdmin.html">Back to Project Owner Administration 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/ProjectOwnerIssues.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerIssues.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerIssues.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,128 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<TITLE>Tracking Project Issues</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>Tracking project issues</SPAN>
+<P>
+<SPAN CLASS="PlainText"><B>Project help for project owner administration: Index</B>
+<P>
+
+<UL>
+<DL>
+<DT><A HREF="ProjectOwnerAdmin.html">Project owner administration</A>
+  <DD><A HREF="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</A>
+  <DD><A HREF="ProjectOwnerNews.html">Managing project site news</A>
+  <DD><A HREF="ProjectOwnerFiles.html">Managing project files</A>
+  <DD><A HREF="ProjectOwnerMembers.html">Adding project members and approving roles</A>
+  <DD><A HREF="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>
+`  <dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a>
+  <DD><A HREF="ProjectOwnerSource.html">Managing project source code</A>
+  <DD><B>You are here: Tracking project issues
+    <UL>
+    <LI><A HREF="#adminpermissions">About administrative issue tracking permissions</A>
+    <LI><A HREF="#adminconfigure">Configuring IssueZilla's administrative options</A>
+    <LI><A HREF="#admintips">Tips and tricks for issue management</A>
+    </UL></B>
+<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
+</DL>
+</UL>
+
+
+<P>
+<B>Issue tracker tool documentation</B>
+<UL>
+  <DL>
+   <DT><A HREF="ProjectIssues.html">Project Issues page help</A>
+     <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>
+    </DL>
+</UL>
+<P>
+
+<HR NOSHADE SIZE=1>
+<A NAME="adminpermissions"><SPAN CLASS="InputHeader">Issue tracking administration</SPAN></A>
+     <P>
+     <P>Because you are a Project Owner, you automatically have administrative permissions in IssueZilla to manage and track your project's issues. You can access these administrative options two different ways:
+  <UL>
+  <LI>Your view of the <B>Project Issues</B> page includes additional sections to <I>Edit Users</I>, <I>Edit Groups</I>, and <I>Edit Components</I>.
+  <P>
+  <LI>All administrative options are included in the Issue Tracking toolbar, which appears in your view of all issue tracking screens.
+  </UL>
+<P>
+Your role of Project Owner gives you the ability to configure almost every element of IssueZilla. Descriptions of these options and their default settings follows. Probably the most significant permission you have is the ability to edit the issue tracking permissions of all other users on your project. This can include delegating some of these administrative permissions to other users to help manage and plan the project workload.
+     <P>
+If one of your project members builds a solid track record of committing issues that get confirmed, this is probably a person who understands the project and the issue tracking system well enough to be granted the "Can confirm an issue" permission. As a project owner, you can and should use IssueZilla to track this kind of information about project participants to help you manage project issues effectively.
+<P>
+To learn how to assign issue tracking permissions to project members, see "Users" in the next section
+
+<HR NOSHADE SIZE=1>
+<A NAME="adminconfigure"></A><SPAN CLASS="InputHeader">Configuring IssueZilla's administrative options</SPAN>
+<P>
+<DL>
+<DT><B>Prefs</B> (Preferences) <DD>Lets you configure some aspects of your issue tracking functionality and display environment, including:
+<P>
+  <UL>
+  <LI>Email settings for automatic issue email notifications to you. 
+    <LI>Page footer links to be included in your query results screens.
+  <LI>Permissions assigned to you as the default issue tracking administrator. (You control these permissions for all members of your project through the <I>Users</I> option in the Issue Tracking toolbar.)
+  </UL>
+<P>
+<DT><B>Sanity check</B> <DD> An automated process that checks for an identifies any anomalies in your project's issues database, such as conflicting dependencies, committed issue errors, and correct references between issue reporters and user profiles.
+<P>
+<DT><B>Users</B> <DD> A text string field lets you access the user edit screen either by filtering for specific users or leaving it blank to access the full list of users after clicking the "Submit" button. Clicking on listed user's link displays another edit screen where you can check and uncheck permissions options.
+<P>
+<DT><B>Components</B> <DD> A component selection screen that lets you create, define, edit, add, and delete project components and subcomponents. Clicking on a component link in the list displays another edit screen where you can configure that particular component or subcomponent.
+<P>
+<DT><B>Groups</B> <DD> A group selection screen that lets you create, define, and delete groups specifically for issue tracking purposes, and assign project member users to groups. You can make changes to one, several, or all fields and submit them all at once. Your project also includes a default set of groups pertaining to issue tracking permissions.
+<P>
+<DT><B>Keywords</B> <DD> A keyword selection screen that lets you create, define, edit, and delete regular expression keywords to be used for issue tracking groups and queries.
+</DL>
+
+<HR NOSHADE SIZE=1>
+<A NAME="admintips"></A><SPAN CLASS="InputHeader">Tips and tricks for issue management</SPAN>
+<P>
+IssueZilla is a powerful tool for managing and tracking your project's development activities down to the fine-grained details. As with most tools, users develop inevitably develop shortcuts and tricks to compensate for particular aspects of the tool, or to tailor it to their specific needs. IssueZilla is no exception.
+<P>
+What follows is a sampling of several tricks that have proved particularly useful to project managers or users with administrative issue tracking permissions:
+<UL>
+<LI>Avoid configuring the same management-level queries repeatedly by creating permanently displayed links to information you use constantly. For example, you can create a page of links for each project member's issue list, and for regularly used milestone or issue status queries.
+<P>
+<LI>Because issues may not be deleted, you can create components or subcomponents named "issue graveyard" or "unknown" to collect dead or no longer applicable issues. IssueZilla's non-delete feature is actually a protective design feature since the ability to track such dead issues can sometimes come in handy, or at least preserve aspects of project history.
+<P>
+<LI>Create a "not determined" milestone for project issues not yet tied to any particular project milestone date or release. Development project objectives and priorities tend to shift dynamically. This lets you identify and hold in reserve those issues affected by your project's evolution.
+<P>
+<LI>Add a pseudo user known as "placeholder" (or some other equally obvious generic identity) who can "own" issues that you are not yet ready or able to assign to specific project members.
+</UL>
+<P>     
+
+<HR NOSHADE SIZE=1>
+<A HREF="ProjectOwnerAdmin.html">Back to Project Owner Administration 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/ProjectOwnerIssues.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerIssues.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerIssues.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,245 @@
+<!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>Tracking project issues</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="projectownerissues">
+   <h2>Tracking 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/ProjectOwnerAdmin.html">Project owner administration</a> 
+
+      <ul>
+       <li><a href="/nonav/docs/ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a></li>
+
+       <li><a href="/nonav/docs/ProjectOwnerNews.html">Managing project site news</a></li>
+
+       <li><a href="/nonav/docs/ProjectOwnerMembers.html">Adding project members and approving roles</a></li>
+
+       <li><a href="/nonav/docs/ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a></li>
+
+       <li><a href="/nonav/docs/ProjectOwnerDocuments.html">Managing project documentation</a></li>
+
+       <li><a href="/nonav/docs/ProjectOwnerSource.html">Managing project source code</a></li>
+
+       <li>
+        Tracking project issues 
+
+            <ul>
+              <li><a href="#adminpermissions">About administrative issue tracking 
+                permissions</a></li>
+              <li><a href="#adminconfigure">Configuring Issuezilla's administrative 
+                options</a></li>
+              <li><a href="#admintips">Tips and tricks for issue management</a></li>
+              <li><a href="#export">Exporting issues to another project</a></li>
+            </ul>
+       </li>
+	   <li><a href="/nonav/docs/ProjectOwnerCustomStyle.html">Managing custom HTML styling</a></li>
+      </ul>
+     </li>
+    </ul>
+
+    <ul>
+     <li><a href="/nonav/docs/ProjectIssues.html">Issue tracking page help</a></li>
+
+     <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>
+    </ul>
+   </div>
+
+   <h3><a id="adminpermissions" name="adminpermissions">Issue tracking administration</a></h3>
+
+   <p>Because you are a Project Owner, you automatically have administrative permissions in IssueZilla to manage and track your project's issues. Along with the options available to other project members, your view of the <b>Issue Tracking</b> page includes a <b>Configuration Options</b> link that will take to the <strong>Issue tracking configuration parameters for project</strong> page. Almost all administrative options are included on this page. (See "<a href="#adminconfigure">Configuring IssueZilla's administrative options</a>" below for descriptions of the fields you can configure.) The exception to this is the assigned to field. The assigned to field is configurable only by the Host Administrator and may be configured as either a drop down box or a text box in which the user 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>Your role of Project Owner gives you the ability to configure almost every element of IssueZilla. Probably the most significant permission you have is the ability to edit the issue tracking permissions of all other users on your project. This can include delegating some of these administrative permissions to other users to help manage and plan the project workload. If one of your project members builds a solid track record of committing issues that get confirmed, this is probably a person who understands the project and the issue tracking system well enough to be granted the "Can confirm an issue" permission. As a project owner, you can and should use IssueZilla to track this kind of information about project participants to help you manage project issues effectively.</p>
+
+   <p>To learn how to assign issue tracking permissions to project members, see "Users" in the next section</p>
+
+   <h3><a id="adminconfigure" name="adminconfigure">Configuring IssueZilla's administrative options</a></h3>
+
+   <p>You can configure <em>Issue Attributes</em> and <em>Operating Parameters</em> from the <strong>Issue tracking configuration parameters for project</strong> page. Below are descriptions of the options that you can configure:</p>
+
+   <dl>
+    <dt><strong>Issue Attributes</strong></dt>
+
+    <dd>
+     <dl>
+      <dt>Add/edit components</dt>
+
+      <dd>
+       When a project is created an issue database is created with the name of the project as the default component in IssueZilla. Each component is a unique entity within IssueZilla. All issues must be associated with a component to be created. The component interface allows you to define subcomponents, versions and milestones. 
+
+       <dl>
+        <dt>Subcomponents</dt>
+
+        <dd>A subcomponent may be used to define functional areas within the component. For example, for a component called pacman you may have a set of subcomponents with the following titles; user interface, strategy, user documentation, installation, etc. A subcomponent inherits all the characteristics of the parent component. Thus, if you assign a set of version numbers to a component, all subcomponents will receive the same set of versions. A component selection screen that lets you create, define, edit, add, and delete project components and subcomponents.</dd>
+
+        <dt>Versions</dt>
+
+        <dd>To assist in tracking the releases and build cycle of your project you can assign versions to your component. Versions represent a full unit of a release cycle. That is, the version is used to track the process from original design, through development and final release. The version includes the development, QA and release cycles. HINT: to assist in your review process you may want to consider using the same versions as you use to tag unique code sets in CVS.</dd>
+
+        <dt>Milestones</dt>
+
+        <dd>Milestones are significant points in the development process which you may wish to track. For instance you may have design, scoping, development, documentation, QA and release milestones. The milestone field can be used to run reports on the progress of your project.</dd>
+       </dl>
+      </dd>
+
+      <dt>Add/edit keywords</dt>
+
+      <dd>Allows you to create, define, edit, and delete regular expression keywords to be used for issue tracking groups and queries.</dd>
+
+      <dt>Add/edit platforms</dt>
+
+      <dd>
+       Allows you to apply a sort key, mark as Closed, or Delete any of the defaults, or add new platforms. Default platforms are: 
+
+       <ul>
+        <li>All (happens on all platform; cross-platform issue)</li>
+
+        <li>DEC</li>
+
+        <li>HP</li>
+
+        <li>Macintosh</li>
+
+        <li>Palm PDA</li>
+
+        <li>PC</li>
+
+        <li>SGI</li>
+
+        <li>SUN</li>
+
+        <li>Other</li>
+       </ul>
+      </dd>
+
+      <dt>Add/edit operating Systems</dt>
+
+      <dd>Allows you to apply a sort key, mark as Closed, or Delete any of the defaults, or add new operating systems. Default values include most available operating systems.</dd>
+     </dl>
+    </dd>
+
+    <dt><strong>Operating Parameters</strong></dt>
+
+    <dd>
+     <dl>
+      <dt>Edit users</dt>
+
+      <dd>Allows you to access the user edit screen either by filtering for specific users or leaving it blank to access the full list of users after clicking the "Submit" button. Clicking on listed user's link displays another edit screen where you can check and uncheck permissions options.</dd>
+
+      <dt>Add/edit groups</dt>
+
+      <dd>Allows you to create, define, and delete groups specifically for issue tracking purposes, and assign project member users to groups. You can make changes to one, several, or all fields and submit them all at once. Your project also includes a default set of groups pertaining to issue tracking permissions.</dd>
+
+      <dt>Edit advanced configuration options</dt>
+
+      <dd>Allows you to edit the values of many of the keys within Issuezilla. This link will take you to the <strong>Edit parameters</strong> page where you can set the issue defaults, organization, appearance, comment triggers, email notifications, and other database options. A definition and directions for setting each key is given on this page.</dd>
+      <dd>Note: This page should be handled with care. Checking the <strong>Reset</strong> box on any item will reset it to the default value.</dd>
+      
+      <dt>Add/edit mimetypes</dt>
+
+      <dd>Allows you to create, define, edit or delete descriptions for attachment uploads.</dd>
+
+      <dt>Add/edit hosts</dt>
+
+      <dd>Allows you to create, edit or delete hosts for issue export.</dd>
+
+      <dt>Edit issue import configuration rules</dt>
+
+      <dd>
+       Allows you to set rules and field values to be used when importing issues from another project's database. The following items can be configured: 
+
+       <ul>
+        <li>Component</li>
+
+        <li>Subcomponent</li>
+
+        <li>Version</li>
+
+        <li>Milestone</li>
+
+        <li>User resolution</li>
+
+        <li>Importing votes</li>
+
+        <li>Subject prefix for imported issues</li>
+       </ul>
+      </dd>
+     </dl>
+    </dd>
+
+    <dt><strong>Run sanity check</strong></dt>
+
+    <dd>Allows you to run an automated process that checks for and identifies any anomalies in your project's issues database, such as conflicting dependencies, committed issue errors, and correct references between issue reporters and user profiles. You can run the sanity check to check for corruption or invalid entries in your issue database.</dd>
+   </dl>
+
+   <h3><a id="admintips" name="admintips">Tips and tricks for issue management</a></h3>
+
+   <p>IssueZilla is a powerful tool for managing and tracking your project's development activities down to the fine-grained details. As with most tools, users develop inevitably develop shortcuts and tricks to compensate for particular aspects of the tool, or to tailor it to their specific needs. IssueZilla is no exception.</p>
+
+   <p>What follows is a sampling of several tricks that have proved particularly useful to project managers or users with administrative issue tracking permissions:</p>
+
+   <ul>
+    <li>Avoid configuring the same management-level queries repeatedly by creating permanently displayed links to information you use constantly. For example, you can create a page of links for each project member's issue list, and for regularly used milestone or issue status queries.</li>
+
+    <li>Because issues may not be deleted, you can create components or subcomponents named "issue graveyard" or "unknown" to collect dead or no longer applicable issues. IssueZilla's non-delete feature is actually a protective design feature since the ability to track such dead issues can sometimes come in handy, or at least preserve aspects of project history.</li>
+
+    <li>Create a "not determined" milestone for project issues not yet tied to any particular project milestone date or release. Development project objectives and priorities tend to shift dynamically. This lets you identify and hold in reserve those issues affected by your project's evolution.</li>
+
+    <li>Add a pseudo user known as "placeholder" (or some other equally obvious generic identity) who can "own" issues that you are not yet ready or able to assign to specific project members.</li>
+   </ul>
+
+<h3><a id="export" name="export">Exporting issues to another project</a></h3>
+<p>You can copy issues from one project to another using the issue export/import feature. This function takes a 'snapshot' of an issue in one project, and creates duplicate of that issue in another project. An issue can be exported to a given host only once; the issue is never updated on the importing side once a successful import has occurred. Exporting an issue does not change its state. For example, the issue is not closed when exported. The export gives an issue independent (but cross-referenced) representation in two places.
+   
+<p>When performing the export operation, there are responsibilities on both the export and the import sides. The exporter is responsible for defining projects or hosts that issues can be exported to, and identifying data that should be included or excluded from the exported version. The importer in turn is responsible for determining whether to accept the issue, and for deciding how to map the data in the issue to data in the importing project.</p>
+
+<h4>Setting up: Exporter</h4>
+
+  <p>Enabled issue exporting by defining one or more hosts to which issues can be exported. On the Issue tracker page, click on <b>Configuration Options</b> and select the <b>Add/edit hosts to export issues to</b> link. This will take you to the<b> Edit export host list</b> page. Enter the hosts to which you want issues to be exported in the fields provided. Hosts should be in URL form, for example <em>https://secureproject.mydomain.net/</em>. Once you have entered the desired host(s), click the <b>Submit</b> button. If you wish to remove a host, simply clear the field and click the submit button again.</p>  
+   
+<p>Once a host is defined, all users with the <b>Project Issue Tracking - Configure</b> permission will see an <b>Export This Issue</b> button when viewing an issue.</p>
+   
+<h4>Setting up: Importer</h4>
+   
+  <p>The importing host must be running SourceCast version 2.0 or greater with at least one project created (to import into), and a user account which will be used to authorize the import. Although it's not necessary to do so for import/export to function, the rules which the importer uses to reconcile incoming data with it's own data can be configured by clicking on <b>Configuration Options</b> and selecting the <b>Edit issue import configuration rules</b> link.
+   
+<h4>Performing an export</h4>
+
+<p>Once both the importing and exporting sides are appropriately configured, you can perform the export function following these steps:</p>
+
+<ol>
+    <li>While viewing the issue you wish to export, click the <b>Export this issue ...</b> button.</li>
+   <li>Enter the username and password for the importing user and select any data fields for suppression.</li>
+   <li>Click the <b>Export Issue</b> button.</li>
+</ol>
+<p>If the export was successful, after a moment the issue will be updated with a link to the issue at its imported location.</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/ProjectOwnerMailingLists.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerMailingLists.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerMailingLists.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,180 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<TITLE>Managing 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>&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">Managing project mailing lists</SPAN> 
+<P>  
+<SPAN CLASS="PlainText"><B>Project help for project owner administration: Index</B>
+<P>
+<UL>
+<DL>
+<DT><A HREF="ProjectOwnerAdmin.html">Project owner administration</A>
+<DD><A HREF="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</A>
+<DD><A HREF="ProjectOwnerNews.html">Managing project site news</A>
+<DD><A HREF="ProjectOwnerFiles.html">Managing project files</A>
+<DD><A HREF="ProjectOwnerMembers.html">Adding project members and approving roles</A>
+<DD><B>You are here: Configuring and managing project mailing lists
+  <UL>
+  <LI><A HREF="#aboutlists">About default project mailing lists</A>
+  <LI><A HREF="#addlists">Adding and deleting mailing lists</A>
+  <LI><A HREF="#mailadmin">Mailing list administration and policies</A>
+  <LI><A HREF="#editsubscribers">Editing subscribers and moderators</A>
+    </UL></B>
+<dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a>
+<DD><A HREF="ProjectOwnerSource.html">Managing project source code</A>
+<DD><A HREF="ProjectOwnerIssues.html">Tracking project issues</A>
+<DT><A HREF="/servlets/HelpTOC">Back to the main Help index</A>
+</DL>
+</UL>
+
+<P>
+<HR NOSHADE SIZE=1>
+<A NAME="aboutlists"></A><SPAN CLASS="InputHeader">About default project mailing lists</SPAN>
+<P>
+All project mailing lists are created with <A HREF="http://anzu.tigris.org/" TARGET="_new">anzu</A>, an open source mail alias and list management extension of qmail simple mail transfer protocol (smtp). Anzu supports multiple domains, enabling each project to define and manage its own unique set of mailing lists for the project domain.
+
+<P>
+If you created your project as a standard development project, your project begins its life with five built-in, pre-configured mailing lists:
+
+<BLOCKQUOTE>
+    <DL>
+  <DT><B>dev@projectname.domain.com</B> <DD>The main list for developers to discuss specific project development issues and requirements for version control in the project.
+<P>
+  <DT><B>cvs@projectname.domain.com</B> <DD>Automated notifications of file version control changes and discussion of those changes.
+<P>
+    <DT><B>announce@projectname.domain.com</B> <DD>Announcements of new releases and other major project events.
+<P>
+  <DT><B>issues@projectname@domain.com</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>users@projectname.domain.com</B> <DD>A more general discussion list for the project's end users.
+    </DL>
+    </BLOCKQUOTE> 
+<P>
+Discussion-only projects are set up with one discussion mailing list initially.
+<P>
+You can access your project's existing mailing lists in two different ways:
+<UL>
+<LI>Clicking the <I>Mailing Lists</I> link in the Project Resources tool bar displays your project's <B>Mailing Lists</B> page. An edit link appears for each mailing list that opens a <B>Mailing List Edit</B> screen for that particular list.
+<P>
+<LI>In the <B>Project Edit</B> page (reached by clicking the <I>Admin</I> link in the Project Resources tool bar), links at the bottom of the page lead to a <B>Mailing List Edit</B> screen for each list.
+</UL>
+<P>
+For an explanation of fields and options on the <B>Mailing List Edit</B> page, see <A HREF="#mailadmin">Mailing list administration and policies</A> below.
+<P>
+<HR NOSHADE SIZE=1>
+<A NAME="addlists"></A><SPAN CLASS="InputHeader">Adding and deleting mailing lists</SPAN>
+<P>
+Your project's growth and progression may warrant adding mailing lists at some point ... or perhaps deleting lists. The default mailing lists created along with your project are "top-level" lists. Should traffic relating to a particular module or component becomes too high for one or more of these lists, you can splinter that discussion off into its own arena by create a separate new mailing list.
+<P>
+Add a new mailing list by going to the <B>Project Edit</B> page and clicking the "new" link in the bottom Mailing Lists section. This action leads you to the <B>Add New Mailing List</B> page to set up and configure your newest list. See the following section about list administration and policies for more information about the fields and settings in this screen.
+<P>
+To delete a mailing list, click the mailing list link in the <B>Project Edit</B> page to open <B>Edit Mailing List</B> page. Click the <I>Delete Mailing List</I> link just above the buttons on this screen. Another page displays asking for delete confirmation before the action is completed.
+
+<P>
+<HR NOSHADE SIZE=1>
+<SPAN CLASS="InputHeader"><A NAME="mailadmin">Mailing list administration and policies</A></SPAN>
+  
+<P>
+As the project owner you can choose to modify your project's default mailing list settings, add new lists, delete unnecessary lists, add and remove subscribers, designate moderators, and set other mailing list parameters.
+<P>
+Both the <B>Add Mailing List</B> and <B>Edit Mailing List</B> page settings include:
+<UL>
+<LI>a list description text field,
+<LI>a prefix to appear on the subject line of all messages,
+<LI>an automatically generated trailer with subscribe/unsubscribe instructions which can be toggled on or off.
+</UL>
+<P>The "List Type" options refer to how you want to set the mailing list policies for handling subscriptions and posting.
+<UL>
+<LI>If your project is under proprietary licensing, your mailing lists are restricted to project members only and the list archives are also private by default. Only users who are members of your private project have the necessary permissions to view these mailing lists and the associated archives. 
+<P>
+<LI>If your project is under open source licensing, you can select among several different combination of these policies, depending upon the purpose of the list. 
+</UL>
+<P>
+  <DL>
+  <DT><B>Posting policy</B>
+  <DD>This determines how the list handles posts from non-subscribers and subscribers. For open source projects, mailing lists can be configured to handle message posts at three different levels:
+<P>
+    <UL>
+    <LI>"<B>Discuss</B>" allows subscribers to post, and moderates posts (requires approval) from non-subscribers.
+    <P>
+    <LI>"<B>Moderated</B>" moderates <I>all</I> posts.
+    <P>
+    <LI>"<B>Unmoderated</B>" allows anyone to post messages without moderation.
+    </UL>
+  <P>
+  <DT><B>Subscription moderation</B>
+  <DD>This determines whether subscription to the list is "open" or "-private." Anyone can subscribe to open lists. Marking a list as "private" has two implications:
+<P>
+    <UL>
+    <LI>Subscribers must be approved by the list moderator.
+    <P>
+    <LI>List archives are not publicly viewable. Users who do not have permission to see the archives do not see links to subscribe to these lists either.
+    </UL>
+<P>
+By default, subscriptions to proprietary project mailing lists are on an approval basis because these lists are always private. This means that even members of a private project must be approved by a list moderator to subscribe to project mailing lists.
+  </DL>
+<P>
+
+<HR NOSHADE SIZE=1>
+<SPAN CLASS="InputHeader"><A NAME="editsubscribers">Editing subscribers and moderators</A></SPAN>
+
+<P>
+You can add and remove mailing list subscribers, designate list moderators, and suppress certain users from posting messages using the links in the "Members" section of the <B>Edit Mailing List</B> page: <I>Edit Subscribers</I>, <I>Edit Digest Subscribers</I>, <I>Edit Moderators</I>, <I>Edit Allowed Posters</I>.
+<P>
+These links display an edit screen where you can designate users by email address for the desired action. You may also imposed list filters in this screen. <!-- parameters for filters? -->
+<P>
+Even for those mailing lists you have designated as unmoderated, you always have control over who may post messages to any of your project mailing lists as the project owner. If someone abuses list privileges or fails to comply with mailing list etiquette on an unmoderated list, you must be able to disallow further postings from this person. For moderated lists, your designated moderator has the permissions to edit list subscribers.
+<P>
+
+<!--
+  <P>Other pre-set mailing list features include:
+<ul>
+<li>Indexing 
+<li>Archiving 
+<li>List digest setup
+*** <li>No archive guards, enabling any user to retrieve archived list messages in the case of open mailing lists.
+*** <li>Public          = true (the list will respond to admin commands like
+                        subscribe)
+
+*** <li>request_address = true (makes life easier for people who are used to majordomo)
+*** <li>Remote administration, allowing list moderators to subscribe people to the list via e-mail  (other useful things***)
+</ul>
+
+  <p>Discussion lists include two addition features when the posting policy is set for either "announce" or "automated-notification":
+
+<ul>
+***<li>Message "extras" are disallowed, stripping messages of certain mime types.
+***<li>Posted message size restrictions requiring messages to be a minimum of 2 bytes and a maximum of 400 kb. This restriction is not applied to the other types of mailing lists by default but can be set up through domain level administration.
+</ul>
+-->
+
+
+<HR NOSHADE SIZE=1>
+<A HREF="Help.html">Back to main Help index</A></P></SPAN>
+
+</SPAN>
+
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerMailingLists.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerMailingLists.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerMailingLists.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,208 @@
+<!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>Managing project mailing lists</title>
+ </head>
+
+ <body class="docs" onLoad="self.focus()">
+  <div class="docs" id="projectownermailinglists">
+   <h2>Managing 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/ProjectOwnerAdmin.html">Project owner administration</a> 
+
+      <ul>
+       <li><a href="/nonav/docs/ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a></li>
+
+       <li><a href="/nonav/docs/ProjectOwnerNews.html">Managing project site news</a></li>
+
+       <li><a href="/nonav/docs/ProjectOwnerMembers.html">Adding project members and approving roles</a></li>
+
+       <li>
+        Configuring and managing project mailing lists 
+
+        <ul>
+         <li><a href="#aboutlists">About default project mailing lists</a></li>
+
+         <li><a href="#addlists">Adding and deleting mailing lists</a></li>
+
+         <li><a href="#archivedel">Deleting archived mail items</a></li>
+
+         <li><a href="#mailadmin">Mailing list administration and policies</a></li>
+
+         <li><a href="#editsubscribers">Editing subscribers and moderators</a></li>
+        </ul>
+       </li>
+
+       <li><a href="/nonav/docs/ProjectOwnerDocuments.html">Managing project documentation</a></li>
+
+       <li><a href="/nonav/docs/ProjectOwnerSource.html">Managing project source code</a></li>
+
+       <li><a href="/nonav/docs/ProjectOwnerIssues.html">Tracking project issues</a></li>
+       <li><a href="/nonav/docs/ProjectOwnerCustomStyle.html">Managing custom HTML styling</a></li>
+	  </ul>
+     </li>
+    </ul>
+   </div>
+
+   <h3><a id="aboutlists" name="aboutlists">About default project mailing lists</a></h3>
+
+   <p>All project mailing lists are created with <a href="http://anzu.tigris.org/">Anzu</a>, an open source mail alias and list management extension of qmail simple mail transfer protocol (smtp). Anzu supports multiple domains, enabling each project to define and manage its own unique set of mailing lists for the project domain.</p>
+
+   <p>If you created your project as a standard development project, your project begins its life with five built-in, pre-configured mailing lists:</p>
+
+   <dl>
+    <dt>dev@projectname.domain.com</dt>
+
+    <dd>The main list for developers to discuss specific project development issues and requirements for version control in the project.</dd>
+
+    <dt>cvs@projectname.domain.com</dt>
+
+    <dd>Automated notifications of file version control changes and discussion of those changes.</dd>
+
+    <dt>announce@projectname.domain.com</dt>
+
+    <dd>Announcements of new releases and other major project events.</dd>
+
+    <dt>issues@projectname@domain.com</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>users@projectname.domain.com</dt>
+
+    <dd>A more general discussion list for the project's end users.</dd>
+   </dl>
+
+   <p>Discussion-only projects are set up with one discussion mailing list initially.</p>
+
+   <p>You can access your project's existing mailing lists in two different ways:</p>
+
+   <ul>
+    <li>Clicking the <i>Mailing Lists</i> link in the Project Resources tool bar displays your project's <b>Mailing Lists</b> page. An edit link appears for each mailing list that opens a <b>Mailing List Edit</b> screen for that particular list.</li>
+
+    <li>In the <b>Project Edit</b> page (reached by clicking the <i>Admin</i> link in the Project Resources tool bar), links at the bottom of the page lead to a <b>Mailing List Edit</b> screen for each list.</li>
+   </ul>
+
+   <p>For an explanation of fields and options on the <b>Mailing List Edit</b> page, see <a href="#mailadmin">Mailing list administration and policies</a> below.</p>
+
+   <h3><a id="addlists" name="addlists">Adding and deleting mailing lists</a></h3>
+
+   <p>Your project's growth and progression may warrant adding mailing lists at some point ... or perhaps deleting lists. The default mailing lists created along with your project are "top-level" lists. Should traffic relating to a particular module or component becomes too high for one or more of these lists, you can splinter that discussion off into its own arena by create a separate new mailing list.</p>
+
+   <p>Add a new mailing list by going to the <b>Project Edit</b> page and clicking the "new" link in the bottom Mailing Lists section. This action leads you to the <b>Add New Mailing List</b> page to set up and configure your newest list. See the following section about list administration and policies for more information about the fields and settings in this screen.</p>
+
+   <p>To delete a mailing list, click the mailing list link in the <b>Project Edit</b> page to open <b>Edit Mailing List</b> page. Click the <i>Delete Mailing List</i> link just above the buttons on this screen. Another page displays asking for delete confirmation before the action is completed.</p>
+
+   <h3><a id="archivedel" name="archivedel"></a>Deleting archived mail items</h3>
+
+   <p>Periodically, you may find a need to delete obsoleted archived messages from a mail list. To do this, navigate to the archive of the mail list in which the item appears. Select the time period and then find the item you want to delete. Click the <i>Delete</i> link. You will need to verify the delete on the next screen by selecting either the yes or no radio button and clicking on the <em>Submit Query</em> button.</p>
+
+   <h3><a id="mailadmin" name="mailadmin">Mailing list administration and policies</a></h3>
+
+   <p>As the project owner you can choose to modify your project's default mailing list settings, add new lists, delete unnecessary lists, add and remove subscribers, designate moderators, and set other mailing list parameters.</p>
+
+   <p>Both the <b>Add Mailing List</b> and <b>Edit Mailing List</b> page settings include:</p>
+
+   <ul>
+    <li>a list description text field,</li>
+
+    <li>a prefix to appear on the subject line of all messages,</li>
+
+    <li>an automatically generated trailer with subscribe/unsubscribe instructions which can be toggled on or off.</li>
+   </ul>
+  <dl> 
+    <dt>List Type</dt>
+    <dd>These options refer to how you want to set the mailing list policies for 
+      handling subscriptions and posting.</dd>
+    <dd> 
+      <ul>
+        <li><b>Private checkbox:</b> If your project is private, your mailing 
+          lists are restricted to project members only and the list archives are 
+          also private by default. Only users who are members of your private 
+          project have the necessary permissions to view these mailing lists and 
+          the associated archives.</li>
+        <li>If your project is public, you can select among several different 
+          combination of these policies, depending upon the purpose of the list.</li>
+      </ul>
+    </dd>
+    <dt>Posting policy</dt>
+    <dd>These options determine how the list handles posts from non-subscribers 
+      and subscribers. For open source projects, mailing lists can be configured 
+      to handle message posts at three different levels: </dd>
+    <dd> 
+      <ul>
+        <li>"<b>Discuss</b>" allows subscribers to post, and moderates posts (requires 
+          approval) from non-subscribers.</li>
+        <li>"<b>Moderated</b>" moderates <i>all</i> posts.</li>
+        <li>"<b>Unmoderated</b>" allows anyone to post messages without moderation.</li>
+      </ul>
+    </dd>
+    <dt>Subscription moderation</dt>
+    <dd> This determines whether subscription to the list is "open" or "private." 
+      Anyone can subscribe to open lists. Marking a list as "private" has two 
+      implications: 
+      <ul>
+        <li>Subscribers must be approved by the list moderator.</li>
+        <li>List archives are not publicly viewable. Users who do not have permission 
+          to see the archives do not see links to subscribe to these lists either.</li>
+      </ul>
+      <p>By default, subscriptions to the mailing lists in a private project are 
+        on an approval basis because these lists are always private. This means 
+        that even members of a private project must be approved by a list moderator 
+        to subscribe to project mailing lists.</p>
+    </dd>
+  </dl>
+
+   <h3><a id="editsubscribers" name="editsubscribers">Editing subscribers and moderators</a></h3>
+
+   <p>You can add and remove mailing list subscribers, designate list moderators, and suppress certain users from posting messages using the links in the "Members" section of the <b>Edit Mailing List</b> page: <i>Edit Subscribers</i>, <i>Edit Digest Subscribers</i>, <i>Edit Moderators</i>, <i>Edit Allowed Posters</i>.</p>
+
+   <p>These links display an edit screen where you can designate users by email address for the desired action. You may also alter the Private component; on to allow only project members to see the contents of the maillist archive, off to allow anyone who can see the project access to the archive.</p>
+
+   <p>For those mailing lists designated as unmoderated, you always have control over who may post messages to any of your project mailing lists as the project owner. If someone abuses list privileges or fails to comply with mailing list etiquette on an unmoderated list, you must be able to disallow further postings from this person. For moderated lists, your designated moderator has the permissions to edit list subscribers.</p>
+
+   <p><!--
+                  <P>Other pre-set mailing list features include:
+                 <ul>
+                 <li>Indexing 
+                 <li>Archiving 
+                 <li>List digest setup
+                 *** <li>No archive guards, enabling any user to retrieve archived list messages in the case of open mailing lists.
+                 *** <li>Public          = true (the list will respond to admin commands like
+                                         subscribe)
+
+                 *** <li>request_address = true (makes life easier for people who are used to majordomo)
+                 *** <li>Remote administration, allowing list moderators to subscribe people to the list via e-mail  (other useful things***)
+                 </ul>
+
+                  <p>Discussion lists include two addition features when the posting policy is set for either "announce" or "automated-notification":
+
+                 <ul>
+                 ***<li>Message "extras" are disallowed, stripping messages of certain mime types.
+                 ***<li>Posted message size restrictions requiring messages to be a minimum of 2 bytes and a maximum of 400 kb. This restriction is not applied to the other types of mailing lists by default but can be set up through domain level administration.
+                 </ul>
+                 -->
+   </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/ProjectOwnerMembers.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerMembers.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerMembers.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,106 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Managing 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>&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">
+    
+    
+    
+
+<title>Managing project members and their roles</title>
+<p>
+<span class=header>Add project members and assigning roles</span>
+<p><span class="PlainText"><b>Project Owner Administration: Index</b>
+<ul>
+<dl>
+<dt><a href="ProjectOwnerAdmin.html">Project Owner Administration</a>
+    <dd><a href="ProjectOwnerNews.html">Managing project site news</a>  
+  <dd><a href="ProjectOwnerFiles.html">Managing project files and documents</a>
+  <dd><b>You are here: Adding project members and assigning roles
+    <ul>
+    <li><a href="#viewingmembers">Viewing project members</a>
+    <li><a href="#invitingmembers">Inviting new members</a>
+    <li><a href="#addingmembers">Adding new members</a>
+    <li><a href="#memberroles">Member roles</a>
+    <li><a href="#memberrequests">Member requests</a>
+    <li><a href="#membertasks">Member issues and tasks</a>
+    </ul></b>
+  <dd><a href="ProjectOwnerMailingLists.html">Managing project mailing lists</a></dd>
+  <dd><a href="ProjectOwnerDocumentation.html">Managing project documentation</a>
+  <dd><a href="ProjectOwnerSource.html">Managing project source code with CVS version control</a>
+  <dd><a href="ProjectOwnerIssues.html">Tracking and managing project issues</a>
+</dl>
+</ul>
+<a href="/servlets/HelpTOC">Back to main Help index</a>
+<p>
+
+<hr noshade size=1>
+<span class="InputHeader">Project members and their roles</span>
+
+<p>A project can succeed or fail depending on the character of the community formed by its members. This is true regardless if the project is open- or closed-source. It is the members who contribute their effort and time (for whatever compensation) to realize the project's ideas and goals. Accordingly, because the project members are so important to the eventual success of the project, it is important that the project owner or whomever she designates to be Project Admin, clearly establish the rules and guidelines determining member participation, including their roles, and articulate what they can expect from the project. 
+<p>
+
+<hr noshade size=1>
+<a name="viewingmembers"></a><span class="InputHeader">Viewing project members</span>
+<p>Project members are often added at the time the project is created. However, you can invite and add new members at any time by going to your Project Home page and clicking on the <i>Members</i> link in the "Project Resources" tool bar. The following discussion first goes through the procedure of inviting someone to be a member of your project, then looks at how to add a new member.
+<p>
+
+<hr noshade size=1>
+<a name="invitingmembers"></a><span class="InputHeader">Inviting new members</span></p>
+Once in the "Members" page, clicking on the "Invite New Members" link on the top right allows you to send an invitation to a prospective member. Click on the link, and a new page opens with fields allowing you to specify the e-mail address or addresses of the persons you wish to invite, and an invitation message. There are two parts to this message. The first, which you compose here, should be in plain text only (HTML is <i>not</i> supported), and should be a greeting and welcoming message. You can, depending on your needs, stipulate here what role you would prefer the invitee to take. There is time later, both for the invitee and for you, as project owner, to change the member's role. 
+<p>The second part of the invitation message comprises the project description which you composed at the time the project was created. If you added several e-mail addresses in the "People to Invite" field, each will receive the same message, so the welcoming message should be inclusive enough to accommodate the interests of the several people you've invited.
+
+<p>You can invite anyone to be a member of your project. They need not, at the time of invitation, already be registered users. However, those you invite who are not registered users are prompted to register on the site as part of viewing your project information.
+<p>
+
+<hr noshade size=1>
+<a name="addingmembers"></a><span class="InputHeader">Adding new members</span>
+<p>Users you have approved for project membership (whether by your invitation or their request), are listed by user name on the <b>Project Members</b> page along with boxes indicating their role or roles (project members may hold more than one role). As project owner, you can change those roles by checking the box by the role name and then clicking on "Revoke Checked Roles" button. 
+
+<p>If you wish to add a registered user (without inviting her beforehand), click on the "Add New Member" button. This takes you to the <b>Add Members</b> page, where all registered user groups and users are listed with empty boxes to the left of their usernames. User groups also include a brief description of the group; individual registered users are listed by both user name and real name. Each user name links to the user's profile, so you can learn something about that user before adding the user by checking the "Add" box.
+<p>You can add as many users to your project as you wish. Because every member in a project must have a role, when you add someone to your project you must, at the same time, specify her role. Accordingly, at the bottom of the <b>Add Members</b> page there is a box listing all available roles. Once you have selected the user(s) you want and the appropriate role(s), click on the <b><i>Grant Roles</i></b> button. Those users will be added to your project with the roles you have stipulated. For more information about member roles, see the help information on <a href="ProjectRoles.html">project roles</a>.
+<p>
+
+<hr noshade size=1>
+<a name="memberroles"></a><span class="InputHeader">Member roles</span>
+<p>Members have roles; these roles are usually specified when the member is invited, or when you add a member. However, as project owner, you can later change the role given to a member by clicking on the member's underlined name and changing the role already assigned to her. If you wish to revoke a role, check the box adjacent to the stipulated role and then "Revoke Member Roles."
+<p>You can also change your own role in the project. First, click on the underlined "Request New Project Role" link on the upper right. Doing so takes you to the "Membership Request" page, where you can see your current role and choose a new role. After you have chosen, click "Submit Request."
+<p>
+
+<hr noshade size=1>
+<a name="memberrequests"></a><span class="InputHeader">Member requests</span>
+<p>A member might request a new role at any time. As project owner, you can approve, reject, or defer the request. To do any of these, check the appropriate box under the "Requests Pending Approval" and "Edit Roles" headings. The change is effective immediately.
+<p>
+
+<hr noshade size=1>
+<a name="membertasks"></a><span class="InputHeader">Member issues and tasks</span>
+<p>This site's issue tracking tool enables you to manage and assign tasks to your project members. An "issue" in broad terms basically refers to project activities to be done.  As the project owner, you may assign issues to members, or you can give other members the ability to assign issues by virtue of their role or expertise. To learn more about issue tracking and administration, see the <a href="ProjectIssues.html">project issues</a> help information.
+
+<hr noshade size=1>
+<a href="ProjectOwnerAdmin.html">Back to Project Owner Administration help</a><br>
+<a href="/servlets/HelpTOC">Back to main Help index</a></p>
+</span>
+</tr>
+</table>
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerMembers.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerMembers.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerMembers.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,148 @@
+<!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/tigris.js" type="text/javascript"></script>
+  <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+  <title>Add project members and assigning roles</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="projectownermembers">
+   <h2>Add project members and assigning roles</h2>
+
+   <div id="toc">
+    <ul>
+     <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+    </ul>
+
+    <ul>
+      <li> <a href="/nonav/scdocs/ProjectOwnerAdmin.html">Project owner administration</a> 
+        <ul>
+          <li><a href="/nonav/scdocs/ProjectOwnerEdit.html">Editing and maintaining 
+            the Project Home page</a></li>
+          <li><a href="/nonav/scdocs/ProjectOwnerNews.html">Managing project site 
+            announcements</a></li>
+          <li>Adding project members and approving roles 
+             <ul>
+              <li><a href="#viewingmembers">Viewing project members</a></li>
+              <li><a href="#invitingmembers">Inviting new members</a></li>
+              <li><a href="#addingmembers">Adding new members</a></li>
+              <li><a href="#memberroles">Member roles</a></li>
+              <li><a href="#addroles">Adding new roles</a></li>
+              <li><a href="#memberrequests">Member requests</a></li>
+              <li><a href="#membertasks">Member issues and tasks</a></li>
+            </ul>
+          </li>
+          <li><a href="/nonav/scdocs/ProjectOwnerMailingLists.html">Managing project 
+            mailing lists</a></li>
+          <li><a href="/nonav/scdocs/ProjectOwnerDocuments.html">Managing project 
+            documentation</a></li>
+          <li><a href="/nonav/scdocs/ProjectOwnerSource.html">Managing project source 
+            code</a></li>
+          <li><a href="/nonav/scdocs/ProjectOwnerIssues.html">Tracking and managing 
+            project issues</a></li>
+          <li><a href="/nonav/scdocs/ProjectOwnerCustomStyle.html">Managing custom 
+            HTML styling</a></li>
+        </ul>
+      </li>
+    </ul>
+   </div>
+   <h3>Project members and their roles</h3>
+
+   <p>A project can succeed or fail depending on the character of the community formed by its members. This is true regardless if the project is open- or closed-source. It is the members who contribute their effort and time (for whatever compensation) to realize the project's ideas and goals. Accordingly, because the project members are so important to the eventual success of the project, it is important that the project owner or whomever she designates to be Project Admin, clearly establish the rules and guidelines determining member participation, including their roles, and articulate what they can expect from the project.</p>
+
+   <h3><a id="viewingmembers" name="viewingmembers">Viewing project members</a></h3>
+
+   <p>Project members are often added at the time the project is created. However, you can invite and add new members at any time by going to your Project Home page and clicking on the <i>Membership</i> link. The following discussion first goes through the procedure of inviting someone to be a member of your project, then looks at how to add a new member.</p>
+
+   <h3><a id="invitingmembers" name="invitingmembers">Inviting new members</a></h3>
+
+   <p>Once in the "Membership" page, clicking on the "Invite New Members" link allows you to send an invitation to a prospective member. Click on the link, and a new page opens with fields allowing you to specify the e-mail address or addresses of the persons you wish to invite, and an invitation message. There are two parts to this message. The first, which you compose here, should be in plain text only (HTML is <i>not</i> supported), and should be a greeting and welcoming message. You can, depending on your needs, stipulate here what role you would prefer the invitee to take. There is time later, both for the invitee and for you, as project owner, to change the member's role.</p>
+
+   <p>The second part of the invitation message comprises the project description which you composed at the time the project was created. If you added several e-mail addresses in the "People to Invite" field, each will receive the same message, so the welcoming message should be inclusive enough to accommodate the interests of the several people you've invited.</p>
+
+   <p>You can invite anyone to be a member of your project. They need not, at the time of invitation, already be registered users. However, those you invite who are not registered users are prompted to register on the site as part of viewing your project information.</p>
+
+   <h3><a id="addingmembers" name="addingmembers">Adding new members</a></h3>
+
+   <p>Users you have approved for project membership (whether by your invitation or their request), are listed by user name on the <b>Project Membership</b> page along with boxes indicating their role or roles (project members may hold more than one role). As project owner, you can change those roles by checking the box by the role name and then clicking on "Revoke Checked Roles" button.</p>
+
+   <p>If you wish to add a registered user (without inviting her beforehand), click on the "Add New Member" button. This takes you to the <b>Add Members</b> page, where all registered user groups and users are listed with empty boxes to the left of their usernames. User groups also include a brief description of the group; individual registered users are listed by both user name and real name. Each user name links to the user's profile, so you can learn something about that user before adding the user by checking the "Add" box.</p>
+
+   <p>You can add as many users to your project as you wish. Because every member in a project must have a role, when you add someone to your project you must, at the same time, specify her role. Accordingly, on the <b>Add Members</b> page there is a box listing all available roles. Once you have selected the user(s) you want and the appropriate role(s), click on the <b><i>Grant Roles</i></b> button. Those users will be added to your project with the roles you have stipulated. For more information about member roles, see the help information on <a href="/nonav/docs/ProjectRoles.html">project roles</a>.</p>
+
+   <h3><a id="memberroles" name="memberroles">Member roles</a></h3>
+
+   <p>Project member roles are specified when the member is invited, or added by the Project owner. If you wish to revoke a role, check the box adjacent to the stipulated role and then "Revoke Member Roles." As project owner, you can change the role given to a member by clicking on the <b>Add new member/role</b> link on the <strong>Membership</strong> page. This link takes you to the <b>Add new member/role</b> page.</p>
+   
+   To grant a new role to project members, select the member you wish to grant the new role by selecting the "Add" check box next to his or her user name. You can select multiple users to grant role, or use the "Mass add" text box to enter several user names at once. Next, select the roles you wish to grant from the <b>Grant these roles to all designated users</b> box and click the <b>Grant roles</b> button. If you wish to return to the <b>Membership</b> page immediately after granting roles, select the <b>Done granting roles</b> check box before clicking <b>Grant roles</b>.
+
+   <p>If no existing role fits the needs of your project, as the Project Owner you can create roles specific to your project. To learn how to create project roles see <a href="#addroles">Adding project roles</a></p>
+
+   <p>You can also change your own role in the project. First, click on the underlined "Request New Project Role" link. Doing so takes you to the "Membership Request" page, where you can see your current role and choose a new role. After you have chosen, click "Submit Request."</p>
+
+   <h3><a id="addroles" name="addroles">Adding project roles</a></h3>
+
+   <p>You have the option to create custom roles and assign the appropriate permissions to them to meet the needs of your project. You should take some time to plan the scope of any new role you create before beginning the creation process. Project roles enable associated user actions within your project only.</p>
+
+   <ol>
+    <li>Enter the project for which you wish to add new roles and click the <b>Edit project</b> link.</li>
+
+    <li>Click the <b>Edit project-specific roles</b> link to access the <b>Roles</b> page.</li>
+
+    <li>Click the <b>Add new role</b> link.</li>
+
+    <li>Enter a name and a description of the role. The role name can be up to 99 characters in length and cannot include a period (.).</li>
+
+    <li>Select the level of functionality required for this role. Each functional item controls the level of access for the role. The following options can be selected by click on the check box next to the item: 
+
+     <ul>
+      <li><b>Requestable</b>: makes the role requestable by users on the site. If this item is not selected, the role must be assigned by an administrator or a project owner.</li>
+      
+      <li><b>Ownership role</b>: grants users with this role "ownership" of functions within the project. Owners receive administrative email pertaining to the function of which they have ownership.</li>
+      
+      
+      <li><b>Grant role on subproject creation</b>: grants the role to users who create new subprojects.</li>
+
+      <li><b>Block recursion into private projects</b>: item when checked prevents a user with this role in a project from having the same role in subprojects. For example, when selected a user with the Project Owner role in the "Games" project cannot have the Project Owner role in the "Dominos" subproject.</li>
+
+     </ul>
+    </li>
+
+    <li>To assign permissions to the role you can either clone an existing role by selecting a role from the drop down menu or you can assign specific permissions to the role. To assign specific permissions, click the check box under the <b>Add</b> field by the name of the permission you desire.</li>
+
+    <li>
+     <p>Click the <b>Create role</b> button. Use this feature with extreme caution! Assigning permissions to roles may have security implications.</p>
+    </li>
+   </ol>
+
+   <p>Some permissions you associate with roles require the assignment of resources. Assigning resources allows you to limit the areas of the project that can be affected by persons with the permission. Those permission for which you can assign resources have a drop down box in the resource column in the Project permissions table. Use this box to determine which project resources to allocate the role's new permissions.</p>
+
+   <p>Selecting ".*" applies the selected permissions for this role universally to all project resources available to this role, including both web content and source code.</p>
+
+   <p>Choosing the "/www/.*" option within this list limits the selected permission for this role specifically to web pages. This means the scope of this permission does not pertain to any source code level access, but only to web page content. For example, assigning the "Version Control - Commit" permission to a role and designating "/www/.*" as the resource results in users with this role only being able to check out and commit web page content, not project source code.</p>
+
+   <p>After you have selected the permissions to add and determined the site resources to apply these to, click the <b>Create role</b> button.</p>
+
+   <h3><a id="memberrequests" name="memberrequests">Member requests</a></h3>
+
+   <p>A member might request a new role at any time. As project owner, you can approve, reject, or defer the request. To do any of these, check the appropriate box under the "Requests Pending Approval" and "Edit Roles" headings. The change is effective immediately.</p>
+
+   <h3><a id="membertasks" name="membertasks">Member issues and tasks</a></h3>
+
+   <p>This site's issue tracking tool enables you to manage and assign tasks to your project members. An "issue" in broad terms basically refers to project activities to be done. As the project owner, you may assign issues to members, or you can give other members the ability to assign issues by virtue of their role or expertise. To learn more about issue tracking and administration, see the <a href="/nonav/docs/ProjectIssues.html">issue tracking</a> help information.</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