Author: buildbot
Date: Sat Dec 30 22:47:55 2017
New Revision: 1023008
Log:
Staging update by buildbot for openoffice
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
websites/staging/openoffice/trunk/content/orientation/infrastructure.html
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Dec 30 22:47:55 2017
@@ -1 +1 @@
-1819697
+1819698
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
Sat Dec 30 22:47:55 2017
@@ -133,28 +133,28 @@ 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="http://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="http://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="http://www.openoffice.org";>www.openoffice.org</a> and <a
href="http://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="http://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="http://meta.wikimedia.org/wiki/Help:Editing";>introduction to the
basics</a>.</p>
+<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>
</li>
<li>
<p>Confluence Wiki (also called CWiki) is used for some <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home";>project
management webpages</a></p>
</li>
<li>
-<p><a href="http://translate.apache.org";>Pootle</a> is our translation
management server, an online service used by translators to translate the UI
and help files of OpenOffice into various languages. Unless you are involved
with translations or builds you probably will never use Pootle. But you will
hear it mentioned on the mailing lists.</p>
+<p><a href="https://translate.apache.org";>Pootle</a> is our translation
management server, an online service used by translators to translate the UI
and help files of OpenOffice into various languages. Unless you are involved
with translations or builds you probably will never use Pootle. But you will
hear it mentioned on the mailing lists.</p>
</li>
<li>
-<p>Apache CMS (Content Management System) is the software that manages our
websites, including the application of side-wide templates used to apply, for
example, the common page footers that occur on each page). There is a web
interface to the Apache CMS that makes it easy to make small updates to a page.
If you are interested in adding or editing the website you can watch this video
on the <a href="http://www.youtube.com/watch?v=7fvg1pfHLhE";>Apache CMS's
Anonymous Mode</a> now. Otherwise this is a valuable skill you can pick up
later.</p>
+<p>Apache CMS (Content Management System) is the software that manages our
websites, including the application of side-wide templates used to apply, for
example, the common page footers that occur on each page). There is a web
interface to the Apache CMS that makes it easy to make small updates to a page.
If you are interested in adding or editing the website you can watch this video
on the <a href="https://www.youtube.com/watch?v=7fvg1pfHLhE";>Apache CMS's
Anonymous Mode</a> now. Otherwise this is a valuable skill you can pick up
later.</p>
</li>
<li>
<p>Subversion is the Version Control System (VCS) used by the project.
Subversion is also its own Apache project. The source code for the OpenOffice
product as well as the files for the websites are all stored in Subversion.
Developers use Subversion heavily in their work. Advanced work in QA and bulk
website changes also involve using Subversion.</p>
</li>
<li>
-<p>phpBB is the software that runs our <a
href="http://forum.openoffice.org/en/forum/";>Community Forums</a>, used for
technical support of our users.</p>
+<p>phpBB is the software that runs our <a
href="https://forum.openoffice.org/en/forum/";>Community Forums</a>, used for
technical support of our users.</p>
</li>
<li>
<p><a href="https://issues.apache.org/ooo/";>Bugzilla</a> is used to track
defect OpenOffice (bug) report.</p>
@@ -165,13 +165,13 @@ h2:hover > .headerlink, h3:hover > .head
</ul>
</li>
<li>
-<p>It is important to understand the role of the <a
href="http://www.apache.org/dev/infrastructure.html";>Apache Infrastructure
Team</a> (Infra or Infra@. The Infrastructure team are essentially the system
administrators for all Apache-wide servers and services, including many of the
services described above. As you can imagine, with all the projects that are
part of Apache, this is huge job. In order to support this number of projects
and provide good service levels in this shared infrastructure environment, we
align ourselves with the common services that are made available to other
projects. In other words, we have a "menu" of services that we can enable for
the project, and the ability to do some customization, within defined bounds,
but we cannot easily use a service outside of that menu.</p>
+<p>It is important to understand the role of the <a
href="https://www.apache.org/dev/infrastructure.html";>Apache Infrastructure
Team</a> (Infra or Infra@. The Infrastructure team are essentially the system
administrators for all Apache-wide servers and services, including many of the
services described above. As you can imagine, with all the projects that are
part of Apache, this is huge job. In order to support this number of projects
and provide good service levels in this shared infrastructure environment, we
align ourselves with the common services that are made available to other
projects. In other words, we have a "menu" of services that we can enable for
the project, and the ability to do some customization, within defined bounds,
but we cannot easily use a service outside of that menu.</p>
</li>
<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>Outages: <a href="http://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>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>
