This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/attic.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new a4f9746  Regenerated website based on 
728308caeb80894e082e1eccae43d15d9e1090bb commit
a4f9746 is described below

commit a4f9746bc2f1fbdefd57a4bd03f22a142900849a
Author: GitHub Actions <acti...@users.noreply.github.com>
AuthorDate: Sun Apr 20 15:31:05 2025 +0000

    Regenerated website based on 728308caeb80894e082e1eccae43d15d9e1090bb commit
---
 output/process.html | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)

diff --git a/output/process.html b/output/process.html
index abaa9a3..1ce45a0 100644
--- a/output/process.html
+++ b/output/process.html
@@ -65,7 +65,7 @@
       </ul>
     </li>
     <li>If the board approves the resolution, open an <a 
href="https://issues.apache.org/jira/browse/ATTIC";>Attic JIRA</a> item - 'Move 
${project} to the Attic'.<br />
-      The Attic PMC will step in and create a detailed issue description using 
<a 
href="https://svn.apache.org/repos/asf/attic/site/retire.py";><code>retire.py</code></a>,
 with other generated parts to move the project to the Attic.<br />
+      The Attic PMC will step in and create a detailed issue description using 
<a 
href="https://github.com/apache/attic/blob/main/retire.py";><code>retire.py</code></a>,
 with other generated parts to move the project to the Attic.<br />
       Generated issue content typically contains following steps (see <a 
href="#howto">"How to"</a> below for a description of each step): 
       <ol type="1">
         <li><a href="#confirm-resolution">#</a> Confirm Board Resolution</li>
@@ -151,9 +151,9 @@ ${Name} on behalf of ${project} + the Attic.
 </h4>
 <div class="section-content">
 <p>The Attic website is built using Anakia. <a 
href="https://velocity.apache.org/anakia/";>Anakia</a> is an old site technology 
built on top of Apache Velocity. 
-     You can get the source for the site from Subversion: </p>
-<pre>svn co https://svn.apache.org/repos/asf/attic/site</pre>
-<p>You can generate the required changes using the Python3 <a 
href="https://svn.apache.org/repos/asf/attic/site/retire.py";><code>retire.py</code></a>
 script as follows:</p>
+     You can get the source for the site from Git: </p>
+<pre>git clone https://github.com/apache/attic</pre>
+<p>You can generate the required changes using the Python3 <a 
href="https://github.com/apache/attic/blob/main/retire.py";><code>retire.py</code></a>
 script as follows:</p>
 <pre>./retire.py id1 [id2...]</pre>
 <p>This should generate the following files for each ID, as well as updating 
<code>xdocs/stylesheets/project.xml</code>:</p>
 <ul>
@@ -162,10 +162,9 @@ ${Name} on behalf of ${project} + the Attic.
     <li><code>xdocs/projects/ID.xml</code></li>
     <li><code>cwiki_retired/WIKI_ID.txt</code> (this adds the CWIKI banner for 
projects)</li>
   </ul>
-<p>The code allows for wiki aliases, as described in the 
cwiki_retired/AAREADME.txt file.</p>
-<p>Review the changes in <code>xdocs/</code>, then commit to svn.</p>
-<p>The <code>ID.jira.tmp</code> file is text that can be copy-pasted into a 
JIRA description. It should be deleted after use, and not committed to SVN.</p>
-<p>The <a href="https://ci2.apache.org/#/builders/16";>buildbot job</a> will 
build the site and commit the result which will be published soon after.</p>
+<p>The code allows for wiki aliases, as described in the 
<code>cwiki_retired/AAREADME.txt</code> file.</p>
+<p>Review the changes in <code>xdocs/</code>, then commit to Git.</p>
+<p>The <code>ID.jira.tmp</code> file is text that can be copy-pasted into a 
JIRA description. It should be deleted after use, and not committed to Git.</p>
 </div>
                  
 <h4 id="doap">
@@ -184,7 +183,7 @@ new category:  &lt;category 
rdf:resource="http://projects.apache.org/category/re
 </h4>
 <div class="section-content">
 <p>Open an <a 
href="https://issues.apache.org/jira/browse/INFRA";>Infrastructure JIRA</a> 
issue identifying the resources that need turning off/making read only.</p>
-<p>The content of the issue can be generated using <a 
href="https://svn.apache.org/repos/asf/attic/site/infrajiratext.py";><code>infrajiratext.py</code></a>.</p>
+<p>The content of the issue can be generated using <a 
href="hhttps://github.com/apache/attic/blob/main/infrajiratext.py";><code>infrajiratext.py</code></a>.</p>
 <p>Typically, it contains steps like following, that need to be tweaked based 
on assets of the retired project:
     <ul>
       <li>Make source control Git|Svn read-only</li>
@@ -237,7 +236,7 @@ ${NAME}
 on behalf of the Apache Attic and the now retired Apache ${project} project
   </pre>
 <p>It's important to include the boilerplate from the project's site so people 
-     know what we're talking about. </p>
+     know what we're talking about.</p>
 </div>
          </div>
     <div class="column span-8 last">

Reply via email to