Hi guys, I totally agree with you Jarek, people might be confused about where to ask questions: Stack Overflow (SO) or Stack Exchange (SE). I personally do not prefer SE over SO. In my view, both attend us in this matter.
I was thinking if when developers that look for community support find the Stack Exchange Airflow, they think about it as "a more official support" and give it more credit. And same for contributors: would they be more encouraged to contribute in this "SE Airflow"? (Maybe not, and this would be a yet--new media as you said). So the pros of SE over SO, in my view, is that it adds to the community brand, from a marketing point of view. But again, if we decide to encourage questions in SO and increase our activity as a community in answering regular questions, making SO our official FAQs/Forum place, this will be enough too! About the communication channels we have, I see the following as a good (and natural) approach: - Github Discussions: keep in Github only discussions over PRs and Issues. This is the best place for that, once the conversation is about code development and evolution. - Github Issues: conversations about bugs only (naturally they will be asked in stack overflow at some point, but this is the place where we track it) - Slack: keep all the diverse and general community topics (but no FAQ or code doubts, they should be asked in SO/SE, we can use a Slack bot to help in this awareness until people naturally understand how things flow) - Stack Overflow: all sort of questions and doubts If we agree about SO, I think we should create this movement of questions from Slack to SO then. This definitely will help the Airflow community to help itself! Count on me to help with that. Bests, *Lucas Fonseca* Data Engineer [image: photo] On Fri, May 21, 2021 at 5: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. >> > -- *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.
