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
perform full provenance review #38
Comments
2023-04-26 notes based on meeting with @gfenoy:
|
@tomkralidis I worked on the provenance review again and completed the page https://github.com/ZOO-Project/ZOO-Project/wiki/ProvenanceReview It should contain everything this time and the fixes required has been made also. |
I think this file is fine, line 6 and 7 reference the copyright holder and the MIT License. |
Thanks @gfenoy. Comments:
|
For reference, to enumerate all code files (I may be missing some extensions, feel free to add/update): find . -name "*.py" -or -name "*.c" -or -name "*.h" -or -name "*.java" -or -name "*.php*" -or -name "*.js" -or -name "*.f" -or -name "*.sh" -or -name "*.bash" -or -name "*.pl" -or -name "*.mono" -or -name "*.cjs" -or -name "*.mjs" -or -name "*.cs" -or -name "*.r" | sort |
I think we are all set with two files still missing headers. |
I have added the header to the two files which were still missing one. I think that the Provenance review should now be correct and containing every code files. |
In support of OSGeo incubation, perform a full provenance review of all code files, by completing https://github.com/ZOO-Project/ZOO-Project/wiki/ProvenanceReview, including a list of all copyright holders (example: https://github.com/geopython/pygeoapi/wiki/ProjectProvenanceReview)
The text was updated successfully, but these errors were encountered: