Author: buildbot
Date: Sun Feb  9 19:47:31 2020
New Revision: 1056330

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/source.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Feb  9 19:47:31 2020
@@ -1 +1 @@
-1872565
+1873838

Modified: websites/staging/openoffice/trunk/content/source.html
==============================================================================
--- websites/staging/openoffice/trunk/content/source.html (original)
+++ websites/staging/openoffice/trunk/content/source.html Sun Feb  9 19:47:31 
2020
@@ -127,38 +127,43 @@ h2:hover > .headerlink, h3:hover > .head
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, 
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, 
dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>We use <a href="https://subversion.apache.org/";>Apache Subversion</a> for 
version control. You can <a 
href="https://svn.apache.org/viewvc/openoffice/trunk/";>browse our
-repository</a> in your web browser.</p>
-<p>See our <a href="http://openoffice.apache.org/svn-basics.html";>Subversion 
Basics</a>
-for more information on using subversion (svn) for the Apache OpenOffice 
project.</p>
-<p>For further information see the <a 
href="https://www.apache.org/dev/version-control.html";>Apache Source Code 
Repository</a> page.</p>
+<p>As of August, 2019, we use GIT for version control. You can <a 
href="https://gitbox.apache.org/repos/asf?p=openoffice.git";>browse our
+repository</a> using the "tree" view from gitbox in your web browser. The <a 
href="https://github.com/apache/openoffice";>README.md</a> at github.com 
provides useful information on how to download and build Apache OpenOffice. </p>
+<p>The previous svn repository, now read only, using <a 
href="https://subversion.apache.org/";>Apache Subversion</a> for version control 
is <a href="https://svn.apache.org/viewvc/openoffice/trunk/";>still viewable</a> 
in your web browser.</p>
+<p>Currently, subversion is still used for the two OpenOffice web sites.
+See our <a href="http://openoffice.apache.org/svn-basics.html";>Subversion 
Basics</a>
+for more information on using subversion (svn) for the Apache OpenOffice 
project. </p>
+<!--- For further information see the [Apache Source Code Repository][3] 
page.-->
+
 <h2 id="getting-the-source-code">Getting the source code<a class="headerlink" 
