Live data from Hacker News

Keeping Open Source Open

rockylinux.org

251–253 of 253 posts

Re: Keeping Open Source Open

#251
post #162

Earlier quoted context omitted.

So you should be well aware of community expectations. And so should Red Hat.

Community expectations aren't necessarily correct and probably won't help paying the salary of thousands of engineers.

I didn't say they were correct. I said be aware of them.

Re: Keeping Open Source Open

#252
post #236
post #156

Earlier quoted context omitted.

They are images tailored towards runtime use. They do not come with server components. For example, you can't get/download udhcpd in a UBI image.

This is a very weird situaiton. As far as I know the whole Red Hat distribution is still open source. Now they put themselves in a position to refrain from publishing their open source changes. If those changes do not flow up or down stream, how are they going to keep calling themselves open source? (They don't call themsegpes free software as far as I can tell)

UBI images are to host applications.

Do you need screen, udhcpd to do so? Nope, but you get httpd, etc. It is just a choice they made to make it easy to host your application in a RHEL container on top of OpenShift running on RHEL (fully supportable stack)

Re: Keeping Open Source Open

#253

Earlier quoted context omitted.

Do you have an example of this, since the project I work on definitely has its code synced to gitlab.. I believe that would be actuall evidence of gpl non compliance, not this dismisive current interpretation that people have. I don't think that most people who commented have a subscription.

Pushing things back to CentOS stream is not a requirement of GPL. GPL's role ends once RHEL customers get the source. Do you mean evidence of CentOS stream not being enough ? The post talks about it. Rocky needs to collate sources from several places now to create 1:1 RHEL rebuilds.

> Do you mean evidence of CentOS stream not being enough ?

I think this is what I mean, yes.

The rhel trees are synced from the centos trees. If centos git trees couldnt build, rhel couldnt build. Afaics the only time this seems to be in conflict is for important and critical cve's , which are built on a rhel specific branch. After package release these branches are merged with centos, and the local rhel branches deleted and business continues as normal.

This is an attempt not to break embargo agreements with researchers who ask for it.

Post reply on HN