Author: mseidel
Date: Mon Feb 4 23:35:50 2019
New Revision: 1852959
URL: http://svn.apache.org/viewvc?rev=1852959&view=rev
Log:
Removed whitespace
Modified:
openoffice/site/trunk/content/orientation/how-aoo-project-works.mdtext
openoffice/site/trunk/content/orientation/index.mdtext
openoffice/site/trunk/content/orientation/infrastructure.mdtext
Modified: openoffice/site/trunk/content/orientation/how-aoo-project-works.mdtext
URL:
http://svn.apache.org/viewvc/openoffice/site/trunk/content/orientation/how-aoo-project-works.mdtext?rev=1852959&r1=1852958&r2=1852959&view=diff
==============================================================================
--- openoffice/site/trunk/content/orientation/how-aoo-project-works.mdtext
(original)
+++ openoffice/site/trunk/content/orientation/how-aoo-project-works.mdtext Mon
Feb 4 23:35:50 2019
@@ -41,4 +41,4 @@ Notice: Licensed to the Apache Softwa
* Conference Committee (ConCom)
* Incubator
-1. Congratulations! You have completed this level. Please send a note to
[[email protected]](mailto:[email protected]?subject=Completed
How the Apache OpenOffice Project Works) 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.
+1. Congratulations! You have completed this Level. Please send a note to
[[email protected]](mailto:[email protected]?subject=Completed
How the Apache OpenOffice Project Works) 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.
Modified: openoffice/site/trunk/content/orientation/index.mdtext
URL:
http://svn.apache.org/viewvc/openoffice/site/trunk/content/orientation/index.mdtext?rev=1852959&r1=1852958&r2=1852959&view=diff
==============================================================================
--- openoffice/site/trunk/content/orientation/index.mdtext (original)
+++ openoffice/site/trunk/content/orientation/index.mdtext Mon Feb 4 23:35:50
2019
@@ -18,7 +18,7 @@ Notice: Licensed to the Apache Softwa
##Welcome!
-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!
+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!
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.
@@ -42,17 +42,17 @@ Levels 3 and 4 are specialized Levels, t
* Level 3: Introductory Specialized Areas
- * [Introduction to Development](intro-development.html)
- * [Introduction to QA](intro-qa.html)
- * [Introduction to
Localization](http://openoffice.apache.org/translate.html) (How to Help
Translate OpenOffice)
- * [Introduction to Marketing](intro-marketing.html)
- * [Introduction to Documentation](intro-doc.html)
- * Introduction to Website Content Authoring
+ * [Introduction to Development](intro-development.html)
+ * [Introduction to QA](intro-qa.html)
+ * [Introduction to
Localization](http://openoffice.apache.org/translate.html) (How to Help
Translate OpenOffice)
+ * [Introduction to Marketing](intro-marketing.html)
+ * [Introduction to Documentation](intro-doc.html)
+ * Introduction to Website Content Authoring
* Level 4: Intermediate Specialized Areas
- * Intermediate Development
- * Intermediate QA
- * Intermediate Localization and Internationalization
- * Intermediate Marketing
- * Intermediate Website Development using Perl and the CMS
+ * Intermediate Development
+ * Intermediate QA
+ * Intermediate Localization and Internationalization
+ * Intermediate Marketing
+ * Intermediate Website Development using Perl and the CMS
Modified: openoffice/site/trunk/content/orientation/infrastructure.mdtext
URL:
http://svn.apache.org/viewvc/openoffice/site/trunk/content/orientation/infrastructure.mdtext?rev=1852959&r1=1852958&r2=1852959&view=diff
==============================================================================
--- openoffice/site/trunk/content/orientation/infrastructure.mdtext (original)
+++ openoffice/site/trunk/content/orientation/infrastructure.mdtext Mon Feb 4
23:35:50 2019
@@ -22,32 +22,32 @@ In this Orientation Module you will lear
1. List of tools and services we use
- * 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-**subscribe**@openoffice.apache.org. Some other popular commands are listed
[here](https://www.apache.org/foundation/mailinglists.html). You can get a full
list of commands available to you by sending the *help* command, as in
dev-**help**@openoffice.apache.org. Each list has moderators who have
additional capabilities. You can find the moderators for our lists
[here](https://openoffice.apache.org/pmc-faqs.html#mailing-lists).
+ * 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-**subscribe**@openoffice.apache.org. Some other popular commands are listed
[here](https://www.apache.org/foundation/mailinglists.html). You can get a full
list of commands available to you by sending the *help* command, as in
dev-**help**@openoffice.apache.org. Each list has moderators who have
additional capabilities. You can find the moderators for our lists
[here](https://openoffice.apache.org/pmc-faqs.html#mailing-lists).
- * Our two websites: [www.openoffice.org](https://www.openoffice.org) and
[openoffice.apache.org](https://openoffice.apache.org). 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.
+ * Our two websites: [www.openoffice.org](https://www.openoffice.org)
and [openoffice.apache.org](https://openoffice.apache.org). 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.
- * MediaWiki (also called MWiki) is used for the wiki on the
[wiki.openoffice.org](https://wiki.openoffice.org/wiki/Main_Page) 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 [introduction to the
basics](https://meta.wikimedia.org/wiki/Help:Editing).
+ * MediaWiki (also called MWiki) is used for the wiki on the
[wiki.openoffice.org](https://wiki.openoffice.org/wiki/Main_Page) 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 [introduction to the
basics](https://meta.wikimedia.org/wiki/Help:Editing).
- * Confluence Wiki (also called CWiki) is used for some [project management
webpages](https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home)
+ * Confluence Wiki (also called CWiki) is used for some [project
management
webpages](https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home)
- * [Pootle](https://translate.apache.org) 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.
+ * [Pootle](https://translate.apache.org) 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.
- * 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 [Apache CMS's Anonymous
Mode](https://www.youtube.com/watch?v=7fvg1pfHLhE) now. Otherwise this is a
valuable skill you can pick up later.
+ * 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 [Apache CMS's Anonymous
Mode](https://www.youtube.com/watch?v=7fvg1pfHLhE) now. Otherwise this is a
valuable skill you can pick up later.
- * 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.
+ * 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.
- * phpBB is the software that runs our [Community
Forums](https://forum.openoffice.org/en/forum/), used for technical support of
our users.
+ * phpBB is the software that runs our [Community
Forums](https://forum.openoffice.org/en/forum/), used for technical support of
our users.
- * [Bugzilla](https://issues.apache.org/ooo/) is used to track defect
OpenOffice (bug) report.
+ * [Bugzilla](https://issues.apache.org/ooo/) is used to track defect
OpenOffice (bug) report.
- * [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.
+ * [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. It is important to understand the role of the [Apache Infrastructure
Team](https://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:
- * 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.
- * Outages: [Current status](https://monitoring.apache.org/status/) is
posted. You might also want to subscribe to Infra's [Twitter
feed](https://twitter.com/infrabot). If you see an outage not noted there
already, you can notify Infra via IRC channel #asfinfra on Freenode.
- * 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.
+ * 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.
+ * Outages: [Current status](https://monitoring.apache.org/status/) is
posted. You might also want to subscribe to Infra's [Twitter
feed](https://twitter.com/infrabot). If you see an outage not noted there
already, you can notify Infra via IRC channel #asfinfra on Freenode.
+ * 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.
-1. Congratulations! You have completed this Module. Please send a note to
[[email protected]](mailto:[email protected]?subject=Completed
Infrastructure Module) 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.
+1. Congratulations! You have completed this Module. Please send a note to
[[email protected]](mailto:[email protected]?subject=Completed
Infrastructure Module) 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.
