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 [17/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/ProjectOwnerNews.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerNews.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerNews.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,133 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Managing Project Site News</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 site news</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><strong>You are here: Managing project site news
+ <ul>
+ <li><a href="#situating">Arranging the news</a>
+ <li><a href="#makingnews">Making it news</a>
+ <li><a href="#things">Things to keep in mind</a></li>
+ </ul></strong>
+ <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 main Help index</a></dt>
+</dl>
+</ul>
+
+
+<p>
+<hr noshade size=1>
+
+ <b>Managing project site news</b> compliments our discussion of the <a href="ProjectNews.html">Project News page</a> and offers some tips and tricks so that the content developer can easily and efficiently manage news articles for your project site. News encompasses articles, essays, and other items that are relevant to your project, or that you think the community would be interested in. News can also include your own press releases--for instance, project press releases.
+<p>
+
+<hr noshade size=1>
+<a name="situating"></a><span class="InputHeader">Arranging the news</span>
+<p>The News page provides current status to project members as well as curious surfers. This page also places your project the world at large.
+
+<p>The <b>Project News</b> page,
+ and the associated pages, have been designed to simplify and automate many
+ of the mail maintenance processes. To add news, click on the <strong>Add a
+ News Item </strong>link on the upper right of the <b>Project News</b> page.
+ <p>The fields on the <b>Add News Item </b>page have the following functionality:
+ <ul><li><p><strong>Date of event</strong> : To add a date to your news item
+ click on the pull-down menus and select a date.</p>
+ <li>
+ <p><strong>Headline</strong>: Enter a title or headline for your news item. You can
+ use HTML markup tags in this text field.</p>
+ <li>
+ <p><strong>Body</strong>: Add in the text of the news item. HTML markup tags
+ can be used in this text field.</p></li></ul>
+ <p>For example, you want to add an article recently
+ published in a trade journal on an issue relevant to your project. The
+ article, "Widget Kids", was published January 13, 2001, in the "Widget Week"
+ magazine. To create this as a news item first click on the appropriate
+ pull-down menus in the <strong>Date </strong>field to enter the date.
+ Next, enter the article headline, "Widget Kids" in the <strong>Headline
+ </strong> field. Since HTML is permitted here, you can cut and paste the headline as you saw it
+ online. </p>
+<p><strong>NOTE</strong>: Instead of cutting and pasting the article information into the news fields, you can include any level of html complexity. However, as a rule, you should opt for that which can load quickly and surely across a range of browsers and platforms. If the original headline is a graphic, it is a good idea to use the original. <p>
+
+<hr noshade size=1>
+<a name="makingnews"></a><span class="InputHeader">Making it news</span>
+<p>If you choose to add previously published articles, keep in mind that you do not "own" the article. While you can refer to the headline or title, and provide a synopsis that you have written, you must provide the proper compensations to the owner of the copyright.
+<p>One process is to cite the headline, link to it, and then provide, in your own words, an explanatory sentence or paragraph, preferably short. See, for an example of this practice, the news page for <a href="http://www.openoffice.org/news.html" target="_new">OpenOffice.org.</a>
+<p><strong>NOTE</strong> : You do not need to follow the process above for your own work.
+<p>Once you have entered the information on your chosen article, you are ready to "publish" it.
+ <p>There are several options for submitting news:
+<ul>
+<li>By clicking on the<strong> Add News Item
+ </strong>button, you can publish the article immediately
+<li>You can select the <strong>Advanced Options
+ </strong>button to set a future date for publication. This button
+ also allows you to set a date for removing the news item. You can
+ either select to have the news item never be removed or to specify a date for
+ obsolescence.</li>
+</ul>
+
+<hr noshade size=1>
+<a name="things"></a><span class="InputHeader">Things to keep in mind:</span>
+<ul>
+ <li>In the case of the acquired sources, be sure to clearly
+ state where you obtained them. Neglecting to do so may be interpreted as plagiarism.
+<p></p>
+ <li> Save a copy of the article featuring your project as it originally
+ appeared in the publication. Although you will need to acquire the rights to the
+ article before you can put the article up on your project's site, having the
+ article will allow you to create and put up a summary of the article more quickly.
+<p></p>
+ <li>Add new items on a regular
+ basis. A page that has been static a long time suggests a lack of momentum.
+ If you have no news to report, you can make announcements and
+ post them. You might also consider placing news items
+ that, if not directly relevant to your project, relate to issues your community
+ (actual or anticipated) will find interesting.
+<p></p>
+ <li>Be sure to notify community members of recently posted news items. You can efficiently do this using the project's mailing lists.
+</ul>
+
+<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>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerNews.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerNews.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerNews.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,119 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>Managing project site news</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="projectownernews">
+ <h2>Managing project site 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/ProjectOwnerAdmin.html">Project Owner Administration</a>
+ <ul>
+ <li><a href="/nonav/docs/ProjectOwnerEdit.html">Editing and maintaining
+ the Project Home page</a></li>
+ <li> Managing project site news
+ <ul>
+ <li><a href="#situating">Arranging the news</a></li>
+ <li><a href="#makingnews">Making it news</a></li>
+ <li><a href="#things">Things to keep in mind</a></li>
+ </ul>
+ </li>
+ <li><a href="/nonav/docs/ProjectOwnerMembers.html">Adding project members
+ and approving roles</a></li>
+ <li><a href="/nonav/docs/ProjectOwnerMailingLists.html">Configuring
+ and managing project mailing lists</a></li>
+ <li><a href="/nonav/docs/ProjectOwnerDocuments.html">Managing project
+ documentation</a></li>
+ <li><a href="/nonav/docs/ProjectOwnerSource.html">Managing project source
+ code</a></li>
+ <li><a href="/nonav/docs/ProjectOwnerIssues.html">Tracking project issues</a></li>
+ <li><a href="/nonav/docs/ProjectOwnerCustomStyle.html">Managing custom
+ HTML styling</a></li>
+ </ul>
+ </li>
+ </ul>
+ </div>
+
+ <h3>Managing project site news</h3>
+
+ <p>compliments our discussion of the <a href="/nonav/docs/ProjectNews.html">Project News page</a> and offers some tips and tricks so that the content developer can easily and efficiently manage news articles for your project site. News encompasses articles, essays, and other items that are relevant to your project, or that you think the community would be interested in. News can also include your own press releases--for instance, project press releases.</p>
+
+ <h3><a id="situating" name="situating">Arranging the news</a></h3>
+
+ <p>The News page provides current status to project members as well as curious surfers. This page also places your project the world at large.</p>
+
+ <p>The <b>Project News</b> page, and the associated pages, have been designed to simplify and automate many of the mail maintenance processes. To add news, click on the <strong>Add a News Item</strong> link on the upper right of the <b>Project News</b> page.</p>
+
+ <p>The fields on the <b>Add News Item</b> page have the following functionality:</p>
+
+ <ul>
+ <li>
+ <p><strong>Date of event</strong> : To add a date to your news item click on the pull-down menus and select a date.</p>
+ </li>
+
+ <li>
+ <p><strong>Headline</strong>: Enter a title or headline for your news item. You can use HTML markup tags in this text field.</p>
+ </li>
+
+ <li>
+ <p><strong>Body</strong>: Add in the text of the news item. HTML markup tags can be used in this text field.</p>
+ </li>
+ </ul>
+
+ <p>For example, you want to add an article recently published in a trade journal on an issue relevant to your project. The article, "Widget Kids", was published January 13, 2001, in the "Widget Week" magazine. To create this as a news item first click on the appropriate pull-down menus in the <strong>Date</strong> field to enter the date. Next, enter the article headline, "Widget Kids" in the <strong>Headline</strong> field. Since HTML is permitted here, you can cut and paste the headline as you saw it online.</p>
+
+ <p><strong>NOTE</strong>: Instead of cutting and pasting the article information into the news fields, you can include any level of html complexity. However, as a rule, you should opt for that which can load quickly and surely across a range of browsers and platforms. If the original headline is a graphic, it is a good idea to use the original.</p>
+
+ <h3><a id="makingnews" name="makingnews">Making it news</a></h3>
+
+ <p>If you choose to add previously published articles, keep in mind that you do not "own" the article. While you can refer to the headline or title, and provide a synopsis that you have written, you must provide the proper compensations to the owner of the copyright.</p>
+
+ <p>One process is to cite the headline, link to it, and then provide, in your own words, an explanatory sentence or paragraph, preferably short. See, for an example of this practice, the news page for <a href="http://www.openoffice.org/news.html">OpenOffice.org.</a></p>
+
+ <p><strong>NOTE</strong> : You do not need to follow the process above for your own work.</p>
+
+ <p>Once you have entered the information on your chosen article, you are ready to "publish" it.</p>
+
+ <p>There are several options for submitting news:</p>
+
+ <ul>
+ <li>By clicking on the <strong>Add News Item</strong> button, you can publish the article immediately</li>
+
+ <li>You can select the <strong>Advanced Options</strong> button to set a future date for publication. This button also allows you to set a date for removing the news item. You can either select to have the news item never be removed or to specify a date for obsolescence.</li>
+ </ul>
+
+ <h3><a id="things" name="things">Things to keep in mind:</a></h3>
+
+ <ul>
+ <li>In the case of the acquired sources, be sure to clearly state where you obtained them. Neglecting to do so may be interpreted as plagiarism.</li>
+
+ <li>Save a copy of the article featuring your project as it originally appeared in the publication. Although you will need to acquire the rights to the article before you can put the article up on your project's site, having the article will allow you to create and put up a summary of the article more quickly.</li>
+
+ <li>Add new items on a regular basis. A page that has been static a long time suggests a lack of momentum. If you have no news to report, you can make announcements and post them. You might also consider placing news items that, if not directly relevant to your project, relate to issues your community (actual or anticipated) will find interesting.</li>
+
+ <li>Be sure to notify community members of recently posted news items. You can efficiently do this using the project's mailing lists.</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/ProjectOwnerSource.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerSource.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerSource.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,157 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Managing Project Source Code</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 source code</span>
+<p>
+<span class="PlainText"><b>Project help for project owner administration: Index</b>
+<p>
+
+<ul>
+<dl>
+<dt><a href="ProjectOwnerAdmin.html">Project owner administration</a>
+ <dd><a href="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a>
+ <dd><a href="ProjectOwnerNews.html">Managing project site news</a>
+ <dd><a href="ProjectOwnerFiles.html">Managing project files</a>
+ <dd><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a>
+ <dd><a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a>
+ <dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a>
+ <dd><b>You are here: Managing project source code
+ <ul>
+ <li><a href="#gettingstarted">Getting started</a>
+ <li><a href="#siteadmincvs">About CVS repository tasks</a>
+ <li><a href="#considerations">A few initial considerations for project owners</a>
+ <li><a href="#cvspermissions">Managing CVS permissions</a>
+ </ul></b>
+ <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 href="gettingstarted"></a><span class="InputHeader">Getting started</span>
+<p>
+If you are new to CVS, this help guide provides some basic quick reference information for administrative CVS tasks relevant to projects hosted this site. This guide by no means exhaustively documents CVS or the many broader project management issues imputed by versioning control. A wealth of published documentation for CVS exists, both online and in print. The following links lead to general CVS tool documentation elsewhere on this site, and these documents include many authoritative, external CVS resources.
+<p>
+<b>CVS tool documentation</b>
+<dl>
+<dt><a href="ddCVS.html">About CVS version control</a>
+<dt><a href="ddCVS_cvsglossary.html">A version control glossary</a>
+<dt><a href="ddUsingCVS_command-line.html">Using command line CVS</a>
+<dt><a href="ddUsingWinCvs.html">UsingWinCvs</a>
+</dl>
+<p>
+<hr noshade size=1>
+<a name="siteadmincvs"></a><span class="InputHeader">About CVS repository tasks</span>
+<p>
+Much of the administrative work involved with setting up your project's source repository is handled "behind the scenes" when your project gains approval. If you are new to CVS, this means that you do not have to start from scratch to set up the CVS repository for your project.
+<p>
+The following tasks occur automatically:
+<p>
+<ul>
+<li>Your project's basic repository structure is created with a top-level directory that can be expanded upon by adding subdirectories as the project evolves. There is also a "/www" directory created for project web content.
+<p>
+<li>Your project's CVS root (that is, the server where your CVS repository is located) is automatically set to this site's host servers and preconfigured. The instructions in the <b>Project Source</b> page for your project display the exact CVS root needed to log in to the project's source repository. For most projects on this site, the cvsroot will be:
+<p>
+<b>:pserver:username@cvs.projectname.thisdomain:/cvs</b>
+</ul>
+<p>
+For CVS experts, this automation means that the CVS administrative module is preconfigured for projects hosted on this site. That includes the following files, listed here for your information:
+<p>
+<ul>
+<li>Modules file
+<li>Cvswrappers file
+<li>Commit support files
+<li>Commitinfo
+<li>Verifying log messages
+<li>Editinfo
+<li>Loginfo
+<li>Rcsinfo
+<li>Ignoring files via cvsignore
+<li>Checkoutlist file
+<li>History file
+<li>Expansions in administrative files
+<p>
+</ul>
+All CVS repository tasks such as backing up, restoring, moving, or configuring remote repository access are also handled by site administrators. Should your project require editing CVS administrative files or other repository-level actions, you must contact a site administrator for support.
+</ul>
+<p>
+<hr noshade size=1>
+<a name="considerations"></a><span class="InputHeader">A few initial considerations for project owners</span>
+<p>
+<span class="PlainText">
+<a name="definestructure"></a><b>Starting from scratch</b>
+<p>
+When your project is completely new or still in infancy, plan the overall directory structure at the front end of project evolution. Although the top level CVS module structure is predetermined, decide how you generally want to organize source files so that you can communicate this to existing and potential contributors. Considering source structure early on enables you to maintain consistency as the project grows, and makes it easier for new contributors to get up to speed.
+<p>
+A good example of communicating overall project source structure is in the <a href="http://scarab.tigris.org/scarab-design.html#directory" target="_new">design document for the scarab open source project</a> which uses a graphic depiction. CVSWeb source browsing, provided with all projects hosted on this site, also allows users to explore your project's source structure.
+<p>
+
+<a name="postrcsissues"></a><b>Version control project management issues</b>
+
+<p>
+As the project owner, you are likely to deal with developers who are grappling with the differences between RCS and CVS. Here are some key differences to clarify:
+<p>
+<ul>
+<li>One of the central principals in RCS is file locking, which prevents other developers from checking out or modifying a file when someone else has checked it out. The benefit of file locking is that developers never have to deal with conflicting modifications within files. RCS controls versioning by only allowing files to be modified by one person at a time. Therefore, the drawback to RCS is: no one can commit changes to a file while another developer has it checked out.
+<p>
+<li>The central tenant of CVS is ability for developers to concurrently check out, modify, and commit files, which greatly benefits projects with developers participating remotely. CVS merges everyone's changes in a central repository, but the tradeoff is developers on your project will inevitably deal with merge conflicts in files. The only way to resolve such conflicts is to edit the file, choosing which changes to keep and which to delete, before it can be committed.
+</ul>
+<p>
+<hr noshade size=1>
+<a name="cvspermissions"></a><span class="INPUTHEADER">Managing CVS permissions</span>
+<p>
+CVS read-access to your project's source code for site users is determined by whether your project is licensed open source or proprietary. Open source projects allow source file read access for any site user by default, whether or not they are project members. Proprietary project pages are not publicly viewable, so source code access is restricted to project members.
+<p>
+In both open source and proprietary projects, however, you as the Project Owner determine which project members will gain CVS write-access permissions through the roles you grant to them.
+
+<p>
+Observers, that is, users you have approved for project membership but who are not actually contributing source code to the project, have read-access but <i>not</i> write-access to your project's source repository . They can check out, view, compare revisions, and update source files, but they cannot contribute modified files or new files to the source repository.
+<p>
+All other project membership roles automatically confer cvs write-access to project members. This includes the ability to:
+<ul>
+<li>commit changes/patches
+<li>add new files
+<li>import files
+<li>remove files
+<li>check file status
+<li>tag and branch files
+</ul>
+<p>
+
+<p>
+Read-write permissions associated with individual files are administered separately from CVS. Note that these permissions cannot be altered for a file once it is checked into the project's CVS repository.
+<p>
+
+<hr noshade size=1>
+<a href="ProjectOwnerAdmin.html">Back to Project Owner Administration help</a><br>
+<a href="/servlets/HelpTOC">Back to main Help index</a></p>
+
+</span>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerSource.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerSource.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerSource.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,173 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>Managing project source code</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="projectownersource">
+ <h2>Managing project source code</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li>
+ <a href="/nonav/docs/ProjectOwnerAdmin.html">Project owner administration</a>
+
+ <ul>
+ <li><a href="/nonav/docs/ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a></li>
+
+ <li><a href="/nonav/docs/ProjectOwnerNews.html">Managing project site news</a></li>
+
+ <li><a href="/nonav/docs/ProjectOwnerMembers.html">Adding project members and approving roles</a></li>
+
+ <li><a href="/nonav/docs/ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a></li>
+
+ <li><a href="/nonav/docs/ProjectOwnerDocuments.html">Managing project documentation</a></li>
+
+ <li>
+ Managing project source code
+
+ <ul>
+ <li><a href="#gettingstarted">Getting started</a></li>
+
+ <li><a href="#siteadmincvs">About CVS repository tasks</a></li>
+
+ <li><a href="#considerations">A few initial considerations for project owners</a></li>
+
+ <li><a href="#cvspermissions">Managing CVS permissions</a></li>
+ </ul>
+ </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 name="gettingstarted" id="gettingstarted">Getting started</a></h3>
+
+ <p>If you are new to CVS, this help guide provides some basic quick reference information for administrative CVS tasks relevant to projects hosted this site. This guide by no means exhaustively documents CVS or the many broader project management issues imputed by versioning control. A wealth of published documentation for CVS exists, both online and in print. The following links lead to general CVS tool documentation elsewhere on this site, and these documents include many authoritative, external CVS resources.</p>
+
+ <h4>CVS tool documentation</h4>
+
+ <ul>
+ <li><a href="/nonav/docs/ddCVS.html">About CVS version control</a></li>
+
+ <li><a href="/nonav/docs/ddCVS_cvsglossary.html">A version control glossary</a></li>
+
+ <li><a href="/nonav/docs/ddUsingCVS_command-line.html">Using command line CVS</a></li>
+
+ <li><a href="/nonav/docs/ddUsingWinCvs.html">UsingWinCvs</a></li>
+ </ul>
+
+ <h3><a id="siteadmincvs" name="siteadmincvs">About CVS repository tasks</a></h3>
+
+ <p>Much of the administrative work involved with setting up your project's source repository is handled "behind the scenes" when your project gains approval. If you are new to CVS, this means that you do not have to start from scratch to set up the CVS repository for your project.</p>
+
+ <p>The following tasks occur automatically:</p>
+
+ <ul>
+ <li>Your project's basic repository structure is created with a top-level directory that can be expanded upon by adding subdirectories as the project evolves. There is also a "/www" directory created for project web content.</li>
+
+ <li>
+ Your project's CVS root (that is, the server where your CVS repository is located) is automatically set to this site's host servers and preconfigured. The instructions in the <b>Source code</b> page for your project display the exact CVS root needed to log in to the project's source repository. For most projects on this site, the cvsroot will be:
+
+ <p><code>:pserver:username@cvs.projectname.thisdomain:/cvs</code></p>
+ </li>
+ </ul>
+
+ <p>For CVS experts, this automation means that the CVS administrative module is preconfigured for projects hosted on this site. That includes the following files, listed here for your information:</p>
+
+ <ul>
+ <li>Modules file</li>
+
+ <li>Cvswrappers file</li>
+
+ <li>Commit support files</li>
+
+ <li>Commitinfo</li>
+
+ <li>Verifying log messages</li>
+
+ <li>Editinfo</li>
+
+ <li>Loginfo</li>
+
+ <li>Rcsinfo</li>
+
+ <li>Ignoring files via cvsignore</li>
+
+ <li>Checkoutlist file</li>
+
+ <li>History file</li>
+
+ <li>Expansions in administrative files</li>
+ </ul>
+
+ <p>All CVS repository tasks such as backing up, restoring, moving, or configuring remote repository access are also handled by site administrators. Should your project require editing CVS administrative files or other repository-level actions, you must contact a site administrator for support.</p>
+
+ <h3><a id="considerations" name="considerations">A few initial considerations for project owners</a></h3>
+
+ <h4><a id="definestructure" name="definestructure">Starting from scratch</a></h4>
+
+ <p>When your project is completely new or still in infancy, plan the overall directory structure at the front end of project evolution. Although the top level CVS module structure is predetermined, decide how you generally want to organize source files so that you can communicate this to existing and potential contributors. Considering source structure early on enables you to maintain consistency as the project grows, and makes it easier for new contributors to get up to speed.</p>
+
+ <p>A good example of communicating overall project source structure is in the <a href="http://scarab.tigris.org/scarab-design.html#directory">design document for the scarab open source project</a> which uses a graphic depiction. ViewCVS source browsing, provided with all projects hosted on this site, also allows users to explore your project's source structure.</p>
+
+ <p><a id="postrcsissues" name="postrcsissues"></a><b>Version control project management issues</b></p>
+
+ <p>As the project owner, you are likely to deal with developers who are grappling with the differences between RCS and CVS. Here are some key differences to clarify:</p>
+
+ <ul>
+ <li>One of the central principals in RCS is file locking, which prevents other developers from checking out or modifying a file when someone else has checked it out. The benefit of file locking is that developers never have to deal with conflicting modifications within files. RCS controls versioning by only allowing files to be modified by one person at a time. Therefore, the drawback to RCS is: no one can commit changes to a file while another developer has it checked out.</li>
+
+ <li>The central tenant of CVS is ability for developers to concurrently check out, modify, and commit files, which greatly benefits projects with developers participating remotely. CVS merges everyone's changes in a central repository, but the tradeoff is developers on your project will inevitably deal with merge conflicts in files. The only way to resolve such conflicts is to edit the file, choosing which changes to keep and which to delete, before it can be committed.</li>
+ </ul>
+
+ <h3><a id="cvspermissions" name="cvspermissions">Managing CVS permissions</a></h3>
+
+ <p>CVS read-access to your project's source code for site users is determined by whether your project is licensed open source or proprietary. Open source projects allow source file read access for any site user by default, whether or not they are project members. Proprietary project pages are not publicly viewable, so source code access is restricted to project members.</p>
+
+ <p>In both open source and proprietary projects, however, you as the Project Owner determine which project members will gain CVS write-access permissions through the roles you grant to them.</p>
+
+ <p>Observers, that is, users you have approved for project membership but who are not actually contributing source code to the project, have read-access but <i>not</i> write-access to your project's source repository . They can check out, view, compare revisions, and update source files, but they cannot contribute modified files or new files to the source repository.</p>
+
+ <p>All other project membership roles automatically confer cvs write-access to project members. This includes the ability to:</p>
+
+ <ul>
+ <li>commit changes/patches</li>
+
+ <li>add new files</li>
+
+ <li>import files</li>
+
+ <li>remove files</li>
+
+ <li>check file status</li>
+
+ <li>tag and branch files</li>
+ </ul>
+
+ <p>Read-write permissions associated with individual files are administered separately from CVS. Note that these permissions cannot be altered for a file once it is checked into the project's CVS repository.</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/ProjectOwnerVersionControl.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerVersionControl.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectOwnerVersionControl.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,80 @@
+<!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>Effective version managment</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="projectownerversioncontrol">
+ <h2><a id="Effective" name="Effective">Effective version management</a></h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </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">Configuring and managing project mailing lists</a></li>
+
+ <li><a href="/nonav/docs/ProjectOwnerDocuments.html">Managing project documentation</a></li>
+
+ <li><a href="/nonav/docs/ProjectOwnerSource.html">Managing project source code</a></li>
+
+ <li>Effective version management</li>
+ </ul>
+ </div>
+
+ <p>Version management is characterized by effectively tracking changes from their origin to the alteration to the project source code. Within a project, links between issues within the issue tracker (IssueZilla) and change records from the change control tool (CVS) are an effect means of managing your versions. Implementing a series of manual processes within your project will provide invaluable information throughout the life-cycle of your project. The manual process includes pasting links to CVS check-in messages in the IssueZilla issues, and supplementing these with adding the issue number to those CVS check-in messages. Further enhanced through the automatic messages generated by these two tools, the peer review process can help keep project members on track with this process.</p>
+
+ <p>Inherent to CVS is the ability to isolate code sets for unique development cycles. When a version is tagged an identifier is required within CVS. To better coordinate the version tracking process, the CVS version identifier should be identifiable within IssueZilla. By adding the CVS version to the IssueZilla database and requiring a version in issue creation the version tracking process can be greatly enhanced. This will allow you to easily identify the status of issues for a particular version and to run queries for all issues associated with a specific version.</p>
+
+ <h3>IssueZilla and version management</h3>
+
+ <p>The version number in IssueZilla allows you to track releases and versions of your project. When determining your version numbers it is recommended that you associate the version in your issue tracker with the tag numbers in your change manager, CVS. Associating the numbers between the two tools simplifies the process of correlating between issues in the issue tracker and changes made in CVS. As the project owner you can set a list of version numbers in the IssueZilla database and require the version number for all new issues. Users creating new issues must assign the version number in order to commit the issue. This is especially effective when running reports. Searching your IssueZilla database for all issues associated with a particular version number is as easy as defining a query. For more information, see <a href="/nonav/docs/ProjectOwnerIssues.html#adminconfigure">Configuring IssueZilla's Administrative options</a>.</p>
+
+ <p>Additionally, reports can be run through IssueZilla to track the progress of the version.</p>
+
+ <h3>CVS and version management</h3>
+
+ <p>Once you've got your issue tracker to mirror versions in CVS, you can further the change management process by requiring your members to add the issue number into any commit messages they create in CVS This can be done using several different manual process.</p>
+
+ <ul>
+ <li>members can manually add the issue number in the commit message. This is simplified in ViewCVS by a "issue number" field.</li>
+
+ <li>Members can paste a link to the IssueZilla issue into the CVS commit message</li>
+
+ <li>members can paste a link to a diff statement for the CVS commit into the IssueZilla issue.</li>
+ </ul>
+
+ <p>Ideally, all of these suggestions would be a regular part of your issue and commit processes.</p>
+
+ <h3>Peer-review process and version management</h3>
+
+ <p>When issues are created in IssueZilla an email is automatically sent to the announce mailing list. Posting links to the commit messages and/or a graphical representation of the <i>diff</i> statement in the IssueZilla issue provides a built in review process. Members of the project automatically receive the emails generated by IssueZilla and can review the issues for proper compliance with your processes and to ensure that enough relevant information has been provided. Further, when you're team is faced with similar issues finding historical information on how the issue was addressed in the past is as simple as either finding the IssueZilla number to access CVS change information or reviewing the commit messages to find the IssueZilla numbers.</p>
+
+ <p>Emails from CVS and IssueZilla commits are archived and searchable by Author, Subject, Date and Thread.</p>
+
+ <p>Using a combination of manual procedures as standard practices within your project can help you to maintain effective version management.</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/ProjectPatches.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectPatches.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectPatches.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,48 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<TITLE>Project Patches</TITLE>
+
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <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>Project Patches</TD>
+ </TR>
+</TABLE>
+
+<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
+ <TR>
+ <TD class="PlainText" VALIGN="top">
+ <UL>
+ <LI><A HREF="/bugs/enger_bug.cgi" CLASS="ProjectName">Enter a new patch</A>
+ <LI><A HREF="/bugs/query.cgi" CLASS="ProjectName">Query database of patches</A>
+ </UL>
+ </TD>
+ </TR>
+</table>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectQuota.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectQuota.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectQuota.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,196 @@
+<!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 project quotas</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="projectquota">
+ <h2>Administering project quotas</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">Help for domain administration</a>
+
+ <ul>
+ <li>
+ <a href="/nonav/docs/DomAdminAddUsers.html">Adding and editing user accounts</a>
+
+ <ul>
+ <li><a href="/nonav/docs/DomAdminRoles.html">Administering roles and permissions</a></li>
+
+ <li><a href="/nonav/docs/DomAdminUserGroups.html">Creating and editing user groups</a></li>
+
+ <li><a href="/nonav/docs/DomAdminProjectGroups.html">Creating and editing project groups</a></li>
+
+ <li><a href="/nonav/docs/DomAdminProjectApproval.html">Approving, disapproving, or deferring projects</a></li>
+
+ <li><a href="/nonav/docs/DomAdminAuditLogs.html">Using administrative audit logs</a></li>
+
+ <li>
+ Administering project quotas
+
+ <ul>
+ <li><a href="#using">Using quotas</a></li>
+
+ <li><a href="#setting">Setting project space quotas</a></li>
+
+ <li><a href="#locking">Locking and unlocking projects</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/DomAdminAuditLogs.html">Using a project database</a></li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </div>
+
+ <p>Project quotas allow administrators to define the amount of disk space allocated to each project in the domain. Administrators can choose to use either a predetermined allocation or define their own quota values. If a project exceeds the quota the administrator will be notified and can select one of three possible actions:</p>
+
+ <ol>
+ <li>The administrator may select to lock the project. This action will render the project invisible to anyone with less than project owner access rights. If a project is locked, the administrator must be contacted to remove the restrictions.</li>
+
+ <li>The project owner may work with the administrator towards an acceptable solution. The agreed upon solution may include archiving old news or issues.</li>
+
+ <li>No action may be taken. In this case, the quota may be used as a form of monitoring disk usage and planning for future needs.</li>
+ </ol>
+
+ <h3><a id="using" name="using">Using quotas</a></h3>
+
+ <p>As the administrator, you have the ability to change the disk-space quota for projects in your domain. You will need to set two levels of quota for each project: the soft disk-space quota and the hard disk-space quota. For the quotas to function correctly, the soft disk-space quota must be greater than 0 but less than the hard disk-space quota. The hard disk-space quota must be greater than the soft disk space quota as well.</p>
+
+ <p>The soft disk-space quota is designed as an early warning level for the project owner. Daily, a scan checks the amount of disk-space used by each project in the domain. If the amount of disk-space used for an individual project exceeds the soft disk-space quota, an email is sent to the project owner warning him or her that their project is reaching the maximum disk space available. The project owner will receive this email each time the project is determined to exceed the soft disk-space quota. To lower the space used, the project owner may choose to clear some of the project's items from the disk.</p>
+
+ <p>If a project has exceed the allocated hard disk-space quota, an email alert is sent to the administrator and a lock project request notice is placed in the administrator's home page. The administrator receives the notice only once each time the project exceeds the hard disk-space quota. The action to be taken is completely at the discretion of the administrator and the normal procedures for the implementation.</p>
+
+ <h4><a id="setting" name="setting">Setting project space quotas</a></h4>
+
+ <ol>
+ <li>Login as an administrator</li>
+
+ <li>Go to your Start Page</li>
+
+ <li>Click on the <b>Adminstration</b> link for the project you would like to edit</li>
+
+ <li>Click on <b>Edit Project Quotas</b> link on the <b>Administer Project</b> screen</li>
+
+ <li>Enter the disk-space quota in kilobites</li>
+
+ <li>Click on the <b>Submit Changes</b> button</li>
+ </ol>
+
+ <h4><a id="locking" name="locking">Locking and unlocking projects</a></h4>
+
+ <p>To lock a project,</p>
+
+ <ol>
+ <li>Login as an administrator</li>
+
+ <li>Go to your Start Page</li>
+
+ <li>Click on the <b>Adminstration</b> link for the project you would like to lock</li>
+
+ <li>Click on <b>Lock Project</b> link in the <b>Other Operations</b> section</li>
+
+ <li>Verify that you would like to lock this project by clicking on the <b>Lock Project</b> button on the next screen</li>
+ </ol>
+
+ <p>To unlock a project,</p>
+
+ <ol>
+ <li>Login as an administrator</li>
+
+ <li>Go to your Start Page</li>
+
+ <li>Click on the name of the project you would like to unlock</li>
+
+ <li>Click on <b>Unlock Project</b> link next to the project name</li>
+ </ol>
+
+ <p>Administering project quotas</p>
+
+ <p>Project quotas allow administrators to define the amount of disk space allocated to each project in the domain. Administrators can choose to use either a predetermined allocation or define their own quota values. If a project exceeds the quota the administrator will be notified and can select one of three possible actions:</p>
+
+ <ol>
+ <li>The administrator may select to lock the project. This action will render the project invisible to anyone with less than project owner access rights. If a project is locked, the administrator must be contacted to remove the restrictions.</li>
+
+ <li>The project owner may work with the administrator towards an acceptable solution. The agreed upon solution may include archiving old news or issues.</li>
+
+ <li>No action may be taken. In this case, the quota may be used as a form of monitoring disk usage and planning for future needs.</li>
+ </ol>
+
+ <h3><a id="using" name="using">Using quotas</a></h3>
+
+ <p>As the administrator, you have the ability to change the disk-space quota for projects in your domain. You will need to set two levels of quota for each project: the soft disk-space quota and the hard disk-space quota. For the quotas to function correctly, the soft disk-space quota must be greater than 0 but less than the hard disk-space quota. The hard disk-space quota must be greater than the soft disk space quota as well.</p>
+
+ <p>The soft disk-space quota is designed as an early warning level for the project owner. Daily, a scan checks the amount of disk-space used by each project in the domain. If the amount of disk-space used for an individual project exceeds the soft disk-space quota, an email is sent to the project owner warning him or her that their project is reaching the maximum disk space available. The project owner will receive this email each time the project is determined to exceed the soft disk-space quota. To lower the space used, the project owner may choose to clear some of the project's items from the disk.</p>
+
+ <p>If a project has exceed the allocated hard disk-space quota, an email alert is sent to the administrator and a lock project request notice is placed in the administrator's home page. The administrator receives the notice only once each time the project exceeds the hard disk-space quota. The action to be taken is completely at the discretion of the administrator and the normal procedures for the implementation.</p>
+
+ <h4><a id="setting" name="setting">Setting project space quotas</a></h4>
+
+ <ol>
+ <li>Login as an administrator</li>
+
+ <li>Go to your Start Page</li>
+
+ <li>Click on the <b>Adminstration</b> link for the project you would like to edit</li>
+
+ <li>Click on <b>Edit Project Quotas</b> link on the <b>Administer Project</b> screen</li>
+
+ <li>Enter the disk-space quota in kilobites</li>
+
+ <li>Click on the <b>Submit Changes</b> button</li>
+ </ol>
+
+ <h4><a id="locking" name="locking">Locking and unlocking projects</a></h4>
+
+ <p>To lock a project,</p>
+
+ <ol>
+ <li>Login as an administrator</li>
+
+ <li>Go to your Start Page</li>
+
+ <li>Click on the <b>Adminstration</b> link for the project you would like to lock</li>
+
+ <li>Click on <b>Lock Project</b> link in the <b>Other Operations</b> section</li>
+
+ <li>Verify that you would like to lock this project by clicking on the <b>Lock Project</b> button on the next screen</li>
+ </ol>
+
+ <p>To unlock a project,</p>
+
+ <ol>
+ <li>Login as an administrator</li>
+
+ <li>Go to your Start Page</li>
+
+ <li>Click on the name of the project you would like to unlock</li>
+
+ <li>Click on <b>Unlock Project</b> link next to the project name</li>
+ </ol>
+
+ <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/ProjectRoles.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectRoles.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectRoles.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,87 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>About project roles</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">
+
+
+
+
+</a><span class="Header"><b>About project roles</b></span>
+
+<span class="PlainText">
+<p>
+<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><a href="ProjectMembershipRequest.html">Joining a project</a>
+ <dd><b>You are here: Learning about project roles</b>
+<dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+</dl>
+</ul>
+<p>
+
+
+
+<hr noshade size=1>
+<b>Observer</b><br>
+<ul>
+<li>Views, but does not change project resources.
+<li>Read-only access to most project resources.
+<li>Read-only access to web content and source code (CVS).
+<li>Submits issue to issue tracking (IssueZilla)
+<li>Subscribes and posts to project mailing lists.
+</ul>
+
+<p><b>Developer</b><br>
+<ul>
+<li>Contributes directly to project -- source code and HTML.
+<li>Gains write access to most project resources.
+<li>Write access to HTML, news utility, files utility, CVS, Issuezilla.
+<li>Mailing list privileges the same.
+</ul>
+
+<p><b>Content Developer</b><br>
+<ul>
+<li>Contributes directly to project's web content (HTML).
+<li>Gains write access to project's HTML, news utility, files utility, and Issuezilla.
+<li>Mailing list privileges the same.
+</ul>
+
+<p><b>Project Owner</b><br>
+<ul>
+<li>Defines the project's overall mission, direction, methodology, and community make-up.
+<li>Gains administrative access to all Project functions.
+<li>Grants members requested permissions on project.
+<li>Administers all project mailing lists and is default moderator on all lists.
+<li>Administers Issuezilla.
+<li>Project Owner role supersedes any other roles you may hold on a project.
+</ul>
+<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/ProjectRoles.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectRoles.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectRoles.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,116 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>About project roles</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="projectroles">
+ <h2>About project roles</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><a href="/nonav/docs/ProjectMembershipRequest.html">Joining a project</a></li>
+
+ <li>Learning about project roles</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>
+
+ <dl>
+ <dt>Observer</dt>
+
+ <dd>
+ <ul>
+ <li>Views, but does not change project resources.</li>
+
+ <li>Read-only access to most project resources.</li>
+
+ <li>Read-only access to web content and source code (CVS).</li>
+
+ <li>Submits issue to issue tracking (IssueZilla)</li>
+
+ <li>Subscribes and posts to project mailing lists.</li>
+ </ul>
+ </dd>
+
+ <dt>Developer</dt>
+
+ <dd>
+ <ul>
+ <li>Contributes directly to project -- source code and HTML.</li>
+
+ <li>Gains write access to most project resources.</li>
+
+ <li>Write access to HTML, news utility, files utility, CVS, Issuezilla.</li>
+
+ <li>Mailing list privileges the same.</li>
+ </ul>
+ </dd>
+
+ <dt>Content Developer</dt>
+
+ <dd>
+ <ul>
+ <li>Contributes directly to project's web content (HTML).</li>
+
+ <li>Gains write access to project's HTML, news utility, files utility, and Issuezilla.</li>
+
+ <li>Mailing list privileges the same.</li>
+ </ul>
+ </dd>
+
+ <dt>Project Owner</dt>
+
+ <dd>
+ <ul>
+ <li>Defines the project's overall mission, direction, methodology, and community make-up.</li>
+
+ <li>Gains administrative access to all Project functions.</li>
+
+ <li>Grants members requested permissions on project.</li>
+
+ <li>Administers all project mailing lists and is default moderator on all lists.</li>
+
+ <li>Administers Issuezilla.</li>
+
+ <li>Project Owner role supersedes any other roles you may hold on a project.</li>
+ </ul>
+ </dd>
+ </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/ProjectSource.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectSource.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectSource.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,113 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Project Resources for Members</title>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+
+<p>
+ <span class="Header" nowrap>Project Source</span>
+ <p>
+
+<span class="PlainText"><b>Project resources for members: Index</b>
+<p>
+ <ul><dl>
+ <dt><a href="ProjectMemberResources.html">Project resources for members</a>
+ <dd><a href="ProjectHome.html">Project Home Page</a>
+ <dd><a href="ProjectNews.html">Project News</a>
+ <dd><a href="ProjectDownload.html">Project Download</a>
+ <dd><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><b>You are here: Project Source Code
+ <ul>
+ <li><a href="#browsesource">Browsing a project's source repository with CVSWeb</a>
+ <li><a href="#getsource">Getting your working copy of project source files</a>
+ <li><a href="#cvsclients">CVS client downloads</a>
+ </ul></b>
+ <dd><a href="ProjectIssues.html">Project Issues</a>
+<dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+ </dl>
+</ul>
+<p>
+<span class="PlainText">
+<b>CVS tool documentation</b>
+ <dl>
+ <dt><a href="ddCVS.html">About CVS versioning control</a><br>
+ <dt><a href="ddCVS_cvsglossary.html">A version control glossary</a>
+ <dt><a href="ddUsingWinCvs.html">Site guide for using WinCVS</a><br>
+ <dt><a href="ddUsingCVS_command-line.html">Site guide for using command line CVS </a>
+</dl>
+<p>
+<hr noshade size=1>
+<span class="InputHeader"><a name="browsesource"></a>Browsing a project's source repository with CVSWeb</span>
+<span class="PlainText">
+<p>
+It's a good idea to browse a project's source repository first to learn how the files are organized. CVS refers to the top-level groupings of files as "modules" (rather than "directories").
+<p>
+ <ol>
+ <li>From your Project Home page, click on Source in the Project Resources toolbar.
+ <p>
+ <li>Click on "Browse project source files" to access the project's source repository through CVSWeb.
+ </ol>
+<p>
+Each project's web content files are located in the "www/" module by default. Other project source modules are created and organized by each project owner or project members with CVS write permissions. If browsing deleted and removed project files is permitted, an "Attic/" module is displayed.
+
+<p><a href="ddSourceBrowse.html">More information about CVSWeb</a>
+
+<p>
+<hr noshade size=1>
+<a name="getsource"></a><span class="InputHeader">Getting your working copy of project source files</span>
+<p>
+To obtain (or "check out") your own working copy of project files, step-by-step instructions are included on the <a href="/templates/org/tigris/helm/project/Project Source.wm">Project Source page</a> for both command line CVS and WinCvs. These instructions also show the exact cvsroot to set for the current project. The <i>cvsroot</i> points to the server location of the project's source repository.
+<p>
+A <i>working copy</i> refers to the replicated set of project source files you maintain and modify on your own local machine. If you are new to CVS, this is an important CVS concept to understand. These files reside in your workspace, and the CVS server does not track or know anything about your changes (or other developers' changes) until you commit modified files or add newly created files back into the main project repository.
+<p>
+This may be different from other versioning systems which explicitly track creation of workspaces. With CVS, you can check out working copies as many times as necessary. Keep in mind, however, that files in the project repository continually change over time as to reflect other developer contributions as the project progresses. It's critical to keep your working copies of files up to date with the repository.
+<p>
+
+<p>
+<hr noshade size=1>
+<span class="InputHeader"><a name="cvsclients">CVS client downloads</a></span>
+ <ul>
+ <li><a
+ href="http://www.cyclic.com/downloads.html" target="_new">Command line clients for many systems</a></li>
+
+ <li><a href="http://www.cvsgui.org/download.html" target="_new">WinCVS: a Windows CVS client</a></li>
+
+ <li><a href="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</a></li>
+
+ <li><a href="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</a></li>
+ </ul>
+<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/ProjectSource.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectSource.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectSource.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,107 @@
+<!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 source code</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="projectsource">
+ <h2>Project Source code</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li><a href="/nonav/docs/Learning.html">Learning about projects</a></li>
+
+ <li>
+ <a href="/nonav/docs/ProjectMemberResources.html">Project resources for members</a>
+
+ <ul>
+ <li><a href="/nonav/docs/ProjectHome.html">Project Home Page</a></li>
+
+ <li><a href="/nonav/docs/ProjectNews.html">Project News</a></li>
+
+ <li><a href="/nonav/docs/ProjectMemberList.html">Project Membership</a></li>
+
+ <li><a href="/nonav/docs/ProjectMail.html">Project Mailing Lists</a></li>
+
+ <li><a href="/nonav/docs/ProjectDocuments.html">Project Documentation</a></li>
+
+ <li>
+ Project Source Code
+
+ <ul>
+ <li><a href="#browsesource">Browsing a project's source repository with ViewCVS</a></li>
+
+ <li><a href="#getsource">Getting your working copy of project source code files</a></li>
+
+ <li><a href="#cvsclients">CVS client downloads</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/ProjectIssues.html">Issue Tracking</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/hostedtools.html">Hosted tools</a></li>
+
+ <li><a href="/nonav/docs/ProjectAdd.html">Creating a new project</a></li>
+ </ul>
+
+ <ul>
+ <li><a href="/nonav/docs/ddCVS.html">About CVS versioning control</a></li>
+
+ <li><a href="/nonav/docs/ddCVS_cvsglossary.html">A version control glossary</a></li>
+
+ <li><a href="/nonav/docs/ddUsingWinCvs.html">Site guide for using WinCVS</a></li>
+
+ <li><a href="/nonav/docs/ddUsingCVS_command-line.html">Site guide for using command line CVS</a></li>
+ </ul>
+ </div>
+
+ <h3><a id="browsesource" name="browsesource">Browsing a project's source code repository with ViewCVS</a></h3>
+
+ <p>Before beginning work in a project, you should take time to learn how the project files are organized. You will want to become familiar with the directory structures as well as any CVS "modules" that have been defined by project members.</p>
+
+ <ol>
+ <li>From your Project Home page, click on <b>Source code</b> on the left navigation bar.</li>
+
+ <li>Click on "Browse source code" to access the project's source repository through ViewCVS.</li>
+ </ol>
+
+ <p>Each project's web content files are located in the myproject/www module by default. Each project has two predefined modules: www and look. Other project source modules are created and organized by project owner or project members with CVS write permissions. If browsing deleted and removed project files is permitted, an "Attic/" module is displayed.</p>
+
+ <ul>
+ <li><a href="/nonav/docs/ddSourceBrowse.html">More information about ViewCVS</a></li>
+ </ul>
+
+ <h3><a id="getsource" name="getsource">Getting your working copy of project source code</a></h3>
+
+ <p>To obtain (or "check out") your own working copy of project files, step-by-step instructions are included on the <a href="/servlets/ProjectSource">Project Source</a> page for both command line CVS and WinCvs. These instructions also show the exact cvsroot to set for the current project. The <i>cvsroot</i> points to the server location of the project's source code.</p>
+
+ <p>A <i>working copy</i> refers to the replicated set of project source code you maintain and modify on your own local machine. If you are new to CVS, this is an important CVS concept to understand. These files reside in your workspace, and the CVS server does not track or know anything about your changes (or other developers' changes) until you commit modified files or add newly created files back into the main project repository.</p>
+
+ <p>This may be different from other versioning systems which explicitly track creation of workspaces. With CVS, you can check out working copies as many times as necessary. Keep in mind, however, that files in the project repository continually change over time as to reflect other developer contributions as the project progresses. It's critical to keep your working copies of files up to date with the repository.</p>
+
+ <h3><a id="cvsclients" name="cvsclients">CVS client downloads</a></h3>
+
+ <p>You can download CVS clients for command line, Windows, or Mac and other developer tools at <a href="http://www.collab.net/developers/tools/">http://www.collab.net/developers/tools/</a>.</p>
+ <div class="courtesylinks">
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectSourceHelp.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectSourceHelp.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectSourceHelp.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,106 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<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" 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/ProjectSource.html#browsesource">Browse project source code...</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/ProjectSource.html#getsource">Get a copy of project source files...</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/ddCVS.html">Learn more about CVS...</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/ProjectSource.html#cvsclients">Find a CVS client...</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/ProjectUnlockedHelp.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectUnlockedHelp.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ProjectUnlockedHelp.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/README
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/README (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/README Sat Apr 8 23:00:09 2017
@@ -0,0 +1 @@
+This is where you can put wedge user documentation.