[ 
https://issues.apache.org/jira/browse/ATTIC-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951232#comment-17951232
 ] 

Melissa Logan commented on ATTIC-243:
-------------------------------------

[~hboutemy] one came through M&P earlier this year (or perhaps late last year) 
but I can't recall which project it was. They asked us how to archive their 
social media profiles, so we developed guidlines for any Attic project moving 
forward.

With regard to your [comment here|https://github.com/apache/attic-site/pull/2], 
yes it would require an action from the project:
{quote}perhaps we'll need to add some introduction steps in the board agenda 
process to make that clear to projects asking to go to the Attic: currently, 
the handover from the (now former) project's team and the Attic team is not 
formalized at all
{quote}
Should we proceed with adding the requirements to the new page - or would it 
make more sense for these instructions to go elsewhere as you suggested?

cc: [~bkp] 

> Add M&P requirements to the Attic process
> -----------------------------------------
>
>                 Key: ATTIC-243
>                 URL: https://issues.apache.org/jira/browse/ATTIC-243
>             Project: Attic
>          Issue Type: New Feature
>            Reporter: Herve Boutemy
>            Priority: Major
>
> see https://lists.apache.org/thread/5b49pn2z04jbvsm2fyf8kno1k73qybpv
> {quote}Last fall the M&P team discovered a gap in the Attic process related to
> marketing, specifically social media profiles and how to handle them once a
> project goes to the Attic. [1]
> The team discussed how to best manage this and we have now submitted a pull
> request with the recommended solution:
> https://github.com/apache/attic-site/pull/2.
> If any questions or updates needed, just let us know.
> Melissa on behalf of ASF M&P
> [1] https://lists.apache.org/thread/3nrb9t5qlx75ps4cmjkxtnzvxc669nzg = 
> https://lists.apache.org/thread/xr9frfcl48l3c3pn5d0qqbnzmt485dq6
> {quote}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to