Looking for maintainers

[sungam3r]

Hi there. For a long time I have been helping to support this project. At first I only used some health checks from it, then I began to offer small changes. Over time, my knowledge and experience became enough for the core maintainers could calmly entrust me with the management of the project and give the necessary permissions to independently change anything in it. I helped and continue to help. Nevertheless, this is not the main project that I am taking time. My knowledge and time is not enough to carry out decent support here by oneself. Many issues are unanswered. The same thing, although to a lesser extent concerns pull requests.

Now I'm the only person who sorts issues, gives any feedback in reviewing PRs, merges PRs, makes releases, etc. I have not received feedback and have not seen any activity from core maintainers - @CarlosLanderas @carlosrecuero @unaizorrilla for that repo for a very long time.

So... I would be very glad if someone is ready to help us to support this project on an ongoing basis. The main pain points so far are

• UI projects
• CI for UI does not call dotnet test DONE
• Docker/K8S stuff - it all needs review
• KubernetesClient nuget package is very old - v4.0.26 (09.04.2021) vs 10.0.1 on nuget.org DONE
• A lot of pending/unanswered issues/PRs.

This project is worthy of continuing to live.

[marioleed]

@sungam3r It seems to me that you're practically the only maintainer, which feels a bit odd for a popular library like this. You are doing a great job, so keep it up 💪🏻

I don't know if I can be of any help, but I can look through some PR's and issues when I have some spare time (don't hold your breath waiting though 😉).

[sungam3r]

which feels a bit odd for a popular library like this

In fact, this can be seen everywhere in OSS. Only 1-2 people on an ongoing basis support projects with millions of downloads.

[rob-baldwin]

@sungam3r I'm willing to put my hand up to help with the long term support of this project. I've not contributed much to this project, but I've used it a fair bit in several companies over many years, so I feel I should give back to the community.

[sungam3r]

OK. You can start by answering issues marked with question label or/and post some PRs. I'll review them as soon as possible. Also you may find a buch of abandoned PRs with no feedback (#1121, for example) from OP, so another way to help - resurrect such PRs so we can merge them.

[SeanFarrow]

@sungam3r I'm also interested in helping.
I have used the library a lot and definitely have ideas as to where this could go, putting tests in Docker for example.

Thanks,
Sean.

[sungam3r]

#1714 (comment) - here is the way to help. I plan to release v7 in coming days so a window for applying breaking changes become less.

[SeanFarrow]

Do you have any features you’d like after V7? I would like to see tests fully dockerised. From: Ivan Maximov ***@***.***> Sent: Monday, July 3, 2023 9:34 PM To: Xabaril/AspNetCore.Diagnostics.HealthChecks ***@***.***> Cc: Sean Farrow ***@***.***>; Comment ***@***.***> Subject: Re: [Xabaril/AspNetCore.Diagnostics.HealthChecks] Looking for maintainers (Issue #1714) #1714 (comment)<#1714 (comment)> - here is the way to help. I plan to release v7 in coming days so a window for applying breaking changes become less. — Reply to this email directly, view it on GitHub<#1714 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AALDK7SW4P5GPJCK6G2HBX3XOMUCZANCNFSM6AAAAAAVJM6EEI>. You are receiving this because you commented.Message ID: ***@***.***>

[sungam3r]

I have no any plans on v8. I support this project at a very limited time.

[sungam3r]

Heads up! I sorted out pending issues and labeled them to simplify tracking progress. See issues column with badges at https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks#health-checks section. Actually the main pain point is out of that section, see https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks#docker-images section with UI badge (54 issues). I don't know how to represent it well so decided to keep readme structure as is - packages are separated from docker images.