nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andre <>
Subject Re: [DISCUSS] Slack team for Apache NiFi
Date Tue, 11 Oct 2016 02:28:24 GMT

I don't want to sound too old school but I not sure the use of slack is a
good idea:

At least one ASF project that has decided to move away from Gitter:

Apparently there are issues around accessibility:

Some people seem to explicit oppose the idea:

And some point to a handy reminder of the risks associated with similar

Having said that, happy to work with whatever people prefer.


On Tue, Oct 11, 2016 at 1:53 AM, Matt Burgess <> wrote:

> All,
> I'd like to revisit the idea of having (and promoting) a Slack team
> for the Apache NiFi community. We broached the subject in an email
> thread a while back [1]. The email lists are great and IRC per se is
> still popular in the open-source community, but I think for folks that
> are more comfortable in the Slack environment, this would be another
> good avenue for the community to get together.
> We could perhaps add integrations with the email list(s), IRC
> channel(s), GitHub, etc. as sort of a one-stop shop for NiFi
> communication, or just use it for online collaboration.
> I'm thinking it would be invite-only (to avoid bots, spam, etc.) but
> that it would be fully open to the community, just an email to an
> admin (such as myself) to request an invitation (kind of like a manual
> version of the Apache Mailing List subscribe bot). The code of conduct
> would be the Apache Software Foundation's CoC [2], as it is a
> "communication channel used by our communities". I have seen this same
> invite-only approach work well for other ASF projects with Slack
> teams.
> I grabbed a URL [3] just in case the community would like to proceed
> ( is taken, but if someone in the community owns it and
> wants to use that instead, it's all good). The PMC would be
> owners/admins, my email address ( could be the
> destination for invite requests, and we could discuss what
> integrations, access rights (creating new channels, e.g.), etc. are
> appropriate.
> Thanks,
> Matt
> [1]
> 201511.mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@mail.
> [2]
> [3]

View raw message