Author: robweir Date: Sat Nov 3 01:32:37 2012 New Revision: 1405251 URL: http://svn.apache.org/viewvc?rev=1405251&view=rev Log: cleanup
Modified: incubator/ooo/site/trunk/content/openofficeorg/orientation/infrastructure.mdtext Modified: incubator/ooo/site/trunk/content/openofficeorg/orientation/infrastructure.mdtext URL: http://svn.apache.org/viewvc/incubator/ooo/site/trunk/content/openofficeorg/orientation/infrastructure.mdtext?rev=1405251&r1=1405250&r2=1405251&view=diff ============================================================================== --- incubator/ooo/site/trunk/content/openofficeorg/orientation/infrastructure.mdtext (original) +++ incubator/ooo/site/trunk/content/openofficeorg/orientation/infrastructure.mdtext Sat Nov 3 01:32:37 2012 @@ -16,7 +16,6 @@ Notice: Licensed to the Apache Softwa specific language governing permissions and limitations under the License. - In this Orientation Module you will learn about tools and servers that are part of the daily operations of the project. You will interact with many of these on a regular basis, or at least hear them discussed on the lists, so it is important to know what they are, and where to go if you need more information or run into problems. @@ -67,13 +66,12 @@ Subversion. * [JIRA](https://issues.apache.org/jira/) is another issue tracking application. Some Apache projects use JIRA instead of Bugzilla. We mainly use JIRA when we need to raise an issue with another group at Apache that uses JIRA, for example the Apache Infrastructure Team. -1. The role of the Apache Infrastructure Team (Infra or Infra@) - -The [Infrastructure team](http://www.apache.org/dev/infrastructure.html) 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. +1. It is important to understand the role of the [Apache Infrastructure Team](http://www.apache.org/dev/infrastructure.html) +(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. 1. What to do if you have a problem: