FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

doc: remove IRC from man page by tniessen · Pull Request #53344 · nodejs/node · GitHub

/ node Public

doc: remove IRC from man page - #53344

Merged
nodejs-github-bot merged 1 commit into
nodejs:mainfrom
tniessen:doc-man-page-irc
Jun 7, 2024
Merged

doc: remove IRC from man page#53344
nodejs-github-bot merged 1 commit into
nodejs:mainfrom
tniessen:doc-man-page-irc

Conversation

tniessen commented Jun 5, 2024

Copy link
Copy Markdown
Member

Our community communication channels come and go, whether that's Freenode or Libera or Slack or whatever other community channels there were at some point, and I simply do not believe that folks regularly see this information at the end of the man page and benefit from it more than from going to our GitHub repository or website (both of which contain references to GitHub, discussions, issues, IRC, Slack, ...).

More importantly, if someone looks at the man page of an outdated version of the Node.js, this way they won't be directed at a potentially outdated or non-existing resource. (Assuming GitHub is here to stay.)

tniessen added the doc Issues and PRs related to the documentations. label Jun 5, 2024
tniessen added the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label Jun 5, 2024

tniessen commented Jun 5, 2024

Copy link
Copy Markdown
Member Author

There is an alternative PR #52943 by @redyetidev that instead adds the OpenJS Foundation Slack to the man page. However, I think that PR demonstrates that the communication channels in the man page will always eventually be outdated, so I'd rather just remove anything besides GitHub and our own website.

Copy link
Copy Markdown
Member

just remove anything besides GitHub and our own website.

+1

Copy link
Copy Markdown
Member

Also, if the initiative described in nodejs/admin#872 gets added, it'd be helpful for this to instead point to the list of support channels, as (like @tniessen mentioned) older versions wouldn't know about it from the man page.

UlisesGascon left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

LGTM!

tniessen added the commit-queue Add this label to land a pull request using GitHub Actions. label Jun 7, 2024
nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Jun 7, 2024
nodejs-github-bot merged commit 1945072 into nodejs:main Jun 7, 2024

Copy link
Copy Markdown
Collaborator

Landed in 1945072

serious-angel commented Jun 18, 2024
edited
Loading

Copy link
Copy Markdown

To be frank, I have no idea why you would do so, and it's sure sad to now that. I used to be on #javascript and #nodejs channels at Libera or Freenode back then for more than a decade. I got banned in those channels, but I loved the place. There have always been more than 500 skillful people discussing awesome cases and there was always a chance to discover something new and incredible. I presume it's still the same. The protocol is still active, convenient (e.g. a preview of frequent personal WeeChat setup attached), and lightweight. Though, while some IRC networks are relatively easy places to get banned and lose fairly great usernames and nerves, those socials I do miss...

Do you read XKCD too much (i.e. 1782) I am sorry?

I heartfelt believe you make a terrible mistake.


Copy link
Copy Markdown
Member Author

@artshade This PR does not change the status of those IRC channels at all, it merely removes any social channels from the Linux man page.

This comment was marked as off-topic.

This comment was marked as resolved.

This comment was marked as off-topic.

This comment was marked as resolved.

nodejs locked as resolved and limited conversation to collaborators Jun 19, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

author ready PRs that have at least one approval, no outstanding review comments, and a CI started. doc Issues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.


Back | FazBrowse Home | New Git URL