Author: buildbot
Date: Fri Oct 21 14:57:02 2016
New Revision: 999749
Log:
Staging update by buildbot for openoffice
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
websites/staging/openoffice/trunk/content/orientation/decision-making.html
websites/staging/openoffice/trunk/content/orientation/how-aoo-project-works.html
websites/staging/openoffice/trunk/content/orientation/infrastructure.html
websites/staging/openoffice/trunk/content/orientation/intro-contributing.html
websites/staging/openoffice/trunk/content/orientation/intro-development.html
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 21 14:57:02 2016
@@ -1 +1 @@
-1764997
+1766036
Modified:
websites/staging/openoffice/trunk/content/orientation/decision-making.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/decision-making.html
(original)
+++ websites/staging/openoffice/trunk/content/orientation/decision-making.html
Fri Oct 21 14:57:02 2016
@@ -49,7 +49,18 @@
<div id="clear"></div>
<div id="sidenav">
- <h1 id="general">General</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<h1 id="general">General<a class="headerlink" href="#general" title="Permanent
link">¶</a></h1>
<ul>
<li><a href="/index.html">About</a></li>
<li><a href="/downloads.html">Downloads</a></li>
@@ -58,7 +69,7 @@
<li><a href="/press.html">Press</a></li>
<li><a href="http://www.openoffice.org/";>OpenOffice.org website</a></li>
</ul>
-<h1 id="community">Community</h1>
+<h1 id="community">Community<a class="headerlink" href="#community"
title="Permanent link">¶</a></h1>
<ul>
<li><a href="/get-involved.html">Get Involved</a></li>
<li><a href="/orientation/index.html">Orientation</a></li>
@@ -71,7 +82,7 @@
<li><a href="/people.html">People</a></li>
<li><a href="/community-faqs.html">Community FAQs</a></li>
</ul>
-<h1 id="development">Development</h1>
+<h1 id="development">Development<a class="headerlink" href="#development"
title="Permanent link">¶</a></h1>
<ul>
<li><a href="/source.html">Source Code</a></li>
<li><a href="/bug-tracking.html">Bug Tracking</a></li>
@@ -82,12 +93,12 @@
<li><a href="/contributing-code.html">Contributing Code</a> </li>
<li><a href="/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project-management-pmc">Project Management PMC</h1>
+<h1 id="project-management-pmc">Project Management PMC<a class="headerlink"
href="#project-management-pmc" title="Permanent link">¶</a></h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/";>Project Blog</a></li>
<li><a href="/pmc-faqs.html">PMC FAQs</a> </li>
</ul>
-<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation<a
class="headerlink" href="#the-apache-software-foundation" title="Permanent
link">¶</a></h1>
<ul>
<li><a href="http://www.apache.org/";>Website</a></li>
<li><a href="http://www.openoffice.org/donations.html";>Donations</a></li>
@@ -98,7 +109,18 @@
<div id="contenta">
<h1 class="title">Decision Making</h1>
- <p>In this Orientation Module you will learn about Decision Making within
the project. As with the previous Level 1 Module, if you have prior experience
with an
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>In this Orientation Module you will learn about Decision Making within the
project. As with the previous Level 1 Module, if you have prior experience
with an
open source software project, especially one at Apache, then much of this
material will already be familiar to you.</p>
<p>In the previous Module we read about collaboration on the mailings lists,
how to do it efficiently and how to avoid the most common pitfalls. We use the
mailing lists for many things,
for asking questions, for sharing information or the like. But one of the
most important uses of the mailing list is for decision making. It is
important to understand
@@ -192,7 +214,7 @@ you when you apply then in your own list
</li>
</ol>
<p>Congratulations, you have completed this Module! </p>
-<p>If you have any questions or feedback on this module, please send a note to
<a
href="mailto:[email protected]?subject=Comments%20on%20Decision%20Making%20Module";>[email protected]</a>.</p>
+<p>If you have any questions or feedback on this module, please send a note to
<a href="mailto:[email protected]?subject=Comments on Decision
Making Module">[email protected]</a>.</p>
</div>
<div id="footera">
Modified:
websites/staging/openoffice/trunk/content/orientation/how-aoo-project-works.html
==============================================================================
---
websites/staging/openoffice/trunk/content/orientation/how-aoo-project-works.html
(original)
+++
websites/staging/openoffice/trunk/content/orientation/how-aoo-project-works.html
Fri Oct 21 14:57:02 2016
@@ -49,7 +49,18 @@
<div id="clear"></div>
<div id="sidenav">
- <h1 id="general">General</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<h1 id="general">General<a class="headerlink" href="#general" title="Permanent
link">¶</a></h1>
<ul>
<li><a href="/index.html">About</a></li>
<li><a href="/downloads.html">Downloads</a></li>
@@ -58,7 +69,7 @@
<li><a href="/press.html">Press</a></li>
<li><a href="http://www.openoffice.org/";>OpenOffice.org website</a></li>
</ul>
-<h1 id="community">Community</h1>
+<h1 id="community">Community<a class="headerlink" href="#community"
title="Permanent link">¶</a></h1>
<ul>
<li><a href="/get-involved.html">Get Involved</a></li>
<li><a href="/orientation/index.html">Orientation</a></li>
@@ -71,7 +82,7 @@
<li><a href="/people.html">People</a></li>
<li><a href="/community-faqs.html">Community FAQs</a></li>
</ul>
-<h1 id="development">Development</h1>
+<h1 id="development">Development<a class="headerlink" href="#development"
title="Permanent link">¶</a></h1>
<ul>
<li><a href="/source.html">Source Code</a></li>
<li><a href="/bug-tracking.html">Bug Tracking</a></li>
@@ -82,12 +93,12 @@
<li><a href="/contributing-code.html">Contributing Code</a> </li>
<li><a href="/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project-management-pmc">Project Management PMC</h1>
+<h1 id="project-management-pmc">Project Management PMC<a class="headerlink"
href="#project-management-pmc" title="Permanent link">¶</a></h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/";>Project Blog</a></li>
<li><a href="/pmc-faqs.html">PMC FAQs</a> </li>
</ul>
-<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation<a
class="headerlink" href="#the-apache-software-foundation" title="Permanent
link">¶</a></h1>
<ul>
<li><a href="http://www.apache.org/";>Website</a></li>
<li><a href="http://www.openoffice.org/donations.html";>Donations</a></li>
@@ -98,9 +109,20 @@
<div id="contenta">
<h1 class="title">How the Apache OpenOffice Project Works
</h1>
- <ol>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<ol>
<li>
-<p>Please send an email to <a
href="mailto:[email protected]?subject=Starting%20How%20the%20Apache%20OpenOffice%20Project%20Works";>[email protected]</a>
to let us know you are working on this module.</p>
+<p>Please send an email to <a
href="mailto:[email protected]?subject=Starting How the Apache
OpenOffice Project Works">[email protected]</a> to let us know
you are working on this module.</p>
</li>
<li>
<p>As you learned in the <a href="intro-contributing.html">previous module</a>
the Apache Software Foundation formally has Members, who elect a Board of
Directors who appoint Officers, including
@@ -134,7 +156,7 @@ users around the globe. This includes t
</ul>
</li>
<li>
-<p>Congratulations! You have completed this Level. Please send a note to <a
href="mailto:[email protected]?subject=Completed%20How%20the%20Apache%20OpenOffice%20Project%20Works";>[email protected]</a>
so
+<p>Congratulations! You have completed this Level. Please send a note to <a
href="mailto:[email protected]?subject=Completed How the Apache
OpenOffice Project Works">[email protected]</a> 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.</p>
</li>
</ol>
Modified:
websites/staging/openoffice/trunk/content/orientation/infrastructure.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/infrastructure.html
(original)
+++ websites/staging/openoffice/trunk/content/orientation/infrastructure.html
Fri Oct 21 14:57:02 2016
@@ -49,7 +49,18 @@
<div id="clear"></div>
<div id="sidenav">
- <h1 id="general">General</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<h1 id="general">General<a class="headerlink" href="#general" title="Permanent
link">¶</a></h1>
<ul>
<li><a href="/index.html">About</a></li>
<li><a href="/downloads.html">Downloads</a></li>
@@ -58,7 +69,7 @@
<li><a href="/press.html">Press</a></li>
<li><a href="http://www.openoffice.org/";>OpenOffice.org website</a></li>
</ul>
-<h1 id="community">Community</h1>
+<h1 id="community">Community<a class="headerlink" href="#community"
title="Permanent link">¶</a></h1>
<ul>
<li><a href="/get-involved.html">Get Involved</a></li>
<li><a href="/orientation/index.html">Orientation</a></li>
@@ -71,7 +82,7 @@
<li><a href="/people.html">People</a></li>
<li><a href="/community-faqs.html">Community FAQs</a></li>
</ul>
-<h1 id="development">Development</h1>
+<h1 id="development">Development<a class="headerlink" href="#development"
title="Permanent link">¶</a></h1>
<ul>
<li><a href="/source.html">Source Code</a></li>
<li><a href="/bug-tracking.html">Bug Tracking</a></li>
@@ -82,12 +93,12 @@
<li><a href="/contributing-code.html">Contributing Code</a> </li>
<li><a href="/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project-management-pmc">Project Management PMC</h1>
+<h1 id="project-management-pmc">Project Management PMC<a class="headerlink"
href="#project-management-pmc" title="Permanent link">¶</a></h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/";>Project Blog</a></li>
<li><a href="/pmc-faqs.html">PMC FAQs</a> </li>
</ul>
-<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation<a
class="headerlink" href="#the-apache-software-foundation" title="Permanent
link">¶</a></h1>
<ul>
<li><a href="http://www.apache.org/";>Website</a></li>
<li><a href="http://www.openoffice.org/donations.html";>Donations</a></li>
@@ -98,12 +109,23 @@
<div id="contenta">
<h1 class="title">Infrastructure</h1>
- <p>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,
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>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.</p>
<ol>
<li>
-<p>First, Please send an email to <a
href="mailto:[email protected]?subject=Starting%20Infrastructure%20Module";>[email protected]</a>
+<p>First, Please send an email to <a
href="mailto:[email protected]?subject=Starting Infrastructure
Module">[email protected]</a>
to let us know you are working on this module.</p>
</li>
<li>
@@ -179,7 +201,7 @@ first on the project's mailing list.</li
</ul>
</li>
<li>
-<p>Congratulations! You have completed this Module. Please send a note to <a
href="mailto:[email protected]?subject=Completed%20Infrastructure%20Module";>[email protected]</a>
so
+<p>Congratulations! You have completed this Module. Please send a note to <a
href="mailto:[email protected]?subject=Completed Infrastructure
Module">[email protected]</a> 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.</p>
</li>
</ol>
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
Fri Oct 21 14:57:02 2016
@@ -128,8 +128,7 @@ the project's mailing mailing list. </p
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
our main public
-mailing list <a href="mailto:[email protected]?subject=Starting
Introduction to Contributing to Apache OpenOffice
Module">[email protected]</a>. Who are you, where
+<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>
@@ -170,7 +169,7 @@ specific <a href="http://openoffice.apac
</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
+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>
</li>
<li>
@@ -203,7 +202,7 @@ and <a href="http://openoffice.apache.or
</li>
<li>
<p>Finally, once you have done the above, go to our our <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers";>Directory
of Volunteers</a> wiki page and add your
-information. Congratulations! Please send a note to <a
href="mailto:[email protected]?subject=Completed Introduction to
Contributing to Apache OpenOffice Module">[email protected]</a>
+information. Congratulations! Please send a note to <a
href="mailto:[email protected]?subject=Completed Introduction
to Contributing to Apache OpenOffice
Module">[email protected]</a>
so we know.</p>
</li>
</ol>
Modified:
websites/staging/openoffice/trunk/content/orientation/intro-development.html
==============================================================================
---
websites/staging/openoffice/trunk/content/orientation/intro-development.html
(original)
+++
websites/staging/openoffice/trunk/content/orientation/intro-development.html
Fri Oct 21 14:57:02 2016
@@ -49,7 +49,18 @@
<div id="clear"></div>
<div id="sidenav">
- <h1 id="general">General</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<h1 id="general">General<a class="headerlink" href="#general" title="Permanent
link">¶</a></h1>
<ul>
<li><a href="/index.html">About</a></li>
<li><a href="/downloads.html">Downloads</a></li>
@@ -58,7 +69,7 @@
<li><a href="/press.html">Press</a></li>
<li><a href="http://www.openoffice.org/";>OpenOffice.org website</a></li>
</ul>
-<h1 id="community">Community</h1>
+<h1 id="community">Community<a class="headerlink" href="#community"
title="Permanent link">¶</a></h1>
<ul>
<li><a href="/get-involved.html">Get Involved</a></li>
<li><a href="/orientation/index.html">Orientation</a></li>
@@ -71,7 +82,7 @@
<li><a href="/people.html">People</a></li>
<li><a href="/community-faqs.html">Community FAQs</a></li>
</ul>
-<h1 id="development">Development</h1>
+<h1 id="development">Development<a class="headerlink" href="#development"
title="Permanent link">¶</a></h1>
<ul>
<li><a href="/source.html">Source Code</a></li>
<li><a href="/bug-tracking.html">Bug Tracking</a></li>
@@ -82,12 +93,12 @@
<li><a href="/contributing-code.html">Contributing Code</a> </li>
<li><a href="/developer-faqs.html">Developer FAQs</a></li>
</ul>
-<h1 id="project-management-pmc">Project Management PMC</h1>
+<h1 id="project-management-pmc">Project Management PMC<a class="headerlink"
href="#project-management-pmc" title="Permanent link">¶</a></h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/";>Project Blog</a></li>
<li><a href="/pmc-faqs.html">PMC FAQs</a> </li>
</ul>
-<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation<a
class="headerlink" href="#the-apache-software-foundation" title="Permanent
link">¶</a></h1>
<ul>
<li><a href="http://www.apache.org/";>Website</a></li>
<li><a href="http://www.openoffice.org/donations.html";>Donations</a></li>
@@ -98,27 +109,38 @@
<div id="contenta">
<h1 class="title">Introduction to Development</h1>
- <h2 id="introduction">Introduction</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+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>
+<h2 id="introduction">Introduction<a class="headerlink" href="#introduction"
title="Permanent link">¶</a></h2>
<p>In this orientation module you will learn how to get started programming
OpenOffice. </p>
<p>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.</p>
-<p>Your first task is to subscribe to our Development mailing list. You can
subscribe by sending an email to
-<a
href="mailto:[email protected]";>[email protected]</a>.
</p>
-<p>Then you can introduce yourself by <a
href="mailto:[email protected]?subject=New%20Dev%20Volunteer";>sending
an email to the list</a>.
+<p>Your first task is to subscribe to our Recruitment mailing list. You can
subscribe by sending an email to
+<a
href="mailto:[email protected]";>[email protected]</a>.
</p>
+<p>Then you can introduce yourself by <a
href="mailto:[email protected]?subject=New Dev
Volunteer">sending an email to the list</a>.
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.</p>
<p>Note: In parallel with the Dev-specific items on this page, you may want
to also review the <a
href="http://openoffice.apache.org/orientation/index.html";>Level 1 and Level 2
Orientation Modules</a>. 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.</p>
<p>Now with the introductions out of the way, let's get started!</p>
-<h2 id="openoffice-development-good-the-bad-and-the-ugly">OpenOffice
Development: Good, the Bad and the Ugly</h2>
+<h2 id="openoffice-development-good-the-bad-and-the-ugly">OpenOffice
Development: Good, the Bad and the Ugly<a class="headerlink"
href="#openoffice-development-good-the-bad-and-the-ugly" title="Permanent
link">¶</a></h2>
<p>Let's be honest. The size, age and complexity of OpenOffice's C++ codebase
makes coding a challenge. This is not a trivial codebase to learn. But if you
like a good challenge then
you'll love this project! There are tasks suitable for programmers with a
range of programming experience, and we have many veteran OpenOffice hackers
in the project who are happy to answer your questions. </p>
<p>And in its favor, there are few other programs that you can help develop,
that have the reach of OpenOffice. Many millions of users depend on
OpenOffice,
with another million downloads every week, downloads from almost every country
in the world. So the work you do, the bugs you fix,
the features you add, will benefit millions of users around the world.</p>
-<h2 id="building-openoffice">Building OpenOffice</h2>
+<h2 id="building-openoffice">Building OpenOffice<a class="headerlink"
href="#building-openoffice" title="Permanent link">¶</a></h2>
<p>It all starts by establishing a local build environment. Building
OpenOffice on Linux or Mac is relatively easy,
but expect the first attempt to require some trial and error. Every
configuration is slightly different.</p>
<p>Building on Windows is more complicated, due to the need to install more
prerequisite tools.</p>
@@ -128,8 +150,8 @@ is a known problem with a known solution
<p>Note also the current list of configuration flags used in building the
development snapshot builds at the
bottom of the <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOO3.4.1";>development
snapshot builds page</a>.
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.</p>
-<p>Once you have a successful build, <a
href="mailto:[email protected]?subject=Successful%201st%20Build!";>post
a note to the dev list</a> for some well-earned congratulations!</p>
-<h2 id="orienting-yourself">Orienting Yourself</h2>
+<p>Once you have a successful build, <a
href="mailto:[email protected]?subject=Successful 1st Build!">post a
note to the dev list</a> for some well-earned congratulations!</p>
+<h2 id="orienting-yourself">Orienting Yourself<a class="headerlink"
href="#orienting-yourself" title="Permanent link">¶</a></h2>
<p>A few suggestions to help you find your way around this massive
codebase:</p>
<ul>
<li>An explanation of the purpose/function of the various <a
href="http://wiki.openoffice.org/wiki/Source_code_directories";>source
directories</a></li>
@@ -137,7 +159,7 @@ Although there are many other combinatio
for understanding the code.</li>
<li>We have an <a href="https://fisheye6.atlassian.com/browse/ooo";>instance of
Atlassian Fisheye</a> which can be useful for browsing the code base and
understanding dependencies.</li>
</ul>
-<h2 id="finding-easy-tasks">Finding Easy Tasks</h2>
+<h2 id="finding-easy-tasks">Finding Easy Tasks<a class="headerlink"
href="#finding-easy-tasks" title="Permanent link">¶</a></h2>
<p>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.</p>
<p>We use a <a href="https://issues.apache.org/ooo/";>Bugzilla issue
tracker</a> to track reported defects in OpenOffice. Some of us also use
Bugzilla for tracking feature and enhancement tasks as well. The value of
tracking
@@ -148,7 +170,7 @@ assign yourself existing ones.</p>
<p>Many tasks are classified in the "difficulty" field. The ones classified
as "easy" or "simple" (one level harder than "easy") are good ones to start
with. You can find these with the
<a
href="https://issues.apache.org/ooo/buglist.cgi?f1=cf_fix_difficulty&o1=equals&resolution=---&query_format=advanced&v1=easy&list_id=42478";>easy-hacks</a>
and <a
href="https://issues.apache.org/ooo/buglist.cgi?f1=cf_fix_difficulty&o1=equals&resolution=---&query_format=advanced&v1=simple&list_id=42478";>simple-hacks</a>
queries.</p>
<p>Once you pick a bug and assign it to yourself, you might want to post a
note to the dev list, letting us know. We might have some helpful hints to get
you started. </p>
-<h2 id="coding-standards">Coding Standards</h2>
+<h2 id="coding-standards">Coding Standards<a class="headerlink"
href="#coding-standards" title="Permanent link">¶</a></h2>
<p>For reference note the following coding standards for the project:</p>
<ul>
<li><a href="http://wiki.openoffice.org/wiki/Coding_Standards";>Coding
Standards</a></li>
@@ -157,13 +179,13 @@ assign yourself existing ones.</p>
<p>The Geneva Convention prevents us from forcing you to read all of those
rules, but know that they are there, and
when your code is reviewed your reviewer might refer to some of those rules if
there is an issue. So you'll
absorb them over time.</p>
-<h2 id="submitting-patches">Submitting Patches</h2>
+<h2 id="submitting-patches">Submitting Patches<a class="headerlink"
href="#submitting-patches" title="Permanent link">¶</a></h2>
<p>As you read in the <a
href="http://openoffice.apache.org/orientation/intro-contributing.html";>Introduction
to Contributing to OpenOffice module</a>, contributors who have demonstrated
merit via
their project contributions can be voted in as Committers. Committers have
the ability to check code into project's source control. Contributors who are
not (yet) Committers
must submit their patches and have them be reviewed first.</p>
<p>Please review these <a
href="http://openoffice.apache.org/svn-basics.html#creating_and_submitting_patches";>guidelines
for submitting patches</a>. A good practice is to attach the patch to the
Bugzilla issue and then send a link to the issue to the Dev list, asking for
someone to review and commit the patch.</p>
-<h2 id="other-useful-resources">Other Useful Resources</h2>
+<h2 id="other-useful-resources">Other Useful Resources<a class="headerlink"
href="#other-useful-resources" title="Permanent link">¶</a></h2>
<ul>
<li>The <a href="http://www.openoffice.org/development/";>OpenOffice.org for
Developers</a> web area has
useful information for getting started.</li>
@@ -171,9 +193,9 @@ useful information for getting started.<
a lot of good general development information.</li>
<li>The <a
href="http://openoffice.apache.org/mailing-lists.html#commits-mailing-list";>commits
mailing list</a> echos every checkin made to the code base. Developers are
encouraged to subscribe so they are aware of other changes, and can help
review.</li>
</ul>
-<h2 id="module-completion">Module Completion</h2>
+<h2 id="module-completion">Module Completion<a class="headerlink"
href="#module-completion" title="Permanent link">¶</a></h2>
<p>Once you have completed this module, go to our our <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers";>Directory
of Volunteers</a> wiki page and add or update
-your information. Congratulations! Please send a note to <a
href="mailto:[email protected]?subject=Completed%20Introduction%20to%20Development";>[email protected]</a>
so we know.</p>
+your information. Congratulations! Please send a note to <a
href="mailto:[email protected]?subject=Completed Introduction
to Development">[email protected]</a> so we know.</p>
</div>
<div id="footera">
