Description
In October 2022 ImageSharp announced they are leaving the .NET foundation:
This is the result of SixLabors changing the terms of their license in July 2022 and being unable to resolve the conflict with the .NET Foundation
The .NET Foundation made a blog post discussing the change (which they later deleted):
https://dotnetfoundation.org/blog/2022/10/20/imagesharpupdate(now 404)- https://dotnetfoundation.org/blog/2022/10/20/imagesharpupdate (Archived on Oct 27, 2022)
The .NET Foundation only works with projects with OSI-approved licenses. ImageSharp has decided to leave the Foundation ... We don’t see a path forward where we maintain a fork of ImageSharp.
After significant consideration, the .NET Foundation board decided that there wasn’t a path forward that satisfied the goals of both Six Labors and the Foundation. The board clarified that projects in the Foundation must use a permissive OSI-approved license and that projects would all be treated the same.
Also, the 2.x NuGet packages will not be deleted. You’ll be able to use those forever.
The official System.Drawing documentation page no longer recommends ImageSharp as an alternative to System.Drawing. Interesting discussion about the removal of this recommendation can be found on the PR that removed the link:
Discussions related to ImageSharp leaving the .NET Foundation:
- https://sixlabors.com/posts/imagesharp-leaves-net-foundation/
- https://news.ycombinator.com/item?id=33301518
- https://www.reddit.com/r/dotnet/comments/yasdyc/imagesharp_is_leaving_the_net_foundation_because/
- https://www.i-programmer.info/news/80-java/15822-imagesharp-changes-license-leaves-net-foundation.html
Considering the .NET Foundation's page describing these events is now 404'd and ImageSharp is still on the .NET Foundation projects page it seems this story is still unfolding:
After the dust settles, a summary of these events and relevant links should be added to the page: