airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Austin Bennett <whatwouldausti...@gmail.com>
Subject Re: [DISCUSS] Time for a user@ list?
Date Sat, 25 May 2019 20:29:32 GMT
+1, these are useful separations.

On Fri, May 24, 2019 at 10:25 PM Prajwal Tuladhar <praj@infynyxx.com> wrote:

> Makes sense.
>
> +1 for this.
>
> On Fri, May 24, 2019 at 10:06 PM Jason Rich <jasonrich85@icloud.com
> .invalid>
> wrote:
>
> > +1
> >
> > Quick question, could we also push user@ threads to a specified Slack
> > channel?
> >
> > Cheers,
> > Jason
> >
> > > On May 24, 2019, at 8:23 AM, Teresa Martyny <
> > teresa.martyny@omadahealth.com> wrote:
> > >
> > > Jared makes a good point about Slack. It seems like the Slack group
> > > channels are mostly troubleshooting questions in spite of their names
> > > seeming to indicate they were meant for other intentions. Having
> > > troubleshooting questions folks have asked in the past more publicly
> > > searchable would be very helpful to allow teams to more quickly iterate
> > > when they run into problems that have already been solved.
> > >
> > > T
> > >
> > > On Fri, May 24, 2019, 12:12 AM Jarek Potiuk <Jarek.Potiuk@polidea.com>
> > > wrote:
> > >
> > >> +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 <bdbruin@gmail.com>
> > 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 <
> > kamil.bregula@polidea.com
> > >>>
> > >>> het volgende geschreven:
> > >>>>
> > >>>> +1
> > >>>>
> > >>>>> On Fri, May 24, 2019 at 7:57 AM Jakob Homan <jghoman@gmail.com>
> > >> 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: kamil.bregula@polidea.com
> > >>>> [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: jarek.potiuk@polidea.com
> > >>
> > >
> > > --
> > > 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.
> >
> > --
> Cheers, Praj
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message