Re: Slack Invites

[Davor Bonaci]

Off-topic:
The most annoying thing (to me) is that Slack's auto-detection of
self-invite bots is very sensitive to frequent invites of just one member.
When this activates, we get blocked from inviting more people and we have
to contact Slack support to unblock further invites. They resolve it very
quickly, but reaching out is a pain. So, for now, when inviting others,
please try to batch multiple invites, which would hopefully reduce the
occurrence frequency.

On-topic:
We shouldn't try to work around Slack's design and deploy auto-invite
functionality. That said, many email domains are automatically approved,
including apache.org. So, any committer on any project can join without
trouble. (Gmail cannot be added, unfortunately.)

Many projects use HipChat, which is the only tool supported by Infra.

Overall, I'm not happy with the invite/management burden of Slack, but
given Slack's popularity these days and high switching costs, I think I
favor status-quo.

On Thu, May 4, 2017 at 11:25 AM, Vladisav Jelisavcic 
wrote:

> Hi,
>
> Apache Ignite [1] is using Gitter, and it seems to work really well.
>
> Best regards,
> Vladisav
>
> [1] https://gitter.im/apacheignite/ignite
>
> On Thu, May 4, 2017 at 8:11 PM, Jason Kuster  invalid
> > wrote:
>
> > Gitter does look like it solves many of the challenges we've been facing
> > and looks like it's had wide adoption in some open-source communities. I
> > haven't found any other official Apache projects using it, so we could be
> > the vanguard here.
> >
> > On Thu, May 4, 2017 at 9:45 AM, Eric Anderson  >
> > wrote:
> >
> > > While on the topic: Have we considered alternatives like Gitter
> > > ? I'm not very familiar with Slack or Gitter, but
> > Gitter
> > > advertises being a little friendlier to open invites.
> > >
> > > On Thu, May 4, 2017 at 9:38 AM Dan Halperin
>  > >
> > > wrote:
> > >
> > > > My understanding is that if you use something like that plugin, and
> > they
> > > > detect it, Slack will ban you from new invites entirely or otherwise
> > > punish
> > > > you. They want this friction for free projects so that there's
> pressure
> > > to
> > > > pay.
> > > >
> > > > On Thu, May 4, 2017 at 9:18 AM, Jesse Anderson <
> > > je...@bigdatainstitute.io>
> > > > wrote:
> > > >
> > > > > Is possible to change how Slack invites are handled? This might
> > > encourage
> > > > > our community contributions.
> > > > >
> > > > > Right now, people have to email in (causing extra dev@/user@
> > emails).
> > > I
> > > > > did
> > > > > a quick search and found this 
> so
> > > > > people
> > > > > can invite themselves.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Jesse
> > > > > --
> > > > > Thanks,
> > > > >
> > > > > Jesse
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > ---
> > Jason Kuster
> > Apache Beam / Google Cloud Dataflow
> >
>

Re: Slack Invites

[Vladisav Jelisavcic]

Hi,

Apache Ignite [1] is using Gitter, and it seems to work really well.

Best regards,
Vladisav

[1] https://gitter.im/apacheignite/ignite

On Thu, May 4, 2017 at 8:11 PM, Jason Kuster  wrote:

