Author: buildbot
Date: Fri Jan 18 00:14:32 2013
New Revision: 847090
Log:
Staging update by buildbot for openoffice
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
websites/staging/openoffice/trunk/content/orientation/intro-development.html
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 18 00:14:32 2013
@@ -1 +1 @@
-1434963
+1434981
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 Jan 18 00:14:32 2013
@@ -116,38 +116,38 @@ project, etc. A quick review is a good
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 every country in the
world (except North Korea). So the work you do, the bugs you fix,
+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>
-<p>It all starts by establish a local build environment. Building OpenOffice
on Linux or Mac is relatively easy,
+<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>
-<p>Our <a
href="http://wiki.openoffice.org/wiki/Documentation/Building_Guide";>Building
Guide</a> on the wiki is your starting point. Follow the instructions there,
step by step. Ask questions on
+<p>Our <a
href="http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO";>Building
Guide</a> on the wiki is your starting point. Follow the instructions there,
step by step. Ask questions on
the dev list if you get stuck. If you get an error it can be useful to search
our <a
href="http://markmail.org/search/+list:org.apache.incubator.ooo-dev";>mailing
list archives</a> to see if it
-is a know problem with a known solution.</p>
-<p>Note also the the current list of configuration flags used in building the
development snapshot builds at the
+is a known problem with a known solution.</p>
+<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:d...@openoffice.apache.org?subject=Succesful 1st Build!">post a
note to the dev list</a> for some well-earned congratulations!</p>
+<p>Once you have a successful build, <a
href="mailto:d...@openoffice.apache.org?subject=Successful 1st Build!">post a
note to the dev list</a> for some well-earned congratulations!</p>
<h2 id="orienting-yourself">Orienting Yourself</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>
<li>Adfinis Sygroup hosts an <a
href="http://opengrok.adfinis-sygroup.org/source/";>instance of OpenGrok</a> for
us which is useful
for understanding the code.</li>
-<li>We have an <a href="https://fisheye6.atlassian.com/browse/ooo";>instance of
Altsassian Fisheye</a> which can be useful for browsing the code base and
understanding dependencies. (This service is currently broken but we hope to
have it back soon).</li>
+<li>We have an <a href="https://fisheye6.atlassian.com/browse/ooo";>instance of
Altassian 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>
<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
-all coding-related tasks in Bugzilla is that it helps our QA volunteer know
which areas to test. Whether code was changed to fix a bug or enhance a
feature -- the QA impact is pretty
+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.</p>
<p>If you have not done so already, please <a
href="https://issues.apache.org/ooo/createaccount.cgi";>sign up for a Bugzilla
account</a>. This will allow you to enter new bugs or tasks, but also
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?cmdtype=runnamed&namedcmd=easy-hacks&list_id=41609";>easy-hacks</a>
and <a
href="https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamed&list_id=41611&namedcmd=simple-hacks";>simple-hacks</a>
queries.</p>
-<p>One 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.<br />
+<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.<br />
</p>
<h2 id="coding-standards">Coding Standards</h2>
<p>For reference note the following coding standards for the project:</p>
@@ -172,7 +172,7 @@ a lot of information, some of it up-to-d
</ul>
<h2 id="module-completion">Module Completion</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:q...@openoffice.apache.org?subject=Completed Introduction to
Development">q...@openoffice.apache.org</a>so we know.</p>
+your information. Congratulations! Please send a note to <a
href="mailto:q...@openoffice.apache.org?subject=Completed Introduction to
Development">q...@openoffice.apache.org</a> so we know.</p>
</div>
<div id="footera">
