From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 88C571382C5 for ; Sun, 23 May 2021 16:41:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 00A5FE0877; Sun, 23 May 2021 16:41:10 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B697DE0871 for ; Sun, 23 May 2021 16:41:09 +0000 (UTC) Date: Sun, 23 May 2021 11:41:05 -0500 From: John Helmert III To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Libera migration summary Message-ID: References: <12C07334-EBD2-4132-BCAE-B72D000B2AFD@gentoo.org> <48f002db-4b25-3d91-393a-e751452ce6e4@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="AP39XjvZ9FKThyfu" Content-Disposition: inline In-Reply-To: <48f002db-4b25-3d91-393a-e751452ce6e4@gentoo.org> X-Archives-Salt: 8755f00c-0d27-4f18-8c72-dc7424e8bc57 X-Archives-Hash: 4b48bbd502936071e89089d6b1a966d6 --AP39XjvZ9FKThyfu Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 23, 2021 at 06:20:40PM +0200, Thomas Deutschmann wrote: > Hi, >=20 > On 2021-05-22 18:37, Alec Warner wrote: > > So my biggest problem is again governance; is there any transparency=20 > > on continuity of *Libera* or will someone just sell it again in 2=20 > > years? >=20 > That's also my problem with Libera: I know they are new and ramping up a > new service but at the moment all we have are promises. I think it's obvious they're seasoned IRC network operators. Even if there are hiccups at first they're surely experienced enough to keep things going in the long term. > It's good to read they plan to create a non-profit organization but we > all know that this isn't easy. You have to do it first. >=20 > And having a non-profit organization is one thing (I actually don't care > about non-profit that much as long as I am not involved/contributing; > I.e. even a Ferengi might provide a good IRC service). I am more > interested in the organization itself. Who is owning the servers? Who is= =20 > in control? Who has access? >=20 >=20 > >> Reasons for migration to Libera: 1) Libera is the continuity > >> choice. irc.freenode.net has no relationship with the previous > >> freenode of the last 15 years other than the domain name and some > >> sponsored servers. (Libera is already building up sponsorship and > >> servers - it is not, as was alluded to on another thread, purely > >> cloud/their own infrastructure.) > >=20 > > I'm not sure what this means; how is Libera 'the continuity choice'? > > Is it: Because the ex-freenode staff have asked us to move there?=20 > > Because we have a strong relationship with that staff? Because many > > other projects are moving there? Some other reason? >=20 > Same thoughts. The relation ship is nice but in the end it has no value:= =20 > You can only look back at 15 years if things will change... not really=20 > an argument (see the distracted boyfriend meme). Also: I don't see any=20 > reason why we shouldn't be able to build up something similar with OFTC= =20 > for example. >=20 >=20 > > Sam wrote: > >> 2) We have a strong working relationship with the staff at Libera. > >>=20 > >> For example, they immediately reserved our namespace (this means > >> #gentoo-*) to prevent any hostile takeovers while we make > >> decisions. >=20 > All nice but not an argument either. >=20 >=20 > >> 3) The vast majority of developers are not involved in IRC > >> administration or indeed the migration efforts and may not be aware > >> of the actual issues involved with coordinating with a new team. We > >> are working with exactly the same people on Libera who understand=20 > >> what we require and have been working with us tirelessly to setup > >> new cloaks, channels, and other special arrangements. >=20 > Again, nice. But in case this should imply we can't have something=20 > similar with OFTC, this is wrong/disrespectful against other services=20 > (yes, you don't mean it that way, I just wanted to write it out). >=20 >=20 > >> 4) Compare this with the current state of #gentoo-groupcontacts on > >> Freenode which has 0 staff members. If we wanted to add/remove a > >> new developer, or handle any other issues, there is simply nobody > >> available to speak to. >=20 > Sorry, right now this is an invalid argument: Freenode staff stepped=20 > down. We cannot blame them, that they don't have people at the moment.=20 > If you say that 15y relationship have some value, we should grant=20 > freenode some time to get the current situation sorted. Not? Surely the "15y relationship" refers to the relationship with the people (who are no longer at Freenode) rather than the abstract of "Freenode". > But this is about freenode, I guess this train is moving so I can stop=20 > talking about freenode. >=20 >=20 > >> 5) Freenode is currently experiencing high turnover of new IRC > >> operators/administrators, some of which have dubious connections to > >> Rizon and other controversial IRC networks. It=E2=80=99s clear that, e= ven > >> if they are skilled individuals, they haven=E2=80=99t been trained on = the > >> current way of working at Freenode given they=E2=80=99re not in any of= the > >> usual mediums we use to handle *projects*. > >=20 > > Why is Rizon controversial? Note that freenode was attacked with > > spambots repeatedly in the past (GNAA, other attacks) and freenode > > admins struggled fighting the attacks for months. So why do we care > > about spambot attacks now, as opposed to in the past? Or are the > > attacks just a pretense we are using to move for other reasons? >=20 > I second your questions. I think the controversial is based on=20 > https://twitter.com/ariadneconill/status/1395347865271246853 >=20 >=20 > My problem with Libera.chat is, that I feel instrumentalized and I don't= =20 > want to get pulled into whatever is going on there. I think gyakovlev=20 > wrote, "This is not about who is right..." but it will become "who is=20 > right" if we follow former freenode staff. Is it a problem? I don't=20 > really now (how should anyone know that? All we have is hearsay/leaks we= =20 > cannot verify). Many Gentoo people probably don't know what happened=20 > many years ago=20 > (https://twitter.com/flameeyes/status/1395042943392751621). Why did we=20 > let that happen and had no discussion about moving away from freenode=20 > when one of us got attacked? But today, when Gentoo is not directly=20 > affected, we are happy to move? >=20 >=20 > >> 4) We=E2=80=99re not the only project to be moving. We=E2=80=99re far = =66rom being > >> the first large FOSS project to move. This means that *if*, in the > >> unlikely event this is the wrong decision, we=E2=80=99re in very good > >> company. We=E2=80=99re joined by Ubuntu and CentOS for a start. 5) Lar= ge > >> swathes of spambots continue to flood freenode given there's a > >> vacuum left by the lack of administration. >=20 > For me, this is the only but also strongest argument for Libera.Chat:=20 > IRC is only successful when our users are around. And users will be,=20 > where their projects are (nobody really wants to maintain multiple=20 > networks if not necessary, not?). So you will be in any Gentoo channel=20 > because you use Gentoo for example but when you have a problem with a=20 > KDE application, you just want to jump into KDE's support channel=20 > without switching network first... >=20 >=20 > >> Reasons against OFTC *for now*: 1) Lack of developer/project cloaks > >> (but dwfreed has indicated it=E2=80=99s _possible_ this can change in > >> future) > >>=20 > >> 2) Outdated/unconventional services and IRC daemon. This includes > >> lack of SASL support and unusual/missing features in e.g. > >> ChanServ. This is the general opinion in the =E2=80=9CIRC community=E2= =80=9D too. > >> Note that OFTC staff are trying to improve this but it will take > >> time. > >=20 > > What is the suboptimal outcome of this? I read this as "things are=20 > > different from freenode" which is not the same thing as "key > > features of chanserv are missing." If they are missing, what are > > they? >=20 > OFTC will be different, yes. But they already have a stable foundation=20 > and aren't built on promises that they have yet to prove. I am somewhat struggling to see a difference between the Freenode of "yesterday" and the Libera of today. Organizations tend to be the sum of their parts, in this case it's people. They've proven they're capable of running Freenode for a long time, I see no reason they wouldn't be able to do the same with a network of another name. > --=20 > Regards, > Thomas Deutschmann / Gentoo Linux Developer > fpr: C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5 >=20 --AP39XjvZ9FKThyfu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEElFuPenBj6NvNLoABXP0dAeB+IzgFAmCqhZ8ACgkQXP0dAeB+ IziZcw//Sxuq7LJr2cjAskbfFV31hOSaPaEq/LetkhKONHwHHD2DqLBztCOWEvcW wPsT87ZQlO+HEu536rzD79+BGx6huyS4FLWdx3P1eFjPwSY8bhR5SCwR3wJya+0B Jp4RKSt9Fiy6QijICVbWzQk3wfF/M8vhGvg6ZF39/V9SinumlLAlI/qxdCS4YMDP izqJz9BlQ7v0IdK6Q9FCFlip74gRAxmU39v/XqBPUHhbgqHxp8jCoedr0xiLOGIw nbaFuMSoFLvjLDVz9E5SqMVKrx+0xNE9tt75mx5zudzePQeMvibSwf/ACm12WaPr TnnLVc0f4+M/qUSirxwGrWirlVMnPslGpXbY79bJM2+gGREFARWNXGJ8dozpTt1D 3K3GcAPR02CIfhNnTfKCQXFUPPBHkkcO0OYuP1qtH+h5em5w5Uu+p521BlHQIRXv qFOrpJ+uPRCHcgfpD+o6G+kCICboTloLjl4YwuwZ5AKK+cAWVliYOh8eVX6nBAbh TNn35ZA5AYDiBrgqfLkQYS4yYffrkzMgr/pU2VgIacVI7MCiQD9/YVfDH8/3vuHD OvJICTqNunWvFPKVQeFh7ZOHDxIeqk2MzpgAz0tnYuaYZDZDrm3jK2IOsBABqMeq EnElSIK9GK7JCRjdxJFZWCvgLAQ4qi9zUK1Tws//evP0TiMjWgU= =z6Al -----END PGP SIGNATURE----- --AP39XjvZ9FKThyfu--