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.

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

deps: upgrade npm to 3.5.0 #4032

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
1 change: 1 addition & 0 deletions deps/npm/.mailmap
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@ Alex K. Wolfe <[email protected]>
Andrew Bradley <[email protected]>
Andrew Lunny <[email protected]>
Arlo Breault <[email protected]>
Ashley Williams <[email protected]> <[email protected]>
Benjamin Coe <[email protected]>
Benjamin Coe <[email protected]> <[email protected]>
Brian White <[email protected]> <[email protected]>
Expand Down
4 changes: 2 additions & 2 deletions deps/npm/.travis.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
language: node_js
node_js:
- "4.1"
- "4.0"
- "5"
- "4"
- iojs
- "0.12"
- "0.10"
Expand Down
4 changes: 4 additions & 0 deletions deps/npm/AUTHORS
Original file line number Diff line number Diff line change
Expand Up @@ -324,3 +324,7 @@ Jason Kurian <[email protected]>
Sebastiaan Deckers <[email protected]>
lady3bean <[email protected]>
Tomi Carr <[email protected]>
Juan Caicedo <[email protected]>
Ashley Williams <[email protected]>
Andrew Marcinkevičius <[email protected]>
Jorrit Schippers <[email protected]>
4,694 changes: 289 additions & 4,405 deletions deps/npm/CHANGELOG.md

Large diffs are not rendered by default.

74 changes: 23 additions & 51 deletions deps/npm/LICENSE
Original file line number Diff line number Diff line change
@@ -1,11 +1,29 @@
The npm application
Copyright (c) npm, Inc. and Contributors
All rights reserved.
Licensed on the terms of The Artistic License 2.0
Copy link

Choose a reason for hiding this comment

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

@Fishrock123
This is a much needed leveraging of Copyright...

Copy link
Contributor

Choose a reason for hiding this comment

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

Um, pardon? You mean All rights reserved. needs to remain?

Copy link

Choose a reason for hiding this comment

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

@Fishrock123
I'll need to examine the full document but GH won't allow me to comment on lines that are too far out from the diff.

Basically npm should be able to define Terms of Service for npmjs.com and Terms of Use for the Software... spelling out exactly which is which and no "npm" (only) references. I know this directly from contractual obligations with closed-source agreements.

I have no difficultly with accepting a TOS for npmjs.com as it is their right to prevent bugged modules from being distributed being a pass through provider as long as it's clear in their TOS. With the FSF though as @scriptjs has pointed out the actual Code License hopefully continues to be FOSS. (Their TOU)

Copy link

Choose a reason for hiding this comment

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

You mean All rights reserved. needs to remain?

No... that would not be leveraging the Copyright... which means node couldn't distribute it period as a module without a written agreement on paper registered with a legal authority... that costs $$ to get it registered and pretty much defeats the concept of FOSS.


npm is released under the Artistic License 2.0, subject to additional terms
that are listed below.
Node package dependencies of the npm application
Copy link

Choose a reason for hiding this comment

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

@Fishrock123
This was an issue since Artistic doesn't allow additional modifications to the terms. (EDIT: But may still be present further down out of the diff)

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think additions would apply to that?

Copy link

Choose a reason for hiding this comment

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

Well that's where the attorneys get involved for dispute resolution... reading comprehension isn't limited to attorneys and/or arbitration but common sense says that the enforcement of the Artistic License says it can't be modified.

Copyright (c) their respective copyright owners
Licensed on their respective license terms

The text of the npm License follows and the text of the additional terms
follows the Artistic License 2.0 terms:
The npm public registry at https://registry.npmjs.com
Copy link

Choose a reason for hiding this comment

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

@Fishrock123
This is better as the distinction between npmjs.com and npm is clearer. (EDIT: you may notice I mostly emphasize package/modules names not entity names such as "npm, Inc.")

and the npm website at https://www.npmjs.com
Operated by npm, Inc.
Use governed by terms published on https://www.npmjs.com

"Node.js"
Trademark Joyent, Inc., https://joyent.com
Neither npm nor npm, Inc. are affiliated with Joyent, Inc.

The Node.js application
Project of Node Foundation, https://nodejs.org

The npm Logo
Copyright (c) Mathias Pettersson and Brian Hammond

"Gubblebum Blocky" typeface
Copyright (c) Tjarda Koster, https://jelloween.deviantart.com
Used with permission


--------
Expand Down Expand Up @@ -215,49 +233,3 @@ ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


--------


The following additional terms shall apply to use of the npm software, the npm
website, the npm repository and any other services or products offered by npm,
Inc.:

"Node.js" trademark Joyent, Inc. npm is not officially part of the Node.js
project, and is neither owned by nor affiliated with Joyent, Inc.

"npm" and "The npm Registry" are owned by npm, Inc. All rights reserved.

Modules published on the npm registry are not officially endorsed by npm, Inc.
or the Node.js project.

Data published to the npm registry is not part of npm itself, and is the sole
property of the publisher. While every effort is made to ensure accountability,
there is absolutely no guarantee, warrantee, or assertion expressed or implied
as to the quality, fitness for a specific purpose, or lack of malice in any
given npm package. Packages downloaded through the npm registry are
independently licensed and are not covered by this license.

Additional policies relating to, and restrictions on use of, npm products and
services are available on the npm website. All such policies and restrictions,
as updated from time to time, are hereby incorporated into this license
agreement. By using npm, you acknowledge your agreement to all such policies
and restrictions.

If you have a complaint about a package in the public npm registry, and cannot
resolve it with the package owner, please email [email protected] and explain
the situation. See the [npm Dispute Resolution
policy](https:/npm/policies/blob/master/disputes.md) for more
details.

Any data published to The npm Registry (including user account information) may
be removed or modified at the sole discretion of the npm server administrators.

"npm Logo" contributed by Mathias Pettersson and Brian Hammond,
use is subject to https://www.npmjs.com/policies/trademark

"Gubblebum Blocky" font
Copyright (c) by Tjarda Koster, https://jelloween.deviantart.com
included for use in the npm website and documentation,
used with permission.

This program uses several Node modules contained in the node_modules/
subdirectory, according to the terms of their respective licenses.
Loading