You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by bu...@apache.org on 2017/04/08 23:00:14 UTC
svn commit: r1010077 [10/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...
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminRoles.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminRoles.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminRoles.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,170 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Administering roles and permissions</title>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<span class="Header">Administering roles and permissions</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><b>You are here: Administering roles and permissions
+ <ul>
+ <li><a href="#aboutroles">Understanding roles and permissions
+ </a><li><a href="#aboutroles"></a><a href="#userroles">Editing user role assignments</a>
+ <li><a href="#editroles">Editing roles</a>
+ <li><a href="#addroles">Adding roles</a>
+ <li><a href="#viewaddresources">About resources and actions</a>
+ </ul></b>
+ <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="aboutroles"></a><span class="InputHeader">Understanding roles and permissions</span>
+<p>
+Every user on this site is able to access features and conduct activities based upon roles the user has been granted. There are two kinds of roles:
+<ul>
+<li><b><i>Domain roles</i></b> give users access to generalized information and actions throughout the site. Domain Administrators assign and configure domain roles to all users on this site. Every new user automatically gets the "registered user" domain role by virtue of being registered on your domain. It is also possible to create other domain roles; more about this is covered in the <a href="#addroles">Adding roles</a> section of this document.
+<p>
+<li><b><i>Project roles</i></b> are limited to information and actions within a project. Domain Administrators also can configure project roles, but by design Project Owners usually assign project roles to users when they become project members.
+</ul>
+<p>
+Roles are either assigned to users through membership in a project, or through association with project groups or user groups. All roles have a default set of permissions associated with them. These permissions govern the users' ability to conduct certain actions on this site.
+<p>
+As Domain Administrator, you can:
+<ul>
+<li>Use and assigning existing roles "as is."
+<p>
+<li>Alter existing roles by changing the permissions, actions, and/or resources are associated with them.
+<p>
+<li>Create entirely new roles and designate permissions for them. (You cannot, however, create new permissions.) See <a href="#addroles">Adding roles</a>.
+</ul>
+<p>
+You can also tailor roles and permissions for sets of users by creating user groups, and for sets of projects by making project groups. For more information about this, see <a href="DomAdminCategories.html">Creating and editing project groups</a> and <a href="DomainAdminUserGroups.html">Creating and editing user groups</a>.
+<p>
+
+<hr noshade size=1>
+<a name="userroles"></a><span class="InputHeader">Editing user role assignments</span>
+<p>
+The fields and options in the bottom section of the <b>Edit User</b> page enable you to view and change the individual user's role assignments.
+<p>
+<dt><b><i>Group Memberships</i></b>
+ <dd>The user's affiliation with any user group or project categories in this domain are listed here. User groups and project groups are created and configured by you as the Domain Administrator. See <a href="DomAdminCategories.html">Creating and editing project groups</a> and <a href="DomainAdminUserGroups.html">Creating and editing user groups</a> for more information.
+<p>
+<dt><b><i>Domain-wide Roles</i></b>
+ <dd>Domain roles assigned or conferred to the user are listed here. These are generalized roles that permit the user to view site pages and conduct site actions not associated with specific projects. See previous <a href="#aboutroles">Understanding roles and permissions</a> section.
+<p>
+<dt>
+<b><i>Roles in domain's public projects</i></b>
+ <dd>Every public project hosted on this domain is automatically part of the default project group labeled (not surprisingly) "All public projects." Any roles the user holds in such projects are flagged here. See <a href="DomAdminProjectGroups.html">Creating and editing project groups</a> for more information.
+ <p>
+<dt><b><i>Submit Changes</i></b>
+ <dd>This button submits any modifications to the individual user account made in the fields above. Modifications to the user's roles are separate actions.
+ <p>
+<dt><b><i>Project Roles</i></b>
+ <dd>Roles the user holds that are associated with specific projects are listed here, grouped by project name. Project names link to project home pages. This list includes both open source and private, proprietary projects. See <a href="#aboutroles">Understanding roles and permission</a> section for a more comprehensive discussion of roles.
+<p>
+<dt><b><i>Detailed Role Info</i></b>
+ <dd>These links lead to secondary screens with more detailed role information associated with the current user:
+ <p>
+ <ul>
+ <li><i>Direct and derived roles</i> displays two different sets roles held by the user. <i>Direct roles</i> are those roles expressly assigned to the user. For example, the user requested and was approved for a certain role in a project. <i>Derived roles</i> are roles <i>conferred</i> to this user because she/he is a member of a project specifically associated with a project group's set of roles, or belongs to a user group assigned a unique set of roles.
+ <p>
+ <li><i>Details of permissions</i> displays a screen rather unceremoniously entitled <b>Permission Dump</b> because it tabulates literally every single permission the user holds in your domain.
+ </ul>
+ <p>
+ <dd>Note that when individual users are part of particular project groups or user groups, you can assign attributes and modify multiple user accounts associated with those groups by using the <b>Project Group Edit</b> or <b>User Group Edit</b> screens. See <a href="DomAdminCategories.html">Creating and editing project groups</a> and <a href="DomainAdminUserGroups.html">Creating and editing user groups</a> for more information.
+<p>
+
+<dt><b>Other operations: <i>Delete User</i></b>
+ <dd>This link removes the current user account. A confirmation message prompts you for verification before this action is completed.
+
+<p>
+
+
+<hr noshade size=1>
+<a name="editroles"></a><span class="InputHeader">Editing roles</span>
+<p>
+This site features a set of default roles that you may view using the <i>Administer Roles</i> link in the "Admin Options" of your <b>Start Page</b>. This displays the <b>Role List</b> page with all site roles listed as either domain or project-level. A brief description of each role is included.
+<p>
+To view a list of individual permissions associated with this role, click on the role name link in the <b>Role List</b> page. Each permission listed on the <b>Editing Role</b> page is characterized by both the site resource and site action that it enables, i.e. "Project - Suggest" or "Version Control - Update." The far right "Resource(s)" column defines in which site resources each permission is effective. The default is for each permission to apply to all available resources.
+<p>
+As domain administrator, you have the option to modify this site's pre-packaged roles by changing the permissions associated with them as needed. Placing a check mark in the boxes next to a permission <i>removes this permission</i> from the role.
+<p>
+If you wish to <i>add</i> permissions to a role, click the <i>Add New Permission</i> link at the top of the <b>Editing Role</b> page. This screen gives you a list of all available permissions. To add permissions, place check marks in the appropriate boxes.
+<p>
+In addition to editing roles by adding and removing permissions, you can modify or limit which resources the permissions associated with that role will apply to. The resource section at the bottom of the <b>Add Permission to Role</b> page lets you determine in which site resources to allocate the role's new permissions.
+<p>
+<ul>
+<li>Selecting "All available resources .*" applies the selected permissions for this role universally to all site resources available to this role, including both web content and source code.
+<p>
+<li>Choosing "All web pages /www/.*" limits the selected permission for this role specifically to web pages. This means the scope of these permissions 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 "All web pages /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.
+</ul>
+After you have selected the permissions to add and determined the site resources to apply these to, click the <b><i>Add Permissions</i></b> button at the bottom of the page.
+<p>
+See the section on <a href="#viewaddresources">Viewing and adding resources</a> for more information about site resources.
+<p>
+
+<hr noshade size=1>
+<a name="addroles"></a><span class="InputHeader">Adding roles</span>
+<p>
+If your site has special requirements that none of the default roles meet, you can also create custom roles and assign the appropriate permissions to them. To do this, in the <b>Role List</b> page click the "Add New Role" link in either the domain or project section, depending upon the type of role you want to create. Depending upon which one you click, this displays either the <b>Add Domain Role</b> or <b>Add Project Role</b> page. You can switch between these pages using the links at the top of this page.
+<p>
+You must determine what you want the scope of your newly created role to be. If you want to create a role that enables certain user actions universally across the site, add the new role as a domain role. If you want to create a role with permissions that are <i>not</i> universally enabled across this site, you should add the new role as a project role. When project roles are assigned, their associated permissions are granted to the user only within that project.
+<p>
+The <b>Add Domain Role</b> and <b>Add Project Role</b> pages list every permission/action available at that level. Use this feature with extreme caution! Assigning permissions to roles may have security implications.
+<p>
+
+
+<hr noshade size=1>
+<a name="viewaddresources"></a><span class="InputHeader">About resources and actions</span>
+<p>
+<b><i>Resources</i></b> are all of the different elements used in this site including tools, content, projects, and web pages. User roles and permissions on this site are defined by the specific resources they apply to. For example, each of these permissions -- "Mailing List - View," "Project - Suggest," "Version Control - Commit" -- is comprised of a certain resource on this site and the <b><i>action</i></b> being permitted within that resource. In these three examples, the resources are, respectively: mailing list, project, and version control.
+<p>
+Resources are described on this site using regular expressions. Thus, the pattern or regular expression meaning all available resources is ".*".
+<p>
+You can view a complete list of all available resources on this site by clicking the <i>Resource List</i> link at the top of the <b>Editing Role</b> page. The default items in the Resource List page are "All available resources (.*)" and "All web pages (/www/.*)". Clicking on the resource link displays the <b>Edit Resource</b> screen where there is short, identifying description and the pattern that represents the resource as a regular expression.
+<p>
+As the domain administrator, you can also create new resources and define them using the <i>Add New Resource</i> link at the top of the <b>Editing Role</b> page. This is a powerful and flexible administrative feature. For example, you might decide that you want to create new user roles with permissions that only apply to certain types of files. If these were java files, you could define that as a resource using the regular expression "*.java". Then you could either create new roles or modify existing roles by adding permissions defined with this "*.java" resource. Your newly created resource automatically appears in the <b>Add Permission to Role</b> page. When you grant these roles to users, their permissions are limited to java files only.
+<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/DomAdminRoles.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminRoles.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminRoles.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,207 @@
+<!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 roles and permissions</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="domadminroles">
+ <h2>Administering roles and permissions</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>
+ Administering roles and permissions
+
+ <ul>
+ <li><a href="#aboutroles">Understanding roles and permissions</a></li>
+
+ <li><a href="#aboutroles"></a><a href="#userroles">Editing user role assignments</a></li>
+
+ <li><a href="#editroles">Editing roles</a></li>
+
+ <li><a href="#addroles">Adding roles</a></li>
+
+ <li><a href="#viewaddresources">About resources and actions</a></li>
+ </ul>
+ </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>
+ </li>
+ </ul>
+ </div>
+
+
+ <h3><a id="aboutroles" name="aboutroles">Understanding roles and permissions</a></h3>
+
+ <p>Users must have permissions assigned to allow them to do anything on the site. Permissions are a combination of the actions that can be performed and the resources upon which they can be used. Actions include activities like reading, writing, editing, deleting, creating and suggesting. Resources can be anything from projects to users; any item that is added to the project is a resource.</p>
+
+ <p>When choosing what permission to grant to users it is important to keep in mind the minimum rights the user needs. For instance, if you want a user to be able to suggest a project document to the administrator for approval, you should grant the user <b>ProjectDocument - Suggest</b> permission but not the ProjectDocument - Approve permission. Likewise, if you would like a user to be able to view their own profile without being able to change it, you should grant them the <b>User - View - Self</b> permission but not the <b>User - Edit - Self</b> permission. For a full list of permissions with descriptions see <a href="/nonav/docs/DomAdminActions.html">Actions and Permissions</a>.</p>
+
+ <p>Every user on this site is able to access features and conduct activities based upon roles the user has been granted. There are two kinds of roles:</p>
+
+ <ul>
+ <li><b><i>Domain roles:</i></b> give users access to generalized information and actions throughout the site. Domain Administrators assign and configure domain roles to all users on this site. Every new user automatically gets the "registered user" domain role by virtue of being registered on your domain. It is also possible to create other domain roles; more about this is covered in the <a href="#addroles">Adding roles</a> section of this document.</li>
+
+ <li><b><i>Project roles:</i></b> limited to information and actions within a project. Domain Administrators also can configure project roles, but by design Project Owners usually assign project roles to users when they become project members.</li>
+ </ul>
+
+ <p>Roles are either assigned to users through membership in a project, or through association with project groups or user groups. All roles have a default set of permissions associated with them. These permissions govern the users' ability to conduct certain actions on this site.</p>
+
+ <p>As Domain Administrator, you can:</p>
+
+ <ul>
+ <li>Use and assign existing roles.</li>
+
+ <li>Alter existing roles by changing the permissions, actions, and/or resources that are associated with them.</li>
+
+ <li>Create entirely new roles and designate permissions for them. See <a href="#addroles">Adding roles</a>.</li>
+ </ul>
+
+ <p>You can also tailor roles and permissions for sets of users by creating user groups, and for sets of projects by making project groups. For more information about this, see <a href="/nonav/docs/DomAdminProjectGroups.html">Creating and editing project groups</a> and <a href="/nonav/docs/DomAdminUserGroups.html">Creating and editing user groups</a>.</p>
+
+ <h3><a id="userroles" name="userroles">Editing user role assignments</a></h3>
+
+ <p>The fields and options on the <b>Edit User</b> page enable you to view and change the individual user's role assignments.</p>
+
+
+ <dl>
+ <dt>Group Memberships</dt>
+
+ <dd>The user's affiliation with any user group or project categories in this domain are listed here. User groups and project groups are created and configured by you as the Domain Administrator. See <a href="/nonav/docs/DomAdminProjectGroups.html">Creating and editing project groups</a> and <a href="/nonav/docs/DomAdminUserGroups.html">Creating and editing user groups</a> for more information.</dd>
+
+ <dt>Domain-wide Roles</dt>
+
+ <dd>Domain roles assigned or conferred to the user are listed here. These are generalized roles that permit the user to view site pages and conduct site actions not associated with specific projects. See previous <a href="#aboutroles">Understanding roles and permissions</a> section.</dd>
+
+ <dt>Roles in domain's public projects</dt>
+
+ <dd>Every public project hosted on this domain is automatically part of the default project group labeled (not surprisingly) "All public projects." Any roles the user holds in such projects are flagged here. See <a href="/nonav/docs/DomAdminProjectGroups.html">Creating and editing project groups</a> for more information.</dd>
+
+ <dt>Submit Changes</dt>
+
+ <dd>This button submits any modifications to the individual user account made in the fields above. Modifications to the user's roles are separate actions.</dd>
+
+ <dt>Project Roles</dt>
+
+ <dd>Roles the user holds that are associated with specific projects are listed here, grouped by project name. Project names link to project home pages. This list includes both open source and private, proprietary projects. See <a href="#aboutroles">Understanding roles and permission</a> section for a more comprehensive discussion of roles.</dd>
+
+ <dt>Detailed Role Info</dt>
+
+ <dd>
+ These links lead to secondary screens with more detailed role information associated with the current user:
+
+ <ul>
+ <li><i>Direct and derived roles</i> displays two different sets roles held by the user. <i>Direct roles</i> are those roles expressly assigned to the user. For example, the user requested and was approved for a certain role in a project. <i>Derived roles</i> are roles <i>conferred</i> to this user because she/he is a member of a project specifically associated with a project group's set of roles, or belongs to a user group assigned a unique set of roles.</li>
+
+ <li><i>Details of permissions</i> displays a screen rather unceremoniously entitled <b>Permission Dump</b> because it tabulates literally every single permission the user holds in your domain.</li>
+ </ul>
+
+ <p>Note that when individual users are part of particular project groups or user groups, you can assign attributes and modify multiple user accounts associated with those groups by using the <b>Project Group Edit</b> or <b>User Group Edit</b> screens. See <a href="/nonav/docs/DomAdminProjectGroups.html">Creating and editing project groups</a> and <a href="/nonav/docs/DomAdminUserGroups.html">Creating and editing user groups</a> for more information.</p>
+ </dd>
+
+ <dt>Other operations: <i>Delete User</i></dt>
+
+ <dd>This link removes the current user account. A confirmation message prompts you for verification before this action is completed.</dd>
+ </dl>
+
+ <h3><a id="editroles" name="editroles">Editing roles</a></h3>
+
+ <p>This site features a set of default roles that you may view using the <i>Administer Roles</i> link in the "Admin Options" of your <b>Start Page</b>. This displays the <b>Role List</b> page with all site roles listed as either domain or project-level. A brief description of each role is included.</p>
+
+ <p>To view a list of individual permissions associated with this role, click on the role name link in the <b>Role List</b> page. Each permission listed on the <b>Editing Role</b> page is characterized by both the site resource and site action that it enables, i.e. "Project - Suggest" or "Version Control - Update." The far right "Resource(s)" column defines in which site resources each permission is effective. The default is for each permission to apply to all available resources.</p>
+
+ <p>As domain administrator, you have the option to modify the default roles for the site by changing the permissions associated with them as needed. Placing a check mark in the boxes next to a permission <i>removes this permission</i> from the role.</p>
+
+ <p>If you wish to <i>add</i> permissions to a role, click the <i>Add New Permission</i> link at the top of the <b>Editing Role</b> page. This screen gives you a list of all available permissions. To add permissions, place check marks in the appropriate boxes.</p>
+
+ <p>In addition to editing roles by adding and removing permissions, you can modify or limit which resources the permissions associated with that role will apply to. The resource section on the <b>Add Permission to Role</b> page lets you determine to which site resources to allocate the role's new permissions.</p>
+
+ <ul>
+ <li>Selecting "All available resources .*" applies the selected permissions for this role universally to all site resources available to this role, including both web content and source code.</li>
+
+ <li>Choosing "All web pages /www/.*" limits the selected permission for this role specifically to web pages. This means the scope of these permissions 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 "All web pages /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.</li>
+ </ul>
+
+ <p>After you have selected the permissions to add and determined the site resources to apply these to, click the <b><i>Add Permissions</i></b> button.</p>
+
+ <p>See the section on <a href="#viewaddresources">Viewing and adding resources</a> for more information about site resources.</p>
+
+ <h3><a id="addroles" name="addroles">Adding 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 site and/or projects within your domain. You should take some time to plan the scope of any new role you create before beginning the creation process. You can create roles for the Host, Domain, or Projects. Host roles enable ssociated user actions across all domains. Domain roles enable associated user actions across the site. Project roles enable associated user actions within the projects only. You can create roles that are specific to one or more particular projects or associate the roles across all projects.</p>
+
+ <ol>
+ <li>To add new roles, select <b>Roles</b> from the <b>Admin Options</b> menu to access the <b>Role List</b> page.</li>
+
+ <li>Click the "Add New Role" link in either the host, domain or project section. Depending upon which link you click, this displays either the <b>Add Host Role, Add Domain Role</b> or <b>Add Project Role</b> page. You can switch between these pages using the links at the top of this page.</li>
+
+ <li>Applies only to <b>Project Role</b> Select he visibility of the role. This determines at what level the project role can be seen. Selecting the Host level will make the role visible at all levels of the site. Selecting the Domain level restricts the visibility to the domain and project level, while the Project level will make the role only viewable at the project level.</li>
+
+ <li>Enter a name and a description of the role. The role name can be up to 99 charactersin length and connot 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.
+
+ <ul>
+ <li>The first item when checked prevents a user with this role in a project to have 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>
+
+ <li>The second item, when selected, 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>The third item, when selected, grants the role to users who create new projects.</li>
+
+ <li>The fourth item, when selected, 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>
+ </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>
+
+
+ <h3><a id="viewaddresources" name="viewaddresources">About resources and actions</a></h3>
+
+ <p><b><i>Resources</i></b> are all of the different elements used in this site including tools, content, projects, and web pages. User roles and permissions on this site are defined by the specific resources they apply to. For example, each of these permissions -- "Mailing List - View," "Project - Suggest," "Version Control - Commit" -- is comprised of a certain resource on this site and the <b><i>action </i></b> being permitted within that resource. In these three examples, the resources are, respectively: mailing list, project, and version control.</p>
+
+<p>Resources are described on this site using regular expressions. Thus, the pattern or regular expression meaning all available resources is ".*".</p>
+
+<p>As the domain administrator, you can view existing resources by clicking the <i>Resources </i> link in the Administration menu. The default items in the Resource List page are "All available resources (.*)" and "All web pages (/www/.*)". Clicking on the resource link displays the <b>Edit Resource</b> screen where there is short, identifying description and the pattern that represents the resource as a regular expression.</p>
+
+<p>You can also create new resources to increase your ability to control user access. For example, you might decide that you want to create new user roles with permissions that only apply to certain types of files. If these were java files, you could define that as a resource using the regular expression "*.java". Then you could either create new roles or modify existing roles by adding permissions defined with this "*.java" resource. When you grant these roles to users, their permissions are limited to java files only.</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/DomAdminUserGroups.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminUserGroups.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminUserGroups.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,122 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Creating and editing user groups</title>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+
+<span class="Header">Creating and editing user groups</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><b>You are here: Creating and editing user groups
+ <ul>
+ <li><a href="#whatis">What is a user group?</a>
+ <li><a href="#createusergroup">Creating user groups</a>
+ <li><a href="#editusergroup">Editing user groups</a>
+ <li><a href="#assign">Assigning roles and permissions to user groups</a>
+ </ul></b>
+ <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="whatis"></a><span class="InputHeader">What is a user group?</span>
+<span class="PlainText"><p>
+A user group allows the Domain Administrator to designate a collection of users who share a special set of privileges for designated projects on this site. This lets you assign roles, and the permissions associated with those roles, to a select group of users in a single operation. Roles can also be removed from user groups in the same manner.
+<p>
+Assigning or removing user group privileges is handled within the context of project groups. More information about this is available in <a href="DomAdminProjectGroups.html">Creating and editing project groups</a>. The document you are currently viewing covers how to create and edit user groups.
+<p>
+As an example of how you might apply the user group feature, suppose your site includes projects which require some users who contribute to projects only for a limited time. You could define a "Contract Project Group" for all those affected projects. Then you could create a "Contractors User Group" and assign modified roles to this group to limit their access and privileges.
+<p>
+You could also define user groups in alignment with your organizational structure, such as by departments or development teams, then tailor the roles and permissions to suit the types of site activities you want to allow these groups of users.
+<p>
+
+
+<hr noshade size=1>
+<a name="createusergroup"></a><span class="InputHeader">Creating user groups</span>
+<p>
+To create a user group:
+<p>
+<ul>
+<li>In the "Admin Options" section of your <b>Start Page</b>, click the <i>Administer User Groups</i> link to display the <b>All User Groups</b> page.
+<p>
+<li>Click the <i>Add New User Group</i> link in the top right corner to display the <b>Add A User Group</b> screen.
+<p>
+<li>Choose a one-word name to identify this new group. Do not use spaces in the name. Use the description field to provide any additional qualifying information about the group.
+<p>
+<li>Enter users to be included by login name in the <b><i>Initial Users</i></b> field. Enter one user per line. If you need to look up users, click on the <b><i>Users</i></b> link in the "Admin Options" tool bar at the top of the screen. This displays the <b>User List</b> screen. Then use your browser's Back button to return to the <b>Add A User Group</b> screen.
+<p>
+<li>Click the <b>Create Group</b> button to finish.
+</ul>
+<p>
+After you have submitted the new user group, the <b>All User Groups</b> page displays with the new group added.
+<p>
+
+
+<hr noshade size=1>
+<a name="editusergroup"></a><span class="InputHeader">Editing user groups</span>
+<p>If you need to view, add, or remove members from a user group:
+<ul>
+<li>In the "Admin Options" section of your <b>Start Page</b>, click the <i>Administer User Groups</i> link to display the <b>All User Groups</b> page.
+<p>
+<li>Click on the user group name to display the <b>User Group Edit</b> screen.
+</ul>
+This page lists all users who are included in the selected user group. You can conduct the following actions here:
+<ul>
+<li>Modify the group description.
+<p>
+<li>View individual user account information by clicking on user names.
+<p>
+<li>Add more users with the <i>Add New User to Group</i> link which displays the <b>Add Users</b> screen allowing you to make one or more selections. Finish by clicking the <b><i>Add to Group</i></b> button.
+<p>
+<li>Remove users by placing a checkmark in the "Remove From Group" column, then pressing the <b><i>Remove Elements</i></b> button.
+<p>
+<li>Remove the entire user group completely using the <i>Delete Group</i> link. (This eradicates only the user group association; it does not delete the individual user accounts in the group.)
+</ul>
+<p>
+
+<hr noshade size=1>
+<a name="assign"></a><span class="InputHeader">Assigning roles and permissions to user groups</span>
+<p>
+Because user groups are designed to work in conjunction with project groups, you must assign a particular set of roles and permissions to users in a group en masse within the context of creating and editing a project group. See <a href="DomAdminProjectGroups.html#editprojgroups">Editing project groups</a> for more details.
+<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>
+
+</span>
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminUserGroups.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminUserGroups.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminUserGroups.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,120 @@
+<!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 user groups</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="domadminusergroups">
+ <h2>Creating and editing user groups</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>
+ Creating and editing user groups
+
+ <ul>
+ <li><a href="#whatis">What is a user group?</a></li>
+
+ <li><a href="#createusergroup">Creating user groups</a></li>
+
+ <li><a href="#editusergroup">Editing user groups</a></li>
+
+ <li><a href="#assign">Assigning roles and permissions to user groups</a></li>
+ </ul>
+ </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>
+ </li>
+ </ul>
+ </div>
+
+ <h3><a id="whatis" name="whatis">What is a user group?</a></h3>
+
+ <p>A user group allows the Domain Administrator to designate a collection of users who share a special set of privileges for designated projects on this site. This lets you assign roles, and the permissions associated with those roles, to a select group of users in a single operation. Roles can also be removed from user groups in the same manner.</p>
+
+ <p>Assigning or removing user group privileges is handled within the context of project groups. More information about this is available in <a href="/nonav/docs/DomAdminProjectGroups.html">Creating and editing project groups</a>. The document you are currently viewing covers how to create and edit user groups.</p>
+
+ <p>As an example of how you might apply the user group feature, suppose your site includes projects which require some users who contribute to projects only for a limited time. You could define a "Contract Project Group" for all those affected projects. Then you could create a "Contractors User Group" and assign modified roles to this group to limit their access and privileges.</p>
+
+ <p>You could also define user groups in alignment with your organizational structure, such as by departments or development teams, then tailor the roles and permissions to suit the types of site activities you want to allow these groups of users.</p>
+
+ <h3><a id="createusergroup" name="createusergroup">Creating user groups</a></h3>
+
+ <p>To create a user group:</p>
+
+ <ul>
+ <li>In the "Admin Options" section of your <b>Start Page</b>, click the <i>Administer User Groups</i> link to display the <b>All User Groups</b> page.</li>
+
+ <li>Click the <i>Add New User Group</i> link in the top right corner to display the <b>Add A User Group</b> screen.</li>
+
+ <li>Choose a one-word name to identify this new group. Do not use spaces in the name. Use the description field to provide any additional qualifying information about the group.</li>
+
+ <li>Enter users to be included by login name in the <b><i>Initial Users</i></b> field. Enter one user per line. If you need to look up users, click on the <b><i>Users</i></b> link in the "Administration Tools". This displays the <b>User List</b> screen. Then use your browser's Back button to return to the <b>Add A User Group</b> screen.</li>
+
+ <li>Click the <b>Create Group</b> button to finish.</li>
+ </ul>
+
+ <p>After you have submitted the new user group, the <b>All User Groups</b> page displays with the new group added.</p>
+
+ <h3><a id="editusergroup" name="editusergroup">Editing user groups</a></h3>
+
+ <p>If you need to view, add, or remove members from a user group:</p>
+
+ <ul>
+ <li>In the "Admin Options" section of your <b>Start Page</b>, click the <i>Administer User Groups</i> link to display the <b>All User Groups</b> page.</li>
+
+ <li>Click on the user group name to display the <b>User Group Edit</b> screen.</li>
+ </ul>
+
+ <p>This page lists all users who are included in the selected user group. You can conduct the following actions here:</p>
+
+ <ul>
+ <li>Modify the group description.</li>
+
+ <li>View individual user account information by clicking on user names.</li>
+
+ <li>Add more users with the <i>Add New User to Group</i> link which displays the <b>Add Users</b> screen allowing you to make one or more selections. Finish by clicking the <b><i>Add to Group</i></b> button.</li>
+
+ <li>Remove users by placing a checkmark in the "Remove From Group" column, then pressing the <b><i>Remove Elements</i></b> button.</li>
+
+ <li>Remove the entire user group completely using the <i>Delete Group</i> link. (This eradicates only the user group association; it does not delete the individual user accounts in the group.)</li>
+ </ul>
+
+ <h3><a id="assign" name="assign">Assigning roles and permissions to user groups</a></h3>
+
+ <p>Because user groups are designed to work in conjunction with project groups, you must assign a particular set of roles and permissions to users in a group en masse within the context of creating and editing a project group. See <a href="/nonav/docs/DomAdminProjectGroups.html#editprojgroups">Editing project groups</a> for more details.</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/DomAdminUtils.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminUtils.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomAdminUtils.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,152 @@
+<!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>Using host administration tools</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="hostadminutils">
+ <h2><a id="HostAdminUtils" name = "hostadminutils">Using domain administration
+ tools</a></h2>
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+
+ <ul>
+ <li>Help for domain administration
+ <ul>
+ <li>Using domain adminstration tools
+ <ul>
+ <li><a href="#sessions">Sessions</a></li>
+ <li><a href="#config">Configure site</a> </li>
+ <li><a href="#build">Build information</a></li>
+ <li><a href="#broadcast">Broadcast message</a></li>
+ <li><a href="#viewlog">Audit logs</a> </li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ </ul>
+</div>
+ <p>The host administrator can set a variety of options for the entire site.
+ These options should be set with caution as they can adversely affect the
+ entire site. Access the host administrator tools from the <strong>Administration
+ </strong> tab. </p>
+ <dl>
+ <dt><a name="sessions"></a>Sessions</dt>
+ <dd>You can view a list of users currently logged into your site by clicking
+ the <strong>Active User Sessions</strong> link. This servlet lists the logged
+ in users by username and details the time and date each logged in, the last
+ servlet accessed by each, and the last access time for each user. While
+ this information is not logged, periodically reviewing the active user session
+ provides insight into who is accessing your site.</dd>
+ <dd> </dd>
+ <dt><a name="config"></a>Configure site</dt>
+ <dd>Use the <strong>Configure site</strong> link to set site wide configuration options.
+ Configuration options are organized into three categories; <a href="#domain">Domain
+ Options </a>and <a href="#project">Project Options</a>. Use the tabs to
+ navigate between configuration sets. </dd>
+ <dt> </dt>
+ <dd>The following options can be set: </dd>
+ <dd>
+ <p> <a name="domain" id="domain"></a><strong><em>Domain Options</em></strong></p>
+ <dl>
+ <dt>Enable dicussion forums</dt>
+ <dd>You can enable or disable the use of discussion forums site-wide.</dd>
+ <dt>Issue tracking component</dt>
+ <dd>You can choose which issue tracking components will be available for
+ projects.</dd>
+ <dt>Domain contact</dt>
+ <dd>You can define an email address for the domain contact.</dd>
+ <dt>Allow guest access</dt>
+ <dd>You can enable or disable the ability for users to see public portions
+ of the site without logging in.</dd>
+ <dt>Always allow access to domain home</dt>
+ <dd>You can make the domain home page visible to all users, even if guest
+ access is turned off.</dd>
+ <dt>Allow user join</dt>
+ <dd>You can enable or disable the ability for users to register on the
+ site. Note, this option is available only when guest user access is
+ enabled.</dd>
+ <dt>Enable community section</dt>
+ <dd>You can activate a community section seperate from the SourceCast
+ tools. The community section can be used to communicate important information
+ to community members.</dd>
+ <dt>Project path separator string</dt>
+ <dd>You can define a character to separate the names of projects within
+ a parentage tree. For example, SuperProject>SuperProject>Project,
+ where > is the separator character. Be sure to add any needed spaces.</dd>
+ <dt>Enforce click-through</dt>
+ <dd>You can enable or disable the requirement for users to agree to the
+ Terms of Use.</dd>
+ <dt>Send plaintext passwords to new users</dt>
+ <dd>New users can receive their current passwords in plaintext email,
+ instead of having a ticket to set their passwords generated. NOTE: this
+ is a potential security risk and should be set only as required.</dd>
+ <dt>Destination on login</dt>
+ <dd>You can choose whether users are sent to their individual start pages
+ or to the community page after logging in.</dd>
+ <dt>Policy on public projects</dt>
+ <dd>You can select whether to allow new projects to be public or private
+ and set a default.</dd>
+ <dt>Show project artifact links on category home page</dt>
+ <dd>You can enable or disable the display of project artifacts on category
+ home pages.</dd>
+ <dt>User can edit own organization</dt>
+ <dd>You can enable or disable the ability for users to edit the <strong>Organization</strong>
+ field on their own user profiles.</dd>
+ <dt>List of file extensions that should always be downloaded</dt>
+ <dd>You can force users to download files with certain extensions, rather
+ than allowing browser plug-ins to automatically open these files. Multiple
+ entries should be seperated by spaces (e.g. .wmv .mp3).</dd>
+ <dt>Show project artifact links on category home</dt>
+ <dd>Checking this adds links to project artifact resources on category
+ home pages</dd>
+ <dt>Users can edit own organizations</dt>
+ <dd>allows users to edit their own "Organization" fields.</dd>
+ </dl>
+ <p><a name="project" id="project"></a><strong><em>Project Default Options</em></strong></p>
+ </dd>
+ <dd>
+ <dl>
+ <dt>Maximum attachment size</dt>
+ <dd>You can define the maximum attachment size that can be uploaded to
+ a project's <strong>Discussion forums</strong> component.</dd>
+ <dt>Maximum file upload size</dt>
+ <dd>You can define the maximum file size that can be uploaded to a project's
+ <strong>File sharing</strong> component.</dd>
+ <dt>Offer to lock files</dt>
+ <dd>You can enable or disable the ability for user to lock files when
+ they are first created in a project's <strong>File sharing</strong> component.</dd>
+ </dl>
+ </dd>
+ <dt><a name="build"></a>Build information</dt>
+ <dd>Use the <strong>Build Information</strong> link to view current build
+ information. Clicking this link will display the versions number, build
+ number and build instance of SourceCast.</dd>
+ <dt><a name="broadcast"></a>Broadcast message</dt>
+ <dd>Use the <strong>Broadcast message</strong> link to enter a message to be displayed
+ at the top od every page viewed by users.</dd>
+ <dt><a name="viewlog"></a>View system logs</dt>
+ <dd>Use the <strong>View system logs </strong>link to select a log to view. </dd>
+ <dt> </dt>
+ </dl>
+
+ <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/DomainCommunity.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCommunity.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCommunity.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,104 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<TITLE>Community</TITLE>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
+ <TR>
+ <TD class="Header" nowrap>Community</TD>
+ </TR>
+</TABLE>
+
+<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
+ <TR>
+ <TD class="ProjectDownloadHeader" bgcolor="#efefef">Welcome to the community!</TD>
+ </TR>
+ <TR>
+ <TD class="InputHeader" VALIGN="top">Brief paragraph on community scope</TD>
+ </TR>
+ <TR>
+ <TD class="PlainText" VALIGN="top">
+ <UL>
+ <LI>This is a working website for developers to share code and hosted tools among their own team members on their own project</LI>
+ <LI>This is a forum for discussing relevant technologies </LI>
+ <LI>This is a repository for seeded code</LI>
+ <LI>This is a meeting place for open source development when developers find mutual self-interests</LI>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD class="InputHeader" VALIGN="top">Details of community goals</TD>
+ </TR>
+ <TR>
+ <TD class="PlainText" VALIGN="top">
+ <UL>
+ <LI>why does this community exist? </LI>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD class="InputHeader" VALIGN="top">Community structure and governance</TD>
+ </TR>
+ <TR>
+ <TD class="PlainText" VALIGN="top">
+ <UL>
+ <LI>how is this community set up?</LI>
+ <LI>who are the stakeholders?</LI>
+ <LI>who holds editorial control? (mainly collab, some by sponsor but NOT censorship)</LI>
+ <LI>who holds copyrights? (jose said "joint copyright like slashdot", need more info)</LI>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD class="InputHeader" VALIGN="top">People and History</TD>
+ </TR>
+ <TR>
+ <TD class="PlainText" VALIGN="top">
+ <UL>
+ <LI>who started this site and when?</LI>
+ <LI>who is the intended audiance?</LI>
+ <LI>what companies are involved?</LI>
+ <LI>broad projections for the future of the site</LI>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD class="InputHeader" VALIGN="top">How to participate</TD>
+ </TR>
+ <TR>
+ <TD class="PlainText" VALIGN="top">
+ <UL>
+ <LI>how to get started?</LI>
+ <LI>proprietary or open source?</LI>
+ <LI>how does someone move from one level of partipation to another?</LI>
+ <LI>Terms of Use, Privacy Policy</LI>
+ <LI>link to community section of FAQ</LI>
+ </UL>
+ </TD>
+ </TR>
+</table>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCommunity.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCommunity.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCommunity.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,84 @@
+<!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>Community</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="domaincommunity">
+ <h2>Community</h2>
+
+ <h3>Welcome to the community!</h3>
+
+ <p>Brief paragraph on community scope</p>
+
+ <ul>
+ <li>This is a working website for developers to share code and hosted tools among their own team members on their own project</li>
+
+ <li>This is a forum for discussing relevant technologies</li>
+
+ <li>This is a repository for seeded code</li>
+
+ <li>This is a meeting place for open source development when developers find mutual self-interests</li>
+ </ul>
+
+ <h3>Details of community goals</h3>
+
+ <ul>
+ <li>why does this community exist?</li>
+ </ul>
+
+ <h3>Community structure and governance</h3>
+
+ <ul>
+ <li>how is this community set up?</li>
+
+ <li>who are the stakeholders?</li>
+
+ <li>who holds editorial control? (mainly collab, some by sponsor but NOT censorship)</li>
+
+ <li>who holds copyrights? (jose said "joint copyright like slashdot", need more info)</li>
+ </ul>
+
+ <h3>People and History</h3>
+
+ <ul>
+ <li>who started this site and when?</li>
+
+ <li>who is the intended audiance?</li>
+
+ <li>what companies are involved?</li>
+
+ <li>broad projections for the future of the site</li>
+ </ul>
+
+ <h3>How to participate</h3>
+
+ <ul>
+ <li>how to get started?</li>
+
+ <li>proprietary or open source?</li>
+
+ <li>how does someone move from one level of partipation to another?</li>
+
+ <li>Terms of Use, Privacy Policy</li>
+
+ <li>link to community section of FAQ</li>
+ </ul>
+
+ <div class="courtesylinks">
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCopyright.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCopyright.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCopyright.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,75 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<TITLE>Domain Copyright</TITLE>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
+ <TR>
+ <TD class="Header" nowrap>Domain Copyright</TD>
+ </TR>
+</TABLE>
+
+<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
+ <TR>
+ <TD class="PlainText" VALIGN="top">
+ <P>All trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the individual who posted them. All other content �2000 Collab.Net, Inc. </P>
+
+ <P><b>COPYRIGHT POLICY</b></P>
+
+ <P><b>COPYRIGHTS AND COPYRIGHT AGENT</b></P>
+
+ <P>Collab.Net, Inc. ("Collab.Net") is committed to respecting others' intellectual property rights, and we ask our users to do the same. Collab.Net may, in its sole discretion, terminate the accounts or access rights of users who violate others' intellectual property rights.</P>
+
+ <P>If you believe that your work has been copied in a way that constitutes copyright infringement on our Website, please deliver the following information to Collab.Net's Copyright Agent:</P>
+
+ <ol>
+ <li> an electronic or physical signature of the person authorized to act on behalf of the copyright owner;</li>
+
+ <li> a description of the copyrighted work that you claim has been infringed;</li>
+
+ <li> a description of where the material that you claim is infringing is located on our Website;</li>
+
+ <li> your address, telephone number, and email address so that we can contact you;</li>
+
+ <li> a statement by you that you have a good faith belief that the disputed use is not authorized by the copyright owner, its agent, or the law; and</li>
+
+ <li> a statement by you, made under penalty of perjury, that the information in your notice to us is accurate and that you are the copyright owner or authorized to act on the copyright owner's behalf.</li>
+ </ol>
+
+ <P>Collab.Net's Copyright Agent for notice of claims of copyright infringement on our Website can be reached as follows:</P>
+
+ <P><b>By mail:</b> <BR>
+ Copyright Department <BR>
+ Collab.Net, Inc.<BR>
+ 425 2nd Street, 5th Floor<BR>
+ San Francisco, CA 94107</P>
+ <P><b>By email:</b><BR>
+ netbeans-copyright@collab.net</P>
+ </TD>
+ </TR>
+</table>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCopyright.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCopyright.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainCopyright.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,46 @@
+<!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 copyright</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="domaincopyright">
+ <h2>Domain Copyright</h2>
+
+ <p>All trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the individual who posted them. All other content ©2000 Collab.Net, Inc.</p>
+
+ <p>COPYRIGHT POLICY</p>
+
+ <p>COPYRIGHTS AND COPYRIGHT AGENT</p>
+
+ <p>Collab.Net, Inc. ("Collab.Net") is committed to respecting others' intellectual property rights, and we ask our users to do the same. Collab.Net may, in its sole discretion, terminate the accounts or access rights of users who violate others' intellectual property rights.</p>
+
+ <p>If you believe that your work has been copied in a way that constitutes copyright infringement on our Website, please deliver the following information to Collab.Net's Copyright Agent:</p>
+
+ <ol>
+ <li>an electronic or physical signature of the person authorized to act on behalf of the copyright owner;</li>
+
+ <li>a description of the copyrighted work that you claim has been infringed;</li>
+
+ <li>a description of where the material that you claim is infringing is located on our Website;</li>
+
+ <li>your address, telephone number, and email address so that we can contact you;</li>
+
+ <li>a statement by you that you have a good faith belief that the disputed use is not authorized by the copyright owner, its agent, or the law; and</li>
+
+ <li>a statement by you, made under penalty of perjury, that the information in your notice to us is accurate and that you are the copyright owner or authorized to act on the copyright owner's behalf.</li>
+ </ol>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainFAQ.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainFAQ.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainFAQ.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,207 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Frequently Asked Questions</title>
+<!-- Changed by: Lori Houston, 30-May-2001 -->
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<table border="0" cellspacing="1" cellpadding="3" border="0" width="100%">
+ <tr>
+ <td class="Header" nowrap>Site FAQ</td>
+ </tr>
+
+ <tr>
+ <td class="ProjectDownloadHeader" bgcolor="#efefef">Sections:</td>
+ </tr>
+ <tr>
+ <td class="InputHeader" valign="top">Community FAQ</td>
+ </tr>
+ <tr>
+ <td class="PlainText" valign="top">
+ <ul>
+ <li><a href="DomainFAQ.html#purpose">What's the purpose of this site?</a></li>
+ <li><a href="DomainFAQ.html#whoelseishere">Who else is here?</a></li>
+ <li><a href="DomainFAQ.html#onlyosproj">Is this site only for open source developers?</a></li>
+ <li><a href="DomainFAQ.html#hostpart">What is <!-- $host --> CollabNet's role in this site?</a></li>
+ <li><a href="DomainFAQ.html#hostedtools">What do you mean by "hosted tools"?</a></li>
+ <li><a href="DomainFAQ.html#whattools">What are those tools?</a></li>
+ <li><a href="DomainFAQ.html#contact">Who do I contact for help or feedback?</a></li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td class="InputHeader" valign="top">How to Participate</td>
+ </tr>
+ <tr>
+ <td class="PlainText" valign="top">
+ <ul>
+ <li><a href="DomainFAQ.html#clientside">What client-side tools will I need to participate?</a></li>
+ <li><a href="DomainFAQ.html#startproj">How do I start a project?</a></li>
+ <li><a href="DomainFAQ.html#content">How do I put proprietary content on my section of the site securely?</a></li>
+ <li><a href="DomainFAQ.html#share">How do I share code?</a></li>
+ <li><a href="DomainFAQ.html#getinvolved">How do I get other developers involved in my project?</a></li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td class="InputHeader" valign="top">Security FAQ</td>
+ </tr>
+ <tr>
+ <td class="PlainText" valign="top">
+ <ul>
+ <li><a href="DomainFAQ.html#protect">What steps do we take to protect your data?</a></li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td> </td>
+ </tr>
+ <tr>
+ <td class="ProjectDownloadHeader" bgcolor="#efefef">Sections:</td>
+ </tr>
+ <tr>
+ <td class="InputHeader" valign="top">Community FAQ</td>
+ </tr>
+ <tr>
+ <td class="PlainText" valign="top">
+
+<p><a name="purpose"><b>Q: What's the purpose of this site?</a></b>
+<p>
+<b>A:</b> SourceCast is dedicated web space for registered developers like you to turn your ideas into active, productive development projects. Here you can participate with other like-minded developers who share this vision. You can even invite developers
+whose expertise you seek to join you. But more than that, all the web-based tools you need to manage your project and collaborate with other developers <i>to get
+it done</i> also reside here.
+<!-- "more info" links here -->
+
+<p><b><a name="whoelseishere">Q: Who else is here?</a></b>
+<p>
+<b>A:</b> Other developer community members, Java developers, open source developers ... any developers who have been invited by project leaders and other developers to collaborate on projects hosted on SourceCast.
+
+<p><a name="hostpart"><b>Q: What is <!-- --> CollabNet's role in this site?</a></b>
+<p>
+<b>A:</b> <!-- --> CollabNet is hosting this site to offer additional opportunities for developer members. This site seeks to extend open source development practises by fostering a
+development community around it. Beyond this overarching mission, there is no other agenda or top-down hierarchy beyond what developers themselves create in this
+web space. The point is to empower developers to drive the ultimate direction of this technology's development through consensus and collaboration. That's one of
+the hallmarks of the open source software movement and the principal reason for its proliferation.
+
+<p><a name="onlyosproj"><b>Q: Is this site only for open source projects?</a></b>
+<p>
+<b>A:</b> Both</i> open source and proprietary projects are accommodated in SourceCast. The simple reason for this is to give developers the choice, acknowledging
+that some development ideas in the emerging Wireless Internet climate may be more viable under commercial licensing. SourceCast offers the best of both worlds by
+giving developers access to the <a href="hostedtools.html">collaborative tools</a> and <a href="bestpractices.html">best practices</a> characteristic of
+successful open source software development projects, while also enabling these to be applied to development in a secure web environment.
+<p>
+</td>
+ </tr>
+ <tr>
+ <td class="PlainText" valign="top">
+<p><a name="hostedtools"><b>Q: What do you mean by "hosted tools"?</a></b>
+<p>
+<b>A:</b> SourceCast enables collaborative development through
+<a href="hostedtools.html">web-based tools</a> made available to project owners
+and developers who become project members. SourceCast combines the best-of-breed
+open source tools into a web-based software development suite. Key features of this
+tool set are security, scalability, extensibility, and customizability.
+
+<p><a name="whattools"><b>Q: What are those tools?</a></b>
+<p>
+<b>A:</b> SourceCast provides simple, powerful web interfaces for
+<a href="ddCVS.html">version control</a>,
+<a href="ProjectIssues.html">issue tracking</a>,
+<a href="ProjectMail.html">discussions and decision-making</a>,
+automated builds<!-- LINK?-->, automated testing<!-- LINK?-->, project management and knowledge management<!-- LINK?-->. Project owners can configure these tools
+within each project and grant roles to project participants to fit the needs of the project.
+
+<p><a name="contact"><b>Q: Who do I contact for help or feedback?</a></b>
+<p>
+<b>A:</b> Send any questions or comments to <a mailto:feedback@sourcecast.com>feedback@sourcecast.com</a>.
+</td>
+ </tr>
+ <tr>
+ <td><hr size="1" noshade></td>
+ </tr>
+ <tr>
+
+ <td class="InputHeader" valign="top">How to Participate</td>
+ </tr>
+ <tr>
+ <td class="PlainText" valign="top">
+<p><a name="clientside"><b>Q: What client-side tools will I need to participate?</a></b>
+<p>
+<b>A:</b> At minimum, you need a web browser, email client, CVS, and optionally SSH to secure your CVS connections. There may be additional domain specific tools you need depending upon the types of development project you wish to contribute to.
+
+
+<p><a name="startproj"><b>Q: How do I start a project?</a></b>
+<p>
+<b>A:</b> Use the "Start New Project" links in the Start Page or subsequent pages to access a brief, four-screen project creation process. After you have
+submitted your project information, you're able to view and customize your newly created project home page. You project is in a "pending" status until approved by
+site administrators. <a href="ProjectAdd.html">Read more about the process.</a>
+
+<p><a name="content"><b>Q: How do I put proprietary content on my section of the site
+securely?</b></a>
+<p>
+<b>A:</b> If your development project is proprietary, only project members can view project documents, participate in project mailing lists, download/upload project files, view and report issues, and access the CVS repository. Proprietary project owners control project membership through a member approval process and project role assignments. In addition, the project administration tool allows project owners to grant specific permissions to individual users and developers through project role assignments.
+<p>
+SourceCast uses Secure Socket Layer (SSL) technology to establishes a secure connection between the user and server, with a private key to encrypt data when transferred across this connection. You can also use optional SSH tunneling to protect your CVS connections from password snooping, data corruption or theft. <a href="ddSSHGuide.html">More information about SSH</a> is available on this site.
+
+<p><a name="share"><b>Q: How do I share code?</a></b>
+<p>
+<b>A:</b> When you join or lead a SourceCast project, you use <a href="ddCVS.html">CVS version control</a> to check out and work with project files, and
+then contribute your changes back into the project's repository. When other project members update their working files, they have access then to your
+code. Everyone on the CVS mailing list also receives automatic email notification when files are updated.
+<p>
+As a project member you will likely be assigned to do code enhancements or contribute patches via <a href="ProjectIssues.html#aboutIZ">IssueZilla</a>, an issue
+tracking tool for managing project issues (defects, enhancements, features, tasks, and patches). You also subscribe to project mailing lists, where you can follow and participate in ongoing discussions about the project.
+
+<p><a name="getinvolved"><b>Q: How do I get other developers involved in my project?</a></b>
+<p>
+<b>A:</b> You can invited other developers to join your project at any time. When you start your own development project on SourceCast, the process includes an
+opportunity to list developers you want to invite to join you. They receive an automatically generated email that explains a little about SourceCast, gives the
+name and a brief description of your project, and includes a personalized message you have composed. After the project is already underway, you can invite someone
+by personal email at your discretion.
+<p>
+</td>
+ </tr>
+ <tr>
+ <td><hr size="1" noshade></td>
+ </tr>
+ <tr>
+ <td class="InputHeader" valign="top">Security FAQ</td>
+ </tr>
+ <tr>
+ <td class="PlainText" valign="top">
+<p><a name="protect"><b>Q: What steps do you take to protect my data?</a></b>
+<p>
+<b>A:</b> SourceCast take appropriate steps to protect the information you share with us from unauthorized access or disclosure.
+<p>
+
+In addition to sharing <!-- --> CollabNet developer site user ID/password authentication, SourceCast implements SSL security with a digital certificate. All pages in SourceCast are https secured through SSL encryption to protect any information in those pages and to authenticate that user information is sent to the correct server. Any CVS password information contained in user profiles for SourceCast is also encrypted to secure project information against unauthorized access.
+<p>
+For more information, see this site's <a href="DomainPrivacyPolicy.html">Privacy Policy</a> and <a href="DomainTermsOfUse.html">Terms of Use</a>.
+</td>
+ </tr>
+</table>
+
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainFAQ.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainFAQ.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/DomainFAQ.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,171 @@
+<!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>Site FAQ</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="domainfaq">
+ <h2>Site FAQ</h2>
+
+ <dl>
+ <dt>Community FAQ</dt>
+
+ <dd>
+ <ul>
+ <li><a href="/nonav/docs/DomainFAQ.html#purpose">What's the purpose of this site?</a></li>
+
+ <li><a href="/nonav/docs/DomainFAQ.html#whoelseishere">Who else is here?</a></li>
+
+ <li><a href="/nonav/docs/DomainFAQ.html#onlyosproj">Is this site only for open source developers?</a></li>
+
+ <li><a href="/nonav/docs/DomainFAQ.html#hostpart">What is <!-- $host --> CollabNet's role in this site?</a></li>
+
+ <li><a href="/nonav/docs/DomainFAQ.html#hostedtools">What do you mean by "hosted tools"?</a></li>
+
+ <li><a href="/nonav/docs/DomainFAQ.html#whattools">What are those tools?</a></li>
+
+ <li><a href="/nonav/docs/DomainFAQ.html#contact">Who do I contact for help or feedback?</a></li>
+ </ul>
+ </dd>
+
+ <dt>How to Participate</dt>
+
+ <dd>
+ <ul>
+ <li><a href="/nonav/docs/DomainFAQ.html#clientside">What client-side tools will I need to participate?</a></li>
+
+ <li><a href="/nonav/docs/DomainFAQ.html#startproj">How do I start a project?</a></li>
+
+ <li><a href="/nonav/docs/DomainFAQ.html#content">How do I put proprietary content on my section of the site securely?</a></li>
+
+ <li><a href="/nonav/docs/DomainFAQ.html#share">How do I share code?</a></li>
+
+ <li><a href="/nonav/docs/DomainFAQ.html#getinvolved">How do I get other developers involved in my project?</a></li>
+ </ul>
+ </dd>
+
+ <dt>Security FAQ</dt>
+
+ <dd>
+ <ul>
+ <li><a href="/nonav/docs/DomainFAQ.html#protect">What steps do we take to protect your data?</a></li>
+ </ul>
+ </dd>
+ </dl>
+
+ <h3>Community FAQ</h3>
+
+ <dl>
+ <dt><a id="purpose" name="purpose">Q: What's the purpose of this site?</a></dt>
+
+ <dd>
+ <p>A: SourceCast is dedicated web space for registered developers like you to turn your ideas into active, productive development projects. Here you can participate with other like-minded developers who share this vision. You can even invite developers whose expertise you seek to join you. But more than that, all the web-based tools you need to manage your project and collaborate with other developers <i>to get it done</i> also reside here. <!-- "more info" links here -->
+ </p>
+ </dd>
+
+ <dt><a id="whoelseishere" name="whoelseishere">Q: Who else is here?</a></dt>
+
+ <dd>
+ <p>A: Other developer community members, Java developers, open source developers ... any developers who have been invited by project leaders and other developers to collaborate on projects hosted on SourceCast.</p>
+ </dd>
+
+ <dt><a id="hostpart" name="hostpart">Q: What is <!-- --> CollabNet's role in this site?</a></dt>
+
+ <dd>
+ <p>A: <!-- --> CollabNet is hosting this site to offer additional opportunities for developer members. This site seeks to extend open source development practises by fostering a development community around it. Beyond this overarching mission, there is no other agenda or top-down hierarchy beyond what developers themselves create in this web space. The point is to empower developers to drive the ultimate direction of this technology's development through consensus and collaboration. That's one of the hallmarks of the open source software movement and the principal reason for its proliferation.</p>
+ </dd>
+
+ <dt><a id="onlyosproj" name="onlyosproj">Q: Is this site only for open source projects?</a></dt>
+
+ <dd>
+ <p>A: Both open source and proprietary projects are accommodated in SourceCast. The simple reason for this is to give developers the choice, acknowledging that some development ideas in the emerging Wireless Internet climate may be more viable under commercial licensing. SourceCast offers the best of both worlds by giving developers access to the <a href="/nonav/docs/hostedtools.html">collaborative tools</a> and <a href="/nonav/docs/bestpractices.html">best practices</a> characteristic of successful open source software development projects, while also enabling these to be applied to development in a secure web environment.</p>
+ </dd>
+
+ <dt><a id="hostedtools" name="hostedtools">Q: What do you mean by "hosted tools"?</a></dt>
+
+ <dd>
+ <p>A: SourceCast enables collaborative development through <a href="/nonav/docs/hostedtools.html">web-based tools</a> made available to project owners and developers who become project members. SourceCast combines the best-of-breed open source tools into a web-based software development suite. Key features of this tool set are security, scalability, extensibility, and customizability.</p>
+ </dd>
+
+ <dt><a id="whattools" name="whattools">Q: What are those tools?</a></dt>
+
+ <dd>
+ <p>A: SourceCast provides simple, powerful web interfaces for <a href="/nonav/docs/ddCVS.html">version control</a>, <a href="/nonav/docs/ProjectIssues.html">issue tracking</a>, <a href="/nonav/docs/ProjectMail.html">discussions and decision-making</a>, automated builds<!-- LINK?-->, automated testing<!-- LINK?-->, project management and knowledge management<!-- LINK?-->. Project owners can configure these tools within each project and grant roles to project participants to fit the needs of the project.</p>
+ </dd>
+
+ <dt><a id="contact" name="contact">Q: Who do I contact for help or feedback?</a></dt>
+
+ <dd>
+ <p>A: Send any questions or comments to feedback@sourcecast.com.</p>
+ </dd>
+ </dl>
+
+ <h3>How to Participate</h3>
+
+ <dl>
+ <dt><a id="clientside" name="clientside">Q: What client-side tools will I need to participate?</a></dt>
+
+ <dd>
+ <p>A: At minimum, you need a web browser, email client, CVS, and optionally SSH to secure your CVS connections. There may be additional domain specific tools you need depending upon the types of development project you wish to contribute to.</p>
+ </dd>
+
+ <dt><a id="startproj" name="startproj">Q: How do I start a project?</a></dt>
+
+ <dd>
+ <p>A: Use the "Start New Project" links in the Start Page or subsequent pages to access a brief, four-screen project creation process. After you have submitted your project information, you're able to view and customize your newly created project home page. You project is in a "pending" status until approved by site administrators. <a href="/nonav/docs/ProjectAdd.html">Read more about the process.</a></p>
+ </dd>
+
+ <dt><a id="content" name="content">Q: How do I put proprietary content on my section of the site securely?</a></dt>
+
+ <dd>
+ <p>A: If your development project is proprietary, only project members can view project documents, participate in project mailing lists, download/upload project files, view and report issues, and access the CVS repository. Proprietary project owners control project membership through a member approval process and project role assignments. In addition, the project administration tool allows project owners to grant specific permissions to individual users and developers through project role assignments.</p>
+
+ <p>SourceCast uses Secure Socket Layer (SSL) technology to establishes a secure connection between the user and server, with a private key to encrypt data when transferred across this connection. You can also use optional SSH tunneling to protect your CVS connections from password snooping, data corruption or theft. <a href="/nonav/docs/ddSSHGuide.html">More information about SSH</a> is available on this site.</p>
+ </dd>
+
+ <dt><a id="share" name="share">Q: How do I share code?</a></dt>
+
+ <dd>
+ <p>A: When you join or lead a SourceCast project, you use <a href="/nonav/docs/ddCVS.html">CVS version control</a> to check out and work with project files, and then contribute your changes back into the project's repository. When other project members update their working files, they have access then to your code. Everyone on the CVS mailing list also receives automatic email notification when files are updated.</p>
+
+ <p>As a project member you will likely be assigned to do code enhancements or contribute patches via <a href="/nonav/docs/ProjectIssues.html#aboutIZ">IssueZilla</a>, an issue tracking tool for managing project issues (defects, enhancements, features, tasks, and patches). You also subscribe to project mailing lists, where you can follow and participate in ongoing discussions about the project.</p>
+ </dd>
+
+ <dt><a id="getinvolved" name="getinvolved">Q: How do I get other developers involved in my project?</a></dt>
+
+ <dd>
+ <p>A: You can invited other developers to join your project at any time. When you start your own development project on SourceCast, the process includes an opportunity to list developers you want to invite to join you. They receive an automatically generated email that explains a little about SourceCast, gives the name and a brief description of your project, and includes a personalized message you have composed. After the project is already underway, you can invite someone by personal email at your discretion.</p>
+ </dd>
+ </dl>
+
+ <h3>Security FAQ</h3>
+
+ <dl>
+ <dt><a id="protect" name="protect">Q: What steps do you take to protect my data?</a></dt>
+
+ <dd>
+ <p>A: SourceCast take appropriate steps to protect the information you share with us from unauthorized access or disclosure.</p>
+
+ <p>In addition to sharing <!-- --> CollabNet developer site user ID/password authentication, SourceCast implements SSL security with a digital certificate. All pages in SourceCast are https secured through SSL encryption to protect any information in those pages and to authenticate that user information is sent to the correct server. Any CVS password information contained in user profiles for SourceCast is also encrypted to secure project information against unauthorized access.</p>
+ </dd>
+ </dl>
+
+ <p>For more information, see this site's <a href="/nonav/docs/DomainPrivacyPolicy.html">Privacy Policy</a> and <a href="/nonav/docs/TermsOfUse.html">Terms of Use</a>.</p>
+
+ <div class="courtesylinks">
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+