Author: buildbot
Date: Mon Feb  4 23:55:04 2019
New Revision: 1039977

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    
websites/staging/openoffice/trunk/content/orientation/intro-contributing.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb  4 23:55:04 2019
@@ -1 +1 @@
-1852959
+1852961

Modified: 
websites/staging/openoffice/trunk/content/orientation/intro-contributing.html
==============================================================================
--- 
websites/staging/openoffice/trunk/content/orientation/intro-contributing.html 
(original)
+++ 
websites/staging/openoffice/trunk/content/orientation/intro-contributing.html 
Mon Feb  4 23:55:04 2019
@@ -133,27 +133,27 @@ h2:hover > .headerlink, h3:hover > .head
 Apache, then much of this will already be familiar to you.</p>
 <ol>
 <li>
-<p>Introduce yourself to the other project Volunteers by sending an email to 
<a href="mailto:[email protected]?subject=Starting Introduction 
to Contributing to Apache OpenOffice 
Module">[email protected]</a>. 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.</p>
+<p>Introduce yourself to the other project Volunteers by sending an email to 
<a href="mailto:[email protected]?subject=Starting Introduction 
to Contributing to Apache OpenOffice 
Module">[email protected]</a>. 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.</p>
 </li>
 <li>
 <p>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:</p>
 <ol>
-<li><a href="http://apache.org/foundation/how-it-works.html";>How It Works</a> 
(to learn about how the ASF is organized and how its meritocracy works)</li>
-<li><a href="http://www.apache.org/foundation/faq.html";>ASF FAQ's</a> (browse 
to see if it answers any questions you might have)</li>
-<li><a href="http://en.wikipedia.org/wiki/OpenOffice";>OpenOffice Wikipedia 
article</a> (for basic historical background)</li>
+<li><a href="https://apache.org/foundation/how-it-works.html";>How It Works</a> 
(to learn about how the ASF is organized and how its meritocracy works)</li>
+<li><a href="https://www.apache.org/foundation/faq.html";>ASF FAQ's</a> (browse 
to see if it answers any questions you might have)</li>
+<li><a href="https://en.wikipedia.org/wiki/OpenOffice";>OpenOffice Wikipedia 
article</a> (for basic historical background)</li>
 <li><a 
href="https://smartbear.com/blog/test-and-monitor/14-ways-to-contribute-to-open-source-without-being/";>14
 Ways to Contribute to Open Source without Being a Programming Genius or a Rock 
Star</a></li>
 </ol>
 </li>
 <li>
 <p>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:</p>
 <ol>
-<li><a 
href="http://openoffice.apache.org/mailing-lists.html#development-mailing-list-public";>dev</a>
 This is the main mailing list for the project, and gets a lot of traffic. But 
this is where project-wide discussions occur.</li>
-<li><a 
href="http://openoffice.apache.org/mailing-lists.html#announce-mailing-list";>announce</a>
 This is the official announcement list for the project. It is used for 
announcing things like new releases, security patches, conferences, etc.</li>
-<li><a 
href="http://openoffice.apache.org/mailing-lists.html#users-mailing-list-public";>users</a>
 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.</li>
+<li><a 
href="https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public";>dev</a>
 This is the main mailing list for the project, and gets a lot of traffic. But 
this is where project-wide discussions occur.</li>
+<li><a 
href="https://openoffice.apache.org/mailing-lists.html#announce-mailing-list";>announce</a>
 This is the official announcement list for the project. It is used for 
announcing things like new releases, security patches, conferences, etc.</li>
+<li><a 
href="https://openoffice.apache.org/mailing-lists.html#users-mailing-list-public";>users</a>
 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.</li>
 </ol>
 </li>
 <li>
-<p>You can also review other mailing lists we host and which may be of 
interest, including ones focused on specific <a 
href="http://openoffice.apache.org/mailing-lists.html";>project functions</a> 
and <a href="http://openoffice.apache.org/native-lang.html";>native 
languages</a>.</p>
+<p>You can also review other mailing lists we host and which may be of 
interest, including ones focused on specific <a 
href="https://openoffice.apache.org/mailing-lists.html";>project functions</a> 
and <a href="https://openoffice.apache.org/native-lang.html";>native 
languages</a>.</p>
 </li>
 <li>
 <p>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".</p>
@@ -162,19 +162,19 @@ Apache, then much of this will already b
 <p>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.</p>
 </li>
 <li>
-<p>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 <a 
href="http://openoffice.apache.org/mailing-lists.html#participation-guidelines";>Participation
 Guidelines</a> and <a 
href="http://openoffice.apache.org/list-conduct.html";>List Conduct 
Guidelines</a> for more information.</p>
+<p>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 <a 
href="https://openoffice.apache.org/mailing-lists.html#participation-guidelines";>Participation
 Guidelines</a> and <a 
href="https://openoffice.apache.org/list-conduct.html";>List Conduct 
Guidelines</a> for more information.</p>
 </li>
 <li>
-<p>From Karl Fogel's book <a href="http://producingoss.com/";>"Producing Open 
Source Software"</a> read through <a 
href="http://producingoss.com/en/communications.html#you-are-what-you-write";>"You
 Are What You Write"</a> and <a 
href="http://producingoss.com/en/common-pitfalls.html";>"Avoiding Common 
Pitfalls"</a>.</p>
+<p>From Karl Fogel's book <a href="https://producingoss.com/";>"Producing Open 
Source Software"</a> read through <a 
href="https://producingoss.com/en/communications.html#you-are-what-you-write";>"You
 Are What You Write"</a> and <a 
href="https://producingoss.com/en/common-pitfalls.html";>"Avoiding Common 
Pitfalls"</a>.</p>
 </li>
 <li>
 <p>Aside from the mailing lists there are several online services that every 
volunteer should be signed up for:</p>
 <ol>
-<li>Our <a href="http://wiki.openoffice.org/wiki/Main_Page";>MediaWiki</a> 
(sometimes called MWiki) used for user documentation and many other things.</li>
+<li>Our <a href="https://wiki.openoffice.org/wiki/Main_Page";>MediaWiki</a> 
(sometimes called MWiki) used for user documentation and many other things.</li>
 <li>Our <a 
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home";>ConfluenceWiki</a>
 (sometimes called CWiki) where we do project planning.</li>
-<li>Our <a href="https://bz.apache.org/ooo/";>Bugzilla database</a> (sometimes 
called BZ) where we  report and track status on bugs.</li>
-<li>Our <a href="http://forum.openoffice.org/";>Community Forums</a> These are 
available in several languages. This is the primary way in which we engage with 
the user community.</li>
-<li>Join our <a href="http://openoffice.apache.org/social.html";>Social 
Networks</a></li>
+<li>Our <a href="https://bz.apache.org/ooo/";>Bugzilla database</a> (sometimes 
called BZ) where we report and track status on bugs.</li>
+<li>Our <a href="https://forum.openoffice.org/";>Community Forums</a> These are 
available in several languages. This is the primary way in which we engage with 
the user community.</li>
+<li>Join our <a href="https://openoffice.apache.org/social.html";>Social 
Networks</a></li>
 </ol>
 </li>
 <li>


Reply via email to