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.

Sign up for GitHub

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

Jump to bottom

docs(readme): add note back about branding/origin #2685

Merged
merged 1 commit into from
Feb 22, 2021
Merged

docs(readme): add note back about branding/origin #2685

merged 1 commit into from
Feb 22, 2021

Conversation

darcyclarke
Copy link
Contributor

@darcyclarke darcyclarke commented Feb 12, 2021 •
edited
Loading

Pretty self-explanatory; Getting tired of trying to find the historical reference to this - might as well pull it in.

Rendered

Original FAQ from 2015

...

@darcyclarke darcyclarke requested a review from a team as a code owner February 12, 2021 18:34
@darcyclarke darcyclarke requested a review from isaacs February 12, 2021 18:34
@darcyclarke darcyclarke added Release 7.x work is associated with a specific npm 7 release release: next These items should be addressed in the next release labels Feb 12, 2021
isaacs
isaacs approved these changes Feb 12, 2021
View reviewed changes
Copy link
Contributor

@isaacs isaacs left a comment

Choose a reason for hiding this comment

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

Is there something stronger than "Approve" I can select here?

isaacs
isaacs reviewed Feb 12, 2021
View reviewed changes
README.md

#### Is "npm" an acronym for "Node Package Manager"?

Contrary to popular belief, **`npm`** **is not** in fact an acronym for "Node Package Manager"; It is a recursive bacronymic abbreviation for **"npm is not an acronym"** (if the project was named "ninaa", then it would be an acronym). The precursor to **`npm`** was actually a bash utility named **"pm"**, which was the shortform name of **"pkgmakeinst"** - a bash function that installed various things on various platforms. If **`npm`** were to ever have been considered an acronym, it would be as "node pm" or, potentially "new pm".
Copy link
Contributor

Choose a reason for hiding this comment

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

I do recommend bringing back the bit about pastoral musicians and brain scans, though.

"NPM", however, is an acronym (more precisely, a capitonym) for the National Association of Pastoral Musicians. You can learn more about them at http://npm.org/.

In software, "NPM" is a Non-Parametric Mapping utility written by Chris Rorden. You can analyze pictures of brains with it. Learn more about the (capitalized) NPM program at http://www.cabiatl.com/mricro/npm/.

Copy link
Contributor Author

@darcyclarke darcyclarke Feb 13, 2021 •
edited
Loading

Choose a reason for hiding this comment

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

@isaacs really? I felt like my edited version was a very good middle ground. There could be other associations/trademarks for "NPM" in different locales tbqh; Giving precedence or highlighting the pastoral musicians & brain scans just seems arbitrary/irrelevant at this point (imo). Trying to strike a balance here. Either way, npm has no doubt eclipsed these references.

Copy link
Contributor

Choose a reason for hiding this comment

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

Good point. If we're not going to do a search for all other things by that name, might be best to leave it out.

ljharb
ljharb approved these changes Feb 12, 2021
View reviewed changes
Copy link
Contributor

@ljharb ljharb left a comment

Choose a reason for hiding this comment

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

whole fleet of roflcopters on this one

@darcyclarke darcyclarke added the semver:patch semver patch level for changes label Feb 13, 2021
@nlf nlf force-pushed the darcyclarke-update-readme-with-branding-ref branch from a32da5e to e3de7be Compare February 18, 2021 20:34
@nlf nlf mentioned this pull request Feb 22, 2021
Merged
@nlf nlf closed this in e3de7be Feb 22, 2021
@nlf nlf merged commit e3de7be into latest Feb 22, 2021
@lumaxis lumaxis deleted the darcyclarke-update-readme-with-branding-ref branch February 22, 2021 18:23
@ruyadorno ruyadorno mentioned this pull request Feb 24, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@isaacs isaacs isaacs approved these changes

@lumaxis lumaxis lumaxis approved these changes

@ljharb ljharb ljharb approved these changes

Assignees
No one assigned
Labels
release: next These items should be addressed in the next release Release 7.x work is associated with a specific npm 7 release semver:patch semver patch level for changes
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@darcyclarke @isaacs @ljharb @lumaxis @nlf