Chris Lattner via llvm-dev
2016-Jul-07 02:37 UTC
[llvm-dev] Suggestion to Stop Cross Posting Discussions
> On Jul 6, 2016, at 1:52 AM, Renato Golin <renato.golin at linaro.org> wrote: > > 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.It seems that the clear scope for the list is topics that apply to all subprojects, including developer meeting, infrastructure issues, policy changes/issues, etc.> If we do have such a list, would any decision/consensus taken in it > (say, move to GitHub) be taken as final?Yep, that affects everyone. -Chris
Chris Lattner via llvm-dev
2016-Jul-07 02:39 UTC
[llvm-dev] Suggestion to Stop Cross Posting Discussions
On Jul 6, 2016, at 7:37 PM, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote:> >> If we do have such a list, would any decision/consensus taken in it >> (say, move to GitHub) be taken as final? > > Yep, that affects everyone.Sorry, I meant to say that issues like “move to github” would be on topic for the list. The addition of a new mailing list certainly doesn’t affect how key decisions in the project are made. -Chris
Renato Golin via llvm-dev
2016-Jul-07 09:28 UTC
[llvm-dev] Suggestion to Stop Cross Posting Discussions
On 7 July 2016 at 03:39, Chris Lattner <clattner at apple.com> wrote:> Sorry, I meant to say that issues like “move to github” would be on topic for the list. The addition of a new mailing list certainly doesn’t affect how key decisions in the project are made.Perfect! I'm glad everyone is in agreement. I think it makes sense to move those things out of the dev list and to make it clear that, if you care about the project/s, you should be on that list. :) cheers, --renato