Author: mseidel
Date: Mon Feb 4 23:54:55 2019
New Revision: 1852961
URL: http://svn.apache.org/viewvc?rev=1852961&view=rev
Log:
Removed whitespace, changed links to https
Modified:
openoffice/site/trunk/content/orientation/intro-contributing.mdtext
Modified: openoffice/site/trunk/content/orientation/intro-contributing.mdtext
URL:
http://svn.apache.org/viewvc/openoffice/site/trunk/content/orientation/intro-contributing.mdtext?rev=1852961&r1=1852960&r2=1852961&view=diff
==============================================================================
--- openoffice/site/trunk/content/orientation/intro-contributing.mdtext
(original)
+++ openoffice/site/trunk/content/orientation/intro-contributing.mdtext Mon Feb
4 23:54:55 2019
@@ -23,37 +23,37 @@ Level 1 is focused on connecting you to
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
[[email protected]](mailto:[email protected]?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 Volunteers by sending an email to
[[email protected]](mailto:[email protected]?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. 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:
- 1. [How It Works](http://apache.org/foundation/how-it-works.html) (to
learn about how the ASF is organized and how its meritocracy works)
- 1. [ASF FAQ's](http://www.apache.org/foundation/faq.html) (browse to see
if it answers any questions you might have)
- 1. [OpenOffice Wikipedia article](http://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. [How It Works](https://apache.org/foundation/how-it-works.html) (to
learn about how the ASF is organized and how its meritocracy works)
+ 1. [ASF FAQ's](https://www.apache.org/foundation/faq.html) (browse to
see if it answers any questions you might have)
+ 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.
[dev](http://openoffice.apache.org/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](http://openoffice.apache.org/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.
- 1.
[users](http://openoffice.apache.org/mailing-lists.html#users-mailing-list-public)
This is our users list and is one way in which we provide support to end
users. Although you may not be interested specifically in user support, it is
still recommended that you follow this list, even if just to get a feel for
user concerns, problems, feature ideas, etc.
+ 1.
[dev](https://openoffice.apache.org/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](https://openoffice.apache.org/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.
+ 1.
[users](https://openoffice.apache.org/mailing-lists.html#users-mailing-list-public)
This is our users list and is one way in which we provide support to end
users. Although you may not be interested specifically in user support, it is
still recommended that you follow this list, even if just to get a feel for
user concerns, problems, feature ideas, etc.
-1. You can also review other mailing lists we host and which may be of
interest, including ones focused on specific [project
functions](http://openoffice.apache.org/mailing-lists.html) and [native
languages](http://openoffice.apache.org/native-lang.html).
+1. You can also review other mailing lists we host and which may be of
interest, including ones focused on specific [project
functions](https://openoffice.apache.org/mailing-lists.html) and [native
languages](https://openoffice.apache.org/native-lang.html).
1. A useful shortcut notation you will often see on the lists. Writing a list
name in full, like [email protected] can be tedious. So you will often
see it called just "dev@". Similarly, top-level lists like
[email protected] 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 email client to do these things, try your help files,
or a web search first, and if that fails post a question to the dev list.
-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](http://openoffice.apache.org/mailing-lists.html#participation-guidelines)
and [List Conduct Guidelines](http://openoffice.apache.org/list-conduct.html)
for more information.
+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](https://openoffice.apache.org/mailing-lists.html#participation-guidelines)
and [List Conduct Guidelines](https://openoffice.apache.org/list-conduct.html)
for more information.
-1. From Karl Fogel's book ["Producing Open Source
Software"](http://producingoss.com/) read through ["You Are What You
Write"](http://producingoss.com/en/communications.html#you-are-what-you-write)
and ["Avoiding Common
Pitfalls"](http://producingoss.com/en/common-pitfalls.html).
+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. Our [MediaWiki](http://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.
- 1. Our [Bugzilla database](https://bz.apache.org/ooo/) (sometimes called
BZ) where we report and track status on bugs.
- 1. Our [Community Forums](http://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](http://openoffice.apache.org/social.html)
+ 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.
+ 1. Our [Bugzilla database](https://bz.apache.org/ooo/) (sometimes
called BZ) where we report and track status on bugs.
+ 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](https://openoffice.apache.org/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
[[email protected]](mailto:[email protected]?subject=Completed
Introduction to Contributing to Apache OpenOffice Module) so we know.
