The main difference is that Fedora - be it rpms, flatpaks from module rpms (current state), flatpaks from whatever - comes with the promise of all the four F's, including freedom from legal issues as outlined in our guidelines. That enables RedHat to make the guarantees which they make for their offerings. Flatpaks from third party sources such as flathub come with no promise whatsover (AFAICT) - unless you track a specific flatpak's provider and figure out their promises/guarantees per flatpak. And without that neither Fedora nor RedHat can ship any app on live media and such. A different question is shipping configuration for third party rpm repos (such as rpmfusion) or flatpak hubs (such flathub). Here, the issue is: - Shipping a Fedora/RHEL specific (enabled) repo/hub config might be considered redistribution, or at least RH legal may consider that a risk too high to take. - Shipping a non-specific (enabled) hub config can hardly be considered redistribution, or at least RH legal does not seem to fear that risk (since unfiltered flathub). >From a customer perspective: Your on your own with anything you pull in from third party sources. Michael _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
