public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Should we switch IRC client defaults off Freenode?
Date: Wed, 16 Jun 2021 17:03:12 +0200	[thread overview]
Message-ID: <f4506672-9b86-d85d-6e19-8fcf05300ee0@gentoo.org> (raw)
In-Reply-To: <d6587901f5c4d1f9355130066964de06b3913e22.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 3879 bytes --]

On 2021-06-16 11:13, Michał Górny wrote:
> 1. Should we be proactively changing the default network in IRC clients
> (provided they have one) from Freenode to Libera.chat?
> 
> 1a. If yes, then should we also make a change if clients default to
> network other than Freenode?

Adding *our* network in case Libera.chat is missing, is one thing. Like 
adding branding for Gentoo.

But imagine the project behind the IRC client is located on EFnet and 
therefore they are defaulting their client to EFnet, we shouldn't mess 
with that because of the Freenode drama. There should be a separate 
discussion if we should add Gentoo branding by default to *every* 
package where possible in which case we can think about it.


> 2. Should we be proactively *removing* Freenode from the network list
> in IRC clients (provided they have one)?

No. Don't become part of a cancel culture where you disagree with 
someone and start to fight your enemy. We moved and are done with 
freenode. Gentoo is about choices. Our users should therefore be able to 
decide on their own. No need to make it harder to connect to a network 
we moved away from. And keep in mind: *Not* everyone has moved away from 
freenode, that's also part of the truth. And we shouldn't judge projects 
still located on freenode.


> 2a. Should we be adding Libera.chat to the list even if we do not remove
> Freenode?

See 1.


> Quick recap for people that haven't been following the news or got
> confused in the lots of data:
> 
> 1. Freenode was sold in 2017 to some guy who apparently wasn't supposed
> to interfere with its operations.
> 
> 2. In 2021, the guy actively started to interfere, then formed a one-man
> Board and demanded full compliance.

The problem with a summary like that is, that you only present one view. 
I.e. the view of the "winner" (history is written by the victors). But 
part of the drama is that freenode owner said he was forced to take 
actions for legal reasons (new owner is held liable for whatever his 
staff is doing) after former staff refused to cooperate.


> 5. New Freenode staff (including some disreputable types) went angry
> about this and started automated reclamation of channels that indicated
> move to another network (including some channels that didn't because
> they failed at grep).

You could also have a different view on that: We (like many others) 
started to violate their TOS. It does not matter whether or not they 
created these TOS retrospectively: It's a proprietary/privately owned 
service. They can do whatever they like whenever they like. And they 
just did that. No question, an unpleasant move from our POV. But I know 
that many people don't like to hear or believe for some reasons that 
this could never happen to other services -- but this can happen at any 
time to our presence at Github and even what happened with freenode 
could happen with Libera.chat again. Both are proprietary and in the end 
privately owned. They can change rules without asking us and without 
even considering our interests.


> Just imagine unknowing Gentoo users having their systems compromised
> through advice from trolls pretending to be Gentoo developers.

True. But this can happen wherever people talk about Gentoo. Even in our 
forums, mailing lists or official IRC channels. I would recommend 
everyone to relax a little bit. There will always be some imperfect 
situations like that we cannot control. We shouldn't start to overreact. 
Like we say, "Gentoo is about choice", have some faith in our users to 
deal with that.

Gentoo is done with freenode, we migrated away. There is no need for us 
take additional actions against freenode.


-- 
Regards,
Thomas Deutschmann / Gentoo Linux Developer
fpr: C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  parent reply	other threads:[~2021-06-16 15:03 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
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 [this message]
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=f4506672-9b86-d85d-6e19-8fcf05300ee0@gentoo.org \
    --to=whissi@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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