[llvm-dev] Suggestion to Stop Cross Posting Discussions

Renato Golin via llvm-dev llvm-dev at lists.llvm.org
Wed Jul 6 01:52:14 PDT 2016

On 6 July 2016 at 09:10, David Chisnall via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> On 6 Jul 2016, at 05:32, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>> +1 for an “llvm-project” list that everyone involved in any llvm subproject is encouraged to sign up for.
> Another +1 from me.  The llvm-dev and cfe-dev lists are both firehoses and a lot of people on the periphery of the community don’t subscribe to them for this reason (which is not a negative, it’s a sign of a healthy and active project).  A lower-traffic list for everyone in the community would be very useful.

I'm not against the idea, never have been, but I'd like to know what's
the expected scope and topics of such a list.

In the past, I have proposed to have a separate list to discuss
non-dev topics, pertinent to the whole community (like infrastructure,
tools, etc), and have only met discouragement. That's why I'm
surprised everyone is now in agreement... :)

If we do have such a list, would any decision/consensus taken in it
(say, move to GitHub) be taken as final?

For example, say we discuss and agree on that list that we'll move to
GitHub, we'd probably have to announce to all lists, so we're sure
everyone is aware. That announcement can spark discussions like "I
wasn't aware, how can you guys take decisions without asking first",
which will be met with responses like "it was done on this and that
list, you should be there if you care". That can be avoided if we are
clear on what kinds of topics and what kind of decision power each
list has. Cross-posting to each list to let people know *beforehand*
defies the purpose of having such a list in the first place.

Another example is the llvm-commits list. It's generally accepted that
we discuss patches, but not design decisions on it, which should be
done in llvm-dev.

I'm more than happy to see all the non-dev discussions moving
elsewhere, but it has to be *clear* to everyone that decisions as
important as which VCS they'll use next month will be decided there.


More information about the llvm-dev mailing list