From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: we moved #xfs to oftc
Date: Tue, 25 May 2021 22:03:48 -0700 [thread overview]
Message-ID: <20210526050348.GW202121@locust> (raw)
Hi folks,
We've moved the #xfs IRC channel to OFTC due to all the recent freenode
drama. Let us know if you can't join the new channel. At some point we
might have to make the access stricter (like we did on freenode) to stop
the bot spam, but in theory it should be easy to get in the new channel.
Please do not continue to use the old freenode channel.
Some Q&A:
- Why not post a notice in #xfs, you ask?
A short while ago, the btrfs folks found out the hard way that if you
leave any /topic breadcrumbs pointing people from freenode to another
network, the new admins will declare a policy violation, strip everyone
of channel op privileges, kick everyone off the channel, and erase the
topic. We'll see how long "10 GOTO OTFC" lasts.
- Why not post a notice on the XFS wiki, you ask?
AFAIK nobody don't have write privileges.
- Why not post a notice on the /new/ XFS wiki, you ask?
The Linux Foundation required us to use their SSO service, which they
are now transitioning to a new third party provider, which means that
nobody can log in anymore.
- Why not use Matrix or something?
The LF have hinted that they might set up an instance, but nothing
concrete has come of that. We could in theory decide ultimately to move
there, but until they make a public announcement, there's nothing for
public to do. Also see previous answer.
--D
reply other threads:[~2021-05-26 5:03 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=20210526050348.GW202121@locust \
--to=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.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