svn commit: r1624917 - /openoffice/site/trunk/content/developer-faqs.mdtext

[ks...@apache.org]

Author: kschenk
Date: Sun Sep 14 22:18:50 2014
New Revision: 1624917

URL: http://svn.apache.org/r1624917
Log:
More changes and reorganization.

Modified:
    openoffice/site/trunk/content/developer-faqs.mdtext

Modified: openoffice/site/trunk/content/developer-faqs.mdtext
URL: http://svn.apache.org/viewvc/openoffice/site/trunk/content/developer-faqs.mdtext?rev=1624917&r1=1624916&r2=1624917&view=diff
==============================================================================
--- openoffice/site/trunk/content/developer-faqs.mdtext (original)
+++ openoffice/site/trunk/content/developer-faqs.mdtext Sun Sep 14 22:18:50 2014
@@ -15,19 +15,27 @@ Notice:    Licensed to the Apache Softwa
            KIND, either express or implied.  See the License for the
            specific language governing permissions and limitations
            under the License.
+           
+Welcome to OpenOffice development! 
 
-##Developer's Frequently Asked Questions
+[TOC]
 
-  - [I've just been voted in as a committer what do I need to do?](#ive_just_been_voted_in_as_a_committer__what_do_i_need_to_do)
-  - [I'm not a committer, but would like to contribute, what should I do?](#im_not_a_committer)
-  - [How do I use Apache Subversion?](#how_do_i_use_apache_subversion)
-  - [Where can I find out more about code development?](#where_can_i_find_out_more_about_code_development)
-  - [Where can I download developer builds?](#where_can_i_download_developer_builds)
-  - [How do I edit the websites?][10]
+## Where can I find out more about code development?</a>
 
+You might want to start by reviewing the legacy information on [OpenOffice.org
+development](http://www.openoffice.org/development/). Or, take
+a look at information posted on the [Apache OpenOffice wiki](http://wiki.openoffice.org/wiki/Main_Page)
+under *Documentation - For Developers*.
 
+Of course, you will need the [source code](http://openoffice.apache.org/source.html) to do anything. We recommend building in your own environment as a first step.
 
-##<a name="ive_just_been_voted_in_as_a_committer__what_do_i_need_to_do">I've just been voted in as a Committer.  What do I need to do?</a>
+You don't have to be an actual committer to submit code. You can submit patches through
+the Apache OpenOffice Bugzilla issue reporting system. You simply need to file an issue
+and supply your patch as an attachment to the issue.
+
+Please also see our [Orientation Modules](http://openoffice.apache.org/orientation/index.html) for information on how the project works and identifying outstanding development tasks.
+
+## I've just been voted in as a Committer.  What do I need to do?
 
 First, congratulations.  Your contributions to the project have been noted and we 
 hope that as a Committer you will be even more active.
@@ -52,24 +60,19 @@ PMC's private mailing list.
  1. Finally, you should read the ["Guide for new committers"] [9]
 
 
-##<a name="im_not_a_committer"/>I'm not a committer, but would like to contribute, what should I do? </a>
+## I'm not a committer, but would like to contribute, what should I do? 
 
 Apache OpenOffice welcomes your contributions!
 
-If you want to contribute to either of the websites, you can do this by
-using subversion and submitting patches via e-mail, or for quick changes, you can use
-the [CMS bookmarklet](https://cms.apache.org/#bookmark) and use to edit a page,
-and submit a patch as described in the [Apache CMS Reference Manual](http://www.apache.org/dev/cmsref.html#non-committer).
-Save your PATCH. File an issue using [OpenOffice Bugzilla](https://issues.apache.org/ooo/) and select the "www"
-category to file it. You should then use your saved patch as an attachment to the
-issue. Please send a follow-up e-mail to [dev](mailto:dev@openoffice.apache.org) and provide the 
-issue number so we can follow-up.
+To contribute to the OpenOffice product, you will need to submit subversion patches ("diff" files), and attach them to issues in our [issues reporting system](http://issues.openoffice.org), Bugzilla.
 
 Your contributions will be recognized by the committer submitting the PATCH in the
 log entry for the committed patch, and you will be added to the [OpenOffice credits page](http://www.openoffice.org/welcome/credits.html)
 to recognize your contribution.
 
-##<a name="how_do_i_use_apache_subversion">How do I use Apache Subversion?</a>
+The following sections will explain more about this.
+
+## How do I use Apache Subversion?
 
 Instructions can be found on the [Subversion Basics] [11] page.
 
@@ -79,21 +82,9 @@ the commit summary, then this bugzilla i
 with some short info about the change. The recommended notation to mention
 e.g. issue 1234 is to use a #i1234# at the start of the commit message summary.
 
-##<a name="where_can_i_find_out_more_about_code_development">Where can I find out more about code development?</a>
 
-You might want to start by reviewing the legacy information on [OpenOffice.org
-development](http://www.openoffice.org/development/). Or, take
-a look at information posted on the [Apache OpenOffice wiki](http://wiki.openoffice.org/wiki/Main_Page)
-under *Documentation - For Developers*.
-
-Of course, you will need the [source code](http://openoffice.apache.org/source.html) to do anything.
-
-You don't have to be an actual committer to submit code. You can submit patches through
-the Apache OpenOffice Bugzilla issue reporting system. You simply need to file an issue
-and supply your patch as an attachment to the issue.
 
-
-##<a name="where_can_i_download_developer_builds">Where can I download developer builds?</a>
+## Where can I download developer builds?
 
 Developer builds are not official releases and may be unstable.  But they can be useful to download for those who 
 need early access to builds, but who do not want to compile their own build. They are announced and discussed only on the development list, as they are not production builds.  Apache OpenOffice currently has two types of development builds: those generated by buildbots, and those manually generated/built.  
@@ -108,6 +99,8 @@ Development snapshots, which are manuall
 Also, please see the [Planning Area of the Project Wiki](https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Planning) for
 additional information on current and future releases.
 
+## [How Do I Edit the Websites?][10]
+
 
 
   [1]: http://www.simpleeditions.com/59001/markdown-an-introduction