4 ms·

> Those icons are Font Awesome 4.7, which is completely open source so you can do almost whatever you want with them. Pro vs Free still bothers me. Couldn't on

by baldfat 10y ago

> Those icons are Font Awesome 4.7, which is completely open source so you can do almost whatever you want with them. Pro vs Free still bothers me. Couldn't one of the stretch goals been to make all fonts free and open?

fortawesome 10y ago
Actually, we think the best way for us to keep making Font Awesome Free as good as it can be is to figure out how to be sustainable so we can put more time into Font Awesome. And the already-funded 38 stretch goal icon packs give 10 each back into Font Awesome Free. So that's another 380. That means FA Free will be over 1,000 icons in version 5 (up from 675). Also, the $1M stretch goal makes the SVG framework and all the code open source.
OJFord 10y ago
I wasn't aware of it before your comment, and now I'm confused, just sounds like buying 'Pro' would damage workflow. Say I have a project on Github, and I want to add some of the new icons I buy - I have to leave the icons out of the repo, and deal with whatever that means for deployment?
- 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 ago
    Wouldn'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 ago
      If someone can see a font, they can pirate it. We just don't want to make it really, really easy.
  - OJFord 10y ago
    Sorry, 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.

by baldfat 10y ago

fortawesome 10y ago

Actually, we think the best way for us to keep making Font Awesome Free as good as it can be is to figure out how to be sustainable so we can put more time into Font Awesome. And the already-funded 38 stretch goal icon packs give 10 each back into Font Awesome Free. So that's another 380. That means FA Free will be over 1,000 icons in version 5 (up from 675). Also, the $1M stretch goal makes the SVG framework and all the code open source.

OJFord 10y ago

I wasn't aware of it before your comment, and now I'm confused, just sounds like buying 'Pro' would damage workflow. Say I have a project on Github, and I want to add some of the new icons I buy - I have to leave the icons out of the repo, and deal with whatever that means for deployment?

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 ago
  Wouldn'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 ago
    If someone can see a font, they can pirate it. We just don't want to make it really, really easy.
- OJFord 10y ago
  Sorry, 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.