Author: buildbot
Date: Fri Apr 7 20:32:30 2017
New Revision: 1009996
Log:
Staging update by buildbot for openoffice
Added:
websites/staging/openoffice/trunk/content/googlec170bf1dc88380dd.html
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
websites/staging/openoffice/trunk/content/contact.html
websites/staging/openoffice/trunk/content/developer-faqs.html
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Apr 7 20:32:30 2017
@@ -1 +1 @@
-1790618
+1790627
Modified: websites/staging/openoffice/trunk/content/contact.html
==============================================================================
--- websites/staging/openoffice/trunk/content/contact.html (original)
+++ websites/staging/openoffice/trunk/content/contact.html Fri Apr 7 20:32:30
2017
@@ -126,7 +126,7 @@ h2:hover > .headerlink, h3:hover > .head
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
<p>Any questions dealing with the use of Apache OpenOffice maybe directed to
either the user web forums at:</p>
<ul>
-<li><a
href="https://forum.openoffice.org";>https://forum.openoffice.org</a>.</li>
+<li><a
href="https://forum.openoffice.org";>https://forum.openoffice.org</a></li>
</ul>
<p>or if you prefer to use a mailing list:</p>
<ul>
@@ -135,15 +135,15 @@ h2:hover > .headerlink, h3:hover > .head
</ul>
<p>For any questions, comments, or concerns about this project or website
please contact the project on the developer mailing list:</p>
<ul>
-<li><a
href="mailto:[email protected]";>[email protected]</a>.</li>
+<li><a
href="mailto:[email protected]";>[email protected]</a></li>
</ul>
<p>For private or legal matters, please contact the Project Management
Committee (PMC):</p>
<ul>
-<li><a
href="mailto:[email protected]";>[email protected]</a>.</li>
+<li><a
href="mailto:[email protected]";>[email protected]</a></li>
</ul>
<p>For security issues, please contact the private security list:</p>
<ul>
-<li><a
href="mailto:[email protected]";>[email protected]</a>.</li>
+<li><a
href="mailto:[email protected]";>[email protected]</a></li>
</ul>
</div>
Modified: websites/staging/openoffice/trunk/content/developer-faqs.html
==============================================================================
--- websites/staging/openoffice/trunk/content/developer-faqs.html (original)
+++ websites/staging/openoffice/trunk/content/developer-faqs.html Fri Apr 7
20:32:30 2017
@@ -128,7 +128,7 @@ h2:hover > .headerlink, h3:hover > .head
<div class="toc">
<ul>
<li><a href="#where-can-i-find-out-more-about-code-development">Where can I
find out more about code development?</a></li>
-<li><a href="#ive-just-been-voted-in-as-a-committer-what-do-i-need-to-do">I've
just been voted in as a Committer. What do I need to do?</a></li>
+<li><a href="#ive-just-been-voted-in-as-a-committer-what-do-i-need-to-do">I've
just been voted in as a Committer. What do I need to do?</a></li>
<li><a
href="#im-not-a-committer-but-would-like-to-contribute-what-should-i-do">I'm
not a committer, but would like to contribute, what should I do?</a></li>
<li><a href="#how-do-i-use-apache-subversion">How do I use Apache
Subversion?</a></li>
<li><a href="#where-can-i-download-developer-builds">Where can I download
developer builds?</a></li>
@@ -136,58 +136,58 @@ h2:hover > .headerlink, h3:hover > .head
</ul>
</div>
<h2 id="where-can-i-find-out-more-about-code-development">Where can I find out
more about code development?<a class="headerlink"
href="#where-can-i-find-out-more-about-code-development" title="Permanent
link">¶</a></h2>
-<p>You might want to start by reviewing the legacy information on <a
href="http://www.openoffice.org/development/";>OpenOffice.org
+<p>You might want to start by reviewing the legacy information on <a
href="https://www.openoffice.org/development/";>OpenOffice.org
development</a>. Or, take
-a look at information posted on the <a
href="http://wiki.openoffice.org/wiki/Main_Page";>Apache OpenOffice wiki</a>
+a look at information posted on the <a
href="https://wiki.openoffice.org/wiki/Main_Page";>Apache OpenOffice wiki</a>
under <em>Documentation - For Developers</em>.</p>
<p>Of course, you will need the <a
href="http://openoffice.apache.org/source.html";>source code</a> to do anything.
We recommend building in your own environment as a first step.</p>
<p>You don't have to be an actual committer to submit code. You can submit
patches through
the Apache OpenOffice Bugzilla issue reporting system. You simply need to file
an issue
and supply your patch as an attachment to the issue.</p>
<p>Please also see our <a
href="http://openoffice.apache.org/orientation/index.html";>Orientation
Modules</a> for information on how the project works and identifying
outstanding development tasks.</p>
-<h2 id="ive-just-been-voted-in-as-a-committer-what-do-i-need-to-do">I've just
been voted in as a Committer. What do I need to do?<a class="headerlink"
href="#ive-just-been-voted-in-as-a-committer-what-do-i-need-to-do"
title="Permanent link">¶</a></h2>
-<p>First, congratulations. Your contributions to the project have been noted
and we
+<h2 id="ive-just-been-voted-in-as-a-committer-what-do-i-need-to-do">I've just
been voted in as a Committer. What do I need to do?<a class="headerlink"
href="#ive-just-been-voted-in-as-a-committer-what-do-i-need-to-do"
title="Permanent link">¶</a></h2>
+<p>First, congratulations. Your contributions to the project have been noted
and we
hope that as a Committer you will be even more active.</p>
<p>But before you are officially given Committer permissions, there are a few
administrative steps that you will need to complete. </p>
<ol>
-<li>Submit a signed <a href="http://www.apache.org/licenses/icla.txt";>ICLA</a>
to Apache.</li>
-<li>Wait for the ICLA to be received and recorded by Apache. You will know
-when this has occurred when your name appears in the <a
href="http://people.apache.org/committer-index.html#unlistedclas";>Unlisted
ICLAs</a> section
-on the Apache Committers page. This could take a couple of days, longer if you
+<li>Submit a signed <a
href="https://www.apache.org/licenses/icla.txt";>ICLA</a> to Apache.</li>
+<li>Wait for the ICLA to be received and recorded by Apache. You will know
+when this has occurred when your name appears in the <a
href="https://people.apache.org/committer-index.html#unlistedclas";>Unlisted
ICLAs</a> section
+on the Apache Committers page. This could take a couple of days, longer if you
submitted the ICLA via post.</li>
<li>Once the your ICLA has been recorded, you should send a note to the <a
href="mailto:[email protected]";>PMC</a>
-and request an Apache account. You will want to include your full name and
email address,
-as you entered in the ICLA, as well as your preferred userid. Please <a
href="http://people.apache.org/committer-index.html";>check first</a>
+and request an Apache account. You will want to include your full name and
email address,
+as you entered in the ICLA, as well as your preferred userid. Please <a
href="https://people.apache.org/committer-index.html";>check first</a>
that your preferred userid is not already in use by another Apache
Committer.</li>
<li>Once your Apache account has been created, you will receive an email with
-further instructions for setting up your account. This may take a couple of
days.</li>
+further instructions for setting up your account. This may take a couple of
days.</li>
<li>
<p>If you were also voted as a PMC member, you should then <a
href="mailto:[email protected]";>subscribe</a> to the
PMC's private mailing list.</p>
</li>
<li>
-<p>Finally, you should read the <a
href="http://www.apache.org/dev/new-committers-guide.html";>"Guide for new
committers"</a></p>
+<p>Finally, you should read the <a
href="https://www.apache.org/dev/new-committers-guide.html";>"Guide for new
committers"</a></p>
</li>
</ol>
<h2 id="im-not-a-committer-but-would-like-to-contribute-what-should-i-do">I'm
not a committer, but would like to contribute, what should I do?<a
class="headerlink"
href="#im-not-a-committer-but-would-like-to-contribute-what-should-i-do"
title="Permanent link">¶</a></h2>
<p>Apache OpenOffice welcomes your contributions!</p>
-<p>To contribute to the OpenOffice product, you will need to submit subversion
patches ("diff" files), and attach them to issues in our <a
href="http://issues.openoffice.org";>issues reporting system</a>, Bugzilla.</p>
+<p>To contribute to the OpenOffice product, you will need to submit subversion
patches ("diff" files), and attach them to issues in our <a
href="https://bz.apache.org/ooo/";>issues reporting system</a>, Bugzilla.</p>
<p>Your contributions will be recognized by the committer submitting the PATCH
in the
-log entry for the committed patch, and you will be added to the <a
href="http://www.openoffice.org/welcome/credits.html";>OpenOffice credits
page</a>
+log entry for the committed patch, and you will be added to the <a
href="https://www.openoffice.org/welcome/credits.html";>OpenOffice credits
page</a>
to recognize your contribution.</p>
<p>The following sections will explain more about this.</p>
<h2 id="how-do-i-use-apache-subversion">How do I use Apache Subversion?<a
class="headerlink" href="#how-do-i-use-apache-subversion" title="Permanent
link">¶</a></h2>
-<p>Instructions can be found on the <a
href="http://openoffice.apache.org/svn-basics.html";>Subversion Basics</a>
page.</p>
+<p>Instructions can be found on the <a href="svn-basics.html">Subversion
Basics</a> page.</p>
<p>Please note that we are using a Subversion/Bugzilla integration,
e.g. when you are committing something and mention the bugzilla issue in
the commit summary, then this bugzilla issue gets automatically updated
with some short info about the change. The recommended notation to mention
e.g. issue 1234 is to use a #i1234# at the start of the commit message
summary.</p>
<h2 id="where-can-i-download-developer-builds">Where can I download developer
builds?<a class="headerlink" href="#where-can-i-download-developer-builds"
title="Permanent link">¶</a></h2>
-<p>Developer builds are not official releases and may be unstable. But they
can be useful to download for those who
-need early access to builds, but who do not want to compile their own build.
They are announced and discussed only on the development list, as they are not
production builds. Apache OpenOffice currently has two types of development
builds: those generated by buildbots, and those manually generated/built. </p>
-<p>Apache OpenOffice makes use of buildbots for some of our environments. You
can review the Apache OpenOffice buildbot information <a
href="http://ci.apache.org/projects/openoffice/";>here</a>. Additional
information on buildbot builds for linux64, window7, and linux32 can be found
<a href="http://ci.apache.org/builders/";>here</a>.</p>
+<p>Developer builds are not official releases and may be unstable. But they
can be useful to download for those who
+need early access to builds, but who do not want to compile their own build.
They are announced and discussed only on the development list, as they are not
production builds. Apache OpenOffice currently has two types of development
builds: those generated by buildbots, and those manually generated/built.</p>
+<p>Apache OpenOffice makes use of buildbots for some of our environments. You
can review the Apache OpenOffice buildbot information <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info";>here</a>.
Additional information on buildbot builds for linux64, window7, and linux32
can be found <a href="http://ci.apache.org/builders/";>here</a>.</p>
<p>Development snapshots, which are manually generated, are used as the final
step leading up to a release. These are used for final testing before an
approved release. You will also find helpful hints for specific platform
building here.</p>
<blockquote>
<p><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds";>the
Unofficial Development Snapshots page</a></p>
Added: websites/staging/openoffice/trunk/content/googlec170bf1dc88380dd.html
==============================================================================
--- websites/staging/openoffice/trunk/content/googlec170bf1dc88380dd.html
(added)
+++ websites/staging/openoffice/trunk/content/googlec170bf1dc88380dd.html Fri
Apr 7 20:32:30 2017
@@ -0,0 +1,79 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<meta name="description" content="The official developer website of the Apache
OpenOffice open source project, home of OpenOffice Writer, Calc, Impress, Draw
and Base." />
+<meta name="keywords" content="OpenOffice, Open Office, Apache OpenOffice,
Apache Open Office, OpenOffice.org, Developer, Project, Website, Official,
Writer, Calc, Impress, Draw, Base, ODF, Open Document Format" />
+<meta name="google-site-verification"
content="wIHUbgA-JO5PaJHpR5jeI8N9E2y2iF94o4oUwpaAdk8" />
+<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" />
+<link rel="icon" href="/favicon.ico" type="image/x-icon" />
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+<script type="text/javascript">
+
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-30193653-3']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript';
ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' :
'https://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga, s);
+ })();
+
+</script>
+</head>
+
+<body>
+ <div id="banner">
+ <div id="bannerleft"><a alt="Apache OpenOffice"
href="https://openoffice.apache.org/";>
+ <img id="logo" alt="Apache OpenOffice"
src="https://www.openoffice.org/images/AOO_logos/AOO4_website_logo.png"/></a></div>
+
+ <div id="bannercenter"><br/> The Free and Open Productivity Suite</div>
+ </div>
+ <div id="clear"></div>
+
+ <div id="content">
+
+
+
+ </div>
+
+ <div id="footera">
+ <div id="poweredby">
+ <p><a href="https://www.apache.org/";><img
src="/images/asf_logo_small.png" alt="Apache Software Foundation" height="76"
width="188"/></a></p>
+ </div>
+ <div id="copyrighta">
+ <p style="text-align:center;">
+ Copyright © 2011-2017 The Apache Software Foundation, Licensed
under the <a href="https://www.apache.org/licenses/LICENSE-2.0";>Apache License,
Version 2.0</a> | <a href="/contact.html">Contact Us</a> | <a
href="/terms.html">Terms of Use</a>
+ </p>
+ <p>
+ Apache and the Apache feather logo are trademarks of The Apache Software
Foundation.
+ OpenOffice.org and the seagull logo are registered trademarks of The Apache
Software Foundation.
+ Other names appearing on the site may be trademarks of their respective
owners.
+ </p>
+
+ </div>
+ </div>
+
+</body>
+</html>
![https://www.openoffice.org/images/AOO_logos/AOO4_website_logo.png"/](https://www.openoffice.org/images/AOO_logos/AOO4_website_logo.png"/){kind=link}