Hi all, Sorry for joining the thread late, but a few thoughts below! > Tl;dr Please start migrating your license tag to SPDX now. Tool `license-fedora2spdx` is > your friend. The JSON format > changed - but is backwards compatible. > > > Hi. > > I want to update you on where we are with SPDX Change > https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_1 > <https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_1>;: > > > 1. All parts that are part of this phase are done. We are missing only one optional item, > and we want to automatize the > generation of legal-docs. Right now I have to manually create PR for legal-docs > whenever I release fedora-license-data. > Miroslav - having to do this manually doesn't seem optimal, do you need some help on automating this? Also, for the Allowed page https://docs.fedoraproject.org/en-US/legal/allowed-licenses/ - we have separate tables for each type of allowed and the full table with columns for each type of allowed license. Do people like having both options? Just wondering if it would be easier to use if we went one way or the other (I'd lean to one table, personally!) > 5. Please, start migrating your spec files **now**. You can use the tool > `license-fedora2spdx` from package > `license-validate`. Use this opportunity to check if your package license matches the > upstream version - especially > if you took over the package from the previous maintainer. If you are not sure what > SPDX string to use, ask for help > on the “legal” mailing > listhttps://lists.fedoraproject.org/archives/list/legal@lists.fedoraproje... > <https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.o... > Can you remind me what 'license-fedora2spdx' does / how it's being used in this context? I recall an earlier version of this, but is this now pulling data from the fedora-license-data repo in Gitlab (TOML files)? > > 7. When your license does not have an SPDX identifier, then please follow this > documentationhttps://docs.fedoraproject.org/en-US/legal/update-existing-p... > <https://docs.fedoraproject.org/en-US/legal/update-existing-packages/> > Note, I recently updated the a few things related to this, namely the info on Public Domain. I also revised the advice on using SPDX-license-diff a bit here https://docs.fedoraproject.org/en-US/legal/license-review-process/#_how_to_determine_if_a_license_or_exception_is_on_the_spdx_license_list based on my own observations. If there is any other suggestions people have, please make an issue in the documentation repo and tag me! > > 10. > > As of 2022-10-27: > > 1. There are 23302 spec files in Fedora > > 2. 264 mentions "SPDX" in the spec changelog > > 3. out of the remaining, 173 packages mention "SPDX" in dist-git log > > 4. 22865 packages need to be migrated yet. > > 5. 11371 package has straight answer from `license-fedora2spdx` and the migration is > trivial. What do you mean by "has a straight answer"? Is this when license-fedora2spdx gives you a single SPDX expression based on the Fedora shortname already in the spec License: field and based on the current fedora-license-data repo? > > 11. Right now, we are finalizing the Change proposal for phase 2 > https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_2<https:/... > is yet about to be finished and approved. The main takeaway is that we do not plan to > do any mass action before > Fedora 38 branching (I.e. 2023-02-07) > Thanks for putting up the Change Proposal - I'll add anything other thoughts there. Jilayne > > Miroslav > > on behalf of other owners of this Change (Jillayne, Neal, David, Richard, Matthew) _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
