I will. Just need sometime as we are at the Apache Beam Summit 😁
Le 14 mars 2018 à 10:21, à 10:21, Lukasz Cwik <lc...@google.com> a écrit: >An ASF admin has to create a self enrollment link >https://the-asf.slack.com/admin/shared_invites and share it with >somebody >in the Apache Beam community. > > >On Wed, Mar 14, 2018 at 10:02 AM Anton Kedin <ke...@google.com> wrote: > >> What's the plan for users without `@apache.org` email? >> The page says to contact a workspace administrator for an invitation. >Will >> all existing users be automatically invited to the new workspace? >> >> >> On Wed, Mar 14, 2018 at 9:58 AM Thomas Weise <t...@apache.org> wrote: >> >>> After you enter the ASF ID on https://the-asf.slack.com/signup an >email >>> will go to your ASF address. Just completed that successfully. >>> >>> >>> -- >>> sent from mobile >>> >>> On Wed, Mar 14, 2018, 9:37 AM Romain Manni-Bucau ><rmannibu...@gmail.com> >>> wrote: >>> >>>> >>>> >>>> 2018-03-14 17:28 GMT+01:00 Lukasz Cwik <lc...@google.com>: >>>> >>>>> Telling people to migrate without updating the website is not >friendly >>>>> to the community or providing the self enrollment link is not >friendly to >>>>> those that helped invite all those existing users. >>>>> We should provide users on the old list a self enrollment link to >the >>>>> new list so that we don't have to handle the 100s of invites >manually. >>>>> >>>>> Also, I tried joining the-asf slack using my @apache.org address >and >>>>> was unable to join. How does one self enroll in this new channel? >>>>> >>>> >>>> Normally you have a big button, you enter your apache.org mail and >can >>>> log in directly. What did you see? >>>> >>>> >>>>> >>>>> On Wed, Mar 14, 2018 at 9:19 AM, Romain Manni-Bucau < >>>>> rmannibu...@gmail.com> wrote: >>>>> >>>>>> Can help but I have no idea how to do it yet, don't hesitate to >ping >>>>>> me if you don't have much cycles. >>>>>> >>>>>> >>>>>> Romain Manni-Bucau >>>>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog >>>>>> <https://rmannibucau.metawerx.net/> | Old Blog >>>>>> <http://rmannibucau.wordpress.com> | Github >>>>>> <https://github.com/rmannibucau> | LinkedIn >>>>>> <https://www.linkedin.com/in/rmannibucau> | Book >>>>>> ><https://www.packtpub.com/application-development/java-ee-8-high-performance> >>>>>> >>>>>> 2018-03-14 17:16 GMT+01:00 Jean-Baptiste Onofré ><j...@nanthrax.net>: >>>>>> >>>>>>> Do you want me to prepare the site PR with you ? >>>>>>> >>>>>>> Regards >>>>>>> JB >>>>>>> Le 14 mars 2018, à 09:12, Romain Manni-Bucau ><rmannibu...@gmail.com> >>>>>>> a écrit: >>>>>>>> >>>>>>>> updated the slack message (feel free to rephrase/reformat it, >the >>>>>>>> length is quite limited so it is ok) and will send the message >just after >>>>>>>> this one on #general >>>>>>>> will need help for the website update on the 26th ;) >>>>>>>> >>>>>>>> >>>>>>>> Romain Manni-Bucau >>>>>>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog >>>>>>>> <https://rmannibucau.metawerx.net/> | Old Blog >>>>>>>> <http://rmannibucau.wordpress.com> | Github >>>>>>>> <https://github.com/rmannibucau> | LinkedIn >>>>>>>> <https://www.linkedin.com/in/rmannibucau> | Book >>>>>>>> ><https://www.packtpub.com/application-development/java-ee-8-high-performance> >>>>>>>> >>>>>>>> 2018-03-14 16:48 GMT+01:00 Reuven Lax <re...@google.com>: >>>>>>>> >>>>>>>>> I don't have a strong feeling here. As long as there are >>>>>>>>> instructions on how to use the new slack channel, sounds good >to me! >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Mar 14, 2018 at 1:35 AM Romain Manni-Bucau < >>>>>>>>> rmannibu...@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hi guys, >>>>>>>>>> >>>>>>>>>> What do you think to migrate to the standard asf slack? I >would >>>>>>>>>> make it a bit more easy to find beam channel IMHO and it >would stay >>>>>>>>>> consistent with others. It also allows to auto join for asf >guys. >>>>>>>>>> >>>>>>>>>> If you think it is the way to go we can do: >>>>>>>>>> >>>>>>>>>> 1. put a message on current slack channel saying "we are >moving to >>>>>>>>>> the-asf #beam, this channel will be closed on the XXX" >>>>>>>>>> 2. notify it on the general (current) channel >>>>>>>>>> 3. update the website >>>>>>>>>> >>>>>>>>>> Personally I think a transition period of 10 days is enough >then >>>>>>>>>> channels can be archived. >>>>>>>>>> >>>>>>>>>> Wdyt? >>>>>>>>>> >>>>>>>>>> Side note: asf is in the process to try to get history on >slack as >>>>>>>>>> well which would be beneficial for beam too. >>>>>>>>>> >>>>>>>>>> Romain Manni-Bucau >>>>>>>>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog >>>>>>>>>> <https://rmannibucau.metawerx.net/> | Old Blog >>>>>>>>>> <http://rmannibucau.wordpress.com> | Github >>>>>>>>>> <https://github.com/rmannibucau> | LinkedIn >>>>>>>>>> <https://www.linkedin.com/in/rmannibucau> | Book >>>>>>>>>> ><https://www.packtpub.com/application-development/java-ee-8-high-performance> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>> >>>>> >>>>
