What is Fork (Open Source)?
A fork is a copy of an open-source repository that diverges from the original to follow a different development direction.
A fork is a copy of an open-source repository that diverges from the original to follow a different development direction. Forks can be: Collaborative (contribute back to the original via pull requests), Maintenance (continue development when the original is abandoned), or Competitive (create a competitor from the original codebase).
Famous forks: LibreOffice (forked from OpenOffice), MariaDB (forked from MySQL after Oracle acquisition), NextCloud (forked from OwnCloud), and io.js (forked from Node.js, later merged back).
Fork economics: Forking is technically free but operationally expensive. The forking team must maintain the entire codebase, handle security patches, build community, and diverge enough to justify existence. Most competitive forks fail because they can't sustain the maintenance burden.
Why It Matters
The ability to fork is the ultimate open-source safety valve — it prevents any single entity from taking a project hostage. License changes, hostile acquisitions, and maintainer abandonment are all mitigated by the right to fork.
Frequently Asked Questions
What is a fork in open source?
A copy of a repository that diverges to follow a different direction. Types: collaborative (contribute back), maintenance (continue abandoned project), and competitive (create alternative).
When should you fork a project?
When the original project is: abandoned (no maintainer response), hostile (license change, paywall), or strategically misaligned (the project's direction doesn't serve your needs). Forking is a last resort.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →