svn commit: r846751 - in /websites/staging/openoffice/trunk/content: ./ orientation/intro-development.html

[bu...@apache.org]

Author: buildbot
Date: Tue Jan 15 19:08:45 2013
New Revision: 846751

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 Tue Jan 15 19:08:45 2013
@@ -1 +1 @@
-1433415
+1433585

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 Tue Jan 15 19:08:45 2013
@@ -129,6 +129,14 @@ is a know problem with a known solution.
 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:dev@openoffice.apache.org?subject=Succesful 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>
+</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>
@@ -141,6 +149,15 @@ assign yourself existing ones.</p>
 <a href="https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamed&amp;namedcmd=easy-hacks&amp;list_id=41609">easy-hacks</a> and <a href="https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamed&amp;list_id=41611&amp;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>
+<h2 id="coding-standards">Coding Standards</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>
+<li><a href="http://wiki.openoffice.org/wiki/Writer/Code_Conventions">Writer/Code Conventions</a></li>
+</ul>
+<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>
 <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
@@ -151,9 +168,6 @@ Bugzilla issue and then send a link to t
 <ul>
 <li>The <a href="http://wiki.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide">OpenOffice.org Developer's Guide</a> has
 a lot of information, some of it up-to-date.</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>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>