[llvm-dev] RFC: Moving toward Discord and Discourse for LLVM's discussions

Joan Lluch via llvm-dev llvm-dev at lists.llvm.org
Mon Nov 18 06:52:14 PST 2019

+1 from me for the replacement of the mailing list by a web based forum

> On 18 Nov 2019, at 15:18, Sam McCall via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> On Mon, Nov 18, 2019 at 2:49 PM Robinson, Paul via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> |  mailing lists for longer-form discussions are unfamiliar, difficult, and often intimidating for newcomers
> Um… what?  While I know (via my own children) that folks nowadays use multiple avenues of communication, it’s *really* hard to imagine email as a *mechanism* being unfamiliar/difficult/intimidating.  Moving to a new mechanism wouldn’t alter the fact of the very large number of strangers participating, which to my mind would be the unfamiliar/difficult/intimidating part.
> --paulr
> Some cases I can think of here:
>  - unclear how to reply to a mail that was sent before you subscribed to the ML (obvious newbie problem - generally I'd lurk on the web until I wanted to reply)
>  - unclear how to create a partitioned space (new mailing list) for a topic
>  - subscription state/bounce messages/moderation are all IMO unclear if you haven't used mailman before
>  - the volume of traffic on (effectively-mandatory) lists is so high that it requires using mail filters, most people don't use those
> (A weak +1 to the concern about this change being made by some people in a conference room somewhere - if that's the decision-making process that's fine with me, but it'd be great to know that and have a defined way to get issues on the agenda)
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191118/ac5afdc2/attachment.html>

More information about the llvm-dev mailing list