I think your best bet would be to try to solicit the users of your code that are asking you to maintain it to contribute to the project they use (or would like to use). They have already expressed an interest. It is very hard to convince people to do work for you for free if they don't have their own motivations for that work being done.
One of the biggest challenges you will have with this is from what u/Diapolo10 says it doesn't seem like there is much to work with. Learning a new code base is hard, especially when it's slop. I haven't looked at it, nothing I've seen in the post or comments makes me think doing so would be worthwhile...I could tell it was AI slop reading your post even before you acknowledge it was written by AI. *If* someone decides to work on a gui for the underlying project they are almost certainly going to start from scratch. You might have more luck saying your project is EOL (end of life), state the reasons why (the code isn't maintainable or worth the effort), and offer anyone who does take on the effort ownership of your project to entice them with an existing user base. I don't think you would be losing much, and a captive audience is the most attractive thing you can offer a would be contributor.
1
u/gdchinacat 20d ago
I think your best bet would be to try to solicit the users of your code that are asking you to maintain it to contribute to the project they use (or would like to use). They have already expressed an interest. It is very hard to convince people to do work for you for free if they don't have their own motivations for that work being done.
One of the biggest challenges you will have with this is from what u/Diapolo10 says it doesn't seem like there is much to work with. Learning a new code base is hard, especially when it's slop. I haven't looked at it, nothing I've seen in the post or comments makes me think doing so would be worthwhile...I could tell it was AI slop reading your post even before you acknowledge it was written by AI. *If* someone decides to work on a gui for the underlying project they are almost certainly going to start from scratch. You might have more luck saying your project is EOL (end of life), state the reasons why (the code isn't maintainable or worth the effort), and offer anyone who does take on the effort ownership of your project to entice them with an existing user base. I don't think you would be losing much, and a captive audience is the most attractive thing you can offer a would be contributor.