That's an interesting point. I think the reason is that committers are checking Github as often as Slack (or more). That doesn't have to be true about the rest of the community which probably does not use Github on a daily basis but may use Slack for company communication.
I think our goal in "migration" should be to create a knowledge base that is persistent, searchable and easy to discover. While I can see that using Github is not that natural for many, I think the gamification element (green contributions and answered questions) on Github may encourage people. On Wed, Dec 23, 2020 at 12:37 PM Elad Kalif <[email protected]> wrote: > I agree that Slack is very useful for small scope questions. > > I took a look at GitHub Discussions, Stackoverflow & Slack > In discussions I didn't find many questions that were answered by the > community - most of them were answered by committers. > On the other hand, Stackoverflow and Slack seems to have a higher > engagement of users helping each other. > > > On Wed, Dec 23, 2020 at 1:10 PM Tomasz Urbaszek <[email protected]> > wrote: > >> +1 for promoting discussions. I think having the Q&A and troubleshooting >> close to repo is even better than stackoverflow. >> >> Although I think we should more often use devlist, we should keep Slack >> for quick and ad hoc communication as Ash and Kamil mentioned. >> >> Tomek >> >> On Wed, Dec 23, 2020 at 10:11 AM Ash Berlin-Taylor <[email protected]> >> wrote: >> >>> I think we need to acknowledge that different people like solving >>> problems in different ways - personally I prefer more interactive solving >>> for example. >>> >>> Encouraging GitHub discussion is fine, but also there's some class of >>> issues where I find a more real-time approach preferable (easier to ask >>> clarifying questions, suggest extra debugging, quicker back and forth etc.) >>> >>> Not sure what I'm suggesting, other than slack still has a place for me. >>> >>> Ash >>> >>> On 23 December 2020 07:49:27 GMT, Deng Xiaodong <[email protected]> >>> wrote: >>>> >>>> My only question is whether some other channels should be treated the >>>> same way as well? For example, channel “#newbie-question” >>>> >>>> >>>> XD >>>> >>>> On Wed, Dec 23, 2020 at 08:28 Sumit Maheshwari <[email protected]> >>>> wrote: >>>> >>>>> Big +1 >>>>> >>>>> Another reason is that in Slack the history is very limited due to the >>>>> free plan. >>>>> >>>>> >>>>> On Wed, Dec 23, 2020 at 11:35 AM Jarek Potiuk < >>>>> [email protected]> wrote: >>>>> >>>>>> Hello everyone, >>>>>> >>>>>> I had a thought - should we start redirecting people and maybe even >>>>>> disable the #troubleshooting channel in our Slack? (including our >>>>>> "community" page and a note in #troubleshooting channel. >>>>>> >>>>>> I found Github Discussions vastly superior for all things >>>>>> troubleshooting. It is indexed by search engines, you can mark the answer >>>>>> as "answer", it's clearly threaded, it naturally fits into GitHub flow. >>>>>> You >>>>>> use the same markdown as for the rest of GitHub ... You can categorise >>>>>> discussions >>>>>> >>>>>> https://github.com/apache/airflow/discussions >>>>>> >>>>>> WDYT? >>>>>> >>>>>> J. >>>>>> >>>>> >>>>>> -- >>>>>> >>>>>> Jarek Potiuk >>>>>> Polidea <https://www.polidea.com/> | Principal Software Engineer >>>>>> >>>>>> M: +48 660 796 129 <+48660796129> >>>>>> [image: Polidea] <https://www.polidea.com/> >>>>>> >>>>>>
