On Sat, Nov 16, 2024 at 4:05 PM Richard Fontana <rfontana@xxxxxxxxxx> wrote: > > On Sat, Nov 16, 2024 at 8:35 AM Peter Lemenkov via legal > <legal@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > Hello! I've stumbled upon the following legal text (a bunch of usually > > bundled UTF-conversion routines are licensed under this one): > > > > ``` > > Copyright 2001-2004 Unicode, Inc. > > > > Disclaimer > > > > This source code is provided as is by Unicode, Inc. No claims are > > made as to fitness for any particular purpose. No warranties of any > > kind are expressed or implied. The recipient agrees to determine > > applicability of information provided. If this file has been > > purchased on magnetic or optical media from Unicode, Inc., the > > sole remedy for any claim will be exchange of defective media > > within 90 days of receipt. > > > > Limitations on Rights to Redistribute This Code > > > > Unicode, Inc. hereby grants the right to freely use the information > > supplied in this file in the creation of products supporting the > > Unicode Standard, and to make copies of this file in any form > > for internal or external distribution as long as this notice > > remains attached. > > ``` > > > > What's the proper SPDX tag for this one? License checking tool during > > the fedora-review says its "Unicode strict" but license-fedora2spdx > > doesn't know about this one although it is a quite popular one > > according to GitHub > > > > * https://github.com/search?q="This+source+code+is+provided+as+is+by+Unicode%2C+Inc"&type=code > -infrastructure/new_issue > > This license is `LicenseRef-Unicode-legacy-source-code` and is *not-allowed* > https://gitlab.com/fedora/legal/fedora-license-data/-/blob/main/data/LicenseRef-Unicode-legacy-source-code.toml?ref_type=heads Ah snap. > However, in at least some cases we've concluded that the license is > irrelevant because it is associated with stuff that is presumed not to > require a license. There have been other situations where a later, > less problematic Unicode license was introduced to cover stuff > purportedly covered by an earlier non-FOSS Unicode license. Please > open an issue at fedora-license-data and we can review the specific > case you're encountering. I'm afraid in my case it cannot be ignored. I am trying to add unshield application to Fedora which is used for extracting InstallShield archives. The code licensed under LicenseRef-Unicode-legacy-source-code is used for converting filenames from UTF16 to UTF8. Good news I just reimplemented it under MIT license, submitted upstream where my code was accepted already! * https://github.com/twogood/unshield/pull/185 https://bugzilla.redhat.com/2324996 -- With best regards, Peter Lemenkov. -- _______________________________________________ legal mailing list -- legal@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to legal-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/legal@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
