# Licensing

OpenKara application code is distributed under **AGPL-3.0-only**; see
[LICENSE](LICENSE). Third-party code, libraries, models, runtimes, fonts, and
artwork retain their own licenses and notices. The project license does not
grant ownership of those components or rights to third-party trademarks.

## Earlier releases and contributions

The application code at revision `f461b2a377f0f6e7ee6a89b2be2a63954425ad9b` was distributed under
Apache-2.0, except for separately licensed material. Earlier releases remain
available under their original terms. Keep [NOTICE](NOTICE) and
[the original Apache license](LICENSES/Apache-2.0.txt) when distributing
portions originating from that code. This migration does not revoke an
existing Apache grant.

The LRC metadata parser change in [PR #466](https://github.com/thedavidweng/OpenKara/pull/466)
was submitted by Chris Joanis (GitHub: Levison) under Apache-2.0 at commit
`388252b105cba7b8e45a6ff758c2b375cbc59e6c`. Preserve its attribution and
original license. No CLA signature is presumed or recorded for that historical
contribution. His future contributions follow the new CLA signing process.

## Contributions and commercial editions

External contributions require [CLA version 1.0](CLA.md), accepted by posting
the signing statement in the PR as described in [CONTRIBUTING.md](CONTRIBUTING.md).
Contributors retain copyright and grant David Weng rights to distribute and
sublicense covered contributions under open-source, commercial, and proprietary
terms, including closed-source paid or mobile editions.

Previously merged contributions are not automatically covered by a new CLA.
An existing Apache-2.0 contribution remains usable under that original grant,
including in a proprietary derivative, subject to its notice and license
requirements. Any earlier AGPL-only contribution without sufficient additional
rights would need separate permission before proprietary reuse.

David Weng may offer separate terms only for material for which he holds
sufficient rights. The CLA does not override third-party code, dependencies,
or asset licenses. Existing recipients retain the rights granted by their
AGPL release.

## Distribution and network use

AGPL permits commercial use. Distribution of covered binaries requires
corresponding source under the applicable provisions of section 6. A modified
version that supports remote user interaction must offer its corresponding
source to those users as described in section 13. Private modifications are
not automatically required to be published, and there is no requirement to
submit changes upstream.

For each release, provide the source matching that binary and the required
build and installation material. Include applicable third-party licenses and
notices. Review App Store distribution terms separately before publishing an
edition there.

## Maintainer dependency policy

Retain the existing third-party license checks. Changing our own code to AGPL
does not authorize importing external GPL/AGPL code into a future proprietary
edition. Review all new dependencies and copied code for both the AGPL release
and intended commercial reuse. Dependency checks are an allowlist, not a
grant of commercial relicensing rights.