diff --git a/.github/SUPPORT.md b/.github/SUPPORT.md index d3af8e681917a0..51f8a326531ed4 100644 --- a/.github/SUPPORT.md +++ b/.github/SUPPORT.md @@ -16,7 +16,7 @@ resources: * [Questions tagged 'node.js' on Stack Overflow](https://stackoverflow.com/questions/tagged/node.js) * [#nodejs](https://openjs-foundation.slack.com/archives/CK9Q4MB53) channel on the OpenJS Foundation Slack ([join here](https://slack-invite.openjsf.org/)) -* [#node.js channel on chat.freenode.net](https://webchat.freenode.net?channels=node.js&uio=d4) +* [#node.js channel on libera.chat](https://web.libera.chat?channels=node.js&uio=d4) * [Node.js Slack Community](https://node-js.slack.com/) * To register: [nodeslackers.com](https://www.nodeslackers.com/) diff --git a/doc/guides/collaborator-guide.md b/doc/guides/collaborator-guide.md index 2791d2a2e508ed..ae860f6446eb6f 100644 --- a/doc/guides/collaborator-guide.md +++ b/doc/guides/collaborator-guide.md @@ -726,7 +726,6 @@ git push upstream master ### I made a mistake * Ping a TSC member. -* `#node-dev` on freenode. * With `git`, there's a way to override remote trees by force pushing (`git push -f`). This is generally forbidden as it creates conflicts in other people's forks. It is permissible for simpler slip-ups such as typos in commit @@ -735,7 +734,6 @@ git push upstream master 10-minute period passes, consider the commit final. * Use `--force-with-lease` to reduce the chance of overwriting someone else's change. - * Post to `#node-dev` (IRC) if you force push. ### Long Term Support diff --git a/doc/guides/contributing/pull-requests.md b/doc/guides/contributing/pull-requests.md index 32411eb96b5010..5f31bab0cfa9a7 100644 --- a/doc/guides/contributing/pull-requests.md +++ b/doc/guides/contributing/pull-requests.md @@ -51,11 +51,8 @@ help, questions and discussions. [#nodejs-dev](https://openjs-foundation.slack.com/archives/C019Y2T6STH) for development of Node.js core specifically. -Node.js also has two IRC channels: -[#Node.js](https://webchat.freenode.net/?channels=node.js) for general help and -questions, and -[#node-dev](https://webchat.freenode.net/?channels=node-dev) for development of -Node.js core specifically. +Node.js also has an unofficial IRC channel: +[#Node.js](https://web.libera.chat/?channels=node.js). ## Setting up your local environment @@ -298,8 +295,7 @@ $ git push --force-with-lease origin my-branch **Important:** The `git push --force-with-lease` command is one of the few ways to delete history in `git`. Before you use it, make sure you understand the -risks. If in doubt, you can always ask for guidance in the Pull Request or on -[IRC in the #node-dev channel][]. +risks. If in doubt, you can always ask for guidance in the Pull Request. If you happen to make a mistake in any of your commits, do not worry. You can amend the last commit (for example if you want to change the commit log). @@ -593,7 +589,6 @@ More than one subsystem may be valid for any particular issue or pull request. [CI (Continuous Integration) test run]: #ci-testing [Code of Conduct]: https://github.com/nodejs/admin/blob/HEAD/CODE_OF_CONDUCT.md [Collaborator Guide]: ../collaborator-guide.md -[IRC in the #node-dev channel]: https://webchat.freenode.net?channels=node-dev&uio=d4 [Onboarding guide]: ../../../onboarding.md [approved]: #getting-approvals-for-your-pull-request [benchmark results]: ../writing-and-running-benchmarks.md diff --git a/doc/guides/releases.md b/doc/guides/releases.md index eac14469a09a2f..832b8c8eda0680 100644 --- a/doc/guides/releases.md +++ b/doc/guides/releases.md @@ -128,7 +128,7 @@ Build is essential to make sure that the CI works, release files are published, and the release blog post is available on the project website. Build can be contacted best by opening up an issue on the [Build issue -tracker][], and by posting in `#node-build` on [webchat.freenode.net][]. +tracker][]. When preparing a security release, contact Build at least two weekdays in advance of the expected release. To ensure that the security patch(es) can be @@ -912,4 +912,3 @@ take place once a new LTS line has been released. [Snap]: https://snapcraft.io/node [nodejs.org release-post.js script]: https://github.com/nodejs/nodejs.org/blob/HEAD/scripts/release-post.js [nodejs.org repository]: https://github.com/nodejs/nodejs.org -[webchat.freenode.net]: https://webchat.freenode.net/ diff --git a/doc/node.1 b/doc/node.1 index 1961ac4ffafbba..319532f50ecfa7 100644 --- a/doc/node.1 +++ b/doc/node.1 @@ -691,13 +691,9 @@ GitHub repository & Issue Tracker: . .Pp IRC (general questions): -.Sy "chat.freenode.net #node.js" +.Sy "libera.chat #node.js" (unofficial) . -.Pp -IRC (Node.js core development): -.Sy "chat.freenode.net #node-dev" -. .\"====================================================================== .Sh AUTHORS Written and maintained by 1000+ contributors: diff --git a/onboarding.md b/onboarding.md index a70f2157eaefed..d1eca3a4c40f79 100644 --- a/onboarding.md +++ b/onboarding.md @@ -59,12 +59,6 @@ onboarding session. The project has two venues for real-time discussion: * [`#nodejs-dev`](https://openjs-foundation.slack.com/archives/C019Y2T6STH) on the [OpenJS Foundation](https://slack-invite.openjsf.org/) -* `#node-dev` on [webchat.freenode.net](https://webchat.freenode.net/) is a - great place to interact with the TSC and other Collaborators - * If there are any questions after the session, a good place to ask is - there! - * Presence is not mandatory, but please drop a note there if force-pushing - to `master` ## Project goals & values @@ -185,9 +179,6 @@ The project has two venues for real-time discussion: `7006` in the `PR_ID`. * The remaining elements on the form are typically unchanged. * If you need help with something CI-related: - * Use #node-dev (IRC) to talk to other Collaborators. - * Use #node-build (IRC) to talk to the Build WG members who maintain the CI - infrastructure. * Use the [Build WG repo](https://github.com/nodejs/build) to file issues for the Build WG members who maintain the CI infrastructure.