diff options
Diffstat (limited to 'deps/npm/man/man7/npm-disputes.7')
| -rw-r--r-- | deps/npm/man/man7/npm-disputes.7 | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/deps/npm/man/man7/npm-disputes.7 b/deps/npm/man/man7/npm-disputes.7 index a740f66d5..77350cdc5 100644 --- a/deps/npm/man/man7/npm-disputes.7 +++ b/deps/npm/man/man7/npm-disputes.7 @@ -1,10 +1,10 @@ -.TH "NPM\-DISPUTES" "7" "June 2015" "" "" +.TH "NPM\-DISPUTES" "7" "August 2015" "" "" .SH "NAME" \fBnpm-disputes\fR \- Handling Module Name Disputes .SH SYNOPSIS .RS 0 .IP 1. 3 -Get the author email with \fBnpm owner ls <pkgname>\fR +Get the author email with \fBnpm owner ls <pkgname>\fP .IP 2. 3 Email the author, CC support@npmjs\.com .IP 3. 3 @@ -20,30 +20,30 @@ later, some other user wants to use that name\. Here are some common ways that happens (each of these is based on actual events\.) .RS 0 .IP 1. 3 -Joe writes a JavaScript module \fBfoo\fR, which is not node\-specific\. -Joe doesn't use node at all\. Bob wants to use \fBfoo\fR in node, so he +Joe writes a JavaScript module \fBfoo\fP, which is not node\-specific\. +Joe doesn't use node at all\. Bob wants to use \fBfoo\fP in node, so he wraps it in an npm module\. Some time later, Joe starts using node, and wants to take over management of his program\. .IP 2. 3 -Bob writes an npm module \fBfoo\fR, and publishes it\. Perhaps much -later, Joe finds a bug in \fBfoo\fR, and fixes it\. He sends a pull +Bob writes an npm module \fBfoo\fP, and publishes it\. Perhaps much +later, Joe finds a bug in \fBfoo\fP, and fixes it\. He sends a pull request to Bob, but Bob doesn't have the time to deal with it, because he has a new job and a new baby and is focused on his new erlang project, and kind of not involved with node any more\. Joe -would like to publish a new \fBfoo\fR, but can't, because the name is +would like to publish a new \fBfoo\fP, but can't, because the name is taken\. .IP 3. 3 -Bob writes a 10\-line flow\-control library, and calls it \fBfoo\fR, and +Bob writes a 10\-line flow\-control library, and calls it \fBfoo\fP, and publishes it to the npm registry\. Being a simple little thing, it never really has to be updated\. Joe works for Foo Inc, the makers -of the critically acclaimed and widely\-marketed \fBfoo\fR JavaScript -toolkit framework\. They publish it to npm as \fBfoojs\fR, but people are -routinely confused when \fBnpm install foo\fR is some different thing\. +of the critically acclaimed and widely\-marketed \fBfoo\fP JavaScript +toolkit framework\. They publish it to npm as \fBfoojs\fP, but people are +routinely confused when \fBnpm install foo\fP is some different thing\. .IP 4. 3 -Bob writes a parser for the widely\-known \fBfoo\fR file format, because +Bob writes a parser for the widely\-known \fBfoo\fP file format, because he needs it for work\. Then, he gets a new job, and never updates the -prototype\. Later on, Joe writes a much more complete \fBfoo\fR parser, -but can't publish, because Bob's \fBfoo\fR is in the way\. +prototype\. Later on, Joe writes a much more complete \fBfoo\fP parser, +but can't publish, because Bob's \fBfoo\fP is in the way\. .RE .P @@ -51,14 +51,14 @@ The validity of Joe's claim in each situation can be debated\. However, Joe's appropriate course of action in each case is the same\. .RS 0 .IP 1. 3 -\fBnpm owner ls foo\fR\|\. This will tell Joe the email address of the +\fBnpm owner ls foo\fP\|\. This will tell Joe the email address of the owner (Bob)\. .IP 2. 3 Joe emails Bob, explaining the situation \fBas respectfully as possible\fR, and what he would like to do with the module name\. He adds the npm support staff support@npmjs\.com to the CC list of the email\. Mention in the email that Bob can run \fBnpm owner add -joe foo\fR to add Joe as an owner of the \fBfoo\fR package\. +joe foo\fP to add Joe as an owner of the \fBfoo\fP package\. .IP 3. 3 After a reasonable amount of time, if Bob has not responded, or if Bob and Joe can't come to any sort of resolution, email support |