hmm, so one has to add one mute for every Discourse category?
Yes. That's 3 or 4 mutes top. My idea was that if we were using a dedicated stream instead, then fewer people would learn about it, and since the Discourse categories map pretty well to Zulip, it made sense to dispatch the posts like that.
Additionally, note that this is only about new topics (maybe I should change the topic in fact to make that clearer), so it won't create much noise.
Indeed, I do not think one should mute zulip Discourse topic, it does not send automated messages for each actions like github integration might do...
Sorry to be a bit borderline here, but what is really the point of keeping 2 channels? Maybe the recent comment "discourse is dead" is a bit exaggerating it, but last time I looked a discourse it did not seem much alive. Here I see a huge load of message per day, and I'm only following a few streams... to conclude, mail integration for dinosaurs like me is really great, a few messages and always relevant. I love it.
I think that we've already answered why we felt the two didn't cover the same use cases even if they partly overlap?
And the integration between the two might reinforce Discourse.
But feel free to elaborate on why you'd like to not keep the 2 channels.
There reasons are still the same, for both keeping the two or not. I'm just saying that a decision made before having even tried Zulip may be reconsidered after. Before trying you don't know it it is going to fly or not, so the it is all hypothetical. I would not ask the question if I was seeing only a few messages per day by the usual know people.
I've nothing against keeping Discourse, I'm just asking if it still perceived as relevant.
OK, I guess we'll have to wait a bit longer to really gauge how the two can cohabitate or not.
can we at least agree that it would be terrible to throw up a login requirement for majority of readers just to get access to some code examples and resources?
Last updated: Jun 10 2023 at 06:31 UTC