Align headers and license metadata with govern-opensource standard - #9
Open
qiuz-cz wants to merge 1 commit into
Open
Align headers and license metadata with govern-opensource standard#9qiuz-cz wants to merge 1 commit into
qiuz-cz wants to merge 1 commit into
Conversation
- Replace proprietary/confidential file headers with the standard two-line SPDX Apache-2.0 header in all Python and JS/TS sources. An open-source template must not stamp PROPRIETARY AND CONFIDENTIAL notices into every project created from it. - Fix FILE-HEADER: stray comma in 'Copyright (c),' and align to the standard header text. - pyproject.toml: PEP 639 SPDX string form (license = "Apache-2.0"), setuptools>=77 (required for PEP 639), drop the deprecated License :: classifier. Surfaced during the CTO-1890 OSS release review; matches cz-standards PR #68 and the updated Open Source at CloudZero Confluence page. Commit Generated with AI Co-Authored-By: AI
Greptile SummaryThis PR aligns the template’s source headers and Python package metadata with the Apache-2.0 open-source standard.
Confidence Score: 5/5The PR appears safe to merge because the changes consistently update licensing metadata without altering runtime behavior or breaking supported build paths. The source changes are comment-only, and the Python metadata uses the matching setuptools build requirement needed to process the new PEP 639 license expression. Important Files Changed
Reviews (1): Last reviewed commit: "Align headers and license metadata with ..." | Re-trigger Greptile |
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.
What
Brings the OSS template in line with the govern-opensource standard, surfaced during the CTO-1890 OSS release review:
Copyright (c) CloudZero - ALL RIGHTS RESERVED - PROPRIETARY AND CONFIDENTIAL ... Direct all questions to legal@cloudzero.com— a proprietary notice that every repo created from this open-source template inherits, contradicting the Apache-2.0 licensing the template exists to establish.FILE-HEADER: stray comma (Copyright (c), CloudZero) that didn't match the standard's header template or its validation regex.python/pyproject.toml: PEP 639 SPDX string form (license = "Apache-2.0"),setuptools>=77(required for PEP 639), and removal of theLicense ::classifier (deprecated by PEP 639; newer setuptools rejects it alongside a license expression).All headers verified against the standard's validation regex.
javascript/package.jsonalready declaredApache-2.0correctly — unchanged.CHANGELOG.mddeliberately untouched since it's template content shipped to downstream projects.Related
PR Generated with AI
Co-Authored-By: AI