Re: Update on SPDX license id adoption in Fedora
Jilayne Lovejoy wrote: > It is not scalable > for Richard to submit most of the licenses to SPDX and me to create the > files for those licenses... :) On the other hand, having many people learn a complex process and use it only once is very inefficient use of man-hours. > We have been implementing labels in the Fedora License Data repo to help > indicate what is needed next. Nothing notifies me about changes to labels, so they don't work as reminders that there's more work to do, but they have some value as confirmation that the next step in the procedure is what I think it is. Björn Persson pgp4sJN8o86Zp.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedora-legal-list] Update on SPDX license id adoption in Fedora
On 2/20/23 17:51, Richard Fontana wrote: If anyone has suggestions for what form such documentation could take that would be helpful. :) Presentation: a .ods spreadsheet with one row per identifiable hunk of software, with columns: name, version, release, architecture(s), minimum date, maximum date, SPDX license(s) name-and-version (perhaps one column for each applicable license.) Then the user can search, sort, select, print, etc. The spreadsheet should be additive (cumulative) since its inception; the user easily can select any combination of desired versions, releases, etc. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedora-legal-list] Update on SPDX license id adoption in Fedora
On Mon, Feb 20, 2023 at 7:17 PM Jilayne Lovejoy wrote: > Let us know if you have any questions or suggestions for improvements. We've > had two "office hours" so far with no attendees, but happy to schedule a few > more for open discussion or questions! We've also talked about developing more documentation around help in determining how packages are licensed (and/or how to describe/represent how packages are licensed). If anyone has suggestions for what form such documentation could take that would be helpful. :) Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Update on SPDX license id adoption in Fedora
Thanks to all the package maintainers who have been diligently updating their packages to SPDX identifiers! Here are a few interesting stats: - 160 issues in the Fedora-license-data, which has resulted in 34 new license/TOML files being added to the data, and 18 more ready to be added https://gitlab.com/fedora/legal/fedora-license-data/-/issues/?sort=created_date=opened_name%5B%5D=TOML%20file%3A%3Aneeded_page_size=100 - As of the SPDX License List v3.20 release this past week, 40 new licenses have been added to the SPDX License List https://github.com/spdx/license-list-XML/releases/tag/v3.20 The vast majority of these have been as a result of Fedora's new policy (and most of those have been submitted by Richard) - We continue to improve the documentation for guidance on updating existing packages Related to process, a couple reminders: Please review the process description for license review https://docs.fedoraproject.org/en-US/legal/license-review-process/ and make sure you see the process through to the end! Issue titles in Gitlab: The License Review template does not add a Title - if you have a current issue in the Fedora License Data and could update the title to "License Review: " that would be immensely helpful. If you end up submitting the license to SPDX, ensuring the name of the license in the issue is consistent in both repos would also be really helpful. Engage with the SPDX-legal community: if your license requires submission there, helping see that process through. (It is not scalable for Richard to submit most of the licenses to SPDX and me to create the files for those licenses... :) We have been implementing labels in the Fedora License Data repo to help indicate what is needed next. I think I've caught up on noting in the corresponding the ones that have been dealt with on the SPDX side, but please check your issues and tag me if I've missed something. Don't forget the last step: create a MR to add the TOML file to the Fedora-license-data! Let us know if you have any questions or suggestions for improvements. We've had two "office hours" so far with no attendees, but happy to schedule a few more for open discussion or questions! Thanks, Jilayne ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
