Hi Mich,If repeated discussions indicate anything, it is that there is no consensus among maintainers regarding using Slack as an *official* communication channel. So which members and whose democracy are w talking about? I don't recall any vote... Oh, and when did we become a democracy anyway? :)
All the concerns raised across preceding discussions seem valid and were not properly addressed. One could add a few more (from privacy to long-term sustainability, not to mention other projects failures), but it is pointless if there is no agreement about what has been already discussed. Additionally, I recall at least a few Spark-related communities (Slack, gitter) that emerged over the last 10 years or so and proved to be not so resilient after all.
That being said, it is perfectly OK to have unofficial channels that can reduce the need for support from the contributors. At this point, the project is mature and has quite stable API and solutions to common problems are well documented. At the same time, users are more likely to encounter problems with platforms vendor's distributions and our lists are not the and our lists are not the place to provide support for this anyway. If sparkcommunitytalk can become such a place (and save us further discussions on the topic) that's great, but please let's not confuse it with the official channel, especially when its current activity doesn't justify claims of its de facto legitimacy.
On 4/6/23 08:49, Mich Talebzadeh wrote:
Reminds me of a case offlogging a dead horse. <https://en.wikipedia.org/wiki/Flogging_a_dead_horse>This has already been discussed many times and there is no need for further discussion or summary. The newly created stack community sparkcommunitytalk.slack.com <http://sparkcommunitytalk.slack.com/> is a reality and is there to stay. I don't see any competition with dev or user mailing lists. Please respect members' democratic values.Mich Talebzadeh, Lead Solutions Architect/Engineering Lead Palantir Technologies London United Kingdom**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 Thu, 6 Apr 2023 at 06:51, Dongjoon Hyun <dongjoon.h...@gmail.com> wrote:Thank you so much, Denny. Yes, let me comment on a few things. > - While there is an ASF Slack <https://infra.apache.org/slack.html>, it > requires an @apache.org <http://apache.org> email address 1. This sounds a little misleading because we can see `guest` accounts in the same link. People can be invited by "Invite people to ASF" link. I invited you, Denny, and attached the screenshots. > using linen.dev <http://linen.dev> as its Slack archive (so we can surpass the 90 days limit) 2. The official Foundation-supported Slack workspace preserves all messages. (the-asf.slack.com <http://the-asf.slack.com>) > Why: Allows for the community to have the option to communicate with each > other using Slack; a pretty popular async communication. 3. ASF foundation not only allows but also provides the option to communicate with each other using Slack as of today. Given the above (1) and (3), I don't think we asked the right questions during most of the parts. 1. Shall we narrow-down our focus on comparing the ASF Slack vs another 3rd-party Slack because all of us agree that this is important? 2. I'm wondering what ASF misses here if Apache Spark PMC invites all remaining subscribers of `user@spark` and `dev@spark` mailing lists. Thanks, Dongjoon. invitation.png invited.png On Wed, Apr 5, 2023 at 7:23 PM Denny Lee <denny.g....@gmail.com> wrote: There have been a number of threads discussing creating a Slack for the Spark community that I'd like to try to help reconcile. Topic: Slack for Spark Why: Allows for the community to have the option to communicate with each other using Slack; a pretty popular async communication. Discussion points: * There are other ASF projects that use Slack including Druid <https://druid.apache.org/community/>, Parquet <https://parquet.apache.org/community/>, Iceberg <https://iceberg.apache.org/community/>, and Hudi <https://hudi.apache.org/community/get-involved/> * Flink <https://flink.apache.org/community/> is also using Slack and using linen.dev <http://linen.dev> as its Slack archive (so we can surpass the 90 days limit) which is also Google searchable (Delta Lake <https://www.linen.dev/s/delta-lake/> is also using this service as well) * While there is an ASF Slack <https://infra.apache.org/slack.html>, it requires an @apache.org <http://apache.org> email address to use which is quite limiting which is why these (and many other) OSS projects are using the free-tier Slack * It does require managing Slack properly as Slack free edition limits you to approx 100 invites. One of the ways to resolve this is to create a bit.ly <http://bit.ly> link so we can manage the invites without regularly updating the website with the new invite link. Are there any other points of discussion that we should add here? I'm glad to work with whomever to help manage the various aspects of Slack (code of conduct, linen.dev <http://linen.dev> and search/archive process, invite management, etc.). HTH! Denny
-- Best regards, Maciej Szymkiewicz Web:https://zero323.net PGP: A30CEF0C31A501EC
OpenPGP_signature
Description: OpenPGP digital signature
