Panel: Openwashing – How Do We Handle (and Enforce?) OSS Policies in Products?
summary
Panel lays out concrete openwashing cases and remedies: a digital‑twin vendor asked to label product open source to win public tenders without publishing code; ownCloud describes Infinite Scale as a mono‑repo on GitHub with an Apache license, public roadmap and CERN contributors; AI models like LLaMA carry user‑count restrictions (700M) that break openness; ZenDiS OpenCode vets projects, maintains an allowlist after checking ~500 licenses and lists 6,000+ users and 600+ projects to protect procurement integrity.
AI-written summary · about
chapters (11)
- 0:00Introduction to open washing
- 2:32Panelist introductions
- 4:48Why open washing is a threat
- 8:54Open source in cloud and AI
- 11:56OwnCloud’s radical open source model
- 14:33Justifying open source for businesses
- 19:48OpenCode’s gatekeeping role
- 26:03Can open source avoid cynicism?
- 30:29Open source AI and competition
- 31:59Small AI tools and open source
- 34:10Optimistic outlook on open source
related talks
25mLet’s tackle Openwashing!
01h 02mPanel: Open Source, Standards, and Economics
15mTackling Openwashers, Freeloaders and Cuckoos
38mPanel: Open Source Management Based on Open Source
33mThe Cathedral, the Bazaar, and the Coffee House
29mThe Rising Ethical Storm in Open Source
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance
16mOpen Source Consumption/ Adoption Manifesto