<div dir="ltr"><div>I've just tried out discourse for the first time. It is not clear to me how to use it to replace mailing lists. It has a setting "mailing list mode", which sounds like the right thing -- sending all messages via email. Except that option is global -- all messages in all categories on the llvm discourse instance. Which definitely isn't what I want at all. I don't want to subscribe to MLIR, for example.</div><div><br></div><div>In general, I'd say I'm pretty uncomfortable with switching from a mailing list to discourse. Discourse seems entirely reasonable to use for end-user-facing forums, but I'm rather unconvinced about its suitability as a dev-list replacement. Other communities (e.g. python) seem to have a split, still: mailing lists for dev-lists, and discourse for end-user-facing forums.</div><div><br></div><div>I'd also note that Mailman3 provides a lot more features than what we're used to with mailman2, including the ability to interact/post through the website.</div><div><br></div><div>Maybe someone can convince me that I'm just being a curmudgeon, but at this point, I'd say we ought to be investigating options to have Someone Else manage the mailman service, and keep using mailing lists, rather than attempting to switch to discourse.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 1, 2021 at 4:50 PM Tom Stellard via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
We recently[1] ran into some issues with the mailing lists that caused<br>
us to disable automatic approval of subscriptions. Over the past few<br>
months, the LLVM Foundation Board of Directors have been investigating<br>
solutions to this issue and are recommending that the project move its<br>
discussion forum from mailman to Discourse[2].<br>
<br>
The proposed migration plan is to move the discussion lists (e.g *-dev,<br>
*-users lists) to Discourse as soon as possible. The commit email lists<br>
(*-commits lists) will remain on mailman until a not-yet-determined date<br>
in the future, after which they will be replaced by something else.<br>
Some commit lists alternatives include Discourse and GitHub commit<br>
comments (but there may be others).<br>
<br>
Here are the reasons why the LLVM Foundation Board of Directors is<br>
recommending this change:<br>
<br>
- The LLVM project discussion lists cannot be adequately maintained by our<br>
current volunteer infrastructure staff and without changes we run the<br>
risk of a major outage.<br>
<br>
- We are able to make this change without significant impact to user's or<br>
developer's daily workflows because Discourse supports email subscriptions<br>
and posting (NOTE: if you are concerned that your workflow may be impacted<br>
by this change, please contact the Infrastructure Working Group[3], so<br>
they can help test your workflow with Discourse.)<br>
<br>
- Discourse gives us additional features that will benefit the community:<br>
- Easy to signup and subscribe to categories<br>
- Better moderation tools.<br>
- Web-based user interface.<br>
- Ability to send announcements to multiple categories to avoid having to<br>
cross-post community wide announcements.<br>
<br>
- A subset of the community (MLIR) have been experimenting with Discourse<br>
for over a year and are able to provide feedback about this experience<br>
to the Board of Directors.<br>
<br>
We did also consider one alternative, which was migrating our lists to a<br>
mailman hosting service. However, we concluded that with all the work it<br>
would take to migrate our lists to another service, it would be better<br>
if we moved to a service (like Discourse) that provided more features<br>
than what we have now.<br>
<br>
We understand that moving to Discourse is a change for the community and<br>
that people may be worried about this having a negative impact on their<br>
participation in the project. As mentioned above, we believe that this<br>
change can be done without significant impact to anyone’s workflows.<br>
If you disagree, please contact the Infrastructure Working Group, to<br>
document the impact to your workflow, so we can work together to find<br>
a solution for your issue.<br>
<br>
If you have any other questions or comments you can raise them on this<br>
thread and please keep criticisms constructive and on topic.<br>
<br>
<br>
LLVM Foundation Board of Directors<br>
<br>
[1] <a href="https://lists.llvm.org/pipermail/llvm-dev/2021-March/149027.html" rel="noreferrer" target="_blank">https://lists.llvm.org/pipermail/llvm-dev/2021-March/149027.html</a><br>
[2] <a href="https://www.discourse.org/" rel="noreferrer" target="_blank">https://www.discourse.org/</a><br>
[3] <a href="https://github.com/llvm/llvm-iwg" rel="noreferrer" target="_blank">https://github.com/llvm/llvm-iwg</a><br>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div>