[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Retiring Airflow Gitter?

I'm not a fan of slack for open source work - it's a walled garden, signing up is a hurdle (where you have to use a work around of a heroku app), not to mention that the client is just so memory hungry!

I'm just a curmudgeon who still likes IRC mainly. So long as I can install <> I won't object ;)

(I am not a fan of Gitter either, but I am constantly logged in via their IRC gateway. I'm usually the only PPMC responding in there, Bolke pops up from time-to-time too)


> On 1 Sep 2018, at 02:40, Sid Anand <sanand@xxxxxxxxxx> wrote:
> Great feedback. There is an overwhelming interest in moving Gitter to
> Slack. Just curious: for the folks who set up Slack for other Apache
> projects, did you go via an Apache Infra ticket?
> -s
> On Fri, Aug 31, 2018 at 4:32 PM James Meickle
> <jmeickle@xxxxxxxxxxxxxx.invalid> wrote:
>> I am in the gitter chat most work days and there's always activity.
>> I would be fine with switching to permanent retention slack for
>> searchability but don't see the point of switching without that feature.
>> On Fri, Aug 31, 2018, 12:59 Sid Anand <sanand@xxxxxxxxxx> 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