And if you really like something about someone else's fork, you can even upstream stuff from it yourself (which, for clarity, SQLite won't do, but you can).
Let people fork and develop their own implementations
Then a fork gets made and if they improve it massively then half your users end up using it and the other half ends up bugging you to add the improvements into your version and it's no longer your project.
I mean I agree too it should be open source if the dev doesn't really update it anymore but I can also completely see why they wouldn't want to do that.
In that case the person would be a bottleneck towards improving a piece of software that would benefit a lot of people. Sure, you're within your right to do that, but really?
Comments
It doesn't have to be. Just say you're not accepting PRs. Let people fork and develop their own implementations.
Yep, the SQLite way.
And if you really like something about someone else's fork, you can even upstream stuff from it yourself (which, for clarity, SQLite won't do, but you can).
Then a fork gets made and if they improve it massively then half your users end up using it and the other half ends up bugging you to add the improvements into your version and it's no longer your project.
I mean I agree too it should be open source if the dev doesn't really update it anymore but I can also completely see why they wouldn't want to do that.
In that case the person would be a bottleneck towards improving a piece of software that would benefit a lot of people. Sure, you're within your right to do that, but really?