## Summary This podcast conversation criticizes Red Hat's decision to restrict access to RHEL source code and tie it to the justification that they "have to pay developers." The speakers argue that a for-profit company posting billion-dollar OpenShift revenue can't credibly use developer pay as cover for cutting off community access, especially right after layoffs that hit open source teams hardest. The core claim is that alienating hobbyists, hackers, and tinkerers destroys the long-term trust and referral pipeline that built Red Hat's customer base in the first place. ## Key Points - Red Hat's "we have to pay developers" reasoning is real but isn't the only option — the speakers say it doesn't justify the decision given ongoing profits. - Layoffs disproportionately hit open source communities (opensource.com gutted, Fedora community manager cut) in the same quarter OpenShift reportedly made a billion dollars. - A for-profit contrasts poorly with not-for-profits like the Drupal Association, where the community bands together to fund infrastructure developers during hard times. - Hobbyists and tinkerers (like the YouTuber host) bring customers to Red Hat by learning on CentOS and then recommending paid support — cutting them out kills those leads. - The host predicts maybe a quarter or two of locked-in contracts but no long-term revenue gain, and damaged trust instead. - History rhymes: this echoes the Red Hat Linux → RHEL → Fedora shift, and competitors are already forking (Alma, Rocky, with Oracle weighing in). ## Claim Atoms - **Cutting out tinkerers cuts off the customer pipeline** — hobbyists learn on free distros, then bring paying clients to Red Hat. - **For-profit firms can't hide behind "we must pay developers"** — billion-dollar profits undercut that justification. - **The decision buys short-term contracts but erodes long-term trust** — maybe a quarter or two of gains, lasting relationship damage. ## Links - Connects to: open-source licensing and stewardship debates, for-profit vs. not-for-profit open source funding models (Drupal Association), RHEL forking (Alma/Rocky/Oracle), community trust as a business asset. - [[3. Resources/MOCs/Open Source Governance MOC]] — applies-in: Joins open source licensing and community trust notes.