From: Ulrich Mueller <ulm@gentoo.org>
To: "Michal Prívozník" <mprivozn@redhat.com>
Cc: gentoo-dev@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Should we switch IRC client defaults off Freenode?
Date: Wed, 16 Jun 2021 16:53:17 +0200 [thread overview]
Message-ID: <u4kdx97z6@gentoo.org> (raw)
In-Reply-To: <e970c143-9114-3fc9-c186-c0236883ee7f@redhat.com> ("Michal Prívozník"'s message of "Wed, 16 Jun 2021 13:28:26 +0200")
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
>>>>> On Wed, 16 Jun 2021, Michal Prívozník wrote:
>>> 1. Should we be proactively changing the default network in IRC clients
>>> (provided they have one) from Freenode to Libera.chat
>>
>> Yes. IMHO Freenode is no longer a reasonable default.
> Why should we mangle with packages this way? I mean, to me Gentoo was
> one of the few distros that allowed real choice for users (systemd vs
> openrc, selinux or !selinux, etc.). We shouldn't be making choices on
> behalf of users. The best we can do is to open issues for whatever IRC
> client we have in portage to switch from freenode to something
> different.
This is merely about the _default_ network, not about taking away any
choices from users.
See my answer to question 2 (which you've conveniently omitted,
therefore restoring it here):
>>> 2. Should we be proactively *removing* Freenode from the network list
>>> in IRC clients (provided they have one)?
>>
>> No (but also don't re-add it if upstream decided to remove it).
> BTW: not everybody is switching from freenode to libera.chat.
A default is never about everybody, but about providing a good
configuration for the majority of users.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2021-06-16 14:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 9:13 [gentoo-dev] [RFC] Should we switch IRC client defaults off Freenode? Michał Górny
2021-06-16 9:21 ` Ulrich Mueller
2021-06-16 9:24 ` Chris Pritchard
2021-06-16 11:28 ` Michal Prívozník
2021-06-16 13:04 ` Rich Freeman
2021-06-16 13:46 ` Thomas Deutschmann
2021-06-16 14:56 ` Ulrich Mueller
2021-06-16 14:53 ` Ulrich Mueller [this message]
2021-06-16 9:43 ` Joonas Niilola
2021-06-16 9:45 ` Michał Górny
2021-06-16 10:06 ` Andrew Ammerlaan
2021-06-16 10:22 ` Michał Górny
2021-06-16 10:53 ` Marek Szuba
2021-06-16 13:09 ` Hanno Böck
2021-06-16 15:03 ` Thomas Deutschmann
2021-06-16 15:42 ` Michał Górny
2021-06-16 15:57 ` Rich Freeman
2021-06-16 16:02 ` Michał Górny
2021-06-16 15:12 ` Sam James
2021-06-16 15:20 ` Sam James
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 \
--in-reply-to=u4kdx97z6@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@gentoo.org \
--cc=mprivozn@redhat.com \
/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