LLVM used to have mailing lists.
Uncategorized
6
Posts
5
Posters
2
Views
-
LLVM used to have mailing lists. This was pretty bad. The main llvm-dev list was a firehose. It got so many message that I’d just file them and then skim subjects later. There were a bunch of smaller lists, but often discussions would start there and then need wider participation, so people would cc some of the bigger lists. Fine, except that not everyone was on all of the lists, so some messages would be stopped at moderation and the people who were on only the larger lists would see a random fragment of a thread. And maybe their replies wouldn’t be seen by people on other lists.
The move to Discourse was meant to fix this, but it’s actually managed to make things worse. I really cannot get over how awful Discourse is as a piece of software. There is an LLVM Cambridge social next week. There is a post about it on Discourse. The only reason o know about this is that the author sent me a Signal message. Searching for ‘Cambridge’ gives me a handful of messages for 10+ years ago (imported from the mailing lists), not the recent one. It doesn’t show up in the new messages feed (neither do most things there).
I basically never see things on Discourse unless someone tags me (and then I get an email) or someone sends me an out-of-band link to a thread. I know far less about what is happening than when I subscribed to the mailing lists. I am far less able to find things in searches.
I voted in favour of the Discourse switch because the problems with the mailing lists were real, but the solution is much worse. I suspect the right solution for a big project like this is:
- Make the ACLs for all lists accept posts from anyone who is subscribed to any of them, so cross-posting to related lists works.
- Provide a read-only IMAP system with all of the messages for all lists in it so anyone can just add it in their mail client and have the full history (or whatever subset they ask their client to download).
-
LLVM used to have mailing lists. This was pretty bad. The main llvm-dev list was a firehose. It got so many message that I’d just file them and then skim subjects later. There were a bunch of smaller lists, but often discussions would start there and then need wider participation, so people would cc some of the bigger lists. Fine, except that not everyone was on all of the lists, so some messages would be stopped at moderation and the people who were on only the larger lists would see a random fragment of a thread. And maybe their replies wouldn’t be seen by people on other lists.
The move to Discourse was meant to fix this, but it’s actually managed to make things worse. I really cannot get over how awful Discourse is as a piece of software. There is an LLVM Cambridge social next week. There is a post about it on Discourse. The only reason o know about this is that the author sent me a Signal message. Searching for ‘Cambridge’ gives me a handful of messages for 10+ years ago (imported from the mailing lists), not the recent one. It doesn’t show up in the new messages feed (neither do most things there).
I basically never see things on Discourse unless someone tags me (and then I get an email) or someone sends me an out-of-band link to a thread. I know far less about what is happening than when I subscribed to the mailing lists. I am far less able to find things in searches.
I voted in favour of the Discourse switch because the problems with the mailing lists were real, but the solution is much worse. I suspect the right solution for a big project like this is:
- Make the ACLs for all lists accept posts from anyone who is subscribed to any of them, so cross-posting to related lists works.
- Provide a read-only IMAP system with all of the messages for all lists in it so anyone can just add it in their mail client and have the full history (or whatever subset they ask their client to download).
@david_chisnall
Have you tried the mailing list mode in Discourse? -
LLVM used to have mailing lists. This was pretty bad. The main llvm-dev list was a firehose. It got so many message that I’d just file them and then skim subjects later. There were a bunch of smaller lists, but often discussions would start there and then need wider participation, so people would cc some of the bigger lists. Fine, except that not everyone was on all of the lists, so some messages would be stopped at moderation and the people who were on only the larger lists would see a random fragment of a thread. And maybe their replies wouldn’t be seen by people on other lists.
The move to Discourse was meant to fix this, but it’s actually managed to make things worse. I really cannot get over how awful Discourse is as a piece of software. There is an LLVM Cambridge social next week. There is a post about it on Discourse. The only reason o know about this is that the author sent me a Signal message. Searching for ‘Cambridge’ gives me a handful of messages for 10+ years ago (imported from the mailing lists), not the recent one. It doesn’t show up in the new messages feed (neither do most things there).
I basically never see things on Discourse unless someone tags me (and then I get an email) or someone sends me an out-of-band link to a thread. I know far less about what is happening than when I subscribed to the mailing lists. I am far less able to find things in searches.
I voted in favour of the Discourse switch because the problems with the mailing lists were real, but the solution is much worse. I suspect the right solution for a big project like this is:
- Make the ACLs for all lists accept posts from anyone who is subscribed to any of them, so cross-posting to related lists works.
- Provide a read-only IMAP system with all of the messages for all lists in it so anyone can just add it in their mail client and have the full history (or whatever subset they ask their client to download).
@david_chisnall the last requirement you mention sounds like the 'lists need to be archived, with searchable archives and messages that can be linked to' that I know from @theasf ...
https://lists.apache.org/ ... Has archives going back in time for all projects including the foundation itself, back into the late 1990s. If logged in, also allows for answering messages in mail threads.
-
@david_chisnall the last requirement you mention sounds like the 'lists need to be archived, with searchable archives and messages that can be linked to' that I know from @theasf ...
https://lists.apache.org/ ... Has archives going back in time for all projects including the foundation itself, back into the late 1990s. If logged in, also allows for answering messages in mail threads.
-
LLVM used to have mailing lists. This was pretty bad. The main llvm-dev list was a firehose. It got so many message that I’d just file them and then skim subjects later. There were a bunch of smaller lists, but often discussions would start there and then need wider participation, so people would cc some of the bigger lists. Fine, except that not everyone was on all of the lists, so some messages would be stopped at moderation and the people who were on only the larger lists would see a random fragment of a thread. And maybe their replies wouldn’t be seen by people on other lists.
The move to Discourse was meant to fix this, but it’s actually managed to make things worse. I really cannot get over how awful Discourse is as a piece of software. There is an LLVM Cambridge social next week. There is a post about it on Discourse. The only reason o know about this is that the author sent me a Signal message. Searching for ‘Cambridge’ gives me a handful of messages for 10+ years ago (imported from the mailing lists), not the recent one. It doesn’t show up in the new messages feed (neither do most things there).
I basically never see things on Discourse unless someone tags me (and then I get an email) or someone sends me an out-of-band link to a thread. I know far less about what is happening than when I subscribed to the mailing lists. I am far less able to find things in searches.
I voted in favour of the Discourse switch because the problems with the mailing lists were real, but the solution is much worse. I suspect the right solution for a big project like this is:
- Make the ACLs for all lists accept posts from anyone who is subscribed to any of them, so cross-posting to related lists works.
- Provide a read-only IMAP system with all of the messages for all lists in it so anyone can just add it in their mail client and have the full history (or whatever subset they ask their client to download).
@david_chisnall i’m not sure of the solution, but I’ve seen this happen with several projects, and I agree that discourse is an abominable piece of software that is ruining communities.
-
LLVM used to have mailing lists. This was pretty bad. The main llvm-dev list was a firehose. It got so many message that I’d just file them and then skim subjects later. There were a bunch of smaller lists, but often discussions would start there and then need wider participation, so people would cc some of the bigger lists. Fine, except that not everyone was on all of the lists, so some messages would be stopped at moderation and the people who were on only the larger lists would see a random fragment of a thread. And maybe their replies wouldn’t be seen by people on other lists.
The move to Discourse was meant to fix this, but it’s actually managed to make things worse. I really cannot get over how awful Discourse is as a piece of software. There is an LLVM Cambridge social next week. There is a post about it on Discourse. The only reason o know about this is that the author sent me a Signal message. Searching for ‘Cambridge’ gives me a handful of messages for 10+ years ago (imported from the mailing lists), not the recent one. It doesn’t show up in the new messages feed (neither do most things there).
I basically never see things on Discourse unless someone tags me (and then I get an email) or someone sends me an out-of-band link to a thread. I know far less about what is happening than when I subscribed to the mailing lists. I am far less able to find things in searches.
I voted in favour of the Discourse switch because the problems with the mailing lists were real, but the solution is much worse. I suspect the right solution for a big project like this is:
- Make the ACLs for all lists accept posts from anyone who is subscribed to any of them, so cross-posting to related lists works.
- Provide a read-only IMAP system with all of the messages for all lists in it so anyone can just add it in their mail client and have the full history (or whatever subset they ask their client to download).
@david_chisnall just to temper the Discourse hate in this thread (but not deny your experience), I absolutely love it... it's lovely to maintain, prevents spam better than anything I've ever maintained including other forum software and mailing lists, and doesn't fill my mailbox (though it can, it has excellent mail support both in and out).
What would make it work better for you? I'm not a contributor, but I have written custom stuff for the one I maintain...I may have suggestions.
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@troppacaffeina @bluberrycookie @serimemo io sono orrendamente indietro con le risposte, ma se a qualcuno va bene aspettare i mesi tra una lettera e l'altra ci sono anche io
-
-
@sabrinaweb71 @bluberrycookie @serimemo confermo, è lui, io lo faccio ed è sempre bello sia spedire che ricevere!
-
@filobus giusta osservazione, facciamo più sconti a chi spreca di più!
-
Quale distribuzione stabile con #KDE consigliate di provare?
-
Your AI chatbot may be stealing your conversations.
Many #BigTech platforms:
• use chat inputs for training
• store conversations indefinitely
• process data in centralized cloudsWhat does that mean for #dataprivacy?
We break it down 👇
https://nextcloud.com/de/blog/the-problems-with-big-tech-ai-data-collection-privacy-concerns-and-how-to-protect-your-data/
-
This post did not contain any content.
-
Del valore o del costo?
https://www.ilpost.it/2026/03/19/furto-scarpe-prada-rubate-dolo-venezia-rubate/
