chore: relicense from AGPL-3.0 to Apache-2.0#443
Merged
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
a5bebbf to
a3882ca
Compare
Contributor
|
LGTM. Before we continue, we need to do two steps:
|
Contributor
Ping me when these steps are conducted and we can merge. |
Part of the OSPO-driven migration of ownCloud repositories toward Apache-2.0, following the Apache Software Foundation's third-party license policy (AGPL-3.0 is Category X). - Replace LICENSE with Apache-2.0 full text - Update "license" field in all package.json files - Add REUSE.toml + LICENSES/ for REUSE 3.x compliance - Add NOTICE with third-party attributions - Add license-check (reuse lint) and dependency-license-check CI jobs - Update OCI image label, README badge, and docs Signed-off-by: Lukas Hirt <info@hirt.cz>
a3882ca to
5329aa0
Compare
Collaborator
Author
|
@dj4oC the latest commit has been released and is also archived in the following branch https://github.com/owncloud/web-extensions/tree/archived/last-agpl-3-commit |
dj4oC
approved these changes
Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part of the OSPO-driven migration of ownCloud repositories toward Apache-2.0, following the Apache Software Foundation's third-party license policy (AGPL-3.0 is Category X).
License compliance (REUSE)
Why REUSE?
REUSE is a specification from the FSFE that defines a machine-readable, SPDX-based way to declare copyright and license information for every file in a repository. No more "check the root LICENSE file and hope for the best." It is the standard used by Apache, Eclipse, and the Linux kernel ecosystem for tooling-verifiable compliance. Adding it here means:
Why REUSE.toml?
REUSE.toml is the REUSE 3.x bulk-annotation file. Rather than embedding an SPDX-License-Identifier header in every source file, the .toml declares licensing by path glob — cleaner for a repo that was not REUSE-aware from the start. It covers two cases:
Why the LICENSES/ directory?
The REUSE spec (and SPDX) require that the full license text for every SPDX identifier referenced in the project lives in LICENSES/.txt. This serves two purposes:
Two files are therefore required: