This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch preview/refresh-staging
in repository https://gitbox.apache.org/repos/asf/openoffice-project.git
The following commit(s) were added to refs/heads/preview/refresh-staging by
this push:
new ce14a77 Automatic Site Publish by Buildbot
ce14a77 is described below
commit ce14a77a48257a412d4f78cc5ff7510796c0d369
Author: buildbot <[email protected]>
AuthorDate: Mon Jun 28 21:31:05 2021 +0000
Automatic Site Publish by Buildbot
---
output/license.html | 2 +-
output/mailing-lists.html | 2 +-
output/orientation/intro-development.html | 4 ++--
output/pmc-faqs.html | 4 ++--
output/svn-basics.html | 22 +++++++++++-----------
5 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/output/license.html b/output/license.html
index 79851a7..bf2edc9 100644
--- a/output/license.html
+++ b/output/license.html
@@ -247,7 +247,7 @@ harmless for any liability incurred by, or claims asserted
against, such
Contributor by reason of your accepting any such warranty or additional
liability.</p>
<p>END OF TERMS AND CONDITIONS</p>
-<h1 id="apply">APPENDIX: How to apply the Apache License to your work #<a
class="headerlink" href="#apply" title="Permalink">¶</a></h1>
+<h1 id="apply">APPENDIX: How to apply the Apache License to your work<a
class="headerlink" href="#apply" title="Permalink">¶</a></h1>
<p>To apply the Apache License to your work, attach the following boilerplate
notice, with the fields enclosed by brackets "[]" replaced with your own
identifying information. (Don't include the brackets!) The text should be
diff --git a/output/mailing-lists.html b/output/mailing-lists.html
index 90446ca..937c996 100644
--- a/output/mailing-lists.html
+++ b/output/mailing-lists.html
@@ -295,7 +295,7 @@ people and tries to help to find the right part. This is a
low traffic list.</p>
<li>Apache Archives: <a
href="http://mail-archives.apache.org/mod_mbox/openoffice-volunteer/";>current</a></li>
<li>Third-party Archives: <a
href="http://www.mail-archive.com/[email protected]/";>Mail
Archive</a></li>
</ul>
-<p>##<a id="native-lang-lists"></a> Native Language (non-English) Mailing
Lists</p>
+<h2 id="native-lang-lists">Native Language (non-English) Mailing Lists<a
class="headerlink" href="#native-lang-lists" title="Permalink">¶</a></h2>
<p>The project has several mailing lists for discussion about OpenOffice in
native
(non-English) languages.</p>
<p>Information about available Native Language mailing lists can be found in
the page
diff --git a/output/orientation/intro-development.html
b/output/orientation/intro-development.html
index 7da67e4..b382b33 100644
--- a/output/orientation/intro-development.html
+++ b/output/orientation/intro-development.html
@@ -93,14 +93,14 @@
<h1>Introduction to Development</h1>
- <p>##Introduction</p>
+ <h2 id="introduction">Introduction<a class="headerlink"
href="#introduction" title="Permalink">¶</a></h2>
<p>In this orientation module you will learn how to get started programming
OpenOffice.</p>
<p>To complete this module, read through the material on this page, including
the linked references. There will also be some start-up tasks for you to
perform, such as signing up for an account in our defect tracking database.</p>
<p>Your first task is to subscribe to our Recruitment mailing list. You can
subscribe by sending an email to <a
href="mailto:[email protected]";>[email protected]</a>.</p>
<p>Then you can introduce yourself by [sending an email to the list](mailto:<a
href="mailto:[email protected]";>[email protected]</a>?subject=New
Dev Volunteer). We'd love to hear who you are, where you are from, what your
background is, etc. Also as you work through the items on this page, if you
have questions or problems, please feel free to ask for help by sending a note
to this same list.</p>
<p>Note: In parallel with the Dev-specific items on this page, you may want to
also review the <a
href="http://openoffice.apache.org/orientation/index.html";>Level 1 and Level 2
Orientation Modules</a>. They have useful background information on The Apache
Way, mailing list etiquette, decision making in the project, etc. A quick
review is a good idea, especially if you are new to working in Apache-style
open source projects.</p>
<p>Now with the introductions out of the way, let's get started!</p>
-<p>##OpenOffice Development: Good, the Bad and the Ugly</p>
+<h2 id="openoffice-development-good-the-bad-and-the-ugly">OpenOffice
Development: Good, the Bad and the Ugly<a class="headerlink"
href="#openoffice-development-good-the-bad-and-the-ugly"
title="Permalink">¶</a></h2>
<p>Let's be honest. The size, age and complexity of OpenOffice's C++ codebase
makes coding a challenge. This is not a trivial codebase to learn. But if you
like a good challenge then you'll love this project! There are tasks suitable
for programmers with a range of programming experience, and we have many
veteran OpenOffice hackers in the project who are happy to answer your
questions.</p>
<p>And in its favor, there are few other programs that you can help develop,
that have the reach of OpenOffice. Many millions of users depend on OpenOffice,
with another half a million downloads every week, from almost every country in
the world. So the work you do, the bugs you fix, the features you add, will
benefit millions of users around the world.</p>
<h2 id="building-openoffice">Building OpenOffice<a class="headerlink"
href="#building-openoffice" title="Permalink">¶</a></h2>
diff --git a/output/pmc-faqs.html b/output/pmc-faqs.html
index 267e7b7..d2e4646 100644
--- a/output/pmc-faqs.html
+++ b/output/pmc-faqs.html
@@ -95,12 +95,12 @@
<p>Here are a number of FAQ's about how the Apache OpenOffice project
governance works.</p>
<p><strong>Contents</strong></p>
-<div id="toc"><ul><li><a class="toc-href" href="#pmc" title="What is the
PMC?">What is the PMC?</a></li><li><a class="toc-href" href="#moderator"
title="Who is the Admin/Moderator/Owner for X? #">Who is the
Admin/Moderator/Owner for X? #</a></li><li><a class="toc-href"
href="#resources-inside-asf" title="Resources inside ASF">Resources inside
ASF</a><ul><li><a class="toc-href" href="#mailing-lists" title="Mailing
lists">Mailing lists</a></li><li><a class="toc-href" href="#svn-git" title=
[...]
+<div id="toc"><ul><li><a class="toc-href" href="#pmc" title="What is the
PMC?">What is the PMC?</a></li><li><a class="toc-href" href="#moderator"
title="Who is the Admin/Moderator/Owner for X?">Who is the
Admin/Moderator/Owner for X?</a></li><li><a class="toc-href"
href="#resources-inside-asf" title="Resources inside ASF">Resources inside
ASF</a><ul><li><a class="toc-href" href="#mailing-lists" title="Mailing
lists">Mailing lists</a></li><li><a class="toc-href" href="#svn-git" title="SVN
[...]
<h1 id="pmc">What is the PMC?<a class="headerlink" href="#pmc"
title="Permalink">¶</a></h1>
<p>The Project Management Committee (PMC) is the government of the project.
The committee
is responsible for the project and decides what to do and which direction to
go.
<br/> (<a
href="https://people.apache.org/committers-by-project.html#openoffice-pmc";>see
here for a list of PMC members</a>)</p>
-<h1 id="moderator">Who is the Admin/Moderator/Owner for X? #<a
class="headerlink" href="#moderator" title="Permalink">¶</a></h1>
+<h1 id="moderator">Who is the Admin/Moderator/Owner for X?<a
class="headerlink" href="#moderator" title="Permalink">¶</a></h1>
<p>Although Apache projects have few formal roles, there are some technical
subsystems
which have admin or similar roles filled by project volunteers. If you have a
question
with one of these systems, these are the people you might want to contact
first,
diff --git a/output/svn-basics.html b/output/svn-basics.html
index 28a6d60..27c6094 100644
--- a/output/svn-basics.html
+++ b/output/svn-basics.html
@@ -109,10 +109,10 @@
<li><a href="#merging_changes">Merging changes to a branch</a></li>
<li><a href="#further_information">Further Information</a></li>
</ul>
-<h2 id="overview_1"><a id="overview"></a>Overview<a class="headerlink"
href="#overview_1" title="Permalink">¶</a></h2>
+<h2 id="overview">Overview<a class="headerlink" href="#overview"
title="Permalink">¶</a></h2>
<p>You begin using Subversion by copying a directory from a remote repository
to a local directory on your file system. This is known as a checkout of a
working copy.</p>
<p>Subversion uses a copy-modify-merge model meaning that you can add and edit
files and directories in your working copy like any other files on your system,
but you should use subversion commands for everything else such as <code>svn
copy</code> and <code>svn move</code> instead of the operating system
commands.</p>
-<h2 id="sub-commands-and-abbreviations"><a
id="sub-commands_and_abbreviations"></a>Sub-commands and Abbreviations<a
class="headerlink" href="#sub-commands-and-abbreviations"
title="Permalink">¶</a></h2>
+<h2 id="sub-commands_and_abbreviations">Sub-commands and Abbreviations<a
class="headerlink" href="#sub-commands_and_abbreviations"
title="Permalink">¶</a></h2>
<p>Subversion commands can be run from a command shell such as Bash on Linux.
The subversion client command is <code>svn</code> followed by optional
sub-commands, options, and arguments.</p>
<p>Show the program version and modules</p>
<pre><code>$ svn --version
@@ -136,12 +136,12 @@
<li><code>status</code> - Print the status of working copy files and
directories</li>
<li><code>update</code> - Bring changes from the repository into your working
copy</li>
</ul>
-<h2 id="client-configuration"><a id="client_configuration"></a>Client
Configuration<a class="headerlink" href="#client-configuration"
title="Permalink">¶</a></h2>
+<h2 id="client_configuration">Client Configuration<a class="headerlink"
href="#client_configuration" title="Permalink">¶</a></h2>
<p>Committers need to <a
href="http://www.apache.org/dev/version-control.html#https-svn-config";>configure
their Subversion client</a> to handle the differences in line endings of text
files on different operating systems.</p>
<p>There are instances where Subversion may need to open an editor. You need
to have the environment variable EDITOR set to the editor you would like to
use. To set it for the current terminal session in Bash (your path may
differ):</p>
<pre><code>$ export EDITOR=/usr/bin/vim
</code></pre>
-<h2 id="repository-layout"><a id="repository_layout"></a>Repository Layout<a
class="headerlink" href="#repository-layout" title="Permalink">¶</a></h2>
+<h2 id="repository_layout">Repository Layout<a class="headerlink"
href="#repository_layout" title="Permalink">¶</a></h2>
<p>The AOO repository layout uses the following top-level directories
<code>branches</code>, <code>site</code>, <code>tags</code>, and
<code>trunk</code>.</p>
<ul>
<li><code>branches</code> - Contains branches used for continued development
of a specific version, experimental versions, or for developing features to be
merged into the trunk or a branch later. (needs examples)</li>
@@ -163,7 +163,7 @@ A aoo-trunk/tools/dev/single-hg.sh
Checked out revision 1145818.
</code></pre>
<p>"A" indicates file or directory is "Added" to working copy</p>
-<h2 id="basic-work-cycle"><a id="basic_work_cycle"></a>Basic Work Cycle<a
class="headerlink" href="#basic-work-cycle" title="Permalink">¶</a></h2>
+<h2 id="basic_work_cycle">Basic Work Cycle<a class="headerlink"
href="#basic_work_cycle" title="Permalink">¶</a></h2>
<ul>
<li>Update your working copy - For this you use the <code>svn update</code>
command</li>
<li>Make changes - For this you may edit files in an editor, or use the
<code>svn add</code>, <code>svn delete</code>, <code>svn copy</code>,
<code>svn-move</code> commands</li>
@@ -259,7 +259,7 @@ Select: (p) postpone, (df) diff-full, (e) edit, (r)
resolved,
Updated to revision 4.
</code></pre>
<p>"G" indicates "merGed"</p>
-<h2 id="committing-changes"><a id="committing_changes"></a>Committing
Changes<a class="headerlink" href="#committing-changes"
title="Permalink">¶</a></h2>
+<h2 id="committing_changes">Committing Changes<a class="headerlink"
href="#committing_changes" title="Permalink">¶</a></h2>
<p>Only Committers can commit directly to the repository. The following
example shows using your Apache ID and password.</p>
<pre><code>$ svn commit test-file.c --username your-name --password
your-password \
-m "added new C file"
@@ -271,7 +271,7 @@ Committed revision 5.
<p>Always check your changes with "svn diff" and "svn status". Also be careful
to specify the files and/or directories you want to change, if
you don't specify, SVN will commit <strong>all</strong> your changes.</p>
<p>For further information see the <a
href="http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html";>Basic Work
Cycle</a> page from <a href="http://svnbook.red-bean.com";>Subversion
Book</a>.</p>
-<h2 id="commit-message"><a id="commit_message"></a>Commit Message<a
class="headerlink" href="#commit-message" title="Permalink">¶</a></h2>
+<h2 id="commit_message">Commit Message<a class="headerlink"
href="#commit_message" title="Permalink">¶</a></h2>
<p>The examples in the previous sections use a simple commit message with the
"-m" option.</p>
<p>This is fine for some quick testing or for large bulk commits of code that
you wrote.</p>
<p>We ask that your commits include special tagging to appropriately credit
the patch.
@@ -290,7 +290,7 @@ Committed revision 5.
<p>Use of the special fields will enable processing by scripts like the
<a href="http://www.red-bean.com/svnproject/contribulyzer/";>contribulyzer</a>
to help quickly identify
contributors.</p>
-<h2 id="committing-changes-by-others"><a
id="committing_changes_by_others"></a>Committing Changes By Others<a
class="headerlink" href="#committing-changes-by-others"
title="Permalink">¶</a></h2>
+<h2 id="committing_changes_by_others">Committing Changes By Others<a
class="headerlink" href="#committing_changes_by_others"
title="Permalink">¶</a></h2>
<p>See the <a
href="http://www.apache.org/dev/committers.html#applying-patches";>Applying
Patches</a> section of the Committer FAQ page. Please use the special fields
described in the previous Commit Message section to commit changes supplied by
others.</p>
<p>Example similar to one on Committer FAQ:</p>
@@ -304,12 +304,12 @@ Suggested by: Jane Brown <janeb.at.notnull.org>
John Doe <john.doe.at.null.org>\nSubmitted by: John Doe /
<john.doe.at.null.org>' test-file.txt
</code></pre>
-<h2 id="creating-and-submitting-patches"><a
id="creating_and_submitting_patches"></a>Creating and Submitting Patches<a
class="headerlink" href="#creating-and-submitting-patches"
title="Permalink">¶</a></h2>
+<h2 id="creating_and_submitting_patches">Creating and Submitting Patches<a
class="headerlink" href="#creating_and_submitting_patches"
title="Permalink">¶</a></h2>
<p>See the <a
href="http://www.apache.org/dev/contributors.html#patches";>Sending in
Patches</a> section on the Contributors Tech Guide page.</p>
<p>Create the patch file from <code>svn diff</code> where
<code>your-patch-name.patch</code> is the full path to the patch file to
create.</p>
<pre><code>svn diff > your-patch-name.patch
</code></pre>
-<h2 id="merging-changes-to-a-branch"><a id="merging_changes"></a>Merging
changes to a branch<a class="headerlink" href="#merging-changes-to-a-branch"
title="Permalink">¶</a></h2>
+<h2 id="merging_changes">Merging changes to a branch<a class="headerlink"
href="#merging_changes" title="Permalink">¶</a></h2>
<p>New development is done in the "trunk", development area, of the tree.
Stable, release branches, are specifically named and can be found
in the <a
href="http://svn.apache.org/viewvc/openoffice/branches/";>branches</a> area of
the openoffice svn tree. With few exceptions you do <strong>NOT</strong> do
direct commits to the stable, release,
branches. Changes, commits, to stable branch are typically only done during a
formal release cycle and must be discussed on the "dev" list.</p>
@@ -356,7 +356,7 @@ and commit from the aoo-update directory:</p>
Transmitting file data ..
Committed revision 1347377.
</code></pre>
-<h2 id="further-information"><a id="further_information"></a>Further
Information<a class="headerlink" href="#further-information"
title="Permalink">¶</a></h2>
+<h2 id="further_information">Further Information<a class="headerlink"
href="#further_information" title="Permalink">¶</a></h2>
<p>For more information see:</p>
<ul>
<li><a href="http://subversion.apache.org";>Apache Subversion Project</a></li>
