diff options
Diffstat (limited to 'deps/npm/html/doc/misc/npm-disputes.html')
| -rw-r--r-- | deps/npm/html/doc/misc/npm-disputes.html | 41 |
1 files changed, 23 insertions, 18 deletions
diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index dccfe0394b..1c01e4870b 100644 --- a/deps/npm/html/doc/misc/npm-disputes.html +++ b/deps/npm/html/doc/misc/npm-disputes.html @@ -20,7 +20,7 @@ Conduct.</p> <h2 id="tl-dr">TL;DR</h2> <ol> <li>Get the author email with <code>npm owner ls <pkgname></code></li> -<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li> +<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li> <li>After a few weeks, if there's no resolution, we'll sort it out.</li> </ol> <p>Don't squat on package names. Publish code or move out of the way.</p> @@ -29,22 +29,25 @@ Conduct.</p> some other user wants to use that name. Here are some common ways that happens (each of these is based on actual events.)</p> <ol> -<li>Alice writes a JavaScript module <code>foo</code>, which is not node-specific. Alice +<li><p>Alice writes a JavaScript module <code>foo</code>, which is not node-specific. Alice doesn't use node at all. Yusuf wants to use <code>foo</code> in node, so he wraps it in an npm module. Some time later, Alice starts using node, and wants to take -over management of her program.</li> -<li>Yusuf writes an npm module <code>foo</code>, and publishes it. Perhaps much later, Alice +over management of her program.</p> +</li> +<li><p>Yusuf writes an npm module <code>foo</code>, and publishes it. Perhaps much later, Alice finds a bug in <code>foo</code>, and fixes it. She sends a pull request to Yusuf, but Yusuf 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. Alice would like to publish a new <code>foo</code>, but can't, -because the name is taken.</li> -<li>Yusuf writes a 10-line flow-control library, and calls it <code>foo</code>, and +because the name is taken.</p> +</li> +<li><p>Yusuf writes a 10-line flow-control library, and calls it <code>foo</code>, and publishes it to the npm registry. Being a simple little thing, it never really has to be updated. Alice works for Foo Inc, the makers of the critically acclaimed and widely-marketed <code>foo</code> JavaScript toolkit framework. They publish it to npm as <code>foojs</code>, but people are routinely confused when -<code>npm install foo</code> is some different thing.</li> +<code>npm install foo</code> is some different thing.</p> +</li> <li><p>Yusuf writes a parser for the widely-known <code>foo</code> file format, because he needs it for work. Then, he gets a new job, and never updates the prototype. Later on, Alice writes a much more complete <code>foo</code> parser, but can't publish, @@ -53,15 +56,17 @@ because Yusuf's <code>foo</code> is in the way.</p> <li><p><code>npm owner ls foo</code>. This will tell Alice the email address of the owner (Yusuf).</p> </li> -<li>Alice emails Yusuf, explaining the situation <strong>as respectfully as possible</strong>, +<li><p>Alice emails Yusuf, explaining the situation <strong>as respectfully as possible</strong>, and what she would like to do with the module name. She adds the npm support -staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of the email. Mention in the email +staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of the email. Mention in the email that Yusuf can run npm owner <code>add alice foo</code> to add Alice as an owner of the -foo package.</li> -<li>After a reasonable amount of time, if Yusuf has not responded, or if Yusuf +foo package.</p> +</li> +<li><p>After a reasonable amount of time, if Yusuf has not responded, or if Yusuf and Alice can't come to any sort of resolution, email support -<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is usually at least -4 weeks.)</li> +<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is usually at least +4 weeks.)</p> +</li> </ol> <h2 id="reasoning">REASONING</h2> <p>In almost every case so far, the parties involved have been able to reach an @@ -96,14 +101,14 @@ application database or otherwise putting non-packagey things into it.</li> <a href="https://www.npmjs.com/policies/conduct">Code of Conduct</a> such as hateful language, pornographic content, or harassment.</li> </ol> -<p>If you see bad behavior like this, please report it to <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> right +<p>If you see bad behavior like this, please report it to <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> right away. <strong>You are never expected to resolve abusive behavior on your own. We are here to help.</strong></p> <h2 id="trademarks">TRADEMARKS</h2> <p>If you think another npm publisher is infringing your trademark, such as by -using a confusingly similar package name, email <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> with a link to -the package or user account on <a href="https://npmjs.com">https://npmjs.com</a>. Attach a -copy of your trademark registration certificate.</p> +using a confusingly similar package name, email <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> with a link to +the package or user account on <a href="https://www.npmjs.com/">https://www.npmjs.com/</a>. +Attach a copy of your trademark registration certificate.</p> <p>If we see that the package's publisher is intentionally misleading others by misusing your registered mark without permission, we will transfer the package name to you. Otherwise, we will contact the package publisher and ask them to @@ -134,5 +139,5 @@ License.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-disputes — npm@6.2.0</p> +<p id="footer">npm-disputes — npm@6.4.1</p> |