I’m contributing to an open-source project and I want to use Elusive Icons however this webapp is going to be distributed in Linux packages for distros such as Ubuntu, Fedora and CentOS. The problem that we are facing is regarding Fedora Font Licensing (which you can access here: https://fedoraproject.org/wiki/Packaging:FontsPolicy). If we want to publish our .rpm package, we can’t keep any woff, woff2, otf, eot, svg or ttf font files. Instead, we have to set Elusive font family as a dependency and expose the font files installed in the server to an URL in the same domain . Unfortunately for us there are no .noarch packages for Elusive Icons, so the solution would be exporting the SVG glyphs that we want to use as paths and attach the RDF metatags with a copy of the license in each one of them. I believe that SIL OFL license forbids that.
I know that “Elusive Icons is fully open source and is GPL friendly. You can use it for commercial projects, open source projects, or really just about whatever you want” but we had issues with FontAwesome, OpenSans and Fontellico already and we had to remove them from our assets and switch to our own icons and system fonts. FA and OpenSans fortunately have .noarch packages and Fontellico clearly distinguishes the SVG glyphs from the font files by claiming the SVGs are not just part of documentation and distributed under CC BY 3.0.
How should we proceed? Can we use a single glyph as SVG? Does SIL OFL allows that? Should we attribute each icon we want to use to a specific author?
I’m contributing to an open-source project and I want to use Elusive Icons however this webapp is going to be distributed in Linux packages for distros such as Ubuntu, Fedora and CentOS. The problem that we are facing is regarding Fedora Font Licensing (which you can access here: https://fedoraproject.org/wiki/Packaging:FontsPolicy). If we want to publish our .rpm package, we can’t keep any woff, woff2, otf, eot, svg or ttf font files. Instead, we have to set Elusive font family as a dependency and expose the font files installed in the server to an URL in the same domain . Unfortunately for us there are no .noarch packages for Elusive Icons, so the solution would be exporting the SVG glyphs that we want to use as paths and attach the RDF metatags with a copy of the license in each one of them. I believe that SIL OFL license forbids that.
I know that “Elusive Icons is fully open source and is GPL friendly. You can use it for commercial projects, open source projects, or really just about whatever you want” but we had issues with FontAwesome, OpenSans and Fontellico already and we had to remove them from our assets and switch to our own icons and system fonts. FA and OpenSans fortunately have .noarch packages and Fontellico clearly distinguishes the SVG glyphs from the font files by claiming the SVGs are not just part of documentation and distributed under CC BY 3.0.
How should we proceed? Can we use a single glyph as SVG? Does SIL OFL allows that? Should we attribute each icon we want to use to a specific author?