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

Require SPDX #1299

Open
isuruf opened this issue Apr 28, 2020 · 20 comments
Open

Require SPDX #1299

isuruf opened this issue Apr 28, 2020 · 20 comments

Comments

@isuruf
Copy link
Member

isuruf commented Apr 28, 2020

This has been working well for a while now. This would be a linter failure instead of a hint.

cc @conda-forge/core

@CJ-Wright
Copy link
Member

What is the plan to bring failing feedstocks into compliance?

@isuruf
Copy link
Member Author

isuruf commented Apr 28, 2020

Nothing. Maintainers should fix them.

@beckermr
Copy link
Member

We can propose migrations for a significant fraction of them.

@isuruf
Copy link
Member Author

isuruf commented Apr 28, 2020

I'd caution against automating it because they can be wrong especially with GPL-3.0-or-later vs GPL-3.0-only.

@beckermr
Copy link
Member

Then what do we do about the R migration? Should we ignore the linter for all of that?

@isuruf
Copy link
Member Author

isuruf commented Apr 28, 2020

For R, the information is given to us by R. We can use that.

@h-vetinari
Copy link
Member

What about those that cannot be made compatible with the current rule? Especially those that combine several licenses, or worse, have different licenses for different parts of the codebase.

Recent example I've worked on cryptography (neither AND nor OR-conjunctions between SPDX identifiers worked), suitesparse (more complicated expression).

@isuruf
Copy link
Member Author

isuruf commented Apr 28, 2020

cryptography works fine as far as I can see.

@isuruf
Copy link
Member Author

isuruf commented Apr 28, 2020

Can you open an issue for suitesparse?

@h-vetinari
Copy link
Member

@isuruf: cryptography works fine as far as I can see.

I don't think it does. The linter checks every commit but doesn't reissue the warning if the warning hasn't changed (or been cleared). If you look at conda-forge/cryptography-feedstock#37 you'll see that the warning was never cleared. It would be also easy to see by just opening a new PR.

@h-vetinari
Copy link
Member

@isuruf: Can you open an issue for suitesparse?

#1300

@jakirkham
Copy link
Member

This is done, right? Should we close?

@beckermr
Copy link
Member

Where is the PR?

@djhoese
Copy link

djhoese commented Jul 20, 2020

Found this while working on the HDF5 package which has its own license (apparently) so "HDF5" is listed: https://github.com/conda-forge/hdf5-feedstock

@isuruf
Copy link
Member Author

isuruf commented Jul 20, 2020

@djhoese, what's the issue here?

@djhoese
Copy link

djhoese commented Jul 20, 2020

That the HDF5 package wouldn't pass the linter with its current license, right? Maybe I misunderstood this issue, but it sounded like the linter would require SPDX license identifiers including compound/combined ones. The HDF5 library doesn't fit in to that.

@isuruf
Copy link
Member Author

isuruf commented Jul 20, 2020

Linter posts a comment like conda-forge/hdf5-feedstock#122 (comment) which has a link to docs https://conda-forge.org/docs/maintainer/adding_pkgs.html#spdx-identifiers-and-expressions . Docs specifically mentions HDF5.

@isuruf
Copy link
Member Author

isuruf commented Jul 20, 2020

Btw, PRs are welcome to improve docs.

@djhoese
Copy link

djhoese commented Jul 20, 2020

PRs are welcome to improve docs.

Mostly just inexperience with SPDX identifiers and this was the first time running into a non-SPDX license on a conda-forge package (I'm not a maintainer of HDF5). I probably just rushed to comment and should have read more. Thanks for the info.

@isuruf
Copy link
Member Author

isuruf commented Jul 20, 2020

That's totally fine. Docs become better when others bring a fresh perspective.

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

No branches or pull requests

6 participants