Re: [E] Re: Apache Druid Slack
Hey I fully support having our slack history indexed on google and I think we should do it sooner rather than later as there are a lot of good threads on slack that are getting purged out. On Wed, Oct 19, 2022 at 9:47 AM Abhishek Agarwal wrote: > I recently learned about Apache Flink making slack conversations google > indexable through linen.dev. That might be worth exploring. Does anyone > know how it works? > > On Wed, Oct 19, 2022 at 4:18 AM Eyal Yurman .invalid> > wrote: > > > What should we do about Slack canceling message history for free tier? > > > > Perhaps we should export history elsewhere? > > > > On Thu, Jan 27, 2022 at 1:10 PM Vadim Ogievetsky > > > wrote: > > > > > Alright, I have setup the new Slack workspace and updated the link on > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__druid.apache.org_community_=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=hV9FPFkuEXDmMbTGo3m_iqUc-baVKjOHznj9kig1I1Q= > > > to point to it. > > > Please join with the > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__druid.apache.org_community_join-2Dslack=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=07e2sPTwojKxi997mSN4a5Ktcr1lyHcekXuTwEZj9JY= > > > link (and share it with others). > > > Sadly there is no way to migrate content from one Slack workspace to > > > workspace, I am sure we will fill the new channel with great content > very > > > quickly! > > > > > > On 2022/01/20 18:15:23 Vadim Ogievetsky wrote: > > > > I think that the PMC should create a new Slack channel for Apache > Druid > > > and > > > > shift the community towards using it away from the ASF Slack. I > > volunteer > > > > to do this on the PMCs behalf and do all the setup/admin work. I > would > > > > share admin access with any PMC member. > > > > > > > > What is the motivation for this? > > > > > > > > As you may have heard, it’s become increasingly difficult for new > users > > > > without an @apache.org email address to join the ASF #druid Slack > > > channel. > > > > ASF Infra disabled the option to publicly provide a link to the > > workspace > > > > to anyone who wanted it, after encountering issues with spammers. > > > > > > > > Per Infra’s guidance ( > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__infra.apache.org_slack.html=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=qZfDyv1d4QnrCrEjvTgSbm8qeEj-B-dFWKil2k4XOyQ= > > > ), new community > > > > members should only be invited as single-channel guests. > Unfortunately, > > > > single-channel guests are unable to extend invitations to new > members, > > > > including their colleagues who are using Druid. Only someone with > full > > > > member privileges is able to extend an invitation to new members. > This > > > lack > > > > of consistency doesn’t make the community feel inclusive. > > > > > > > > There is a workaround in place ( > > > > > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_druid-2Dwebsite-2Dsrc_pull_278=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=LZAv4yoEkFJcPmJckcAR0xXyuo7V81ZfR2X_jxQjH58= > > > ) – users can send an > > > > email to druid-u...@googlegroups.com to request an invite to the > Slack > > > > channel from an existing member – but this still poses a barrier to > > > entry, > > > > and isn’t a viable permanent solution. It also creates potential > > privacy > > > > issues as not everyone is at liberty to announce they’re using Druid > > nor > > > > wishes to display their email address in a public forum. > > > > > > > > I propose we make our own free Slack channel for Apache Druid and > > > encourage > > > > people to migrate to it. Then we can have our own policy on Slack > > > > invitations - I would like to restore the ability for anyone on the > web > > > to > > > > join our Slack. > > > > > > > > This is not a 100% original idea, in fact this is what other Apache > > > > projects have done, notably Apache Pinot (see "join our slack" on > > > > > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__pinot.apache.org_=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=GYTpyHD-1U_Er2eKNXk41b9aiy4zW9EtCt-2YXxSh9o= > > > ). I propose we do the same. > > > > > > > > Vadim > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > > > > For additional commands, e-mail: dev-h...@druid.apache.org > > > > > > > > > > > >
Re: [E] Re: Apache Druid Slack
I recently learned about Apache Flink making slack conversations google indexable through linen.dev. That might be worth exploring. Does anyone know how it works? On Wed, Oct 19, 2022 at 4:18 AM Eyal Yurman wrote: > What should we do about Slack canceling message history for free tier? > > Perhaps we should export history elsewhere? > > On Thu, Jan 27, 2022 at 1:10 PM Vadim Ogievetsky > wrote: > > > Alright, I have setup the new Slack workspace and updated the link on > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__druid.apache.org_community_=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=hV9FPFkuEXDmMbTGo3m_iqUc-baVKjOHznj9kig1I1Q= > > to point to it. > > Please join with the > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__druid.apache.org_community_join-2Dslack=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=07e2sPTwojKxi997mSN4a5Ktcr1lyHcekXuTwEZj9JY= > > link (and share it with others). > > Sadly there is no way to migrate content from one Slack workspace to > > workspace, I am sure we will fill the new channel with great content very > > quickly! > > > > On 2022/01/20 18:15:23 Vadim Ogievetsky wrote: > > > I think that the PMC should create a new Slack channel for Apache Druid > > and > > > shift the community towards using it away from the ASF Slack. I > volunteer > > > to do this on the PMCs behalf and do all the setup/admin work. I would > > > share admin access with any PMC member. > > > > > > What is the motivation for this? > > > > > > As you may have heard, it’s become increasingly difficult for new users > > > without an @apache.org email address to join the ASF #druid Slack > > channel. > > > ASF Infra disabled the option to publicly provide a link to the > workspace > > > to anyone who wanted it, after encountering issues with spammers. > > > > > > Per Infra’s guidance ( > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__infra.apache.org_slack.html=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=qZfDyv1d4QnrCrEjvTgSbm8qeEj-B-dFWKil2k4XOyQ= > > ), new community > > > members should only be invited as single-channel guests. Unfortunately, > > > single-channel guests are unable to extend invitations to new members, > > > including their colleagues who are using Druid. Only someone with full > > > member privileges is able to extend an invitation to new members. This > > lack > > > of consistency doesn’t make the community feel inclusive. > > > > > > There is a workaround in place ( > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_druid-2Dwebsite-2Dsrc_pull_278=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=LZAv4yoEkFJcPmJckcAR0xXyuo7V81ZfR2X_jxQjH58= > > ) – users can send an > > > email to druid-u...@googlegroups.com to request an invite to the Slack > > > channel from an existing member – but this still poses a barrier to > > entry, > > > and isn’t a viable permanent solution. It also creates potential > privacy > > > issues as not everyone is at liberty to announce they’re using Druid > nor > > > wishes to display their email address in a public forum. > > > > > > I propose we make our own free Slack channel for Apache Druid and > > encourage > > > people to migrate to it. Then we can have our own policy on Slack > > > invitations - I would like to restore the ability for anyone on the web > > to > > > join our Slack. > > > > > > This is not a 100% original idea, in fact this is what other Apache > > > projects have done, notably Apache Pinot (see "join our slack" on > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__pinot.apache.org_=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=GYTpyHD-1U_Er2eKNXk41b9aiy4zW9EtCt-2YXxSh9o= > > ). I propose we do the same. > > > > > > Vadim > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > > > For additional commands, e-mail: dev-h...@druid.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > > For additional commands, e-mail: dev-h...@druid.apache.org > > > > >
Re: [E] Re: Apache Druid Slack
What should we do about Slack canceling message history for free tier? Perhaps we should export history elsewhere? On Thu, Jan 27, 2022 at 1:10 PM Vadim Ogievetsky wrote: > Alright, I have setup the new Slack workspace and updated the link on > https://urldefense.proofpoint.com/v2/url?u=https-3A__druid.apache.org_community_=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=hV9FPFkuEXDmMbTGo3m_iqUc-baVKjOHznj9kig1I1Q= > to point to it. > Please join with the > https://urldefense.proofpoint.com/v2/url?u=https-3A__druid.apache.org_community_join-2Dslack=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=07e2sPTwojKxi997mSN4a5Ktcr1lyHcekXuTwEZj9JY= > link (and share it with others). > Sadly there is no way to migrate content from one Slack workspace to > workspace, I am sure we will fill the new channel with great content very > quickly! > > On 2022/01/20 18:15:23 Vadim Ogievetsky wrote: > > I think that the PMC should create a new Slack channel for Apache Druid > and > > shift the community towards using it away from the ASF Slack. I volunteer > > to do this on the PMCs behalf and do all the setup/admin work. I would > > share admin access with any PMC member. > > > > What is the motivation for this? > > > > As you may have heard, it’s become increasingly difficult for new users > > without an @apache.org email address to join the ASF #druid Slack > channel. > > ASF Infra disabled the option to publicly provide a link to the workspace > > to anyone who wanted it, after encountering issues with spammers. > > > > Per Infra’s guidance ( > https://urldefense.proofpoint.com/v2/url?u=https-3A__infra.apache.org_slack.html=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=qZfDyv1d4QnrCrEjvTgSbm8qeEj-B-dFWKil2k4XOyQ= > ), new community > > members should only be invited as single-channel guests. Unfortunately, > > single-channel guests are unable to extend invitations to new members, > > including their colleagues who are using Druid. Only someone with full > > member privileges is able to extend an invitation to new members. This > lack > > of consistency doesn’t make the community feel inclusive. > > > > There is a workaround in place ( > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_druid-2Dwebsite-2Dsrc_pull_278=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=LZAv4yoEkFJcPmJckcAR0xXyuo7V81ZfR2X_jxQjH58= > ) – users can send an > > email to druid-u...@googlegroups.com to request an invite to the Slack > > channel from an existing member – but this still poses a barrier to > entry, > > and isn’t a viable permanent solution. It also creates potential privacy > > issues as not everyone is at liberty to announce they’re using Druid nor > > wishes to display their email address in a public forum. > > > > I propose we make our own free Slack channel for Apache Druid and > encourage > > people to migrate to it. Then we can have our own policy on Slack > > invitations - I would like to restore the ability for anyone on the web > to > > join our Slack. > > > > This is not a 100% original idea, in fact this is what other Apache > > projects have done, notably Apache Pinot (see "join our slack" on > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__pinot.apache.org_=DwIFaQ=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY=XsVtrQ1n66sQ9WUOQT8K162x-6-hXEAYJwF2JdxJbMU=adK2ZRhIznXu2_uvV3MLkV-rmdB2gTTJbxUdYqZHQ_DabAl8uQCbiEDLwBUVdYxF=GYTpyHD-1U_Er2eKNXk41b9aiy4zW9EtCt-2YXxSh9o= > ). I propose we do the same. > > > > Vadim > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > > For additional commands, e-mail: dev-h...@druid.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > >
Re: Apache Druid Slack
Alright, I have setup the new Slack workspace and updated the link on https://druid.apache.org/community/ to point to it. Please join with the https://druid.apache.org/community/join-slack link (and share it with others). Sadly there is no way to migrate content from one Slack workspace to workspace, I am sure we will fill the new channel with great content very quickly! On 2022/01/20 18:15:23 Vadim Ogievetsky wrote: > I think that the PMC should create a new Slack channel for Apache Druid and > shift the community towards using it away from the ASF Slack. I volunteer > to do this on the PMCs behalf and do all the setup/admin work. I would > share admin access with any PMC member. > > What is the motivation for this? > > As you may have heard, it’s become increasingly difficult for new users > without an @apache.org email address to join the ASF #druid Slack channel. > ASF Infra disabled the option to publicly provide a link to the workspace > to anyone who wanted it, after encountering issues with spammers. > > Per Infra’s guidance (https://infra.apache.org/slack.html), new community > members should only be invited as single-channel guests. Unfortunately, > single-channel guests are unable to extend invitations to new members, > including their colleagues who are using Druid. Only someone with full > member privileges is able to extend an invitation to new members. This lack > of consistency doesn’t make the community feel inclusive. > > There is a workaround in place ( > https://github.com/apache/druid-website-src/pull/278) – users can send an > email to druid-u...@googlegroups.com to request an invite to the Slack > channel from an existing member – but this still poses a barrier to entry, > and isn’t a viable permanent solution. It also creates potential privacy > issues as not everyone is at liberty to announce they’re using Druid nor > wishes to display their email address in a public forum. > > I propose we make our own free Slack channel for Apache Druid and encourage > people to migrate to it. Then we can have our own policy on Slack > invitations - I would like to restore the ability for anyone on the web to > join our Slack. > > This is not a 100% original idea, in fact this is what other Apache > projects have done, notably Apache Pinot (see "join our slack" on > https://pinot.apache.org/). I propose we do the same. > > Vadim > > - > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: Apache Druid Slack
+1 There is a lot of friction in joining apache infra slack. Also, I can't tell if it is a recent policy change but any new invitation to the druid channel now needs to be approved by ASF slack admin. That seems like one more manual step to get over. Though is there a way to migrate/copy the channel contents? There is a whole lot of history that we would want to retain in the new slack channel. On Fri, Jan 21, 2022 at 10:48 PM Gian Merlino wrote: > It sounds like a good idea to me. It's not ideal that the current Slack > workspace is hard for new people to join. > > On Thu, Jan 20, 2022 at 10:15 AM Vadim Ogievetsky > wrote: > > > I think that the PMC should create a new Slack channel for Apache Druid > and > > shift the community towards using it away from the ASF Slack. I volunteer > > to do this on the PMCs behalf and do all the setup/admin work. I would > > share admin access with any PMC member. > > > > What is the motivation for this? > > > > As you may have heard, it’s become increasingly difficult for new users > > without an @apache.org email address to join the ASF #druid Slack > channel. > > ASF Infra disabled the option to publicly provide a link to the workspace > > to anyone who wanted it, after encountering issues with spammers. > > > > Per Infra’s guidance (https://infra.apache.org/slack.html), new > community > > members should only be invited as single-channel guests. Unfortunately, > > single-channel guests are unable to extend invitations to new members, > > including their colleagues who are using Druid. Only someone with full > > member privileges is able to extend an invitation to new members. This > lack > > of consistency doesn’t make the community feel inclusive. > > > > There is a workaround in place ( > > https://github.com/apache/druid-website-src/pull/278) – users can send > an > > email to druid-u...@googlegroups.com to request an invite to the Slack > > channel from an existing member – but this still poses a barrier to > entry, > > and isn’t a viable permanent solution. It also creates potential privacy > > issues as not everyone is at liberty to announce they’re using Druid nor > > wishes to display their email address in a public forum. > > > > I propose we make our own free Slack channel for Apache Druid and > encourage > > people to migrate to it. Then we can have our own policy on Slack > > invitations - I would like to restore the ability for anyone on the web > to > > join our Slack. > > > > This is not a 100% original idea, in fact this is what other Apache > > projects have done, notably Apache Pinot (see "join our slack" on > > https://pinot.apache.org/). I propose we do the same. > > > > Vadim > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > > For additional commands, e-mail: dev-h...@druid.apache.org > > > > >
Re: Apache Druid Slack
It sounds like a good idea to me. It's not ideal that the current Slack workspace is hard for new people to join. On Thu, Jan 20, 2022 at 10:15 AM Vadim Ogievetsky wrote: > I think that the PMC should create a new Slack channel for Apache Druid and > shift the community towards using it away from the ASF Slack. I volunteer > to do this on the PMCs behalf and do all the setup/admin work. I would > share admin access with any PMC member. > > What is the motivation for this? > > As you may have heard, it’s become increasingly difficult for new users > without an @apache.org email address to join the ASF #druid Slack channel. > ASF Infra disabled the option to publicly provide a link to the workspace > to anyone who wanted it, after encountering issues with spammers. > > Per Infra’s guidance (https://infra.apache.org/slack.html), new community > members should only be invited as single-channel guests. Unfortunately, > single-channel guests are unable to extend invitations to new members, > including their colleagues who are using Druid. Only someone with full > member privileges is able to extend an invitation to new members. This lack > of consistency doesn’t make the community feel inclusive. > > There is a workaround in place ( > https://github.com/apache/druid-website-src/pull/278) – users can send an > email to druid-u...@googlegroups.com to request an invite to the Slack > channel from an existing member – but this still poses a barrier to entry, > and isn’t a viable permanent solution. It also creates potential privacy > issues as not everyone is at liberty to announce they’re using Druid nor > wishes to display their email address in a public forum. > > I propose we make our own free Slack channel for Apache Druid and encourage > people to migrate to it. Then we can have our own policy on Slack > invitations - I would like to restore the ability for anyone on the web to > join our Slack. > > This is not a 100% original idea, in fact this is what other Apache > projects have done, notably Apache Pinot (see "join our slack" on > https://pinot.apache.org/). I propose we do the same. > > Vadim > > - > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > >
Apache Druid Slack
I think that the PMC should create a new Slack channel for Apache Druid and shift the community towards using it away from the ASF Slack. I volunteer to do this on the PMCs behalf and do all the setup/admin work. I would share admin access with any PMC member. What is the motivation for this? As you may have heard, it’s become increasingly difficult for new users without an @apache.org email address to join the ASF #druid Slack channel. ASF Infra disabled the option to publicly provide a link to the workspace to anyone who wanted it, after encountering issues with spammers. Per Infra’s guidance (https://infra.apache.org/slack.html), new community members should only be invited as single-channel guests. Unfortunately, single-channel guests are unable to extend invitations to new members, including their colleagues who are using Druid. Only someone with full member privileges is able to extend an invitation to new members. This lack of consistency doesn’t make the community feel inclusive. There is a workaround in place ( https://github.com/apache/druid-website-src/pull/278) – users can send an email to druid-u...@googlegroups.com to request an invite to the Slack channel from an existing member – but this still poses a barrier to entry, and isn’t a viable permanent solution. It also creates potential privacy issues as not everyone is at liberty to announce they’re using Druid nor wishes to display their email address in a public forum. I propose we make our own free Slack channel for Apache Druid and encourage people to migrate to it. Then we can have our own policy on Slack invitations - I would like to restore the ability for anyone on the web to join our Slack. This is not a 100% original idea, in fact this is what other Apache projects have done, notably Apache Pinot (see "join our slack" on https://pinot.apache.org/). I propose we do the same. Vadim - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
