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 2012/03/19 23:22:37 UTC
svn commit: r809211 - in /websites/staging/openofficeorg/trunk/content: ./
openofficeorg/ openofficeorg/docs/ openofficeorg/docs/governance/
Author: buildbot
Date: Mon Mar 19 22:22:36 2012
New Revision: 809211
Log:
Staging update by buildbot for openofficeorg
Modified:
websites/staging/openofficeorg/trunk/content/ (props changed)
websites/staging/openofficeorg/trunk/content/openofficeorg/bug-tracking.html
websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html
websites/staging/openofficeorg/trunk/content/openofficeorg/contact.html
websites/staging/openofficeorg/trunk/content/openofficeorg/developer-faqs.html
websites/staging/openofficeorg/trunk/content/openofficeorg/docs/download_process.html
websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html
websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/consensusBuilding.html
websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html
websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/voting.html
websites/staging/openofficeorg/trunk/content/openofficeorg/get-involved.html
websites/staging/openofficeorg/trunk/content/openofficeorg/index.html
websites/staging/openofficeorg/trunk/content/openofficeorg/license.html
websites/staging/openofficeorg/trunk/content/openofficeorg/mailing-lists.html
websites/staging/openofficeorg/trunk/content/openofficeorg/native-lang.html
websites/staging/openofficeorg/trunk/content/openofficeorg/people.html
websites/staging/openofficeorg/trunk/content/openofficeorg/ppmc-faqs.html
websites/staging/openofficeorg/trunk/content/openofficeorg/release-process.html
websites/staging/openofficeorg/trunk/content/openofficeorg/security.html
websites/staging/openofficeorg/trunk/content/openofficeorg/source.html
websites/staging/openofficeorg/trunk/content/openofficeorg/svn-basics.html
websites/staging/openofficeorg/trunk/content/openofficeorg/terms.html
websites/staging/openofficeorg/trunk/content/openofficeorg/trademarks.html
websites/staging/openofficeorg/trunk/content/openofficeorg/website-local.html
Propchange: websites/staging/openofficeorg/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Mar 19 22:22:36 2012
@@ -1 +1 @@
-1302686
+1302690
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/bug-tracking.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/bug-tracking.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/bug-tracking.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
@@ -78,7 +79,7 @@
<div id="contenta">
<h1 class="title">Community FAQs</h1>
- <h2 id="how_are_decisions_made_in_the_project">How are decisions made in the project?</h2>
+ <h2 id="how-are-decisions-made-in-the-project">How are decisions made in the project?</h2>
<p>The most important thing about engaging with any Apache project is that everyone
is equal. All people with an opinion are entitled to express that opinion and, where
appropriate, have it considered by the community.</p>
@@ -88,18 +89,18 @@ set of simple processes to ensure things
<p>In ASF projects we don't like to vote. We reserve that for the few things that need
official approval for legal or process reasons (e.g. a release or a new committer).
Most of the time we work with the consensus building techniques documented below.</p>
-<h2 id="what_is_lazy_consensus">What is "Lazy Consensus"?</h2>
+<h2 id="what-is-lazy-consensus">What is "Lazy Consensus"?</h2>
<p><a href="/openofficeorg/docs/governance/lazyConsensus.html">Lazy consensus</a> is the first, and possibly the most important, consensus building
tool we have. Essentially lazy consensus means that you don't need to get explicit
approval to proceed, but you need to be prepared to listen if someone objects.</p>
-<h2 id="consensus_building">Consensus Building</h2>
+<h2 id="consensus-building">Consensus Building</h2>
<p>Sometimes lazy consensus is not appropriate. In such cases it is necessary to
make a proposal to the mailing list and discuss options. There are mechanisms
for quickly showing your support or otherwise for a proposal and
<a href="/openofficeorg/docs/governance/consensusBuilding.html">building consensus</a> amongst the community.</p>
<p>Once there is a consensus people can proceed with the work under the <a href="/openofficeorg/docs/governance/lazyConsensus.html">lazy
consensus</a> model.</p>
-<h2 id="what_about_voting">What about voting?</h2>
+<h2 id="what-about-voting">What about voting?</h2>
<p>Occasionally a "feel" for consensus is not enough. Sometimes we need to
have a measurable consensus. For example, when <a href="/openofficeorg/docs/governance/voting.html">voting</a> in new committers or
to approve a release. </p>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/contact.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/contact.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/contact.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/developer-faqs.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/developer-faqs.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/developer-faqs.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/docs/download_process.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/docs/download_process.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/docs/download_process.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
@@ -81,7 +82,7 @@
<p>This documentation shows how to edit the Apache OpenOffice.org
website. This includes creation of new pages, modification, and deletion - for files
and sub-directories.</p>
-<h2 id="how_it_works_in_general">How it works in general</h2>
+<h2 id="how-it-works-in-general">How it works in general</h2>
<p>The website is hosted in a Content Management System (CMS). When you edit a web page
there are potentially four different versions of it to think about:</p>
<ol>
@@ -106,7 +107,7 @@ there are potentially four different ver
<p>The intent of this workflow is to allow committers flexibility in changing
webpages and testing changes on a staging website, before moving these changes to
the public web site.</p>
-<h2 id="command_line_editing_workflow">Command line editing workflow</h2>
+<h2 id="command-line-editing-workflow">Command line editing workflow</h2>
<p>It is assumed that you have already checked out the code from the SVN repository
(https://svn.apache.org/repos/asf/incubator/ooo).</p>
<p>Edit the file via your favorite editor like vi and finally commit via SVN:</p>
@@ -132,19 +133,19 @@ executing this:</p>
</pre></div>
-<h2 id="browser-based_editing_workflow">Browser-based editing workflow</h2>
+<h2 id="browser-based-editing-workflow">Browser-based editing workflow</h2>
<h3 id="prerequisites">Prerequisites</h3>
-<h4 id="browser_bookmark">Browser bookmark</h4>
+<h4 id="browser-bookmark">Browser bookmark</h4>
<p>Normally you see the webpage in your browser. To update this page with an
inline-editor and little preview you use the <a href="javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))">Apache CMS</a> JavaScript bookmarklet. Drag that
link to your browser's toolbar. For more information see <a href="https://cms.apache.org/#bookmark">here</a>.</p>
-<h4 id="apache_id">Apache ID</h4>
+<h4 id="apache-id">Apache ID</h4>
<p>Furthermore, you need an Apache ID to authenticate to the system.</p>
<h3 id="starting">Starting</h3>
<p>Browse to the webpage or directory you would like to edit and click on
the bookmarklet. Now click on the [Edit this directory] link on the top. The following
is displayed as content from the CMS.</p>
-<h3 id="edit_an_existing_webpage">Edit an existing webpage</h3>
+<h3 id="edit-an-existing-webpage">Edit an existing webpage</h3>
<p>Click on the actions link [Edit] in the appropriate table cell for editing the
current file. If the file is not in this directory but in a subdirectory, just click on
the directory name (e.g., "docs/") to enter this directory.</p>
@@ -158,7 +159,7 @@ the directory name (e.g., "docs/") to en
<p>When you have finished writing your text, check the "Quick Commit" box, enter a
commit message and click on [Submit]. This commits your changes to the Subversion
repository.</p>
-<h3 id="verifying_the_staged_web_site">Verifying the staged web site</h3>
+<h3 id="verifying-the-staged-web-site">Verifying the staged web site</h3>
<p>As noted above, committing your changes triggers a build of the markdown files
into HTML in the staging directory. Wait a few
seconds and then click the [Staged] link to view your web page as staged.</p>
@@ -167,20 +168,20 @@ errors? Do the links work? If you've ma
more than one browser.</p>
<p>Once you are satisfied that the page is correct, you are ready to publish it
to the production site.</p>
-<h3 id="publishing_to_the_production_directory">Publishing to the production directory</h3>
+<h3 id="publishing-to-the-production-directory">Publishing to the production directory</h3>
<p>After you have edited your files and/or directories, you need now to publish your
modifications into production. For this please click on the link
[Publish site] on the top of the webpage. Enter a commit message on click
on [Submit]. After a few seconds you can check the [Production] link to see the
live version of your changes.<br />
</p>
-<h3 id="create_a_new_webpage">Create a new webpage</h3>
+<h3 id="create-a-new-webpage">Create a new webpage</h3>
<p>When in the correct directory, at the top enter a name for the new text file (e.g.,
"my-file.mdtext"). Now you enter your text (see topic above).</p>
-<h3 id="create_new_subdirectory">Create new subdirectory</h3>
+<h3 id="create-new-subdirectory">Create new subdirectory</h3>
<p>When in the correct directory, at the top enter a name for the new directory (e.g.,
"my-dir/"). Make sure you entered a trailing "/"!</p>
-<h3 id="delete_a_webpage_or_subdirectory">Delete a webpage or subdirectory</h3>
+<h3 id="delete-a-webpage-or-subdirectory">Delete a webpage or subdirectory</h3>
<p>When in the correct directory, click on the actions link [Delete] in the appropriate
table cell and enter a commit message. Finally click on [Submit]. Generally speaking
it is always a good idea to use the CMS to delete files and directories over using
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/consensusBuilding.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/consensusBuilding.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/consensusBuilding.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
@@ -86,7 +87,7 @@ amounts of unnecessary mail that everyon
That is not to say that we want to avoid constructive discussion. This is
the lifeblood of a successful project. However, many ASF projects adopt a
shorthand notation for showing support, or otherwise, for a proposal.</p>
-<h2 id="expressing_support_or_otherwise">Expressing support (or otherwise)</h2>
+<h2 id="expressing-support-or-otherwise">Expressing support (or otherwise)</h2>
<p>The notation used is "+1", "-1" and "0". It's also common to see "+0" and "-0".</p>
<p>So, what do these notations mean?</p>
<ul>
@@ -103,7 +104,7 @@ to help implement"</li>
like "+1000".</p>
<p>The important thing is that this is not an exact science. It's just a shorthand
way of communicating strength of feeling.</p>
-<h2 id="consensus_building_is_not_voting">Consensus Building is Not Voting</h2>
+<h2 id="consensus-building-is-not-voting">Consensus Building is Not Voting</h2>
<p>The confusing thing about this notation is that it is the same notation
used in a formal vote. Knowing when something is a vote and when it is a
preference is important. It's easy to tell though, if the subject does not have
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
@@ -89,7 +90,7 @@ You just assume you have the community's
to indicate disapproval. If you believe the community will support your action
you can operate on lazy consensus as long as you are prepared to roll back
any work should a valid objection is raised.</p>
-<h2 id="avoiding_unnecessary_discussion">Avoiding Unnecessary Discussion</h2>
+<h2 id="avoiding-unnecessary-discussion">Avoiding Unnecessary Discussion</h2>
<p>The key thing about lazy consensus is that it's easier for people to agree,
by doing nothing, than it is to object, which requires an
alternative to be proposed. This has two effects, firstly people are less
@@ -101,7 +102,7 @@ of the project to watch what is happenin
far down the road will cause upset, but objecting (or asking for clarification
of intent) early is likely to be greeted with relief that someone is watching
and cares.</p>
-<h2 id="stating_lazy_consensus">Stating Lazy Consensus</h2>
+<h2 id="stating-lazy-consensus">Stating Lazy Consensus</h2>
<p>Sometimes a member of the community will believe a specific action is the correct
one for the community but are not sure enough to proceed with the work under the
lazy consensus model. In these circumstances they can state Lazy Consensus is in
@@ -117,7 +118,7 @@ around their proposal, nor are they requ
supports their actions. However, this differs from assuming lazy consensus
since it allows space and time to <a href="/openofficeorg/docs/governance/consensusBuilding.html">express support or objections</a> and corrections to
the proposal before work begins. </p>
-<h2 id="silence_is_consent">Silence is consent</h2>
+<h2 id="silence-is-consent">Silence is consent</h2>
<p>People may choose to indicate their support for the actions taken with a +1
mail - quick and easy to read and reassuring for the implementer. However,
remember, in a lazy consensus world silence is the equivalent to support. This
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/voting.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/voting.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/voting.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
@@ -81,19 +82,19 @@
<p>Occasionally a "feel" for consensus is not enough. Sometimes we need to have a
measurable consensus. For example, when voting in new committers or to approve a
release. </p>
-<h2 id="preparing_for_a_vote">Preparing for a Vote</h2>
+<h2 id="preparing-for-a-vote">Preparing for a Vote</h2>
<p>Before calling a vote it is important to ensure that the community is given time to
discuss the upcoming vote. This will be done by posting an email to the list
indicating the intention to call a vote and the options available. By the time a
vote is called there should already be <a href="http://incubator.apache.org/openofficeorg/docs/governance/consensusBuilding.html">consensus in the community</a>. The vote
itself is, normally, a formality.</p>
-<h2 id="calling_a_vote">Calling a Vote</h2>
+<h2 id="calling-a-vote">Calling a Vote</h2>
<p>Once it is time to call the vote a mail is posted with a subject starting with
"[VOTE]". This enables the community members to ensure they do not miss an important
vote thread. It also indicates that this is not consensus building but a formal
vote. The initiator is responsible for the vote. That means also to count the votes
and present the results. Everyone has 1 vote.</p>
-<h3 id="casting_your_vote">Casting Your Vote</h3>
+<h3 id="casting-your-vote">Casting Your Vote</h3>
<p>The notation used in voting is:</p>
<p>+1 (means I vote positive)
You can say why you vote positive but it's not a must-have.</p>
@@ -101,7 +102,7 @@ and present the results. Everyone has 1
<p>-1 (means I vote negative because of the following reason)
Yes, you must support your objection and provide an alternative course of action
that you are willing and able to implement (where appropriate).</p>
-<h4 id="example_for_a_vote_mail">Example for a vote mail:</h4>
+<h4 id="example-for-a-vote-mail">Example for a vote mail:</h4>
<div class="codehilite"><pre><span class="err">Address:</span> <span class="kd">private</span><span class="err">@</span>
<span class="err">Subject:</span> <span class="err">[VOTE]</span> <span class="err">John</span> <span class="err">Doe</span> <span class="err">should</span> <span class="err">become</span> <span class="err">a</span> <span class="err">regular</span> <span class="err">committer</span>
@@ -118,7 +119,7 @@ and present the results. Everyone has 1
</pre></div>
-<h4 id="example_for_a_reply_mail">Example for a reply mail:</h4>
+<h4 id="example-for-a-reply-mail">Example for a reply mail:</h4>
<div class="codehilite"><pre><span class="n">Text:</span>
<span class="o">+</span><span class="mi">1</span>
@@ -126,7 +127,7 @@ and present the results. Everyone has 1
</pre></div>
-<h4 id="example_for_a_result_mail">Example for a result mail:</h4>
+<h4 id="example-for-a-result-mail">Example for a result mail:</h4>
<div class="codehilite"><pre><span class="n">Subject:</span> <span class="p">[</span><span class="n">VOTE</span><span class="p">][</span><span class="n">RESULTS</span><span class="p">]</span> <span class="n">John</span> <span class="n">Doe</span> <span class="n">should</span> <span class="n">become</span> <span class="n">a</span> <span class="n">regular</span> <span class="n">committer</span>
<span class="n">Text:</span>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/get-involved.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/get-involved.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/get-involved.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
@@ -102,7 +103,7 @@ the community. The project team and the
therefore welcome and encourage participation, and attempt to make it
as easy as possible for people to get involved. </p>
<p>We maintain a list of specific areas where we need volunteers on our <a href="https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted">Help Wanted</a> page of the wiki.</p>
-<h2 id="mailing_lists">Mailing lists</h2>
+<h2 id="mailing-lists">Mailing lists</h2>
<p>Your first engagement with the project should be to subscribe to our
<a href="/openofficeorg/mailing-lists.html">mailing lists</a>.</p>
</div>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/index.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/index.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/index.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/license.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/license.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/license.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/mailing-lists.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/mailing-lists.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/mailing-lists.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/native-lang.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/native-lang.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/native-lang.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/people.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/people.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/people.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/ppmc-faqs.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/ppmc-faqs.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/ppmc-faqs.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/release-process.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/release-process.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/release-process.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
@@ -78,7 +79,7 @@
<div id="contenta">
<h1 class="title">Release Process</h1>
- <h3 id="incubator_release_steps">Incubator Release Steps</h3>
+ <h3 id="incubator-release-steps">Incubator Release Steps</h3>
<ol>
<li>Environment setup for releasing artifacts (same for SNAPSHOTs and releases) -</li>
<li>
@@ -135,7 +136,9 @@
</p>
<p><em>If you cancel a release:prepare before it updates the pom.xml versions, then use the release:clean goal to just remove the extra files that were created.</em></p>
<ol>
-<li>Verify that the release process completed as expected<ol>
+<li>
+<p>Verify that the release process completed as expected</p>
+<ol>
<li>The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number.</li>
<li>
<p>If other formatting changes have been made you should review the changes and then commit them - <br />
@@ -198,21 +201,21 @@
</ol>
</li>
<li>
+<p>Put the release candidate up for a vote</p>
<ol>
<li>Create a VOTE email thread on rave-dev@ to record votes as replies, like <a href="release-vote.txt">this</a></li>
<li>Create a DISCUSS email thread on rave-dev@ for any vote questions, <a href="release-discuss.txt">this</a></li>
<li>Perform a review of the release and cast your vote. See the following for more details on Apache releases </li>
</ol>
-<p>Put the release candidate up for a vote</p>
<p><a href="http://www.apache.org/dev/release.html">http://www.apache.org/dev/release.html</a><br />
<a href="http://incubator.apache.org/guides/releasemanagement.html">http://incubator.apache.org/guides/releasemanagement.html</a></p>
<ol>
<li>A -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea to rollback the release if a -1 vote is received. See - Recovering from a vetoed release</li>
<li>
+<p>After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes, then post the results to the vote thread by -</p>
<ol>
<li>reply to the initial email and prepend to the original subject -</li>
</ol>
-<p>After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes, then post the results to the vote thread by -</p>
<p>[RESULTS]</p>
<ol>
<li>Include a list of everyone who voted +1, 0 or -1.</li>
@@ -242,14 +245,14 @@
<p>Finalizing a release</p>
</li>
<li>
+<p>Promote the staged nexus artifacts -</p>
<ol>
<li>https://repository.apache.org/index.html</li>
<li>Enterprise --> Staging</li>
<li>Staging tab --> Name column --> org.apache.rave</li>
-<li>Right click on the closed staging repo (org.apache.rave-XXX) and select Promote.</li>
-</ol>
-<p>Promote the staged nexus artifacts -</p>
-<ol>
+<li>
+<p>Right click on the closed staging repo (org.apache.rave-XXX) and select Promote.</p>
+</li>
<li>
<p>Copy the distribution artifacts over to the distribution area</p>
<p>$ ssh ${user.name}@people.apache.org<br />
@@ -281,7 +284,7 @@
<li>Make a news announcement on the Rave homepage.</li>
<li>Make an announcement about the release on the rave-users@incubator.apache.org, rave-dev@incubator.apache.org, general@incubator.apache.org, and announce@apache.org list as per the Apache Announcement Mailing Lists page)</li>
</ol>
-<h4 id="recovering_from_a_vetoed_release">Recovering from a vetoed release</h4>
+<h4 id="recovering-from-a-vetoed-release">Recovering from a vetoed release</h4>
<ol>
<li>
<p>Reply to the initial vote email and prepend to the original subject -</p>
@@ -320,7 +323,7 @@
</li>
<li>Spin another release candidate!</li>
</ol>
-<h4 id="verifying_release_signatures">Verifying release signatures</h4>
+<h4 id="verifying-release-signatures">Verifying release signatures</h4>
<p>On unix platforms the following command can be executed -</p>
<div class="codehilite"><pre> for file in `find . -type f -iname '*.asc'`
do
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/security.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/security.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/security.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
@@ -78,7 +79,7 @@
<div id="contenta">
<h1 class="title">Security Reports</h1>
- <h2 id="reporting_new_security_problems_with_apache_openofficeorg">Reporting New Security Problems with Apache OpenOffice.org</h2>
+ <h2 id="reporting-new-security-problems-with-apache-openofficeorg">Reporting New Security Problems with Apache OpenOffice.org</h2>
<p>The Apache Software Foundation takes a very active stance in eliminating security problems with Apache OpenOffice.org</p>
<p>We strongly encourage folks to report such problems to our private security mailing list first, before disclosing them in a public forum.</p>
<p><strong>Please note that the security mailing list should only be used for reporting undisclosed security vulnerabilities in Apache OpenOffice.org and managing
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/source.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/source.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/source.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/svn-basics.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/svn-basics.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/svn-basics.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
@@ -94,7 +95,7 @@
<h2 id="overview">Overview</h2>
<p>You begin using Subversion by copying a directory from a remote repository to a local directory on your file system. This is known as a checkout of a working copy.</p>
<p>Subversion uses a copy-modify-merge model meaning that you can add and edit files and directories in your working copy like any other files on your system, but you should use subversion commands for everything else such as <code>svn copy</code> and <code>svn move</code> instead of the operating system commands.</p>
-<h2 id="sub-commands_and_abbreviations">Sub-commands and Abbreviations</h2>
+<h2 id="sub-commands-and-abbreviations">Sub-commands and Abbreviations</h2>
<p>Subversion commands can be run from a command shell such as Bash on Linux. The subversion client command is <code>svn</code> followed by optional sub-commands, options, and arguments.</p>
<p>Show the program version and modules</p>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="o">--</span><span class="n">version</span>
@@ -122,14 +123,14 @@
<li><code>status</code> - Print the status of working copy files and directories</li>
<li><code>update</code> - Bring changes from the repository into your working copy</li>
</ul>
-<h2 id="client_configuration">Client Configuration</h2>
+<h2 id="client-configuration">Client Configuration</h2>
<p>Committers need to <a href="http://www.apache.org/dev/version-control.html#https-svn-config">configure their Subversion client</a> to handle the differences in line endings of text files on different operating systems.</p>
<p>There are instances where Subversion may need to open an editor. You need to have the environment variable EDITOR set to the editor you would like to use. To set it for the current terminal session in Bash (your path may differ):</p>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">export</span> <span class="n">EDITOR</span><span class="o">=</span><span class="sr">/usr/</span><span class="n">bin</span><span class="o">/</span><span class="n">vim</span>
</pre></div>
-<h2 id="repository_layout">Repository Layout</h2>
+<h2 id="repository-layout">Repository Layout</h2>
<p>The OOo repository layout uses the following top-level directories <code>branches</code>, <code>site</code>, <code>tags</code>, and <code>trunk</code>.</p>
<ul>
<li><code>branches</code> - Contains branches used for continued development of a specific version, experimental versions, or for developing features to be merged into the trunk or a branch later. (needs examples)</li>
@@ -138,7 +139,7 @@
<li><code>trunk</code> - Contains the current source code.
For more information see the <a href="http://www.apache.org/dev/contributors.html#svnbasics">Contributors Tech Guide</a>.</li>
</ul>
-<h2 id="getting_the_source_code">Getting the source code</h2>
+<h2 id="getting-the-source-code">Getting the source code</h2>
<p>From the parent directory of where you want the working copy. In this example the <code>ooo-trunk</code> directory will be created if it does not exist.</p>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">co</span> <span class="n">https:</span><span class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/repos/</span><span class="n">asf</span><span class="sr">/incubator/ooo</span><span class="o">/</span><span class="n">trunk</span> <span class="n">ooo</span><span class="o">-</span><span class="n">trunk</span>
<span class="n">A</span> <span class="n">ooo</span><span class="o">-</span><span class="n">trunk</span><span class="o">/</span><span class="n">tools</span>
@@ -153,7 +154,7 @@ For more information see the <a href="ht
<p>"A" indicates file or directory is "Added" to working copy</p>
-<h2 id="basic_work_cycle">Basic Work Cycle</h2>
+<h2 id="basic-work-cycle">Basic Work Cycle</h2>
<ul>
<li>Update your working copy - For this you use the <code>svn update</code> command</li>
<li>Make changes - For this you may edit files in an editor, or use the <code>svn add</code>, <code>svn delete</code>, <code>svn copy</code>, <code>svn-move</code> commands</li>
@@ -162,7 +163,7 @@ For more information see the <a href="ht
<li>Resolve Conflicts - There is a chance others have committed changes while you have been changing your working copy. You should run the <code>svn update</code> command to bring your copy up to date. This may create a local conflict where someone may have added a file with a name that you also want to add, or may have made changes to the same line of a file as you. For this use the <code>svn resolve</code> command.</li>
<li>Publish Changes - For this you use the <code>svn commit</code> command</li>
</ul>
-<h3 id="adding_a_file">Adding a File</h3>
+<h3 id="adding-a-file">Adding a File</h3>
<p>After creating the file "test-file.txt" in the working copy.</p>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">status</span>
<span class="p">?</span> <span class="n">test</span><span class="o">-</span><span class="n">file</span><span class="o">.</span><span class="n">txt</span>
@@ -170,7 +171,7 @@ For more information see the <a href="ht
<p>? indicates test-file.txt is not under version control</p>
-<h3 id="scheduling_a_file_for_addition_to_repository">Scheduling a file for addition to repository</h3>
+<h3 id="scheduling-a-file-for-addition-to-repository">Scheduling a file for addition to repository</h3>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">add</span> <span class="n">test</span><span class="o">-</span><span class="n">file</span><span class="o">.</span><span class="n">txt</span>
<span class="n">A</span> <span class="n">test</span><span class="o">-</span><span class="n">file</span><span class="o">.</span><span class="n">txt</span>
@@ -180,7 +181,7 @@ For more information see the <a href="ht
<p>"A" indicates file is scheduled for addition</p>
-<h3 id="running_a_diff">Running a diff</h3>
+<h3 id="running-a-diff">Running a diff</h3>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">diff</span>
<span class="n">Index:</span> <span class="n">test</span><span class="o">-</span><span class="n">file</span><span class="o">.</span><span class="n">txt</span>
<span class="o">===================================================================</span>
@@ -196,7 +197,7 @@ For more information see the <a href="ht
</pre></div>
-<h3 id="committing_a_file">Committing a file</h3>
+<h3 id="committing-a-file">Committing a file</h3>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">commit</span> <span class="n">test</span><span class="o">-</span><span class="n">file</span><span class="o">.</span><span class="n">txt</span> <span class="o">-</span><span class="n">m</span> <span class="s">"added test-file.txt"</span>
<span class="n">Adding</span> <span class="n">test</span><span class="o">-</span><span class="n">file</span><span class="o">.</span><span class="n">txt</span>
<span class="n">Transmitting</span> <span class="n">file</span> <span class="n">data</span> <span class="o">.</span>
@@ -204,7 +205,7 @@ For more information see the <a href="ht
</pre></div>
-<h3 id="update_the_working_copy">Update the working copy</h3>
+<h3 id="update-the-working-copy">Update the working copy</h3>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">update</span>
<span class="n">U</span> <span class="n">test</span><span class="o">-</span><span class="n">file</span><span class="o">.</span><span class="n">txt</span>
<span class="n">Updated</span> <span class="n">to</span> <span class="n">revision</span> <span class="mi">3</span><span class="o">.</span>
@@ -217,7 +218,7 @@ For more information see the <a href="ht
</pre></div>
-<h3 id="check_the_status">Check the Status</h3>
+<h3 id="check-the-status">Check the Status</h3>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">status</span>
<span class="n">M</span> <span class="n">test</span><span class="o">-</span><span class="n">file</span><span class="o">.</span><span class="n">txt</span>
</pre></div>
@@ -236,7 +237,7 @@ For more information see the <a href="ht
</pre></div>
-<h3 id="resolving_conflicts">Resolving Conflicts</h3>
+<h3 id="resolving-conflicts">Resolving Conflicts</h3>
<p>Suppose someone edits the same line as you before you commit</p>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">update</span>
<span class="n">Conflict</span> <span class="n">discovered</span> <span class="n">in</span> <span class="s">'test-file.txt'</span><span class="o">.</span>
@@ -271,7 +272,7 @@ Select: (p) postpone, (df) diff-full, (e
<p>"G" indicates "merGed"</p>
-<h3 id="committing_the_changes">Committing the Changes</h3>
+<h3 id="committing-the-changes">Committing the Changes</h3>
<p>Only Committers can commit directly to the repository. The following example shows using your Apache ID and password.</p>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">commit</span> <span class="n">test</span><span class="o">-</span><span class="n">file</span><span class="o">.</span><span class="n">txt</span> <span class="o">--</span><span class="n">username</span> <span class="n">your</span><span class="o">-</span><span class="n">name</span> <span class="o">--</span><span class="n">password</span> <span class="n">your</span><span class="o">-</span><span class="n">password</span> <span class="o">\</span>
<span class="o">-</span><span class="n">m</span> <span class="s">"added new line"</span>
@@ -282,7 +283,7 @@ Select: (p) postpone, (df) diff-full, (e
<p>For further information see the <a href="http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html">Basic Work Cycle</a> page from <a href="http://svnbook.red-bean.com">Subversion Book</a>.</p>
-<h2 id="committing_changes_by_others">Committing Changes By Others</h2>
+<h2 id="committing-changes-by-others">Committing Changes By Others</h2>
<p>See the <a href="http://www.apache.org/dev/committers.html#applying-patches">Applying Patches</a> section of the Committer FAQ page.</p>
<p>Example similar to one on Committer FAQ:</p>
<div class="codehilite"><pre><span class="n">Issue</span> <span class="c1">#43835:</span>
@@ -292,14 +293,14 @@ Select: (p) postpone, (df) diff-full, (e
<p>Using the <code>-m (--message)</code> option only allows a single line log message. To commit a multi-line message use the <code>-F (--file)</code> option (with a previously created file) or use neither -m or -F and an editor will be started.</p>
-<h2 id="creating_and_submitting_patches">Creating and Submitting Patches</h2>
+<h2 id="creating-and-submitting-patches">Creating and Submitting Patches</h2>
<p>See the <a href="http://www.apache.org/dev/contributors.html#patches">Sending in Patches</a> section on the Contributors Tech Guide page.</p>
<p>Create the patch file from <code>svn diff</code> where <code>your-patch-name.patch</code> is the full path to the patch file to create.</p>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">diff</span> <span class="o">></span> <span class="n">your</span><span class="o">-</span><span class="n">patch</span><span class="o">-</span><span class="n">name</span><span class="o">.</span><span class="n">patch</span>
</pre></div>
-<h2 id="further_information">Further Information</h2>
+<h2 id="further-information">Further Information</h2>
<p>For more information see: </p>
<ul>
<li><a href="http://subversion.apache.org">Apache Subversion Project</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/terms.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/terms.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/terms.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/trademarks.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/trademarks.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/trademarks.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/website-local.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/website-local.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/website-local.html Mon Mar 19 22:22:36 2012
@@ -48,6 +48,7 @@
<li><a href="/openofficeorg/get-involved.html">Get Involved</a></li>
<li><a href="/openofficeorg/mailing-lists.html">Mailing Lists</a></li>
<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/openofficeorg/native-lang.html">Native Language Information</a></li>
<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
<li><a href="/openofficeorg/people.html">People</a></li>
<li><a href="/openofficeorg/community-faqs.html">Community FAQs</a></li>
@@ -60,14 +61,14 @@
<li><a href="/openofficeorg/security.html">Security Reports</a></li>
<li><a href="/openofficeorg/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project_management_ppmc">Project Management PPMC</h1>
+<h1 id="project-management-ppmc">Project Management PPMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
<li><a href="http://incubator.apache.org/projects/openofficeorg.html">Incubation Status</a></li>
<li><a href="/openofficeorg/ppmc-faqs.html">PPMC FAQs</a><br />
</li>
</ul>
-<h1 id="the_apache_software_foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
<li><a href="http://www.apache.org/">Website</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
@@ -78,7 +79,7 @@
<div id="contenta">
<h1 class="title">Website Development</h1>
- <h2 id="two_websites">Two Websites</h2>
+ <h2 id="two-websites">Two Websites</h2>
<p>The Apache OpenOffice project maintains two websites:</p>
<ul>
<li>The <a href="http://incubator.apache.org/openofficeorg/">project website</a> (from which you are viewing this page)</li>
@@ -93,11 +94,11 @@ the staging sites for these areas, respe
</ul>
<p>Additionally, the project website uses <a href="http://daringfireball.net/projects/markdown/">Markdown</a> for page contents.
The "legacy" OpenOffice.org site uses html.</p>
-<h2 id="version_control">Version Control</h2>
+<h2 id="version-control">Version Control</h2>
<p>We use <a href="http://subversion.apache.org">Apache Subversion</a> for version control. You can <a href="http://svn.apache.org/viewvc/incubator/ooo/site/trunk">browse the project
repository</a> or <a href="https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/">browse the user portal repository</a> in your web browser.</p>
-<h2 id="making_changes_to_the_sites">Making Changes to the Sites</h2>
-<h3 id="using_svn">Using SVN</h3>
+<h2 id="making-changes-to-the-sites">Making Changes to the Sites</h2>
+<h3 id="using-svn">Using SVN</h3>
<p>You can make changes to either site using svn (subversion). This typically involves
doing an svn checkout, making changes to files and then either committing your changes
if you are an "Apache committer", or submitting a "patch" (an svn "diff" file) if you are a contributor but
@@ -106,13 +107,13 @@ patches. (See also, the <a href="http://
<a href="mailto:ooo-dev@incubator.apache.org">Apache OpenOffice developer</a> list.</p>
<p>SVN commits will commit your changes to the "staging area". you will need to
"publish" your changes to make them active on the "production" site.</p>
-<h3 id="using_the_apache_cms_bookmarklet">Using the Apache CMS Bookmarklet</h3>
+<h3 id="using-the-apache-cms-bookmarklet">Using the Apache CMS Bookmarklet</h3>
<p>Quick editing of the site is available for committers and contributors using the Apache CMS
<a href="https://cms.apache.org/#bookmark">from your browser.</a> If you are a commtter and use the bookmarklet, you should use
your Apache credentials to log in, make changes and submit them to staging.
If you are a contributor, and not a committer, you can still use the bookmarklet.
See additional details in the <a href="http://www.apache.org/dev/cmsref.html#non-committer">Apache CMS Reference</a>.</p>
-<h2 id="publishing_changes">Publishing Changes</h2>
+<h2 id="publishing-changes">Publishing Changes</h2>
<p>As previously noted, changes you make, either through an svn commit or using the CMS GUI tool,
are enacted on the staging sites. Only Apache "committers" can actually publish sites. </p>
<ul>
@@ -125,7 +126,7 @@ after reviewing it in staging from a "co
</ul>
<p>Generally speaking, unless you have established a full <strong>Complete Local Development</strong> environment as described in the next
section, you will likely be running <strong>publish.pl</strong> from your "people.apache.org" account.</p>
-<h2 id="preparations_for_complete_local_development">Preparations for Complete Local Development</h2>
+<h2 id="preparations-for-complete-local-development">Preparations for Complete Local Development</h2>
<p>The following information provides instructions on doing website development on your local computer.
These instructions assume you have setup a webserver in your local environment. Details are
provided on setting up the resources needed to process "Markdown" on your local server
@@ -137,49 +138,49 @@ and how to publish to the production Apa
<li><a href="#submitting_your_results">Submitting Your Results</a> - How to contribute your edits.</li>
</ul>
<h3 id="setup">Setup</h3>
-<h4 id="create_a_directory_on_your_computer_for_the_apache_cms_work_with_both_the_podlings">Create a directory on your computer for the Apache CMS work with both the podling's</h4>
+<h4 id="create-a-directory-on-your-computer-for-the-apache-cms-work-with-both-the-podlings">Create a directory on your computer for the Apache CMS work with both the podling's</h4>
<p>incubator site and the migrating openoffice.org website.</p>
<div class="codehilite"><pre><span class="nb">mkdir</span> <span class="n">ooo</span><span class="o">-</span><span class="n">web</span>
<span class="n">cd</span> <span class="n">ooo</span><span class="o">-</span><span class="n">web</span>
</pre></div>
-<h4 id="download_the_svn_repos_for_the_aooo_site">Download the svn repos for the AOOo site.</h4>
+<h4 id="download-the-svn-repos-for-the-aooo-site">Download the svn repos for the AOOo site.</h4>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">co</span> <span class="n">https:</span><span class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/repos/</span><span class="n">asf</span><span class="sr">/incubator/ooo/site/</span><span class="n">trunk</span> <span class="n">site</span>
</pre></div>
-<h4 id="download_the_svn_repos_for_the_migrated_openofficeorg_website">Download the svn repos for the migrated OpenOffice.org website.</h4>
+<h4 id="download-the-svn-repos-for-the-migrated-openofficeorg-website">Download the svn repos for the migrated OpenOffice.org website.</h4>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">co</span> <span class="n">https:</span><span class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/repos/</span><span class="n">asf</span><span class="sr">/incubator/ooo/ooo-site/</span><span class="n">trunk</span> <span class="n">ooo</span><span class="o">-</span><span class="n">site</span>
</pre></div>
-<h4 id="download_the_svn_repos_for_the_apache_cms">Download the svn repos for the Apache CMS.</h4>
+<h4 id="download-the-svn-repos-for-the-apache-cms">Download the svn repos for the Apache CMS.</h4>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">co</span> <span class="n">https:</span><span class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/repos/i</span><span class="n">nfra</span><span class="sr">/websites/cms</span><span class="o">/</span> <span class="n">cms</span>
</pre></div>
<p>You will have three sub-directories in your local website directory - <code>site</code>, <code>ooo-site</code>, and <code>cms</code>.</p>
-<h4 id="install_python_dependencies">Install Python dependencies.</h4>
+<h4 id="install-python-dependencies">Install Python dependencies.</h4>
<p>Adapted from the <a href="http://www.apache.org/dev/cmsref.html#local-build">Apache CMS Reference</a></p>
<p>The easiest way to install the dependencies is to use Python setuptools.</p>
-<h4 id="check_your_version_of_python">Check your version of Python</h4>
+<h4 id="check-your-version-of-python">Check your version of Python</h4>
<div class="codehilite"><pre><span class="n">python</span> <span class="o">--</span><span class="n">version</span>
</pre></div>
-<h4 id="follow_the_installation_instructions_for_setuptools4">Follow the installation instructions for <a href="http://pypi.python.org/pypi/setuptools">setuptools</a>.</h4>
-<h4 id="install_dependencies">Install dependencies</h4>
+<h4 id="follow-the-installation-instructions-for-setuptools">Follow the installation instructions for <a href="http://pypi.python.org/pypi/setuptools">setuptools</a>.</h4>
+<h4 id="install-dependencies">Install dependencies</h4>
<div class="codehilite"><pre><span class="n">sudo</span> <span class="n">easy_install</span> <span class="n">Pygments</span>
<span class="n">sudo</span> <span class="n">easy_install</span> <span class="n">ElementTree</span>
<span class="n">sudo</span> <span class="n">easy_install</span> <span class="n">Markdown</span>
</pre></div>
-<h3 id="directory_layout">Directory Layout</h3>
-<h4 id="content_directories">Content directories</h4>
+<h3 id="directory-layout">Directory Layout</h3>
+<h4 id="content-directories">Content directories</h4>
<p>The <code>site/content/openofficeorg</code> and <code>ooo-site/content/</code> directories contain web content - markdown, html, javascript, css, images and other files. Files that do not fit recognized patterns from <code>site/lib/path.pm</code> or <code>ooo-site/lib/path.pm</code> are copied as is to the web site during the build.</p>
-<h4 id="templates_directory">Templates directory</h4>
+<h4 id="templates-directory">Templates directory</h4>
<p>The <code>site/templates</code> and <code>ooo-site/templates</code> directories contain the html skeletons used during the site build.</p>
<ul>
<li><code>skeleton.html</code> - our current html page template.</li>
@@ -187,13 +188,13 @@ and how to publish to the production Apa
<li><code>html_page.html</code> - wrapping for html pages.</li>
<li><code>single_narrative.html</code> - extends skeleton.html.</li>
</ul>
-<h4 id="lib_directory">Lib directory</h4>
+<h4 id="lib-directory">Lib directory</h4>
<p>The <code>site/lib</code> and <code>ooo-site/lib</code> directories contain two python modules that determine how content files are processed during the site build.</p>
<ul>
<li><code>path.pm</code> - maps file patterns like <code>.mdtext</code> into the view building routines. We can expand to cover other patterns.</li>
<li><code>view.pm</code> - a set of python subroutines for converting content into web pages.</li>
</ul>
-<h4 id="build_tools">Build tools</h4>
+<h4 id="build-tools">Build tools</h4>
<p>You can find the CMS build tools in the <code>cms</code> directory.</p>
<ul>
<li><code>cms/build/</code> - perl scripts for building the site and markdown extensions.</li>
@@ -201,30 +202,30 @@ and how to publish to the production Apa
<li><code>cms/webgui/</code> - the webgui behind the <code>bookmarklet</code>.</li>
</ul>
<p>These can be extended locally. Before any changes become part of our process they will need to be cleared with Apache Infrastructure. We'll need to submit patches. These should be additive or be bug fixes.</p>
-<h3 id="local_development">Local Development</h3>
-<h4 id="edit_the_site">Edit the site</h4>
+<h3 id="local-development">Local Development</h3>
+<h4 id="edit-the-site">Edit the site</h4>
<p>Using your favorite editors edit the site content, templates, and lib scripts.</p>
-<h4 id="python_markdown_daemon">Python Markdown Daemon</h4>
+<h4 id="python-markdown-daemon">Python Markdown Daemon</h4>
<p>Start the Python Markdown daemon.</p>
<div class="codehilite"><pre><span class="n">export</span> <span class="n">MARKDOWN_SOCKET</span><span class="o">=</span><span class="sb">`pwd`</span><span class="o">/</span><span class="n">markdown</span><span class="o">.</span><span class="nb">socket</span> <span class="n">PYTHONPATH</span><span class="o">=</span><span class="sb">`pwd`</span>
<span class="n">python</span> <span class="n">cms</span><span class="sr">/build/m</span><span class="n">arkdownd</span><span class="o">.</span><span class="n">py</span>
</pre></div>
-<h4 id="build_the_sites">Build the sites.</h4>
+<h4 id="build-the-sites">Build the sites.</h4>
<div class="codehilite"><pre><span class="n">cms</span><span class="sr">/build/</span><span class="n">build_site</span><span class="o">.</span><span class="n">pl</span> <span class="o">--</span><span class="n">source</span><span class="o">-</span><span class="n">base</span> <span class="n">site</span> <span class="o">--</span><span class="n">target</span><span class="o">-</span><span class="n">base</span> <span class="n">www</span>
<span class="n">cms</span><span class="sr">/build/</span><span class="n">build_site</span><span class="o">.</span><span class="n">pl</span> <span class="o">--</span><span class="n">source</span><span class="o">-</span><span class="n">base</span> <span class="n">ooo</span><span class="o">-</span><span class="n">site</span> <span class="o">--</span><span class="n">target</span><span class="o">-</span><span class="n">base</span> <span class="n">www</span>
</pre></div>
-<h4 id="copy_the_site_to_your_computers_web_server">Copy the site to your computer's web server.</h4>
+<h4 id="copy-the-site-to-your-computers-web-server">Copy the site to your computer's web server.</h4>
<p>On my Mac:</p>
<div class="codehilite"><pre><span class="n">sudo</span> <span class="n">scp</span> <span class="o">-</span><span class="n">rp</span> <span class="n">www</span><span class="sr">/content /</span><span class="n">Library</span><span class="sr">/WebServer/</span><span class="n">Documents</span><span class="o">/.</span>
</pre></div>
<p>The site is then available with <a href="http://localhost/openofficeorg">http://localhost/openofficeorg/</a> or <a href="http://localhost/">http://localhost/</a></p>
-<h3 id="submitting_your_results">Submitting your results.</h3>
+<h3 id="submitting-your-results">Submitting your results.</h3>
<h4 id="committer">Committer</h4>
<p>Do the appropriate combination of svn status, svn add, and svn commits. Commits will cause staging rebuilds.
See <a href="https://cms.apache.org/#bookmark">How to Edit the OpenOffice.org Website</a></p>