This message was deleted.

Good proposal! I agree 100%. We have tried to switch to this type of policy a few times in the past. We just have to start once again and have better communication about the policy and the reasoning. I wonder if @tison and @bala rao could help making this happen?

Pulsar enables Discussions in the main repo: https://github.com/apache/pulsar/discussions For redirecting discussions, IMO Slack workspace is an instant messaging platform for short conversations, and when the question answering becomes complicated, we can move the context to the Discussions forum. Or duplicate valuable discussion on the forum afterwards.

Probably it makes sense to change the general channel description to something like it:

Sounds reasonable. cc @merlimat

IMO Slack workspace is an instant messaging platform for short conversations, and when the question answering becomes complicated, we can move the context to the Discussions forum.

Most of the questions I see here are quite complicated.

This is the reason way in the ASF we promote discussions on the mailing lists 😀 Even if they are old style ML have all you need for community interaction: • they are asynchronous (you can take your time to answer, it works well with different timezones and with people that only occasionally contribute) • they are archived • they still support a “conversational” style

FWIW Discussions are delivered to commit@ mailing list.

(we should move them to dev@ because really nobody cares about commit@ apart from PMC members)

There’s a concern about duplicate notifications. I remember we first send them to dev@ and later change it. There should be some discussions. … while for the duplicate notification issues I can set up some filters to workaround. It can be a separate topic, though.

This is the reason way in the ASF we promote discussions on the mailing lists 😀

The problem with mailing lists is it’s too hardcore for the average user. I say about Pulsar users, not about contributors.

sure

Thank you @Kiryl Valkovich for bringing this up. I hope we finally get this addressed... It's been floating around for at least the last 2 years.

I don’t see channel description at all.

this is what I see:

Yes, you are right.

Thanks for updating!

Thanks for the initiative @Kiryl Valkovich. Yap, I do agree with your points.

Dear ChatGPT, is there a way to automate the posting of Slack questions to Stack Overflow and/or GitHub discussions? Publish once, write 3 replicas sort of thing? 🤔

@David K what do you think about the following workflow: • The user asks a new question in Slack. • You click the three dots button on his message -> “Convert to a GitHub discussion”. • The bot creates a new GitHub discussion in the “Q&A” category with the original message’s content. • The bot converts the original message to a thread and posts a message like:

In order to keep history and make your question searchable by other Apache Pulsar users, it has been converted to a GitHub discussion.

Further conversation is available by this link: https://github.com/apache/pulsar/discussions/18766.

• You answer the question on GitHub. How it may work: https://api.slack.com/best-practices/blueprints/actions-and-dialogs I can try to implement it makes any sense for you.

This sounds reasonable to me. @Enrico Olivelli @Lari Hotari @Chris Latimer let us know if you have any additional thoughts on this approach sent by @Kiryl Valkovich

hey folks, this is exactly the kind of discussions that should run on the dev@ mailing list. In all the Apache projects discussions and especially decisions happen only on the mailing lists this is the wrong place. slack is meant for quick chats and the community isn’t involved, only people following this thread will see it

It seems that there should be a flow chart on how to pick the right place.

Enrico, can you start the discussion in the dev mailing list?

it would be great if @Kiryl Valkovich could kickstart it 😉

@tison I published a PR about adding GitHub discussions to the community page. https://github.com/apache/pulsar-site/pull/414