supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-skaware@skarnet.org>
To: "skaware@list.skarnet.org" <skaware@list.skarnet.org>,
	"supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: [announce] #s6 is moving from Freenode to OFTC
Date: Mon, 24 May 2021 19:57:27 +0000
Message-ID: <em93ecedf0-1f66-465d-bcdc-1b0e96bd2f9a@elzian> (raw)


  Hello,
  As some of you are aware of, last week, the Freenode IRC network was
subjected to a forceful change of its operational control. The history
and details of the change are deeply political in nature and very much
off-topic for our lists, and I really do not wish this event to be
discussed here; there is plenty of information and discussion to be had
in other corners of the Internet.
  The fact remains, however, that Freenode is no longer a safe IRC
network for free and open source software communities.
  As of now, the #s6 channel (and its associated off-topic channel) has
moved to the OFTC network: https://www.oftc.net/
  The skarnet.org documentation has been updated accordingly.
  Please update your pointers, and if you're currently hanging on
Freenode, please come to OFTC instead.
  The #s6 channel on Freenode will cease to be maintained, except for
a /topic  pointing to the new hosting network. At some point, it will
be moderated, i.e. you will not be able to write in it anymore.
  In the same way, there will be an empty #s6 channel on the libera.chat
network, pointing to the OFTC network as well.
  I know that some of you would have preferred to move to libera.chat,
the "official" successor of freenode, instead of OFTC. It was not an
easy choice to make, and no matter the decision, some people would
have ended up unhappy anyway. Please fight the undoubtedly overwhelming
urge to explain why the decision was wrong and the other one would have
been better; instead, feel free to address all complaints to Andrew Lee,
Crown Prince of Korea and originator of all this shitshow.
  Thank you. I hope to meet you on the other side.
--
  Laurent


                 reply	other threads:[~2021-05-24 19:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=em93ecedf0-1f66-465d-bcdc-1b0e96bd2f9a@elzian \
    --to=ska-skaware@skarnet.org \
    --cc=skaware@list.skarnet.org \
    --cc=supervision@list.skarnet.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

supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/supervision

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 supervision supervision/ http://inbox.vuxu.org/supervision \
		subscribe@list.skarnet.org
	public-inbox-index supervision

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.supervision.general


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git