Author: robweir
Date: Tue Jan 15 19:08:41 2013
New Revision: 1433585
URL: http://svn.apache.org/viewvc?rev=1433585&view=rev
Log:
CMS commit to openoffice by robweir
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=1433585&r1=1433584&r2=1433585&view=diff
==============================================================================
--- openoffice/site/trunk/content/orientation/intro-development.mdtext
(original)
+++ openoffice/site/trunk/content/orientation/intro-development.mdtext Tue Jan
15 19:08:41 2013
@@ -64,6 +64,16 @@ Although there are many other combinatio
Once you have a successful build, [post a note to the dev
list](mailto:d...@openoffice.apache.org?subject=Succesful 1st Build!) for some
well-earned congratulations!
+## Orienting Yourself
+
+A few suggestions to help you find your way around this massive codebase:
+
+ - 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).
+
+
## Finding Easy Tasks
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
@@ -81,6 +91,16 @@ Many tasks are classified in the "diffic
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.
+## Coding Standards
+
+For reference note the following coding standards for the project:
+
+ - [Coding Standards](http://wiki.openoffice.org/wiki/Coding_Standards)
+ - [Writer/Code
Conventions](http://wiki.openoffice.org/wiki/Writer/Code_Conventions)
+
+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.
## Submitting Patches
@@ -95,9 +115,6 @@ Bugzilla issue and then send a link to t
* The [OpenOffice.org Developer's
Guide](http://wiki.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide)
has
a lot of information, some of it up-to-date.
- * 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).
* The [commits mailing
list](http://openoffice.apache.org/mailing-lists.html#commits-mailing-list)
echos every checkin made to the code base. Developers are encouraged to
subscribe so they are aware of other changes, and can help review.
## Module Completion
