This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch preview/refresh-staging
in repository https://gitbox.apache.org/repos/asf/openoffice-project.git
The following commit(s) were added to refs/heads/preview/refresh-staging by
this push:
new 9dab842 Automatic Site Publish by Buildbot
9dab842 is described below
commit 9dab84247bf91be801cba1d44ae585d4625a9af7
Author: buildbot <[email protected]>
AuthorDate: Tue Jun 29 18:34:41 2021 +0000
Automatic Site Publish by Buildbot
---
output/contributing-code.html | 2 +-
output/developer-faqs.html | 4 ++--
output/docs/governance/voting.html | 2 +-
output/get-involved-de.html | 6 +++---
output/get-involved.html | 10 +++++-----
output/get-it-here.html | 6 +++---
output/index.html | 30 +++++++++++++++---------------
output/mailing-lists.html | 4 ++--
output/orientation/decision-making.html | 4 ++--
output/orientation/index.html | 2 +-
output/orientation/infrastructure.html | 4 ++--
output/orientation/intro-contributing.html | 12 ++++++------
output/orientation/intro-development.html | 8 ++++----
output/orientation/intro-doc.html | 2 +-
output/orientation/intro-marketing.html | 16 ++++++++--------
output/orientation/intro-qa.html | 2 +-
output/people.html | 2 +-
output/pmc-faqs.html | 4 ++--
output/qa.html | 12 ++++++------
output/source.html | 2 +-
output/students.html | 6 +++---
output/terms.html | 2 +-
output/trademarks.html | 2 +-
output/translate.html | 6 +++---
output/website-local.html | 6 +++---
output/website-native.html | 4 ++--
26 files changed, 80 insertions(+), 80 deletions(-)
diff --git a/output/contributing-code.html b/output/contributing-code.html
index 2ecda24..abed1a9 100644
--- a/output/contributing-code.html
+++ b/output/contributing-code.html
@@ -102,7 +102,7 @@ if one of the first things we question you about is the
license and the pedigree
<li>The code must be under the Apache License 2.0 and it must be
contributed by or with permission of the original author(s) of the code.
Dependencies on third party libraries should be
-discussed on the <a
href="https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public";>dev
list</a>,
+discussed on the <a
href="/mailing-lists.html#development-mailing-list-public">dev list</a>,
to see how these can be brought into conformance with
<a href="https://www.apache.org/legal/resolved.html#category-a";>ASF
policy</a>.</li>
<li>The code must be of sufficient quality and value to the project that our
programmer (Committers) approve it, or at least don't reject it.</li>
diff --git a/output/developer-faqs.html b/output/developer-faqs.html
index 2cbb187..fe793ad 100644
--- a/output/developer-faqs.html
+++ b/output/developer-faqs.html
@@ -100,11 +100,11 @@
development</a>. Or, take
a look at information posted on the <a
href="https://wiki.openoffice.org/wiki/Main_Page";>Apache OpenOffice wiki</a>
under <em>Documentation - For Developers</em>.</p>
-<p>Of course, you will need the <a
href="https://openoffice.apache.org/source.html";>source code</a> to do
anything. We recommend building in your own environment as a first step.</p>
+<p>Of course, you will need the <a href="/source.html">source code</a> to do
anything. We recommend building in your own environment as a first step.</p>
<p>You don't have to be an actual committer to submit code. You can submit
patches through
the Apache OpenOffice Bugzilla issue reporting system. You simply need to file
an issue
and supply your patch as an attachment to the issue.</p>
-<p>Please also see our <a
href="https://openoffice.apache.org/orientation/index.html";>Orientation
Modules</a> for information on how the project works and identifying
outstanding development tasks.</p>
+<p>Please also see our <a href="/orientation/index.html">Orientation
Modules</a> for information on how the project works and identifying
outstanding development tasks.</p>
<h2 id="ive-just-been-voted-in-as-a-committer-what-do-i-need-to-do">I've just
been voted in as a Committer. What do I need to do?<a class="headerlink"
href="#ive-just-been-voted-in-as-a-committer-what-do-i-need-to-do"
title="Permalink">¶</a></h2>
<p>First, congratulations. Your contributions to the project have been noted
and we
hope that as a Committer you will be even more active.</p>
diff --git a/output/docs/governance/voting.html
b/output/docs/governance/voting.html
index decf70d..ec7d8af 100644
--- a/output/docs/governance/voting.html
+++ b/output/docs/governance/voting.html
@@ -100,7 +100,7 @@ release.</p>
<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://openoffice.apache.org/docs/governance/consensusBuilding.html";>consensus
in the community</a>. The vote
+vote is called there should already be <a
href="/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<a class="headerlink"
href="#calling-a-vote" title="Permalink">¶</a></h2>
<p>Once it is time to call the vote a mail is posted with a subject starting
with
diff --git a/output/get-involved-de.html b/output/get-involved-de.html
index 08fef7f..a565901 100644
--- a/output/get-involved-de.html
+++ b/output/get-involved-de.html
@@ -140,7 +140,7 @@ viele Jahre als unabhängiges Projekt entwickelt und
gepflegt, und jetzt mit
unseren Erfahrungen im Rahmen von Apache zusammengeführt.</p>
<p>Wenn dir die Entwicklung von Open Source-Projekten in der Apache Software
Foundation bereits
geläufig ist, dann kannst Du gleich mitmachen. Du musst lediglich die
-<a href="https://openoffice.apache.org/mailing-lists.html";>Mailing-Liste</a>
+<a href="/mailing-lists.html">Mailing-Liste</a>
eines Projekts abonnieren und Dich dort vorstellen. Wir
helfen dir bei diesem ersten Schritt.</p>
<hr/>
@@ -161,14 +161,14 @@ helfen dir bei diesem ersten Schritt.</p>
<hr/>
<p>Wenn Du aber zum ersten Mal hier bist oder eine systematischere
Heranführung wünschst, dann haben wir für Dich ein Paket von
Modulen für
-die <a
href="https://openoffice.apache.org/orientation/index.html";>Orientierung neuer
Helfer</a> vorbereitet, das Dich durch die wichtigsten
+die <a href="/orientation/index.html">Orientierung neuer Helfer</a>
vorbereitet, das Dich durch die wichtigsten
Aspekte von Apache OpenOffice und unserer Arbeitsweise führt.</p>
<p>Welchen Weg Du nimmst, bleibt Deine persönliche Entscheidung –
beide Wege
bleiben dir jeder Zeit offen.</p>
<p>Wir haben auf der Seite <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted";>»Hilfe
gesucht«</a> im Wiki auch eine Liste von
konkreten Arbeitsaufgaben, die in Angriff genommen werden sollten.</p>
<p>Wenn Du Student bist und zum Projekt im Rahmen Deines Studiums beitragen
-möchtest, werfe einen Blick auf unsere Seite <a
href="https://openoffice.apache.org/students.html";>»Empfehlungen für
Studenten«</a>.</p>
+möchtest, werfe einen Blick auf unsere Seite <a
href="/students.html">»Empfehlungen für Studenten«</a>.</p>
<p>
diff --git a/output/get-involved.html b/output/get-involved.html
index 0d9ced9..7a63860 100644
--- a/output/get-involved.html
+++ b/output/get-involved.html
@@ -93,7 +93,7 @@
<h1>Get Involved in Apache OpenOffice</h1>
- <p><a href="https://openoffice.apache.org/get-involved-de.html";>Diese
Seite in Deutsch</a></p>
+ <p><a href="/get-involved-de.html">Diese Seite in Deutsch</a></p>
<h2 id="help-needed">Help Needed<a class="headerlink" href="#help-needed"
title="Permalink">¶</a></h2>
<p>OpenOffice is currently looking for people with the following:</p>
<ul>
@@ -103,7 +103,7 @@
<li>Do you like contributing to open source projects?</li>
</ul>
<p>Come and join us in helping OpenOffice to thrive. Subscribe to the
-<a
href="http://openoffice.apache.org/mailing-lists.html#recruitment-mailing-list-public";>recruitment
mailing list</a>
+<a href="/mailing-lists.html#recruitment-mailing-list-public">recruitment
mailing list</a>
and introduce yourself. We'll help you get started.</p>
<h2 id="why-get-involved-with-the-openoffice-project">Why get involved with
the OpenOffice project?<a class="headerlink"
href="#why-get-involved-with-the-openoffice-project"
title="Permalink">¶</a></h2>
<p>Although many want to <a
href="http://www.openoffice.org/donations.html";>make a small donation</a>
@@ -150,11 +150,11 @@ people to get involved.</p>
years as an independent project, combined with our experience at Apache.</p>
<p>If you are familiar with Apache-style open source development then you
might just jump
in. Subscribe to the
-<a
href="http://openoffice.apache.org/mailing-lists.html#recruitment-mailing-list-public";>recruitment
mailing list</a>
+<a href="/mailing-lists.html#recruitment-mailing-list-public">recruitment
mailing list</a>
and introduce yourself. We'll help you get started.</p>
<p>If, however, you are new to Apache, or want a more methodical approach to
getting started,
then we have a set of graduated
-<a href="http://openoffice.apache.org/orientation/index.html";>New Volunteer
Orientation Modules</a>
+<a href="/orientation/index.html">New Volunteer Orientation Modules</a>
designed for new volunteers that takes you through a number of background
topics related
to OpenOffice and how we do things.</p>
<p>Which path you take is up to you and is a matter of personal preference.
You can even do both.</p>
@@ -162,7 +162,7 @@ to OpenOffice and how we do things.</p>
<a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted";>Help
Wanted</a>
page of the wiki.</p>
<p>If you are a student, looking to contribute to the project as part of your
school work,
-please also see our <a
href="http://openoffice.apache.org/students.html";>Advice for Students</a>
+please also see our <a href="/students.html">Advice for Students</a>
page.</p>
diff --git a/output/get-it-here.html b/output/get-it-here.html
index 774cefb..d3ef56a 100644
--- a/output/get-it-here.html
+++ b/output/get-it-here.html
@@ -101,9 +101,9 @@ following logo subject to the following conditions:</p>
<img alt="Download Apache OpenOffice here" height="100"
src="https://openoffice.apache.org/images/get-it-here/en.png"; width="300"/>
</a>
</p>
-<p>The logo file may be [found here] <a
href="https://openoffice.apache.org/images/get-it-here/en.png";>1</a>.</p>
+<p>The logo file may be [found here] <a
href="/images/get-it-here/en.png">1</a>.</p>
<p>If translations of the "Get it here!" text are required, send a request to
the
-[dev mailing list] <a
href="https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public";>2</a>
and we can make a translated version for you.</p>
+[dev mailing list] <a
href="/mailing-lists.html#development-mailing-list-public">2</a> and we can
make a translated version for you.</p>
<h2 id="conditions">Conditions:<a class="headerlink" href="#conditions"
title="Permalink">¶</a></h2>
<ol>
<li>
@@ -130,7 +130,7 @@ users from getting the latest version of Apache
OpenOffice.</p>
</li>
<li>
<p>Any use of this logo or any other Apache logo beyond the above
-requires explicit permission per the existing <a
href="https://openoffice.apache.org/trademarks.html";>trademark policy</a></p>
+requires explicit permission per the existing <a
href="/trademarks.html">trademark policy</a></p>
</li>
</ol>
<h2 id="example">Example<a class="headerlink" href="#example"
title="Permalink">¶</a></h2>
diff --git a/output/index.html b/output/index.html
index ff71582..ad20546 100644
--- a/output/index.html
+++ b/output/index.html
@@ -105,79 +105,79 @@ OpenOffice.org</a>.</p>
<h2 id="announcements">Announcements<a class="headerlink"
href="#announcements" title="Permalink">¶</a></h2>
<p><em>2021-05-04 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.10 is released!</em></p>
<ul>
-<li><a href="https://openoffice.apache.org/downloads.html";>Download Source and
SDK</a></li>
+<li><a href="/downloads.html">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.10+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2021-02-07 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.9 is released!</em></p>
<ul>
-<li><a href="https://openoffice.apache.org/downloads.html";>Download Source and
SDK</a></li>
+<li><a href="/downloads.html">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.9+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2020-11-10 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.8 is released!</em></p>
<ul>
-<li><a href="https://openoffice.apache.org/downloads.html";>Download Source and
SDK</a></li>
+<li><a href="/downloads.html">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.8+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2019-09-21 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.7 is released!</em></p>
<ul>
-<li><a href="https://openoffice.apache.org/downloads.html";>Download Source and
SDK</a></li>
+<li><a href="/downloads.html">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.7+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2018-11-18 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.6 is released!</em></p>
<ul>
-<li><a href="https://openoffice.apache.org/downloads.html";>Download Source and
SDK</a></li>
+<li><a href="/downloads.html">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.6+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2017-12-30 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.5 is released!</em></p>
<ul>
-<li><a
href="https://openoffice.apache.org/downloads.html#release-archives";>Download
Source and SDK</a></li>
+<li><a href="/downloads.html#release-archives">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.5+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2017-10-19 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.4 is released!</em></p>
<ul>
-<li><a
href="https://openoffice.apache.org/downloads.html#release-archives";>Download
Source and SDK</a></li>
+<li><a href="/downloads.html#release-archives">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.4+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2016-10-12 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.3 is released!</em></p>
<ul>
-<li><a
href="https://openoffice.apache.org/downloads.html#release-archives";>Download
Source and SDK</a></li>
+<li><a href="/downloads.html#release-archives">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2015-10-28 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.2 is released!</em></p>
<ul>
-<li><a
href="https://openoffice.apache.org/downloads.html#release-archives";>Download
Source and SDK</a></li>
+<li><a href="/downloads.html#release-archives">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2014-08-21 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.1 is released!</em></p>
<ul>
-<li><a
href="https://openoffice.apache.org/downloads.html#release-archives";>Download
Source and SDK</a></li>
+<li><a href="/downloads.html#release-archives">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.1+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2014-04-29 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.1.0 is released!</em></p>
<ul>
-<li><a
href="https://openoffice.apache.org/downloads.html#release-archives";>Download
Source and SDK</a></li>
+<li><a href="/downloads.html#release-archives">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2013-10-01 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.0.1 is released!</em></p>
<ul>
-<li><a
href="https://openoffice.apache.org/downloads.html#release-archives";>Download
Source and SDK</a></li>
+<li><a href="/downloads.html#release-archives">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0.1+Release+Notes";>Release
Notes</a></li>
</ul>
<p><em>2013-07-23 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 4.0.0 is released!</em></p>
<ul>
-<li><a
href="https://openoffice.apache.org/downloads.html#release-archives";>Download
Source and SDK</a></li>
+<li><a href="/downloads.html#release-archives">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/";>Download Binaries</a></li>
<li><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Notes";>Release
Notes</a></li>
</ul>
@@ -192,13 +192,13 @@ OpenOffice.org</a>.</p>
<p><em>2012-08-23 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 3.4.1 (incubating) is released!</em></p>
<ul>
<li><a
href="https://blogs.apache.org/OOo/entry/announcing_apache_openoffice_3_41";>Release
announcement</a></li>
-<li><a
href="https://openoffice.apache.org/downloads.html#release-archives";>Download
Source and SDK</a></li>
+<li><a href="/downloads.html#release-archives">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download";>Download Binaries</a></li>
</ul>
<p><em>2012-05-08 -- <a href="https://www.openoffice.org/";>Apache
OpenOffice</a> 3.4.0 (incubating) is released!</em></p>
<ul>
<li><a href="https://www.openoffice.org/news/aoo34.html";>Release
announcement</a></li>
-<li><a
href="https://openoffice.apache.org/downloads.html#release-archives";>Download
Source and SDK</a></li>
+<li><a href="/downloads.html#release-archives">Download Source and SDK</a></li>
<li><a href="https://www.openoffice.org/download/archive.html";>Download
Binaries</a></li>
</ul>
diff --git a/output/mailing-lists.html b/output/mailing-lists.html
index 0012795..251ad1f 100644
--- a/output/mailing-lists.html
+++ b/output/mailing-lists.html
@@ -148,7 +148,7 @@ additional help with a mailing list in any way including
reporting inappropriate
behavior, you can e-mail the list moderator at <em>xyz</em><a
href="mailto:[email protected]";>[email protected]</a>
where
<em>xyz</em> is a list name. Example: <a
href="mailto:[email protected]";>[email protected]</a>.</p>
<h2 id="participation-guidelines">Participation Guidelines<a
class="headerlink" href="#participation-guidelines"
title="Permalink">¶</a></h2>
-<p>We ask all mailing list participants to observe <a
href="http://openoffice.apache.org/list-conduct.html";>these conduct
guidelines</a>.</p>
+<p>We ask all mailing list participants to observe <a
href="/list-conduct.html">these conduct guidelines</a>.</p>
<p>Specifically note the request "Use sensible and concise e-mail subject
headings". On our
high-traffic lists, especially dev, we encourage the use of e-mail subject
tags that
indicate the topic of your post. Consistent use of such tags makes it more
likely that
@@ -299,7 +299,7 @@ people and tries to help to find the right part. This is a
low traffic list.</p>
<p>The project has several mailing lists for discussion about OpenOffice in
native
(non-English) languages.</p>
<p>Information about available Native Language mailing lists can be found in
the page
-describing <a href="http://openoffice.apache.org/native-lang.html";>native
language resources</a>.</p>
+describing <a href="/native-lang.html">native language resources</a>.</p>
<h2 id="legacy-openofficeorg-lists">Legacy OpenOffice.org Lists<a
class="headerlink" href="#legacy-openofficeorg-lists"
title="Permalink">¶</a></h2>
<p>As of March 16th, 2012 the legacy OpenOffice.org mailing lists have been
disabled.
Archived posts from these mailing lists are archived on <a
href="http://openoffice.markmail.org/";>MarkMail</a>.</p>
diff --git a/output/orientation/decision-making.html
b/output/orientation/decision-making.html
index a35bef0..370a73b 100644
--- a/output/orientation/decision-making.html
+++ b/output/orientation/decision-making.html
@@ -145,7 +145,7 @@ list.</p>
<p>Proposals</p>
<p>The convention is to send all proposals in their own new thread. (Don't
hide a proposal 10 posts deep in an existing thread). Put "[PROPOSAL]" in the
subject line or make it obvious that you are making a proposal.</p>
<p>Because the Volunteers are spread out all across the globe, in various time
zones, and many have day jobs or other commitments, the convention is to wait
<em>at least</em> 72 hours for feedback on a proposal.</p>
-<p>In cases where the proposer wants to act on their proposal, if there are no
objections, they should state this in the proposal. For example, "If there are
no objections voiced within 72 hours, I'll go ahead and make these changes".
This is called "stating lazy consensus". You can read more about lazy consensus
<a
href="https://openoffice.apache.org/docs/governance/lazyConsensus.html";>here</a>.</p>
+<p>In cases where the proposer wants to act on their proposal, if there are no
objections, they should state this in the proposal. For example, "If there are
no objections voiced within 72 hours, I'll go ahead and make these changes".
This is called "stating lazy consensus". You can read more about lazy consensus
<a href="/docs/governance/lazyConsensus.html">here</a>.</p>
</li>
<li>
<p>Voting, Consensus, and Vetoes</p>
@@ -163,7 +163,7 @@ list.</p>
<p>There is one disorder of community decision making that is common enough to
warrant a colorful name: <a href="http://bikeshed.com/";>bikeshedding</a>.
Follow the link and read more about this topic.</p>
</li>
<li>
-<p>To apply the above skills, be sure you are subscribed to the project's <a
href="https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public";>main
mailing list</a>. Keep your eye out for terms like "proposal", "lazy
consensus", "vote" or "veto" and see how they are used in practice. Compare
actual practice to the above descriptions. No, we're not perfect. But we work
best and have the most fun when we follow the above guidelines. And so will you
when you apply then [...]
+<p>To apply the above skills, be sure you are subscribed to the project's <a
href="/mailing-lists.html#development-mailing-list-public">main mailing
list</a>. Keep your eye out for terms like "proposal", "lazy consensus", "vote"
or "veto" and see how they are used in practice. Compare actual practice to the
above descriptions. No, we're not perfect. But we work best and have the most
fun when we follow the above guidelines. And so will you when you apply then in
your own list communicati [...]
</li>
</ol>
</li>
diff --git a/output/orientation/index.html b/output/orientation/index.html
index 7dc9e1b..4ba6890 100644
--- a/output/orientation/index.html
+++ b/output/orientation/index.html
@@ -116,7 +116,7 @@
<ul>
<li><a href="intro-development.html">Introduction to Development</a></li>
<li><a href="intro-qa.html">Introduction to QA</a></li>
-<li><a href="http://openoffice.apache.org/translate.html";>Introduction to
Localization</a> (How to Help Translate OpenOffice)</li>
+<li><a href="/translate.html">Introduction to Localization</a> (How to Help
Translate OpenOffice)</li>
<li><a href="intro-marketing.html">Introduction to Marketing</a></li>
<li><a href="intro-doc.html">Introduction to Documentation</a></li>
<li>Introduction to Website Content Authoring</li>
diff --git a/output/orientation/infrastructure.html
b/output/orientation/infrastructure.html
index 4ea6e09..41fddb3 100644
--- a/output/orientation/infrastructure.html
+++ b/output/orientation/infrastructure.html
@@ -102,10 +102,10 @@
<p>List of tools and services we use</p>
<ul>
<li>
-<p>ezmlm: This is the time-tested EZ Mailing List Manager application that
manages our mailing lists. You control ezmlm by sending commands to a list
address. For example, if the list address is <a
href="mailto:[email protected]";>[email protected]</a> then
you subscribe to the list with the command
dev-<strong>subscribe</strong>@openoffice.apache.org. Some other popular
commands are listed <a
href="https://www.apache.org/foundation/mailinglists.html";>here</a>. You can
get [...]
+<p>ezmlm: This is the time-tested EZ Mailing List Manager application that
manages our mailing lists. You control ezmlm by sending commands to a list
address. For example, if the list address is <a
href="mailto:[email protected]";>[email protected]</a> then
you subscribe to the list with the command
dev-<strong>subscribe</strong>@openoffice.apache.org. Some other popular
commands are listed <a
href="https://www.apache.org/foundation/mailinglists.html";>here</a>. You can
get [...]
</li>
<li>
-<p>Our two websites: <a
href="https://www.openoffice.org";>www.openoffice.org</a> and <a
href="https://openoffice.apache.org";>openoffice.apache.org</a>. Why two? There
is some logic here, although it is not perfectly executed (yet). The <a
href="http://www.openoffice.org";>www.openoffice.org</a> website is our primary
user-facing website. It is where we put content intended for end-users to use,
so downloads, product documentations, support and other related materials. The
openoffice.apach [...]
+<p>Our two websites: <a
href="https://www.openoffice.org";>www.openoffice.org</a> and <a
href="/">openoffice.apache.org</a>. Why two? There is some logic here, although
it is not perfectly executed (yet). The <a
href="http://www.openoffice.org";>www.openoffice.org</a> website is our primary
user-facing website. It is where we put content intended for end-users to use,
so downloads, product documentations, support and other related materials. The
openoffice.apache.org website, on the other [...]
</li>
<li>
<p>MediaWiki (also called MWiki) is used for the wiki on the <a
href="https://wiki.openoffice.org/wiki/Main_Page";>wiki.openoffice.org</a>
website. We use MWiki for many of the user-facing pages on the website,
especially in the areas of documentation and support. If you are familiar with
Wikipedia and the syntax used for authoring articles there, then you will find
our MediaWiki very easy to use, since Wikipedia also uses MediaWiki. If you are
new to MediaWiki please read over this <a hr [...]
diff --git a/output/orientation/intro-contributing.html
b/output/orientation/intro-contributing.html
index bb56381..5dbbe73 100644
--- a/output/orientation/intro-contributing.html
+++ b/output/orientation/intro-contributing.html
@@ -113,13 +113,13 @@ Apache, then much of this will already be familiar to
you.</p>
<li>
<p>As a globally-distributed all-volunteer open source project, there is never
a time or place where we can all meet together in the same room or even on a
telephone call. Because of this, and out of respect for everyone's busy and
varying schedule, we use mailing lists to coordinate our work, make proposals,
gather consensus and resolve community issues. There are three mailing lists
that every Volunteer should be on:</p>
<ol>
-<li><a
href="https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public";>dev</a>
This is the main mailing list for the project, and gets a lot of traffic. But
this is where project-wide discussions occur.</li>
-<li><a
href="https://openoffice.apache.org/mailing-lists.html#announce-mailing-list";>announce</a>
This is the official announcement list for the project. It is used for
announcing things like new releases, security patches, conferences, etc.</li>
-<li><a
href="https://openoffice.apache.org/mailing-lists.html#users-mailing-list-public";>users</a>
This is our users list and is one way in which we provide support to end
users. Although you may not be interested specifically in user support, it is
still recommended that you follow this list, even if just to get a feel for
user concerns, problems, feature ideas, etc.</li>
+<li><a href="/mailing-lists.html#development-mailing-list-public">dev</a> This
is the main mailing list for the project, and gets a lot of traffic. But this
is where project-wide discussions occur.</li>
+<li><a href="/mailing-lists.html#announce-mailing-list">announce</a> This is
the official announcement list for the project. It is used for announcing
things like new releases, security patches, conferences, etc.</li>
+<li><a href="/mailing-lists.html#users-mailing-list-public">users</a> This is
our users list and is one way in which we provide support to end users.
Although you may not be interested specifically in user support, it is still
recommended that you follow this list, even if just to get a feel for user
concerns, problems, feature ideas, etc.</li>
</ol>
</li>
<li>
-<p>You can also review other mailing lists we host and which may be of
interest, including ones focused on specific <a
href="https://openoffice.apache.org/mailing-lists.html";>project functions</a>
and <a href="https://openoffice.apache.org/native-lang.html";>native
languages</a>.</p>
+<p>You can also review other mailing lists we host and which may be of
interest, including ones focused on specific <a
href="/mailing-lists.html">project functions</a> and <a
href="/native-lang.html">native languages</a>.</p>
</li>
<li>
<p>A useful shortcut notation you will often see on the lists. Writing a list
name in full, like <a
href="mailto:[email protected]";>[email protected]</a> can be
tedious. So you will often see it called just "dev@". Similarly, top-level
lists like <a href="mailto:[email protected]";>[email protected]</a> are
often referred to as "trademarks@". This shortcut can be used to refer either
to the mailing list and to the team that operates the mailing list. The context
sh [...]
@@ -128,7 +128,7 @@ Apache, then much of this will already be familiar to
you.</p>
<p>One of the first practical tests each Volunteer faces is dealing with the
volume of emails that comes from participation in an open source project like
this. A good email client for this kind of work will support folders,
rule-based folder assignments, and most importantly quote collapsing. A common
practice is to make a separate folder for each Apache mailing list and define a
rule to move incoming emails directly into that folder. If you have a question
on how to configure your emai [...]
</li>
<li>
-<p>Because our mailing lists can be busy, and we're not all native English
speakers, and because email text is a crude medium which makes it hard to
express nuanced emotions, we need to be careful and tolerant in how we use it.
Please read over our <a
href="https://openoffice.apache.org/mailing-lists.html#participation-guidelines";>Participation
Guidelines</a> and <a
href="https://openoffice.apache.org/list-conduct.html";>List Conduct
Guidelines</a> for more information.</p>
+<p>Because our mailing lists can be busy, and we're not all native English
speakers, and because email text is a crude medium which makes it hard to
express nuanced emotions, we need to be careful and tolerant in how we use it.
Please read over our <a
href="/mailing-lists.html#participation-guidelines">Participation
Guidelines</a> and <a href="/list-conduct.html">List Conduct Guidelines</a> for
more information.</p>
</li>
<li>
<p>From Karl Fogel's book <a href="https://producingoss.com/";>"Producing Open
Source Software"</a> read through <a
href="https://producingoss.com/en/communications.html#you-are-what-you-write";>"You
Are What You Write"</a> and <a
href="https://producingoss.com/en/common-pitfalls.html";>"Avoiding Common
Pitfalls"</a>.</p>
@@ -140,7 +140,7 @@ Apache, then much of this will already be familiar to
you.</p>
<li>Our <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home";>ConfluenceWiki</a>
(sometimes called CWiki) where we do project planning.</li>
<li>Our <a href="https://bz.apache.org/ooo/";>Bugzilla database</a> (sometimes
called BZ) where we report and track status on bugs.</li>
<li>Our <a href="https://forum.openoffice.org/";>Community Forums</a> These are
available in several languages. This is the primary way in which we engage with
the user community.</li>
-<li>Join our <a href="https://openoffice.apache.org/social.html";>Social
Networks</a></li>
+<li>Join our <a href="/social.html">Social Networks</a></li>
</ol>
</li>
<li>
diff --git a/output/orientation/intro-development.html
b/output/orientation/intro-development.html
index 3ab2c0e..49b8041 100644
--- a/output/orientation/intro-development.html
+++ b/output/orientation/intro-development.html
@@ -98,7 +98,7 @@
<p>To complete this module, read through the material on this page, including
the linked references. There will also be some start-up tasks for you to
perform, such as signing up for an account in our defect tracking database.</p>
<p>Your first task is to subscribe to our Recruitment mailing list. You can
subscribe by sending an email to <a
href="mailto:[email protected]";>[email protected]</a>.</p>
<p>Then you can introduce yourself by [sending an email to the list](mailto:<a
href="mailto:[email protected]";>[email protected]</a>?subject=New
Dev Volunteer). We'd love to hear who you are, where you are from, what your
background is, etc. Also as you work through the items on this page, if you
have questions or problems, please feel free to ask for help by sending a note
to this same list.</p>
-<p>Note: In parallel with the Dev-specific items on this page, you may want to
also review the <a
href="http://openoffice.apache.org/orientation/index.html";>Level 1 and Level 2
Orientation Modules</a>. They have useful background information on The Apache
Way, mailing list etiquette, decision making in the project, etc. A quick
review is a good idea, especially if you are new to working in Apache-style
open source projects.</p>
+<p>Note: In parallel with the Dev-specific items on this page, you may want to
also review the <a href="/orientation/index.html">Level 1 and Level 2
Orientation Modules</a>. They have useful background information on The Apache
Way, mailing list etiquette, decision making in the project, etc. A quick
review is a good idea, especially if you are new to working in Apache-style
open source projects.</p>
<p>Now with the introductions out of the way, let's get started!</p>
<h2 id="openoffice-development-good-the-bad-and-the-ugly">OpenOffice
Development: Good, the Bad and the Ugly<a class="headerlink"
href="#openoffice-development-good-the-bad-and-the-ugly"
title="Permalink">¶</a></h2>
<p>Let's be honest. The size, age and complexity of OpenOffice's C++ codebase
makes coding a challenge. This is not a trivial codebase to learn. But if you
like a good challenge then you'll love this project! There are tasks suitable
for programmers with a range of programming experience, and we have many
veteran OpenOffice hackers in the project who are happy to answer your
questions.</p>
@@ -130,13 +130,13 @@ Although there are many other combinations of flags you
can use, some of which a
</ul>
<p>The Geneva Convention prevents us from forcing you to read all of those
rules, but know that they are there, and when your code is reviewed your
reviewer might refer to some of those rules if there is an issue. So you'll
absorb them over time.</p>
<h2 id="submitting-patches">Submitting Patches<a class="headerlink"
href="#submitting-patches" title="Permalink">¶</a></h2>
-<p>As you read in the <a
href="https://openoffice.apache.org/orientation/intro-contributing.html";>Introduction
to Contributing to OpenOffice module</a>, contributors who have demonstrated
merit via their project contributions can be voted in as Committers. Committers
have the ability to check code into project's source control. Contributors who
are not (yet) Committers must submit their patches and have them be reviewed
first.</p>
-<p>Please review these <a
href="https://openoffice.apache.org/svn-basics.html#creating_and_submitting_patches";>guidelines
for submitting patches</a>. A good practice is to attach the patch to the
Bugzilla issue and then send a link to the issue to the Dev list, asking for
someone to review and commit the patch.</p>
+<p>As you read in the <a
href="/orientation/intro-contributing.html">Introduction to Contributing to
OpenOffice module</a>, contributors who have demonstrated merit via their
project contributions can be voted in as Committers. Committers have the
ability to check code into project's source control. Contributors who are not
(yet) Committers must submit their patches and have them be reviewed first.</p>
+<p>Please review these <a
href="/svn-basics.html#creating_and_submitting_patches">guidelines for
submitting patches</a>. A good practice is to attach the patch to the Bugzilla
issue and then send a link to the issue to the Dev list, asking for someone to
review and commit the patch.</p>
<p>##Other Useful Resources</p>
<ul>
<li>The <a href="https://www.openoffice.org/development/";>OpenOffice.org for
Developers</a> web area has useful information for getting started.</li>
<li>The <a href="https://wiki.openoffice.org/wiki/Development";>OpenOffice.org
Development Wiki Area</a> has a lot of good general development
information.</li>
-<li>The <a
href="https://openoffice.apache.org/mailing-lists.html#commits-mailing-list";>commits
mailing list</a> echos every checkin made to the code base. Developers are
encouraged to subscribe so they are aware of other changes, and can help
review.</li>
+<li>The <a href="/mailing-lists.html#commits-mailing-list">commits mailing
list</a> echos every checkin made to the code base. Developers are encouraged
to subscribe so they are aware of other changes, and can help review.</li>
</ul>
<h2 id="module-completion">Module Completion<a class="headerlink"
href="#module-completion" title="Permalink">¶</a></h2>
<p>Once you have completed this Module, go to our our <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers";>Directory
of Volunteers</a> wiki page and add or update your information.
Congratulations! Please send a note to [<a
href="mailto:[email protected]";>[email protected]</a>](mailto:<a
href="mailto:[email protected]";>[email protected]</a>?subject=Completed
Introduction to Development) so we know.</p>
diff --git a/output/orientation/intro-doc.html
b/output/orientation/intro-doc.html
index 0d560de..670028c 100644
--- a/output/orientation/intro-doc.html
+++ b/output/orientation/intro-doc.html
@@ -98,7 +98,7 @@
<p>To complete this module, read through the material on this page, including
the linked references. There will also be some start-up tasks for you to
perform, such as signing up for an account in our wiki.</p>
<p>Your first task is to subscribe to our Documentation mailing list. You can
subscribe by sending an email to <a
href="mailto:[email protected]";>[email protected]</a>.</p>
<p>Then you can introduce yourself by [sending an email to the list](mailto:<a
href="mailto:[email protected]";>[email protected]</a>?subject=New
Doc Volunteer). We'd love to hear who you are, where you are from, what your
background is, etc. Also as you work through the items on this page, if you
have questions or problems, please feel free to ask for help by sending a note
to this same list.</p>
-<p>Note: In parallel with the Doc-specific items on this page, you may want to
also review the <a
href="https://openoffice.apache.org/orientation/index.html";>Level 1 and Level 2
Orientation Modules</a>. They have useful background information on The Apache
Way, mailing list etiquette, decision making in the project, etc. A quick
review is a good idea, especially if you are new to working in Apache-style
open source projects.</p>
+<p>Note: In parallel with the Doc-specific items on this page, you may want to
also review the <a href="/orientation/index.html">Level 1 and Level 2
Orientation Modules</a>. They have useful background information on The Apache
Way, mailing list etiquette, decision making in the project, etc. A quick
review is a good idea, especially if you are new to working in Apache-style
open source projects.</p>
<p>Now with the introductions out of the way, let's get started!</p>
<h2 id="the-big-picture">The Big Picture<a class="headerlink"
href="#the-big-picture" title="Permalink">¶</a></h2>
<p>As a popular end-user facing product, Apache OpenOffice is used by millions
of people around the world, with a wide range of skills and backgrounds. Some
have been using OpenOffice for decades. Others are just moving over from
Microsoft Office. Some are very familiar with computers and their operating
systems. Others may be using a computer for the first time. Some are doing just
basic editing. Others are "power users" and are creating complex applications
built on top of OpenOffice.</p>
diff --git a/output/orientation/intro-marketing.html
b/output/orientation/intro-marketing.html
index 98595c9..bf7dbc3 100644
--- a/output/orientation/intro-marketing.html
+++ b/output/orientation/intro-marketing.html
@@ -95,8 +95,8 @@
<p>In this orientation module you will be introduced to Marketing within
the Apache OpenOffice community. You will learn about many of the ways in which
we can do marketing, as well as some of the constraints we must keep in mind as
an non-profit organization. After completion of this module you should be
prepared to jump in and assist with ongoing marketing activities.</p>
<p>To complete this module you should read the following material, along with
associated links.</p>
-<p>But first, please subscribe to our <a
href="http://openoffice.apache.org/mailing-lists.html#marketing-mailing-list";>Marketing
Mailing List</a>, and then [send a note](mailto:<a
href="mailto:[email protected]";>[email protected]</a>?subject=Starting
Intro to Marketing Module) to introduce yourself.</p>
-<p>Note: You may also want to review the <a
href="http://openoffice.apache.org/orientation/index.html";>Level 1 and Level 2
Orientation Modules</a> which give an overview of the project as a whole, and a
perspective on working on open source at Apache.</p>
+<p>But first, please subscribe to our <a
href="/mailing-lists.html#marketing-mailing-list">Marketing Mailing List</a>,
and then [send a note](mailto:<a
href="mailto:[email protected]";>[email protected]</a>?subject=Starting
Intro to Marketing Module) to introduce yourself.</p>
+<p>Note: You may also want to review the <a
href="/orientation/index.html">Level 1 and Level 2 Orientation Modules</a>
which give an overview of the project as a whole, and a perspective on working
on open source at Apache.</p>
<h2 id="what-is-marketing">What is Marketing?<a class="headerlink"
href="#what-is-marketing" title="Permalink">¶</a></h2>
<p>There are many definitions, and most of them are right. Heidi Cohen has a
nice blog post with <a href="http://heidicohen.com/marketing-definition/";>72
definitions</a> which you should browse through.</p>
<p>From the perspective of Apache OpenOffice: <em>Marketing is the set of
activities our volunteers undertake to communicate the value and benefits of
the OpenOffice product, as well as the OpenOffice project, to potential users,
to the press and to potential project members.</em></p>
@@ -133,13 +133,13 @@
<p>The Apache Software Foundation owns the trademarks for its projects, and
they have defined a <a href="http://www.apache.org/foundation/marks/";>trademark
policy</a>, including some FAQ's that are worth reviewing.</p>
<h2 id="tools-for-communications">Tools for Communications<a
class="headerlink" href="#tools-for-communications"
title="Permalink">¶</a></h2>
<ul>
-<li>Mailing Lists: Our project-wide mailing lists are listed <a
href="http://openoffice.apache.org/mailing-lists.html";>here</a>. From a
marketing perspective, the two most relevant are the dev list, which reaches
the "core" team, and the announce list which reaches 9000+ users.</li>
-<li>Website: <a
href="http://www.openoffice.org";>http://www.openoffice.org</a> and <a
href="http://openoffice.apache.org";>http://openoffice.apache.org</a>. The
former gets 750K+ visits/day. We have the ability to add news stories to the
front page as well as a banner message on all pages.</li>
-<li>Events: Our events page is <a
href="http://openoffice.apache.org/events.html";>here</a>.</li>
+<li>Mailing Lists: Our project-wide mailing lists are listed <a
href="/mailing-lists.html">here</a>. From a marketing perspective, the two most
relevant are the dev list, which reaches the "core" team, and the announce list
which reaches 9000+ users.</li>
+<li>Website: <a
href="https://www.openoffice.org";>https://www.openoffice.org</a> and <a
href="/">https://openoffice.apache.org</a>. The former gets 750K+ visits/day.
We have the ability to add news stories to the front page as well as a banner
message on all pages.</li>
+<li>Events: Our events page is <a href="/events.html">here</a>.</li>
<li>Project Blog: The Blog is <a href="http://blogs.apache.org/OOo/";>here</a>.
New posts are easily cross-promoted. With a new post, the blog easily gets
4000+ visits/day.</li>
-<li>Social Networking: A list of our accounts is <a
href="http://openoffice.apache.org/social.html";>here</a></li>
-<li>Word of Mouth: Along with other occasional programs we have a <a
href="http://openoffice.apache.org/get-it-here.html";>"Get it here!"</a> logo
that we encourage users to put on their websites.</li>
-<li>The Press: Our press contact page is <a
href="http://openoffice.apache.org/press.html";>here</a>. As you can see we
seriously need some work there, and any volunteer who can make a more
meaningful page here, with most-requested information, would be most
welcome.</li>
+<li>Social Networking: A list of our accounts is <a
href="/social.html">here</a></li>
+<li>Word of Mouth: Along with other occasional programs we have a <a
href="/get-it-here.html">"Get it here!"</a> logo that we encourage users to put
on their websites.</li>
+<li>The Press: Our press contact page is <a href="/press.html">here</a>. As
you can see we seriously need some work there, and any volunteer who can make a
more meaningful page here, with most-requested information, would be most
welcome.</li>
<li>Surveys: We have the ability to poll users via surveys both informal and
formal.</li>
<li>Statistics: We maintain a variety of product and project statistics <a
href="http://www.openoffice.org/stats/";>here</a>.</li>
</ul>
diff --git a/output/orientation/intro-qa.html b/output/orientation/intro-qa.html
index f211cc7..821f539 100644
--- a/output/orientation/intro-qa.html
+++ b/output/orientation/intro-qa.html
@@ -98,7 +98,7 @@
<p>To complete this module, read through the material on this page, including
the linked references. There will also be some start-up tasks for you to
perform, such as signing up for an account in our defect tracking database.</p>
<p>Your first task is to subscribe to our QA mailing list and to introduce
yourself to the other QA volunteers. You can subscribe by sending an email to
<a
href="mailto:[email protected]";>[email protected]</a>.</p>
<p>Then you can introduce yourself by [sending an email to the list](mailto:<a
href="mailto:[email protected]";>[email protected]</a>?subject=New
QA Volunteer). We'd love to hear who you are, where you are from, what your
background is, etc. Also as you work through the items on this page, if you
have questions or problems, please feel free to ask for help by sending a note
to this same list.</p>
-<p>Note: In parallel with the QA-specific items on this page, you may want to
first review the <a
href="http://openoffice.apache.org/orientation/index.html";>Level 1 and Level 2
Orientation Modules</a> as well. They have useful background information on The
Apache Way, mailing list etiquette, decision making in the project, etc. A
quick review is a good idea, especially if you are new to working in
Apache-style open source projects.</p>
+<p>Note: In parallel with the QA-specific items on this page, you may want to
first review the <a href="/orientation/index.html">Level 1 and Level 2
Orientation Modules</a> as well. They have useful background information on The
Apache Way, mailing list etiquette, decision making in the project, etc. A
quick review is a good idea, especially if you are new to working in
Apache-style open source projects.</p>
<p>Now with the introductions out of the way, let's get started with the
QA!</p>
<h2 id="the-purpose-of-qa">The Purpose of QA<a class="headerlink"
href="#the-purpose-of-qa" title="Permalink">¶</a></h2>
<p>Our goal is to maintain and improve the quality of Apache OpenOffice. We
primarily accomplish this by finding defects (bugs) in the product before it is
released to the general public. The defects are found by a combination of
manual and automated tests that we perform on pre-release builds of OpenOffice.
We also review and try to reproduce
diff --git a/output/people.html b/output/people.html
index a93fa79..3fc4dba 100644
--- a/output/people.html
+++ b/output/people.html
@@ -96,7 +96,7 @@
<ul>
<li>A list of current project volunteers can be found on our wiki <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers";>here</a>.
The information there is self-managed by volunteers.</li>
-<li>Project Committers and PMC members are listed in the <a
href="https://people.apache.org/phonebook.html";>Apache Phone Book</a> under
Apache OpenOffice. New developers are announced on the <a
href="https://openoffice.apache.org/mailing-lists.html";>Development Mailing
List</a>.</li>
+<li>Project Committers and PMC members are listed in the <a
href="https://people.apache.org/phonebook.html";>Apache Phone Book</a> under
Apache OpenOffice. New developers are announced on the <a
href="/mailing-lists.html">Development Mailing List</a>.</li>
<li>We also have a large cumulative list of <a
href="https://www.openoffice.org/welcome/credits.html";>legacy contributors</a>
to OpenOffice</li>
</ul>
diff --git a/output/pmc-faqs.html b/output/pmc-faqs.html
index 42b74be..74b3260 100644
--- a/output/pmc-faqs.html
+++ b/output/pmc-faqs.html
@@ -186,7 +186,7 @@ Rob Weir, (Apache id) imacat</p>
<p>First of all you have to think how you want to participate as we have
different
kind of roles like user, developer, committer. The easiest way is to use what
we
build as user. If you want to improve parts of the software, or documentation,
-write to our <a
href="https://openoffice.apache.org/mailing-lists.html";>mailing lists</a> what
should be modified and how it should be done.
+write to our <a href="/mailing-lists.html">mailing lists</a> what should be
modified and how it should be done.
On the <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home";>community
wiki</a> you can just create an account and start to work on it
right away. There is a <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted";>Help
Wanted</a> page that has ideas for getting started.</p>
<p>The following are conditions to become a committer:</p>
@@ -267,7 +267,7 @@ information.</p>
to vote in new members as committers. In any case avoid voting as the normal
way is
to come to a decision by discussions. The initiator is responsible for the
vote,
that means also to count the votes and present the result. Every member has 1
vote.
-<br/> (<a href="https://openoffice.apache.org/docs/governance/voting.html";>see
here for more information</a>)</p>
+<br/> (<a href="/docs/governance/voting.html">see here for more
information</a>)</p>
<h1 id="release_managers">Information for Release Managers<a
class="headerlink" href="#release_managers" title="Permalink">¶</a></h1>
<ul>
<li>ASF General Information:
diff --git a/output/qa.html b/output/qa.html
index 579a603..f295526 100644
--- a/output/qa.html
+++ b/output/qa.html
@@ -98,7 +98,7 @@
QA doesn't require programming skills, so everyone can help us. If you are
interested in doing QA, please join us.</p>
<h2 id="talk-to-us">Talk to Us<a class="headerlink" href="#talk-to-us"
title="Permalink">¶</a></h2>
<ul>
-<li>We coordinate our work on the <a
href="https://openoffice.apache.org/mailing-lists.html#qa-mailing-list-public";>QA
mailing list</a>.
+<li>We coordinate our work on the <a
href="/mailing-lists.html#qa-mailing-list-public">QA mailing list</a>.
Subscribe to this list if you want to follow our work.</li>
<li>We also have a <a
href="https://wiki.openoffice.org/wiki/Quality_Assurance";>QA Wiki</a> that we
use for planning and documenting our process.</li>
</ul>
@@ -106,15 +106,15 @@ Subscribe to this list if you want to follow our
work.</li>
<p>We welcome QA volunteers and have several ways to get started:</p>
<ul>
<li>If you are familiar with both QA work and with Apache-style open source
projects, then you can probably
-jump right in. Join the <a
href="https://openoffice.apache.org/mailing-lists.html#qa-mailing-list-public";>QA
mailing list</a> and introduce yourself and we can help you get started.</li>
-<li>If you are familiar with Apache or similar open source projects, but new
to QA, then you can look at our <a
href="https://openoffice.apache.org/orientation/index.html";>Orientation
Modules</a>.
+jump right in. Join the <a
href="/mailing-lists.html#qa-mailing-list-public">QA mailing list</a> and
introduce yourself and we can help you get started.</li>
+<li>If you are familiar with Apache or similar open source projects, but new
to QA, then you can look at our <a href="/orientation/index.html">Orientation
Modules</a>.
You can skim over the first two levels, since much of this may be familiar.
But spend more time on the
-<a href="https://openoffice.apache.org/orientation/intro-qa.html";>Introduction
to QA</a> module.</li>
+<a href="/orientation/intro-qa.html">Introduction to QA</a> module.</li>
<li>If you are new to QA and to open source development, then you may also
want to start with our
-<a href="https://openoffice.apache.org/orientation/index.html";>Orientation
Modules</a>, and give attention
+<a href="/orientation/index.html">Orientation Modules</a>, and give attention
to the Level 1 and Level 2 topics, as well as the Level 3 Introduction to
QA.</li>
</ul>
-<p>In all cases, please join the <a
href="https://openoffice.apache.org/mailing-lists.html#qa-mailing-list-public";>QA
mailing list</a> and introduce yourself.</p>
+<p>In all cases, please join the <a
href="/mailing-lists.html#qa-mailing-list-public">QA mailing list</a> and
introduce yourself.</p>
<p>
diff --git a/output/source.html b/output/source.html
index 5297130..6652b9d 100644
--- a/output/source.html
+++ b/output/source.html
@@ -97,7 +97,7 @@
repository</a> using the "tree" view from gitbox in your web browser. The <a
href="https://github.com/apache/openoffice#readme";>README.md</a> at github.com
provides useful information on how to download and build Apache OpenOffice.</p>
<p>The previous svn repository, now read only, using <a
href="https://subversion.apache.org/";>Apache Subversion</a> for version control
is <a href="https://svn.apache.org/viewvc/openoffice/trunk/";>still viewable</a>
in your web browser.</p>
<p>Currently, subversion is still used for the two OpenOffice web sites.
-See our <a href="http://openoffice.apache.org/svn-basics.html";>Subversion
Basics</a>
+See our <a href="/svn-basics.html">Subversion Basics</a>
for more information on using subversion (svn) for the Apache OpenOffice
project.</p>
<!--- For further information see the [Apache Source Code Repository][3]
page.-->
<h2 id="getting-the-source-code">Getting the source code<a class="headerlink"
href="#getting-the-source-code" title="Permalink">¶</a></h2>
diff --git a/output/students.html b/output/students.html
index 14a51fc..3dd41d4 100644
--- a/output/students.html
+++ b/output/students.html
@@ -98,7 +98,7 @@ requirement for a course that they contribute to an open
source project or demon
context. The following points will help make the experience volunteering with
the OpenOffice project a good one for all:</p>
<ul>
<li>
-<p><a
href="http://openoffice.apache.org/mailing-lists.html#development-mailing-list-public";>Let
us know</a> what you are trying to accomplish. Do you need to volunteer a
specific number of hours? Weeks? Enough to write up a report?
+<p><a href="/mailing-lists.html#development-mailing-list-public">Let us
know</a> what you are trying to accomplish. Do you need to volunteer a
specific number of hours? Weeks? Enough to write up a report?
When do you need to have this done? Next week? Or three months from now?
The more you let us know what your goal is the better we can
recommend appropriate tasks for you to work on.</p>
</li>
@@ -118,14 +118,14 @@ many time zones. Many of us have "day jobs" or otherwise
work on OpenOffice onl
Keep this in mind if you will be volunteering only for a short period of time
(less than a month or two).</p>
</li>
<li>
-<p>You will find lots of useful information about QA, development,
documentation, and translation in the <a
href="http://openoffice.apache.org/orientation/index.html";>Orientation
Modules</a>.</p>
+<p>You will find lots of useful information about QA, development,
documentation, and translation in the <a
href="/orientation/index.html">Orientation Modules</a>.</p>
</li>
<li>
<p>We cannot offer any formal grade or evaluation of a student's
contributions, but your contributions will be public, on our mailing lists
and other tools, so your professor can easily verify your work.</p>
</li>
<li>
-<p>If your class will be having multiple students wanting to volunteer at the
same time, please have your professor <a
href="http://openoffice.apache.org/mailing-lists.html#development-mailing-list-public";>contact
us</a>
+<p>If your class will be having multiple students wanting to volunteer at the
same time, please have your professor <a
href="/mailing-lists.html#development-mailing-list-public">contact us</a>
in advance, so we can understand the course requirements and have time to
prepare of some appropriate tasks.</p>
</li>
</ul>
diff --git a/output/terms.html b/output/terms.html
index d5f2277..e18e80a 100644
--- a/output/terms.html
+++ b/output/terms.html
@@ -127,7 +127,7 @@ This section refers to the Materials found on the Site, as
defined above.</p>
<p>In legalese: You hereby grant to the Host and all Users a royalty-free,
perpetual, irrevocable, worldwide, non-exclusive and fully sub-licensable right
and license under Your intellectual property rights to reproduce, modify,
adapt, publish, translate, create derivative works from, distribute, perform,
display and use Your Submissions (in whole or part) and to incorporate them in
other works in any form, media, or technology now known or later developed, all
subject to the obligation [...]
<p>d. Private Projects. With respect to a Project that is designated as
"Private," the preceding license for "Other Submissions" is limited to Users
who have access to the Project, and such rights may only be sublicensed to
other Users with authorized access to the Project.</p>
<p>e. Other Licenses/Terms. Some Projects are governed by their own terms
regarding Submissions and may require You to sign agreements (such as an Apache
Software Foundation Individual Contributor License Agreement) licensing Your
rights in Your Submissions. In all such cases, and to the extent there is a
conflict, the terms of those Projects and agreements take precedence over these
Terms.</p>
-<p>f. Privacy. You consent to the collection, processing and storage by the
Host of any personal information provided by You in accordance with the terms
of AOO-PMC Privacy Policy, which is available at <a
href="http://openoffice.apache.org/privacy.html";>http://openoffice.apache.org/privacy.html</a>.
You agree to comply with all applicable laws and regulations, and the terms of
Apache OpenOffice Privacy Policy, with respect to any use by You of any
personal information in connection with [...]
+<p>f. Privacy. You consent to the collection, processing and storage by the
Host of any personal information provided by You in accordance with the terms
of AOO-PMC Privacy Policy, which is available at <a
href="/privacy.html">https://openoffice.apache.org/privacy.html</a>. You agree
to comply with all applicable laws and regulations, and the terms of Apache
OpenOffice Privacy Policy, with respect to any use by You of any personal
information in connection with this Site.</p>
</li>
<li>
<p>MISCELLANEOUS.</p>
diff --git a/output/trademarks.html b/output/trademarks.html
index 2a86f32..5a1c309 100644
--- a/output/trademarks.html
+++ b/output/trademarks.html
@@ -167,7 +167,7 @@ relevant details, especially, a URL for the offending
page.</p>
<h2 id="the-get-it-here-download-logo">The "Get it here!" download logo<a
class="headerlink" href="#the-get-it-here-download-logo"
title="Permalink">¶</a></h2>
<p>A specific logo is recommended for use by those who wish to help
promote the project by hosting a download logo on their website.
-The <a href="https://openoffice.apache.org/get-it-here.html";>"Get it
here!"</a> logo may be used according to the
+The <a href="/get-it-here.html">"Get it here!"</a> logo may be used according
to the
requirements listed on that page.</p>
diff --git a/output/translate.html b/output/translate.html
index f6a8276..71931b2 100644
--- a/output/translate.html
+++ b/output/translate.html
@@ -122,7 +122,7 @@ in your language, you should download and
install it. If you find errors in the translation, you can report them
via bug reports in <a
href="https://issues.apache.org/ooo/enter_bug.cgi?product=native-lang";>Bugzilla</a>
or enter a suggested fix into Pootle (more on Pootle below). You can
-contact the <a
href="https://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public";>L10n
list</a>
+contact the <a
href="/mailing-lists.html#localization-mailing-list-public">L10n list</a>
also for reporting errors in the English version.</p>
<p>If an OpenOffice build is not yet available for your language, then that
typically
means that the translation is not yet complete. You can help finish
@@ -134,7 +134,7 @@ our online translation system.</p>
to know how to request access to Pootle and
find useful tips for translators.</p>
<p>When you have completed the initial translation, send a note to the
-<a
href="https://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public";>L10n
list</a>.
+<a href="/mailing-lists.html#localization-mailing-list-public">L10n list</a>.
At that point we can make a special test build of Apache
OpenOffice for you to review. If more changes are required in the
translation, we can iterate on these steps, making changes, making new
@@ -146,7 +146,7 @@ can help review the test build and point out errors in
translation, as well as other localization errors. Others on the
OpenOffice project might be able to help you find other interested
users, so let us know, via a note to the
-<a
href="https://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public";>L10n
list</a>
+<a href="/mailing-lists.html#localization-mailing-list-public">L10n list</a>
if you want that help.</p>
diff --git a/output/website-local.html b/output/website-local.html
index 9f20ee6..850fb3e 100644
--- a/output/website-local.html
+++ b/output/website-local.html
@@ -100,7 +100,7 @@ pages are updated by the project community.</p>
<h2 id="two-websites">Two Websites<a class="headerlink" href="#two-websites"
title="Permalink">¶</a></h2>
<p>The Apache OpenOffice project maintains two websites:</p>
<ul>
-<li>The <a href="https://openoffice.apache.org/";>project website</a>,
primarily for development and technical information (which you're viewing now).
+<li>The <a href="/">project website</a>, primarily for development and
technical information (which you're viewing now).
All content for this website uses <a
href="http://daringfireball.net/projects/markdown/";>Markdown</a> syntax
(.mdtext files).</li>
<li>The user portal, <a
href="https://www.openoffice.org";>www.openoffice.org</a>, primarily for end
user information and support.
Content for the user portal primarily uses html, but some content is in
@@ -150,7 +150,7 @@ your Apache credentials to log in, make changes and submit
them to staging.
If you are not a committer, you can still use the bookmarklet by signing in to
the bookmarklet as <em>anonymous</em>.
See detailed how-to steps in the <a
href="https://www.apache.org/dev/cmsref.html#non-committer";>Apache CMS
Reference</a> for non-committers.</p>
<h3 id="more-details">More Details<a class="headerlink" href="#more-details"
title="Permalink">¶</a></h3>
-<p>Additional details on the above methods can be found on <a
href="https://openoffice.apache.org/docs/edit-cms.html";>How to edit the Apache
OpenOffice website</a>.</p>
+<p>Additional details on the above methods can be found on <a
href="/docs/edit-cms.html">How to edit the Apache OpenOffice website</a>.</p>
<h2 id="publishing-changes-to-the-production-websites">Publishing Changes to
the Production Websites<a class="headerlink"
href="#publishing-changes-to-the-production-websites"
title="Permalink">¶</a></h2>
<h3 id="for-committers">For Committers<a class="headerlink"
href="#for-committers" title="Permalink">¶</a></h3>
<p>As previously noted, changes you make, either through an svn commit or
using the CMS GUI tool,
@@ -169,7 +169,7 @@ section, you will likely be running
<strong>publish.pl</strong> from your "peopl
<h3 id="for-contributors-non-committers">For Contributors -- non-committers<a
class="headerlink" href="#for-contributors-non-committers"
title="Permalink">¶</a></h3>
<p>If you are not a committer, you will need
to follow the procedures for "contributors" in the
-<a
href="https://openoffice.apache.org/developer-faqs.html#im_not_a_committer";>Developer
FAQ</a>
+<a href="/developer-faqs.html#im_not_a_committer">Developer FAQ</a>
for getting your changes published by a committer of the project, after you
submit a patch.</p>
<h2
id="complete-local-website-development-for-technical-users-and-committers">Complete
Local Website Development (for technical users and committers)<a
class="headerlink"
href="#complete-local-website-development-for-technical-users-and-committers"
title="Permalink">¶</a></h2>
<p>The following information provides instructions on doing website
development for either of the OpenOffice websites
diff --git a/output/website-native.html b/output/website-native.html
index 3a0bf05..27e655f 100644
--- a/output/website-native.html
+++ b/output/website-native.html
@@ -269,9 +269,9 @@ release? A new blog post?</p>
and file structure is the same.</p>
<h2 id="you-need-a-helping-hand">You need a helping hand?<a class="headerlink"
href="#you-need-a-helping-hand" title="Permalink">¶</a></h2>
<p>You can get in contact with us via the
-<a
href="https://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public";>L10N
mailing list</a>.
+<a href="/mailing-lists.html#localization-mailing-list-public">L10N mailing
list</a>.
See the general explanation for
-<a
href="https://openoffice.apache.org/mailing-lists.html#using-mailing-lists";>what
a mailing list is</a>.</p>
+<a href="/mailing-lists.html#using-mailing-lists">what a mailing list
is</a>.</p>
<p>
![https://openoffice.apache.org/images/get-it-here/en.png"](https://openoffice.apache.org/images/get-it-here/en.png"){kind=link}