Yes - I think we are getting to the point now where we will want to do this. We've avoided it a bit so far as many/most topics are fairly cross-cutting. For example, most of the discussions in #CJ909TL6P and #CDE799L1M have in practice not really been unique to those languages.
Also - in practice questions have been more likely to be answered in #C84L4E3N1 than in those more specific channels just because more folks are reading #C84L4E3N1.
That said - I expect we should go ahead and do this to spread out the traffic a bit.
Feedback on what new channels would be useful - is this the right set to add right now?
- #aws
- #azure
- #gcp
- #kubernetes
c
colossal-room-15708
06/20/2019, 12:36 AM
I get what you're saying, and tend to agree that most people are in #C84L4E3N1 , but it's also very un-slacky to post in #C84L4E3N1 😉
I think those channels that you mentioned would be a great start.
colossal-room-15708
06/20/2019, 12:37 AM
In other slacks I've seen #C84L4E3N1 be renamed to #CB36DSVSA and a new "general" was created.
That way people join into #CB36DSVSA and then go and find the "correct" channel to ask a question.
w
white-balloon-205
06/20/2019, 12:42 AM
I'll admit I've seen a wide mix of styles here - but have generally seen Slacks with a vibrant #C84L4E3N1 normally invite less fragmentation early on. Certainly this doesn't scale indefinitely, and we'll need to start breaking off more channels. But I'd hate to silo off parts of the Pulumi community too quickly into separate Slack bubbles.