I wouldn't be in favor of such "solutions" on top of Slack, unless specifically endorsed by Slack itself. It sounds like something intended to override specific design decisions, and we may not be acting in the best faith if we were to deploy it.
If Slack doesn't support features we think we need, we can always consider other solutions as well. On Mon, Jan 23, 2017 at 10:41 AM, Jason Kuster <[email protected]> wrote: > I've set up https://github.com/thesandlord/SlackEngine for a different > slack group I'm a part of before; would there be interest in that? It's an > automated slack invite generator -- we could just put up a link to it on > the Beam website and then anyone could generate themselves an invite. > > On Mon, Jan 23, 2017 at 10:39 AM, Dan Halperin <[email protected]> > wrote: > >> +1 to please make it an open slack channel if possible. And if not, >> please enlarge the set of approvers as quickly as possible. >> >> On Sun, Jan 22, 2017 at 11:10 PM, Ritesh Kasat <[email protected]> >> wrote: >> >>> Thanks Jean >>> >>> —Ritesh >>> >>> On 22-Jan-2017, at 10:36 PM, Jean-Baptiste Onofré <[email protected]> >>> wrote: >>> >>> I will. >>> >>> By the way, not sure it's possible (I gonna check) but maybe it would be >>> great to have a open slack channel (like IRC) without invite needed. >>> >>> Regards >>> JB >>> On Jan 23, 2017, at 07:32, Ritesh Kasat <[email protected]> wrote: >>>> >>>> Hello, >>>> >>>> Can someone add me to the Beam slack channel. >>>> >>>> Thanks >>>> Ritesh >>>> >>>> >>> >> > > > -- > ------- > Jason Kuster > Apache Beam (Incubating) / Google Cloud Dataflow >
