Yeah. I am also not sure what advantages it might bring? I personally think that Stack Exchange site is only successful if this is "huge" enough and general enough. There are quite a few Stack Exchange "ghost towns" out there. I think narrowing it down per product is just going a bit too far. And people might be confused where to ask questions (General Stack Overflow? Airflow Stack Exchange?).
What we could do instead is to increase our activity as a community in answering regular questions from Stack Overflow. I plan to pay more attention to it as well and we already have those questions automatically in the #stackoverflow Slack channel of ours: https://app.slack.com/client/TCQ18L22Z/C01EUHSTD2R Maybe we can think of somehow improving that rather than adding yet-new "media". WDYT? On Fri, May 21, 2021 at 10:10 PM Kaxil Naik <[email protected]> wrote: > Hi Lucas, > > Thanks for bringing this up. What advantages will Stack Exchange give us > above and beyond Stack Overflow? > > My only concern is we have an increasing number of things we as a > community will be managing (not saying we shouldn't, but just pick and > choose which ones): > > > - Github Discussions > - Slack > - Github Issues > - Stack Overflow > - Medium & Dev.to Blogs > > Regards, > Kaxil > > On Fri, May 21, 2021 at 8:07 PM Lucas Fonseca > <[email protected]> wrote: > >> Hello guys. >> I have a suggestion for the community support organization. >> I was talking with Tomek Urbaszek and he asked me to send it to devlist. >> >> *Problem:* >> Today I see the community is not well supported in terms of FAQs or >> problems solving. >> New people get frustrated not finding answers to their basic questions in >> Slack. >> Maaany person has doubts and posts them here in the Slack channels. But >> they don't get answers, because: >> - it isn't the best channel to get help >> - and many doubts are pretty basic (and could be answered with >> documentation or with some other question already answered) >> >> And more experienced users also struggle to find community support >> because their questions got lost between so many spammed questions in the >> Slack community. Also, we lose track of the questions in the channels and >> we don't keep history. >> >> On other hand, we have the general Stack Overflow that helps a lot in >> that sense but is not so "official" as the Airflow channel for such a thing. >> The community could develop/grow much faster if had some better approach >> for this. >> >> *Suggestion:* >> We could create a community for Airflow in Stack Exchange. >> >> If we have a community dedicated to Airflow in Stack Exchange, all the >> doubts could be better indexed, we would avoid redundant questions and have >> a community looking at the quality of the questions/answers. >> >> This would be pretty helpful to the Airflow Community and help us to grow >> faster. >> Bonus: Also, the Slack channels would be more objectives and productive. >> >> >> *Related conversations in devlist (sorry I did not know how to continue >> the conversation in that threads):* >> - Thread 1 >> <https://lists.apache.org/thread.html/r5d03a9afc609bcc8eb574a85826820cdd2c46f4075d0c3e3c7c7729d%40%3Cdev.airflow.apache.org%3E> >> - Thread 2 >> <https://lists.apache.org/thread.html/rf2165ed05f709787e8961c8fce4e53a81c1af5d01ac97575a6cb5efe%40%3Cdev.airflow.apache.org%3E> >> - Thread 3 >> <https://lists.apache.org/thread.html/r0cc6cda29984da9fc6f1a8c135a608cf049c3f1bdcdb3a659a4e94df%40%3Cdev.airflow.apache.org%3E> >> >> *Bests,* >> *Lucas Fonseca* >> Data Engineer >> >> [image: photo] >> >> *Atenção*: este email contém informação confidencial. Se você o receber >> por engano, por favor, informe-nos e apague-o; não copie ou divulgue seu >> conteúdo. >> *Warning*: this email contains confidential information. If you have >> received it by mistake, please let us know and delete it; do not copy or >> disclose its contents. >> > -- +48 660 796 129
