openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1010077 [9/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/market...
Date Sat, 08 Apr 2017 23:00:14 GMT
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminAuditLogs.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminAuditLogs.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminAuditLogs.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>&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">
+    
+    
+    
+  <div class="docs" id="domadminauditlogs">
+   <h2>Using domain administration tools</h2>
+
+   <div class="toc">
+    <h3>Help for domain administration: Index</h3>
+
+    <ul>
+     <li>
+      <a href="DomAdminOverview.html">Domain administration overview</a> 
+
+      <ul>
+       <li><a href="DomAdminAddUsers.html">Adding and editing user accounts</a></li>
+
+       <li><a href="DomAdminRoles.html">Administering roles and permissions</a></li>
+
+       <li><a href="DomAdminUserGroups.html">Creating and editing user groups</a></li>
+
+       <li><a href="DomAdminProjectGroups.html">You are here: Creating and editing project groups</a></li>
+
+       <li><a href="DomAdminProjectApproval.html">Approving, disapproving, or deferring projects</a></li>
+
+       <li>
+        <strong>You are here:</strong> Using domain administration tools 
+
+        <ul>
+         <li><b><a href="#auditlog">About the administrative audit log</a></b></li>
+
+         <li><b><a href="#monitorsessions">Monitoring user sessions</a></b></li>
+        </ul>
+       </li>
+      </ul>
+     </li>
+    </ul>
+   </div>
+
+   <div class="courtesylinks">
+    <p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
+   </div>
+
+   <h3><a id="auditlog" name="auditlog">About the administrative audit log</a></h3>
+
+   <p>All site-level administrative actions are logged and you can view this information using the <i>Administer Audit Logs</i> link in the "Admin Options" section of your <b>Start Page</b>. The Audit Log keeps a cumulative record of key administrative events in your domain. Optionally you can append notes to log entries preserve more detailed historical information.</p>
+
+   <p>The Audit Log displays 50 entries per page identified by date/time, person, and location, logging the most recent actions in the first page displayed. The log may be filtered on any of the fields displayed to extrapolate specific site information. For example, if you are not the only domain administrator on your site, the log can provide a useful reference of the administrative actions conducted by each person. Also, log actions for specific projects yield detailed histories of the project beginning from its inception.</p>
+
+   <p>Logged domain admin actions include:</p>
+
+   <ul>
+    <li>user additions</li>
+
+    <li>user deletions</li>
+
+    <li>user edits</li>
+
+    <li>project creation</li>
+
+    <li>project edits</li>
+
+    <li>project deletion</li>
+
+    <li>granting a role in a project</li>
+
+    <li>revoking a role in a project</li>
+
+    <li>project group creation</li>
+
+    <li>project group edit (adding or removing a project or other attributes)</li>
+
+    <li>project group delete</li>
+
+    <li>user group creation</li>
+
+    <li>user group edit (adding or deleting members or other attributes)</li>
+
+    <li>user group deletion</li>
+
+    <li>starting or stopping task runner</li>
+
+    <li>role creation</li>
+
+    <li>role edit</li>
+
+    <li>role delete</li>
+
+    <li>permission creation, edit, delete</li>
+
+    <li>resource scope creation, edit, delete</li>
+
+    <li>operations from StaticUtils page</li>
+   </ul>
+
+   <h3><a id="monitorsessions" name="monitorsessions">Monitoring user sessions</a></h3>
+
+   <p>You can also view about currently site activity at any given time by clicking the <i>Active User Sessions</i> link in the "Admin Options" section of your <b>Start Page</b>. This provides a snapshot view of who is currently logged in to your site. Although this information is not logged or stored long term, periodically viewing active sessions may provide some insight into who is using your site.</p>
+
+   <p>If you require more formal user statistical information, you must contact this site's host administrator.</p>
+
+   <div class="courtesylinks">
+    <p><a href="DomAdminOverview.html">Back to help for domain administration</a><br />
+    <a href="/servlets/HelpTOC">Back to main Help index</a></p>
+   </div>
+  </div>
+ 
+
+
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminLicenseAdmin.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminLicenseAdmin.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminLicenseAdmin.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,114 @@
+<!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>Administering licenses</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="domadminlicense">
+   <h2><a id="DomAdminLicenseAdmin" name="domadminlicenseadmin">Administering Licenses</a></h2>
+
+   <div id="toc">
+    <ul>
+     <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+    </ul>
+
+    <dl>
+     <dt><a href="/nonav/docs/DomAdminOverview.html">Help for domain administration</a></dt>
+
+     <dd>
+      <ul>
+       <li><a href="/nonav/docs/DomAdminAddUsers.html">Adding and editing user accounts</a></li>
+
+       <li><a href="/nonav/docs/DomAdminRoles.html">Administering roles and permissions</a></li>
+
+       <li><a href="/nonav/docs/DomAdminUserGroups.html">Creating and editing user groups</a></li>
+
+       <li><a href="/nonav/docs/DomAdminProjectGroups.html">Creating and editing project groups</a></li>
+
+       <li><a href="/nonav/docs/DomAdminProjectApproval.html">Approving, disapproving, or deferring projects</a></li>
+
+       <li><a href="/nonav/docs/DomAdminAuditLogs.html">Using administrative utilities</a></li>
+
+       <li>Administering Licenses</li>
+
+       <li>
+        <ul>
+         <li><a href="#overview">Overview of licenses</a></li>
+
+         <li><a href="#add">Creating a new license</a></li>
+
+         <li><a href="#detail">Viewing a license</a></li>
+
+         <li><a href="#edit">Editing a license</a></li>
+
+         <li><a href="#delete">Deleting a license</a></li>
+        </ul>
+       </li>
+      </ul>
+     </dd>
+    </dl>
+   </div>
+
+   <h3><a id="overview" name="overview"></a>Overview of licenses</h3>
+
+   <p>Licensing a project is an important component of controlling how your project output is used. It is critical to consider all the components in any license you choose to associate with your project. When considering your project license you can choose from a list of popular, preconfigured licenses or create your own.</p>
+
+   <p>Licenses are orignially associated during the project creation process (see <a href="/nonav/docs/ProjectAdd.html">Create a New Project</a>), but can be altered by users with the proper permissions. Users with the "Project - Edit" permission (by default the Project Owner and all Administrator roles have this permission) can change the license associated with the project in which they have the proper permission. New licenses can be created, edited or deleted by users with the "Licenses - Administer" permission (by default the domain and host admin roles).</p>
+
+   <h3><a id="detail" name="detail">Viewing licenses</a></h3>
+
+   <p>Selecting any item from the <b>Admin Options</b> items will direct you to the <b>Admin Options</b> function. At this point you can select <b>Licenses</b> from the <b>Admin Options</b> menu. A page with a list of all currently available licenses and add, edit and delete links will appear.</p>
+
+   <p>If you need the text of a specific license, you can click on the name of the license. You will find yourself on a new screen with the text of the license. To return, click your browsers back button.</p>
+
+   <h3><a id="add" name="add">Creating a new license</a></h3>
+
+   <p>Clicking on the <b>Add New License</b> link will present you with two fields to describe your new license. On this page, you will need to give your license a name. The name can be up to 65 characters in length. You must also provide information in the description field. This text can have one of the following characteristics:</p>
+
+   <ul>
+    <li>A url that links to the text of the license</li>
+
+    <li>A description of the license. You may include a url to the full text of the license as well.</li>
+
+    <li>The complete text of the license. You can use HTML formatting to enhance your layout.</li>
+   </ul>
+
+   <p>After you have completed your description, click on the <b>Submit</b> button.</p>
+
+   <h3><a id="edit" name="edit">Editing a license</a></h3>
+
+   <p>From the list of licenses, clicking on the name of a license will give you access to editing the name and the description of the license. The name of the license cannot exceed 65 characters in length. The <b>Description</b> field has no limits in character length, but you should use this field to provide one of the following characteristics:</p>
+
+   <ul>
+    <li>A url that links to the text of the license</li>
+
+    <li>A description of the license. You may include a url to the full text of the license as well.</li>
+
+    <li>The complete text of the license. You can use HTML formatting to enhance your layout.</li>
+   </ul>
+
+   <p>After you have completed your description, click on the <b>Submit Changes</b> button.</p>
+
+   <h3><a id="delete" name="delete">Deleting a license</a></h3>
+
+   <p>You can delete licenses that are no longer required in your domain. Any license that is associated with one or more projects cannot be deleted. On the page listing the licenses are all the licenses currently available in the domain; any license that is currently not associated with any project will have a <b>Delete</b> link next to the name. Those without the <b>Delete</b> link have at least one associated project.</p>
+
+   <p>To delete a license find the name of the license and click on the <b>Delete</b> link next to the name. You must approve the deletion on the next page by clicking on the <b>Confirm Delete</b> button. If you do not want to delete the license, use your browser's back button to return to the previous page. Once a license has been deleted you will no longer see it in your list of available licenses.</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/DomAdminOverview.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminOverview.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminOverview.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,120 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Domain Administration Overview</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">Domain administration overview</span>
+<p>
+<span class="PlainText"><b>Help for domain administration: Index</b>
+<p>
+<ul>
+  <dl>
+  <dt><b>You are here: Domain administration overview
+  </b><ul><b>
+  <li><a href="#webadmin">Concepts in web-based administration</a>
+  <li><a href="#adminstartpage">About your Start Page</a></b>
+  </ul>
+    <dd><a href="DomAdminAddUsers.html">Adding and editing user accounts</a>
+    <dd><a href="DomAdminRoles.html">Administering roles and permissions</a>
+    <dd><a href="DomAdminUserGroups.html">Creating and editing user groups</a>
+    <dd><a href="DomAdminProjectGroups.html">Creating and editing project groups</a>
+    <dd><a href="DomAdminProjectApproval.html">Approving, disapproving, or deferring projects</a>
+    <dd><a href="DomAdminAuditLogs.html">Using domain administration tools</a>
+ <dt> <a href="/servlets/HelpTOC">Back to main Help index</a>
+  </dl>
+</ul>
+<p>
+
+<hr noshade size=1>
+<a name="webadmin"></a><span class="InputHeader">Concepts in web-based administration</span>
+<p>
+Administration of this site is web-based, enabling you as the Domain Administrator to access certain administrative web pages that are restricted to other users. Administrative options are also included in pages accessible to other users, but are only displayed to you due to your unique permissions.
+<p>
+Several essential concepts govern this site's administrative web pages: </p>
+
+<ul>
+<li><b>Users</b> are individuals who have either registered with this site or had a user account created by you. Each individual user has a unique user name and password. They also play one or more given roles on the site with certain permissions. You set the operating parameters for how individual users and groups of users to interact with this site.</li>
+<p>
+<li><b>User Groups</b> are sets of users that you can create and collectively grant roles and permissions according to your organization's needs.
+<p>
+<li><b>Projects</b> are collections of modules, members, and mailing lists. Each project has its own subdomain, such as http://projectname.thisdomain. When projects are created on this site, the following  automatically establish:
+<p>
+  <ul>
+  <li>a home page and supporting project pages to access hosted tools and site features
+  <li>a dedicated issue tracking database
+  <li>a top-level source code module for version control of project files
+  <li>a default set of mailing lists for developers to communicate with one another and to receive notifications of project events.
+  </ul>
+ </li>
+<p>
+<li><b>Project Groups and Categories</b> enable easier site-wide administration of hosted projects. Project Groups contain multiple projects, and are created and administered by you according to your organization's needs. Project Groups can also contain groups of users. Categories are a unique kind of project group to provide a way for organizing all projects on the site by development type to summarize this information on all users' start pages.
+<p>
+<li><b>Roles and Permissions</b> are the means by which users are able to conduct activities on this site. A unique permission governs every single user action possible; roles are pre-packaged sets of permissions granted to users. You can also assign roles to users collectively via user groups.
+<p>
+<li><b>Resources</b> are all of the different elements used in this site including the tools, content, projects, and web pages. User roles and permissions on this site are defined by the specific resources they apply to.
+</ul>
+<p>
+The development environment and integrated tool set on this site is modeled around the suggest-and-approve workflow common to open source software development methodology. Although this site features "prepackaged" resources, user roles, project settings, and tool configurations as a matter of convenience, you can either use these default settings "as is" or alter them to address particular community, project, or organizational needs. Read more about how to access domain administrative features in the next section, "About your Start Page."
+<p>
+
+<hr noshade size=1>
+<a name="adminstartpage"></a><span class="InputHeader">About your Start Page</span>
+<p>
+When you log in, your view of the Start Page features an <b><i>Admin Options</i></b> section with direct links to administrative screens where you conduct these domain level tasks:
+<p>
+<dl>
+<dt><b><i>Administer Projects</i></b>
+  <dd>Displays a comprehensive, alphabetical listing of all projects hosted on this site with links to project home pages. Includes a filtering option and a link to add new projects. See <a href="DomAdminProjectApproval.html">Approving, deferring, and disapproving projects</a> for further information.
+<p>
+<dt><b><i>Administer Users</i></b>
+  <dd>Displays a comprehensive, alphabetical listing of all users registered on this site with links to individual user account information. Includes a link for adding new users. See <a href="DomAdminAddUsers.html">Adding and editing user accounts</a> for further information.
+<p>
+<dt><b><i>Administer Roles</i></b>
+  <dd>Displays a screen listing all user roles available on the site, both at the domain level and within projects. Roles are sets of permissions that determine which site activities users can access. See <a href="DomAdminRoles.html">Administering roles and permissions</a> for further information.
+<p>
+<dt><b><i>Active User Sessions</i></b>
+  <dd>Displays a page logging currently active user sessions with login date/timestamp, last servlet accessed, and previous access date/timestamp information. This page provides a status snapshot of current, real-time site activity. See <a href="DomAdminAuditLogs.html#monitorsessions">Monitoring user sesions</a> for further information.
+<p>
+<dt><b><i>Project Groups and Categories</i></b>
+  <dd>Displays a listing of all project groups and categories on this site. Includes links to create or edit groups and categories. See <a href="DomAdminProjectGroups.html">Creating and editing project groups</a> for further information.
+<p>
+<dt><b><i>Administer User Groups</i></b>
+  <dd>Displays a listing of all groups of users on this site. Includes links to create or edit user groups. See <a href="DomAdminUserGroups.html">Creating and editing user groups</a> for further information.
+<p>
+<dt><b><i>Administrative Audit Log</i></b>
+  <dd>Displays a summary log page of numerous site activities with date/time stamps and other event identifying information. Includes links to a detail page for each event. See <a href="DomAdminAuditLogs.html">Using administrative audit logs</a> for further information.
+</dl>
+<p>
+Specific requests requiring your immediate attention appear in the "Pending Actions" section immediately following the administrative section.
+<p>
+As the Domain Administrator, you are the gatekeeper of the site, and you effectively "own" all the projects hosted here. You also own two special projects that are included in the "My projects" section of your <b>Start Page</b>: the "www" and "look" projects. These contain this site's domain-level content pages and data files. They are only accessible to users with domain-level administrative permissions, i.e. domain administrators such as you.
+<p>
+<hr noshade size=1>
+<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/DomAdminOverview.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminOverview.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminOverview.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,128 @@
+<!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>Domain administration overview</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="domadminoverview">
+   <h2>Domain administration overview</h2>
+
+   <div id="toc">
+    <ul>
+     <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+    </ul>
+
+    <ul>
+     <li>
+      Domain administration overview 
+
+      <ul>
+       <li><a href="#webadmin">Concepts in web-based administration</a></li>
+
+       <li><a href="#adminstartpage">About your Start Page</a></li>
+      </ul>
+     </li>
+
+     <li><a href="/nonav/docs/DomAdminAddUsers.html">Adding and editing user accounts</a></li>
+
+     <li><a href="/nonav/docs/DomAdminRoles.html">Administering roles and permissions</a></li>
+
+     <li><a href="/nonav/docs/DomAdminUserGroups.html">Creating and editing user groups</a></li>
+
+     <li><a href="/nonav/docs/DomAdminProjectGroups.html">Creating and editing project groups</a></li>
+
+     <li><a href="/nonav/docs/DomAdminProjectApproval.html">Approving, disapproving, or deferring projects</a></li>
+
+     <li><a href="/nonav/docs/DomAdminAuditLogs.html">Using domain administration tools</a></li>
+    </ul>
+   </div>
+
+   <h3><a id="webadmin" name="webadmin">Concepts in web-based administration</a></h3>
+
+   <p>Administration of this site is web-based, enabling you as the Domain Administrator to access certain administrative web pages that are restricted to other users. Administrative options are also included in pages accessible to other users, but are only displayed to you due to your unique permissions.</p>
+
+   <p>Several essential concepts govern this site's administrative web pages:</p>
+
+   <ul>
+    <li><b>Users</b> are individuals who have either registered with this site or had a user account created by you. Each individual user has a unique user name and password. They also play one or more given roles on the site with certain permissions. You set the operating parameters for how individual users and groups of users to interact with this site.</li>
+
+    <li><b>User Groups</b> are sets of users that you can create and collectively grant roles and permissions according to your organization's needs.</li>
+
+    <li>
+     <b>Projects</b> are collections of modules, members, and mailing lists. Each project has its own subdomain, such as http://projectname.thisdomain. When projects are created on this site, the following automatically establish: 
+
+     <ul>
+      <li>a home page and supporting project pages to access hosted tools and site features</li>
+
+      <li>a dedicated issue tracking database</li>
+
+      <li>a top-level source code module for version control of project files</li>
+
+      <li>a default set of mailing lists for developers to communicate with one another and to receive notifications of project events.</li>
+     </ul>
+    </li>
+
+    <li><b>Project Groups and Categories</b> enable easier site-wide administration of hosted projects. Project Groups contain multiple projects, and are created and administered by you according to your organization's needs. Project Groups can also contain groups of users. Categories are a unique kind of project group to provide a way for organizing all projects on the site by development type to summarize this information on all users' start pages.</li>
+
+    <li><b>Roles and Permissions</b> are the means by which users are able to conduct activities on this site. A unique permission governs every single user action possible; roles are pre-packaged sets of permissions granted to users. You can also assign roles to users collectively via user groups.</li>
+
+    <li><b>Resources</b> are all of the different elements used in this site including the tools, content, projects, and web pages. User roles and permissions on this site are defined by the specific resources they apply to.</li>
+   </ul>
+
+   <p>The development environment and integrated tool set on this site is modeled around the suggest-and-approve workflow common to open source software development methodology. Although this site features "prepackaged" resources, user roles, project settings, and tool configurations as a matter of convenience, you can either use these default settings "as is" or alter them to address particular community, project, or organizational needs. Read more about how to access domain administrative features in the next section, "About your Start Page."</p>
+
+   <h3><a id="adminstartpage" name="adminstartpage">About your Start Page</a></h3>
+
+   <p>When you log in, your view of the Start Page features an <b><i>Admin Options</i></b> section with direct links to administrative screens where you conduct these domain level tasks:</p>
+
+   <dl>
+    <dt>Administer Projects</dt>
+
+    <dd>Displays a comprehensive, alphabetical listing of all projects hosted on this site with links to project home pages. Includes a filtering option and a link to add new projects. See <a href="/nonav/docs/DomAdminProjectApproval.html">Approving, deferring, and disapproving projects</a> for further information.</dd>
+
+    <dt>Administer Users</dt>
+
+    <dd>Displays a comprehensive, alphabetical listing of all users registered on this site with links to individual user account information. Includes a link for adding new users. See <a href="/nonav/docs/DomAdminAddUsers.html">Adding and editing user accounts</a> for further information.</dd>
+
+    <dt>Administer Roles</dt>
+
+    <dd>Displays a screen listing all user roles available on the site, both at the domain level and within projects. Roles are sets of permissions that determine which site activities users can access. See <a href="/nonav/docs/DomAdminRoles.html">Administering roles and permissions</a> for further information.</dd>
+
+    <dt>Active User Sessions</dt>
+
+    <dd>Displays a page logging currently active user sessions with login date/timestamp, last servlet accessed, and previous access date/timestamp information. This page provides a status snapshot of current, real-time site activity. See <a href="/nonav/docs/DomAdminAuditLogs.html#monitorsessions">Monitoring user sesions</a> for further information.</dd>
+
+    <dt>Project Groups and Categories</dt>
+
+    <dd>Displays a listing of all project groups and categories on this site. Includes links to create or edit groups and categories. See <a href="/nonav/docs/DomAdminProjectGroups.html">Creating and editing project groups</a> for further information.</dd>
+
+    <dt>Administer User Groups</dt>
+
+    <dd>Displays a listing of all groups of users on this site. Includes links to create or edit user groups. See <a href="/nonav/docs/DomAdminUserGroups.html">Creating and editing user groups</a> for further information.</dd>
+
+    <dt>Administrative Audit Log</dt>
+
+    <dd>Displays a summary log page of numerous site activities with date/time stamps and other event identifying information. Includes links to a detail page for each event. See <a href="/nonav/docs/DomAdminAuditLogs.html">Using administrative audit logs</a> for further information.</dd>
+   </dl>
+
+   <p>Specific requests requiring your immediate attention appear in the "Pending Actions" section immediately following the administrative section.</p>
+
+   <p>As the Domain Administrator, you are the gatekeeper of the site, and you effectively "own" all the projects hosted here. You also own two special projects that are included in the "My projects" section of your <b>Start Page</b>: the "www" and "look" projects. These contain this site's domain-level content pages and data files. They are only accessible to users with domain-level administrative permissions, i.e. domain administrators such as you.</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/DomAdminProjectApproval.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminProjectApproval.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminProjectApproval.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,110 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Approving projects</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">
+    
+    
+    
+   
+<p>
+<span class="Header">Approving, deferring, or disapproving projects</span>
+<p>
+<span class="PlainText"> 
+<b>Help for domain administration: Index</b>
+<p>
+<ul>
+  <dl>
+  <dt><a href="DomAdminOverview.html">Domain administration overview</a>
+    <dd><a href="DomAdminAddUsers.html">Adding and editing user accounts</a>
+    <dd><a href="DomAdminRoles.html">Administering roles and permissions</a>
+    <dd><a href="DomAdminUserGroups.html">Creating and editing user groups</a>
+    <dd><a href="DomAdminProjectGroups.html">You are here: Creating and editing project groups</a>
+    <dd><b>You are here: Approving, disapproving, or deferring projects
+    <ul>
+    <li><a href="#aboutapproval">About the project approval process</a>
+    <li><a href="#deferdisapprove">Deferring and disapproving projects</a>
+    <li><a href="#other">Locking, unlocking, and deleting projects</a>
+    </ul></b>
+    <dd><a href="DomAdminAuditLogs.html">Using domain administration tools</a>
+      <dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+  </dl>
+</ul>
+<p>
+
+<hr noshade size=1>
+<a name="aboutapproval"></a><span class="InputHeader">About the project approval process</span>
+<p>
+When a project is proposed on this site, it appears in the <i>Proposed Projects</i> link in the "Pending Actions" section of the Domain Administrator's <b>Start Page</b>. The next time you log in, this count indicates how many projects are awaiting your action. Taking no action has the same result as deferring a project; they remain effectively in limbo as pending actions.
+<p>
+Click the <i>Proposed Projects</i> link in the "Pending Actions" section to display the <b>Project Approval</b> page. An alphabetical listing of all pending projects appears with the proposer's name and a project summary included. Project titles link to each project's home page. The proposer's name links to the <b>Edit User</b> screen containing this user's account information.
+<p>
+As the Domain Administrator, you disperse with pending projects in one of three ways: approve, defer, or disapprove them by placing checkmarks in the appropriate boxes. All of these actions are tracked in an administrative audit log, along with other administrative actions. See <a href="DomAdminAuditLogs.html">Using administrative audit logs</a> for further information.
+<p>
+The criteria for approving or disapproving proposed projects falls within your judgment as the Domain Administrator. Factors to consider might include:
+<ul>
+<li>Does the project fall within your site's overall mission and general goals?
+<li>Is the project well scoped out? 
+<li>Are project objectives clearly stated?
+</ul>
+<p>
+When you approve a project, an email message is automatically generated notifying the Project Owner. The project appears in the site's hosted project listings, including the <b>Hosted Projects</b> page and the appropriate category home page(s). The Project Owner can now approve members and grant roles to them.
+<p>
+
+<hr noshade size=1>
+<a name="deferdisapprove"></a><span class="InputHeader">Deferring or disapproving projects</span>
+<p>
+While your approval of a project is pending, or when you defer approval, the project simply remains in your list of pending projects awaiting approval. It does not appear within any project listings in public pages or to any other users. The proposer, however, continues to see a link to this project in her/his <b>Start Page</b> under the "My Projects" section, and can conduct most project related activities including:
+<ul>
+<li>accessing and updating their project's home page
+<li>inviting participants
+<li>uploading and downloading project files and documents
+<li>adding and editing news items
+<li>checking source code into the project's CVS repository
+<li>assigning and tracking project issues.
+</ul>
+None of this project information on pending projects is visible to other site users, however. And until you approve a pending project, the Project Owner <i>cannot</i> approve project members or grant roles to them.
+<p>
+When you disapprove a project, an email message is automatically generated to notify the proposer. This message is brief; the proposer is encouraged to contact you for further discussion about the specific reasons for disapproval. 
+<p>
+
+<hr noshade size=1>
+<a name="other"></a><span class="InputHeader">Locking, unlocking, and deleting projects</span>
+<p>
+The Project Lock feature enables you to stop all activity on a project if circumstances arise to necessitate this. Whether this is due to site policy matters, technical issues, or other reasons, project locking lets you essentially turn off all site-related project activity. The locked project's home page and other pages can still be accessed and all existing project data is intact, however the Project Owner and members have read-only access to the source code repository, email archives, issue database, project files, and documents.  No one -- including the project owner -- can commit source code, enter issues, upload or download files and documents, change web content, or subscribe to or modify mailing lists. If the locked project is a public project, other site users can still view the project's home page but the project is flagged as "locked."
+<p>
+To lock a currently active project, navigate to the project's home page and click on the <i>Admin</i> link in the Project Resources tool bar to display the <b>Project Edit</b> page. Use the <i>Project Lock</i> link at the bottom to display a screen where you can set the lock. This action automatically generates an email notice to the project owner, telling him/her to contact a site administrator immediately. 
+<p>
+To unlock a project, your view of the locked project's home page displays the red "Locked" flag and an <i>Unlock</i> link next to it you can use to enable the project again. Alternatively, you can use the <b>Project Edit</b> page where there an <b>Unlock Project</b> link appears at the bottom of the page. When you unlock a project to reactivate it, another email notice is automatically sent to the project owner.
+<p>
+Projects may also be deleted from this site when they either don't pan out or reach the end of their development life cycle. The <b>Project Edit</b> page includes a <i>Project Delete</i> link at the bottom of the page. If you click this link, you are asked to confirm the action. <b><i>Use the project delete feature with caution!</i> Deleting the project not only removes it from site project listings, but also completely erases the project's cvs repository files, all project files and documents, issues database, and mailing list archives.</b>
+<p>
+
+<hr noshade size=1>
+<a href="DomAdminOverview.html">Back to help for domain administration</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/DomAdminProjectApproval.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminProjectApproval.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminProjectApproval.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,114 @@
+<!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>Approving, deferring, or disapproving projects</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="domadminprojectapproval">
+   <h2>Approving, deferring, or disapproving projects</h2>
+
+   <div id="toc">
+    <ul>
+     <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+    </ul>
+
+    <ul>
+     <li>
+      <a href="/nonav/docs/DomAdminOverview.html">Domain administration overview</a> 
+
+      <ul>
+       <li><a href="/nonav/docs/DomAdminAddUsers.html">Adding and editing user accounts</a></li>
+
+       <li><a href="/nonav/docs/DomAdminRoles.html">Administering roles and permissions</a></li>
+
+       <li><a href="/nonav/docs/DomAdminUserGroups.html">Creating and editing user groups</a></li>
+
+       <li><a href="/nonav/docs/DomAdminProjectGroups.html">Creating and editing project groups</a></li>
+
+       <li>
+        Approving, disapproving, or deferring projects 
+
+        <ul>
+         <li><a href="#aboutapproval">About the project approval process</a></li>
+
+         <li><a href="#deferdisapprove">Deferring and disapproving projects</a></li>
+
+         <li><a href="#other">Locking, unlocking, and deleting projects</a></li>
+        </ul>
+       </li>
+
+       <li><a href="/nonav/docs/DomAdminAuditLogs.html">Using domain administration tools</a></li>
+      </ul>
+     </li>
+    </ul>
+   </div>
+
+   <h3><a id="aboutapproval" name="aboutapproval">About the project approval process</a></h3>
+
+   <p>When a project is proposed on this site, it appears in the <i>Proposed Projects</i> link in the "Pending Actions" section of the Domain Administrator's <b>Start Page</b>. The next time you log in, this count indicates how many projects are awaiting your action. Taking no action has the same result as deferring a project; they remain effectively in limbo as pending actions.</p>
+
+   <p>Click the <i>Proposed Projects</i> link in the "Pending Actions" section to display the <b>Project Approval</b> page. An alphabetical listing of all pending projects appears with the proposer's name and a project summary included. Project titles link to each project's home page. The proposer's name links to the <b>Edit User</b> screen containing this user's account information.</p>
+
+   <p>As the Domain Administrator, you disperse with pending projects in one of three ways: approve, defer, or disapprove them by placing checkmarks in the appropriate boxes. All of these actions are tracked in an administrative audit log, along with other administrative actions. See <a href="/nonav/docs/DomAdminAuditLogs.html">Using administrative audit logs</a> for further information.</p>
+
+   <p>The criteria for approving or disapproving proposed projects falls within your judgment as the Domain Administrator. Factors to consider might include:</p>
+
+   <ul>
+    <li>Does the project fall within your site's overall mission and general goals?</li>
+
+    <li>Is the project well scoped out?</li>
+
+    <li>Are project objectives clearly stated?</li>
+   </ul>
+
+   <p>When you approve a project, an email message is automatically generated notifying the Project Owner. The project appears in the site's hosted project listings, including the <b>Projects</b> page and the appropriate category home page(s). The Project Owner can now approve members and grant roles to them.</p>
+
+   <h3><a id="deferdisapprove" name="deferdisapprove">Deferring or disapproving projects</a></h3>
+
+   <p>While your approval of a project is pending, or when you defer approval, the project simply remains in your list of pending projects awaiting approval. It does not appear within any project listings in public pages or to any other users. The proposer, however, continues to see a link to this project in her/his <b>Start Page</b> under the "My Projects" section, and can conduct most project related activities including:</p>
+
+   <ul>
+    <li>accessing and updating their project's home page</li>
+
+    <li>inviting participants</li>
+
+    <li>uploading and downloading project files and documents</li>
+
+    <li>adding and editing news items</li>
+
+    <li>checking source code into the project's CVS repository</li>
+
+    <li>assigning and tracking project issues.</li>
+   </ul>
+
+   <p>None of this project information on pending projects is visible to other site users, however. And until you approve a pending project, the Project Owner <i>cannot</i> approve project members or grant roles to them.</p>
+
+   <p>When you disapprove a project, an email message is automatically generated to notify the proposer. This message is brief; the proposer is encouraged to contact you for further discussion about the specific reasons for disapproval.</p>
+
+   <h3><a id="other" name="other">Locking, unlocking, and deleting projects</a></h3>
+
+   <p>The Project Lock feature enables you to stop all activity on a project if circumstances arise to necessitate this. Whether this is due to site policy matters, technical issues, or other reasons, project locking lets you essentially turn off all site-related project activity. The locked project's home page and other pages can still be accessed and all existing project data is intact, however the Project Owner and members have read-only access to the source code repository, email archives, issue database, project files, and documents. No one -- including the project owner -- can commit source code, enter issues, upload or download files and documents, change web content, or subscribe to or modify mailing lists. If the locked project is a public project, other site users can still view the project's home page but the project is flagged as "locked."</p>
+
+   <p>To lock a currently active project, navigate to the project's home page and click on the <b>Edit this project</b> link. Use the <i>Project Lock</i> link at the bottom to display a screen where you can set the lock. This action automatically generates an email notice to the project owner, telling him/her to contact a site administrator immediately.</p>
+
+   <p>To unlock a project, your view of the locked project's home page displays the red "Locked" flag and an <i>Unlock</i> link next to it you can use to enable the project again. Alternatively, you can use the <b>Project Edit</b> page where there an <b>Unlock Project</b> link appears at the bottom of the page. When you unlock a project to reactivate it, another email notice is automatically sent to the project owner.</p>
+
+   <p>Projects may also be deleted from this site when they either don't pan out or reach the end of their development life cycle. The <b>Project Edit</b> page includes a <i>Project Delete</i> link at the bottom of the page. If you click this link, you are asked to confirm the action. <b><i>Use the project delete feature with caution!</i> Deleting the project not only removes it from site project listings, but also completely erases the project's cvs repository files, all project files and documents, issues database, and mailing list archives.</b></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/DomAdminProjectGroups.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminProjectGroups.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminProjectGroups.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,234 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Creating and editing project groups and categories</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">Creating and editing project groups and categories</span>
+<p>
+
+<span class="PlainText"><b>Help for domain administration: Index</b>
+<p>
+<ul>
+  <dl>
+  <dt><a href="DomAdminOverview.html">Domain administration overview</a>
+    <dd><a href="DomAdminAddUsers.html">Adding and editing user accounts</a>
+    <dd><a href="DomAdminRoles.html">Administering roles and permissions</a>
+    <dd><a href="DomAdminUserGroups.html">Creating and editing user groups</a>
+    <dd><b>You are here: Creating and editing project groups</b>
+      <ul>
+      <li><a href="#whatis"><b>What are project groups and categories?</b></a>
+      <li><a href="#defaultgroups"><b>About default project groups</b></a>
+      <li><a href="#createprojgroup"><b>Creating project groups</b></a>
+      <li><a href="#addtoprojgroup"><b>Adding user groups to project groups</b></a>
+      <li><a href="#editprojgroup"><b>Editing project groups</b></a>
+      <li><a href="#manageroles"><b>Managing user group roles for project groups</b></a>
+      </ul>
+    <dd><a href="DomAdminProjectApproval.html">Approving, disapproving, or deferring projects</a>
+    <dd><a href="DomAdminAuditLogs.html">Using domain administration tools</a>
+    <dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+  </dl>
+</ul>
+<p>
+
+<hr noshade size=1>
+<a name="whatis"></a><span class="InputHeader">What are project groups and categories?</span>
+<p>
+A project group is set of projects grouped together for administrative purposes. As the Domain Administrator, you define the basis upon which project groups are created. You can elect to group projects by technologies, by departments, by clients--or by any other criteria your development environment may require. Regardless of how you set up your project groups, any given project on you site may belong to more than one project group.
+<p>
+Project groups enable you to perform administrative actions to affect multiple projects and users simultaneously. User membership in project groups can happen two different ways:
+<ol>
+<li>When the projects a user belongs to are added to the project group.
+<p>
+<li>When users are associated with <i>user groups</i> you have created and then added to the project group. You can read more about this in <a href="DomAdminUserGroups.html">Creating and editing user groups</a>. 
+</ol>
+<p>
+The "project categories" listed on your <b>Start Page</b> are special kinds of project groups. Categories enable projects on this site to be cataloged <i>publicly</i> by development type as a way of organizing project information for browsing. Because project groups are an administrative feature, they are not visible to site users, but project categories appear on every user's <b>Start Page</b> and in the <b>Hosted Projects</b> page. The <b>Project Group Add</b> screen lets you choose whether to make a new project group be an administrative group or a public category. See <a href="#editprojgroup">Editing project groups</a> for more information about this.
+<p>
+Both project groups and categories can be managed as projects themselves as an administrative feature. Like individual hosted projects, every project group/category has its own home page, CVS repository, issue tracker, and web pages for news, file uploads/downloads, and project documentation.
+<p>
+
+
+<hr noshade size=1>
+<a name="defaultgroups"></a><span class="InputHeader">About default project groups</span>
+<p>
+There are already two existing project groups for this site:
+<p>
+<ul>
+<li>All projects in this domain
+<li>All public projects in this domain
+</ul>
+<p>
+All projects created on this site automatically belong to one or both of these groups. If you want to special modifications changes across multiple projects, you must create your own additional project groups. These groups become subsets of one or both of these default project groups, which cannot be edited.
+<p>
+Continue through this document to follow the examples of how to create project groups and make changes across multiple projects within that group. In the <a href="#createprojgroup">Creating project groups</a> section, the hypothetical example shows creating a project group for all the projects in your domain that are using contract content contributors. In the <a href="#manageroles">Managing user group roles for project groups</a> section, the example assigns the "content developer" role to a certain user group that belongs to the contract project group.
+<p>
+
+<p>
+
+<hr noshade size=1>
+<a name="createprojgroup"></a><span class="InputHeader">Creating project groups</span>
+<p>
+To create a project group:
+<p>
+<ul>
+<li>In the "Admin Options" section of your <b>Start Page</b>, click the <i>Administer Project Groups</i> link to display the <b>All Project Groups</b> page.
+<p>
+<li>Click the <i>Add New Group</i> link in the top right corner to display the <b>Add a Project Group</b> screen.
+</ul>
+<p>
+Input fields:
+<p>
+<dl>
+<dt><b><i>Group Name</i></b>
+<dd>Choose a one-word name to identify this new group. Do not use spaces in the name. Example: <i>contractprojects</i>
+<p>
+<dt><b><i>Summary</i></b>
+<dd>Use the summary description field to include a few qualifying words about the nature of the group. Information in this field is included in the <b>Project Group Add</b> screen where all project groups are listed. Example: <i>projects using contractors</i>
+<p>
+<dt><b><i>Description</i></b>
+<dd>This text box enables you to include further detail about the project group. Example: <i>Several projects require outsourcing to handle content development. Any projects using independent contractors must be tracked separately for cost accounting purposes. </i>
+<p>
+<dt><b><i>Category</i></b>
+<dd>Check this box to make the newly created project group a category. A category is a unique kind of project group for organizing how project listings appear on the <b>Start Page</b> and <b>Hosted Projects</b> page. Each category has a category home page listing all projects associated with it. The default categories on this site group projects by types of applications being developed, i.e. communication, education, games, etc., but you may wish to categorize projects differently. Both categories and project groups may be edited; see the following <a href="#editprojgroup">Editing project groups</a> section for more information.
+<p>
+<dt><b><i>Initial Projects</i></b>
+<dd>List the projects you wish to include in this group. Identify projects by their one-word names, one entry per line. These projects become <i>elements</i> of the project group you are creating.
+</dl>
+<p>
+When you are finishing entering project group information, click the <i>Create Group</i> button to submit the new group. The <b>All Project Groups</b> page displays with the new group included. 
+<p>
+
+<hr noshade size=1>
+<a name="editprojgroup"></a><span class="InputHeader">Editing project groups</span>
+<p>
+You can modify project group information through the <b>Project Group Edit</b> screen. This is also the page you must use to add users or user groups to a project group, and to assign or modify the roles of those users.
+<p>
+To access the <b>Project Group Edit</b> screen:
+<p>
+<ul>
+<li>In the "Admin Options" section of your <b>Start Page</b>, click the <i>Administer Project Groups</i> link to display the <b>All Project Groups</b> page.
+<p>
+<li>Click on the project group name link to display the <b>Project Group Edit</b> screen.
+</ul>
+<p>
+This screen contains three sections containing separate editing actions that affect the project group. The top and middle sections are explained here. The bottom section of the <b>Project Group Edit</b> screen is covered in <a href="#manageroles">Managing user group roles in project groups</a>.
+<p>
+In the first section of the <b>Project Group Edit</b> page, you can modify the summary and description fields, then use the <b><i>Submit Changes</i></b> button to save your changes.
+<p>
+The middle "Group Elements" section of the page displays those projects that are included in this project group. <i>Elements</i> refer to the individual projects that make up the project group. Here you can:
+<p>
+<ul>
+<li>Click the project name link to view the <b>Project Home</b> page.
+<p>
+<li>Remove a project by placing a checkmark in the "Remove From Group" column and clicking the <b><i>Remove Elements</i></b> button. This action disassociates the project from the project group, but does not remove or delete the project itself from the site.
+<p>
+<li>Use the <i>Add New Project to Group</i> link to display the <b>Add Projects</b> screen listing all hosted projects. You can select one or more projects and add them to the project group in one action.
+</ul>
+<p>
+
+<hr noshade size=1>
+<a name="addtoprojgroup"></a><span class="InputHeader">Adding user groups to project groups</span>
+
+<p>To add one or more user groups to a project group:
+<p>
+<ul>
+<li>In the "Admin Options" section of your <b>Start Page</b>, click the <i>Administer Project Groups</i> link to display the <b>All Project Groups</b> page.
+<p>
+<li>Click on the project group name link to display the <b>Project Group Edit</b> screen.
+<p>
+<li>In the "Other Options" section at the bottom of the screen, click on the <i>Grant User Roles</i> link.
+<p>
+<li>This displays the <b>Add Members</b> screen listing existing user groups at the top followed by individual users.
+<p>
+<li>Make your user group selections by checking the appropriate box or boxes. Highlighting the role or roles you wish to grant to the user group <i>to be effective only within the project group</i>. 
+<p>
+<li>Finish adding the user group(s) by clicking the <b><i>Grant Roles</i></b> button. The user groups you have designated become <i>members</i> of the project group.
+</ul>
+<p>
+
+
+
+<hr noshade size=1>
+<a name="manageroles"></a><span class="InputHeader">Managing user groups and roles for project groups</span>
+<p>
+To view and modify user group roles for project groups:
+<p>
+<ul>
+<li>In your <b>Start Page</b>, click the <i>List All Project Groups</i> link to display the <b>All Project Groups</b> page.
+<p>
+<li>Click on the project group name link you wish to edit, which displays the <b>Project Group Edit</b> screen.
+<p>
+<li>The bottom "Other Options" section of this page features links for managing user groups' roles pertaining to the current project group.
+<p>
+<dl>
+<dt><b><i>View User Roles in this Group</i></b>
+<dd>Click this link to display the <b>Project Members</b> screen listing all users and user groups associated with this project group. Remember that project groups function as seperate projects themselves, therefore adding user groups equates to make those user groups <i>members</i> of the project named "project group."
+<p>
+If no user groups are affiliated with the project group yet (or you wish to add additional users or user groups), you can use the <i>Add New Member</i> link in the top right corner. The <b>Project Member Add</b> page is displayed with both user groups and users listed.
+<p>
+To add users to a project group:
+<ul>
+<li>Place checkmarks next to the user groups and/or users you wish to add to the project group.
+<p>
+<li>Select the role(s) you to assign to the users you have flagged.
+<p>
+<li>Click the <b><i>Grant Roles</i></b> button to complete the member adds. Notice the checkbox labeled "Done granting roles" is checked by default. This means that once you add the designated users, you will be returned to the <b>Project Group Edit</b> screen. If you wish to add additional users or user groups with different roles, removing this checkmark will redisplay the <b>Add Members</b> page and confirm your most recent action.
+</ul>
+<p>
+If the project group contains any users and/or user groups, the <b>Project Member List</b> page displays these along with their real names and any roles they hold in the project group. The <i>View Issues</i> link applies only when you have assigned issues to these users specifically related to the project group. This is not a link to any project-specific issues.
+<p>
+
+<dt><b><i>Grant User Roles in this Group</i></b>
+<dd>Click this link also displays the <b>Add Members</b> screen. User groups are listed first, followed by individual users. Place checkmarks in the boxes next to those users and/or groups whose roles you wish to modify.
+<p>
+Example: Continuing with the <i>contractprojects</i> scenario, suppose you have created a user group called <i>contractwriters</i> for users who are contractors contributing content to projects hosted on this site.
+  <p>
+  <ol>
+  <li>You would select the <i>contractwriters</i> user group using the <i>Add New Member</i> link.
+  <p>
+  <li>After reloading the <b>Project Members</b> screen for the <i>contractprojects</i> project group, you would place a check in the box next to <i>contractwriters</i>.
+  <p>
+  <li>Then you would designate the role you wish to grant these users specifically for all projects in the <i>contractprojects</i> project group. In this example, you would highlight "content developer" in the roles field.
+  <p>
+  <li>Pressing the <b><i>Grant Roles</i></b> button completes the action of adding the selected user group. You are returned to the <b>Project Group Edit</b> screen if the "Done granting roles" box is left checked. If you wish to make further role modifications for other users or user groups, remove this checkmark before clicking the <b>Grant Roles</b> button.
+  </ol>
+<p>
+
+<dt><b><i>Delete Group</i></b>
+<dd>
+Click this link to remove the entire project group completely. This eradicates only the project group; it does not delete any user groups associated with the deleted project group.
+</dl>
+</ul>
+<p>
+
+<hr noshade size=1>
+<a href="DomAdminOverview.html">Back to Help for domain administration</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/DomAdminProjectGroups.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminProjectGroups.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminProjectGroups.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,244 @@
+<!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>Creating and editing project groups and categories</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="domadminprojectgroups">
+   <h2>Creating and editing project groups and categories</h2>
+
+   <div id="toc">
+    <ul>
+     <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+    </ul>
+
+    <ul>
+     <li>
+      <a href="/nonav/docs/DomAdminOverview.html">Domain administration overview</a> 
+
+      <ul>
+       <li><a href="/nonav/docs/DomAdminAddUsers.html">Adding and editing user accounts</a></li>
+
+       <li><a href="/nonav/docs/DomAdminRoles.html">Administering roles and permissions</a></li>
+
+       <li><a href="/nonav/docs/DomAdminUserGroups.html">Creating and editing user groups</a></li>
+
+       <li>
+        Creating and editing project groups 
+
+        <ul>
+         <li><a href="#whatis"><b>What are project groups and categories?</b></a></li>
+
+         <li><a href="#defaultgroups"><b>About default project groups</b></a></li>
+
+         <li><a href="#createprojgroup"><b>Creating project groups</b></a></li>
+
+         <li><a href="#nesting"><b>Nesting project groups</b></a></li>
+
+         <li><a href="#addtoprojgroup"><b>Adding user groups to project groups</b></a></li>
+
+         <li><a href="#editprojgroup"><b>Editing project groups</b></a></li>
+
+         <li><a href="#manageroles"><b>Managing user group roles for project groups</b></a></li>
+        </ul>
+       </li>
+
+       <li><a href="/nonav/docs/DomAdminProjectApproval.html">Approving, disapproving, or deferring projects</a></li>
+
+       <li><a href="/nonav/docs/DomAdminAuditLogs.html">Using domain administration tools</a></li>
+      </ul>
+     </li>
+    </ul>
+   </div>
+
+   <h3><a id="whatis" name="whatis">What are project groups and categories?</a></h3>
+
+   <p>A project group is set of projects grouped together for administrative purposes. As the Domain Administrator, you define the basis upon which project groups are created. You can elect to group projects by technologies, by departments, by clients--or by any other criteria your development environment may require. Regardless of how you set up your project groups, any given project on you site may belong to more than one project group.</p>
+
+   <p>Project groups enable you to perform administrative actions to affect multiple projects and users simultaneously. User membership in project groups can happen two different ways:</p>
+
+   <ol>
+    <li>When the projects a user belongs to are added to the project group.</li>
+
+    <li>When users are associated with <i>user groups</i> you have created and then added to the project group. You can read more about this in <a href="/nonav/docs/DomAdminUserGroups.html">Creating and editing user groups</a>.</li>
+   </ol>
+
+   <p>The "project categories" listed on your <b>My pages</b> are special kinds of project groups. Categories enable projects on this site to be cataloged <i>publicly</i> by development type as a way of organizing project information for browsing. Because project groups are an administrative feature, they are not visible to site users, but project categories appear on every user's <b>My pages</b> and in the <b>Projects</b> page. The <b>Project Group Add</b> screen lets you choose whether to make a new project group be an administrative group or a public category. See <a href="#editprojgroup">Editing project groups</a> for more information about this.</p>
+
+   <p>Both project groups and categories can be managed as projects themselves as an administrative feature. Like individual hosted projects, every project group/category has its own home page, CVS repository, issue tracker, and web pages for news, file uploads/downloads, and project documentation.</p>
+
+   <h3><a id="defaultgroups" name="defaultgroups">About default project groups</a></h3>
+
+   <p>There are already two existing project groups for this site:</p>
+
+   <ul>
+    <li>All projects in this domain</li>
+
+    <li>All public projects in this domain</li>
+   </ul>
+
+   <p>All projects created on this site automatically belong to one or both of these groups. If you want to special modifications changes across multiple projects, you must create your own additional project groups. These groups become subsets of one or both of these default project groups, which cannot be edited.</p>
+
+   <p>Continue through this document to follow the examples of how to create project groups and make changes across multiple projects within that group. In the <a href="#createprojgroup">Creating project groups</a> section, the hypothetical example shows creating a project group for all the projects in your domain that are using contract content contributors. In the <a href="#manageroles">Managing user group roles for project groups</a> section, the example assigns the "content developer" role to a certain user group that belongs to the contract project group.</p>
+
+   <h3><a id="createprojgroup" name="createprojgroup">Creating project groups</a></h3>
+
+   <p>To create a project group:</p>
+
+   <ul>
+    <li>In the "Admin Options" section of your <b>Start Page</b>, click the <i>Administer Project Groups</i> link to display the <b>All Project Groups</b> page.</li>
+
+    <li>Click the <i>Add New Group</i> link in the top right corner to display the <b>Add a Project Group</b> screen.</li>
+   </ul>
+
+   <p>Input fields:</p>
+
+   <dl>
+    <dt>Group Name</dt>
+
+    <dd>Choose a one-word name to identify this new group. Do not use spaces in the name. Example: <i>contractprojects</i></dd>
+
+    <dt>Summary</dt>
+
+    <dd>Use the summary description field to include a few qualifying words about the nature of the group. Information in this field is included in the <b>Project Group Add</b> screen where all project groups are listed. Example: <i>projects using contractors</i></dd>
+
+    <dt>Description</dt>
+
+    <dd>This text box enables you to include further detail about the project group. Example: <i>Several projects require outsourcing to handle content development. Any projects using independent contractors must be tracked separately for cost accounting purposes.</i></dd>
+
+    <dt>Category</dt>
+
+    <dd>Check this box to make the newly created project group a category. A category is a unique kind of project group for organizing how project listings appear on the <b>My pages</b> and <b>Projects</b> page. Each category has a category home page listing all projects associated with it. The default categories on this site group projects by types of applications being developed, i.e. communication, education, games, etc., but you may wish to categorize projects differently. Both categories and project groups may be edited; see the following <a href="#editprojgroup">Editing project groups</a> section for more information.</dd>
+
+    <dt>Initial Projects</dt>
+
+    <dd>List the projects you wish to include in this group. Identify projects by their one-word names, one entry per line. These projects become <i>elements</i> of the project group you are creating.</dd>
+   </dl>
+
+   <p>When you are finishing entering project group information, click the <i>Create Group</i> button to submit the new group. The <b>All Project Groups</b> page displays with the new group included.</p>
+
+   <h3><a id="nesting" name="nesting"></a>Nesting Project Groups</h3>
+
+   <p>Project Groups can be nested to create subgroups. Nested groups have a parent/child relationship. When you create a Project Group, you can specify another Project Group as its parent. You can change the parent Project Groups by editing the child Project Group. The parent is shown on Project home page and other project-related servlets. Any children of the project are visible on that project's home page.</p>
+
+   <p><em>Note: This same process can be used with project categories and individual projects.</em></p>
+
+   <h3><a id="editprojgroup" name="editprojgroup">Editing project groups</a></h3>
+
+   <p>You can modify project group information through the <b>Project Group Edit</b> screen. This is also the page you must use to add users or user groups to a project group, and to assign or modify the roles of those users.</p>
+
+   <p>To access the <b>Project Group Edit</b> screen:</p>
+
+   <ul>
+    <li>In the "Admin Options" section of your <b>Start Page</b>, click the <i>Administer Project Groups</i> link to display the <b>All Project Groups</b> page.</li>
+
+    <li>Click on the project group name link to display the <b>Project Group Edit</b> screen.</li>
+   </ul>
+
+   <p>This screen contains three sections containing separate editing actions that affect the project group. The top and middle sections are explained here. The bottom section of the <b>Project Group Edit</b> screen is covered in <a href="#manageroles">Managing user group roles in project groups</a>.</p>
+
+   <p>In the first section of the <b>Project Group Edit</b> page, you can modify the summary and description fields, then use the <b><i>Submit Changes</i></b> button to save your changes.</p>
+
+   <p>The middle "Group Elements" section of the page displays those projects that are included in this project group. <i>Elements</i> refer to the individual projects that make up the project group. Here you can:</p>
+
+   <ul>
+    <li>Click the project name link to view the <b>Project Home</b> page.</li>
+
+    <li>Remove a project by placing a checkmark in the "Remove From Group" column and clicking the <b><i>Remove Elements</i></b> button. This action disassociates the project from the project group, but does not remove or delete the project itself from the site.</li>
+
+    <li>Use the <i>Add New Project to Group</i> link to display the <b>Add Projects</b> screen listing all hosted projects. You can select one or more projects and add them to the project group in one action.</li>
+   </ul>
+
+   <h3><a id="addtoprojgroup" name="addtoprojgroup">Adding user groups to project groups</a></h3>
+
+   <p>To add one or more user groups to a project group:</p>
+
+   <ul>
+    <li>In the "Admin Options" section of your <b>Start Page</b>, click the <i>Administer Project Groups</i> link to display the <b>All Project Groups</b> page.</li>
+
+    <li>Click on the project group name link to display the <b>Project Group Edit</b> screen.</li>
+
+    <li>In the "Other Options" section at the bottom of the screen, click on the <i>Grant User Roles</i> link.</li>
+
+    <li>This displays the <b>Add Members</b> screen listing existing user groups at the top followed by individual users.</li>
+
+    <li>Make your user group selections by checking the appropriate box or boxes. Highlighting the role or roles you wish to grant to the user group <i>to be effective only within the project group</i>.</li>
+
+    <li>Finish adding the user group(s) by clicking the <b><i>Grant Roles</i></b> button. The user groups you have designated become <i>members</i> of the project group.</li>
+   </ul>
+
+   <h3><a id="manageroles" name="manageroles">Managing user groups and roles for project groups</a></h3>
+
+   <p>To view and modify user group roles for project groups:</p>
+
+   <ul>
+    <li>In your <b>Start Page</b>, click the <i>List All Project Groups</i> link to display the <b>All Project Groups</b> page.</li>
+
+    <li>Click on the project group name link you wish to edit, which displays the <b>Project Group Edit</b> screen.</li>
+
+    <li>
+     The bottom "Other Options" section of this page features links for managing user groups' roles pertaining to the current project group. 
+
+     <dl>
+      <dt>View User Roles in this Group</dt>
+
+      <dd>
+       Click this link to display the <b>Membership</b> screen listing all users and user groups associated with this project group. Remember that project groups function as separate projects themselves, therefore adding user groups equates to make those user groups <i>members</i> of the project named "project group." 
+
+       <p>If no user groups are affiliated with the project group yet (or you wish to add additional users or user groups), you can use the <i>Add New Member</i> link in the top right corner. The <b>Project Member Add</b> page is displayed with both user groups and users listed.</p>
+
+       <p>To add users to a project group:</p>
+
+       <ul>
+        <li>Place checkmarks next to the user groups and/or users you wish to add to the project group.</li>
+
+        <li>Select the role(s) you to assign to the users you have flagged.</li>
+
+        <li>Click the <b><i>Grant Roles</i></b> button to complete the member adds. Notice the checkbox labeled "Done granting roles" is checked by default. This means that once you add the designated users, you will be returned to the <b>Project Group Edit</b> screen. If you wish to add additional users or user groups with different roles, removing this checkmark will redisplay the <b>Add Members</b> page and confirm your most recent action.</li>
+       </ul>
+
+       <p>If the project group contains any users and/or user groups, the <b>Project Member List</b> page displays these along with their real names and any roles they hold in the project group. The <i>View Issues</i> link applies only when you have assigned issues to these users specifically related to the project group. This is not a link to any project-specific issues.</p>
+      </dd>
+
+      <dt>Grant User Roles in this Group</dt>
+
+      <dd>
+       Click this link also displays the <b>Add Members</b> screen. User groups are listed first, followed by individual users. Place checkmarks in the boxes next to those users and/or groups whose roles you wish to modify. 
+
+       <p>Example: Continuing with the <i>contractprojects</i> scenario, suppose you have created a user group called <i>contractwriters</i> for users who are contractors contributing content to projects hosted on this site.</p>
+
+       <ol>
+        <li>You would select the <i>contractwriters</i> user group using the <i>Add New Member</i> link.</li>
+
+        <li>After reloading the <b>Project Member</b> screen for the <i>contractprojects</i> project group, you would place a check in the box next to <i>contractwriters</i>.</li>
+
+        <li>Then you would designate the role you wish to grant these users specifically for all projects in the <i>contractprojects</i> project group. In this example, you would highlight "content developer" in the roles field.</li>
+
+        <li>Pressing the <b><i>Grant Roles</i></b> button completes the action of adding the selected user group. You are returned to the <b>Project Group Edit</b> screen if the "Done granting roles" box is left checked. If you wish to make further role modifications for other users or user groups, remove this checkmark before clicking the <b>Grant Roles</b> button.</li>
+       </ol>
+      </dd>
+
+      <dt>Delete Group</dt>
+
+      <dd>Click this link to remove the entire project group completely. This eradicates only the project group; it does not delete any user groups associated with the deleted project group.</dd>
+     </dl>
+    </li>
+   </ul>
+
+   <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