Skip to content

chore: relicense to Apache-2.0 - #1

Open
simontaurus wants to merge 1 commit into
mainfrom
relicense-apache-2.0
Open

chore: relicense to Apache-2.0#1
simontaurus wants to merge 1 commit into
mainfrom
relicense-apache-2.0

Conversation

@simontaurus

Copy link
Copy Markdown
Contributor

Relicense from AGPL-3.0 to Apache-2.0.

Changes

  • LICENSE: full Apache License 2.0 text
  • NOTICE: copyright and year range, per Apache section 4(d)
  • extension.json: license-name set to Apache-2.0

Rationale

  • The AGPL network clause (section 13) obliges anyone operating the software as a service to publish their full source, which industry partners' legal reviews routinely reject.
  • Apache section 3 grants an explicit, irrevocable patent license covering claims necessarily infringed by each contribution, and terminates it for anyone bringing patent litigation over the work. MIT and the AGPL offer no comparable express grant.
  • Apache section 5 places inbound contributions under the project license by default, removing the need for a separate CLA.
  • Apache section 6 reserves trademark rights explicitly.

Compatibility

A license scan of the full OSL stack (210 composer packages, 100 extensions and skins) found no GPL-2.0-only component. Every GPL-2.0 dependency is or-later, so Apache-2.0 introduces no compatibility barrier.

Consent

Sole-authored repository. No third-party contributor holds surviving lines, so no external consent is required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant