Thank you, Chitral. Dongjoon
On Mon, Apr 10, 2023 at 12:08 AM Chitral Verma <chitralve...@gmail.com> wrote: > Hi all, > Thanks for starting a discussion on this super-important topic. > > I'm not sure if this is already considered, but Discord is also a viable > option and many many open-source projects and communities are using it. > > - It's *mostly* free with no online user limitations like slack. > - Has a big feature overlap with Slack. > - Sign up process is simple and straightforward. Clients for web/ > desktop/ mobile are available. > - Policies and controlling can be possibly done via bots + designated > channel managers. > - allows channels like Slack for the organisation of messages. > > > On Mon, 10 Apr 2023 at 08:09, Dongjoon Hyun <dongjoon.h...@gmail.com> > wrote: > >> Thank you, Holden, Bjorn, Maciej. >> >> Yes, those are also valid. >> >> Dongjoon. >> >> On Sat, Apr 8, 2023 at 4:20 AM Maciej <mszymkiew...@gmail.com> wrote: >> >>> @Bjørn Matrix (represented by element in the linked summary. Also, since >>> the last year, Rocket Chat uses Matrix under the hood) is already used for >>> user support and related discussions for a number of large projects, since >>> gitter migrated there. And it is not like we need Slack or its replacement >>> in the first place. Some of the Slack features are useful for us, but its >>> not exactly the best tool for user support IMHO. >>> >>> @Dongjoon There are probably two more things we should discuss: >>> >>> - What are data privacy obligations while keeping a communication >>> channel, advertised as official, outside the ASF? Does it put it out of >>> scope for the ASF legal and data privacy teams? >>> >>> If I recall correctly, Slack requires at least some of the >>> formalities to be handled by the primary owner and as far as I am aware >>> the >>> project is not a legal person. Not sure how linen.dev or another >>> retention tool fits into all of that, but it's unrealistic to expect it >>> makes things easier. >>> >>> This might sound hypothetical, but we've already seen users leaking >>> sensitive information on the mail list and requesting erasure (which, >>> luckily for us, is not technically possible). >>> >>> - How are we going to handle moderation, if we assume number of >>> users comparable to Delta Lake Slack and open registration? At minimum we >>> have to ensure that the ASF Code of Conduct is respected. An official >>> channel or not, failure to do that reflects badly on the project, the ASF >>> and all of us. >>> >>> -- >>> Maciej >>> >>> >>> >>> On 4/7/23 21:02, Bjørn Jørgensen wrote: >>> >>> Yes, I have done some search for slack alternatives >>> <https://itsfoss.com/open-source-slack-alternative/> >>> I feel that we should do some search, to find if there can be a >>> better solution than slack. >>> For what I have found, there are two that can be an alternative for >>> slack. >>> >>> Rocket.Chat <https://www.rocket.chat/> >>> >>> and >>> >>> Zulip Chat <https://zulip.com> >>> Zulip Cloud Standard is free for open-source projects >>> <https://zulip.com/for/open-source/> >>> Witch means we get >>> >>> - Unlimited search history >>> - File storage up to 10 GB per user >>> - Message retention policies >>> <https://sparkzulip.zulipchat.com/help/message-retention-policy> >>> - Brand Zulip with your logo >>> - Priority commercial support >>> - Funds the Zulip open source project >>> >>> >>> Rust is using zulip <https://forge.rust-lang.org/platforms/zulip.html> >>> >>> We can import chats from slack >>> <https://sparkzulip.zulipchat.com/help/import-from-slack> >>> We can use zulip for events <https://zulip.com/for/events/> With multi-use >>> invite links <https://zulip.com/help/invite-new-users>, there’s no need >>> to create individual Zulip invitations. This means that PMC doesn't have >>> to send a link to every user. >>> CODE BLOCKS >>> >>> Discuss code with ease using Markdown code blocks, syntax highlighting, >>> and code playgrounds >>> <https://zulip.com/help/code-blocks#code-playgrounds>. >>> >>> >>> >>> >>> >>> >>> fre. 7. apr. 2023 kl. 18:54 skrev Holden Karau <hol...@pigscanfly.ca>: >>> >>>> I think there was some concern around how to make any sync channel show >>>> up in logs / index / search results? >>>> >>>> On Fri, Apr 7, 2023 at 9:41 AM Dongjoon Hyun <dongjoon.h...@gmail.com> >>>> wrote: >>>> >>>>> Thank you, All. >>>>> >>>>> I'm very satisfied with the focused and right questions for the real >>>>> issues by removing irrelevant claims. :) >>>>> >>>>> Let me collect your relevant comments simply. >>>>> >>>>> >>>>> # Category 1: Invitation Hurdle >>>>> >>>>> > The key question here is that do PMC members have the bandwidth of >>>>> inviting everyone in user@ and dev@? >>>>> >>>>> > Extending this to inviting everyone on @user (over >4k subscribers >>>>> according to the previous thread) might be a stretch, >>>>> >>>>> > we should have an official project Slack with an easy invitation >>>>> process. >>>>> >>>>> >>>>> # Category 2: Controllability >>>>> >>>>> > Additionally. there is no indication that the-asf.slack.com is >>>>> intended for general support. >>>>> >>>>> > I would also lean towards a standalone workspace, where we have more >>>>> control over organizing the channels, >>>>> >>>>> >>>>> # Category 3: Policy Suggestion >>>>> >>>>> > *Developer* discussions should still happen on email, JIRA and >>>>> GitHub and be async-friendly (72-hour rule) to fit the ASF’s development >>>>> model. >>>>> >>>>> >>>>> Are there any other questions? >>>>> >>>>> >>>>> Dongjoon. >>>>> >>>>> >>>>> -- >>>> Twitter: https://twitter.com/holdenkarau >>>> Books (Learning Spark, High Performance Spark, etc.): >>>> https://amzn.to/2MaRAG9 <https://amzn.to/2MaRAG9> >>>> YouTube Live Streams: https://www.youtube.com/user/holdenkarau >>>> >>> >>> >>> -- >>> Bjørn Jørgensen >>> Vestre Aspehaug 4, 6010 Ålesund >>> Norge >>> >>> +47 480 94 297 >>> >>> >>>
