How can we help?

[svenvg93]

First of all, thank you for all the work you’ve put into this amazing project! Beszel has replaced what used to be a very complicated monitoring setup for me, and it’s been a breeze to use.

It’s clear that a lot of time and effort has gone into building and maintaining this project, and I would love to help you where possible, for example with things like managing issues, reviewing contributions, or other maintenance tasks. Please let me know if there’s any way I can contribute or support you.

[henrygd]

Thanks so much Sven! I always appreciate your contributions, and this is very generous of you. It means a lot to me.

I can certainly use your help. I'll spare you the details, but over the last few months in particular I've been struggling to find the time, energy, and motivation to stay on top of things here. I'm hopeful this will change soon.

I'll go ahead and invite you to the repo as a collaborator. This should give you access to manage issues / discussions and do most other things besides writing to the main branch. Let me know if this doesn't work correctly. Please do as little or as much as you'd like. I trust your judgement, and you can always tag me if you're unsure of something :)

[svenvg93]

Thanks, Hank! I completely understand how overwhelming it can be to manage everything in such a popular project, on top of everything else in life. I’m happy to help wherever I can.

I’ll start by reviewing the issues to identify duplicate or similar feature requests, linking them together and closing duplicates so there’s only one open request per feature. I’ll also check which requested features may have already been implemented in the meantime, as well as older open bug reports where the original poster never followed up on questions.

For anything I’m unsure about, I’ll tag you. I hope this approach sounds good to you.

[henrygd]

Sounds great, thank you!

[svenvg93]

I’ve completed the first round of cleaning up the requests. I hope I did not close any issues that should not be closed 😅 .

• Closed all duplicate issues and linked them to the relevant original issue.
• Closed requests that have already been implemented.
• Marked a few requests as “Help Wanted” since they require specific hardware for development/testing — these could be picked up by the community.
• Converted some issues into discussions since they are more about exploring ideas than reporting bugs.
• Changed a couple of titles to make it clearer what the request is about, hopefully making it easier for others to find them.
• There are several requests that I’m unsure about. They seem like edge cases or possibly out of scope, in my opinion. I’ve marked them as “Under Consideration” so you can review and decide what to do.
• Added an "waiting on upstream" label to mark issues where the root cause is upstream and not on our side.
• Closed and Locked some troubleshooting issues. They didn't had any action in months. I assume the problem is not relevant anymore. Otherwise a new issue can be opened.
• Most other old issues have been closed as well.
• For some older issues, I asked the requester to confirm whether the problem still exists. These were labeled “waiting-requester”; if there’s no response, the stale bot will handle them in a few weeks.

Its a nice cleanup for now, hopefully it will allow you to focus on the fun parts 😄

[henrygd]

Thanks so much for this. I missed this comment at the time, but I really appreciate your help :)

[svenvg93]

@henrygd Maybe this is a bit of a silly thought, but would it help to temporarily limit PRs to collaborators until you’ve had some time to catch up?

It’s really awesome to see so many people contributing to the project — it just looks like things might be piling up a little. If you do decide to go that route, I’m totally fine holding off and won’t open any PRs for the time being as well.

[henrygd]

Not silly at all, it has crossed my mind as well. It's not a good feeling for anyone to have PRs sit indefinitely.

Let me think about it a bit more. Maybe we can just make it clear in the docs and PR template that we have an existing backlog that we need to prioritize, so expect a delay before review.

It's definitely something that I will consider if they continue to come in at the current pace.

[svenvg93]

I’ll jump in and help with the PRs as much as possible to take some of the weight off your shoulders! 😄 It might be worth closing some of the older ones, while not ideal, starting fresh is likely easier than trying to reconcile them with the latest changes.