https://bugzilla.redhat.com/show_bug.cgi?id=2122022 --- Comment #8 from Akira TAGOH <tagoh@xxxxxxxxxx> --- BTW just waiting for the progress on upstream though, I want to bring this up to be sure. Registering the own foundry name isn't a must. we are considering to pick it up into the package name because it would be easier to recognize if a font is a part of variants/series of fonts made by same font developers/authors - for example, we use the same the foundry prefix in a package name as "google" for google-noto-fonts and google-noto-cjk-fonts. The question is that do we have another variants/typefaces made by same authors, particularly which can be used together such as sans-serif, serif, and monospace, and/or regional typefaces, etc? if this is a single font or other fonts isn't that useful to use together, we can simply omit the foundry from the package name IMHO. the family name is basically unique. it wouldn't conflicts anything else. Anyway, I can do the formal review any time. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2122022 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
