Mention registry terms of use in manpage and registry doc #54
Conversation
This file contains 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
iarna
approved these changes
Aug 18, 2018
zkat
pushed a commit
that referenced
this pull request
Aug 20, 2018
* doc: Mention terms of use in npm-registry * doc: Mention registry terms of use in manpage * doc: Update terms of use language in README Credit: @kemitchell PR-URL: #54
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This small PR spruces up the language on registry terms of use in
README, and adds parallel language to source files fornpm-registryandman npmdoc.The general thrust is to increase the notice folks using
npmget that their registry server---whoever runs it---potentially comes with terms of service they should be aware of. If there are other places where that message should appear, I'd be very interested in pushing more commits.cc & thanks: @iarna