'Fork published on NuGet confusing users / unlist request
Recently I got an e-mail from a package maintainer asking me to unlist my fork of said package from NuGet due to my fork "confusing nuget users".
I've never encountered a request like this before and as I have a few more forks like that I now wonder whether I'm doing something wrong and if I should unlist my other forks as well.
- source code of the original package (any my fork too) is available on GitHub
- there is no LICENSE.md file but in the readme is a section stating:
This project is Copyright © 2021 XXX. Free for non-commercial use. For commercial use please contact the author.
- clicking "License Info" on NuGet brings up Apache 2.0 license for both the original repo and the fork (which is weird as the author is prohibitng commercial use in GitHub readme without a commercial license)
- Me and my friends needed to use the package with a change (a minor one but still blocking our use cases)
- I've opened a PR with said change and got no response from the maintainer
- hence I've published my fork to NuGet
- the original package is called
Package, my fork was available asPackage-lof(my handle, unlisted after I got the request)
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|
