We relicensed HyCanvas from ELv2 to AGPL. Here’s why

Описание и применение

HyCanvas перешёл с Elastic License 2.0 на AGPL‑3.0‑only, чтобы соответствовать определению открытого исходного кода, разрешить хостинг и внутреннее использование, а также поддержать модель двойной лицензии.

Задача

HyCanvas was under Elastic License 2.0, which limited hosting and made it not OSI‑approved, conflicting with the product’s open‑source positioning.

Результат

HyCanvas now meets OSI open‑source definition, allows hosting and internal use, and supports a dual‑licensing business model while maintaining clear trademark guidance.

Рабочий процесс

• 1. Release v0.3.17 with AGPL license.
• 2. Ship license files (LICENSE, NOTICE, COMMERCIAL.md, TRADEMARKS.md) in all artifacts.
• 3. Audit dependencies’ licenses (e.g., @imgly/background‑removal is AGPL‑3.0).
• 4. Publish trademark policy to distinguish official builds.
• 5. Communicate changes in release notes and FAQ.

Доказательства

Everything up to v0.3.16 was under the Elastic License 2.0 (ELv2). From v0.3.17 onwards the code is under the GNU Affero General Public License v3, AGPL-3.0-only.

Источник

You may not provide the software to others as a hosted or managed service that gives them a substantial set of its features.

Источник

The AGPL closes that gap with one rule: if you distribute HyCanvas, or let people use a modified version over a network, you offer them the complete source of your version under the same license.

Источник

Ship the license files in every artifact.

Источник

Audit your dependencies' licenses first.

Источник