Hi, I write here as an end user, which has subscribed to ask his first questions on airflow. I agree that slack is not the best place to keep trace of the old posts and there's no reason to pay to have something publicly available. But, I've always privileged the mailing lists instead of StackOverflow to have direct contact with the developers or power users themselves. And frankly, when I see some of my colleagues that instantly post on StackOverflow instead of even trying to look for an answer before, I don't feel like I'm going to change my mind.
regards, Flo On Mon, May 27, 2019 at 2:38 PM Jarek Potiuk <[email protected]> wrote: > Yep. Agree with Szymon. > > Stack Overflow is also good as it is publicly searchable. And there are > 2300+ question about Airflow already there :). Probably we should encourage > users to have longer discussions at the user@ list and ask questions they > would normally do on slack using StackOverflow. > > J. > > On Mon, May 27, 2019 at 9:29 AM Szymon Przedwojski < > [email protected]> wrote: > > > I'd also lean in favour of encouraging users to post their questions on > > StackOverflow, and us being more active there in terms of answering > those. > > It's the de-facto standard QA forum for our industry, most > > programmers/people in IT are familiar with it and many use it daily. So > to > > me it seems best if they were able to find answers to questions on using > > Airflow there, and not in Slack nor even in search-engine-indexed devlist > > threads. > > > > *Szymon Przedwojski* > > Polidea | Software Engineer > > > > M: +48 500 330 790 > > > > > > On Sun, 26 May 2019 at 11:06, airflowuser > > <[email protected]> wrote: > > > > > In most of the projects I see the tech/support questions are directed > to > > > stackoverflow. In general many consider popularity of project by how > many > > > answers are there in stackoverflow. > > > > > > users/dev list & Jira should be for something that needs discussions. > Not > > > for questions like: How to use X. > > > > > > I hope that contributes and committers will participate more on > > > stackoverflow questions and encourage users to ask questions there. > > > > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > > On Sunday, May 26, 2019 12:00 PM, Jarek Potiuk < > [email protected] > > > > > > wrote: > > > > > > > Yeah but: > > > > > > > > - those are not indexed by search engines > > > > - we have no paid slack, only last 10k are not indexed in free > > version. > > > > - unlike the devlist archives which are available for free via > > http:// > > > , > > > > slack is proprietary/not open standard - I don't think it is > really > > > in-line > > > > with ASF open approach to have commercial entities controlling > > > access to > > > > the open data. > > > > > > > > J. > > > > > > > > On Sat, May 25, 2019 at 10:32 PM Austin Bennett > > > [email protected] > > > > > > > > > > > > wrote: > > > > > > > > > Slack has a search capability, which I've used to find "old' > issues. > > I > > > did > > > > > loose track of whether airflow's slack maintains history > > persistently. > > > If > > > > > it doesn't do I remember that the ASFs overall does (which airflow > > > could > > > > > benefit from/opt-into, if desired)? > > > > > On Sat, May 25, 2019 at 3:16 AM Jarek Potiuk > > [email protected] > > > > > wrote: > > > > > > > > > > > I'd go even further and remove troubleshooting altogether and > leave > > > it > > > > > > for > > > > > > announcements, personal discussions, user groups, asking for PRs > to > > > be > > > > > > reviewed - anything that has no "persistent" value. > > > > > > See the separate discussion about the user@ devlist: > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/9cf5a633cac0eb0652eef88dee82f567d57c39b302a8e9f02b016d85@ > > > <dev.airflow.apache.org> > > > > > > > > > > > I think we should discourage users to ask questions in slack and > > > > > > encourage > > > > > > to move to the userlist, but to do it on the userlist instead. > Main > > > > > > reason > > > > > > is simply because the information in userlist is publicly > > searchable > > > and > > > > > > you can find answers to the questions you want much easier if it > > has > > > > > > already been answered. Questions/answers in slack are lost very > > > quickly. > > > > > > J. > > > > > > On Sat, May 25, 2019 at 1:34 AM Teresa Martyny < > > > > > > [email protected]> wrote: > > > > > > > > > > > > > Thanks for breaking this out Sergio! > > > > > > > What is the current process for maintaining/moderating existing > > > > > > > channels? > > > > > > > > > > > > > How would that change with this infrastructure change? > > > > > > > Teresa Martyny > > > > > > > pronouns: she, her, hers > > > > > > > Software Engineer | Data Team Lead | Omada Health > > > > > > > https://www.omadahealth.com/ > > > > > > > 500 Sansome St #200, SF, CA 94111 > > > > > > > What is Omada? https://vimeo.com/203386025 > > > > > > > On Fri, May 24, 2019 at 3:17 PM Sergio Kef [email protected] > > > > > > > wrote: > > > > > > > > > > > > > > Slack is a channel that could support a lot more our > community. > > > > > > > > I've noticed that as a developer I get a bit overwhelmed by > the > > > > > > > > amount > > > > > > > > of > > > > > > > > > > > > > > messages there, every time I join. This is a "good" problem, > > > shows > > > > > > > > engaging > > > > > > > > community. What we miss though is the opportunity to catch up > > > quickly > > > > > > > > what's going on, if we missed some days/weeks or even if it's > > our > > > > > > > > first > > > > > > > > > > > > > > time there. > > > > > > > > So I propose a small restructure of the channels to make it > > > easier > > > > > > > > follow > > > > > > > > > > > > > > > and catch up. > > > > > > > > > > > > > > > > - announcements (as is) > > > > > > > > - new releases > > > > > > > > - community announcements > > > > > > > > - general > > > > > > > > - events (meetings, webinars, conferences, etc) > > > > > > > > - material (tutorials, blog posts, etc) > > > > > > > > - contribute > > > > > > > > - contributors' questions (getting started, ci, > testing, > > > etc) > > > > > > > > - future ideas & more (eg some premature AIPs) > > > > > > > > - call for help on bugs/fixes/PRs > > > > > > > > - how-to (similar to current troubleshooting) > > > > > > > > - user issues > > > > > > > > - guidance on ETLs > > > > > > > > > > > > > > > > Of course the list is open for suggestions. > > > > > > > > Let me know what you think. > > > > > > > > Sergio. > > > > > > > > > > > > > > -- > > > > > > > This email may contain material that is confidential and/or > > > privileged > > > > > > > for > > > > > > > the sole use of the intended recipient. Any review, reliance, > or > > > > > > > distribution by others or forwarding without express permission > > is > > > > > > > strictly > > > > > > > prohibited. If you are not the intended recipient, please > contact > > > the > > > > > > > sender and delete all copies. Also note that email is not an > > > > > > > appropriate > > > > > > > > > > > > > way to send protected health information to Omada Health > > employees. > > > > > > > Please > > > > > > > use your discretion when responding to this email. > > > > > > > > > > > > -- > > > > > > Jarek Potiuk > > > > > > Polidea https://www.polidea.com/ | Principal Software Engineer > > > > > > M: +48 660 796 129 <+48660796129> > > > > > > E: [email protected] > > > > > > > > -- > > > > > > > > Jarek Potiuk > > > > Polidea https://www.polidea.com/ | Principal Software Engineer > > > > > > > > M: +48 660 796 129 <+48660796129> > > > > E: [email protected] > > > > > > > > > > > > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48660796129> > E: [email protected] >
