openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1040010 - in /websites/staging/openoffice/trunk/content: ./ orientation/intro-development.html
Date Tue, 05 Feb 2019 16:00:46 GMT
Author: buildbot
Date: Tue Feb  5 16:00:46 2019
New Revision: 1040010

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 Feb  5 16:00:46 2019
@@ -1 +1 @@
-1853017
+1853019

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 Feb 
5 16:00:46 2019
@@ -146,12 +146,10 @@ Although there are many other combinatio
 <p>Once you have a successful build, <a href="mailto:dev@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<a class="headerlink" href="#orienting-yourself"
title="Permanent link">&para;</a></h2>
 <p>A few suggestions to help you find your way around this massive codebase:</p>
-<div class="codehilite"><pre><span class="o">-</span> <span class="n">An</span>
<span class="n">explanation</span> <span class="n">of</span> <span
class="n">the</span> <span class="n">purpose</span><span class="o">/</span><span
class="k">function</span> <span class="n">of</span> <span class="n">the</span>
<span class="n">various</span> <span class="p">[</span><span class="n">source</span>
<span class="n">directories</span><span class="p">](</span><span
class="n">https</span><span class="p">:</span><span class="o">//</span><span
class="n">wiki</span><span class="p">.</span><span class="n">openoffice</span><span
class="p">.</span><span class="n">org</span><span class="o">/</span><span
class="n">wiki</span><span class="o">/</span><span class="n">Source_code_directories</span><span
class="p">)</span>
-</pre></div>
-
-
-<p><!--    - 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. -->
-    - We have an <a href="https://fisheye.apache.org/changelog/openoffice">instance
of Atlassian Fisheye</a> which can be useful for browsing the code base and understanding
dependencies.</p>
+<ul>
+<li>An explanation of the purpose/function of the various <a href="https://wiki.openoffice.org/wiki/Source_code_directories">source
directories</a></li>
+<li>We have an <a href="https://fisheye.apache.org/changelog/openoffice">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<a class="headerlink" href="#finding-easy-tasks"
title="Permanent link">&para;</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://bz.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 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>
@@ -160,22 +158,20 @@ Although there are many other combinatio
 <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<a class="headerlink" href="#coding-standards"
title="Permanent link">&para;</a></h2>
 <p>For reference note the following coding standards for the project:</p>
-<div class="codehilite"><pre><span class="o">-</span> <span class="p">[</span><span
class="n">Coding</span> <span class="n">Standards</span><span class="p">](</span><span
class="n">https</span><span class="p">:</span><span class="o">//</span><span
class="n">wiki</span><span class="p">.</span><span class="n">openoffice</span><span
class="p">.</span><span class="n">org</span><span class="o">/</span><span
class="n">wiki</span><span class="o">/</span><span class="n">Coding_Standards</span><span
class="p">)</span>
-<span class="o">-</span> <span class="p">[</span><span class="n">Writer</span><span
class="o">/</span><span class="n">Code</span> <span class="n">Conventions</span><span
class="p">](</span><span class="n">https</span><span class="p">:</span><span
class="o">//</span><span class="n">wiki</span><span class="p">.</span><span
class="n">openoffice</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">wiki</span><span class="o">/</span><span
class="n">Writer</span><span class="o">/</span><span class="n">Code_Conventions</span><span
class="p">)</span>
-</pre></div>
-
-
+<ul>
+<li><a href="https://wiki.openoffice.org/wiki/Coding_Standards">Coding Standards</a></li>
+<li><a href="https://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<a class="headerlink" href="#submitting-patches"
title="Permanent link">&para;</a></h2>
 <p>As you read in the <a href="https://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="https://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<a class="headerlink" href="#other-useful-resources"
title="Permanent link">&para;</a></h2>
-<div class="codehilite"><pre><span class="o">*</span> <span class="n">The</span>
<span class="p">[</span><span class="n">OpenOffice</span><span
class="p">.</span><span class="n">org</span> <span class="k">for</span>
<span class="n">Developers</span><span class="p">](</span><span
class="n">https</span><span class="p">:</span><span class="o">//</span><span
class="n">www</span><span class="p">.</span><span class="n">openoffice</span><span
class="p">.</span><span class="n">org</span><span class="o">/</span><span
class="n">development</span><span class="o">/</span><span class="p">)</span>
<span class="n">web</span> <span class="n">area</span> <span class="n">has</span>
<span class="n">useful</span> <span class="n">information</span> <span
class="k">for</span> <span class="n">getting</span> <span class="n">started</span><span
class="p">.</span>
-<span class="o">*</span> <span class="n">The</span> <span class="p">[</span><span
class="n">OpenOffice</span><span class="p">.</span><span class="n">org</span>
<span class="n">Development</span> <span class="n">Wiki</span> <span
class="n">Area</span><span class="p">](</span><span class="n">https</span><span
class="p">:</span><span class="o">//</span><span class="n">wiki</span><span
class="p">.</span><span class="n">openoffice</span><span class="p">.</span><span
class="n">org</span><span class="o">/</span><span class="n">wiki</span><span
class="o">/</span><span class="n">Development</span><span class="p">)</span>
<span class="n">has</span> <span class="n">a</span> <span class="n">lot</span>
<span class="n">of</span> <span class="n">good</span> <span class="n">general</span>
<span class="n">development</span> <span class="n">information</span><span
class="p">.</span>
-<span class="o">*</span> <span class="n">The</span> <span class="p">[</span><span
class="n">commits</span> <span class="n">mailing</span> <span class="n">list</span><span
class="p">](</span><span class="n">https</span><span class="p">:</span><span
class="o">//</span><span class="n">openoffice</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">mailing</span><span class="o">-</span><span
class="n">lists</span><span class="p">.</span><span class="n">html</span>#<span
class="n">commits</span><span class="o">-</span><span class="n">mailing</span><span
class="o">-</span><span class="n">list</span><span class="p">)</span>
<span class="n">echos</span> <span class="n">every</span> <span
class="n">checkin</span> <span class="n">made</span> <span class="n">to</span>
<span class="n">the</span> <span class="n">code</span> <span class="n">base</span><span
class="p">.</span> <span class="n">Developers
 </span> <span class="n">are</span> <span class="n">encouraged</span>
<span class="n">to</span> <span class="n">subscribe</span> <span
class="n">so</span> <span class="n">they</span> <span class="n">are</span>
<span class="n">aware</span> <span class="n">of</span> <span class="n">other</span>
<span class="n">changes</span><span class="p">,</span> <span class="n">and</span>
<span class="n">can</span> <span class="n">help</span> <span class="n">review</span><span
class="p">.</span>
-</pre></div>
-
-
+<ul>
+<li>The <a href="https://www.openoffice.org/development/">OpenOffice.org for
Developers</a> web area has useful information for getting started.</li>
+<li>The <a href="https://wiki.openoffice.org/wiki/Development">OpenOffice.org
Development Wiki Area</a> has a lot of good general development information.</li>
+<li>The <a href="https://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<a class="headerlink" href="#module-completion"
title="Permanent link">&para;</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:recruitment@openoffice.apache.org?subject=Completed Introduction
to Development">recruitment@openoffice.apache.org</a> so we know.</p>
   </div>



Mime
View raw message