You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by Matt Burgess <ma...@apache.org> on 2016/10/10 14:53:49 UTC
[DISCUSS] Slack team for Apache NiFi
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
(nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/201511.mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@mail.gmail.com%3E
[2] https://www.apache.org/foundation/policies/conduct
[3] https://apachenifi.slack.com
Re: [DISCUSS] Slack team for Apache NiFi
Posted by Andre <an...@fucs.org>.
Matt,
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:
https://www.mail-archive.com/dev@airflow.incubator.apache.org/msg00901.html
Apparently there are issues around accessibility:
https://www.christianheilmann.com/2016/01/10/dont-use-slack/
https://www.marcozehe.de/2016/01/16/status-of-the-accessibility-of-slack/
Some people seem to explicit oppose the idea:
http://sircmpwn.github.io/2015/11/01/Please-stop-using-slack.html
http://www.theregister.co.uk/2016/03/17/no_slack_for_open_sourcers/
And some point to a handy reminder of the risks associated with similar
moves...
https://en.wikipedia.org/wiki/BitKeeper#Pricing_change
Having said that, happy to work with whatever people prefer.
Cheers
On Tue, Oct 11, 2016 at 1:53 AM, Matt Burgess <ma...@apache.org> 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
> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/
> 201511.mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@mail.
> gmail.com%3E
>
> [2] https://www.apache.org/foundation/policies/conduct
>
> [3] https://apachenifi.slack.com
>
Re: [DISCUSS] Slack team for Apache NiFi
Posted by Andre <an...@fucs.org>.
Matt,
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:
https://www.mail-archive.com/dev@airflow.incubator.apache.org/msg00901.html
Apparently there are issues around accessibility:
https://www.christianheilmann.com/2016/01/10/dont-use-slack/
https://www.marcozehe.de/2016/01/16/status-of-the-accessibility-of-slack/
Some people seem to explicit oppose the idea:
http://sircmpwn.github.io/2015/11/01/Please-stop-using-slack.html
http://www.theregister.co.uk/2016/03/17/no_slack_for_open_sourcers/
And some point to a handy reminder of the risks associated with similar
moves...
https://en.wikipedia.org/wiki/BitKeeper#Pricing_change
Having said that, happy to work with whatever people prefer.
Cheers
On Tue, Oct 11, 2016 at 1:53 AM, Matt Burgess <ma...@apache.org> 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
> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/
> 201511.mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@mail.
> gmail.com%3E
>
> [2] https://www.apache.org/foundation/policies/conduct
>
> [3] https://apachenifi.slack.com
>
Re: [DISCUSS] Slack team for Apache NiFi
Posted by John Wiesel <jw...@itembase.biz>.
According to this reply to a feature request on gitter.im from a year
ago, "the archives are also indexed via Google."
-
https://gitter.zendesk.com/hc/communities/public/questions/200747261-Searching-in-archives
Best
John
On 10.10.2016 20:55, Russell Bateman wrote:
> In my opinion, Bryan brings up early a huge point given the paucity of
> NiFi documentation, discussion and samples out there in Googleland. It
> would be a big loss not to have questions and answers show up in searches.
>
> On 10/10/2016 12:46 PM, Bryan Bende wrote:
>> My only concern with any kind of chat/channel is the loss of searchable
>> public content.
>> Right now the mailing list posts show up in Google searches and can be
>> found through other various tools, which is valuable for people searching
>> for information related to an issue they are seeing.
>> If people start transitioning to chat-based communication, all the
>> conversations there will likely only be found through that tool, and will
>> probably not be organized into individual threads of questions.
>>
>> I have not used Slack or Gitter much so I can't really say which is better,
>> but if I remember correctly Gitter only required you to sign-in with your
>> GitHub account and after that you could go into the community without
>> approval, which seems more open to me, but I really don't know.
>>
>> On Mon, Oct 10, 2016 at 2:28 PM, John Wiesel <jw...@itembase.biz> wrote:
>>
>>> Good evening,
>>>
>>> I am a new member to the community so I do not know much about the current
>>> needs.
>>> Still I'd like to point at gitter.im which has an open-sourced IRC bridge
>>> (https://irc.gitter.im/) for the heavy IRC users.
>>> Overall imho a good Slack alternative, its aim is to provide chatrooms for
>>> developers.
>>>
>>> Best
>>> John
>>>
>>>
>>> On Mon, Oct 10, 2016 at 4:53 PM, Matt Burgess <ma...@apache.org>
>>> 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
>>>> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/201511.
>>>> mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@
>>>> mail.gmail.com%3E
>>>>
>>>> [2] https://www.apache.org/foundation/policies/conduct
>>>>
>>>> [3] https://apachenifi.slack.com
>>>>
>>>
>
--
John Wiesel
Team Lead Information Extraction
itembase.com
Wilhelm Strasse 118 (Aufgang B) | 10963 Berlin | Germany
Email: jw@itembase.biz
itembase GmbH | Handelsregister: Berlin (Charlottenburg) | HRB 138369 B
| Verantwortlich f�r den Inhalt nach � 55 Abs. 2 RStV: Gesch�ftsf�hrer
Stefan J�rgensen
Re: [DISCUSS] Slack team for Apache NiFi
Posted by Russell Bateman <ru...@perfectsearchcorp.com>.
In my opinion, Bryan brings up early a huge point given the paucity of
NiFi documentation, discussion and samples out there in Googleland. It
would be a big loss not to have questions and answers show up in searches.
On 10/10/2016 12:46 PM, Bryan Bende wrote:
> My only concern with any kind of chat/channel is the loss of searchable
> public content.
> Right now the mailing list posts show up in Google searches and can be
> found through other various tools, which is valuable for people searching
> for information related to an issue they are seeing.
> If people start transitioning to chat-based communication, all the
> conversations there will likely only be found through that tool, and will
> probably not be organized into individual threads of questions.
>
> I have not used Slack or Gitter much so I can't really say which is better,
> but if I remember correctly Gitter only required you to sign-in with your
> GitHub account and after that you could go into the community without
> approval, which seems more open to me, but I really don't know.
>
> On Mon, Oct 10, 2016 at 2:28 PM, John Wiesel <jw...@itembase.biz> wrote:
>
>> Good evening,
>>
>> I am a new member to the community so I do not know much about the current
>> needs.
>> Still I'd like to point at gitter.im which has an open-sourced IRC bridge
>> (https://irc.gitter.im/) for the heavy IRC users.
>> Overall imho a good Slack alternative, its aim is to provide chatrooms for
>> developers.
>>
>> Best
>> John
>>
>>
>> On Mon, Oct 10, 2016 at 4:53 PM, Matt Burgess <ma...@apache.org>
>> 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
>>> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/201511.
>>> mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@
>>> mail.gmail.com%3E
>>>
>>> [2] https://www.apache.org/foundation/policies/conduct
>>>
>>> [3] https://apachenifi.slack.com
>>>
>>
Re: [DISCUSS] Slack team for Apache NiFi
Posted by Josh Elser <el...@apache.org>.
ASF's chat bot has the ability to automatically record conversations and
mail them to a list. As long as you remember to turn it on before
starting the conversation (wink), it's not too bad.
http://www.apache.org/dev/asfbot.html#meetings
Bryan Bende wrote:
> My only concern with any kind of chat/channel is the loss of searchable
> public content.
> Right now the mailing list posts show up in Google searches and can be
> found through other various tools, which is valuable for people searching
> for information related to an issue they are seeing.
> If people start transitioning to chat-based communication, all the
> conversations there will likely only be found through that tool, and will
> probably not be organized into individual threads of questions.
>
> I have not used Slack or Gitter much so I can't really say which is better,
> but if I remember correctly Gitter only required you to sign-in with your
> GitHub account and after that you could go into the community without
> approval, which seems more open to me, but I really don't know.
>
> On Mon, Oct 10, 2016 at 2:28 PM, John Wiesel<jw...@itembase.biz> wrote:
>
>> Good evening,
>>
>> I am a new member to the community so I do not know much about the current
>> needs.
>> Still I'd like to point at gitter.im which has an open-sourced IRC bridge
>> (https://irc.gitter.im/) for the heavy IRC users.
>> Overall imho a good Slack alternative, its aim is to provide chatrooms for
>> developers.
>>
>> Best
>> John
>>
>>
>> On Mon, Oct 10, 2016 at 4:53 PM, Matt Burgess<ma...@apache.org>
>> 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
>>> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/201511.
>>> mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@
>>> mail.gmail.com%3E
>>>
>>> [2] https://www.apache.org/foundation/policies/conduct
>>>
>>> [3] https://apachenifi.slack.com
>>>
>>
>
Re: [DISCUSS] Slack team for Apache NiFi
Posted by Josh Elser <el...@apache.org>.
ASF's chat bot has the ability to automatically record conversations and
mail them to a list. As long as you remember to turn it on before
starting the conversation (wink), it's not too bad.
http://www.apache.org/dev/asfbot.html#meetings
Bryan Bende wrote:
> My only concern with any kind of chat/channel is the loss of searchable
> public content.
> Right now the mailing list posts show up in Google searches and can be
> found through other various tools, which is valuable for people searching
> for information related to an issue they are seeing.
> If people start transitioning to chat-based communication, all the
> conversations there will likely only be found through that tool, and will
> probably not be organized into individual threads of questions.
>
> I have not used Slack or Gitter much so I can't really say which is better,
> but if I remember correctly Gitter only required you to sign-in with your
> GitHub account and after that you could go into the community without
> approval, which seems more open to me, but I really don't know.
>
> On Mon, Oct 10, 2016 at 2:28 PM, John Wiesel<jw...@itembase.biz> wrote:
>
>> Good evening,
>>
>> I am a new member to the community so I do not know much about the current
>> needs.
>> Still I'd like to point at gitter.im which has an open-sourced IRC bridge
>> (https://irc.gitter.im/) for the heavy IRC users.
>> Overall imho a good Slack alternative, its aim is to provide chatrooms for
>> developers.
>>
>> Best
>> John
>>
>>
>> On Mon, Oct 10, 2016 at 4:53 PM, Matt Burgess<ma...@apache.org>
>> 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
>>> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/201511.
>>> mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@
>>> mail.gmail.com%3E
>>>
>>> [2] https://www.apache.org/foundation/policies/conduct
>>>
>>> [3] https://apachenifi.slack.com
>>>
>>
>
Re: [DISCUSS] Slack team for Apache NiFi
Posted by Russell Bateman <ru...@perfectsearchcorp.com>.
In my opinion, Bryan brings up early a huge point given the paucity of
NiFi documentation, discussion and samples out there in Googleland. It
would be a big loss not to have questions and answers show up in searches.
On 10/10/2016 12:46 PM, Bryan Bende wrote:
> My only concern with any kind of chat/channel is the loss of searchable
> public content.
> Right now the mailing list posts show up in Google searches and can be
> found through other various tools, which is valuable for people searching
> for information related to an issue they are seeing.
> If people start transitioning to chat-based communication, all the
> conversations there will likely only be found through that tool, and will
> probably not be organized into individual threads of questions.
>
> I have not used Slack or Gitter much so I can't really say which is better,
> but if I remember correctly Gitter only required you to sign-in with your
> GitHub account and after that you could go into the community without
> approval, which seems more open to me, but I really don't know.
>
> On Mon, Oct 10, 2016 at 2:28 PM, John Wiesel <jw...@itembase.biz> wrote:
>
>> Good evening,
>>
>> I am a new member to the community so I do not know much about the current
>> needs.
>> Still I'd like to point at gitter.im which has an open-sourced IRC bridge
>> (https://irc.gitter.im/) for the heavy IRC users.
>> Overall imho a good Slack alternative, its aim is to provide chatrooms for
>> developers.
>>
>> Best
>> John
>>
>>
>> On Mon, Oct 10, 2016 at 4:53 PM, Matt Burgess <ma...@apache.org>
>> 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
>>> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/201511.
>>> mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@
>>> mail.gmail.com%3E
>>>
>>> [2] https://www.apache.org/foundation/policies/conduct
>>>
>>> [3] https://apachenifi.slack.com
>>>
>>
Re: [DISCUSS] Slack team for Apache NiFi
Posted by Bryan Bende <bb...@gmail.com>.
My only concern with any kind of chat/channel is the loss of searchable
public content.
Right now the mailing list posts show up in Google searches and can be
found through other various tools, which is valuable for people searching
for information related to an issue they are seeing.
If people start transitioning to chat-based communication, all the
conversations there will likely only be found through that tool, and will
probably not be organized into individual threads of questions.
I have not used Slack or Gitter much so I can't really say which is better,
but if I remember correctly Gitter only required you to sign-in with your
GitHub account and after that you could go into the community without
approval, which seems more open to me, but I really don't know.
On Mon, Oct 10, 2016 at 2:28 PM, John Wiesel <jw...@itembase.biz> wrote:
> Good evening,
>
> I am a new member to the community so I do not know much about the current
> needs.
> Still I'd like to point at gitter.im which has an open-sourced IRC bridge
> (https://irc.gitter.im/) for the heavy IRC users.
> Overall imho a good Slack alternative, its aim is to provide chatrooms for
> developers.
>
> Best
> John
>
>
> On Mon, Oct 10, 2016 at 4:53 PM, Matt Burgess <ma...@apache.org>
> 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
>> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/201511.
>> mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@
>> mail.gmail.com%3E
>>
>> [2] https://www.apache.org/foundation/policies/conduct
>>
>> [3] https://apachenifi.slack.com
>>
>
>
Re: [DISCUSS] Slack team for Apache NiFi
Posted by Bryan Bende <bb...@gmail.com>.
My only concern with any kind of chat/channel is the loss of searchable
public content.
Right now the mailing list posts show up in Google searches and can be
found through other various tools, which is valuable for people searching
for information related to an issue they are seeing.
If people start transitioning to chat-based communication, all the
conversations there will likely only be found through that tool, and will
probably not be organized into individual threads of questions.
I have not used Slack or Gitter much so I can't really say which is better,
but if I remember correctly Gitter only required you to sign-in with your
GitHub account and after that you could go into the community without
approval, which seems more open to me, but I really don't know.
On Mon, Oct 10, 2016 at 2:28 PM, John Wiesel <jw...@itembase.biz> wrote:
> Good evening,
>
> I am a new member to the community so I do not know much about the current
> needs.
> Still I'd like to point at gitter.im which has an open-sourced IRC bridge
> (https://irc.gitter.im/) for the heavy IRC users.
> Overall imho a good Slack alternative, its aim is to provide chatrooms for
> developers.
>
> Best
> John
>
>
> On Mon, Oct 10, 2016 at 4:53 PM, Matt Burgess <ma...@apache.org>
> 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
>> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/201511.
>> mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@
>> mail.gmail.com%3E
>>
>> [2] https://www.apache.org/foundation/policies/conduct
>>
>> [3] https://apachenifi.slack.com
>>
>
>
Re: [DISCUSS] Slack team for Apache NiFi
Posted by John Wiesel <jw...@itembase.biz>.
Good evening,
I am a new member to the community so I do not know much about the current
needs.
Still I'd like to point at gitter.im which has an open-sourced IRC bridge (
https://irc.gitter.im/) for the heavy IRC users.
Overall imho a good Slack alternative, its aim is to provide chatrooms for
developers.
Best
John
On Mon, Oct 10, 2016 at 4:53 PM, Matt Burgess <ma...@apache.org> 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
> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/
> 201511.mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@mail.
> gmail.com%3E
>
> [2] https://www.apache.org/foundation/policies/conduct
>
> [3] https://apachenifi.slack.com
>
Re: [DISCUSS] Slack team for Apache NiFi
Posted by johny casanova <co...@gmail.com>.
Matt,
I think this is an awesome idea. Slack is so awesome for all the things you
mentioned. 1+
On Oct 10, 2016 10:53 AM, "Matt Burgess" <ma...@apache.org> 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
> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/
> 201511.mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@mail.
> gmail.com%3E
>
> [2] https://www.apache.org/foundation/policies/conduct
>
> [3] https://apachenifi.slack.com
>
Re: [DISCUSS] Slack team for Apache NiFi
Posted by John Wiesel <jw...@itembase.biz>.
Good evening,
I am a new member to the community so I do not know much about the current
needs.
Still I'd like to point at gitter.im which has an open-sourced IRC bridge (
https://irc.gitter.im/) for the heavy IRC users.
Overall imho a good Slack alternative, its aim is to provide chatrooms for
developers.
Best
John
On Mon, Oct 10, 2016 at 4:53 PM, Matt Burgess <ma...@apache.org> 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
> (nifi.slack.com 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 (mattyb149@apache.org) 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] https://mail-archives.apache.org/mod_mbox/nifi-users/
> 201511.mbox/%3CCA+w4d5RJvxvFEnGVsexCSmEvzL_TxG_Ne2KEiFsrGEapCwoOAQ@mail.
> gmail.com%3E
>
> [2] https://www.apache.org/foundation/policies/conduct
>
> [3] https://apachenifi.slack.com
>