- Name: Nicolas Mailhot (probably a good idea to consider Jens Petersen as co-lead and backup)
- email: <nim AT fedoraproject.org>
- Targeted release: Fedora 11
- Last updated: 2009-01-24
- Percentage of completion: 40%:
- rpm support files have been written, proofed and published
- packaging guidelines have been written, discussed, approved and published
- complementary documentation has been written
- most affected packagers have been notified (those we could identify)
- distribution default font packages have been converted
- i18n-controlled font packages are being converted
- progress on other packages is uneven and varies depending on packager disponibility, goodwill and experience
The best way to follow progress is probably the bugzilla tracker.
Since the Fonts special interest group was created rules on the legal and technical aspects have been progressively written and refined. Thanks to the fine Fedora review process they've mostly been applied to font packages created since.
However a lot of pre-existing font packages have never been changed to conform to those rules, and packagers that shipped fonts as part of some other whole have largely ignored them. Targeted licensing or packaging audits happened, but never distribution-wide.
The aim of this Feature is to clean up the cruft and try to make sure we follow our own packaging guidelines.
Benefit to Fedora
Our guidelines address multiple problems and thus enforcing them comprehensively will provide multiple benefits:
- purging the distribution of fonts we distribute under unclear, inappropriate or plain unlawful licensing conditions.
- exposing all our fonts in our primary font system, fontconfig. It is unacceptable that years after fontconfig was generalised some fonts are still segregated inside apps, especially since the packaging of many of them was requested by users meanwhile. Just making sure existing Fedora fonts are properly exposed in fontconfig would increase our user-visible font offering tremendously.
- fixing all the packaging bugs which have been introduced by the free-form variations on fontconfig scriptlets our packagers have unfortunately been fond of in the past. The new guidelines are much more rigid and only allow the exact pattern our fontconfig maintainer approved.
- clearly signalling upstreams what our target font system is so they stop procrastinating and clinging to brittle marginal font resolution systems that increase our maintenance burden.
- reducing our spin, mirror and bandwidth requirements, by identifying and removing the unnecessary duplication of the same big font files in multiple packages.
- cleanly separating each font family in a specific package, to present users a uniform font selection granularity and stop forcing the installation of unrelated material just to get a particular font.
- presenting users consistent discoverable font package names.
- preparing for Features/AutomaticFontInstallation and increasing its effectiveness. Having the infrastructure to perform automatic font installation is useless without a pool of clean font packages to install. Features/AutomaticFontInstallation will require rebuilding of font packages to add autoinstall-related metadata. This can only be automated if the font packages are sane in the first place.
- removing new packager uncertainty by exposing them to a pool of consistent packages.
- sensitising non-fonts packagers to the constraints induced by the fonts they ship.
- enhancing our desktop with the rich font complement expected by today's users.
- leading the advancement of free, open software and content at a time the free/open font scene is undergoing tectonic changes.
How To Test
- Install packages in the fonts and legacy-fonts Fedora 10 groups,
- Install other packages affected by the bugzilla tracker,
- Check yum or packagekit manage to update this packageset to its Rawhide/Fedora devel/Fedora 11 test versions,
- Check that all the F11 font package names conform to Packaging:FontsPolicy#Naming,
- Check that all the different font families are properly split in independent packages in F11, and that you can un-install other font or application packages without removing the one you want to keep: Packaging:FontsPolicy#Package_layout_for_fonts,
- Check they're all declared in the F11 fonts or legacy-fonts groups: Packaging:FontsPolicy#Grouping,
- (For packagers), check the new spec files conform to our new templates: Packaging:FontsPolicy#Technical_implementation,
- Check that the fontconfig rules packagers wrote are sane, do not substitute their font to unrelated ones in fontconfig-aware apps such as firefox, and do not pre-empt better fonts for a particular locale (especially for unicode blocks shared by multiple scripts, typically CJK locales).
- Check a clean install works fine too, and that no spin references a font package name that will disappear in Fedora 11.
- Check the problems in the bugzilla tracker are properly taken care of, and add new entries if necessary
- users will (hopefully) notice a much larger font complement in applications, with more flexible installation possibilities.
- more fonts we do not provide will be substituted properly.
- the need for third-party sites advising to install other fonts outside Fedora packages will diminish.
- kickstart files and other howtos and third party scripts that reference our old package names will need to be updated.
- it is a large change, even with lots of QA some new problems are likely to make it to the final release
- many fonts that were left to rot in peace inside obscure applications will now be exposed to a larger public, who is bound to identify new problems.
The changes are spread over more than a hundred of existing source packages. They range from trivial (changing a font package dependency name), easy (adapting a recent guidelines-compliant package to the latest guidelines changes) and hard (untangling packages which have accumulated many fonts without installing them in the proper place, and without checking their licensing properly).
They can only be performed in a distributed manner by each packager with a QA team checking no big mistakes are made.
The completion of this feature is thus dependant on the goodwill of every packager dealing with fonts in the distribution. It is unfortunately probable some of them will decide they're not concerned, and will hamper the change by not cleaning up their font dependencies or font installation.
None needed. The effectiveness of this feature does depend on the number of packages changed, and it would be better for Fedora and its derivatives if those changes were cleanly concentrated in a single release cycle, but continuing it the next cycle is not a technical problem.
Extensive documentation has been written:
- clear, complete and accurate packaging guidelines: Packaging:FontsPolicy
- wikified packaging templates: simple, multi-font
- helper rpm macros and text templates: Packaging:FontsPolicy#Technical_implementation
- a FAQ: Shipping fonts in Fedora (FAQ)
- plus all the pre-existing material in Category:Fonts_packaging
Fedora font packages underwent a massive reorganisation for Fedora 11. Many pre-existing font packages have been renamed or split. Fonts are now systematically exposed in fontconfig the primary Fedora font system.
You should now have access to more fonts in Fedora, with a font-family granularity, both in the installer and in applications.
As usual the complete list of font package changes and additions is available here.
Comments and Discussion
- Probably meaningless given all the different ways to measure this operation, and since all font packages have not the same user visibility
- Non modifiable…
- Yes it already unearthed some proprietary fonts we had no right to distribute and who were owned by fierce Linux competitors.
- It is common for upstreams to copy a version of Vera, DejaVu or Freefont in their releases instead of thinking on how to use the system one
- For example, one should be able to install opensymbol without openoffice.org binaries.
- Is it a good idea to show the dependency tree, show resolved, view as bug list, and change columns to show component names and order by change date.
- None of our current Packaging:FontsPolicy requirements are particularly new, a lot of them were present in previous guideline versions, but some packagers chose to ignore them so far.