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
Comments
Many others are also moving away from Freenode: https://twitter.com/TwitchiH/status/1395139030313017345 |
cc @golang/osp-team |
We are in the process of registering |
Change https://golang.org/cl/321731 mentions this issue: |
The channel was just forced out of the hands of the go community. I guess that freenode made this decision for us. |
Indeed, we need to move: https://mastodon.sdf.org/@kline/106299403921451814 |
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. |
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. |
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>
The updated https://golang.org/help page is deployed, closing. |
I will finalize the cutover of the freenode channel later today. Thanks for updating the site. |
Change https://golang.org/cl/325450 mentions this issue: |
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>
Change https://golang.org/cl/336931 mentions this issue: |
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>
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.)
The text was updated successfully, but these errors were encountered: