AGPL provisions kick in for services delivered over a network, basically the SaaS models. With RHEL some of the code may be under the AGPL (I haven't checked i

AGPL provisions kick in for services delivered over a network, basically the SaaS models. With RHEL some of the code may be under the AGPL (I haven't checked if any of the RHEL packages are actually AGPL), but it's not being offered as a service in a way that should trigger AGPL requirements AFAIK. GPLv3 doesn't contain any provisions that address this as far as I am aware. It was concerned with things like "Tivoization" and embedded software. None of the terms in those licenses require the things that everybody seems to want them to require: verbatim publishing of exact source code to everyone everywhere that allows "bug for bug" clones of RHEL and/or continuing a business relationship that forces Red Hat to convey the GPL rights for all RHEL releases no matter what a customer does with those rights.