Define long-term roadmap for mailing list archive
ChristianKuehnel opened this issue · 3 comments
ChristianKuehnel commented
From the discussing in the IWG meeting on 2022-02-01:
What is the long-term roadmap for the mailing lists and the archive?
- Do we want to create static snapshot of the http server?
- How to handle GDPR deletion requests?
- How to handle incoming links from code comments or commits? How long do we want to preserve these?
This is part of #47.
ChristianKuehnel commented
from meeting on 2022-02-15:
- no action needed at the moment.
- Revisit when mailman is turned down.
- We can also manage these pages as static html.
- We still have the -commis and -bugs mailing list still running on mailman.
- How do we want to continue with these lists? How do we notify users?
- GitHub Issues will hopefully implement subscription to labels, this could replace the -bugs lists.
- Herald rules in Phabricator could replace the -commits mailing lists.
- We should run an RFC there to understand user needs.
- This is something we could do today.
ChristianKuehnel commented
from meeting on 2022-03-01:
fork this issue into a new one for the RFC on the -commits lists #100
aeubanks commented
A tiny nit, there's only one -bugs list right now, llvm-bugs.