What is the etiquette around forking and NPM?
Consider the following sequence of events:
- There is an existing open source project published on GitHub (or similar) under some standard permissive license (e.g. MIT) that is also published to NPM. That package has a relatively high download rate on NPM. The NPM package name accurately and concisely describes the intent of the package.
- A user unaffliated with the library discovers the package & library but notices that there are some bugs or other improvements to be made. The new user opens some GitHub issues outlining the bugs/improvements and then forks the repo and opens a PR where those problems are addressed.
- There is no immediate or short term response from the maintainer(s).
- While waiting for the maintainer to acknowlege the PR (either reject, merge or otherwise request changes), the new user
- notices further changes that need to be made
- needs their changes to be consumed by other upstream packages (that may or may not be open source)
Which course of action is most beneficial to the new user and applies reasonable etiquette? Some possibilities include:
- Having NPM consume their fork (based on GitHub url)
- Publishing a new package to NPM based on their fork