Closed jopabe closed 1 year ago
Thanks for bringing it to my attention. For the moment there is no reason to upgrade to a higher ImageSharp version and it is only used on a few places and it also should not be to hard to remove any dependencies. The only problem is then what to replace it with,
The .NET Foundation recently announced that ImageSharp is leaving the Foundation as future versions will no longer be available under an OSI-approved license.
If future versions of MsgReader would have a dependency on ImageSharp (>2.1.3), that could prevent development teams in somewhat larger organizations (even if it's a small team) from using MsgReader.
Please be conscious of the impact of upgrading the ImageSharp dependency and consider either:
If this is not possible, it would be best to clearly specify the license restrictions in your license file, and maybe even adding a readme to the NuGet packages to notify users who are unaware of the implications.
Thank you and keep up the good work!