Technology

37797 readers

25 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

TheRtRevKaiser@kbin.social

100

Red Hat strikes a crushing blow against RHEL downstreams | The Register (www.theregister.com)

submitted 2 years ago by aranym@lemmy.name to c/technology

108 comments fedilink hide all child comments

A superficially modest blog post from a senior Hatter announces that going forward, the company will only publish the source code of its CentOS Stream product to the world. In other words, only paying customers will be able to obtain the source code to Red Hat Enterprise Linux… And under the terms of their contracts with the Hat, that means that they can't publish it.

you are viewing a single comment's thread
view the rest of the comments

[–] quaddo@kbin.social 7 points 2 years ago* (last edited 2 years ago) (2 children)

From TFA:

Some commentators are pointing out that it's possible to sign up for a free Red Hat Developer account, and obtain the source code legitimately that way. This is perfectly true, but the problem is that the license agreement that you have to sign to get that account prevents you from redistributing the software.

So although the downstream distros could still get hold of the software source code, they can't actually use it. In principle, if they make substantial modifications, they can share those, but the whole raison d'être of RHEL-compatible distros is to avoid major changes and so retain "bug-for-bug compatibility."

Of course, they could take a "publish and be damned" attitude and do it anyway. At best, the likely result is immediate cancellation of their subscription and account. That could work but will result in a cat-and-mouse game: downstream distributors continually opening new free developer accounts, and the Hat potentially retaliating by blueprinting downloads and stomping on violators' accounts. It would not be a sustainable model.

At worst, though, they could face potentially getting sued into oblivion.

ETA the full context.

[–] 13zero@kbin.social 3 points 2 years ago (1 children)

Got it.

I don’t see how that could comply with the terms of the GPL.

[–] jeena@jemmy.jeena.net 1 points 2 years ago

I don't think all the code there is GPL. A lot of it is MIT, BSD, Apache, etc.

load more comments (1 replies)