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 <jasonkus...@google.com.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 <eric...@google.com.invalid>
> wrote:
>
> > While on the topic: Have we considered alternatives like Gitter
> > <http://gitter.im>? 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 <dhalp...@google.com.invalid
> >
> > 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 <https://github.com/rauchg/slackin> so
> > > > people
> > > > can invite themselves.
> > > >
> > > > Thanks,
> > > >
> > > > Jesse
> > > > --
> > > > Thanks,
> > > >
> > > > Jesse
> > > >
> > >
> >
>
>
>
> --
> -------
> Jason Kuster
> Apache Beam / Google Cloud Dataflow
>

Reply via email to