Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NuGet.org Bug]: Universal-FOSS-exception-1.0 license missing #10225

Open
fjssilva opened this issue Oct 16, 2024 · 7 comments
Open

[NuGet.org Bug]: Universal-FOSS-exception-1.0 license missing #10225

fjssilva opened this issue Oct 16, 2024 · 7 comments

Comments

@fjssilva
Copy link

Impact

It's more difficult to complete my work

Describe the bug

License identifier 'Universal-FOSS-exception-1.0' is an approved SPDX license exception identifier but the corresponding license text cannot be found in licences.nuget.org/Universal-FOSS-exception-1.0. Can you please add it?

Repro Steps

Open the link https://licenses.nuget.org/Universal-FOSS-exception-1.0

Expected Behavior

The link above is expected to show the contents of the Universal FOSS exception 1.0 license text, same as in https://spdx.org/licenses/Universal-FOSS-exception-1.0.html.

Screenshots

No response

Additional Context and logs

This is currently breaking the licencing information in MySQL Connector/NET NuGet packages

@erdembayar
Copy link
Contributor

erdembayar commented Oct 22, 2024

@fjssilva
Thank you for filing this issue. Could you please add this license to here?
https://github.com/NuGet/NuGet.Licenses/tree/main/src/NuGet.Licenses/App_Data/Licenses

@fjssilva
Copy link
Author

fjssilva commented Oct 25, 2024

@erdembayar
I just did in PR #54, however I'm being asked to agree with .NET Foundation CLA, which I can't without involving my company's Legal team and I'm afraid that may take a while. I have to ask, can you do it yourself? If you accept to do it, the fix is pretty simple: you just have to fix the script src/NuGet.Licenses/license-text-extractor.ps1 like this and run it.

@lyndaidaii
Copy link
Contributor

@fjssilva, thank you for your feedback. We are currently working on this. Will get back to you once we get decision from legal team.

@fjssilva
Copy link
Author

fjssilva commented Nov 8, 2024

@lyndaidaii, the PR is finished and reviewed but stuck on the CLA issue. Can you please confirm if the PR can be accepted as-is? Or whether your are willing to reproduce the fix yourselves?
Thanks.

@lyndaidaii
Copy link
Contributor

@agr is currently active looking into your PR.

@fjssilva
Copy link
Author

fjssilva commented Nov 9, 2024

Yes he is, and he's the one who approved the PR, however, his last comment was "@fjssilva, you'd need to NuGet/NuGet.Licenses#54 (comment) to CLA in order for this PR to be unblocked for merging."

My question is whether there's a way of skipping the CLA, for all the reasons I already explained. IIUC, two weeks ago you said something about checking with legal. Are there any news regarding this?

@erdembayar
Copy link
Contributor

Yes he is, and he's the one who approved the PR, however, his last comment was "@fjssilva, you'd need to NuGet/NuGet.Licenses#54 (comment) to CLA in order for this PR to be unblocked for merging."

My question is whether there's a way of skipping the CLA, for all the reasons I already explained. IIUC, two weeks ago you said something about checking with legal. Are there any news regarding this?

@agr 's comment was about below CLA:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants