All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wladislav Artsimovich <vlad@frost.kiwi>
To: Simon Ser <contact@emersion.fr>, lyude@redhat.com
Cc: "mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>,
	members@x.org, "board@x.org" <board@x.org>,
	xorg-devel <xorg-devel@lists.x.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Mesa-dev] Freenode fallout
Date: Fri, 21 May 2021 16:11:58 +0200	[thread overview]
Message-ID: <7eb19738-1a51-930c-b6a2-c83d77168857@frost.kiwi> (raw)
In-Reply-To: <kqrCx-H3bt-9rRccwW7Vw2RGy6V_yvVxOw9-hFZ600mJ8kdC9KVAeWpWGbY1c3FbkLCjQ9HZagowdf_ZtqerRLE_u3bclwYcTad3tb4sxl4=@emersion.fr>

Indeed, a lot of communities are moving to Libera. However, 
centralization is what caused the mess with freenode in the first place, 
thus communities spreading to different services may not be such a bad 
idea. As long as the channels themselves are not split, that is.

On 21/05/2021 15:33, Simon Ser wrote:
> On Friday, May 21st, 2021 at 1:49 AM, Lyude Paul <lyude@redhat.com> wrote:
>
>> After considering Libera and OFTC as options, the board settled on
>> recommending OFTC. The primary reason for this is because OFTC is
>> associated with our parent foundation SPI, and has a long and well known
>> history of involvement with the open source community. As well, the
>> board believes OFTC's current Governance model is a lot more clear then
>> Libera's.
> I'd personally prefer Libera Chat. They don't yet have a published
> formal governance model, but I hope this will come soon. As the former
> Freenode staff, I trust them to make sure mistakes from the past won't
> be repeated.
>
> Apart from politics, Libera also offers a more modern feature set. This
> can ease daily usage, with features such as reliable authentication,
> account tracking, and many other IRC protocol improvements. OFTC has
> plans to eventually migrate to Solanum, but they don't have the time to
> do it for now.
>
> For reference, on OFTC:
>
>      CAP LS 302
>      :kinetic.oftc.net CAP * LS :multi-prefix
>
> And on Libera:
>
>      CAP LS 302
>      :ruthenium.libera.chat CAP * LS :account-notify away-notify chghost extended-join multi-prefix sasl=PLAIN,ECDSA-NIST256P-CHALLENGE,EXTERNAL tls userhost-in-names account-tag cap-notify echo-message solanum.chat/identify-msg solanum.chat/realhost
> _______________________________________________
> mesa-dev mailing list
> mesa-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev



      reply	other threads:[~2021-05-21 14:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 23:49 Lyude Paul
2021-05-21 13:33 ` Simon Ser
2021-05-21 14:11   ` Wladislav Artsimovich [this message]

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=7eb19738-1a51-930c-b6a2-c83d77168857@frost.kiwi \
    --to=vlad@frost.kiwi \
    --cc=board@x.org \
    --cc=contact@emersion.fr \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lyude@redhat.com \
    --cc=members@x.org \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=xorg-devel@lists.x.org \
    --subject='Re: [Mesa-dev] Freenode fallout' \
    /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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.