chore: OSPO compliance for public repo (Apache-2.0 + REUSE) - #1662
Merged
Conversation
Repo went public; the SAP Repository Linter flagged three findings. This clears the two that are fixable in-repo: - rl-license_file (#1631): add root LICENSE with full Apache-2.0 text - rl-reuse_tool (#1633): add REUSE.toml (SAP standard v1 format, path=** aggregate annotation, External Products disclaimer) + LICENSES/Apache-2.0.txt, and replace the stale 'SAP Internal - Not for redistribution' README section with the SAP-standard Licensing section referencing the REUSE tool rl-assigned_teams (#1632) is GitHub org team config (>=2 maintainers on the admin and members teams) and must be actioned by an org owner - not fixable in-repo.
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
1 participant
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.
Why
The repo is now public, so the SAP Repository Linter (OSPO) opened three findings:
rl-license_fileLICENSE(Apache-2.0)rl-reuse_toolREUSE.toml+LICENSES/Apache-2.0.txt+ README Licensing sectionrl-assigned_teamsWhat this PR does
LICENSE— full canonical SPDX Apache-2.0 text (clears FAILED: Repository Linter Issue: rl-license_file #1631).REUSE.toml— SAP standard v1 format (matchesSAP/openui5):path = "**"aggregate annotation withSPDX-FileCopyrightText+SPDX-License-Identifier = "Apache-2.0", plus the standard SAP "External Products / API Calls" disclaimer.LICENSES/Apache-2.0.txt— license text in the REUSE-required location.README.md— replaced the stale## License → SAP Internal — Not for redistribution.with the SAP-standard## Licensingsection referencing the REUSE tool (clears FAILED: Repository Linter Issue: rl-reuse_tool #1633).License choice (Apache-2.0) and public posture confirmed with the maintainer.
rl-assigned_teamsrequires the admin team and the members team to each have ≥2 maintainers. This is GitHub org/team membership, done via the org UI or:Once maintainers are added, the linter closes #1632 on its next run.
Closes #1631, closes #1633.