Re: Use shared invites for Beam Slack Channel

[Lukasz Cwik]

Thanks Dan,

I generated the invite URL:
https://join.slack.com/t/apachebeam/shared_invite/enQtMzI4ODYzODY3MTY5LTIxOTJmMmFkMGVkMThhYmIwOWRkMTFiOGI3NDdlYzNmMmE2ZTA4N2JiMjc5ZDNmYTgxZGY5OTNlMDljMzM5NDU

and opened https://issues.apache.org/jira/browse/BEAM-3846 to update the
Apache Beam website so people can join themselves.


On Tue, Mar 13, 2018 at 12:48 PM Dan Halperin  wrote:

> Slack now has a publicly-endorsed way to post a public shared invite:
> https://my.slack.com/admin/shared_invites
>
> The downside is that it apparently has to be renewed monthly.
>
> Maybe Beam should use that, instead? Tradeoffs are not obvious, but it
> seems a win:
>
> * forget to renew -> people can't sign up (and reach out to user@?)
> vs
> * now, always force them to mail user@
>
> Dan
>
> On Tue, Mar 13, 2018 at 11:54 AM, Lukasz Cwik  wrote:
>
>> Invite sent, welcome.
>>
>> On Tue, Mar 13, 2018 at 11:08 AM, Ramjee Ganti 
>> wrote:
>>
>>> Hello,
>>>
>>> I am using Apache Beam and Dataflow for the last few months and Can
>>> someone please add me to the Beam slack channel?
>>>
>>> Thanks
>>> Ramjee
>>> http://ramjeeganti.com
>>>
>>
>>
>

Use shared invites for Beam Slack Channel

[Dan Halperin]

Slack now has a publicly-endorsed way to post a public shared invite:
https://my.slack.com/admin/shared_invites

The downside is that it apparently has to be renewed monthly.

Maybe Beam should use that, instead? Tradeoffs are not obvious, but it
seems a win:

* forget to renew -> people can't sign up (and reach out to user@?)
vs
* now, always force them to mail user@

Dan

On Tue, Mar 13, 2018 at 11:54 AM, Lukasz Cwik  wrote:

> Invite sent, welcome.
>
> On Tue, Mar 13, 2018 at 11:08 AM, Ramjee Ganti 
> wrote:
>
>> Hello,
>>
>> I am using Apache Beam and Dataflow for the last few months and Can
>> someone please add me to the Beam slack channel?
>>
>> Thanks
>> Ramjee
>> http://ramjeeganti.com
>>
>
>