(no title)
dxf | 2 years ago
But you might only be able to do this once. Because what RedHat can do is cancel your contract, and stop you from using RedHat services, and you won't have access to future versions or updates.
dxf | 2 years ago
But you might only be able to do this once. Because what RedHat can do is cancel your contract, and stop you from using RedHat services, and you won't have access to future versions or updates.
jonhohle|2 years ago
As long as one subscriber is willing to leave their contract per release, downstream derivatives should have no end of supply for each release. This may not help with patches, but many of those would come from third parties to begin with.
zugi|2 years ago
Start a consortium that creates a new LLC or non-profit organization with no ties back to the consortium. That new organization buys a license, and publishes the code until RedHat cuts them off. Start a new one and repeat.
Of course it could become a cat and mouse game, where RedHat starts denying customers it deems suspicious. They start demanding more info of their customers. But all that could be bad for business...
theonemind|2 years ago
1. You purchase release N
2. You distribute the source code to release N.
3. Red Hat terminates you.
4. You needed Red Hat N. You're doing enterprisey things or using software that runs on Red Hat.
5. Red Hat releases N + 1.
6. You try to get release N + 1 from Red Hat, because you're in the ecosystem, doing enterprisey things, using software that runs on Red Hat
7. Red Hat remembers what you did on release N and doesn't offer you release N + 1.
It doesn't quite seem like the purchase model. This barely seems to get you anything over what a Rocky or Alma or whatever scrape to put together with Red Hat damming distribution, so you might as well resort to them right at release N instead of paying Red Hat for it.
indigodaddy|2 years ago
insanitybit|2 years ago