<p><code><ahref="../../doc/README.html">README</a></code>, <code>CHANGES</code>&<code>LICENSE</code> can have any case and extension.</p>
<p><code><ahref="../../doc/README.html">README</a></code>, <code>CHANGES</code>, <code>LICENSE</code>&<code>NOTICE</code> can have any case and extension.</p>
<p><code><ahref="../../doc/README.html">README</a></code>, <code>CHANGES</code>&<code>LICENSE</code> can have any case and extension.</p>
<p><code><ahref="../../doc/README.html">README</a></code>, <code>CHANGES</code>, <code>LICENSE</code>&<code>NOTICE</code> can have any case and extension.</p>
<li>Get the author email with <code>npm owner ls <pkgname></code></li>
<li>Email the author, CC <ahref="mailto:support@npmjs.com">support@npmjs.com</a></li>
<li>Email the author, CC <ahref="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>
@ -51,12 +51,12 @@ Joe's appropriate course of action in each case is the same.</p>
owner (Bob).</li>
<li>Joe emails Bob, explaining the situation <strong>as respectfully as
possible</strong>, and what he would like to do with the module name. He
adds the npm support staff <ahref="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of
adds the npm support staff <ahref="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of
the email. Mention in the email that Bob can run <code>npm owner add
joe foo</code> to add Joe as an owner of the <code>foo</code> package.</li>
<li>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
<ahref="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is
<ahref="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is
usually at least 4 weeks, but extra time is allowed around common