Wow! I was just looking for something like this. Thanks for sharing.
I especially like the permissive license -- commercial or non-commercial use with modifications allowed and no attribution requirements. Basically, you just can't sell the icons as your own work.
That means I can actually have nice icons in this project I'm doing for work. Good stuff.
Also see FlatIcon [1] which has 1000s of icons. I've been especially impressed by their download flow. Only negative is the pagination, which is a bit pants.
As someone with open projects on GitHub that may or may not be a future source of income (lol), specific and succinct language on the licensing is probably your best way to ensure adoption of your product.
I just cannot be bothered to risk using an icon font in a GitHub repo only to have to bleach every trace of it, because I misunderstood the license or the author’s intent.
To help remember just how the hell the most popular “free” font icons are licensed, I created a gist: https://gist.github.com/4443939. There is no way that overview looks simple to anyone.
This is what I as a developer think about as the very first thing, when I see a collection of free-asterisk icons.
The cognitive load of parsing the legalese, especially from the standpoint of someone with zero jurisprudence is a huge toll and reason for my personal bounce rate on similar products.
Consider what the point of your free icons are (portfolio vs. seeing your icons everywhere), and how you wish to stand out (quality vs. licensing).
They say cache invalidation and naming things are the hardest thing in programming, but licensing is definitely up there; at the very least, it is something most people in the field do not—but should—understand.
+++
tl;dr: If you launch a set of free(*) icons, crystal-clear licensing should be at the top of your checklist.
The style is different. The glyphs are similar like chars in fonts. This shoudn't be a problem. Or is a circle with a plus sign in it copyright property of Batch ?
Of course. Most icons packs include trademarks and servicemarks of companies without worrying about the legal implications. I'm a little paranoid of legal quagmires and that's why I didn't include any of them in my Clear icon pack http://appzgear.com/products/clear-icons.htm The understanding is that anybody who wants to use the trademarks can do so by downloading them directly from the companies' websites.
Loads of icon packs have customised versions of the social media icons. IANAL, but my reading of the situation is that the companies hold the copyright for the logos, but in general allow people to use the logos, and their own versions of them, to link to their services. So, for instance, if someone were to try to use a version of the Dropbox logo as the icon for their own software or service then they would be sued, but if they use the icon for a link to share something on Dropbox then that is alright because it is promoting their business.
This is great, I hope he makes more. I'd especially like to see the +,-,x overlays as separate icons. Though that's easy enough to do on your own if you needed to. Still, I love this.
[+] [-] ogreyonder|12 years ago|reply
I especially like the permissive license -- commercial or non-commercial use with modifications allowed and no attribution requirements. Basically, you just can't sell the icons as your own work.
That means I can actually have nice icons in this project I'm doing for work. Good stuff.
[+] [-] nilliams|12 years ago|reply
[1] http://www.flaticon.com
[+] [-] Ruska|12 years ago|reply
[1] http://fontawesome.io/
[+] [-] hugoroy|12 years ago|reply
> Making modifications or alterations to any of the icons does not free you to then sell, license or distribute them to anyone else.
If you’re looking for something really permissive: http://fortawesome.github.io/Font-Awesome/icons/
[+] [-] thatthatis|12 years ago|reply
That said, for what I'd use them for free commercial is far preferable to GPL.
[+] [-] pessimism|12 years ago|reply
I just cannot be bothered to risk using an icon font in a GitHub repo only to have to bleach every trace of it, because I misunderstood the license or the author’s intent.
To help remember just how the hell the most popular “free” font icons are licensed, I created a gist: https://gist.github.com/4443939. There is no way that overview looks simple to anyone.
This is what I as a developer think about as the very first thing, when I see a collection of free-asterisk icons.
The cognitive load of parsing the legalese, especially from the standpoint of someone with zero jurisprudence is a huge toll and reason for my personal bounce rate on similar products.
Consider what the point of your free icons are (portfolio vs. seeing your icons everywhere), and how you wish to stand out (quality vs. licensing).
They say cache invalidation and naming things are the hardest thing in programming, but licensing is definitely up there; at the very least, it is something most people in the field do not—but should—understand.
+++
tl;dr: If you launch a set of free(*) icons, crystal-clear licensing should be at the top of your checklist.
[+] [-] Breefield|12 years ago|reply
[+] [-] annnnd|12 years ago|reply
Any idea how to get around this?
[+] [-] ChrisArchitect|12 years ago|reply
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] chmike|12 years ago|reply
[+] [-] legulere|12 years ago|reply
[+] [-] runn1ng|12 years ago|reply
[+] [-] akrakesh|12 years ago|reply
[+] [-] sampk|12 years ago|reply
[+] [-] Chromozon|12 years ago|reply
[+] [-] Digit-Al|12 years ago|reply
[+] [-] kbutler|12 years ago|reply
In general, you can use a trademark to refer to the trademark owner's good or service. That is, you can use the Android robot to refer to Android.
[+] [-] justncase80|12 years ago|reply
[+] [-] davexunit|12 years ago|reply
Also, the license doesn't seem to be a free culture license. Lame.
[+] [-] RexRollman|12 years ago|reply
[+] [-] Spone|12 years ago|reply
[+] [-] yiransheng|12 years ago|reply
[+] [-] hadem|12 years ago|reply
[+] [-] jpamorgan|12 years ago|reply