Gluster users - Apr 2019 - [Gluster-devel] One more way to contact Gluster team - Slack (gluster.slack.com)

Le vendredi 26 avril 2019 ? 13:24 +0530, Amar Tumballi Suryanarayan a
?crit :
> Hi All,
> 
> We wanted to move to Slack from IRC for our official communication
> channel
> from sometime, but couldn't as we didn't had a proper URL for us to
> register. 'gluster' was taken and we didn't knew who had it
> registered.
> Thanks to constant ask from Satish, Slack team has now agreed to let
> us use
> https://gluster.slack.com and I am happy to invite you all there.
> (Use this
> link
> <
>
https://join.slack.com/t/gluster/shared_invite/enQtNjIxMTA1MTk3MDE1LWIzZWZjNzhkYWEwNDdiZWRiOTczMTc4ZjdiY2JiMTc3MDE5YmEyZTRkNzg0MWJiMWM3OGEyMDU2MmYzMTViYTA
> >
> to
> join)
> 
> Please note that, it won't be a replacement for mailing list. But can
> be
> used by all developers and users for quick communication. Also note
> that,
> no information there would be 'stored' beyond 10k lines as we are
> using the
> free version of Slack.
Aren't we concerned about the ToS of slack ? Last time I did read them,
they were quite scary (like, if you use your corporate email, you
engage your employer, and that wasn't the worst part). 

Also, to anticipate the question, my employer Legal department told me
to not setup a bridge between IRC and slack, due to the said ToS.
 
-- 
Michael Scherer
Sysadmin, Community Infrastructure



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20190426/a8cf6748/attachment.sig>

Hello, are you not _BOTH_ Red Hat FTEs or contractors?

On Fri, Apr 26, 2019, 3:16 AM Michael Scherer <mscherer at redhat.com>
wrote:
> Le vendredi 26 avril 2019 ? 13:24 +0530, Amar Tumballi Suryanarayan a
> ?crit :
> > Hi All,
> >
> > We wanted to move to Slack from IRC for our official communication
> > channel
> > from sometime, but couldn't as we didn't had a proper URL for
us to
> > register. 'gluster' was taken and we didn't knew who had
it
> > registered.
> > Thanks to constant ask from Satish, Slack team has now agreed to let
> > us use
> > https://gluster.slack.com and I am happy to invite you all there.
> > (Use this
> > link
> > <
> >
>
https://join.slack.com/t/gluster/shared_invite/enQtNjIxMTA1MTk3MDE1LWIzZWZjNzhkYWEwNDdiZWRiOTczMTc4ZjdiY2JiMTc3MDE5YmEyZTRkNzg0MWJiMWM3OGEyMDU2MmYzMTViYTA
> > >
> > to
> > join)
> >
> > Please note that, it won't be a replacement for mailing list. But
can
> > be
> > used by all developers and users for quick communication. Also note
> > that,
> > no information there would be 'stored' beyond 10k lines as we
are
> > using the
> > free version of Slack.
>
> Aren't we concerned about the ToS of slack ? Last time I did read them,
> they were quite scary (like, if you use your corporate email, you
> engage your employer, and that wasn't the worst part).
>
> Also, to anticipate the question, my employer Legal department told me
> to not setup a bridge between IRC and slack, due to the said ToS.
>
> --
> Michael Scherer
> Sysadmin, Community Infrastructure
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20190426/1b0952f2/attachment.html>