search for: discourse

Hello everyone, *Short version:*I've set up an LLVM Discord server for real time chat (similar to IRC) and an LLVM Discourse server for forums (similar to email lists): https://discord.gg/xS7Z362 https://llvm.discourse.group/ Please join and use these new services. They are only partially set up and still very new, so don't hesitate to improve them and/or reach out to this thread with any issues you see or things yo...

...and definitive communication channel. > > It should be absolutely enough to follow llvm-dev to be completely informed > about any major RFC, discussion or design decisions. > If your concern is to be able to stay informed by email, then subscribing to the right "category" on Discourse should provide exactly this (everyone can select their notification preferences on Discourse). Is there something more you need that I missed? Best, -- Mehdi > > David > > On 18. Nov 2019, at 08:48, Chandler Carruth via llvm-dev < > llvm-dev at lists.llvm.org> wrote:...

FWIW I'm a fan of using open-source stuff for open-source projects. Discourse looks open source, but Discord doesn't as far as I can tell (?). On Mon, Nov 18, 2019 at 3:15 AM Chandler Carruth via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Hello folks, > > I sent the message quoted below to llvm-dev@ just now, but it applies to > the whole community...

...e days? > > On Mon, Nov 18, 2019 at 8:48 AM Chandler Carruth via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > > > Hello everyone, > > > > Short version: > > I've set up an LLVM Discord server for real time chat (similar to IRC) > and an LLVM Discourse server for forums (similar to email lists): > > https://discord.gg/xS7Z362 > > https://llvm.discourse.group/ > > > > Please join and use these new services. They are only partially set up > and still very new, so don't hesitate to improve them and/or reach out to >...

...xisting community members to participate to be useful should be launched without a wider discussion. This paragraph in your announcement stood out: > > > We talked to a bunch of people and looked at the options out there and > > the most promising ones were Discord for chatting and Discourse for > > longer-form discussions. > > Who are these 'bunch of people'? Why were they selected to make this decision (and by whom)? > > Note that I don't object to the creation of a Discord server (though the 'YOUR CONTENT' section of the T&Cs contains cla...

Hi all, We’ve been having discussions over the last few weeks with stakeholders both inside and outside of AMD about where we could best have a dedicated and open discussion space for topics around the AMDGPU target. The conclusion was that we’d like to try the use of a category in the LLVM Discourse group, which is mostly used for MLIR discussion so far. I have started a Discourse topic with more detail, as that seemed rather fitting: https://llvm.discourse.group/t/category-for-the-amdgpu-target/1480 However, this obviously affects the broader LLVM community, hence this e-mail on llvm-dev. I...

...personal interest here - but my understanding was > that there was/is a fair bit of pushback to fragmenting the > communications channels to discord before there's a more general > buy-in to switch over across the project? (perhaps I'm misremembering > the previous threads about discourse, though - and we have already > pretty significantly fragmented on the chat-like medium between IRC > and Discord) Discourse is really more of an alternative to mailing lists, not to chat. For what it's worth, the alternatives we've looked at were: 1. Just use llvm-dev. This avoids...

...; --paulr > > > > *From:* llvm-dev <llvm-dev-bounces at lists.llvm.org> *On Behalf Of *Chandler > Carruth via llvm-dev > *Sent:* Monday, November 18, 2019 2:48 AM > *To:* llvm-dev <llvm-dev at lists.llvm.org> > *Subject:* [llvm-dev] RFC: Moving toward Discord and Discourse for LLVM's > discussions > > > > Hello everyone, > > > *Short version: *I've set up an LLVM Discord server for real time chat > (similar to IRC) and an LLVM Discourse server for forums (similar to email > lists): > https://discord.gg/xS7Z362 > https://llv...

...t 10:49 PM Daniel Chapiesky via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > ---------- Forwarded message --------- > From: Daniel Chapiesky <dchapiesky2 at gmail.com> > Date: Tue, Nov 19, 2019 at 1:48 AM > Subject: Re: [llvm-dev] RFC: Moving toward Discord and Discourse for > LLVM's discussions > To: Gaier, Bjoern <Bjoern.Gaier at horiba.com> > > > Bjoern said: > > " I found it pretty difficult to use Discord for that, because there was > one channel for asking questions. So I posted my question, but the next > reply was t...

