svn commit: r921549 - in /websites/staging/openoffice/trunk/content: ./ developer-faqs.html

[bu...@apache.org]

Author: buildbot
Date: Sun Sep  7 20:50:34 2014
New Revision: 921549

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/developer-faqs.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Sep  7 20:50:34 2014
@@ -1 +1 @@
-1623224
+1623226

Modified: websites/staging/openoffice/trunk/content/developer-faqs.html
==============================================================================
--- websites/staging/openoffice/trunk/content/developer-faqs.html (original)
+++ websites/staging/openoffice/trunk/content/developer-faqs.html Sun Sep  7 20:50:34 2014
@@ -100,22 +100,14 @@
     <h1 class="title">Developer FAQs</h1>
     <h2 id="developers-frequently-asked-questions">Developer's Frequently Asked Questions</h2>
 <ul>
-<li><a href="#how_do_i_edit_the_websites">How do I edit the websites?</a></li>
 <li><a href="#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></li>
 <li><a href="#im_not_a_committer">I'm not a committer, but would like to contribute, what should I do?</a></li>
 <li><a href="#how_do_i_use_apache_subversion">How do I use Apache Subversion?</a></li>
 <li><a href="#where_can_i_find_out_more_about_code_development">Where can I find out more about code development?</a></li>
 <li><a href="#where_can_i_download_developer_builds">Where can I download developer builds?</a></li>
+<li><a href="website-local.html">How do I edit the websites?</a></li>
 </ul>
-<h2 id="wzxhzdk0how-do-i-edit-the-websiteswzxhzdk1"><a name="how_do_i_edit_the_websites">How do I edit the websites?</a></h2>
-<p>The pages on this, the Apache OpenOffice "project", website are written in <a href="http://www.simpleeditions.com/59001/markdown-an-introduction">markdown syntax</a> and stored in SVN at 
-<a href="https://svn.apache.org/repos/asf/openoffice/site">https://svn.apache.org/repos/asf/openoffice/site</a>.</p>
-<p>The migrated www.openoffice.org is stored in SVN at <a href="https://svn.apache.org/repos/asf/openoffice/ooo-site">https://svn.apache.org/repos/asf/openoffice/ooo-site</a> and is primarily "html".</p>
-<p>Via integration with the <a href="http://www.apache.org/dev/cms.html">Apache CMS</a>, it is possible to edit, stage and publish 
-website updates from the command line, or by using a web-based interface, the <a href="https://cms.apache.org/#bookmark">CMS bookmarklet</a>.</p>
-<p>Detailed information can be found in the <a href="http://openoffice.apache.org/docs/edit-cms.html">How to edit the Apache OpenOffice website</a> page.</p>
-<p>Information on deeper website development is found on the <a href="website-local.html">Website Development</a> page.</p>
-<h2 id="wzxhzdk2ive-just-been-voted-in-as-a-committer-what-do-i-need-to-dowzxhzdk3"><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></h2>
+<h2 id="wzxhzdk0ive-just-been-voted-in-as-a-committer-what-do-i-need-to-dowzxhzdk1"><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></h2>
 <p>First, congratulations.  Your contributions to the project have been noted and we 
 hope that as a Committer you will be even more active.</p>
 <p>But before you are officially given Committer permissions, there are a few 
@@ -140,7 +132,7 @@ PMC's private mailing list.</p>
 <p>Finally, you should read the <a href="http://www.apache.org/dev/new-committers-guide.html">"Guide for new committers"</a></p>
 </li>
 </ol>
-<h2 id="wzxhzdk4im-not-a-committer-but-would-like-to-contribute-what-should-i-do-wzxhzdk5"><a name="im_not_a_committer"/>I'm not a committer, but would like to contribute, what should I do? </a></h2>
+<h2 id="wzxhzdk2im-not-a-committer-but-would-like-to-contribute-what-should-i-do-wzxhzdk3"><a name="im_not_a_committer"/>I'm not a committer, but would like to contribute, what should I do? </a></h2>
 <p>Apache OpenOffice welcomes your contributions!</p>
 <p>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
@@ -153,14 +145,14 @@ issue number so we can follow-up.</p>
 <p>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 <a href="http://www.openoffice.org/welcome/credits.html">OpenOffice credits page</a>
 to recognize your contribution.</p>
-<h2 id="wzxhzdk6how-do-i-use-apache-subversionwzxhzdk7"><a name="how_do_i_use_apache_subversion">How do I use Apache Subversion?</a></h2>
+<h2 id="wzxhzdk4how-do-i-use-apache-subversionwzxhzdk5"><a name="how_do_i_use_apache_subversion">How do I use Apache Subversion?</a></h2>
 <p>Instructions can be found on the <a href="http://openoffice.apache.org/svn-basics.html">Subversion Basics</a> page.</p>
 <p>Please note that we are using a Subversion/Bugzilla integration,
 e.g. when you are committing something and mention the bugzilla issue in
 the commit summary, then this bugzilla issue gets automatically updated
 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.</p>
-<h2 id="wzxhzdk8where-can-i-find-out-more-about-code-developmentwzxhzdk9"><a name="where_can_i_find_out_more_about_code_development">Where can I find out more about code development?</a></h2>
+<h2 id="wzxhzdk6where-can-i-find-out-more-about-code-developmentwzxhzdk7"><a name="where_can_i_find_out_more_about_code_development">Where can I find out more about code development?</a></h2>
 <p>You might want to start by reviewing the legacy information on <a href="http://www.openoffice.org/development/">OpenOffice.org
 development</a>. Or, take
 a look at information posted on the <a href="http://wiki.openoffice.org/wiki/Main_Page">Apache OpenOffice wiki</a>.</p>
@@ -168,7 +160,7 @@ a look at information posted on the <a h
 <p>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.</p>
-<h2 id="wzxhzdk10where-can-i-download-developer-buildswzxhzdk11"><a name="where_can_i_download_developer_builds">Where can I download developer builds?</a></h2>
+<h2 id="wzxhzdk8where-can-i-download-developer-buildswzxhzdk9"><a name="where_can_i_download_developer_builds">Where can I download developer builds?</a></h2>
 <p>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.  </p>
 <p>Apache OpenOffice makes use of buildbots for some of our environments. You can review the Apache OpenOffice buildbot information <a href="http://ci.apache.org/projects/openoffice/">here</a>. Additional information on buildbot builds for linux64, window7, and linux32 can be found <a href="http://ci.apache.org/builders/">here</a>.</p>