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

FSF-SPDX issues in other repositories #20

Closed
davidhedlund opened this issue Sep 9, 2021 · 5 comments
Closed

FSF-SPDX issues in other repositories #20

davidhedlund opened this issue Sep 9, 2021 · 5 comments

Comments

@CAM-Gerlach
Copy link
Collaborator

CAM-Gerlach commented Sep 9, 2021

@davidhedlund Just out of curiosity, I'd be curious to know the purpose of that repo and how it intersects with this one? There didn't appear to be a high-level description of what its all actually for other than some technical discussion in the top-level readme, so I'm trying to piece together how it fits into the picture.

It seems like to distill down what is being requested here (I'm not a SPDX member myself like @goneall ), what is specifically being asked for on the code side is:

However, at least from the perspective of this API, both of these things are provided on this side (given this API has a GPL compatibility tag, and a lack of a FSFlibre tag is de-facto a false indication, given the API only includes licenses reviewed by the FSF). So unless I'm missing something, aren't the changes needed be on the SPDX side of things (i.e. other repos), or is something else needed here to support that?

@davidhedlund davidhedlund changed the title FSF-SPDX issues FSF-SPDX-spec issues Sep 10, 2021
@davidhedlund davidhedlund changed the title FSF-SPDX-spec issues FSF-SPDX issues Sep 11, 2021
@davidhedlund davidhedlund changed the title FSF-SPDX issues FSF-SPDX issues in other repositories Sep 11, 2021
@CAM-Gerlach
Copy link
Collaborator

CAM-Gerlach commented Sep 14, 2021

@goneall Given both of these things are already present here on the FSF API side and the limitations seem to be in the core SPDX projects that consumes it, is there something else we're missing here that needs to be addressed in our codebase, as this issue here seems to imply?

@goneall
Copy link
Member

goneall commented Sep 14, 2021

Given both of these things are already present here on the FSF API side and the limitations seem to be in the core SPDX projects that consumes it, is there something else we're missing here that needs to be addressed in our codebase, as this issue here seems to imply?

Yes - here's an update or plan on the 2 issues:

@goneall
Copy link
Member

goneall commented Sep 14, 2021

@davidhedlund Since these issues are being tracked in the other repos, can we close this? I don't think there are any changes needed from the fsf-api to support either of the issues referenced.

@davidhedlund
Copy link
Author

@davidhedlund Since these issues are being tracked in the other repos, can we close this? I don't think there are any changes needed from the fsf-api to support either of the issues referenced.

True. I tracked them in https://directory.fsf.org/wiki/Free_Software_Directory:SPDX_Group#Issues

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

3 participants