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 efab4b9 Regenerated website based on
298d98fb7afa0e71553af030fb5b8608b0a94d27 commit
efab4b9 is described below
commit efab4b99e9e42e972628f8e699a9727c2a8d7cc3
Author: GitHub Actions <acti...@users.noreply.github.com>
AuthorDate: Sat May 3 20:56:50 2025 +0000
Regenerated website based on 298d98fb7afa0e71553af030fb5b8608b0a94d27 commit
---
output/assets/js/search-data.json | 6 +++---
output/process-howto.html | 2 +-
output/process.html | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/output/assets/js/search-data.json
b/output/assets/js/search-data.json
index fe40fda..9a42ba9 100644
--- a/output/assets/js/search-data.json
+++ b/output/assets/js/search-data.json
@@ -57,7 +57,7 @@
},"8": {
"doc": "Attic Process",
"title": "Attic Process: How To",
- "content": ". The sections below describe How To complete the various
tasks of retiring a project and moving it to The Apache Attic: . | 1. Confirm
Board Resolution | 2. Create project page on Attic site: | 3. Inform users of
the move to the Attic | 4. Update the project DOAP file (if any): | 5. Get
infra lock down project’s resources | 6. Announce on annou...@apache.org | .
The following are useful Git/svn/https locations: . | site source, built to
asf-site branch | ATTIC Jira | per [...]
+ "content": ". The sections below describe How To complete the various
tasks to be done by Attic team for retiring a project and moving it to The
Apache Attic: . | 1. Confirm Board Resolution | 2. Create project page on Attic
site: | 3. Inform users of the move to the Attic | 4. Update the project DOAP
file (if any): | 5. Get infra lock down project’s resources | 6. Announce on
annou...@apache.org | . The following are useful Git/svn/https locations: . |
Attic site source | ATTIC Jira [...]
"url": "/process-howto.html#attic-process-how-to",
"relUrl": "/process-howto.html#attic-process-how-to"
@@ -71,7 +71,7 @@
},"10": {
"doc": "Attic Process",
"title": "2. Create project page on Attic site:",
- "content": "https://attic.apache.org/projects/${project}.html . The Attic
Website uses Jekyll, which generates the Project Pages from project data files
in YAML Format. Adding a project to the website is done by adding a YAML file
for the project to the _data/projects directory. THIS NEEDS UPDATING, see
details in process.md* . | clone the Git Attic Repository | Create the project
YAML file (see the Project Data page for help on crafting the YAML file) |
Commit the file to your clone [...]
+ "content": "https://attic.apache.org/projects/${project}.html . You can
create a PR for the $project.yaml file using the GitHub Action Generate PR to
add _data/projects/pid.yaml file. Click on ‘Run workflow’ and enter the lower
case project id. If the id is valid, the workflow will create a PR to add the
YAML file. Once the PR has been checked and applied, the site will be
regenerated. The project details will be found at
https://attic.apache.org/projects/$project.html and associated [...]
"url": "/process-howto.html#2-create-project-page-on-attic-site",
"relUrl": "/process-howto.html#2-create-project-page-on-attic-site"
@@ -127,7 +127,7 @@
},"18": {
"doc": "Process",
"title": "2. If the board approves the resolution",
- "content": "The Attic team will open an Attic JIRA item - ‘Move ${project}
to the Attic’. If you have an ASF GH login, you can create a PR for the
projectId.yaml file using the GitHub action Generate PR to add
_data/projects/pid.yaml file . Click on ‘Run workflow’ and enter the lower case
project id. If the id is valid, the workflow will create a PR to add the YAML
file. Once the PR has been checked and applied, the site will be regenerated.
The project details will be found at https [...]
+ "content": "The Attic team will open an Attic JIRA item - ‘Move ${project}
to the Attic’. Generated issue content typically contains following steps (see
“How to” for a description of each step that the Attic team will follow): . | #
Confirm Board Resolution | # Create project page on Attic site:
https://attic.apache.org/projects/$project.html | # Inform users of the move to
the Attic | # Update the project DOAP files (if any) or copy to
projects-override | # Get infra lock down proj [...]
"url": "/process.html#2-if-the-board-approves-the-resolution",
"relUrl": "/process.html#2-if-the-board-approves-the-resolution"
diff --git a/output/process-howto.html b/output/process-howto.html
index 673516d..5b057d2 100644
--- a/output/process-howto.html
+++ b/output/process-howto.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta
http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet"
href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet"
href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet">
<style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a,
.site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(2)) > a,
.site-nav > ul.nav-list:first-child > li > ul > li [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta
http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet"
href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet"
href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet">
<style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a,
.site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(2)) > a,
.site-nav > ul.nav-list:first-child > li > ul > li [...]
been 'moved to the Attic'. This means that the ${project} developers (more
formally its Project Management Committee) have voted to retire ${project}
and move the responsibility for its oversight over to the Attic project.
diff --git a/output/process.html b/output/process.html
index 2e86da5..e6b79d3 100644
--- a/output/process.html
+++ b/output/process.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta
http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet"
href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet"
href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet">
<style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child >
li:not(:nth-child(2)) > a, .site-nav > ul.nav-list:first-child > li > ul > li a
{ background-image: none; } .site-nav > ul.nav-list:no [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta
http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet"
href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet"
href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet">
<style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child >
li:not(:nth-child(2)) > a, .site-nav > ul.nav-list:first-child > li > ul > li a
{ background-image: none; } .site-nav > ul.nav-list:no [...]
