Forking is an approach to keep the project moving but the underlying problem is then notification &amp; distribution. If I use one of the package managers - npm, composer, gems, etc - people only know of the original project and have its namespace somewhere in the project.<p>If I fork a project, resolve all the issues, and make it better, faster, etc, there&#x27;s not a mechanism for those users to pick up my fork unless they actively go looking for it.<p>I think many of those package managers would be well-served to have a 301-like redirect saying &quot;deprecated, but continued over in this new package&quot;