Exactly. Someone unhappy with the name, but wants to contribute to the product, can fork the project with a different name and start putting all their patches i

Exactly. Someone unhappy with the name, but wants to contribute to the product, can fork the project with a different name and start putting all their patches in there. If their features are good, they might get backported to the other project. That person may continue to rebase off the original as well. Eventually you might have two packages in all the major distros and CI that helps keep both trees in sync. That really is the right way forward here. Or ... the person could just make a CI that pulls, applies a single script that renames and rebrands everything, and then rerelease packages. That's all they have to do .. and if it catches on, well then they've made a change without having to bother the original developers at all.