archive mirror
 help / color / mirror / Atom feed
From: Martin Blumenstingl <>
Cc:, Neil Armstrong <>,,,
	Beniamino Galvani <>
Subject: #linux-amlogic IRC channel: move to Libera.Chat or OFTC?
Date: Wed, 26 May 2021 20:25:27 +0200	[thread overview]
Message-ID: <> (raw)


today the #linux-amlogic channel on Freenode was taken over by the
Freenode network administrators: [0]
I believe it is because the channel subject contained "Also on Libera.Chat".

Due to the recent events going on with Freenode other (large)
communities are also leaving Freenode, for example:
- Arch Linux: migrating to Libera.Chat
- OpenWrt: migrating to OFTC
- panfrost and lima drivers: migrating to OFTC
- (many more)

So I think we have two options:
1. Moving to Libera.Chat
2. Moving to OFTC
3. Trying to get back our "old" channel on Freenode

The steps (as far as I can tell) for switching to a new network are:
- creating #linux-amlogic on the new network (already done by Neil on
Libera.Chat and OFTC)
- inviting the whitequark IRC logger to the channel on the new network
- updating the topic of the new channel to inform users that all
messages are logged and the logs are available publicly
- updating our wiki with the new IRC network: [1]

I am not sure which steps need to be taken to get our "old" channel on
Freenode back.

What do you think?

Personally I vote for option #1 or #2.
I have no strong preference on which network to choose.

Best regards,


linux-amlogic mailing list

             reply	other threads:[~2021-05-26 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 18:25 Martin Blumenstingl [this message]
2021-05-26 19:24 ` #linux-amlogic IRC channel: move to Libera.Chat or OFTC? Jerome Brunet
2021-05-26 20:34   ` Martin Blumenstingl
2021-05-27  7:32 ` Neil Armstrong
2021-05-31  7:20   ` Neil Armstrong
2021-05-31 19:18     ` Martin Blumenstingl
2021-06-01  8:19       ` Neil Armstrong

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).