Tackling Openwashers, Freeloaders and Cuckoos
summary
Defines open washing as claiming to be free software while shipping proprietary parts and shows concrete fixes: a password manager using two licenses where one is nonfree, FreeFsync that is “free” only for private use, and tactics like misleading licenses, open core, closed servers and pseudo open AI. Explains harms — unfair procurement, vendor lock‑in, loss of trust — and gives tools used: a community survey, a public repository of confusion cases and a policy goal of public money public code 2048 target plus steps public bodies can take.
AI-written summary · about
chapters (6)
- 0:00Introduction to open washing
- 3:32What is open washing
- 5:59Examples of open washing
- 8:45Why open washing harms free software
- 11:16How to combat open washing
- 13:21Actions for civil society and public administrations
related talks
25mLet’s tackle Openwashing!
36mPanel: Openwashing – How Do We Handle (and Enforce?) OSS Policies in Products?
01h 04mOpen Source, Open Mind: The Cost of Free Software
01h 38mOpen Source Licensing: Types, Strategies and Compliance
33mThe Cathedral, the Bazaar, and the Coffee House
31mUpdate on licensing - "not really" open source licenses
01h 04mOpen Source, Open Mind: The Cost of Free Software
01h 03mFree Software: It's not about the license