Author: buildbot
Date: Mon Feb 4 23:35:58 2019
New Revision: 1039975
Log:
Staging update by buildbot for openoffice
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
websites/staging/openoffice/trunk/content/orientation/how-aoo-project-works.html
websites/staging/openoffice/trunk/content/orientation/index.html
websites/staging/openoffice/trunk/content/orientation/infrastructure.html
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb 4 23:35:58 2019
@@ -1 +1 @@
-1852801
+1852959
Modified:
websites/staging/openoffice/trunk/content/orientation/how-aoo-project-works.html
==============================================================================
---
websites/staging/openoffice/trunk/content/orientation/how-aoo-project-works.html
(original)
+++
websites/staging/openoffice/trunk/content/orientation/how-aoo-project-works.html
Mon Feb 4 23:35:58 2019
@@ -160,7 +160,7 @@ users around the globe. This includes tr
</ul>
</li>
<li>
-<p>Congratulations! You have completed this level. Please send a note to <a
href="mailto:[email protected]?subject=Completed How the Apache
OpenOffice Project Works">[email protected]</a> so we all know
you have completed this level. This is also a good opportunity to send along
any feedback or questions you might have on this Orientation Module.</p>
+<p>Congratulations! You have completed this Level. Please send a note to <a
href="mailto:[email protected]?subject=Completed How the Apache
OpenOffice Project Works">[email protected]</a> so we all know
you have completed this level. This is also a good opportunity to send along
any feedback or questions you might have on this Orientation Module.</p>
</li>
</ol>
</div>
Modified: websites/staging/openoffice/trunk/content/orientation/index.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/index.html (original)
+++ websites/staging/openoffice/trunk/content/orientation/index.html Mon Feb 4
23:35:58 2019
@@ -128,7 +128,7 @@ h2:hover > .headerlink, h3:hover > .head
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
<h2 id="welcome">Welcome!<a class="headerlink" href="#welcome"
title="Permanent link">¶</a></h2>
-<p>So you are interested in volunteering with the Apache OpenOffice project,
one of the oldest and most famous open source projects around? Great, welcome
to the project!</p>
+<p>So you are interested in volunteering with the Apache OpenOffice project,
one of the oldest and most famous open source projects around? Great, welcome
to the project!</p>
<p>Getting involved in a large open source project can be a little
intimidating. There is so much going on, so many new names, new processes, new
ways of communicating. It can be confusing, even frustrating at first. In some
ways, maybe at the technical level, it is similar to other software development
projects you may be familiar with. But as a community-led open source project
the ways we work, communicate, make decisions, and resolve disputes are very
different than what you might see in other environments.</p>
<p>In order to help new Volunteers fit into the OpenOffice Community and
understand socially and technically how we work, we have created a set of
self-directed Orientation Modules to provide key information and help you
develop key skills needed to contribute effectively to the project.</p>
<h2 id="four-levels">Four Levels<a class="headerlink" href="#four-levels"
title="Permanent link">¶</a></h2>
Modified:
websites/staging/openoffice/trunk/content/orientation/infrastructure.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/infrastructure.html
(original)
+++ websites/staging/openoffice/trunk/content/orientation/infrastructure.html
Mon Feb 4 23:35:58 2019
@@ -136,10 +136,10 @@ h2:hover > .headerlink, h3:hover > .head
<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 [email protected] 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 a full list of commands available to you by sending the <em>help</em>
command, as in dev-<strong>help</strong>@openoffice.apache.org. Each list has
moderators who have additional capabilities. You can find the moderators for
our lists <a
href="https://openoffice.apache.org/pmc-faqs.html#mailing-lists";>here</a>.</p>
+<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 [email protected] 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 a full list of commands available to you by sending the <em>help</em>
command, as in dev-<strong>help</strong>@openoffice.apache.org. Each list has
moderators who have additional capabilities. You can find the moderators for
our lists <a
href="https://openoffice.apache.org/pmc-faqs.html#mailing-lists";>here</a>.</p>
</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
www.openoffice.org 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 hand, is the main portal for project members, the
contributors to the project. We run the project on openoffice.apache.org, and
the www.openoffice.org website is a service we provide to users.</p>
+<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
www.openoffice.org 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 hand, is the main portal for project members, the
contributors to the project. We run the project on openoffice.apache.org, and
the www.openoffice.org website is a service we provide to users.</p>
</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
href="https://meta.wikimedia.org/wiki/Help:Editing";>introduction to the
basics</a>.</p>
@@ -173,13 +173,13 @@ h2:hover > .headerlink, h3:hover > .head
<li>
<p>What to do if you have a problem:</p>
<ul>
-<li>Questions on how to use the service: First, look for intructions on the
website. If that fails, post a note to the dev mailing list for hints.</li>
+<li>Questions on how to use the service: First, look for instructions on the
website. If that fails, post a note to the dev mailing list for hints.</li>
<li>Outages: <a href="https://monitoring.apache.org/status/";>Current
status</a> is posted. You might also want to subscribe to Infra's <a
href="https://twitter.com/infrabot";>Twitter feed</a>. If you see an outage not
noted there already, you can notify Infra via IRC channel #asfinfra on
Freenode.</li>
<li>Requests to enhance or modify the service: Propose something on dev. Even
though Infra is required to carry out some tasks, you still should get
consensus first on the project's mailing list.</li>
</ul>
</li>
<li>
-<p>Congratulations! You have completed this Module. Please send a note to <a
href="mailto:[email protected]?subject=Completed Infrastructure
Module">[email protected]</a> so we all know you have completed
this level. This is also a good opportunity to send along any feedback or
questions you might have on this Orientation Module.</p>
+<p>Congratulations! You have completed this Module. Please send a note to <a
href="mailto:[email protected]?subject=Completed Infrastructure
Module">[email protected]</a> so we all know you have completed
this level. This is also a good opportunity to send along any feedback or
questions you might have on this Orientation Module.</p>
</li>
</ol>
</div>
