[GH-ISSUE #1718] [Doc] Proposal for dual licensing appflowy_editor and appflowy_board under AGPL 3.0 and MPL 2.0. #656

New issue

Closed

opened 2026-03-23 20:39:19 +00:00 by mirror · 0 comments

mirror commented

2026-03-23 20:39:19 +00:00

Owner

Originally created by @annieappflowy on GitHub (Jan 17, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/1718

Originally assigned to: @annieappflowy on GitHub.

Reasons for switching from AGPL 3.0 only

Currently residing under https://github.com/AppFlowy-IO/AppFlowy/tree/main/frontend/app_flowy/packages, appflowy_editor and appflowy_board are standalone Flutter packages, supporting multiple platforms that include native apps and the Web. The fact that mobile apps under AGPL are not common and embedding an AGPL component into a native app under a non-AGPL license is not possible puts a ceiling on the adoption of appflowy libraries. We do not want the licensing scheme to be a blocker for native app developers to use appflowy libraries in their proprietary applications because the mission of AppFlowy is to enable everyone to build applications that suit their needs well.

Why MPL v2.0?

It’s less restrictive than the GPL and LGPL but is still a copy-left license. In addition, it’s compatible with AGPL. See this FAQ for more details.

The timeline for dual-licensing

Jan 17: All future contributions to appflowy_editor and appflowy_board will be under both the AGPL and MPL but leave AppFlowy as a whole licensed under AGPL 3.0 only.

Jan 24: Seek consent via GitHub from past contributors who made contributions to any of appflowy_editor or appflowy_board.

Feb 1: Begin removing or rewriting code that cannot be relicensed

Feb 5: Separate appflowy_editor and appflowy_board from AppFlowy and create appflowy_editor and appflowy_board as two new repositories under https://github.com/AppFlowy-IO for the libraries and license them under an AGPL/MPL dual license. AppFlowy remains available under AGPL 3.0 only.

Note: The dual-licensing is accompanied by another change - a CLA assistant (license agreement) is / will be in place for open PRs and all future contributions to any of AppFlowy’s open source software projects. This is for contributors' protection as well as the protection of AppFlowy and its licensees; it does not change contributors' rights to use their contributions for any other purpose.

The purpose of this post is to create transparency into this upcoming change and open up discussions in the community.

Originally created by @annieappflowy on GitHub (Jan 17, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/1718 Originally assigned to: @annieappflowy on GitHub. Reasons for switching from AGPL 3.0 only Currently residing under https://github.com/AppFlowy-IO/AppFlowy/tree/main/frontend/app_flowy/packages, appflowy_editor and appflowy_board are standalone Flutter packages, supporting multiple platforms that include native apps and the Web. The fact that mobile apps under AGPL are not common and embedding an AGPL component into a native app under a non-AGPL license is not possible puts a ceiling on the adoption of appflowy libraries. We do not want the licensing scheme to be a blocker for native app developers to use appflowy libraries in their proprietary applications because the mission of AppFlowy is to enable everyone to build applications that suit their needs well. Why MPL v2.0? It’s less restrictive than the GPL and LGPL but is still a copy-left license. In addition, it’s compatible with AGPL. See [this FAQ](https://appflowy.gitbook.io/docs/essential-documentation/contribute-to-appflowy/software-contributions/licenses/appflowy_editor-licensing-faq) for more details. The timeline for dual-licensing Jan 17: All future contributions to [appflowy_editor](https://github.com/AppFlowy-IO/AppFlowy/tree/main/frontend/app_flowy/packages/appflowy_editor) and [appflowy_board](https://github.com/AppFlowy-IO/AppFlowy/tree/main/frontend/app_flowy/packages/appflowy_board) will be under both the AGPL and MPL but leave [AppFlowy](https://github.com/AppFlowy-IO/AppFlowy) as a whole licensed under AGPL 3.0 only. Jan 24: Seek consent via GitHub from past contributors who made contributions to any of appflowy_editor or appflowy_board. Feb 1: Begin removing or rewriting code that cannot be relicensed Feb 5: Separate appflowy_editor and appflowy_board from [AppFlowy](https://github.com/AppFlowy-IO/AppFlowy) and create appflowy_editor and appflowy_board as two new repositories under https://github.com/AppFlowy-IO for the libraries and license them under an AGPL/MPL dual license. [AppFlowy](https://github.com/AppFlowy-IO/AppFlowy) remains available under AGPL 3.0 only. Note: The dual-licensing is accompanied by another change - a CLA assistant [(license agreement)](https://cla-assistant.io/AppFlowy-IO/AppFlowy) is / will be in place for open PRs and all future contributions to any of AppFlowy’s open source software projects. This is for contributors' protection as well as the protection of AppFlowy and its licensees; it does not change contributors' rights to use their contributions for any other purpose. The purpose of this post is to create transparency into this upcoming change and open up discussions in the community.