Skip to content

Commit

Permalink
doc: remove references to deleted freenode channels
Browse files Browse the repository at this point in the history
PR-URL: nodejs#39047
Reviewed-By: Robert Nagy <ronagy@icloud.com>
Reviewed-By: Mary Marchini <oss@mmarchini.me>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
Reviewed-By: Zijian Liu <lxxyxzj@gmail.com>
Reviewed-By: Khaidi Chu <i@2333.moe>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
  • Loading branch information
devsnek authored and foxxyz committed Oct 18, 2021
1 parent 3762ab9 commit 81c7ed2
Show file tree
Hide file tree
Showing 6 changed files with 6 additions and 27 deletions.
2 changes: 1 addition & 1 deletion .github/SUPPORT.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/)

Expand Down
2 changes: 0 additions & 2 deletions doc/guides/collaborator-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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

Expand Down
11 changes: 3 additions & 8 deletions doc/guides/contributing/pull-requests.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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).
Expand Down Expand Up @@ -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
Expand Down
3 changes: 1 addition & 2 deletions doc/guides/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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/
6 changes: 1 addition & 5 deletions doc/node.1
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
9 changes: 0 additions & 9 deletions onboarding.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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.

Expand Down

0 comments on commit 81c7ed2

Please sign in to comment.