Three non-negotiables on the LG U+ RHEL-layering path - drawn before the technical debate, with a lawyer-and-everybody-else escape hatch

July 29, 2026 at 9:02 PMstrategyhigh

Situation

After Howard produced a document mapping what is technically possible for layering CIQ/Rocky packages onto a RHEL host, Peter opened his reply to Bjorn with three flat lines: (1) we are not going to take CIQ packages and present them as RH packages, (2) we are not going to have CIQ repos that point to or include RH key files, (3) we are not going to host any RH files ourselves. He named the Oracle precedent Howard cited - listing RH as its own EFI vendor directory - as something CIQ can do technically but not legally or morally. He then supplied the only conditions under which he would revisit: a room where everyone confirms they understood the question, a lawyer who agrees, and evidence that CIQ would not be the only party doing it. Even then he held that it remains another release chain that is real work.

Reasoning

Peter separated technically possible from business possible before arguing any of the engineering, because the engineering conversation was already drifting on loose language - there are a bunch of ways to make this work technically, and no way to make it work reliably long term while signing as CIQ, not hosting RH binaries, and not masquerading as RH. He also refused to treat open source as a licence to violate trademark: open source means we have access to the code, not that we get to violate trademark law. The escape hatch is deliberately shaped so the legality objection can be retired without the cost objection being retired - if everyone else were doing it, the this is wrong and illegal and stupid part goes away, but it is STILL another release we need to support. And the appetite question is escalated to a joint Peter-and-Bjorn call, not an engineering call: if CIQ were the only party doing this, you and I should have a conversation about our appetite for getting sued.

Additional Context

Follows the 7/27 definitive no to LG U+ cross-distro package support. Bjorn was pressure-testing hypotheticals and had asked earlier whether Oracle and RH might have an agreement. Peter noted he had asked can we point to RH signing authority a month back and got a resounding no from engineering. Also flagged the durable-maintenance cost even if the legal path cleared: Rocky packages next to RH packages in a repo MIGHT work for a while but WILL break eventually, and would require manual CVE porting where CIQ packages diverge from RH.

Observed Evidence

Direct numbered statement in Slack DM to Bjorn at 16:40 PDT 7/28, followed by the conditional revisit criteria at 17:03. Corroborated in the Justin Haynes DM the same evening and in the multi-party group DM later that night.

Matching Patterns

45%
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict(involves Bjorn Hovland and Howard, same category (strategy), supplies a criterion rather than only a verdict)

Confidence Breakdown

34/35
Evidence
18/30
Pattern
20/20
Source
14/15
Corroboration

Reasoning Depth Analysis

Org Signal:Engineering leadership will state the legal and ethical boundary before the technical feasibility argument, so nobody has to litigate feasibility to arrive at a no.
Who Affected:Howard (whose document is being partly reclassified from proposal to inventory), Justin Haynes and the release-engineering team who would own the new chain, Kelly Hall on any contract framing, and Rocky/RESF whose trademark posture is downstream.
Precedent:Sets the rule that technically possible is not an argument, and that a legality objection can only be retired by a lawyer plus evidence CIQ would not be a lone actor - not by an engineer saying it can be made to work.
Consequences:Real: no CIQ repo will point at RH keys, no RH binaries hosted, no CIQ package presented as RH. The lawsuit-appetite conversation is genuinely reserved rather than rhetorical.
Timing:Now because Howard had just produced the document and Bjorn was actively reading it - the boundary had to land before the document became a menu.

Source

reflection

AI Confidence

86%

Related Context

💬
DM with Bjorn Hovland

slack

So here are a few points to align on, to help parse through what in Howards document. here is what is technically possible but not business possible or reasonably feasible. I would argue: 1. We are not going to take CIQ packages and present them as RH packages 2. We are not going to have CIQ repos that point to or include RH key files 3. We are not going to host any RH files ourselves.

💬
DM with Bjorn Hovland - the escape hatch

slack

So - I will consider your hypothetical. But I will also point out that I asked can we point to RH signing authority a month back and got a resounding No... Open source means we have access to the code. Not that we get to violate trademark law... And then I would want a lawyer to agree with them. And then after that, if we are the ONLY people doing this You and I should have a conversation about our appetite for getting sued. But if everyone else were doing it... then sure, go for it. It is STILL another release we need to support.

💬
DM with Justin Haynes

slack

Yup. I walked bjorn through how it all works this afternoon. If we were to do something like this, it will be treated as a whole new release chain that would need to be supported by 3 people. And it is stupid.

Outcome

No outcome recorded yet.

Decision ID: f9eda5df-1b50-4aad-a8d3-eb06193132aa