Author: pescetti
Date: Fri Jan 18 00:14:27 2013
New Revision: 1434981
URL: http://svn.apache.org/viewvc?rev=1434981&view=rev
Log:
Minor fixes.
Modified:
openoffice/site/trunk/content/orientation/intro-development.mdtext
Modified: openoffice/site/trunk/content/orientation/intro-development.mdtext
URL:
http://svn.apache.org/viewvc/openoffice/site/trunk/content/orientation/intro-development.mdtext?rev=1434981&r1=1434980&r2=1434981&view=diff
==============================================================================
--- openoffice/site/trunk/content/orientation/intro-development.mdtext
(original)
+++ openoffice/site/trunk/content/orientation/intro-development.mdtext Fri Jan
18 00:14:27 2013
@@ -43,26 +43,26 @@ you'll love this project! There are tas
in the project who are happy to answer your questions.
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.
## Building OpenOffice
-It all starts by establish a local build environment. Building OpenOffice on
Linux or Mac is relatively easy,
+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.
Building on Windows is more complicated, due to the need to install more
prerequisite tools.
-Our [Building
Guide](http://wiki.openoffice.org/wiki/Documentation/Building_Guide) on the
wiki is your starting point. Follow the instructions there, step by step. Ask
questions on
+Our [Building
Guide](http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO) 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 [mailing list
archives](http://markmail.org/search/+list:org.apache.incubator.ooo-dev) to see
if it
-is a know problem with a known solution.
+is a known problem with a known solution.
-Note also the the current list of configuration flags used in building the
development snapshot builds at the
+Note also the current list of configuration flags used in building the
development snapshot builds at the
bottom of the [development snapshot builds
page](https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOO3.4.1).
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.
-Once you have a successful build, [post a note to the dev
list](mailto:[email protected]?subject=Succesful 1st Build!) for some
well-earned congratulations!
+Once you have a successful build, [post a note to the dev
list](mailto:[email protected]?subject=Successful 1st Build!) for some
well-earned congratulations!
## Orienting Yourself
@@ -71,8 +71,7 @@ A few suggestions to help you find your
- An explanation of the purpose/function of the various [source
directories](http://wiki.openoffice.org/wiki/Source_code_directories)
- Adfinis Sygroup hosts an [instance of
OpenGrok](http://opengrok.adfinis-sygroup.org/source/) for us which is useful
for understanding the code.
- - We have an [instance of Altsassian
Fisheye](https://fisheye6.atlassian.com/browse/ooo) 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).
-
+ - We have an [instance of Altassian
Fisheye](https://fisheye6.atlassian.com/browse/ooo) which can be useful for
browsing the code base and understanding dependencies.
## Finding Easy Tasks
@@ -80,7 +79,7 @@ As a new developer you will want to find
OpenOffice is put together. The tasks are more localized. By doing easy
tasks you gain experience and confidence hacking with the code base.
We use a [Bugzilla issue tracker](https://issues.apache.org/ooo/) 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.
If you have not done so already, please [sign up for a Bugzilla
account](https://issues.apache.org/ooo/createaccount.cgi). This will allow you
to enter new bugs or tasks, but also
@@ -89,7 +88,7 @@ assign yourself existing ones.
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
[easy-hacks](https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamed&namedcmd=easy-hacks&list_id=41609)
and
[simple-hacks](https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamed&list_id=41611&namedcmd=simple-hacks)
queries.
-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.
+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.
## Coding Standards
@@ -120,7 +119,5 @@ a lot of information, some of it up-to-d
## Module Completion
Once you have completed this module, go to our our [Directory of
Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers)
wiki page and add or update
-your information. Congratulations! Please send a note to
[[email protected]](mailto:[email protected]?subject=Completed
Introduction to Development)so we know.
-
-
+your information. Congratulations! Please send a note to
[[email protected]](mailto:[email protected]?subject=Completed
Introduction to Development) so we know.
