SkiaSharp icon indicating copy to clipboard operation
SkiaSharp copied to clipboard

[IMPORTANT] From discussion: We need more Project Maintainers

Open Code-Chops opened this issue 2 years ago • 5 comments

Discussed in https://github.com/mono/SkiaSharp/discussions/1884

Originally posted by robloo December 8, 2021 It seems @mattleibow is the sole maintainer of this repository. I'm not sure how scalable that is long term. For example, I am guessing he is on a well deserved vacation yet building with Uno Platform 4.x is completely broken right now. As several companies depend on SkiaSharp, having responsibility left to a single individual is a high risk.

I know this project is backed by Microsoft. However, I wonder who is on the SkiaSharp team besides @mattleibow? We need the ability to review patches and potentially do a preview release while he is away. This is just good stewardship of the project and helps mitigate risks for the vast number of consumers of this project.

You do great work @mattleibow and I know you are spread quite thin on time these days. I just want to start the discussion about other maintainers to this repo -- nothing against the amazing work you have done to date.

Code-Chops avatar Jan 06 '22 15:01 Code-Chops

This is especially true now that @mattleibow has been pulled into working on other MAUI-related projects.

robloo avatar Jan 09 '22 20:01 robloo

Could someone of the skiasharp team please elaborate on this? @mattleibow ? The issues and pull requests are piling up. Thanks in advance!

Code-Chops avatar Jan 28 '22 11:01 Code-Chops

@Code-Chops We tried do do a fix ourselves, but we are unable to build the project based on the explanations found in README.md (see #1723).

This makes this issue even more severe.

thisisthekap avatar Jan 31 '22 05:01 thisisthekap

@Code-Chops We tried do do a fix ourselves, but we are unable to build the project based on the explanations found in README.md (see #1723).

This makes this issue even more severe.

I am having the same problem

hrkrx avatar Feb 06 '22 23:02 hrkrx

I was also not able to build Skia locally by following the instructions in the README the last time I tried, which was earlier this year.

It is surprising that Microsoft does not have more than just one person working on this repository, especially given the number of frameworks it is used in (Xamarin Forms, .NET MAUI, Uno Platform, Avalonia, etc.) and platform targets (just look at the list in the README!). The issues continue to build up because there is only one person to get to them.

I greatly, greatly appreciate the existence and work that goes into this repository and NuGet package. However, at least right now, I am unable to use SkiaSharp due to issues with it on desktop, both macOS and Windows. Both issues are due to either SkiaSharp exceptions that leave no stack trace or .NET crashes due to SkiaSharp, and I have little idea how to debug them. I'm already writing my own bindings for GLFW. Now I am wondering if I need to do the same for Skia or use something else or some other platform (other than .NET).

bmitc avatar Jun 24 '22 05:06 bmitc