Comment by crote
> the former isn't interested in the help or has a very specific vision for the project and doesn't allow any input that isn't in line with that
I've come to call this "fenceware": technically open source due to its licensing, but community-wise it is as if the developers just throw a ball of code over the fence every few months. Sure, they let you play with it for a bit, but it is not yours to co-own.
Why not if you are free to fork it and do whatever you want with it ?