Skip to content

Add SPDX license expression to package metadata#1439

Open
maxi-seiringer wants to merge 1 commit into
meta-pytorch:mainfrom
maxi-seiringer:patch-1
Open

Add SPDX license expression to package metadata#1439
maxi-seiringer wants to merge 1 commit into
meta-pytorch:mainfrom
maxi-seiringer:patch-1

Conversation

@maxi-seiringer
Copy link
Copy Markdown

This adds an explicit SPDX license expression to the package metadata.

The project already includes the LICENSE file via license-files, but without project.license some license-reporting tools may show less useful license metadata. BSD-3-Clause matches the repository license.

This adds an explicit SPDX license expression to the package metadata.

The project already includes the LICENSE file via license-files, but without project.license some license-reporting tools may show less useful license metadata. BSD-3-Clause matches the repository license.
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented May 21, 2026

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/meta-pytorch/torchcodec/1439

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

✅ No Failures

As of commit cedd4f5 with merge base e4be2e0 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 21, 2026

Hi @maxi-seiringer!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@NicolasHug
Copy link
Copy Markdown
Contributor

Thanks for the PR @maxi-seiringer

without project.license some license-reporting tools may show less useful license metadata

Can you share which ones exactly?

@maxi-seiringer
Copy link
Copy Markdown
Author

Thanks for the PR @maxi-seiringer

without project.license some license-reporting tools may show less useful license metadata

Can you share which ones exactly?

Yes, I use pip-licenses. For your project the license name is the license text which messes up formatting when displaying all used licenses.

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.

2 participants