Ah good to know.
Still, for me the biggest downsides against migrating is cost - we've got about
3-400 active users a week which would cost the ASF almost $28,000 a year. That
seems like a lot for chat history; and secondly the hassle of migrating
everyone to a new chat workspace - there are st
The ASF slack has two ways of auto-invites:
- For people with @apache.org emails, they can request an invitation
directly in the-asf.slack.com.
- For people without @apache.org, the ASF slack admins need to renew an
open invitation that anyone can use. Short link:
https://s.apache.o
I’m glad yarn wasn’t the only option - it would have meant I’d have never been
in a position to use Airflow! (Many of our workflows don’t touch EMR/Hadoop,
and running Celery is much more of a known element to a python developer than
configuring Yarn)
> On 11 Feb 2019, at 17:14, Maxime Beauchem
Automatic invitations only work if you have an @apache.org email address I
think, so that is going to be of use to almost no one.
> On 12 Feb 2019, at 08:03, Kaxil Naik wrote:
>
> Sounds good actually. How's does automatic invitation works ?
>
> On Tue, Feb 12, 2019, 01:09 Aizhamal Nurmamat
Sounds good actually. How's does automatic invitation works ?
On Tue, Feb 12, 2019, 01:09 Aizhamal Nurmamat kyzy
wrote:
> Hi Kaxil,
>
> As Austin mentioned above, it is possible to create separate channels per
> topic in the ASF. You can see in the first screenshot that I attached.
>
> And yes,
