-
Notifications
You must be signed in to change notification settings - Fork 18
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
Update link in https://spdx.org/licenses/ #186
Comments
This is actually generated by the LicenseLIstPublisher. We can update the utility and "hack" the existing web page once 3.0.1 is published. |
Transferring to LicenseListPublisher to fix in the next iteration @swinslow - you may want to "hack" the current published website |
Thank you both! Is https://spdx.github.io/spdx-spec/v3.0.1/annexes/license-matching-guidelines-and-templates/ likely to continue to be the final correct URL, at least for as long as 3.0.1 remains available? |
There's an active discussion ongoing in spdx/spdx-spec#1155 We'll (very) likely to continue to redirect the above referenced URL to whatever we land on. You can also use the link without the patch release and it will redirect to the latest 3.0 patch version (currently 3.0.1). Depending on how quick we want to fix this, we can go with the 3.0 version of the URL and count on it getting redirected to whatever final URL we end up with: https://spdx.github.io/spdx-spec/v3.0/annexes/license-matching-guidelines-and-templates/ @bact - let me know if you agree. |
I think it is best to use v3.0 without the patch version and rely on the redirection. That way, there will be less burden on the license page side to keep updating and we can guarantee that people will be brought to the latest information (within scope of major.minor version). |
So in short, agrees with what @goneall purposed |
"matching guidelines" text on https://spdx.org/licenses/ still link to v2.3 spec
May need to ask LF team to update this on spdx.org, after v3.0.1 release
The new URL is likely to be:
The text was updated successfully, but these errors were encountered: