this post was submitted on 25 Jun 2023
76 points (100.0% liked)

Technology

37720 readers
545 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
 

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
[–] carlyman@beehaw.org 16 points 1 year ago (17 children)

Can we avoid clickbait titles? Really hoping the Lemmy community is better than what Reddit turned into.

[–] aranym@lemmy.name 23 points 1 year ago* (last edited 1 year ago) (2 children)

..I don't see how this is clickbait, this is a major damaging move to downstream distros. They can no longer use RHEL source. Also, I just copy and pasted the original article's title. RHEL is an extremely influential distro, others will follow its lead.

I actually considered changing it at first because I didn't think it properly conveyed just how damaging to open source this is. This is an inflection point for the entire space. Red Hat is one of the most influential distros and others will follow its lead.

If you disagree with my take, fair, but tell me why. Same for all the people upvoting @carlyman's comment. I want to have real discourse with you all, and I will change the title if you have good reasoning that it is in fact inaccurate. Like you said, we don't want this to be like Reddit.

[–] 13zero@kbin.social 7 points 1 year ago* (last edited 1 year ago) (2 children)

It’s also against the spirit of the GPL if not the letter. Red Hat isn’t just required to release source code to its customers upon request; that source code comes with GPL rights and restrictions attached (including the right to distribute).

Is it legal for Red Hat to require customers to waive their GPL rights? I don’t think it should be, but I don’t think courts are particularly friendly to copyleft holders.

[–] IHeartBadCode@kbin.social 15 points 1 year ago (1 children)

I will leave this article from the Software Freedom Conservancy which gives an analysis of the legal impact of the new terms of the RHEL CCS distribution in terms of the GPL.

In short, it is as you say, not distributing to the public at large is only a violation of the spirit of the GPL but not an actual legal violation. As for redistribution, the new terms stipulate that RedHat CANNOT STOP YOU from redistributing the code (unless you forgot to remove their icons/artwork/copyrightable stuff), but doing so will put you under consideration for a 30-day notice that your ability to access binaries and sources will be revoked.

Additionally, the SFC has gone ahead and assumed that RedHat will have little inclination to sell a single license to Rocky or Alma for them to them attempt a systematic way to get around their RHEL CCS distribution model. In short, RedHat has come full circle in implementing the full breadth of their hostilities towards downstream projects of their RHEL.

I know RedHat folks justify it as "None of the downstream projects helped patched anything. That the downstream projects were the ones being hostile and RedHat is just finally responding in like." I think the "none" might be over exaggerated, but RedHat has indeed submitted easily over 90% of the patches to RHEL's code base. That said, working with the community to help foster more contributions is the correct answer, not taking the ball and going home.

All in all, RedHat is basically allowed to do what it is doing. But everyone is free to not like this path RedHat has taken themselves down. I mean, there's a lot of "questionable" spirit of FOSS that multiple companies that contribute to open source do with their product. cough Java cough.

[–] JustADirtyLurker@lemmy.ml 1 points 1 year ago

Your comment should be more upvoted. Great info.

[–] aranym@lemmy.name 4 points 1 year ago* (last edited 1 year ago)

Yeah - even if it technically isn't legal, GPL violators have a long history of getting away with it. IBM has a legal team that'll scare almost anyone away.

[–] carlyman@beehaw.org 5 points 1 year ago (2 children)

I agree with the sentiment....but hard not to say this isn't a clickbait title. Let's not rely on rhetoric....let's speak with data, details, and specifics to help foster actual discourse and constructive disagreement.

[–] aranym@lemmy.name 10 points 1 year ago* (last edited 1 year ago) (1 children)

When most people think of clickbait, there is a disconnect between the content presented and the title. There is no such disconnect in this case. Your interpretation of the word is an outlier, and even if I agreed that it was clickbait, you still haven't convinced me it is a bad thing in this specific scenario.

[–] carlyman@beehaw.org 1 points 1 year ago (1 children)

There is generally some truth to clickbait titles...and the more you agree with it, the less clickbait-y it seems. "Crushing blow" is unnecessary rhetoric in my view (and I'd bet 50 cents AI wrote it).

I'm actually not arguing the intent of the article...rather just how I hope this community raises the bar in discourse.

[–] aranym@lemmy.name 4 points 1 year ago (1 children)

We clearly have a disconnect here. There's a reason I always put a quote to act as summary in the description of my article posts, they provide more detail than the title could. At the end of the day, I think providing the original title regardless of its perceived quality is the better option when these posts are glorified links anyways. (I assure you it was not from AI, The Register has pretty high journalistic standards.)

[–] carlyman@beehaw.org 1 points 1 year ago
[–] Geometric7792@kbin.social 8 points 1 year ago (1 children)

You're upset that the headline didn't have data, details and specifics in it?...

[–] carlyman@beehaw.org 4 points 1 year ago

I prefer to avoid clickbait titles and discussions around soundbites. If you prefer clickbait titles and rhetoric, so be it. I was hoping for something different.

load more comments (14 replies)