Jarek I'm glad you suggested connecting it to a slack channel - I think that automating the integration into we currently have will be crucial to gaining adoption. My only nit would be to spell out #stackoverflow-questions in the channel name just so that it's immediately obvious what it is at first glance.
On Wed, Nov 11, 2020 at 12:10 PM Ry Walker <[email protected]> wrote: > i like all those ideas, Jarek > > On Wed, Nov 11, 2020 at 2:39 PM Jarek Potiuk <[email protected]> > wrote: > >> I read the docs (thanks Martijn!). Looks like SO would be great if we use >> more of it. >> >> We are promoting it very lightly, though. At our >> https://airflow.apache.org/community/ page we have "Stack Overflow" lin >> kas one of the options (which is good, according to those SO guidelines). >> But I think we have one place which could be improved: >> >> I think we could do a few things to utilize it a bit more: >> >> 1) Change links on the "new issue" page. >> >> When we run "new issue" we see: >> https://github.com/apache/airflow/issues/new/choose - "Ask a question of >> get support leads to the https://github.com/apache/airflow/discussions >> page. It's light in traffic, and we might try to use it more, but I think >> GitHub discussions should be more for ... discussions, not Q&A (not yet at >> least). SO has so much more content, rating, traffic etc. >> >> Why don't we split into: >> >> "Discuss an idea" -> https://github.com/apache/airflow/discussions >> "Ask a question or get support" -> >> https://stackoverflow.com/questions/tagged/airflow >> >> 2) Linking SO with our slack? >> >> And why don't we connect the " >> https://stackoverflow.com/questions/tagged/airflow"; RSS to a new >> "#so-questions" in our Slack ? I think we are not often looking at SO, but >> there is a substantial (but not overwhelming) traffic there - I see 10 >> questions today, 46 this week for example. And there are many unanswered >> questions there. I think just seeing those in slack might drag more >> attention from the commiters and some active community members. >> >> WDYT everyone ? >> >> J. >> >> >> On Thu, Nov 5, 2020 at 2:07 PM Martijn Pieters <[email protected]> >> wrote: >> >>> On 2020/11/05 08:37:28, Jarek Potiuk <[email protected]> wrote: >>> > I was wondering if we should do something about it? Maybe we should >>> promote >>> > more Stack Overflow? We already have a link about it on our website in >>> "Ask >>> > the questions' chapter. But Stack Overflow answers and links very >>> rarely >>> > come up in the discussions in Slack for example. I was just wondering >>> if >>> > there is anything we can do to make it more "promoted"? >>> > >>> > Maybe someone can have some ideas on how to make it more "visible"? >>> >>> Hi! Quick intro: I've been contributing to Airflow recently, especially >>> to the 2.0.0 release currently in alpha. But I'm also one of the community >>> elected moderators on Stack Overflow as well as a frequent Python >>> contributor on that site. >>> >>> Stack Overflow can be a temperamental place, but it is _is_ a great >>> resource for people that know how to formulate good, focused questions on >>> programming-related subjects. If there were a few people from the Airflow >>> project actively answering questions there, then the resulting content can >>> be of great help to anyone else with similar problems. >>> >>> There are a few FAQs on meta.stackoverflow.com which might be >>> applicable here, I strongly recommend people take a look at these; they >>> cover SO from the perspective both of a project team (OSS or commercial) >>> and from the perspective of the question askers: >>> >>> - >>> https://meta.stackoverflow.com/questions/326374/how-can-i-use-stack-overflow-to-support-our-developer-community >>> - >>> https://meta.stackoverflow.com/questions/255745/why-cant-i-ask-customer-service-related-questions >>> - >>> https://meta.stackoverflow.com/questions/253849/is-it-acceptable-to-use-stack-overflow-as-a-qa-for-a-specific-product >>> >>> Some of that advice is more aimed at tech companies, but it's still >>> helpful to keep in mind that not everyone active in content curation (e.g. >>> most of the users with a bit of reputation) will view questions without >>> clear context on the problem at hand, in the same light. >>> >>> At any rate, to promote Stack Overflow as a resource, linking it from a >>> 'further resources' page in the documentation would be a good starting >>> point. Just make sure it is not implied that Stack Overflow is a general >>> support channel for the project. :-) >>> >>> -- >>> Martijn Pieters >>> https://stackoverflow.com/users/100297/martijn-pieters | >>> https://www.zopatista.com >>> >>> >> >> -- >> >> Jarek Potiuk >> Polidea <https://www.polidea.com/> | Principal Software Engineer >> >> M: +48 660 796 129 <+48660796129> >> [image: Polidea] <https://www.polidea.com/> >> >> -- Leah Cole (she/her) | Developer Programs Engineer | [email protected] | (925) 257-2112 *I'm working weird hours during this pandemic and am sometimes a bit slower to respond to PRs/CLs than normal. Please feel free to send me a gentle ping for a status update if my slowness is blocking you and I'll do my best to give you an ETA. *
