This is an automated email from the ASF dual-hosted git repository.
wave pushed a commit to branch preview/refresh
in repository https://gitbox.apache.org/repos/asf/openoffice-project.git
commit 835997338fef4329c04cfcd3979b6f397183b272
Author: Dave Fisher <d...@davefisher.tech>
AuthorDate: Wed Jun 30 10:04:42 2021 -0700
fix mailto subjects and change volunteer@ to recruitment@
---
content/contributing-code.md | 2 +-
content/developer-faqs.md | 2 +-
content/mailing-lists.md | 22 +++++++++++-----------
content/orientation/decision-making.md | 2 +-
content/orientation/how-aoo-project-works.md | 12 ++++++------
content/orientation/infrastructure.md | 4 ++--
content/orientation/intro-contributing.md | 12 ++++++------
content/orientation/intro-development.md | 10 +++++-----
content/orientation/intro-doc.md | 10 +++++-----
content/orientation/intro-l10n.md | 4 ++--
content/orientation/intro-marketing.md | 4 ++--
content/orientation/intro-qa.md | 4 ++--
content/pmc-faqs.md | 2 +-
13 files changed, 45 insertions(+), 45 deletions(-)
diff --git a/content/contributing-code.md b/content/contributing-code.md
index 660bc81..ec191a0 100644
--- a/content/contributing-code.md
+++ b/content/contributing-code.md
@@ -25,7 +25,7 @@ Some specific scenarios:
- For small bug fixes and enhancements, contributed by the original author of
the code, these are best submitted as patches attached to a [Bugzilla
issue](https://bz.apache.org/ooo/)
- For larger contributions, contributed by a single original author, we might
ask you to
- submit an [Individual Contributor License Agreement
(ICLA)](https://www.apache.org/licenses/icla.txt) form.
+ submit an [Individual Contributor License Agreement
(ICLA)](https://www.apache.org/licenses/icla.pdf) form.
The copyright on your code will still belong to you, but the ICLA helps
protect the users of Apache OpenOffice. All project Committers have also
signed this form.
- For contributions of multi-author code, it is best to start a discussion on
our [dev mailing list](mailto:d...@openoffice.apache.org) so we can discuss the
most appropriate way of processing it.
diff --git a/content/developer-faqs.md b/content/developer-faqs.md
index 2abbaae..45ec80e 100644
--- a/content/developer-faqs.md
+++ b/content/developer-faqs.md
@@ -93,7 +93,7 @@ additional information on current and future releases.
[1]: http://www.simpleeditions.com/59001/markdown-an-introduction
[2]: https://svn.apache.org/repos/asf/openoffice/site
[3]: /docs/edit-cms.html
- [4]: https://www.apache.org/licenses/icla.txt
+ [4]: https://www.apache.org/licenses/icla.pdf
[5]: https://people.apache.org/committer-index.html#unlistedclas
[6]: mailto:priv...@openoffice.apache.org
[7]: https://people.apache.org/committer-index.html
diff --git a/content/mailing-lists.md b/content/mailing-lists.md
index 62a8df2..b4fd5a7 100644
--- a/content/mailing-lists.md
+++ b/content/mailing-lists.md
@@ -18,7 +18,7 @@ Archive
Policy](http://www.apache.org/foundation/public-archives.html)
- [Marketing Mailing List](#marketing-mailing-list-public)
- [Announce Mailing List](#announce-mailing-list)
- [Development Mailing List](#development-mailing-list-public)
-- [Volunteer Mailing List](#volunteer-mailing-list-public)
+- [Recruitment Mailing List](#recruitment-mailing-list-public)
- [Documentation Mailing List](#documentation-mailing-list-public)
- [Quality Assurance (QA) Mailing List](#qa-mailing-list-public)
- [Localization Mailing List](#localization-mailing-list-public)
@@ -218,14 +218,14 @@ average of 20 posts/day and will increase in the future.
- Apache Archives: [current][55], [legacy][34]
- Third-party Archives: [Mail Archive][80], [Markmail][33] (incomplete)
-## Volunteer Mailing List (Public)
+## Recruitment Mailing List (Public)
This list is for welcoming new contributors. It coordinates the activities for
new
people and tries to help to find the right part. This is a low traffic list.
-- Subscribe: [volunteer-subscr...@openoffice.apache.org][84]
-- Post (after subscription): [volunt...@openoffice.apache.org][85]
-- Unsubscribe: [volunteer-unsubscr...@openoffice.apache.org][86]
+- Subscribe: [recruitment-subscr...@openoffice.apache.org][84]
+- Post (after subscription): [recruitm...@openoffice.apache.org][85]
+- Unsubscribe: [recruitment-unsubscr...@openoffice.apache.org][86]
- Apache Archives: [current][87]
- Third-party Archives: [Mail Archive][81]
@@ -258,7 +258,7 @@ the OpenOffice project:
- anything of a confidential nature should be sent to
priv...@openoffice.apache.org
- support questions related to the OpenOffice product should go to
us...@openoffice.apache.org
- website related questions should go to d...@openoffice.apache.org
-- questions on volunteering for the project should go to
d...@openoffice.apache.org
+- questions on recruitmenting for the project should go to
d...@openoffice.apache.org
- press queries should go to pr...@openoffice.apache.org
For any topic not covered by the above, send your post to:
d...@openoffice.apache.org
@@ -353,13 +353,13 @@ For any topic not covered by the above, send your post
to: dev@openoffice.apache
[78]: http://www.mail-archive.com/l10n@openoffice.apache.org/
[79]: http://www.mail-archive.com/commits@openoffice.apache.org/
[80]: http://www.mail-archive.com/issues@openoffice.apache.org/
- [81]: http://www.mail-archive.com/volunteer@openoffice.apache.org/
+ [81]: http://www.mail-archive.com/recruitment@openoffice.apache.org/
[82]: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html
[83]: http://openoffice.2283327.n4.nabble.com/Users-f2814619.html
- [84]: mailto:volunteer-subscr...@openoffice.apache.org
- [85]: mailto:volunt...@openoffice.apache.org
- [86]: mailto:volunteer-unsubscr...@openoffice.apache.org
- [87]: http://mail-archives.apache.org/mod_mbox/openoffice-volunteer/
+ [84]: mailto:recruitment-subscr...@openoffice.apache.org
+ [85]: mailto:recruitm...@openoffice.apache.org
+ [86]: mailto:recruitment-unsubscr...@openoffice.apache.org
+ [87]: http://mail-archives.apache.org/mod_mbox/openoffice-recruitment/
diff --git a/content/orientation/decision-making.md
b/content/orientation/decision-making.md
index 3c19472..435437b 100644
--- a/content/orientation/decision-making.md
+++ b/content/orientation/decision-making.md
@@ -67,4 +67,4 @@ In the previous Module we read about collaboration on the
mailings lists, how to
Congratulations, you have completed this Module!
-If you have any questions or feedback on this module, please send a note to
[recruitm...@openoffice.apache.org](mailto:recruitm...@openoffice.apache.org?subject=Comments
on Decision Making Module).
+If you have any questions or feedback on this module, please send a note to
[recruitm...@openoffice.apache.org](mailto:recruitm...@openoffice.apache.org?subject=Comments%20on%20Decision%20Making%20Module).
diff --git a/content/orientation/how-aoo-project-works.md
b/content/orientation/how-aoo-project-works.md
index 133db6f..e79af96 100644
--- a/content/orientation/how-aoo-project-works.md
+++ b/content/orientation/how-aoo-project-works.md
@@ -1,17 +1,17 @@
Title: How the Apache OpenOffice Project Works
Notice: http://www.apache.org/licenses/LICENSE-2.0
-1. Please send an email to
[volunt...@openoffice.apache.org](mailto:volunt...@openoffice.apache.org?subject=Starting
How the Apache OpenOffice Project Works) to let us know you are working on
this module.
+1. Please send an email to
[recruitm...@openoffice.apache.org](mailto:recruitm...@openoffice.apache.org?subject=Starting%20How%20the%20Apache%20OpenOffice%20Project%20Works)
to let us know you are working on this module.
1. As you learned in the [previous module](intro-contributing.html) the Apache
Software Foundation formally has Members, who elect a Board of Directors who
appoint Officers, including PMC (Project Management Committee) Chairs, who work
with the PMC's of the individual Top Level Projects and their communities, to
publish open source software for the public good. In this module we'll take a
closer look at how exactly we accomplish this within the Apache OpenOffice
project, how we divide up [...]
-1. Volunteers in the project tend to self-identify themselves in one or more
of the following categories, depending on their interests, skills and
contributions:
+1. Recruitments in the project tend to self-identify themselves in one or more
of the following categories, depending on their interests, skills and
contributions:
* Developers are the programmers who write, debug and fix the C++ code that
is the core of the OpenOffice software.
- * QA (Quality Assurance) are the volunteers to test OpenOffice builds,
looking for bugs. They also develop test automation and test cases.
- * Support are the volunteers who answer user questions on our Community
Forums and User list.
+ * QA (Quality Assurance) are the recruitments to test OpenOffice builds,
looking for bugs. They also develop test automation and test cases.
+ * Support are the recruitments who answer user questions on our Community
Forums and User list.
* UX (Usability)
- * Localization/Internationalization are the volunteers whose expertise is
in adapting OpenOffice so it works well with the writing and other cultural
conventions and expectations of
+ * Localization/Internationalization are the recruitments whose expertise is
in adapting OpenOffice so it works well with the writing and other cultural
conventions and expectations of
users around the globe. This includes translations and related activities.
* Documentation
* Admins, including moderators,
@@ -26,4 +26,4 @@ Notice: http://www.apache.org/licenses/LICENSE-2.0
* Conference Committee (ConCom)
* Incubator
-1. Congratulations! You have completed this Level. Please send a note to
[volunt...@openoffice.apache.org](mailto:volunt...@openoffice.apache.org?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
[recruitm...@openoffice.apache.org](mailto:recruitm...@openoffice.apache.org?subject=Completed%20How%20the%20Apache%20OpenOffice%20Project%20Works)
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.
diff --git a/content/orientation/infrastructure.md
b/content/orientation/infrastructure.md
index b6a7048..0f24f2e 100644
--- a/content/orientation/infrastructure.md
+++ b/content/orientation/infrastructure.md
@@ -3,7 +3,7 @@ Notice: http://www.apache.org/licenses/LICENSE-2.0
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.
-1. First, Please send an email to
[volunt...@openoffice.apache.org](mailto:volunt...@openoffice.apache.org?subject=Starting
Infrastructure Module) to let us know you are working on this module.
+1. First, Please send an email to
[recruitm...@openoffice.apache.org](mailto:recruitm...@openoffice.apache.org?subject=Starting%20Infrastructure%20Module)
to let us know you are working on this module.
1. List of tools and services we use
@@ -35,4 +35,4 @@ In this Orientation Module you will learn about tools and
servers that are part
* 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
[volunt...@openoffice.apache.org](mailto:volunt...@openoffice.apache.org?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
[recruitm...@openoffice.apache.org](mailto:recruitm...@openoffice.apache.org?subject=Completed%20Infrastructure%20Module)
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.
diff --git a/content/orientation/intro-contributing.md
b/content/orientation/intro-contributing.md
index b556ffe..c1ae291 100644
--- a/content/orientation/intro-contributing.md
+++ b/content/orientation/intro-contributing.md
@@ -1,14 +1,14 @@
Title: Introduction to Contributing to Apache OpenOffice
Notice: http://www.apache.org/licenses/LICENSE-2.0
-In this Orientation Module you will gain basic familiarity with the Apache
Software Foundation and how it works, get signed up for various important
online project services, and introduce yourself to the other volunteers on the
project's mailing mailing list.
+In this Orientation Module you will gain basic familiarity with the Apache
Software Foundation and how it works, get signed up for various important
online project services, and introduce yourself to the other recruitments on
the project's mailing mailing list.
Level 1 is focused on connecting you to the project.
If you have prior experience with an open source software project, especially
one at
Apache, then much of this will already be familiar to you.
-1. Introduce yourself to the other project Volunteers by sending an email to
[volunt...@openoffice.apache.org](mailto:volunt...@openoffice.apache.org?subject=Starting
Introduction to Contributing to Apache OpenOffice Module). Who are you, where
are you from, what are you interested in? These are all good things to cover.
Also, as you work through the items on this page, if you have questions or
problems, please feel free to ask for help by sending a note to this list.
+1. Introduce yourself to the other project Recruitments by sending an email to
[recruitm...@openoffice.apache.org](mailto:recruitm...@openoffice.apache.org?subject=Starting%20Introduction%20to%20Contributing%20to%20Apache%20OpenOffice%20Module).
Who are you, where are you from, what are you interested in? These are all
good things to cover. Also, as you work through the items on this page, if you
have questions or problems, please feel free to ask for help by sending a note
to this list.
1. It is important that you understand a little about the Apache Software
Foundation and OpenOffice, what it is, how it is organized and how the Apache
OpenOffice Project fits into the overall Foundation. This is partially
organizational knowledge and a little history. But it is important for
understanding how things work here, and understanding the culture of this open
source community. Suggested readings are:
@@ -17,7 +17,7 @@ Apache, then much of this will already be familiar to you.
1. [OpenOffice Wikipedia article](https://en.wikipedia.org/wiki/OpenOffice)
(for basic historical background)
1. [14 Ways to Contribute to Open Source without Being a Programming Genius
or a Rock
Star](https://smartbear.com/blog/test-and-monitor/14-ways-to-contribute-to-open-source-without-being/)
-1. As a globally-distributed all-volunteer open source project, there is never
a time or place where we can all meet together in the same room or even on a
telephone call. Because of this, and out of respect for everyone's busy and
varying schedule, we use mailing lists to coordinate our work, make proposals,
gather consensus and resolve community issues. There are three mailing lists
that every Volunteer should be on:
+1. As a globally-distributed all-recruitment open source project, there is
never a time or place where we can all meet together in the same room or even
on a telephone call. Because of this, and out of respect for everyone's busy
and varying schedule, we use mailing lists to coordinate our work, make
proposals, gather consensus and resolve community issues. There are three
mailing lists that every Recruitment should be on:
1. [dev](/mailing-lists.html#development-mailing-list-public) This is the
main mailing list for the project, and gets a lot of traffic. But this is where
project-wide discussions occur.
1. [announce](/mailing-lists.html#announce-mailing-list) This is the
official announcement list for the project. It is used for announcing things
like new releases, security patches, conferences, etc.
@@ -27,13 +27,13 @@ Apache, then much of this will already be familiar to you.
1. A useful shortcut notation you will often see on the lists. Writing a list
name in full, like d...@openoffice.apache.org can be tedious. So you will often
see it called just "dev@". Similarly, top-level lists like
tradema...@apache.org are often referred to as "trademarks@". This shortcut can
be used to refer either to the mailing list and to the team that operates the
mailing list. The context should make it clear, e.g., "You should check with
trademarks@ on whether this will be problem".
-1. One of the first practical tests each Volunteer faces is dealing with the
volume of emails that comes from participation in an open source project like
this. A good email client for this kind of work will support folders,
rule-based folder assignments, and most importantly quote collapsing. A common
practice is to make a separate folder for each Apache mailing list and define a
rule to move incoming emails directly into that folder. If you have a question
on how to configure your emai [...]
+1. One of the first practical tests each Recruitment faces is dealing with the
volume of emails that comes from participation in an open source project like
this. A good email client for this kind of work will support folders,
rule-based folder assignments, and most importantly quote collapsing. A common
practice is to make a separate folder for each Apache mailing list and define a
rule to move incoming emails directly into that folder. If you have a question
on how to configure your em [...]
1. Because our mailing lists can be busy, and we're not all native English
speakers, and because email text is a crude medium which makes it hard to
express nuanced emotions, we need to be careful and tolerant in how we use it.
Please read over our [Participation
Guidelines](/mailing-lists.html#participation-guidelines) and [List Conduct
Guidelines](/list-conduct.html) for more information.
1. From Karl Fogel's book ["Producing Open Source
Software"](https://producingoss.com/) read through ["You Are What You
Write"](https://producingoss.com/en/communications.html#you-are-what-you-write)
and ["Avoiding Common
Pitfalls"](https://producingoss.com/en/common-pitfalls.html).
-1. Aside from the mailing lists there are several online services that every
volunteer should be signed up for:
+1. Aside from the mailing lists there are several online services that every
recruitment should be signed up for:
1. Our [MediaWiki](https://wiki.openoffice.org/wiki/Main_Page) (sometimes
called MWiki) used for user documentation and many other things.
1. Our
[ConfluenceWiki](https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home)
(sometimes called CWiki) where we do project planning.
@@ -41,4 +41,4 @@ Apache, then much of this will already be familiar to you.
1. Our [Community Forums](https://forum.openoffice.org/) These are
available in several languages. This is the primary way in which we engage with
the user community.
1. Join our [Social Networks](/social.html)
-1. Finally, once you have done the above, go to our our [Directory of
Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers)
wiki page and add your information. Congratulations! Please send a note to
[volunt...@openoffice.apache.org](mailto:volunt...@openoffice.apache.org?subject=Completed
Introduction to Contributing to Apache OpenOffice Module) so we know.
+1. Finally, once you have done the above, go to our our [Directory of
Recruitments](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Recruitments)
wiki page and add your information. Congratulations! Please send a note to
[recruitm...@openoffice.apache.org](mailto:recruitm...@openoffice.apache.org?subject=Completed%20Introduction%20to%20Contributing%20to%20Apache%20OpenOffice%20Module)
so we know.
diff --git a/content/orientation/intro-development.md
b/content/orientation/intro-development.md
index 2a932c7..d7f9acd 100644
--- a/content/orientation/intro-development.md
+++ b/content/orientation/intro-development.md
@@ -7,9 +7,9 @@ In this orientation module you will learn how to get started
programming OpenOff
To complete this module, read through the material on this page, including the
linked references. There will also be some start-up tasks for you to perform,
such as signing up for an account in our defect tracking database.
-Your first task is to subscribe to our Recruitment mailing list. You can
subscribe by sending an email to
[volunteer-subscr...@openoffice.apache.org](mailto:volunteer-subscr...@openoffice.apache.org).
+Your first task is to subscribe to our Recruitment mailing list. You can
subscribe by sending an email to
[recruitment-subscr...@openoffice.apache.org](mailto:recruitment-subscr...@openoffice.apache.org).
-Then you can introduce yourself by [sending an email to the
list](mailto:volunt...@openoffice.apache.org?subject=New Dev Volunteer). We'd
love to hear who you are, where you are from, what your background is, etc.
Also as you work through the items on this page, if you have questions or
problems, please feel free to ask for help by sending a note to this same list.
+Then you can introduce yourself by [sending an email to the
list](mailto:recruitm...@openoffice.apache.org?subject=New%20Dev%20Recruitment).
We'd love to hear who you are, where you are from, what your background is,
etc. Also as you work through the items on this page, if you have questions or
problems, please feel free to ask for help by sending a note to this same list.
Note: In parallel with the Dev-specific items on this page, you may want to
also review the [Level 1 and Level 2 Orientation
Modules](/orientation/index.html). They have useful background information on
The Apache Way, mailing list etiquette, decision making in the project, etc. A
quick review is a good idea, especially if you are new to working in
Apache-style open source projects.
@@ -33,7 +33,7 @@ Our [Building
Guide](https://wiki.openoffice.org/wiki/Documentation/Building_Gui
Note also the current list of configuration flags used in building the
development snapshot builds at the bottom of the [development snapshot builds
page](https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOO3.4.1).
Although there are many other combinations of flags you can use, some of which
are very useful for development, the flags on that page are what we use in our
official releases.
-Once you have a successful build, [post a note to the dev
list](mailto:d...@openoffice.apache.org?subject=Successful 1st Build!) for some
well-earned congratulations!
+Once you have a successful build, [post a note to the dev
list](mailto:d...@openoffice.apache.org?subject=Successful%20First%20Build!)
for some well-earned congratulations!
## Orienting Yourself
@@ -46,7 +46,7 @@ A few suggestions to help you find your way around this
massive codebase:
As a new developer you will want to find some easy coding tasks. These are
tasks that generally can be done with good C++ skills, but do not require
comprehensive knowledge of how OpenOffice is put together. The tasks are more
localized. By doing easy tasks you gain experience and confidence hacking with
the code base.
-We use a [Bugzilla issue tracker](https://bz.apache.org/ooo/) to track
reported defects in OpenOffice. Some of us also use Bugzilla for tracking
feature and enhancement tasks as well. The value of tracking all coding-related
tasks in Bugzilla is that it helps our QA volunteers know which areas to test.
Whether code was changed to fix a bug or enhance a feature -- the QA impact is
pretty much the same.
+We use a [Bugzilla issue tracker](https://bz.apache.org/ooo/) to track
reported defects in OpenOffice. Some of us also use Bugzilla for tracking
feature and enhancement tasks as well. The value of tracking all coding-related
tasks in Bugzilla is that it helps our QA recruitments know which areas to
test. Whether code was changed to fix a bug or enhance a feature -- the QA
impact is pretty much the same.
If you have not done so already, please [sign up for a Bugzilla
account](https://issues.apache.org/ooo/createaccount.cgi). This will allow you
to enter new bugs or tasks, but also assign yourself existing ones.
@@ -77,4 +77,4 @@ Please review these [guidelines for submitting
patches](/svn-basics.html#creatin
## Module Completion
-Once you have completed this Module, go to our our [Directory of
Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers)
wiki page and add or update your information. Congratulations! Please send a
note to
[volunt...@openoffice.apache.org](mailto:volunt...@openoffice.apache.org?subject=Completed
Introduction to Development) so we know.
+Once you have completed this Module, go to our our [Directory of
Recruitments](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Recruitments)
wiki page and add or update your information. Congratulations! Please send a
note to
[recruitm...@openoffice.apache.org](mailto:recruitm...@openoffice.apache.org?subject=Completed%20Introduction%20to%20Development)
so we know.
diff --git a/content/orientation/intro-doc.md b/content/orientation/intro-doc.md
index ff00d82..b6f14e3 100644
--- a/content/orientation/intro-doc.md
+++ b/content/orientation/intro-doc.md
@@ -9,7 +9,7 @@ To complete this module, read through the material on this
page, including the l
Your first task is to subscribe to our Documentation mailing list. You can
subscribe by sending an email to
[doc-subscr...@openoffice.apache.org](mailto:doc-subscr...@openoffice.apache.org).
-Then you can introduce yourself by [sending an email to the
list](mailto:d...@openoffice.apache.org?subject=New Doc Volunteer). We'd love
to hear who you are, where you are from, what your background is, etc. Also as
you work through the items on this page, if you have questions or problems,
please feel free to ask for help by sending a note to this same list.
+Then you can introduce yourself by [sending an email to the
list](mailto:d...@openoffice.apache.org?subject=New%20Doc%20Volunteer). We'd
love to hear who you are, where you are from, what your background is, etc.
Also as you work through the items on this page, if you have questions or
problems, please feel free to ask for help by sending a note to this same list.
Note: In parallel with the Doc-specific items on this page, you may want to
also review the [Level 1 and Level 2 Orientation
Modules](/orientation/index.html). They have useful background information on
The Apache Way, mailing list etiquette, decision making in the project, etc. A
quick review is a good idea, especially if you are new to working in
Apache-style open source projects.
@@ -67,14 +67,14 @@ Volunteers on the Documentation Team work on a variety of
tasks, including:
The Documentation Team is the easiest one to get started with. There are just
a few basic steps:
1. Subscribe to our Documentation mailing list by sending an email to
[doc-subscr...@openoffice.apache.org](mailto:doc-subscr...@openoffice.apache.org).
-1. Sign up for an account on our MWiki by sending an e-mail with your
preferred user name and e-mail address to the [Documentation mailing
list](mailto:d...@openoffice.apache.org?subject=Requesting MWiki Account)
-1. Sign up for an account on [our
CWiki](https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home) (Why do
we have two wikis? It is a long story...)**Note:** **After creation the account
must be whitelisted by sending a request with the account name to the
[Documentation mailing
list](mailto:d...@openoffice.apache.org?subject=Whitelist CWiki Account)**
+1. Sign up for an account on our MWiki by sending an e-mail with your
preferred user name and e-mail address to the [Documentation mailing
list](mailto:d...@openoffice.apache.org?subject=Requesting%20MWiki%20Account)
+1. Sign up for an account on [our
CWiki](https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home) (Why do
we have two wikis? It is a long story...)**Note:** **After creation the account
must be whitelisted by sending a request with the account name to the
[Documentation mailing
list](mailto:d...@openoffice.apache.org?subject=Whitelist%20CWiki%20Account)**
1. Add your name to our [Directory of
Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers)
and
[Documentation
Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Documentation+Volunteers)
pages.
-1. Send an email to the [Documentation mailing
list](mailto:d...@openoffice.apache.org?subject=New Doc Volunteer) and
introduce yourself.
+1. Send an email to the [Documentation mailing
list](mailto:d...@openoffice.apache.org?subject=New%20Doc%20Volunteer) and
introduce yourself.
We can then bring you up to speed on what we're currently working on.
## Module Completion
-Once you have completed this Module, go to our our [Directory of
Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers)
wiki page and add or update your information. Congratulations! Please send a
note to
[d...@openoffice.apache.org](mailto:d...@openoffice.apache.org?subject=Completed
Introduction to Documentation) so we know.
+Once you have completed this Module, go to our our [Directory of
Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers)
wiki page and add or update your information. Congratulations! Please send a
note to
[d...@openoffice.apache.org](mailto:d...@openoffice.apache.org?subject=Completed%20Introduction%20to%20Documentation)
so we know.
diff --git a/content/orientation/intro-l10n.md
b/content/orientation/intro-l10n.md
index c6ad4ac..f3b1d3c 100644
--- a/content/orientation/intro-l10n.md
+++ b/content/orientation/intro-l10n.md
@@ -1,6 +1,6 @@
Title: Introduction to Localization
Notice: http://www.apache.org/licenses/LICENSE-2.0
-1. Please send an email to
[l...@openoffice.apache.org](mailto:l...@openoffice.apache.org?subject=Starting
Introduction to Localization) to let us know you are working on this module.
+1. Please send an email to
[l...@openoffice.apache.org](mailto:l...@openoffice.apache.org?subject=Starting%20Introduction%20to%20Localization)
to let us know you are working on this module.
-1. Congratulations! You have completed this Level. Please send a note to
[l...@openoffice.apache.org](mailto:l...@openoffice.apache.org?subject=Completed
Introduction to Localization) 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
[l...@openoffice.apache.org](mailto:l...@openoffice.apache.org?subject=Completed%20Introduction%20to%20Localization)
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.
diff --git a/content/orientation/intro-marketing.md
b/content/orientation/intro-marketing.md
index d9ff88c..acbe2b9 100644
--- a/content/orientation/intro-marketing.md
+++ b/content/orientation/intro-marketing.md
@@ -5,7 +5,7 @@ In this orientation module you will be introduced to Marketing
within the Apache
To complete this module you should read the following material, along with
associated links.
-But first, please subscribe to our [Marketing Mailing
List](/mailing-lists.html#marketing-mailing-list), and then [send a
note](mailto:market...@openoffice.apache.org?subject=Starting Intro to
Marketing Module) to introduce yourself.
+But first, please subscribe to our [Marketing Mailing
List](/mailing-lists.html#marketing-mailing-list), and then [send a
note](mailto:market...@openoffice.apache.org?subject=Starting%20Intro%20to%20Marketing%20Module)
to introduce yourself.
Note: You may also want to review the [Level 1 and Level 2 Orientation
Modules](/orientation/index.html) which give an overview of the project as a
whole, and a perspective on working on open source at Apache.
@@ -91,4 +91,4 @@ Along with this orientation, and the ASF's [charitable
mission](https://www.apac
## End of Module
-Congratulations! You have completed this Module. Please send a note to
[market...@openoffice.apache.org](mailto:market...@openoffice.apache.org?subject=Completed
Marketing 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.
+Congratulations! You have completed this Module. Please send a note to
[market...@openoffice.apache.org](mailto:market...@openoffice.apache.org?subject=Completed%20Marketing%20Module)
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.
diff --git a/content/orientation/intro-qa.md b/content/orientation/intro-qa.md
index e2b24f4..968bcb2 100644
--- a/content/orientation/intro-qa.md
+++ b/content/orientation/intro-qa.md
@@ -9,7 +9,7 @@ To complete this module, read through the material on this
page, including the l
Your first task is to subscribe to our QA mailing list and to introduce
yourself to the other QA volunteers. You can subscribe by sending an email to
[qa-subscr...@openoffice.apache.org](mailto:qa-subscr...@openoffice.apache.org).
-Then you can introduce yourself by [sending an email to the
list](mailto:q...@openoffice.apache.org?subject=New QA Volunteer). We'd love to
hear who you are, where you are from, what your background is, etc. Also as you
work through the items on this page, if you have questions or problems, please
feel free to ask for help by sending a note to this same list.
+Then you can introduce yourself by [sending an email to the
list](mailto:q...@openoffice.apache.org?subject=New%20QA%20Volunteer). We'd
love to hear who you are, where you are from, what your background is, etc.
Also as you work through the items on this page, if you have questions or
problems, please feel free to ask for help by sending a note to this same list.
Note: In parallel with the QA-specific items on this page, you may want to
first review the [Level 1 and Level 2 Orientation
Modules](/orientation/index.html) as well. They have useful background
information on The Apache Way, mailing list etiquette, decision making in the
project, etc. A quick review is a good idea, especially if you are new to
working in Apache-style open source projects.
@@ -185,4 +185,4 @@ Useful guide for writing manual test cases:
## Module Completion
-Once you have done the above, go to our our [Directory of
Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers)
wiki page and add or update your information. Also, add an entry for yourself
to the [QA Testing
Preferences](https://cwiki.apache.org/confluence/display/OOOUSERS/QA+Testing+Preferences)
page. Congratulations! Please send a note to
[q...@openoffice.apache.org](mailto:q...@openoffice.apache.org?subject=Completed
Introduction to QA) so we know.
+Once you have done the above, go to our our [Directory of
Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers)
wiki page and add or update your information. Also, add an entry for yourself
to the [QA Testing
Preferences](https://cwiki.apache.org/confluence/display/OOOUSERS/QA+Testing+Preferences)
page. Congratulations! Please send a note to
[q...@openoffice.apache.org](mailto:q...@openoffice.apache.org?subject=Completed%20Introduction%20to%20QA)
so we know.
diff --git a/content/pmc-faqs.md b/content/pmc-faqs.md
index 2a8e6dd..a8eea29 100644
--- a/content/pmc-faqs.md
+++ b/content/pmc-faqs.md
@@ -190,7 +190,7 @@ keys:
[https://dist.apache.org/repos/dist/release/openoffice](https://dist.apach
[2]: /mailing-lists.html
[3]: https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home
[4]: https://incubator.apache.org/guides/participation.html
-[5]: https://www.apache.org/licenses/icla.txt
+[5]: https://www.apache.org/licenses/icla.pdf
[6]: https://www.apache.org/licenses/cla-corporate.txt
[7]: https://people.apache.org/committer-index.html
[8]: https://svn.apache.org/repos/private/committers
