A bunch of developers isn't going to do anything though if they retain control over everything. I think after learning about this background, and their weird claims surrounding it yesterday, the path forward I would prefer is for a strong fork to emerge of the original code that instances deploy instead.
I prophesied that to happen back on reddit but with FLOSS development culture being as it is pre-emptive forking is kinda considered the same as a pre-emptive nuclear strike. It's just not done in polite company.
I'm about 100% that there's going to come a make-or break situation where, if the developers don't concede, there will be a fork, but it could also be that the devs are conscious enough of what's happening that they'll cave under the pressure and thus manage to retain some influence over the project.
Forking the project would beyond stupid, and to so blithely suggest it leads me to believe to you don't actually know much about that which you are discussing.
A bunch of developers isn't going to do anything though if they retain control over everything. I think after learning about this background, and their weird claims surrounding it yesterday, the path forward I would prefer is for a strong fork to emerge of the original code that instances deploy instead.
I prophesied that to happen back on reddit but with FLOSS development culture being as it is pre-emptive forking is kinda considered the same as a pre-emptive nuclear strike. It's just not done in polite company.
I'm about 100% that there's going to come a make-or break situation where, if the developers don't concede, there will be a fork, but it could also be that the devs are conscious enough of what's happening that they'll cave under the pressure and thus manage to retain some influence over the project.
Forking the project would beyond stupid, and to so blithely suggest it leads me to believe to you don't actually know much about that which you are discussing.