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> >> >
