Re: Slack for PySpark users

2023-04-04 Thread Mich Talebzadeh
gt;>>>>>>>>> https://github.com/RocketChat/Rocket.Chat >>>>>>>>>>>>>> >>>>>>>>>>>>>> tor. 30. mar. 2023 kl. 18:54 skrev Mich Talebzadeh < >>>>>>>>&

Re: Slack for PySpark users

2023-04-04 Thread Bjørn Jørgensen
;>>>>>>>>>>>> ASF-related Slack channels because I don't think that matters. >>>>>>>>>>>>>> However, I >>>>>>>>>>>>>> stand corrected >>>>>>>>>>>

Re: Slack for PySpark users

2023-04-04 Thread Mich Talebzadeh
t;>>>>>>> list >>>>>>>>>>>>> archive... >>>>>>>>>>>>> Well, there are activities on Spark and indeed other open >>>>>>>>>>>>> source software everywhere. One wa

Re: Slack for PySpark users

2023-04-03 Thread Dongjoon Hyun
erriding reason, >>>>>>>>>>>> we should embrace it as slack can co-exist with the other mailing >>>>>>>>>>>> lists and >>>>>>>>>>>> channels like linkedin etc. >>>>&g

Re: Slack for PySpark users

2023-04-03 Thread Denny Lee
gt;>>>>>>>> >>>>>>>>>>>view my Linkedin profile >>>>>>>>>>> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> >>>>>>>>>>> >>>>>>>>>>> &g

Re: Slack for PySpark users

2023-04-03 Thread Dongjoon Hyun
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, d

Re: Slack for PySpark users

2023-04-03 Thread Mich Talebzadeh
>>>>>> - To be clear, I intentionally didn't refer to any specific >>>>>>>>>> mailing list because we didn't set up any rule here yet. >>>>>>>>>> >>>>>>>>>> To Xiao. I understand what you mean. That's t

Re: Slack for PySpark users

2023-04-03 Thread Jungtaek Lim
channels >>>>>>>>> outside ASF email which is specifically concerning Slack. >>>>>>>>> Please hold on any official action for this topic. We will know >>>>>>>>> how to support it seamlessly. >>>

Re: Slack for PySpark users

2023-04-03 Thread Jungtaek Lim
gt;>>>> 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

Re: Slack for PySpark users

2023-04-03 Thread Dongjoon Hyun
t;>> outside ASF email which is specifically concerning Slack. >>>>>>>>> Please hold on any official action for this topic. We will know >>>>>>>>> how to support it seamlessly. >>>>>>>>> >>>>>&

Re: Slack for PySpark users

2023-04-03 Thread Mich Talebzadeh
bjection 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 &g

Re: Slack for PySpark users

2023-04-03 Thread Dongjoon Hyun
munity? >>>>>>>> >>>>>>>> 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 >>>>>>>&g

Re: Slack for PySpark users

2023-03-30 Thread Jungtaek Lim
i) >>>>>>>> >>>>>>>> Please hold on the vote. >>>>>>>> >>>>>>>> There is a concern expressed by ASF board because recent Slack >>>>>>>> activities created an isolated

Re: Slack for PySpark users

2023-03-30 Thread Mich Talebzadeh
>> >>>>>>> >>>>>>> On Wed, Mar 29, 2023 at 11:32 PM Xiao Li >>>>>>> wrote: >>>>>>> >>>>>>>> +1 >>>>>>>> >>>>>>>> + @dev@spark.apac

Re: Slack for PySpark users

2023-03-30 Thread Denny Lee
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 >>>>>>>

Re: Slack for PySpark users

2023-03-30 Thread Mridul Muralidharan
gt;>>>> >>>>>> >>>>>> >>>>>> Mich Talebzadeh 于2023年3月28日周二 07:07写道: >>>>>> >>>>>>> I created one at slack called pyspark >>>>>>> >>>>>>> >>>>>>>

Re: Slack for PySpark users

2023-03-30 Thread Bjørn Jørgensen
>>>>> >>>>>> >>>>>>view my Linkedin profile >>>>>> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> >>>>>> >>>>>> >>>>>> https://en.everybodywiki.com/Mich

Re: Slack for PySpark users

2023-03-30 Thread Mich Talebzadeh
gt;>> >>>>> >>>>> *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

Re: Slack for PySpark users

2023-03-30 Thread Dongjoon Hyun
ntent 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 wrote

Re: Slack for PySpark users

2023-03-30 Thread Xiao Li
;>> u...@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 >>>>> wrote: >>>>>

Re: Slack for PySpark users

2023-03-30 Thread Mich Talebzadeh
y damages >>> arising from such loss, damage or destruction. >>> >>> >>> >>> >>> On Tue, 28 Mar 2023 at 03:52, asma zgolli wrote: >>> >>>> +1 good idea, I d like to join as well. >>>> >>>> Le mar. 2

Re: Slack for PySpark users

2023-03-30 Thread Dongjoon Hyun
>>> +1 good idea, I d like to join as well. >>> >>> Le mar. 28 mars 2023 à 04:09, Winston Lai a >>> écrit : >>> >>>> Please let us know when the channel is created. I'd like to join :) >>>> >>>> Thank You &

Re: Slack for PySpark users

2023-03-30 Thread Mich Talebzadeh
t;> Please let us know when the channel is created. I'd like to join :) >>>> >>>> Thank You & Best Regards >>>> Winston Lai >>>> -- >>>> *From:* Denny Lee >>>> *Sent:* Tuesday, March 28, 2023 9:4

Re: Slack for PySpark users

2023-03-30 Thread Mich Talebzadeh
; Please let us know when the channel is created. I'd like to join :) >>>> >>>> Thank You & Best Regards >>>> Winston Lai >>>> -- >>>> *From:* Denny Lee >>>> *Sent:* Tuesday, March 28, 2023 9:43:08

Re: Slack for PySpark users

2023-03-30 Thread Xiao Li
t Regards >>> Winston Lai >>> -- >>> *From:* Denny Lee >>> *Sent:* Tuesday, March 28, 2023 9:43:08 AM >>> *To:* Hyukjin Kwon >>> *Cc:* keen ; u...@spark.apache.org < >>> u...@spark.apache.org> >>&g