Hi, Dongjoon, The other communities (e.g., Pinot, Druid, Flink) created their own Slack workspaces last year. I did not see an objection from the ASF board. At the same time, Slack workspaces are very popular and useful in most non-ASF open source communities. TBH, we are kind of late. I think we can do the same in our community?
We can follow the guide when the ASF has an official process for ASF archiving. Since our PMC are the owner of the slack workspace, we can make a change based on the policy. WDYT? Xiao Dongjoon Hyun <dongjoon.h...@gmail.com> 于2023年3月30日周四 09:03写道： > Hi, Xiao and all. > > (cc Matei) > > Please hold on the vote. > > There is a concern expressed by ASF board because recent Slack activities > created an isolated silo outside of ASF mailing list archive. > > We need to establish a way to embrace it back to ASF archive before > starting anything official. > > Bests, > Dongjoon. > > > > On Wed, Mar 29, 2023 at 11:32 PM Xiao Li <gatorsm...@gmail.com> wrote: > >> +1 >> >> + @d...@spark.apache.org <d...@spark.apache.org> >> >> This is a good idea. The other Apache projects (e.g., Pinot, Druid, >> Flink) have created their own dedicated Slack workspaces for faster >> communication. We can do the same in Apache Spark. The Slack workspace will >> be maintained by the Apache Spark PMC. I propose to initiate a vote for the >> creation of a new Apache Spark Slack workspace. Does that sound good? >> >> Cheers, >> >> Xiao >> >> >> >> >> >> >> >> Mich Talebzadeh <mich.talebza...@gmail.com> 于2023年3月28日周二 07:07写道： >> >>> I created one at slack called pyspark >>> >>> >>> Mich Talebzadeh, >>> Lead Solutions Architect/Engineering Lead >>> Palantir Technologies Limited >>> >>> >>> view my Linkedin profile >>> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> >>> >>> >>> https://en.everybodywiki.com/Mich_Talebzadeh >>> >>> >>> >>> *Disclaimer:* Use it at your own risk. Any and all responsibility for >>> any loss, damage or destruction of data or any other property which may >>> arise from relying on this email's technical content is explicitly >>> disclaimed. The author will in no case be liable for any monetary damages >>> arising from such loss, damage or destruction. >>> >>> >>> >>> >>> On Tue, 28 Mar 2023 at 03:52, asma zgolli <zgollia...@gmail.com> wrote: >>> >>>> +1 good idea, I d like to join as well. >>>> >>>> Le mar. 28 mars 2023 à 04:09, Winston Lai <weiruanl...@gmail.com> a >>>> écrit : >>>> >>>>> Please let us know when the channel is created. I'd like to join :) >>>>> >>>>> Thank You & Best Regards >>>>> Winston Lai >>>>> ------------------------------ >>>>> *From:* Denny Lee <denny.g....@gmail.com> >>>>> *Sent:* Tuesday, March 28, 2023 9:43:08 AM >>>>> *To:* Hyukjin Kwon <gurwls...@gmail.com> >>>>> *Cc:* keen <kee...@gmx.net>; user@spark.apache.org < >>>>> user@spark.apache.org> >>>>> *Subject:* Re: Slack for PySpark users >>>>> >>>>> +1 I think this is a great idea! >>>>> >>>>> On Mon, Mar 27, 2023 at 6:24 PM Hyukjin Kwon <gurwls...@gmail.com> >>>>> wrote: >>>>> >>>>> Yeah, actually I think we should better have a slack channel so we can >>>>> easily discuss with users and developers. >>>>> >>>>> On Tue, 28 Mar 2023 at 03:08, keen <kee...@gmx.net> wrote: >>>>> >>>>> Hi all, >>>>> I really like *Slack *as communication channel for a tech community. >>>>> There is a Slack workspace for *delta lake users* ( >>>>> https://go.delta.io/slack) that I enjoy a lot. >>>>> I was wondering if there is something similar for PySpark users. >>>>> >>>>> If not, would there be anything wrong with creating a new >>>>> Slack workspace for PySpark users? (when explicitly mentioning that this >>>>> is >>>>> *not* officially part of Apache Spark)? >>>>> >>>>> Cheers >>>>> Martin >>>>> >>>>> >>>> >>>> -- >>>> Asma ZGOLLI >>>> >>>> Ph.D. in Big Data - Applied Machine Learning >>>> >>>>