> Gitter does look like it solves many of the challenges we've been facing
> and looks like it's had wide adoption in some open-source communities. I
> haven't found any other official Apache projects using it, so we could be
> the vanguard here.
>
> On Thu, May 4, 2017 at 9:45 AM, Eric Anderson 
> wrote:
>
> > While on the topic: Have we considered alternatives like Gitter
> > ? I'm not very familiar with Slack or Gitter, but
> Gitter
> > advertises being a little friendlier to open invites.
> >
> > On Thu, May 4, 2017 at 9:38 AM Dan Halperin  >
> > wrote:
> >
> > > My understanding is that if you use something like that plugin, and
> they
> > > detect it, Slack will ban you from new invites entirely or otherwise
> > punish
> > > you. They want this friction for free projects so that there's pressure
> > to
> > > pay.
> > >
> > > On Thu, May 4, 2017 at 9:18 AM, Jesse Anderson <
> > je...@bigdatainstitute.io>
> > > wrote:
> > >
> > > > Is possible to change how Slack invites are handled? This might
> > encourage
> > > > our community contributions.
> > > >
> > > > Right now, people have to email in (causing extra dev@/user@
> emails).
> > I
> > > > did
> > > > a quick search and found this  so
> > > > people
> > > > can invite themselves.
> > > >
> > > > Thanks,
> > > >
> > > > Jesse
> > > > --
> > > > Thanks,
> > > >
> > > > Jesse
> > > >
> > >
> >
>
>
>
> --
> ---
> Jason Kuster
> Apache Beam / Google Cloud Dataflow
>

Re: Slack Invites

[Jason Kuster]

Gitter does look like it solves many of the challenges we've been facing
and looks like it's had wide adoption in some open-source communities. I
haven't found any other official Apache projects using it, so we could be
the vanguard here.

On Thu, May 4, 2017 at 9:45 AM, Eric Anderson 
wrote:

> While on the topic: Have we considered alternatives like Gitter
> ? I'm not very familiar with Slack or Gitter, but Gitter
> advertises being a little friendlier to open invites.
>
> On Thu, May 4, 2017 at 9:38 AM Dan Halperin 
> wrote:
>
> > My understanding is that if you use something like that plugin, and they
> > detect it, Slack will ban you from new invites entirely or otherwise
> punish
> > you. They want this friction for free projects so that there's pressure
> to
> > pay.
> >
> > On Thu, May 4, 2017 at 9:18 AM, Jesse Anderson <
> je...@bigdatainstitute.io>
> > wrote:
> >
> > > Is possible to change how Slack invites are handled? This might
> encourage
> > > our community contributions.
> > >
> > > Right now, people have to email in (causing extra dev@/user@ emails).
> I
> > > did
> > > a quick search and found this  so
> > > people
> > > can invite themselves.
> > >
> > > Thanks,
> > >
> > > Jesse
> > > --
> > > Thanks,
> > >
> > > Jesse
> > >
> >
>



-- 
---
Jason Kuster
Apache Beam / Google Cloud Dataflow

Re: Slack Invites

[Eric Anderson]

While on the topic: Have we considered alternatives like Gitter
? I'm not very familiar with Slack or Gitter, but Gitter
advertises being a little friendlier to open invites.

On Thu, May 4, 2017 at 9:38 AM Dan Halperin 
wrote:

> My understanding is that if you use something like that plugin, and they
> detect it, Slack will ban you from new invites entirely or otherwise punish
> you. They want this friction for free projects so that there's pressure to
> pay.
>
> On Thu, May 4, 2017 at 9:18 AM, Jesse Anderson 
> wrote:
>
> > Is possible to change how Slack invites are handled? This might encourage
> > our community contributions.
> >
> > Right now, people have to email in (causing extra dev@/user@ emails). I
> > did
> > a quick search and found this  so
> > people
> > can invite themselves.
> >
> > Thanks,
> >
> > Jesse
> > --
> > Thanks,
> >
> > Jesse
> >
>

Re: Slack Invites

[Dan Halperin]

My understanding is that if you use something like that plugin, and they
detect it, Slack will ban you from new invites entirely or otherwise punish
you. They want this friction for free projects so that there's pressure to
pay.

On Thu, May 4, 2017 at 9:18 AM, Jesse Anderson 
wrote:

> Is possible to change how Slack invites are handled? This might encourage
> our community contributions.
>
> Right now, people have to email in (causing extra dev@/user@ emails). I
> did
> a quick search and found this  so
> people
> can invite themselves.
>
> Thanks,
>
> Jesse
> --
> Thanks,
>
> Jesse
>