Author: buildbot
Date: Sat Nov 3 01:32:41 2012
New Revision: 837094
Log:
Staging update by buildbot for openofficeorg
Modified:
websites/staging/openofficeorg/trunk/content/ (props changed)
websites/staging/openofficeorg/trunk/content/openofficeorg/orientation/infrastructure.html
Propchange: websites/staging/openofficeorg/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Nov 3 01:32:41 2012
@@ -1 +1 @@
-1405249
+1405251
Modified:
websites/staging/openofficeorg/trunk/content/openofficeorg/orientation/infrastructure.html
==============================================================================
---
websites/staging/openofficeorg/trunk/content/openofficeorg/orientation/infrastructure.html
(original)
+++
websites/staging/openofficeorg/trunk/content/openofficeorg/orientation/infrastructure.html
Sat Nov 3 01:32:41 2012
@@ -158,16 +158,14 @@ need to raise an issue with another grou
</ul>
</li>
<li>
-<p>The role of the Apache Infrastructure Team (Infra or Infra@)</p>
-</li>
-</ol>
-<p>The <a href="http://www.apache.org/dev/infrastructure.html";>Infrastructure
team</a> 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.<br />
-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.<br />
+<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.<br />
+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.<br />
</p>
-<ol>
+</li>
<li>
<p>What to do if you have a problem:</p>
<ul>
