Remove legal cruft and clarify registry.npmjs.org is default

[kemitchell]

This small pull request:

1. Follows on from Refer to npm terms of use on npmjs.com in LICENSE #10326 by deleting extraneous and potentially confusing legal-sounding language from README
2. Further clarifies that registry.npmjs.org is the default package registry

[isaacs]

LGTM.

We should land this on both master and v2 branches (and v1 branch?)

Also, cc @ashleygwilliams so we can ensure that this gets into the cli docs on the website.

[othiym23]

and v1 branch?

My plan was for npm@1.4.29 to be the last release of npm@1, with subsequent versions of the Node 0.10 maintenance branch getting npm@2. I don't think it's necessary to land these changes there, unless we want to do another release of npm@1.4 specifically for the purposes of licensing.

[othiym23]

I'm going to merge these into the npm@3 and npm@2 release branches for this week, which means that the license will be up-to-date as of npm@3.5.1 and npm@2.14.13.

[kemitchell]

Thanks, @othiym23!

[othiym23]

Landed as 743af42 and 21418ca on release-3.5.1, scheduled to be released to npm@next on Wednesday.

Landed as 6733539 and 1f3e936 on release-2.14.13, also scheduled to be released to npm@next-2 on Wednesday.

To bring all of the release lines into sync, 9538c2c, ec50079, and eadd752 have been cherry-picked onto the 1.4.x branch. This branch is not currently scheduled to (ever) receive another release, but if there's sufficient interest or concern from Node.js LTS (paging @jasnell), especially if Node.js 0.10 LTS hasn't gone out yet, it would be easy enough for me to produce an npm@1.4.30 that includes them. Otherwise, I'd like to stick to the plan of moving Node 0.10 over to npm@2, as planned in nodejs/Release#37.

[jasnell]

+1 thanks!
On Nov 23, 2015 5:58 PM, "Forrest L Norvell" notifications@github.com
wrote:

Landed as 743af42
743af42
and 21418ca
21418ca
on release-3.5.1, scheduled to be released to npm@next on Wednesday.

Landed as 6733539
6733539
and 1f3e936
1f3e936
on release-2.14.13, also scheduled to be released to npm@next-2 on
Wednesday.

To bring all of the release lines into sync, 9538c2c
9538c2c,
ec50079
ec50079,
and eadd752
eadd752
have been cherry-picked onto the 1.4.x branch. This branch is not
currently scheduled to (ever) receive another release, but if there's
sufficient interest or concern from Node.js LTS (paging @jasnell
https://github.com/jasnell), especially if Node.js 0.10 LTS hasn't gone
out yet, it would be easy enough for me to produce an npm@1.4.30 that
includes them. Otherwise, I'd like to stick to the plan of moving Node 0.10
over to npm@2, as planned in nodejs/Release#37
https://github.com/nodejs/LTS/issue%20s/37.

—
Reply to this email directly or view it on GitHub
#10532 (comment).

[othiym23]

Getting ready to release npm@3.5.1 and npm@2.14.13, so closing this out!