Within a day of releasing my first piece of open source software, it’s already been proven incomplete.
The thing I made fails to take something into account which can result in a jumpy, stuttery game if that’s not accounted for. So I have presented an incomplete solution. Luckily, due to the nature of open source software, someone saw this and told me about it. Sadly, due to the nature of open source software, I feel obligated to fix it. And I should, I guess? But on bigger projects, that can be an issue.
On bigger projects, with more users, there’s more issues and more frequent discovery of those issues. You’ll get messages, emails, phone calls in the middle of the night telling you “hey your thing doesn’t work in my very specific setup”. And that’s hard. It’s still your project, you want it to be something good. But somewhere you have to draw the line, because you can’t fix everything.
There’s always something to fix, but you don’t always have the time or will for it. Luckily, you’re not obligated to do anything.