airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Gregory <...@astronomer.io>
Subject Re: Retiring Airflow Gitter?
Date Fri, 31 Aug 2018 18:27:54 GMT
+1 to Slack over Gitter

On Fri, Aug 31, 2018 at 12:18 PM Daniel Imberman <daniel.imberman@gmail.com>
wrote:

> I'm with Adam. Slack has been significantly more useful for the k8s
> community. It's now the case that all k8s executor questions are being
> fielded on kubernetes.slack.com. Would be great to have an airflow slack
> instead.
>
> On Fri, Aug 31, 2018 at 10:54 AM Trent Robbins <robbintt@gmail.com> wrote:
>
> > I'm in favor of (yet another) slack. It will probably improve community
> > growth and development, not just support searchable answers. I think
> > nonprofits have an easy time getting permanent message retention for free
> > but that would be an issue if that was not possible for Airflow. The
> > default free account does not have permanent message retention (last I
> > checked).
> >
> > Trent
> >
> > On Fri, Aug 31, 2018 at 10:32 Daniel Cohen <daniel.cohen@cloudinary.com>
> > wrote:
> >
> > > As a newcommer I find gitter lacking it's hard to follow or find
> things.
> > +1
> > > slack
> > >
> > > On Fri, Aug 31, 2018, 20:11 Adam Boscarino
> > > <aboscarino@digitalocean.com.invalid> wrote:
> > >
> > > > The search functionality on Gitter is sorely lacking, which limits
> it's
> > > > usefulness for me. This will probably be unpopular, but I get more
> out
> > of
> > > > the communities that use Slack (go, kubernetes, etc.) because the
> > search
> > > is
> > > > so much better.
> > > >
> > > > On Fri, Aug 31, 2018 at 1:05 PM Andrew Harmon <
> andrewhharmon@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > I'm new to Airlfow and I personally get a lot of use out of
> Gitter. I
> > > > find
> > > > > there's almost always someone in there that can help answer a
> > queation.
> > > > >
> > > > > On Fri, Aug 31, 2018 at 12:58 PM Sid Anand <sanand@apache.org>
> > wrote:
> > > > >
> > > > > > For a while now, we have had an Airflow Gitter account. Though
> this
> > > > > seemed
> > > > > > like a good idea initially, I'd like to hear from the community
> if
> > > > anyone
> > > > > > gets value of out it. I don't believe any of the committers
spend
> > any
> > > > > time
> > > > > > on Gitter.
> > > > > >
> > > > > > Early on, the initial committers tried to be available on it,
but
> > > soon
> > > > > > found it impossible to be available on all the timezones in
which
> > we
> > > > had
> > > > > > users. Furthermore, Gitter notoriously sucks at making previously
> > > > > answered
> > > > > > questions discoverable. Also, the single-threaded nature of
> Gitter
> > > > > > essentially makes it confusing to debug/discuss more than on
> topic
> > > at a
> > > > > > time.
> > > > > >
> > > > > > The community seems to be humming along by relying on the Apache
> > > > mailing
> > > > > > lists, which don't suffer the downside listed above. Hence,
as
> > > newbies
> > > > > join
> > > > > > Apache Airflow, they likely hop onto Gitter. Are they getting
> value
> > > > from
> > > > > > it? If not, perhaps we are doing them a disservice and should
> > > consider
> > > > > just
> > > > > > deleting it.
> > > > > >
> > > > > > Thoughts welcome.
> > > > > > -s
> > > > > >
> > > > > --
> > > > > Andrew Harmon
> > > > > (202) 615-6433
> > > > >
> > > >
> > > >
> > > > --
> > > > Adam Boscarino
> > > > Senior Data Engineer
> > > >
> > > > aboscarino@digitalocean.com
> > > > ------------------------------
> > > > We're Hiring! <https://www.digitalocean.com/company/careers/> |
> > > > @digitalocean <https://twitter.com/digitalocean>
> > > >
> > >
> > --
> > (Sent from cellphone)
> >
>


-- 

[image: Astronomer Logo] <https://www.astronomer.io/>

*Ben Gregory*
Data Engineer

Mobile: +1-615-483-3653 • Online: astronomer.io <https://www.astronomer.io/>

Download our new ebook. <http://marketing.astronomer.io/guide/> From Volume
to Value - A Guide to Data Engineering.

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