Skip to main content
Open Source Licensing CC0 Community

Why We Chose CC0 1.0 Universal for a Code Editor

Public domain licensing, no CLA, no copyright assignment - maximum freedom.

CodeEditorLand 6 min read

Why We Chose CC0 1.0 Universal for a Code Editor

Code Editor Land is released under CC0 1.0 Universal - a public domain dedication. This means the entire codebase, including every Rust crate, TypeScript package, and build script, carries no copyright restrictions whatsoever.

What CC0 Actually Means

CC0 is not a license in the traditional sense. It is a waiver. The copyright holder (CodeEditorLand Foundation, operated by PlayForm, Sofia, Bulgaria) irrevocably surrenders all copyright and related rights to the work, to the fullest extent permitted by law. Where waiver is not legally possible (as in some jurisdictions), CC0 includes a permissive fallback license.

In practical terms:

  • You can use Land’s code in proprietary software.
  • You can modify it without publishing your changes.
  • You do not need to include attribution (though it is appreciated).
  • You can sell products built on top of it.
  • No patent claims are made or reserved.

Many open-source projects require contributors to sign a Contributor License Agreement (CLA) that transfers or grants broad rights over their contributions. Others require full copyright assignment to a corporate entity.

Land requires neither.

When you submit a pull request to any CodeEditorLand repository, your contribution is accepted under the same CC0 dedication. There is no paperwork, no legal review, no waiting period. You retain the ability to use your own code however you wish - CC0 does not restrict the contributor, only the project’s ability to restrict others.

Why Not MIT, Apache 2.0, or GPL?

Each of these licenses carries conditions that create friction:

LicenseCondition
MITMust include copyright notice and license text
Apache 2.0Must include notice, state changes, patent grant
GPL 3.0Must distribute source for derivative works

These conditions are reasonable and well-intentioned. But for a code editor - a tool that developers use to build everything else - we wanted zero friction. You should not need a lawyer to decide whether you can embed a snippet from your editor’s source into your project.

CC0 eliminates that question entirely.

How NLnet Makes This Possible

Developing a full-featured code editor without a commercial license or a SaaS revenue model requires funding that does not depend on restricting the output. The NGI0 Commons Fund (grant No. 101135429), administered by the NLnet Foundation, provides exactly this. The grant funds development of open internet infrastructure without requiring proprietary lock-in.

PlayForm (Sofia, Bulgaria) operates the CodeEditorLand Foundation under this grant. The funding model ensures that CC0 licensing is sustainable - contributors and maintainers are compensated through public interest funding, not through monetizing user data or restricting distribution.

What This Means for You

If you are an individual developer, CC0 means Land is yours. Fork it, ship it, break it apart, rebuild it.

If you are a company, CC0 means there is no license compliance burden. Your legal team does not need to audit it. Your procurement process does not need to flag it.

If you are a contributor, CC0 means your code reaches the widest possible audience without gatekeepers.

That is the kind of freedom a code editor should provide.