Re: Slack for PySpark users

2023-04-04 Thread Mich Talebzadeh
gt;>>>>>>>>> rocket chat is open source >>>>>>>>>>>>>> https://github.com/RocketChat/Rocket.Chat >>>>>>>>>>>>>> >>>>>>>>>>>>>> tor.

Re: Slack for PySpark users

2023-04-04 Thread Bjørn Jørgensen
t;>>>>>No, I don't have any reference from other official >>>>>>>>>>>>>> ASF-related Slack channels because I don't think that matters. >>>>>>>>>>>>>> However, I >>>>>>

Re: Slack for PySpark users

2023-04-04 Thread Mich Talebzadeh
;> Slack activities created an isolated silo outside of ASF mailing >>>>>>>>>>>>> list >>>>>>>>>>>>> archive... >>>>>>>>>>>>> Well, there are activities on Spark and indeed othe

Re: Slack for PySpark users

2023-04-03 Thread Dongjoon Hyun
e pragmatic. Unless there is an >>>>>>>>>>>> overriding reason, >>>>>>>>>>>> we should embrace it as slack can co-exist with the other mailing >>>>>>>>>>>> lists and >>>

Re: Slack for PySpark users

2023-04-03 Thread Denny Lee
Palantir Technologies Limited >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>view my Linkedin profile >>>>>>>>>>> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> >>

Re: Slack for PySpark users

2023-04-03 Thread Dongjoon Hyun
;>>>>>>>>> other >>>>>>>>>> property which may arise from relying on this email's technical >>>>>>>>>> content is >>>>>>>>>> explicitly disclaimed. The author will in no case be liable fo

Re: Slack for PySpark users

2023-04-03 Thread Mich Talebzadeh
ial ASF-related Slack >>>>>>>>>> channels? >>>>>>>>>> - To be clear, I intentionally didn't refer to any specific >>>>>>>>>> mailing list because we didn't set up any rule here yet. >>>>>>>

Re: Slack for PySpark users

2023-04-03 Thread Jungtaek Lim
>> >>>>>>>>> There is on-going discussion about the communication channels >>>>>>>>> outside ASF email which is specifically concerning Slack. >>>>>>>>> Please hold on any official action for this

Re: Slack for PySpark users

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

Re: Slack for PySpark users

2023-04-03 Thread Dongjoon Hyun
e is on-going discussion about the communication channels >>>>>>>>> outside ASF email which is specifically concerning Slack. >>>>>>>>> Please hold on any official action for this topic. We will know >>>>>>>>> how to support

Re: Slack for PySpark users

2023-04-03 Thread Mich Talebzadeh
gt;>>>>> 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 >>>>>>>&

Re: Slack for PySpark users

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

Re: Slack for PySpark users

2023-03-30 Thread Jungtaek Lim
t;>>>>> >>>>>>>> (cc Matei) >>>>>>>> >>>>>>>> Please hold on the vote. >>>>>>>> >>>>>>>> There is a concern expressed by ASF board because recent Slack

Re: Slack for PySpark users

2023-03-30 Thread Mich Talebzadeh
>>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Mar 29, 2023 at 11:32 PM Xiao Li >>>>>>> wrote: >>>>>>> >>>>>>>> +1 >>>>>>>> &

Re: Slack for PySpark users

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

Re: Slack for PySpark users

2023-03-30 Thread Mridul Muralidharan
;>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> 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
Lead >>>>>> Palantir Technologies Limited >>>>>> >>>>>> >>>>>>view my Linkedin profile >>>>>> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> >>>>>> >>>>>> >>>>

Re: Slack for PySpark users

2023-03-30 Thread Mich Talebzadeh
alebzadeh >>>>> >>>>> >>>>> >>>>> *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 rely

Re: Slack for PySpark users

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

Re: Slack for PySpark users

2023-03-30 Thread Xiao Li
med. 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: >>> >>>> +1 good idea, I d like to join as

Re: Slack for PySpark users

2023-03-30 Thread Mich Talebzadeh
ny monetary 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. 28 mars

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

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

Re: Slack for PySpark users

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

Re: Slack for PySpark users

2023-03-29 Thread Xiao Li
& Best 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>