You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@attic.apache.org by hb...@apache.org on 2026/04/13 20:57:48 UTC
(attic) branch anticipate-social-media created (now 51a8479)
This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a change to branch anticipate-social-media
in repository https://gitbox.apache.org/repos/asf/attic.git
at 51a8479 social media in parallel to Attic
This branch includes the following new commits:
new 51a8479 social media in parallel to Attic
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(attic) 01/01: social media in parallel to Attic
Posted by hb...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch anticipate-social-media
in repository https://gitbox.apache.org/repos/asf/attic.git
commit 51a84797bca34e18b8a8de43576c2142b627eedf
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Mon Apr 13 22:57:37 2026 +0200
social media in parallel to Attic
---
process-howto.md | 44 ++++++++++++++++++++++----------------------
process.md | 5 +++--
2 files changed, 25 insertions(+), 24 deletions(-)
diff --git a/process-howto.md b/process-howto.md
index 79994f0..94712eb 100644
--- a/process-howto.md
+++ b/process-howto.md
@@ -32,6 +32,8 @@ graph TD;
accTitle: the Attic Process
accDescr: Attic process diagram which shows the steps of moving a Retired Project to the Attic
RESL("`1 **Confirm Board Resolution**`")
+ SOCL("`**Update social media**
+ (if any)`")
JIRA("`**Create ATTIC Jira**
(to manage the move)`")
PROJ("`2 **Create Project Page**
@@ -40,29 +42,26 @@ graph TD;
of move to Attic`")
DOAP("`4 **Update Project DOAP**
file (if any)`")
- SOCL("`5 **Update social media**
- (if any)`")
- LOCK("`6 **Lock Down Resources**
+ LOCK("`5 **Lock Down Resources**
(create INFRA Jira ticket)`")
- ANNC("`7 **Announce**
+ ANNC("`6 **Announce**
*announce AT apache.org*`")
RESL-->JIRA;
RESL-->PROJ;
JIRA<-->PROJ;
+ RESL-->SOCL;
PROJ-->USER;
PROJ-->DOAP;
- PROJ-->SOCL;
USER-->LOCK;
DOAP-->LOCK;
- SOCL-->LOCK;
LOCK-->ANNC;
click RESL "#1-confirm-board-resolution"
+ click SOCL "#update-social-media-if-any"
click PROJ "#2-create-project-page-on-attic-site"
click USER "#3-inform-users-of-the-move-to-the-attic"
click DOAP "#4-update-the-project-doap-file-if-any"
- click SOCL "#5-update-social-media-if-any"
- click LOCK "#6-get-infra-to-lock-down-project-resources"
- click ANNC "#7-announce-on-announce-at-apacheorg"
+ click LOCK "#5-get-infra-to-lock-down-project-resources"
+ click ANNC "#6-announce-on-announce-at-apacheorg"
```
The following are useful Git/svn/https locations:
@@ -94,6 +93,18 @@ and its rendered HTML in [asf-site](https://github.com/apache/www-site/tree/asf-
Create initial [ATTIC Jira issue](https://issues.apache.org/jira/projects/ATTIC/) to start tracking retirement process and add former PMC Chair for information about next steps where their help may be necessary.
+### Update Social Media (if any)
+
+In parallel to Attic work, Marketing & Publicity will coordinate with the retiring project's members to know if there is a social media profile associated.
+
+In that case, retiring PMC members will have to to:
+
+1. Update social media profiles:
+ Change the profile name (not handle) from "Apache Foo" to "Apache Foo (Attic)".
+ Update the profile messaging to read “Apache Foo (Attic) is no longer an active project. Visit Apache.org to learn more."
+2. Provide ASF Marketing & Publicity with social media access:
+ Once social media changes have been made, email <a href="mailto:press@apache.org">press@apache.org</a> to discuss with the ASF Marketing & Publicity team the best way to share social media credentials for safekeeping.
+
## 2. Create project page on Attic site:
**https://attic.apache.org/projects/${project}.html**
@@ -161,18 +172,7 @@ add category: <category rdf:resource="http://projects.apache.org/category/retir
You can use [`script/project2attic.py`](https://github.com/apache/comdev-projects/blob/trunk/scripts/project2attic.py) to prepare the update that you'll just need to
review and commit.
-## 5. Update Social Media (if any)
-
-Contact the retiring project's members to know if there is a social media profile associated.
-
-In that case, ask them to:
-1. Update social media profiles:
- Change the profile name (not handle) from "Apache Foo" to "Apache Foo (Attic)".
- Update the profile messaging to read “Apache Foo (Attic) is no longer an active project. Visit Apache.org to learn more."
-2. Provide ASF Marketing & Publicity with social media access:
- Once social media changes have been made, email <a href="mailto:press@apache.org">press@apache.org</a> to discuss with the ASF Marketing & Publicity team the best way to share social media credentials for safekeeping.
-
-## 6. Get Infra to lock down project resources
+## 5. Get Infra to lock down project resources
Open an [Infrastructure Jira](https://issues.apache.org/jira/browse/INFRA) issue identifying
the resources that need turning off/making read only.
@@ -192,7 +192,7 @@ Typically, it contains steps like following, that need to be tweaked based on as
- Delete LDAP group(s)
- Turn off automated builds
-## 7. Announce on *announce AT apache.org*
+## 6. Announce on *announce AT apache.org*
Announce that the project [is now retired](https://lists.apache.org/list?announce@apache.org:lte=1M:%22is%20now%20retired%22).
diff --git a/process.md b/process.md
index ee586d9..760daaa 100644
--- a/process.md
+++ b/process.md
@@ -45,12 +45,13 @@ to move that PMC into the Attic and gently close it down.
## 2. If the board approves the resolution
The Attic team will open an [Attic JIRA](https://issues.apache.org/jira/browse/ATTIC) item - `Move ${project} to the Attic`.
-Issue content typically contains the following steps (click for a description of each step of the process):
+In parallel, Marketing & Publicity will coordinate with the retiring project's members to [update social media (if any)](process-howto.html#update-social-media-if-any).
+
+Attic JIRA issue content typically contains the following steps (click for a description of each step of the process):
1. [Confirm Board Resolution](process-howto.html#1-confirm-board-resolution)
1. [Create project page on Attic site](process-howto.html#2-create-project-page-on-attic-site)
1. [Inform users of the move to the Attic](process-howto.html#3-inform-users-of-the-move-to-the-attic)
1. [Update the project DOAP files (if any)](process-howto.html#4-update-the-project-doap-file-if-any)
- 1. [Update social media (if any)](process-howto.html#5-update-social-media-if-any)
1. [Get Infra to lock down project resources](process-howto.html#6-get-infra-to-lock-down-project-resources)
1. [Announce on *announce AT apache.org*](process-howto.html#7-announce-on-announce-at-apacheorg)