On Thu, 2025-03-20 at 15:04 -0400, Ben Beasley via legal wrote: > On Thu, Mar 20, 2025, at 1:39 PM, Michel Lind via legal wrote: > > Related question: as I understand it public domain dedications have > > to > > be vetted before use, but where is this requirement documented? > > e.g. > > https://docs.fedoraproject.org/en-US/legal/license-approval/#_overview > > does not specifically mention a special process for LicenseRef- > > Fedora- > > Public-Domain. > > This is documented in the “Updating Existing Packages” section, which > probably isn’t currently the best place for it. > > https://docs.fedoraproject.org/en-US/legal/update-existing-packages/#_public_domain
Ahh, thanks. Yes, I agree. Especially since... new package review is when we catch most of these issues We really need better ways of tracking issues affecting existing packages. Maybe once we move to forgejo we can look having a Debian style tracker flagging both bugs and nits (e.g. hey you're not using the new Python guidelines!) Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 README: https://fedoraproject.org/wiki/User:Salimma#README
signature.asc
Description: This is a digitally signed message part
-- _______________________________________________ legal mailing list -- legal@lists.fedoraproject.org To unsubscribe send an email to legal-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/legal@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