...dev via cfe-dev <cfe-dev at lists.llvm.org> ezt írta (időpont: 2019. nov. 18., H, 16:08): > On Mon, Nov 18, 2019 at 4:10 PM Nico Weber via cfe-dev > <cfe-dev at lists.llvm.org> wrote: > > > > FWIW I'm a fan of using open-source stuff for open-source projects. > Discourse looks open source, but Discord doesn't as far as I can tell (?). > +1. I don't believe this decision was well thought-through. > The Discord's ToS, lack of open-source clients (if you can even call > the situation like that, > feels like ICQ/Skype all over again), centraliza...

...dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: ---------- Forwarded message --------- From: Daniel Chapiesky <dchapiesky2 at gmail.com<mailto:dchapiesky2 at gmail.com>> Date: Tue, Nov 19, 2019 at 1:48 AM Subject: Re: [llvm-dev] RFC: Moving toward Discord and Discourse for LLVM's discussions To: Gaier, Bjoern <Bjoern.Gaier at horiba.com<mailto:Bjoern.Gaier at horiba.com>> Bjoern said: " I found it pretty difficult to use Discord for that, because there was one channel for asking questions. So I posted my question, but the next reply was to...

On Jun 2, 2020, at 9:54 PM, Mehdi AMINI <joker.eph at gmail.com> wrote: > This was a mistake, fixed. > > I missed that this was changed, I was excited about a Discourse category for this! In particular the second point of the doc points at llvm-dev@ being a problem as the current forum for such discussions. > If Discourse is a no-go (?), then having a separate mailing-list would seem better to me: if only for archiving/searching/tracking such discussions (but D...

If I am not mistaken, there are two things that are becoming clear: 1. For email, nobody seems to be against Discourse as long as the mailing lists are still a supported way to participate. So this seems non-controversial. 2. For IRC, people seem to be happy with switching to a more modern solution, but Discord is largely disliked by a significant portion of respondents. So perhaps we can focus the discussion on &...

On Jun 2, 2020, at 1:57 PM, Kit Barton <kit.barton at gmail.com> wrote: > A few comments on the document: > 1. It seems the current document has settled on using threads on > llvm-dev, however there are still two reference to the LLVM Proposal > Reviews category on Discourse: last paragraph of Proposed Solution > section, first paragraph of the Review Discussion Template section. This was a mistake, fixed. > 2. I think it would be nice to try and keep the proposal document on > GitHub as up-to-date as possible as it evolves based on the discussion on &g...

...etter in general, tbh, but more companies allow them > on corporate networks. > > IRC has a ton of problems, too, but it's our default. We should only > move to a better tool, not a different tool. We want to bring in new > people without alienating old people, like me. > > Discourse seems to be OSS GPLv2, so we could host our own and apply > our own CoC / moderating if providers are not able to meet our needs. > I have real trouble using web BBSs (text ones over dialup were fine), > so I'd really appreciate an email/subscription mechanism. > > If we do selec...

On Wed, 20 Nov 2019 at 21:36, Whisperity via llvm-dev <llvm-dev at lists.llvm.org> wrote: > there will be the other 70+ gaming-related servers constantly nagging for attention... I very literally cannot cope with that at all. I can't "just filter" the noise on my own, so, if that becomes the norm, I'll be forced to pass.

...r of strangers participating, which to my mind would be the unfamiliar/difficult/intimidating part. FWIW, I agree with Paul. I can't recall an instance when I had difficulty using, or was intimidated by, email, for saying something on a mailing list. I am very unclear as to what problem this Discourse thing is supposed to solve. Being welcoming, or off-putting, has nothing to do with the form of the communications medium IMO. It has much more to do with the contents and style of the communication. -- Stefan Teleman stefan.teleman at gmail.com

Reply to Kiran Chandramohan: > You are welcome to participate, provide feedback and criticism to change the design as well as to contribute to the implementation. Thank you Kiran. > But the latest is what is there in the RFC in discourse. I have used this as reference for the response. > We did a study of a few constructs and clauses which was shared as mails to flang-dev and the RFC. As we make progress and before implementation, we will share further details. > “ Yes, parallel and flush would be the next two constructs t...

On Mon, Nov 18, 2019 at 2:49 PM Robinson, Paul via llvm-dev < 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

On Mon, Nov 18, 2019 at 11:55 AM David Chisnall via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 18/11/2019 16:39, Stefan Teleman via llvm-dev wrote: > > I can't recall an instance when I had difficulty using, or was > > intimidated by, email, for saying something on a mailing list. > > Subscribing to a mailing list, particularly one as high-traffic as >