I don't see this exactly in the same vein as the other two reports. They've not materially modified Fedora itself by replacing any packages. The disabling of SELinux is unfortunate, but in my opinion it is not enough for it to be a remix. The usage of Everything is completely fine. We ship it, they used it to create an image. That doesn't make it somehow not Fedora.

There is a difference between making modifications to Fedora packages that are not reflected in Fedora sources and still calling it Fedora vs. runtime tuning and package selection. It seems Hetzner has done the latter.

@noda Can you re-upload the pastebins so we can discuss this specific example in a larger conversation about configuration changes. Thank you.

I feel like it is hard for us to dictate runtime configuration. Without seeing the pastebins, I lean toward what @jwboyer has said. I believe this is not a trademark violation, though it is a configuration we would generally consider sub-optimal. I believe it is reasonable for us to ask them to consider using a default secure installation, but not somehow try to require it.

I agree with @bex and @jwboyer here. it does not look enough to force a remix label on it. the regular cloud images disable firewall https://pagure.io/fedora-kickstarts/blob/af96d2b41fc8ae2a05c8e718c8ecd22d1a43832f/f/fedora-cloud-base.ks#_36 shows the disabling of the firewall. I used the current git hash so that the url will always be consistent with the state now. that they disable selinux is unfortunate. all the arm images also disable /tmp on tmpfs

Disabling SELinux is the main thing that gives me pause.

I'm going to mark this as deferred until we can finalize updated VPS/cloud/hosting policies.