Author: kschenk
Date: Sun Sep 14 22:19:39 2014
New Revision: 1624918
URL: http://svn.apache.org/r1624918
Log:
More chagnes to make explanations more clear.
Modified:
openoffice/site/trunk/content/website-local.mdtext
Modified: openoffice/site/trunk/content/website-local.mdtext
URL:
http://svn.apache.org/viewvc/openoffice/site/trunk/content/website-local.mdtext?rev=1624918&r1=1624917&r2=1624918&view=diff
==============================================================================
--- openoffice/site/trunk/content/website-local.mdtext (original)
+++ openoffice/site/trunk/content/website-local.mdtext Sun Sep 14 22:19:39 2014
@@ -51,14 +51,25 @@ repository][2] or [browse the user porta
### Using SVN Directly (for technical users)
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 [SVN Book](http://svnbook.red-bean.com/) ). Patches
can be submitted as attachments to e-mail to the
+doing an svn checkout, making changes to files and --
+
+* 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 [SVN Book](http://svnbook.red-bean.com/) ).
+
+Patches, svn "diff" files can be submitted in a variety of ways:
+
+* 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:[email protected]) and provide the
+issue number so we can follow-up.
+
+* Patches can be submitted as attachments to e-mail to the
[Apache OpenOffice developer](mailto:[email protected]) list.
-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.
+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.
### Using the Apache CMS Bookmarklet (simpler method)
