Legal gate#
The project exists to be used safely in teaching and in other projects, so the license of a dataset is treated like a test: it can fail the build.
Only
CC0-1.0andCC-BY-4.0are accepted. The allowed list is a constant inpyml_datasets/_types.pyandDatasetInforefuses anything else.Every license used has its text in
LICENSES/, andpyproject.tomldeclares the license expression of the wheel (MIT AND CC-BY-4.0 AND CC0-1.0) together withNOTICE.md.Every dataset has an evidence file in
legal/evidence/: the license, the page that states it, the date, who checked it and an archived copy of the page.python -m scripts legalfails on a missing evidence file, a mismatch between the evidence andINFO, a DOI that is missing from the citation, aTODOleft in the files, an orphan data file and a license expression that does not match the data. It fails as well when the evidence is not complete: theArchivemust be a Wayback Machine link to the license page of the evidence, and theMaintainer checkmust give the name of the maintainer and a date in UTC. The date cannot be in the future, and it cannot be earlier than the day of the archived copy, whose timestamp is in UTC too. A dataset with apendingvalue in either field cannot be merged. The check only warns when a license was verified more than a year ago.
Why not allow more licenses? Share-alike and non-commercial licenses would change the license of the whole package or limit its use, and “free for educational use” statements are not licenses. If a good dataset is excluded, it is the safer choice.
The check cannot read a license page for you. The evidence files are written by hand, and a person must re-read the page and open the archived copy, because the Wayback Machine sometimes saves an empty or blocked page. That is the purpose of the Maintainer check field.