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.

[michaelmairegger]

@sungam3r As i use the library a lot I am also willing to help maintaining

[sungam3r]

Any help is welcome. I can react with a delay, but I track all activity.

[mathlizee]

@sungam3r I would like to open a PR that resolves #718, but I'm not authorized to push my local branch to the repo. Is there a file or a README that explains the steps to contribute to the project?

[sungam3r]

First fork this repo. Then make changes into your personal fork. The last thing - make PR from your fork to that repo (origin).

[hschink]

@sungam3r I'd like to contribute as well.

[sungam3r]

https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22

[LeeAtCfc]

@sungam3r I have a fix for this open issue. I'm keen to raise a PR for it to resolve the issue.

[thompson-tomo]

Also happy to contribute especially given my recent thoughts and long term wishes for which I am willing to submit pr's. Also willing to work through PR Backlog.

[Alirexaa]

@sungam3r I am also willing to help maintain this project

[SeanKilleen]

@sungam3r firstly -- thank you for your effort on all this! I think it's a very valuable project and I don't want it to be takne for granted.

To that end, a few points (none of which are a reflection on you and your excellent efforts, but a suggestion on how to move forward)

• Something I've noticed in projects that are seeking this sort of support is that each project seems to view the role of maintainer differently. The next time you perform maintainer activities, it might make sense to do so as part of a Twitch/YouTube livestream and talk through them. This might help others feel empowered to contribute more, and serve as an onboarding into the project
• Instead of maintainer activities the next time you have space, maybe it would be helpful to describe the current way a lot of these operate and the standards they use as if you were explaining them to a new maintainer. This could form the basis of a CONTRIBUTING.md that gives an overview of the project and helps others get into it conceptually which might help empower others to come forward.
• What are your biggest blockers to being the most effective core contributor that you can be? I ask because sometimes project roadmapping and issue triage can be a big source of stress and helping others understand how to help you there might also be a good bridge for people to get interested and start the path toward co-maintainership.
• If there was a "league of fractional maintainers" as part of a trusted organization (.NET Foundation or similar), do you think that would possibly help? My theory is that a number of people who can't be a full-time maintainer could still deliver meaningful support if their efforts are targeted correctly to be more than "drive-by".
  • (CC @1kevgriff as I think this could be a place for the .NET Foundation to really help and I don't want to forget to mention it to him. 😄 )

If these activities above don't bring joy (and I don't blame you if they don't!), I wonder if doing so as part of an "interview"-style conversation might be helpful. E.g. someone asking you questions about the project and how it works, on a livestream, recorded for posterity and for anyone looking to join up.

I know this post is definitely more questions than answers, but as I think about OSS sustainability and happened to see this, I'm hopeful that you might have some insights in ways that can help us better support you beyond waiting for someone to be able to step up to be an additional full-time maintainer.

[WeihanLi]

@sungam3r maybe I could also help with the code review