-
Notifications
You must be signed in to change notification settings - Fork 39
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
Is this still not authoritative? #47
Comments
It's still not authoritative, correct; I need to spend more time weeding out any last issues and moving the OSI site to use this |
@paultag let us know if there is anything we can do to help. |
@paultag Can you give me a quick status check here? It appears this and the OSI site never synced up. We have multiple interests (ClearlyDefined, web updates, etc.) in standardizing the license text and I do not want to break/abandon/neglect this work. Any updates appreciated. Thanks - Patrick |
API is missing at least
|
Any update on the status of the API would be appreciated. |
Hi @Nosferican, no one is currently allocated to work on this, so unfortunately I don't have any updates for you. Can you let us know what issues you found with the SPDX license list? |
I could contribute to the project whenever I find time if there is public access to the data or specific tasks in the roadmap. |
Bump. |
I can confirm it is now OSI's intent to make this resource authoritative and to maintain it. |
Question is better directed at smaffulli (I can't figure out how to reassign). The plan is for an authoritative resource, I just can't speak to whether this will be it. |
Hi. Your README says that this is not an authoritative source of information. I think you might have forgot to update the status after this got published. Note that the page contains two links to this repository in the last and second to last paragraphs.
The text was updated successfully, but these errors were encountered: