+1. I think Airflow user's community is quite strong so this might be rather useful. Also there are lots of discussions on slack channels - #troubleshooting for example - which is not great. Slack messages are not publicly indexed/searchable so it is difficult to build a public troubleshooting knowledge base this way.
Having such discussions in dev list would be really helpful for others. J. On Fri, May 24, 2019 at 8:53 AM Bolke de Bruin <[email protected]> wrote: > +1, although I do see that quite a few ‘user’ lists are a bit quiet. > > Verstuurd vanaf mijn iPad > > > Op 24 mei 2019 om 08:09 heeft Kamil Breguła <[email protected]> > het volgende geschreven: > > > > +1 > > > >> On Fri, May 24, 2019 at 7:57 AM Jakob Homan <[email protected]> wrote: > >> > >> The dev list is quite crowded, which several members of the community > >> have noted, and it's getting hard to separate the technical direction > >> questions from the general user questions. > >> > >> Most Top-Level Projects maintain a user@ list as well. Should we > create > >> one? > >> > >> If there's a positive response, the process is a simple form that the > >> project VP or an ASF member can submit. > >> > > > > > > -- > > > > Kamil Breguła > > Polidea <https://www.polidea.com/> | Software Engineer > > > > M: +48 505 458 451 <+48505458451> > > E: [email protected] > > [image: Polidea] <https://www.polidea.com/> > > > > We create human & business stories through technology. > > Check out our projects! <https://www.polidea.com/our-work> > > [image: Github] <https://github.com/Polidea> [image: Facebook] > > <https://www.facebook.com/Polidea.Software> [image: Twitter] > > <https://twitter.com/polidea> [image: Linkedin] > > <https://www.linkedin.com/company/polidea> [image: Instagram] > > <https://instagram.com/polidea> [image: Behance] > > <https://www.behance.net/polidea> > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> E: [email protected]
