Hi Kaxil, Not suggesting that a migration to ASF slack is the right move (don't have a strong opinion).
I disagree with your premise that separation of channels per topic is impossible in the ASF Seems could have channels in the ASF Slack : #Airflow-announce #Airflow-users-bay-area #Airflow-github #Airflow-random #Airflow-creative As an example, Beam has many different slack channels for many different topics. Another point to consider, message history: Do either Airflow and/or ASF Slack's keep full history? And/or would one or the other allow or make easier the ability to keep history for archive of ongoing record (if desired)? I have seen slack being 'mirrored'/synced, with other messaging platforms for either alternate interface or archive/history. Cheers, Austin On Mon, Feb 11, 2019 at 12:04 AM Kaxil Naik <kaxiln...@gmail.com> wrote: > Currently, we have a good separation of channels per topic. A separate > channel for announcement etc. This won't be possible if we move to ASF > slack. > > > > On Mon, Feb 11, 2019, 07:45 Aizhamal Nurmamat kyzy > <aizha...@google.com.invalid> wrote: > > > Hello everybody! > > > > I was wondering what the community thinks of migrating Apache Airflow > slack > > channel [1] to the official ASF slack [2]? > > > > Some advantages would be: > > > > 1. It would allow for Airflow community to interact/chat with the > > communities of many other Apache projects > > 2. It would make Airflow remain consistent with ASF projects > > 3. It would allow to auto join for ASF community members > > > > A possible disadvantage would be that we will depend on Apache members to > > renew the invite link. > > > > What are your thoughts? > > > > [1] https://apache-airflow.slack.com > > [2] https://the-asf.slack.com > > > > -- > > > > *Aizhamal Nurmamat kyzy* > > > > Open Source Program Manager > > > > 646-355-9740 Mobile > > > > 601 North 34th Street, Seattle, WA 98103 > > >
