svn commit: r922206 - in /websites/staging/openoffice/trunk/content: ./ website-local.html

[bu...@apache.org]

Author: buildbot
Date: Sun Sep 14 22:19:43 2014
New Revision: 922206

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/website-local.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Sep 14 22:19:43 2014
@@ -1 +1 @@
-1624917
+1624918

Modified: websites/staging/openoffice/trunk/content/website-local.html
==============================================================================
--- websites/staging/openoffice/trunk/content/website-local.html (original)
+++ websites/staging/openoffice/trunk/content/website-local.html Sun Sep 14 22:19:43 2014
@@ -174,13 +174,27 @@ repository</a> or <a href="https://svn.a
 <h2 id="how-to-make-or-request-changes-to-the-websites">How To Make or Request Changes to the Websites</h2>
 <h3 id="using-svn-directly-for-technical-users">Using SVN Directly (for technical users)</h3>
 <p>You can make changes to either site using svn (subversion). This typically involves 
-doing an svn checkout, making changes to files and then either committing your changes
-if you are an "Apache committer", or submitting a "patch" (an svn "diff" file) if you are a contributor but
-not a "committer". Consult your local svn implementation for how to do commits or create
-patches. (See also, the <a href="http://svnbook.red-bean.com/">SVN Book</a> ). Patches can be submitted as attachments to e-mail to the 
+doing an svn checkout, making changes to files and --</p>
+<ul>
+<li>committing your changes
+if you are an "Apache committer", or </li>
+<li>submitting a "patch" (an svn "diff" file) if you are a contributor but not a "committer". </li>
+</ul>
+<p>Consult your local svn implementation for how to do commits or create patches. (See also, the <a href="http://svnbook.red-bean.com/">SVN Book</a> ). </p>
+<p>Patches, svn "diff" files can be submitted in a variety of ways:</p>
+<ul>
+<li>
+<p>File an issue using <a href="https://issues.apache.org/ooo/">OpenOffice Bugzilla</a> 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 <a href="mailto:dev@openoffice.apache.org">dev</a> and provide the 
+issue number so we can follow-up.</p>
+</li>
+<li>
+<p>Patches can be submitted as attachments to e-mail to the 
 <a href="mailto:dev@openoffice.apache.org">Apache OpenOffice developer</a> list.</p>
-<p>SVN commits will commit your changes to the "staging area". you will need to 
-"publish" your changes to make them active on the "production" site.</p>
+</li>
+</ul>
+<p>Changes committed with SVN commit your changes to the "staging area".  These changes will need to be published to become active on the "production" site.</p>
 <h3 id="using-the-apache-cms-bookmarklet-simpler-method">Using the Apache CMS Bookmarklet (simpler method)</h3>
 <p>Quick editing of the site is available for committers and contributors using the Apache CMS
 <a href="https://cms.apache.org/#bookmark">from your browser.</a> If you are a committer and use the bookmarklet in your web browser, you should use