From: Jens Axboe <[email protected]>
To: Jason Bowen <[email protected]>,
Gabriel Krisman Bertazi <[email protected]>,
Mathieu Masson <[email protected]>
Cc: [email protected]
Subject: Re: [Announcement] io_uring Discord chat
Date: Fri, 17 May 2024 18:43:55 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <2b21e1e5d78c0c34de555e840ce780d3b49f82d1.camel@infinitecactus.com>
On 5/17/24 6:25 PM, Jason Bowen wrote:
>> I'm really open to whatever, however I do think it's a good sign if
>> an existing similar community is already using zulip. But as is
>> customary, whoever does the work and sets it up, gets to choose :-)
>
> Not to be that guy (and I'm just a lurker/observer [for now, at least],
> so feel free to ignore me), but a lot of the other kernel communities
> are using IRC (generally libera.chat or oftc.net).
IRC was fine in the 90s, honestly things have moved on. It's not usable
without some kind of intermediary that makes it work disconnected, and
it's not searchable without having logging separately too. So hard pass
on IRC. I used to use it a lot, but decades ago, and even the use I
still have today is pretty miserable.
> I may be wrong, but I'd suspect some in the community are leery of
> closed platforms like Discord.
And probably rightfully so, but at least we have other suggestions in
the thread now which seem more tenable imho.
> P.S. relevant xkcd: https://xkcd.com/1782/
Right, and not exactly in favor of IRC :-)
--
Jens Axboe
next prev parent reply other threads:[~2024-05-18 0:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 0:25 [Announcement] io_uring Discord chat Jason Bowen
2024-05-18 0:43 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-17 18:51 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
2024-05-18 0:52 ` David Wei
2024-05-18 8:31 ` Mathieu Masson
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] \
[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