Frenemies in FOSS: How to deal with Charter Conflicts & competing efforts
summary
Explains when a parallel project is a nuisance versus an existential threat and gives concrete responses: watch and ignore for now when hostile forks rarely gain traction, assess community signals, or absorb or improve by contributing back as Cloudera did with Hadoop or Drupal did with Symfony. Cites OpenOffice/LibreOffice, PostgreSQL vs MySQL, AWS vs Elasticsearch, Audacity/Tenacity and BSD security forks as case studies and recommends measured escalation, licensing review, or targeted community outreach rather than reflexive litigation.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:50Examples of Frenemies
- 10:45Dont the one possibility
- 12:45Display high moral ground
- 14:38Fight
- 17:54Absorb the competition
- 20:51Offer to be absorbed
- 21:33Digital sovereignty
- 23:58Closing remarks
related talks
34mWhen Your Open Source Turns to the Dark Side
32mA Fork to Reckon With: Minimizing Friction When Adopting OSS
37mTalking with management about open source
42mOpen Source at a Crossroads
32mSOS: Sustainable Open Source
27mFOSS behind the scenes - the center stage is not enough
22mWhy UX and FOSS clash and what we can do about it
29mOpen Source Contribution - How does it even work?