> > > 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>
> > >
his 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 invi
ressure
> 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 contribu
son <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 s
;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/slacki
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,
