Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/website: update the #go-nuts IRC channel server #46281

Closed
seebs opened this issue May 20, 2021 · 12 comments
Closed

x/website: update the #go-nuts IRC channel server #46281

seebs opened this issue May 20, 2021 · 12 comments
Labels
Community FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@seebs
Copy link
Contributor

seebs commented May 20, 2021

Not so much the language, as: There's IRC drama involving freenode, and the Go web page says that, for real-time help, people should use the "official" IRC channel, #go-nuts on freenode. I'm not sure that's still the right place; most of the historical freenode ops have left, and the person still running things has put up announcements about this, and I don't know whether or not this has implications from the Go team's perspective, but I think it's at least worth waving this at people and asking what "official" means.

some statements:

Andrew Lee: https://freenode.net/news/freenode-is-foss
edk: https://gist.github.com/edk0/478fb4351bc3ba458288d6878032669d
fuchs: https://fuchsnet.ch/freenode-resign-letter.txt

I don't even know how to begin on this. (For what it's worth, though, I wasn't sure until I read Lee's post, but given that, I stopped using freenode and have migrated the tabs I had on various channels to libera.chat or oftc depending on where their respective communities went.)

@theckman
Copy link
Contributor

Many others are also moving away from Freenode: https://twitter.com/TwitchiH/status/1395139030313017345

@seankhliao seankhliao added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 20, 2021
@seankhliao
Copy link
Member

cc @golang/osp-team

@dmitshur dmitshur added this to the Unreleased milestone May 20, 2021
@SamWhited
Copy link
Member

SamWhited commented May 21, 2021

We are in the process of registering #go-nuts on Libera.chat as a community or project. It would be good to have it listed on the website either way, and if we could get a core team member to verify that they're okay with it we can register as a project instead which gives us some added benefits (https://libera.chat/chanreg). If anyone from the Go team is interested, please reach out to me (Sam on libera.chat, or sam@samwhited.com via email or XMPP)

@gopherbot
Copy link

Change https://golang.org/cl/321731 mentions this issue: _content/doc: update IRC server

@A-UNDERSCORE-D
Copy link

The channel was just forced out of the hands of the go community. I guess that freenode made this decision for us.

@4ad
Copy link
Member

4ad commented May 26, 2021

Indeed, we need to move: https://mastodon.sdf.org/@kline/106299403921451814

@danderson
Copy link
Contributor

Ohai, one of the owners/operators of #go-nuts on freenode here. So, freenode has started taking a moderation policy that's pretty hostile to the ideals of the Go project (in particular, removal of bans on hate speech and various other such things), and as a couple folks mentioned, a few hours ago they unilaterally nuked #go-nuts, along with 700+ other channels of OSS projects, on the basis that its topic contained the string "libera".

After a lot of confusion and wading through hundreds of other angry channel owners, I was able to regain ownership of #go-nuts, but at this point it's fairly clear that freenode is a hostile environment to operate in, even by IRC's standards.

There are currently 20 people on the freenode channel, and 286 people on the libera channel. It seems like the community's already voted with its feet. All that remains is to update golang.org (https://go-review.googlesource.com/c/website/+/321731) and turn out the lights on the freenode channel. I have the IRC permission bits to do the latter, but I want to keep the channel around on life support as long as it's being referenced from golang.org. I defer to @golang/osp-team from here on, think of me as your consensus-driven sudo on freenode.

@dmitshur
Copy link
Contributor

Thanks for reporting this and providing relevant information. This is indeed rather unfortunate, and I appreciate everyone's support with helping find a good resolution to this for the Go project.

Thanks for sending CL 321731 for this issue. Based on the information and feedback I'm seeing, it seems we should proceed with the change proposed there. The review comments I left there have already been addressed, so we can submit it soon, which will close this issue.

@dmitshur dmitshur changed the title website: freenode/#go-nuts still the "official" golang IRC channel? x/website: update the #go-nuts IRC channel server May 26, 2021
@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels May 26, 2021
gopherbot pushed a commit to golang/website that referenced this issue May 27, 2021
See golang/go#46281

Change-Id: I35628633e47d92aa449d73512f80ed6326405229
GitHub-Last-Rev: 0013cd4
GitHub-Pull-Request: #53
Reviewed-on: https://go-review.googlesource.com/c/website/+/321731
Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Trust: Josh Bleecher Snyder <josharian@gmail.com>
Trust: Brad Fitzpatrick <bradfitz@golang.org>
@dmitshur
Copy link
Contributor

The updated https://golang.org/help page is deployed, closing.

@danderson
Copy link
Contributor

I will finalize the cutover of the freenode channel later today. Thanks for updating the site.

@gopherbot
Copy link

Change https://golang.org/cl/325450 mentions this issue: _content/.well-known: register libera.chat project

gopherbot pushed a commit to golang/website that referenced this issue Jun 8, 2021
The libera.chat folks have asked that we verify our chat room by temporarily (I will make the follow up to remove this) placing this string in the well-known tree. This would allow the `#go-nuts` channel to have certain protections including reservig the name `#go-*` and the ability to continue using the single `#` (instead of the two ##s for unverified channels). Is it possible the Go team would be okay with merging this temporarily? Thank you.

See golang/go#46281

/cc @danderson

Change-Id: I45e2a658c473e94c4ba6a03e68df02d68273cfa2
GitHub-Last-Rev: 7150aad
GitHub-Pull-Request: #58
Reviewed-on: https://go-review.googlesource.com/c/website/+/325450
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Trust: Cherry Mui <cherryyz@google.com>
@gopherbot
Copy link

Change https://golang.org/cl/336931 mentions this issue: .github: update IRC server

gopherbot pushed a commit that referenced this issue Sep 30, 2021
Updates #46281

Change-Id: I1c70ad72a155a39138f120df5b71de61bb01e20c
Reviewed-on: https://go-review.googlesource.com/c/go/+/336931
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Daniel Martí <mvdan@mvdan.cc>
Trust: Ian Lance Taylor <iant@golang.org>
Trust: Daniel Martí <mvdan@mvdan.cc>
@golang golang locked and limited conversation to collaborators Jul 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Community FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

9 participants