public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Mathieu Masson <[email protected]>
Cc: Gabriel Krisman Bertazi <[email protected]>, [email protected]
Subject: Re: [Announcement] io_uring Discord chat
Date: Fri, 17 May 2024 17:51:17 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 5/17/24 4:24 PM, Mathieu Masson wrote:
> On 17 mai 13:09, Jens Axboe wrote:
>> On 5/17/24 12:51 PM, Gabriel Krisman Bertazi wrote:
>>> Following our LSFMM conversation, I've created a Discord chat for topics
>>> that could benefit from a more informal, live discussion space than the
>>> mailing list might offer.  The idea is to keep this new channel alive for a
>>> while and see if it does indeed benefit the broader io_uring audience.
>>>
>>> The following is an open invite link:
>>>
>>>  https://discord.gg/8EwbZ6gkfX
>>
>> Great initiative!
>>
>>> Which might be revoked in the future.  If it no longer works, drop me an
>>> email for a new one.
>>>
>>> Once we have some key people around, I intend to add an invite code to
>>> the liburing internal documentation.
>>
>> Is it public - and if not, can it be? Ideally I'd love to have something
>> that's just open public (and realtime) discussion, ideally searchable
>> from your favorite search engine. As the latter seems
>> difficult/impossible, we should at least have it be directly joinable
>> without an invite link. Or maybe this is not how discord works at all,
>> and you need the invite link? If so, as long as anyone can join, then
>> that's totally fine too I guess.
>>
> 
> Not to start any form of chat platform war, but the rust-for-linux community has
> been using Zulip for a while now. At some point they made the full message
> history live accessible without an account :
> 
> https://rust-for-linux.zulipchat.com/

Not a war at all, the only ones I could think of were discord and slack.
So really appreciate the input!

> It is even search-able apparently, which is quite appreciable as an
> outsider who just wants to follow a bit in a more informal way than
> the ML.

Yep, this is exactly why I brought that up both here and in person,
being searchable is really key imho. It allows people to find past
discussions by searching for similar keywords.

-- 
Jens Axboe


  parent reply	other threads:[~2024-05-17 23:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 18:51 [Announcement] io_uring Discord chat Gabriel Krisman Bertazi
2024-05-17 19:09 ` Jens Axboe
2024-05-17 19:44   ` Gabriel Krisman Bertazi
2024-05-17 19:46     ` Jens Axboe
2024-05-17 22:24   ` Mathieu Masson
2024-05-17 23:03     ` Gabriel Krisman Bertazi
2024-05-17 23:52       ` Jens Axboe
2024-05-17 23:51     ` Jens Axboe [this message]
2024-05-18  0:52     ` David Wei
2024-05-18  8:31       ` Mathieu Masson
  -- strict thread matches above, loose matches on Subject: below --
2024-05-18  0:25 Jason Bowen
2024-05-18  0:43 ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox