3 ms·
If you're talking a private repo, that's no problem at all. As for a public repo, the same applies as to commercial typography. Don't make it available for dow
by fortawesome 10y ago
If you're talking a private repo, that's no problem at all.
As for a public repo, the same applies as to commercial typography. Don't make it available for download.
This is part of why we're doing Font Awesome Pro CDN. Choose your options and icon packs and we'll serve them up for you. And we're making this free for open source projects. It also means you can upgrade to a new version without pushing code if you like.
- tf2manu994 10y agoWouldn't the end-user be able to download it from the cdn anyway? Would an alternative not be to allow them in an open source repo provided that the owner adds a readme to the folder in which the font resides, telling the end-user to refrain from downloading? Edit: what about an open source non-electron web application? How would they use the font?
- fortawesome 10y agoIf someone can see a font, they can pirate it. We just don't want to make it really, really easy.
- OJFord 10y agoSorry, that wasn't clear, but yes I meant public. So I could commit, say, an HTML file that linked your CDN; I couldn't commit the actual file on the CDN and link it relatively if I wanted to host it myself for some reason? What about if the repos private, and instead of using your CDN, I serve it from my own `/assets` or whatever, does that count as making it "available for download" and therefore not allowed? Serving static files on the web and making files available for download seems a pretty tenuous distinction.