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/> >>> >>>
