Author: mseidel
Date: Tue Feb 5 16:00:40 2019
New Revision: 1853019
URL: http://svn.apache.org/viewvc?rev=1853019&view=rev
Log:
Re-upload because of list formatting
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=1853019&r1=1853018&r2=1853019&view=diff
==============================================================================
--- openoffice/site/trunk/content/orientation/intro-development.mdtext
(original)
+++ openoffice/site/trunk/content/orientation/intro-development.mdtext Tue Feb
5 16:00:40 2019
@@ -54,9 +54,8 @@ Once you have a successful build, [post
A few suggestions to help you find your way around this massive codebase:
- - An explanation of the purpose/function of the various [source
directories](https://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 Atlassian
Fisheye](https://fisheye.apache.org/changelog/openoffice) which can be useful
for browsing the code base and understanding dependencies.
+ - An explanation of the purpose/function of the various [source
directories](https://wiki.openoffice.org/wiki/Source_code_directories)
+ - We have an [instance of Atlassian
Fisheye](https://fisheye.apache.org/changelog/openoffice) which can be useful
for browsing the code base and understanding dependencies.
## Finding Easy Tasks
@@ -74,8 +73,8 @@ Once you pick a bug and assign it to you
For reference note the following coding standards for the project:
- - [Coding Standards](https://wiki.openoffice.org/wiki/Coding_Standards)
- - [Writer/Code
Conventions](https://wiki.openoffice.org/wiki/Writer/Code_Conventions)
+ - [Coding Standards](https://wiki.openoffice.org/wiki/Coding_Standards)
+ - [Writer/Code
Conventions](https://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.
@@ -87,9 +86,9 @@ Please review these [guidelines for subm
##Other Useful Resources
- * The [OpenOffice.org for
Developers](https://www.openoffice.org/development/) web area has useful
information for getting started.
- * The [OpenOffice.org Development Wiki
Area](https://wiki.openoffice.org/wiki/Development) has a lot of good general
development information.
- * The [commits mailing
list](https://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.
+ * The [OpenOffice.org for
Developers](https://www.openoffice.org/development/) web area has useful
information for getting started.
+ * The [OpenOffice.org Development Wiki
Area](https://wiki.openoffice.org/wiki/Development) has a lot of good general
development information.
+ * The [commits mailing
list](https://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