href="#getting-the-source-code" title="Permanent link">&para;</a></h2>
-<h3 id="using-svn">Using SVN<a class="headerlink" href="#using-svn" 
title="Permanent link">&para;</a></h3>
+<h3 id="using-git">Using GIT<a class="headerlink" href="#using-git" 
title="Permanent link">&para;</a></h3>
+<!--- You can use our git repository for downloading source but not committing 
(read only):
+    
[https://github.com/apache/openoffice](https://github.com/apache/openoffice)-->
+
+<p>Instructions provided in <a 
href="https://github.com/apache/openoffice";>README.md</a> from github.com can 
be used successfully to get a local copy of the complete source for Apache 
OpenOffice.</p>
+<h3 id="using-svn-applies-to-code-through-july-2019">Using SVN (applies to 
code through July, 2019)<a class="headerlink" 
href="#using-svn-applies-to-code-through-july-2019" title="Permanent 
link">&para;</a></h3>
 <p>This will get you everything, including the language files:</p>
 <div class="codehilite"><pre><span class="n">svn</span> <span 
class="n">co</span> <span class="n">https</span><span class="p">:</span><span 
class="o">//</span><span class="n">svn</span><span class="p">.</span><span 
class="n">apache</span><span class="p">.</span><span class="n">org</span><span 
class="o">/</span><span class="n">repos</span><span class="o">/</span><span 
class="n">asf</span><span class="o">/</span><span 
class="n">openoffice</span><span class="o">/</span><span class="n">trunk</span> 
<span class="n">aoo</span>
 </pre></div>
 
 
 <p>Including SVN overhead, this requires approximately 4 GB of storage.</p>
-<h3 id="using-git">Using GIT<a class="headerlink" href="#using-git" 
title="Permanent link">&para;</a></h3>
-<p>You can use our git repository for downloading source but not committing 
(read only):
-    <a 
href="https://github.com/apache/openoffice";>https://github.com/apache/openoffice</a></p>
 <h3 id="source-archive-of-the-latest-release">Source archive of the latest 
release<a class="headerlink" href="#source-archive-of-the-latest-release" 
title="Permanent link">&para;</a></h3>
 <p>An archive of the source for the latest release can be obtainted from the 
Apache Software Foundation repository:
-    <a 
href="http://www.apache.org/dyn/aoo-closer.cgi/openoffice/";>http://www.apache.org/dyn/aoo-closer.cgi/openoffice/</a></p>
+    <a 
href="http://archive.apache.org/dist/openoffice/";>http://archive.apache.org/dist/openoffice</a></p>
 <h2 id="browsingsearching-source-code">Browsing/Searching Source Code<a 
class="headerlink" href="#browsingsearching-source-code" title="Permanent 
link">&para;</a></h2>
-<p>We have an instance of <a 
href="https://fisheye.apache.org/changelog/openoffice";>Atlassian FishEye</a> 
for source browsing, searching,
-reporting and visualization of main trunk (main development area).</p>
-<p>Also, we hosts an <a href="http://opengrok.openoffice.org";>OpenGrok</a> 
instance for our
+<!--- We have an instance of [Atlassian FishEye][4] for source browsing, 
searching,
+reporting and visualization of main trunk (main development area).-->
+
+<p>We host an <a href="http://openoffice-vm1-he-de.apache.org/";>OpenGrok</a> 
instance for our
 main repository areas.</p>
 <h2 id="building-and-running">Building and Running<a class="headerlink" 
href="#building-and-running" title="Permanent link">&para;</a></h2>
 <p>See the <a 
href="https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO";>Apache 
OpenOffice Building Guide page</a>
     for an overview on building.</p>
-<p>See <a 
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-buildflags";>Development
 Snapshots builds</a> for additional information on building.</p>
+<p>The <a 
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-buildflags";>Development
 Snapshots builds</a> page, pre-release builds, also provide additional 
information on building.</p>
 <h2 id="testing-developer-installation-sets">Testing Developer Installation 
Sets<a class="headerlink" href="#testing-developer-installation-sets" 
title="Permanent link">&para;</a></h2>
-<p>See <a 
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-fullsets";>Development
 Snapshot Builds: Full installation sets</a> or <a 
href="https://www.openoffice.org/download/devbuilds.html";>Development Builds</a>
-for complete installation sets for available platforms.</p>
-<p>Install the "Developer Installation Set" to a new directory if you don't 
want to overwrite your
+<p>See <a 
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-fullsets";>Development
 Snapshot Builds: Full installation sets</a>, pre-release builds, or <a 
href="https://www.openoffice.org/download/devbuilds.html";>Development 
Builds</a>, nightly builds from the buildbots, for complete installation sets 
for available platforms.</p>
+<p>Install developer builds to a new directory if you don't want to overwrite 
your
 existing Apache OpenOffice installation.</p>
 <ul>
 <li>Linux: Create a new directory for the AOO developer install.
@@ -169,13 +174,15 @@ AOO developer install.</li>
 to the new directory.</li>
 </ul>
 <h2 id="code-and-contribution-statistics">Code and Contribution Statistics<a 
class="headerlink" href="#code-and-contribution-statistics" title="Permanent 
link">&para;</a></h2>
-<p>Our SVN tree is read by the <a 
href="https://www.openhub.net/p/openoffice";>Open Hub tracker</a> to generate 
some various statistics.
+<!--- Our SVN tree is read by the [Open Hub tracker][6] to generate some 
various statistics.
 Note that the migration from the legacy Mercurial repository to SVN at Apache 
has
 caused pre-existing files to be double-counted. But the contribution history 
should
-be intact.</p>
+be intact.-->
+
+<p><a href="https://gitbox.apache.org/repos/asf?p=openoffice.git";>The Apache 
OpenOffice Gitbox site</a> provides useful statistics on code contributions and 
changes.</p>
 <h2 id="special-development-branches">Special Development Branches<a 
class="headerlink" href="#special-development-branches" title="Permanent 
link">&para;</a></h2>
-<p>For larger, extensive code modifications, specialized branches are created.
-You can find out more information on them from the Wiki <a 
href="https://wiki.openoffice.org/wiki/Source_Code";>Source Code</a> page.</p>
+<p>For larger, extensive code modifications, specialized branches are created. 
These branches can also be found in our git repository.</p>
+<!--- You can find out more information on them from the Wiki [Source 
Code](https://wiki.openoffice.org/wiki/Source_Code) page.-->
   </div>
 
   <div id="footera">


Reply via email to