title: Publish fork of GitHub project to new NPM module but keep option to merge with original?
body: <p>A high quality open source repo exists on GitHub and NPM, with a wide user base.</p>
  
  <p>I've forked the project and made a substantial extension.  I think is ready to merge back.   But (appropriately) its the project owner who gets to make that call not me.  And it's now been several weeks without reply.</p>
  
  <p>Several users have asked on the repo issue discussion that this be merged back, and more have contacted me directly to publish to NPM as a separate project.   </p>
  
  <p>Serious developers can get the new version via GitHub, but it has just the raw source, not the catenated/minified/tailored versions as the README says not to run <code>make dist</code> until it's merged back and the version number incremented.</p>
  
  <p>I <em>think</em> it should be as simple as creating a fork of this fork, and publishing that as a new NPM module.  But GitHub doesn't allow me to do that ("You're already looking at this project")</p>
  
  <p>Is there a way that I can publish this as a new NPM module, but still retain the options for </p>
  
  <ol>
  <li>my fork to submit a pull request to the original</li>
  <li>my fork to fetch upstream changes from the original</li>
  <li>my sub-fork to fetch upstream changes from my fork (and thus the original)</li>
  </ol>
  
  <p>Do I create a new GitHub account under a new email address? </p>
  
  <p><a href="https://stackoverflow.com/questions/18306457/forking-a-fork-of-my-repo-in-githu">Forking a fork of my repo in GitHub</a></p>