What about such wording? --- Your question was moved here: https://github.com/apache/pulsar/discussions/123
Please consider asking new questions here: * At StackOverflow using apache-pulsar tag. * In the Q&A category at GitHub Discussions. * Apache Pulsar User Mailing List. It will make it searchable by others. Also, this way we can collect a knowledge base outside of Slack over time. I can’t see how the words “please consider” force the user to do something. Users who have an account on StackOverflow or GitHub can use these platforms next time. Others can send their question via the mailing list. From: Dave Fisher <wave4d...@comcast.net> Date: Friday, February 17, 2023 at 9:28 PM To: dev@pulsar.apache.org <dev@pulsar.apache.org> Subject: Re: Force redirect questions from Slack to GitHub Discussions or StackOverflow? My concern is that users should have a choice on where to post their questions. They might have concerns about GitHub’s terms and conditions. We can pin a message to slack pointing to GitHub discussions and stackoverflow. Best, Dave Sent from my iPhone > On Feb 17, 2023, at 9:22 AM, Kiryl Valkovich <kiryl_valkovich@teal.tools> > wrote: > > I’m the owner of this account. > The goal is to test drive duplicating Slack questions to the GitHub > discussions. > With the current level of activity in Slack it’s not so hard to do it > manually. > > I’m in CET now. I can share the account credentials with people who can post > questions to GitHub Discussions on behalf of this account in other time zones. > Or I can do it once a day. > > If someone doesn’t find it useful or has ideas on how to do it in a better > way, just say it directly. > > From: Enrico Olivelli <eolive...@gmail.com> > Date: Friday, February 17, 2023 at 3:43 PM > To: dev@pulsar.apache.org <dev@pulsar.apache.org> > Subject: Re: Force redirect questions from Slack to GitHub Discussions or > StackOverflow? > Hello, > I see that some "Pulsar Community Bot" appeared in Slack > > it is connected to this email address "pulsar.community....@gmail.com" > > While I find this thing "amazing"....I wonder if I missed something, > who is the owner of this "bot" ? > > > Enrico > >> Il giorno gio 16 feb 2023 alle ore 16:03 Kiryl Valkovich >> <kiryl_valkovich@teal.tools> ha scritto: >> >> Played with Slack and StackOverflow APIs a bit. >> >> The Slack API works as expected. After clicking the message button, it sends >> a message descriptor to my app where I can do anything with its content. >> >> It’s possible to post messages via the StackOverflow API, but it’s unlikely >> that any Slack message can be converted to a StackOverflow question. >> >> I encountered several types of validation errors: >> >> - This question body does not meet our quality standards. Please >> make sure that it completely describes your problem - including what you >> have already tried - and is written using proper grammar. >> >> * Something similar to “This message looks like a duplicate of another >> message”. >> >> I believe, GitHub Discussions don’t have such kind of “quality standards” >> validation. >> >> From: Kiryl Valkovich <kiryl_valkovich@teal.tools> >> Date: Thursday, February 16, 2023 at 1:33 PM >> To: dev@pulsar.apache.org <dev@pulsar.apache.org> >> Subject: Re: Force redirect questions from Slack to GitHub Discussions or >> StackOverflow? >> If there are no hidden obstacles, we can implement it. >> StackOverflow supports question creation using REST API: >> https://api.stackexchange.com/docs/create-question >> >> From: Zike Yang <z...@apache.org> >> Date: Thursday, February 16, 2023 at 11:41 AM >> To: dev@pulsar.apache.org <dev@pulsar.apache.org> >> Subject: Re: Force redirect questions from Slack to GitHub Discussions or >> StackOverflow? >> +1, That sounds great to me. >> >>> 2. You click the three dots button on his message -> “Convert to a GitHub >>> discussion”. >> >> Is it a similar workflow for converting to a StackOverflow question? >> >> BR, >> Zike Yang >> >>> On Thu, Feb 16, 2023 at 12:14 PM <mattisonc...@gmail.com> wrote: >>> >>> +1 >>> >>> Since web pages are more easily and public. >>> >>> Best >>> Mattison >>> On Feb 16, 2023, 07:58 +0800, Christophe Bornet <bornet.ch...@gmail.com>, >>> wrote: >>>> +100 >>>> Also note that for good or bad reasons, the number of questions on >>>> StaOverflow is often used as a metric for the popularity of a project. >>>> >>>> Le mer. 15 févr. 2023 à 13:12, Kiryl Valkovich <kiryl_valkovich@teal.tools> >>>> a écrit : >>>> >>>>> Hi everyone! Enrico Olivelli asked me to repost it to the mailing list. >>>>> >>>>> --- Me >>>>> I’m very worried that good answers from David Kjerrumgaard and others >>>>> won’t be googleable because it’s in Slack. To make any search you need to >>>>> pay a monthly subscription. >>>>> >>>>> In my opinion, it would be wiser to make StackOverflow, Discuss, or GitHub >>>>> discussions a place for questions. And strictly redirect people who ask >>>>> any >>>>> question in Slack to the right place. >>>>> In GitHub discussions, you also can manage categories, as well as you can >>>>> manage channels in Slack. >>>>> >>>>> Subscription to a specific category is coming soon. >>>>> https://github.com/community/community/discussions/3951#discussioncomment-3879939 >>>>> The most important that it’s searchable. >>>>> >>>>> Examples: >>>>> https://github.com/community/community/discussions >>>>> https://github.com/apache/superset/discussions >>>>> >>>>> --- Later me to David Kjerrumgaard >>>>> What do you think about the following workflow: >>>>> 1. The user asks a new question in Slack. >>>>> 2. You click the three dots button on his message -> “Convert to a GitHub >>>>> discussion”. >>>>> 3. The bot creates a new GitHub discussion in the “Q&A” category with the >>>>> original message’s content. >>>>> 4. 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. >>>>> 5. 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. (edited) >>>>> >>>>> Full original thread: >>>>> https://apache-pulsar.slack.com/archives/C5Z4T36F7/p1676449603034309 >>>>> >>>>>
