Add list packages and community forks to README #261
Conversation
This library was only intended for usage with ASP.NET Core's tools, and not a general purpose library. After receiving bugs and questions about this, we realized that we didn't really intend to produce and support a command-line parsing library. We will still leave the 1.0.0 and 1.1.0 versions of this library on NuGet.org, but the current plan is to stop producing new versions of this package. The source code is still available for internal use via Microsoft.Extensions.CommandLineUtils.Sources, however we will not be publishing this library again as a general purpose library.
|
Looks good! You'll probably need to change some of the license/copyright info in your fork, but IANAL, so you'll need to figure that out 😄 |
|
One suggestion: the name(space) McMaster.Extensions.CommandLineUtils might feel more inclusive if it were instead something like MicrosoftCommunity.Extensions.CommandLineUtils or something like that. "McMaster" as the root namespace doesn't feel very community-oriented, and use in my professional environment would probably be frowned upon. |
|
Community packages often pick whatever name makes sense for them. For example, one of the most popular packages is Json.NET, which is in the But, ultimately, I recommend discussing this with @natemcmaster directly on https://github.com/natemcmaster/CommandLineUtils/issues. Thanks! |
In response to the discontinuation of active dev work on CommandLineUtils (#257), I've decided to fork the command-line utils project here: https://github.com/natemcmaster/CommandLineUtils. This will be an outside of work project and does not have official sponsorship from the aspnet team. This project is also under the same Apache license: @Eilon let me know if I need to change any of the license documents or links this fork.