search

llvm / llvm-iwg

The LLVM Infrastructure Working Group
https://foundation.llvm.org/docs/infrastructure-wg/
Other
18 stars 14 forks source link

[Discourse migration] Can we preserve the links to the email archive? #46

Closed ChristianKuehnel closed 2 years ago

ChristianKuehnel commented 3 years ago

People frequently refer to emails via their archive links. Also people link emails to other emails via the archive URLs. So it would be really important to find a way to preserve the links after the migration.

It would be great if archive links between emails would be upgraded to links within Discourse. So that clicking on such a link it gets opened in Discourse, not the mailing list archive.

ChristianKuehnel commented 3 years ago

@sqlbyme since you were talking to Discourse (the company): Can you please raise the question there?

ChristianKuehnel commented 3 years ago

@sqlbyme any news on this topic?

ChristianKuehnel commented 3 years ago

@tlattner please discuss this with the folks from Discourse.

ChristianKuehnel commented 3 years ago

stale effort, removing from out backlog

ChristianKuehnel commented 2 years ago

Hi @tlattner , Have you found a solution for this? Or do we need someone to investigate the options further? In any case we should be transparent about this in the documentation.

tlattner commented 2 years ago

We do not plan to support any redirect. The old archives will exist for reference on the web server for any old links.

tlattner commented 2 years ago

Keep in mind that any post can be edited by an admin at any point. So if someone really wants to fix up a link, we can do it (f they can't).

ChristianKuehnel commented 2 years ago

OK, I'll propose an extension to the documentation.

I was mostly concerned with links in commits and code reviews. People sometimes refer to a discussion on the mailing list via link as background to a certain decision/design in the code ,.

Best, Christian

On Thu, Jan 13, 2022 at 6:43 PM Tanya Lattner @.***> wrote:

Keep in mind that any post can be edited by an admin at any point. So if someone really wants to fix up a link, we can do it (f they can't).

— Reply to this email directly, view it on GitHub https://github.com/llvm/llvm-iwg/issues/46#issuecomment-1012363084, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEYJMCB3BFLJ2RURQOMMSHLUV4FKJANCNFSM46JIXXZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

ChristianKuehnel commented 2 years ago

The string lists.llvm.org/pipermail/occurs around times in the sources of llvm-project. I suppose these should be updated to point to Discourse after the migration and before we shut down the mailing list archive...

ChristianKuehnel commented 2 years ago

OK, I'll propose an extension to the documentation.

No need for at update, the documentation already reflects that.