Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMembershipRequest.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMembershipRequest.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMembershipRequest.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,63 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + + +<title>Joining a project</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">Joining a project</span> + +<span class="PlainText"> +<ul> +<dl> +<dt><a href="Learning.html">Learning about projects</a> + <dd><a href="ProjectHomeView.html">Viewing project details</a> + <dd><a href="Subscribing.html">About subscribing to mailing lists</a> + <dd><b>You are here: Joining a project</b> + <dd><a href="ProjectRoles.html">Learning about project roles</a> +<dt><a href="/servlets/HelpTOC">Back to main Help index</a> +</dl> +</ul> +<p> + +<hr noshade size=1> +<p>To request membership in a project, click <i>Join This Project</i> on the far right side of the screen in the <b>Project Home</b> page, which takes you to the <b>Project Membership Request</b> page. (If you are already a member of that project, the link changes to reflect your status.) The radio buttons in the middle of the page present you with several role options. To select a project role, click on the radio button to the left of the desired role and click on the <b>Submit Request</b> button at the end of the list of roles. </p> + + <p> Think of the roles as a method of informing the project owner of how you intend to contribute. You may request, or even be asked, to fulfill more than one role at some point, and you can certainly fulfill other roles on different projects. See more about <a href="ProjectRoles.html">project roles</a>. +</p> +<p>Depending on the project's configuration, you will receive an email from the project owner approving or disapproving your project membership. Upon being approved, you will also receive more information about the nature of the particular module you will be working on.</p> + +<p>Once you are a project member and your involvement progresses, you may wish to change your role in a project. The Project Home page includes a <i>Request New Project Role</i> link in the top right corner of the same page you originally used to request membership originally in the project. Now, however, your current role is noted in the top section, and only the remaining roles available to you are displayed with radio buttons. Again, you submit this change as a request that the project owner must approve.</p> + +<p>As a project member, you are able to work with the full set of hosted tools. These include signing up for tasks, reporting issues using IssueZilla, and obtaining project source code using CVS.</p> +<p> + +<hr noshade size=1> +<a href="/servlets/HelpTOC">Back to main Help index</a></p> + +</span> + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMembershipRequest.html.en ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMembershipRequest.html.en (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMembershipRequest.html.en Sat Apr 8 23:00:09 2017 @@ -0,0 +1,64 @@ +<!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>Joining a project</title> + </head> + + <body class="docs" onload="self.focus()"> + <div class="docs" id="projectmembershiprequest"> + <h2>Joining a project</h2> + + <div id="toc"> + <ul> + <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li> + </ul> + + <ul> + <li> + <a href="/nonav/docs/Learning.html">Learning about projects</a> + + <ul> + <li><a href="/nonav/docs/ProjectHomeView.html">Viewing project details</a></li> + + <li><a href="/nonav/docs/ProjectMail.html#mailsubscribe">About subscribing to mailing lists</a></li> + + <li>Joining a project</li> + + <li><a href="/nonav/docs/ProjectRoles.html">Learning about project roles</a></li> + </ul> + </li> + + <li><a href="/nonav/docs/ProjectMemberResources.html">Project resource for members</a></li> + + <li><a href="/nonav/docs/hostedtools.html">Hosted tools</a></li> + + <li><a href="/nonav/docs/ProjectAdd.html">Creating a new project</a></li> + </ul> + </div> + + <p>To request membership in a project, click the <i>Join This Project</i> link on the <b>Project Home</b> page, which takes you to the <b>Project Membership Request</b> page. Users who are not logged into the domain, do not have permission to join the project or are already members of the project will not see this link. The radio buttons in the middle of the page present you with several role options. To select a project role, click on the radio button to the left of the desired role and click on the <b>Submit Request</b> button at the end of the list of roles.</p> + + <p>Think of the roles as a method of informing the project owner of how you intend to contribute. You may request, or even be asked, to fulfill more than one role at some point, and you can certainly fulfill other roles on different projects. See more about <a href="/nonav/docs/ProjectRoles.html">project roles</a>.</p> + + <p>Depending on the project's configuration, you will receive an email from the project owner approving or disapproving your project membership. Upon being approved, you will also receive more information about the nature of the particular module you will be working on.</p> + + <p>Once you are a project member and your involvement progresses, you may wish to change your role in a project. The Project Home page includes a <i>Request New Project Role</i> link in the top right corner of the same page you originally used to request membership originally in the project. Now, however, your current role is noted in the top section, and only the remaining roles available to you are displayed with radio buttons. Again, you submit this change as a request that the project owner must approve.</p> + + <p>As a project member, you are able to work with the full set of hosted tools. These include signing up for tasks, reporting issues using IssueZilla, and obtaining project source code using CVS.</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/ProjectMembershipRequestHelp.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMembershipRequestHelp.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectMembershipRequestHelp.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,51 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +<!-- Help Text Box --> +<TABLE BORDER="0" CELLSPACING="0" CELLPADDING="3" BORDER="0" WIDTH="100%"> + <TR> + <TD CLASS="HelpText" BGCOLOR="#ffcc66"><IMG SRC="/branding/images/pixel.gif" HEIGHT="1" WIDTH="135"><BR> +<b>How do I...?</b></TD> + </TR> + <TR> + <TD BGCOLOR="#ffffcc"> + + <TABLE BORDER="0" CELLSPACING="0" CELLPADDING="0" BORDER="0" WIDTH="100%"> + <TR> + <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD> + <TD BGCOLOR="#ffffcc" CLASS="HelpText"><a href="/project/www/docs/ProjectRoles.html">What do these roles mean?</a></TD> + </TR> + <TR> + <TD BGCOLOR="#ffffcc" WIDTH="2"><SPACER TYPE="block" WIDTH="2"></TD> + <TD BGCOLOR="#ffffcc" HEIGHT="2"><SPACER TYPE="block" HEIGHT="2"></TD> + </TR> + </TABLE> + + </TD> + </TR> +</TABLE> + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNews.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNews.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNews.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,73 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + + +<TITLE>Project Resources for Project Members</TITLE> + + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + + +<P> +<SPAN CLASS="Header"><B>Project News</B></SPAN> +<P> +<SPAN CLASS="PlainText"><B>Project resources for members: Index</B> +<P> + <UL><DL> + <DT><A HREF="ProjectMemberResources.html">Project resources for members</A></DT> + <DD><A HREF="ProjectHome.html">Project Home Page</A> + <DD><B>You are here: Project News + <UL> + <LI><A HREF="#viewnews">Viewing posted articles</A> + <LI><A HREF="#addnews">Adding articles</A> + </UL></b> + <DD><A HREF="ProjectDownload.html">Project Download</A> + <DD><A HREF="ProjectMemberList.html">Project Members</A> + <DD><A HREF="ProjectMail.html">Project Mailing Lists</A> + <dd><a href="ProjectDocuments.html">Project Documentation</a> + <DD><A HREF="ProjectSource.html">Project Source Code</A> + <DD><A HREF="ProjectIssues.html">Project Issues</A> + <DT><A HREF="/servlets/HelpTOC">Back to main Help index</A> + </DL> +</UL> +<P> +<HR NOSHADE SIZE=1> +<A NAME="viewnews"></A><SPAN CLASS="InputHeader">Viewing posted articles</SPAN> +<P>The <B>Project News</B> page provides a space for those announcements, milestones, and articles that relate to a specific hosted project. These "news" items are arranged according to date and have been selected by the project owner or whomever she has delegated to that role. Depending on the preferences of the project owner, the items will be represented either as links to the actual articles or as links plus a short synopsis of the article. + +<P>If you would like to see the full article of any news item, simply click on the underlined link. You should be taken immediately to the article. If you are not, it is possible that the source site has discontinued the article. In this case, you should let the project owner know. +<P>Not all articles featured on this page are necessarily previously published news items. Some might be announcements, white papers, or any other document that can be considered "news" and which the project owner has deemed important to place here and consequently available to all those interested in the project. Depending on how the project owner has constructed these pages, there might be an archive of older articles. + +<P>Note: A link posted to a published article does not constitute ownership. If you wish to distribute the article on your own, you must negotiate with the copyright owner. +<P> + +<HR NOSHADE SIZE=1> +<A NAME="addnews"></A><SPAN CLASS="InputHeader">Adding articles</SPAN> +<P>Generally, the only one who can add articles to the news page is the project owner and those to whom she has delegated that responsibility. If your project role includes the ability to add news articles, please read the <A HREF="ProjectOwnersNews.html">discussion</A> of how to add news items. +<P>If your project role does not, however, include adding news articles, and you happen to come across an article that you think would be particularly apropos for the project. The easiest way to have it added to the project news site would be to send its URL and a description to the project owner, who can then choose whether to include it or not. + + +<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/ProjectNews.html.en ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNews.html.en (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNews.html.en Sat Apr 8 23:00:09 2017 @@ -0,0 +1,85 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" +"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd";> + +<html xmlns="http://www.w3.org/1999/xhtml";> + <head> +<style type="text/css"> +/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */ +</style> + <script src="/branding/scripts/sc.js" type="text/javascript"></script> + <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" /> + + <title>Project news</title> + </head> + + <body class="docs" onload="self.focus()"> + <div class="docs" id="projectnews"> + <h2>Project News</h2> + + <div id="toc"> + <ul> + <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li> + </ul> + + <ul> + <li><a href="/nonav/docs/Learning.html">Learning about projects</a></li> + + <li> + <a href="/nonav/docs/ProjectMemberResources.html">Project resources for members</a> + + <ul> + <li><a href="/nonav/docs/ProjectHome.html">Project Home Page</a></li> + + <li> + Project News + + <ul> + <li><a href="#viewnews">Viewing posted articles</a></li> + + <li><a href="#addnews">Adding articles</a></li> + </ul> + </li> + + <li><a href="/nonav/docs/ProjectMemberList.html">Project Members</a></li> + + <li><a href="/nonav/docs/ProjectMail.html">Project Mailing Lists</a></li> + + <li><a href="/nonav/docs/ProjectDocuments.html">Project Documentation</a></li> + + <li><a href="/nonav/docs/ProjectSource.html">Project Source Code</a></li> + + <li><a href="/nonav/docs/ProjectIssues.html">Project Issues</a></li> + </ul> + </li> + + <li><a href="/nonav/docs/hostedtools.html">Hosted tools</a></li> + + <li><a href="/nonav/docs/ProjectAdd.html">Creating a new project</a></li> + </ul> + </div> + + <h3><a id="viewnews" name="viewnews">Viewing posted articles</a></h3> + + <p>The <b>Project News</b> page provides a space for those announcements, milestones, and articles that relate to a specific hosted project. These "news" items are arranged according to date and have been selected by the project owner or whomever she has delegated to that role. Depending on the preferences of the project owner, the items will be represented either as links to the actual articles or as links plus a short synopsis of the article.</p> + + <p>If you would like to see the full article of any news item, simply click on the underlined link. You should be taken immediately to the article. If you are not, it is possible that the source site has discontinued the article. In this case, you should let the project owner know.</p> + + <p>Not all articles featured on this page are necessarily previously published news items. Some might be announcements, white papers, or any other document that can be considered "news" and which the project owner has deemed important to place here and consequently available to all those interested in the project. Depending on how the project owner has constructed these pages, there might be an archive of older articles.</p> + + <p>Note: A link posted to a published article does not constitute ownership. If you wish to distribute the article on your own, you must negotiate with the copyright owner.</p> + + <h3><a id="addnews" name="addnews">Adding articles</a></h3> + + <p>Generally, the only one who can add articles to the news page is the project owner and those to whom she has delegated that responsibility. If your project role includes the ability to add news articles, please read the <a href="/nonav/docs/ProjectOwnerNews.html">discussion</a> of how to add news items.</p> + + <p>If your project role does not, however, include adding news articles, and you happen to come across an article that you think would be particularly apropos for the project. The easiest way to have it added to the project news site would be to send its URL and a description to the project owner, who can then choose whether to include it or not.</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/ProjectNewsAddAdvancedHelp.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsAddAdvancedHelp.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsAddAdvancedHelp.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,43 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +<div id="helptext"> + <table border="0" cellspacing="0" cellpadding="3" width="100%"> + <tr> + <th>How do I...?</th> + </tr> + <tr> + <td> + <div> <a href="/project/www/docs/print.html">Print this page</a>...</div> + <div></div> + </td> + </tr> + </table> +</div> + + + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsAddHelp.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsAddHelp.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsAddHelp.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,63 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +<!-- Help Text Box --> +<table border="0" cellspacing="0" cellpadding="3" border="0" width="100%"> + <tr> + <td class="HelpText" bgcolor="#ffcc66"><img src="/branding/images/pixel.gif" height="1" width="135"><br><b>How do I...?</b></td> + </tr> + <tr> + <td bgcolor="#ffffcc"> + + <table border="0" cellspacing="0" cellpadding="0" border="0" width="100%"> + <tr> + <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td> + <td bgcolor="#ffffcc" class="HelpText"><a href="/project/www/docs/ProjectOwnerNews.html">Know what kind of news to add...</a></td> + </tr> + <tr> + <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td> <td bgcolor="#ffffcc" height="2"><spacer type="block" height="2"></td> + </tr> + <tr> + <td bgcolor="#ffcc66" width="2"><spacer type="block" width="2"></td> <td bgcolor="#ffcc66" height="1"><spacer type="block" height="1"></td> + </tr> + <tr> + <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td> <td bgcolor="#ffffcc" height="2"><spacer type="block" height="2"></td> + </tr> + <tr> + <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td> + <td bgcolor="#ffffcc" class="HelpText"><a href="/project/www/docs/ProjectOwnerNews.html#situating">Learn more about publishing project news...</a></td> + </tr> + <tr> + <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td> + <td bgcolor="#ffffcc" height="2"><spacer type="block" height="2"></td> + </tr> + </table> + + </td> + </tr> +</table> + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsApprovalHelp.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsApprovalHelp.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsApprovalHelp.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,43 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +<div id="helptext"> + <table border="0" cellspacing="0" cellpadding="3" width="100%"> + <tr> + <th>How do I...?</th> + </tr> + <tr> + <td> + <div> <a href="/project/www/docs/print.html">Print this page</a>...</div> + <div></div> + </td> + </tr> + </table> +</div> + + + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsDeleteHelp.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsDeleteHelp.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsDeleteHelp.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,43 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +<div id="helptext"> + <table border="0" cellspacing="0" cellpadding="3" width="100%"> + <tr> + <th>How do I...?</th> + </tr> + <tr> + <td> + <div> <a href="/project/www/docs/print.html">Print this page</a>...</div> + <div></div> + </td> + </tr> + </table> +</div> + + + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsEditAdvancedHelp.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsEditAdvancedHelp.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsEditAdvancedHelp.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,43 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +<div id="helptext"> + <table border="0" cellspacing="0" cellpadding="3" width="100%"> + <tr> + <th>How do I...?</th> + </tr> + <tr> + <td> + <div> <a href="/project/www/docs/print.html">Print this page</a>...</div> + <div></div> + </td> + </tr> + </table> +</div> + + + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsEditHelp.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsEditHelp.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsEditHelp.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,43 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +<div id="helptext"> + <table border="0" cellspacing="0" cellpadding="3" width="100%"> + <tr> + <th>How do I...?</th> + </tr> + <tr> + <td> + <div> <a href="/project/www/docs/print.html">Print this page</a>...</div> + <div></div> + </td> + </tr> + </table> +</div> + + + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsListHelp.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsListHelp.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsListHelp.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,63 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +<!-- Help Text Box --> +<table border="0" cellspacing="0" cellpadding="3" border="0" width="100%"> + <tr> + <td class="HelpText" bgcolor="#ffcc66"><img src="/branding/images/pixel.gif" height="1" width="135"><br><b>How do I...?</b></td> + </tr> + <tr> + <td bgcolor="#ffffcc"> + + <table border="0" cellspacing="0" cellpadding="0" border="0" width="100%"> + <tr> + <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td> + <td bgcolor="#ffffcc" class="HelpText"><a href="/project/www/docs/ProjectNews.html#viewnews">View news items...</a></td> + </tr> + <tr> + <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td> <td bgcolor="#ffffcc" height="2"><spacer type="block" height="2"></td> + </tr> + <tr> + <td bgcolor="#ffcc66" width="2"><spacer type="block" width="2"></td> <td bgcolor="#ffcc66" height="1"><spacer type="block" height="1"></td> + </tr> + <tr> + <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td> <td bgcolor="#ffffcc" height="2"><spacer type="block" height="2"></td> + </tr> + <tr> + <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td> + <td bgcolor="#ffffcc" class="HelpText"><a href="/project/www/docs/ProjectNews.html#addnews">Add news items...</a></td> + </tr> + <tr> + <td bgcolor="#ffffcc" width="2"><spacer type="block" width="2"></td> + <td bgcolor="#ffffcc" height="2"><spacer type="block" height="2"></td> + </tr> + </table> + + </td> + </tr> +</table> + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsListTasks.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsListTasks.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectNewsListTasks.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,38 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +Tasks : +<div class="pipelinks"> + #if($acl.hasPermission("Project News - Approve", $currentProject)) + #set($addVerb="Add") + #elseif($acl.hasPermission("Project News - Suggest", $currentProject)) + #set($addVerb="Suggest") + #end + <a href="$currentProject.getProjectPageURL("ProjectNewsAdd")">$addVerb + a News Item</a> +</div> + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerAdmin.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerAdmin.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerAdmin.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,131 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + + +<title>Project Owner Administration</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" nowrap>Project owner administration</span> +<p> +<span class="PLAINTEXT"><b>Project help for project owner administration: Index</b> +<p> + +<ul> +<dl> +<dt><b>You are here: Project owner administration</b> +<ul> +<li><a href="#aboutprojadmin"><b>About project administration on this site</b></a></li> +<li><a href="#projmgmtguidelines"><b>Project management and leadership guidelines</b></a></li> +</ul> +<dd><a href="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a> +<dd><a href="ProjectOwnerNews.html">Managing project site news</a> +<dd><a href="ProjectOwnerFiles.html">Managing project files</a> +<dd><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a> +<dd><a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a> +<dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a> +<dd><a href="ProjectOwnerSource.html">Managing project source code</a> +<dd><a href="ProjectOwnerIssues.html">Tracking project issues</a> +<dt><a href="/servlets/HelpTOC">Back to the main Help index</a> +</dl> +</ul> + +<hr noshade size=1> +<a name="aboutprojadmin"><span class="InputHeader">About project administration on this site</span> +<p> +As a Project Owner with one or more development projects +hosted on this site, your administrative tasks are organized around the same +project pages viewed by other project members or registered users. You access +these same project pages as any project member or registered user, +however, your page view may include additional administrative links and +options. Your Project Resources toolbar also includes an additional +<i>Admin </i> link enabling you to edit your project home page and appearance throughout the site. +<p> + If your project's approval is pending, you still have access to most features and tools to help you get established and set up. Because the hosted tools for projects are automatically configured upon project creation, you may: +<ul> +<li>invite additional developer participants +<li>update your project's home page +<li>publish project news +<li>upload project files and documents +<li>post to your project's mailing lists +<li>create subdirectories in your project's CVS repository +<li>check in source code +<li>use the issue tracker to enter and search project + issues.</li> +</ul> +<p>While still in a pending approval status you cannot perform the following tasks:</p> +<ul><p><li>add project members +<li>approve project membership requests + <li>grant project roles. </li> + </ul> +<p></p> + +<hr noshade size=1> +<a name="projmgmtguidelines"><span class="InputHeader">Project management and leadership guidelines</span> +<p> +The help documents in this section cover this site's administrative functions available to you as a Project Owner. How you use this functionality to structure and lead your project toward achieving particular goals remains largely in your purview. Whenever possible, these help documents suggest the implications of administrative options with respect to project leadership and management. +<p> +Project type will strongly influence the method in which you manage projects. If your project is a proprietary endeavor with commercial licensing, project governance may be largely determined by external factors, for example: corporate strategy, fiscal priorities, organizational structure, and established development methods. While many collaborative development practices can be successfully adopted within this framework, final decision making authority rests with the license holder and influences the development schedule and project goals to a high degree. +<p> +If your project is under open source licensing, the development culture is intrinsically different and far more self determinant. The Project owner -- equipped with some knowledge and understanding of open source practices -- is responsible for establishing and communicating the project's parameters up front. As the project progresses, the project owner will need to nurture project participants toward an increasing sense of community and ownership. +<p> +A third possibility is a combination of the above, that is, you are leading an open source project with the involvement and support of a corporate entity embracing open source to achieve certain business goals. In these circumstances, as the project owner you essentially function as the liaison between two cultures. +<p> +Whichever scenario applies, answering the +questions below will help you to communicate the fundamental purpose and structure of the project to members and potential participants. While these questions are geared towards open source projects, most can be applied to collaborative and proprietary projects as well. Consider the following: +<p> +<ul> +<li>What is the ultimate mission of the project? +<p></p> +<li>What decision making and conflict resolution methodology will be used for the project(for example, voting, consensus building, or final authority)? +<p></p> +<li>What coding standards will be used for the project (for example, adherence to certain conventions and/or emphasis on particular architectural characteristics)? +<p></p> +<li>What methods will be used to help project + members gain responsibility and ownership within the project (for example, how can developers' roles evolve to earn more privileges such as becoming module leaders)? +<p></p> +<li>What are the terms for accepting contributions (for + example, as defined by the licensing, but also how are non-member ideas or + bug-fixes dealt with)?</li> +</ul> +<p> +To learn more about managing collaborative development in +commercial development, see the following +<a href="http://navigation.helper.realnames.com/framer/1/1/default.asp?realname=Information+Week&url=http%3A%2F%2Fwww%2Einformationweek%2Ecom&frameid=1&providerid=1&uid=30013699"; target="_new">"The Customer as Co-Developer"</a>, by Christopher Locke in +InformationWeek (PDF).</p><a +href="http://navigation.helper.realnames.com/framer/1/1/default.asp?realname=Information+Week&url=http%3A%2F%2Fwww%2Einformationweek%2Ecom&frameid=1&providerid=1&uid=30013699"; target="_new"></a> +<p> +To learn more about leading open source development +efforts see<a +href="http://sern.ucalgary.ca/%7Emaurer/ICSE99WS/Submissions/Cubranic/Cubranic.html"; target="_new">"Open-Source +Software Development"</a>, by Davor Cubranic, University of British +Columbia.<br> +<p> + +<hr noshade size=1> +<a href="/servlets/HelpTOC">Back to main Help index</a></p> +</span> + + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerAdmin.html.en ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerAdmin.html.en (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerAdmin.html.en Sat Apr 8 23:00:09 2017 @@ -0,0 +1,123 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" +"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd";> + +<html xmlns="http://www.w3.org/1999/xhtml";> + <head> +<style type="text/css"> +/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */ +</style> + <script src="/branding/scripts/sc.js" type="text/javascript"></script> + <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" /> + + <title>Project owner administration</title> + </head> + + <body class="docs" onload="self.focus()"> + <div class="docs" id="projectowneradmin"> + <h2>Project owner administration</h2> + + <div id="toc"> + <ul> + <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li> + </ul> + + <ul> + <li> + Project owner administration + <ul> + <ul> + <li><a href="#aboutprojadmin">About project administration on this site</a></li> + + <li><a href="#projmgmtguidelines">Project management and leadership guidelines</a></li> + </ul> + </ul> + <ul> + <li><a href="/nonav/docs/ProjectOwnerEdit.html">Editing and maintaining + the Project Home page</a></li> + <li><a href="/nonav/docs/ProjectOwnerNews.html">Managing project site + news</a></li> + <li><a href="/nonav/docs/ProjectOwnerMembers.html">Adding project members + and approving roles</a></li> + <li><a href="/nonav/docs/ProjectOwnerMailingLists.html">Managing project + mailing lists</a></li> + <li><a href="/nonav/docs/ProjectOwnerDocuments.html">Managing project + documentation</a></li> + <li><a href="/nonav/docs/ProjectOwnerSource.html">Managing project source + code</a></li> + <li><a href="/nonav/docs/ProjectOwnerIssues.html">Tracking and managing + project issues</a></li> + <li><a href="/nonav/docs/ProjectOwnerCustomStyle.html">Managing custom HTML styling</a></li> + </ul> + </ul> + </div> + + <h3><a id="aboutprojadmin" name="aboutprojadmin">About project administration on this site</a></h3> + + <p>As a Project Owner with one or more development projects hosted on this site, your administrative tasks are organized around the same project pages viewed by other project members or registered users. You access these same project pages as any project member or registered user, however, your page view may include additional administrative links and options. A link to <strong>Edit this project</strong> appears in the project task space below the project home title, enabling you to edit your project home page and appearance throughout the site.</p> + + <p>If your project's approval is pending, you still have access to most features and tools to help you get established and set up. Because the hosted tools for projects are automatically configured upon project creation, you may:</p> + + <ul> + <li>invite additional developer participants</li> + + <li>update your project's home page</li> + + <li>publish project news</li> + + <li>upload project files and documents</li> + + <li>post to your project's mailing lists</li> + + <li>create subdirectories in your project's CVS repository</li> + + <li>check in source code</li> + + <li>use the issue tracker to enter and search project issues.</li> + </ul> + + <p>While still in a pending approval status you cannot perform the following tasks:</p> + + <ul> + <li>add project members</li> + + <li>approve project membership requests</li> + + <li>grant project roles.</li> + </ul> + + <h3><a id="projmgmtguidelines" name="projmgmtguidelines">Project management and leadership guidelines</a></h3> + + <p>The help documents in this section cover this site's administrative functions available to you as a Project Owner. How you use this functionality to structure and lead your project toward achieving particular goals remains largely in your purview. Whenever possible, these help documents suggest the implications of administrative options with respect to project leadership and management.</p> + + <p>Project type will strongly influence the method in which you manage projects. If your project is a proprietary endeavor with commercial licensing, project governance may be largely determined by external factors, for example: corporate strategy, fiscal priorities, organizational structure, and established development methods. While many collaborative development practices can be successfully adopted within this framework, final decision making authority rests with the license holder and influences the development schedule and project goals to a high degree.</p> + + <p>If your project is under open source licensing, the development culture is intrinsically different and far more self determinant. The Project owner -- equipped with some knowledge and understanding of open source practices -- is responsible for establishing and communicating the project's parameters up front. As the project progresses, the project owner will need to nurture project participants toward an increasing sense of community and ownership.</p> + + <p>A third possibility is a combination of the above, that is, you are leading an open source project with the involvement and support of a corporate entity embracing open source to achieve certain business goals. In these circumstances, as the project owner you essentially function as the liaison between two cultures.</p> + + <p>Whichever scenario applies, answering the questions below will help you to communicate the fundamental purpose and structure of the project to members and potential participants. While these questions are geared towards open source projects, most can be applied to collaborative and proprietary projects as well. Consider the following:</p> + + <ul> + <li>What is the ultimate mission of the project?</li> + + <li>What decision making and conflict resolution methodology will be used for the project(for example, voting, consensus building, or final authority)?</li> + + <li>What coding standards will be used for the project (for example, adherence to certain conventions and/or emphasis on particular architectural characteristics)?</li> + + <li>What methods will be used to help project members gain responsibility and ownership within the project (for example, how can developers' roles evolve to earn more privileges such as becoming module leaders)?</li> + + <li>What are the terms for accepting contributions (for example, as defined by the licensing, but also how are non-member ideas or bug-fixes dealt with)?</li> + </ul> + + <p>To learn more about managing collaborative development in commercial development, see the following <a href="http://www.informationweek.com/816/16uwcl.htm";>"The Customer as Co-Developer"</a>, by Christopher Locke in InformationWeek.</p> + + <p>To learn more about leading open source development efforts see<a href="http://sern.ucalgary.ca/%7Emaurer/ICSE99WS/Submissions/Cubranic/Cubranic.html";>"Open-Source Software Development"</a>, by Davor Cubranic, University of British Columbia.</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/ProjectOwnerCustomStyle.html.en ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerCustomStyle.html.en (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerCustomStyle.html.en Sat Apr 8 23:00:09 2017 @@ -0,0 +1,181 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" +"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd";> + +<html xmlns="http://www.w3.org/1999/xhtml";> + <head> +<style type="text/css"> +/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */ +</style> + <script src="/branding/scripts/sc.js" type="text/javascript"></script> + <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" /> + + <title>Managing custom HTML styling</title> + </head> + + +<body class="docs" bgcolor="#FFFFFF"><div class="docs" id="projectownercustomstyle"> +<h2>Managing custom HTML styling</h2> + <div id="toc"> + <ul> + <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li> + </ul> + + <ul> + <li><a href="/nonav/docs/ProjectOwnerAdmin.html">Project owner administration + </a> + <ul> + <li><a href="/nonav/docs/ProjectOwnerAdmin.html#aboutprojadmin">About + project administration on this site</a></li> + <li><a href="/nonav/docs/ProjectOwnerAdmin.html#projmgmtguidelines">Project + management and leadership guidelines</a></li> + </ul> + <li><a href="/nonav/docs/ProjectOwnerEdit.html">Editing and maintaining + the Project Home page</a></li> + <li><a href="/nonav/docs/ProjectOwnerNews.html">Managing project site news</a></li> + <li><a href="/nonav/docs/ProjectOwnerMembers.html">Adding project members + and approving roles</a></li> + <li><a href="/nonav/docs/ProjectOwnerMailingLists.html">Managing project + mailing lists</a></li> + <li><a href="/nonav/docs/ProjectOwnerDocuments.html">Managing project documentation</a></li> + <li><a href="/nonav/docs/ProjectOwnerSource.html">Managing project source + code</a></li> + <li><a href="/nonav/docs/ProjectOwnerIssues.html">Tracking and managing + project issues</a></li> + <li><a href="/nonav/docs/ProjectOwnerCustomStyle.html">Managing custom HTML + styling</a></li> + </ul> + </div> + + <h3>About customizing HTML</h3> + <p>This site provides several opportunities for users to add HTML content to + screens. For instance, the Community, Project home, and My start pages might + include custom HTML content.</p> +<p>Custom HTML generally inherits the styling from the page's Cascading Style +Sheet (CSS) files. Styles and formatting defined in the style sheet will apply +also to user-supplied content, adding to or possibly overriding any formatting +specified in it. For instance, the stylesheet might specify that table heading +(th) content is to be aligned left. Table headings in user-supplied HTML that +appear center-aligned before inclusion will automatically be left-aligned after +inclusion. Similarly, the fonts and colors will match that of other HTML +appearing in the same page.</p> +<p>In most cases, this is desirable for the sake of consistency and ease of HTML +authoring; however, if it is not, you can use the tips that follow to help +eliminate unwanted styling differences.</p> +<h3>If the desired CSS styles do not apply...</h3> +<p>To make user-supplied HTML more consistent with SourceCast formatting, try to +remove the formatting-related elements and attributes from the included HTML. +For instance, remove all font tags, style, bgcolor, and align attributes, and +use structural HTML elements like headings (e.g., h3), paragraphs, and list +constructs instead of breaks (br), images of text, tables for layout, spacer +images, and so on.</p> +<p>The most likely cause for SourceCast style application failure is that the +HTML fails to identify the structural significance of the text, instead +describing its desired appearance. To remedy, convert this sort of HTML:</p><pre><code><font size="4" face="Arial, Helvetica"> + <b> + Welcome to project foo! + </b> +<Br> +<img src="../images/spacer.gif" height="1" width="1" vspace="4" alt=""> + <font size="2"> + This is only a picture of a paragraph. + </font> +</font> +<Br> +<Br></code></pre> +<p>...to this: </p><pre><code><h3> + Welcome to project foo! +</h3> +<p> + This is a real paragraph. +</p></code></pre> +<p>Note that the HTML best suited for application of CSS is also the simplest to +write and edit by hand, and results in smaller (faster) files. Furthermore, it +tends to remain accessible when rendered outside the context of a desktop PC, +such as WebTV or a hand-held browsing device. </p> + <p>A useful tool for automating cleanup of HTML produced by software such as + MS Office, FrontPage, or Netscape 4.x Composer is <a +href="http://www.w3.org/People/Raggett/tidy/";>HTML Tidy</a>. A suggested configuration + file for Tidy appears in <a +href="https://www.extranet.collab.net/files/documents/177/166/scast121_external_releasenotes.html#tidy";>HTML + Tidy Configuration</a> below.</p> +<h3>If SourceCast styles are overriding desired custom styling...</h3> +<p>To preserve custom styling in user-supplied HTML, use inline CSS; i.e., +HTML's <code>style</code> attribute instead of the various style-related +attributes and elements such as <code>FONT</code>, <code>bgcolor</code>, +<code>align</code>, or <code>valign</code> that CSS superseded in 1996.</p> +<p>For instance, the following HTML may not render with the intended styling in +the context of a SourceCast screen: </p><pre><code><h2 align="center"> + <font face="Times" color="#cc0000"> + Welcome to project foo! + </font> +</h2></code></pre> +<p>To preserve such styling, the various formatting properties should be +expressed using CSS: </p><pre><code><h2 style="text-align:center; font-family:Times; color:#c00"> + Welcome to project foo! +</h2></code></pre> +<p>This inline CSS will override any conflicting styling provided by the +SourceCast stylesheet. To learn more about CSS usage, check the following +sources:</p> +<ul> + <li><a href="http://www.htmlhelp.com/reference/css/";>Guide to Cascading Style + Sheets</a> (tutorial) + <li><a href="http://www.w3.org/TR/REC-CSS2";>Cascading Style Sheets, Level + 2</a> (official specification) </li></ul> +<p>More complex or extensive style customization may call for appendices to the +SourceCast stylesheets themselves and requires a deeper understanding of CSS in +SourceCast than this document aims to provide. Please provide feedback to +CollabNet about your expectations in this area. </p> +<h3><a name=tidy></a>HTML Tidy configuration</h3> +<p>The following is a suggested configuration file for <a +href="http://www.w3.org/People/Raggett/tidy/";>HTML Tidy</a>. This utility will +clean up many HTML syntax and usage problems that can lead to unexpected results +with SourceCast in various browser/platform contexts. For best results, use Tidy +on all HTML you intend to integrate into SourceCast screens. </p><pre><code>tidy-mark: no +markup: yes +wrap: 0 +wrap-attributes: no +wrap-script-literals: no +wrap-asp: yes +wrap-jste: yes +wrap-php: yes +literal-attributes: no +tab-size: 1 +indent: auto +indent-spaces: 1 +indent-attributes: no +hide-endtags: no +input-xml: no +output-xml: yes +add-xml-pi: no +add-xml-decl: no +output-xhtml: no +doctype: auto +char-encoding: ascii +numeric-entities: yes +quote-marks: no +quote-nbsp: yes +quote-ampersand: yes +assume-xml-procins: no +fix-backslash: yes +break-before-br: no +uppercase-tags: no +uppercase-attributes: no +word-2000: yes +clean: yes +logical-emphasis: no +drop-empty-paras: yes +drop-font-tags: yes +enclose-text: yes +enclose-block-text: no +fix-bad-comments: yes +add-xml-space: no +alt-text: "" +write-back: yes +keep-time: no +show-warnings: no +quiet: yes +gnu-emacs: yes +split: no</code></pre> +</div> +</body> +</html> Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerDocuments.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerDocuments.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerDocuments.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,103 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + + +<title>Managing project documentation</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">Managing project documentation</span> +<p> +<span class="PlainText"><b>Project help for project owner administration: Index</b> +<p> + +<ul> +<dl> +<dt><a href="ProjectOwnerAdmin.html">Project owner administration</a> + <dd><a href="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a> + <dd><a href="ProjectOwnerNews.html">Managing project site news</a> + <dd><a href="ProjectOwnerFiles.html">Managing project files</a> + <dd><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a> + <dd><a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a> + <dd><b>You are here: Managing project documentation + <ul> + <li><a href="#aboutdocs">About your project documentation</a> + <li><a href="#adddocs">Adding/maintaining documents and sections</a> + <li><a href="#approvedocs">Approving documentation suggestions</a> + </ul></b> + <dd><a href="ProjectOwnerSource.html">Managing project source code</a> + <dd><a href="ProjectOwnerIssues.html">Managing project issues and generating reports</a> +<dt><a href="/servlets/HelpTOC">Back to the main Help index</a> +</dl> +</ul> + +<p> +<hr noshade size=1> +<a name="aboutdocs"></a><span class="InputHeader">About your project documentation</span> + +<p> +Either you or members of your project can make your project's working documents available for viewing and sharing through the <b>Project Documents List</b> page. These can be binary or other file format uploads, URLs, and HTML pages. The documents you include here come under your project's version control. +<p> +Project documentation is meant to be distinct from files available through the <b>Project Files</b> page. Both features let you publish a variety of files and documents, but project documentation is intended to organize works in progress. Project files, on the other hand, should reflect any finished work being made available for download, the results of your project's efforts to date. +<p> + +<hr noshade size=1> +<a name="adddocs"></a><span class="InputHeader">Adding/maintaining documents and sections</span> + +<p> +You can add projects documents by clicking <i>Add New Document</i> link to display the <b>Add Project Document</b> page. Use the input fields in this page to enter the document name that will appear in the <b>Project Documents</b> page, a brief description of the document, then select one of the three document options for submitting document: +<ul> +<li>Locate the file by browsing your local machine directories +<li>Enter the URL for online documents +<li>Cut and paste the document's HTML content directly into a text box. +</ul> +<p> +The maximum size allowed for each uploaded document is 25 MB. Documents larger than this cannot be accepted. If you have a document to add that is larger than 25 MB, consider breaking into two or more smaller files. +<p> +Choose which section the document should be placed in on the Project Documents page or leave the default selection of "none" which places the document at the top level. Finally, click the "Add Document" button. <p> +If you want to create a new section, click the <i>Add New Section</i> link in the top right corner of the <b>Project Documents List</b> page to display the <b>Add a Document Section</b> page. Here you may create a new section, enter a description of it, and designate its place within your project's documentation hierarchy. However, document subsections can only be created two levels deep. +<p> +If you need to update document information, move documents to different sections, or remove documents altogether, use the <i>Edit</i> and <i>Delete</i> links in the <b>Project Documents List</b> page. You may also rearrange the hierarchy of documentation subsections you have created or delete sections altogether. If a subsection you wish to delete contains documents, you can choose to delete everything or move the documents to the top level. +<p> + + + +<hr noshade size=1> +<a name="approvedocs"></a><span class="InputHeader">Approving documentation suggestions</span> + +<p> +Project members can suggest documents and/or new sections for document organization, but these are not added to the <b>Project Documents List</b> page until you give your approval. Project members' view of this page features links to suggest new documents and sections. +<p> +Suggested documents appear in the "Pending Actions" section of your <b>Start Page</b>. Both suggested documents and sections appear in your view of the <b>Project Documents List</b> page. The <i>Pending Approval</i> links adjacent to suggested documents/sections lead to the <b>Project Document Approval</b> page where you can approve, defer, or disapprove each item using the radio buttons. Then click the "Perform Actions" button to complete the task. +<p> +The actions you take as Project Owner in response to suggested documents and sections automatically generate email notifications to the users who suggested the documents, and include instructions for them to contact you directly by email if they have further questions about your action. When you disapprove a suggested document, you are prompted to give the reason for your decision. This reason is included verbatim in the email notification to the user who suggested the document. +<p> +For example, since the maximum document upload size is 25 MB per document, if one of your project members suggests a document that exceeds this limit, you can disapprove the document but also include a suggestion to break the document into smaller pieces to address this. + +<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/ProjectOwnerDocuments.html.en ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerDocuments.html.en (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerDocuments.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>Project File sharing</title> + </head> + + <body class="docs" onload="self.focus()"> + <div class="docs" id="projectownerdocuments"> + <h2>Managing file sharing</h2> + + <div id="toc"> + <ul> + <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li> + </ul> + + <ul> + <li> + <a href="/nonav/docs/ProjectOwnerAdmin.html">Project owner administration</a> + + <ul> + <li><a href="/nonav/docs/ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a></li> + + <li><a href="/nonav/docs/ProjectOwnerNews.html">Managing project site news</a></li> + + <li><a href="/nonav/docs/ProjectOwnerMembers.html">Adding project members and approving roles</a></li> + + <li><a href="/nonav/docs/ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a></li> + + <li> + Managing file sharing + + <ul> + <li><a href="#aboutdocs">About file sharing</a></li> + + <li><a href="#adddocs">Adding/maintaining files and folders</a></li> + + <li><a href="#approvedocs">Approving file suggestions</a></li> + </ul> + </li> + + <li><a href="/nonav/docs/ProjectOwnerSource.html">Managing project source code</a></li> + + + <li><a href="/nonav/docs/ProjectOwnerIssues.html">Managing project issues and generating reports</a></li> + <li><a href="/nonav/docs/ProjectOwnerCustomStyle.html">Managing custom HTML styling</a></li> + + + </ul> + </li> + </ul> + </div> + + <h3><a id="aboutdocs" name="aboutdocs">About your project file sharing</a></h3> + + <p>Either you or members of your project can make your project's files available for viewing and sharing through the <b>File sharing</b> page. These can be binary or other file format uploads, URLs, and HTML pages. The files you include here come under your project's version control.</p> + + <p>Files are organized in folders. Folders are organized in a tree hierarchy; the parent folder at the top, with child folders beneath. The folder hierarchy provides ease of organization of files. Thus, you may have a parent folder entitled "Test Scripts" with child folders "White Box Tests" and "Black Box Tests", each containing files relevant to their folder name.</p> + + <p>The <b>File sharing</b> page displays the folder hierarchy down three levels; you are able to see the level you currently are in as well as it's subfolders and their subfolders. When you select a subfolder it becomes your current top level and you are presented with two levels of child folders beneath. The folder description appears to the right of the folder name, and above the list of files contained within the folder.</p> + + <h3><a id="folders" name="folders"></a>Creating Folders</h3> + + <p>To create a new folder:</p> + + <ol> + <li>From the Project Home page, select the <b>File sharing</b> link from the left navigation bar.</li> + + <li>Select the <b>Suggest a Folder</b> link from the <b>Tasks</b> bar.</li> + + <li>Enter a name in the <i>Folder Name</i> field. The folder name should be short and descriptive of the content expected to be placed in this folder. The <i>Folder Name</i> field will accept up to 125 characters, but you should carefully consider the length of your folder name. If you feel the need to further describe the folder to your end users you can use the <i>Optional Description</i> field to enter a description of the type of content, up to 240 characters in length.</li> + + <li>Click on the <b>Add Folder</b> button.</li> + </ol> + + <h3><a id="adddocs" name="adddocs">Adding/maintaining files and sections</a></h3> + + <p>You can add files by clicking <i>Add New Document</i> from the <b>Tasks</b> bar displays the <b>Add Project Document</b> <b>to Folder</b> page. Use the input fields on this page to describe the file that will appear in this folder. To suggest a file enter the following information:</p> + + <ul> + <li>File Name: this should be a short name for the file and cannot be more than 120 characters in length.</li> + + <li>Status: you must set your status as active or inactive.</li> + + <li>Description (optional): if you find that you would like to further describe the file, use this field to add more information</li> + + <li> + one or more of the following: + + <ul> + <li>File (can be made public):</li> + + <li>URL</li> + + <li>HTML content</li> + </ul> + </li> + </ul> + + <p>Click on the <b>Add a file</b> button.</p> + + <p>If you need to update file information, move files to different folders, or remove files altogether, use the <i>Edit</i> and <i>Delete</i> links in the <b>File sharing</b> page. You may also rearrange the hierarchy of file subsections you have created or delete sections altogether. If a subsection you wish to delete contains files, you can choose to delete everything or move the files to the top level.</p> + + <h3><a id="approvedocs" name="approvedocs">Approving file suggestions</a></h3> + + <p>Project members can suggest files and/or new sections for file organization, but these are not added to the <b>File sharing</b> page until you give your approval. Project members' view of this page features links to suggest new files and sections.</p> + + <p>Suggested files appear in the "Pending Actions" section of your <b>Start Page</b>. Both suggested files and sections appear in your view of the <b>File sharing</b> page. The <i>Pending Approval</i> links adjacent to suggested files/sections lead to the <b>Project Document Approval</b> page where you can approve, defer, or disapprove each item using the radio buttons. Then click the "Perform Actions" button to complete the task.</p> + + <p>The actions you take as Project Owner in response to suggested files and sections automatically generate email notifications to the users who suggested the files, and include instructions for them to contact you directly by email if they have further questions about your action. When you disapprove a suggested file, you are prompted to give the reason for your decision. This reason is included verbatim in the email notification to the user who suggested the file.</p> + + <p>For example, since the maximum file upload size is 25 MB per file, if one of your project members suggests a file that exceeds this limit, you can disapprove the file but also include a suggestion to break the file into smaller pieces to address this.</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/ProjectOwnerEdit.html ============================================================================== --- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerEdit.html (added) +++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerEdit.html Sat Apr 8 23:00:09 2017 @@ -0,0 +1,151 @@ +<!--#include virtual="/doctype.html" --> +<html> +<head> +<link href="/css/ooo.css" rel="stylesheet" type="text/css"> + + +<title>Project Help for Project Owner Administration</title> + + +<!--#include virtual="/google-analytics.js" --> +<!--#include virtual="/scripts/entourage.js" --> +</head> +<body> +<!--#include virtual="/pl/brand.html" --> + <div id="topbara"> + <!--#include virtual="/pl/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +<p> + <span class="Header" nowrap>Editing and maintaining the Project Home page</span> +<p> +<span class="PlainText"><b>Project help for project owner administration: Index</b> +<p> + <ul> +<dl> +<dt><a href="ProjectOwnerAdmin.html">Project owner administration</a> + <dd><strong>You are here: Editing and maintaining the + Project Home page + <ul> + <li><a href="#updatehome">Maintaining project information</a> + <li><a href="#useindex">About the 'Use Project Home Page' option</a> + <li><a href="#ownersmessage">Updating the owner's message</a> + <li><a href="#aboutlists">About configuring project mailing lists</a></li> + <li><a href="#aboutlocking">About project locking</a> + </ul></strong> + <dd><a href="ProjectOwnerNews.html">Managing project site news</a> + <dd><a href="ProjectOwnerFiles.html">Managing project files</a> + <dd><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a> + <dd><a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a> + <dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a> + <dd><a href="ProjectOwnerSource.html">Managing project source code</a> + <dd><a href="ProjectOwnerIssues.html">Tracking project issues</a> +<dt><a href="/servlets/HelpTOC">Back to the main Help index</a></dt> +</dl> +</ul> + +<p> + +<hr noshade size=1> +<a name="updatehome"></a><span class="InputHeader">Maintaining project information</span> +<p> The <strong>Project Home </strong>page is the entry +point for all project users, members as well as potential contributors. The +primary role of the <strong>Project Home </strong> page is to highlight the project's mission, primary goals, current status, and ongoing needs. +<p><strong>NOTE</strong>: +For a good example of summarizing project goals and status, see the open source <a href="http://subversion.tigris.org/"; target="_new">Subversion project home page</a>. +<p> + Project information can be modified through the <b>Administer Projects</b> page, accessed by one of the following methods: +<p> +<ul> +<li>At first login, the home page has + a <strong>My Projects</strong> link as well as + an <strong>Admin</strong> link to the <strong>Project Edit + </strong> page. +<p></p> +<li>Once you are on your <strong>Project Home + </strong>page or other project pages, use the <strong>Admin </strong> link in the Project + Resources tool bar at the top of every screen.</li> +</ul> +<p> +The <strong>Project Home </strong>page has the following +fields which are also part of the project creation process: +<ul><p><li>Project Name + <li>Summary + <li>Description + <li>License + <li>Project Category. +</li></ul> +By clicking on the +<strong>Edit this Project </strong>link you can modify the information in each of these fields. Because the description field accommodates html formatting and graphics, you can use this to customize and add information to your project home page. + +<p>There are several additional fields in the <b>Administer Projects</b> page that do not appear during the project creation process: </p> +<p><ul><li>Message From the Owner(s) + <li>Edit this Project + <li>Request New Project Role + <p></p></li></ul> +<p> + + +<hr noshade size=1> +<a name="useindex"></a><span class="InputHeader">About the 'Use Project Home Page' option</span> +<p> + +Your <b>Project Home</b> page by default displays the content that you entered in the Description field in the <b>Administer Project</b> page. +<p> +Because some projects require more complex home pages, however, you have the option to store and display special home page content from a different file. The "Use Index" flag in the <b>Administer Project</b> page indicates that your project home page should display the contents of the "index.html" file instead of displaying description field information from the database. This file is located in: +<blockquote> +<b>http://yourprojectname.this domain/www/index.html</b> +</blockquote>This +file is part of the project's source code repository under CVS version control. If you check the "Use Index" flag, this means you must update your home page content by editing the index.html file, saving it, and then committing it into CVS to display the newest file revision in your project's home page. When you use the index.html file, you can include HTML formatting, graphics, and other more complex elements for your project's home page. +<p> + +<hr noshade size=1> +<a name="ownersmessage"></a><span class="InputHeader"><b>Updating the owner's message</b></span> + +<p> Initially you use the field to identify yourself as the project owner and convey project goals. As the project progresses, use the Owner's Message to highlight project milestones, list changing requirements, and identify particular resource needs. For example, you may advertise the types of development expertise currently being sought: +<blockquote> + <p> +<i>"Desperately seeking experienced Java servlet developers with a passion for creating apps that will change the world."</i> + </p></blockquote> + <p>Or, you can give updates about the current status of development and what's + coming up next. </p> + + +<p> + However you use this field, your Owner's Message should be updated frequently: usually once a week, but no less than monthly. Fresh messages convey a sense of excitement and momentum; critical perceptions to the growth of development projects. +<p> + +<hr noshade size=1> +<a name="aboutlists"></a><span class="InputHeader"><b>About configuring project mailing lists</b></span> +<p> +The <strong>Project Edit </strong> + page is also the place to administer your project's mailing list. To find out more about this, see <a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a>. +<p> + +<hr noshade size=1> +<a name="aboutlocking"></a><span class="InputHeader">About project locking</span> +<p> +If you have received email notification that your project is locked, you should contact a site administrator immediately for further information. Project locking means that site administrators have temporarily disabled your project. This may be due to site policy matters, technical issues, or other reasons. +<p> +When you load your <b>Project Home</b> or <b>Project Edit</b> page, you encounter the "Locked" flag in red at the top. All site-related project activity is suspended in locked projects. Your project pages can still be accessed and all existing project data is intact, however <b><i>you and your project members temporarily have read-only access</i></b> to the source code repository, email archives, issue database, project files, and documents. No one -- including you -- can commit source code, enter issues, upload or download files and documents, change web content, or subscribe to or modify mailing lists. If your locked project is a public project, other site users can still view your project's home page but the project is flagged as "locked." +<p> +A site administrator must unlock your project to reactivate it. You will receive email notification when this action is taken also. +<p> + +<hr noshade size=1> +<a href="ProjectOwnerAdmin.html">Back to Help for project owner administration</a><br> +<a href="/servlets/HelpTOC">Back to main Help index</a> + +</span> + + </div> +<!--#include virtual="/footer.html" --> +</body> +</html>
