One could also not feel obligated to address all requests and just let anyone fork the project.

Isn’t it a bit about the ego to keep running the project while it’s too much to handle?

Didn’t downvote ya but, yeah I guess I could do that if I were a dev. Also, I would personally feel responsible for someone’s loss or havoc caused my my app.

Also, I would personally feel responsible for someone’s loss or havoc caused my my app.

Which is one of the reasons I’ll never implement the delete function in the Jellyfin for Roku client.

Sure, I’m assuming the project has a stable version and a warning or archived banner clearly advertised 😉

You can keep running the project and invite people wishing for an XYZ integration to open a pull request. The collaborative nature is kind of a big point of open source imo.

oh absolutely. I only meant in case it’s physically too much for the repo owner.

There’s no need to feel obligated to carry on to one’s own detriment. The community knows how to move on with it, e.g. ownership transfer or a fork.

He specifically goes on to say it’s primarily from dealing with anti-AI backlash in response to his use of Claude to help (solely) maintain the client: github.com/andrewrabert/jellium-desktop/…/609

I think I’m going to put a declarations.md that says something like “I made this for me, but I’m sharing it with the world. If you find it useful, use it and let me know! If you find issues, submit request and I’ll look but no promises. And if you want feature X … fork it and build it. The code’s yours, with my blessings. PS: I don’t accept PRs, sorry”.

I code for fun; I’m not looking for a third unpaid job. That’s what parenting is for.

That would be a way to do it. Here it is, works on my machine, it you feel you can use it, knock yourselves out. 30 minute, 30 mile guarantee.

That’s what parenting is for.

Well, that’s a full time job right there. I wish you the very best of luck in those endeavors. You’ll need it.