Yes, nitpicking as usual: note that not all those icons are PD, so |link= is not good practice. Some in the Noun project even explicitly require attribution by name.
Topic on Talk:How to contribute
Then why are they used? Let's replace all on PD-versions?
If you find better versions that are PD please propose them here. Nemo, point taken and I will remove the |link=.
I Propose:
- File:Tools-hammer.svg for "Testing"
- File:Tango-style question icon.svg for "Support"
I believe visual consistency is more important than Public Domain license vs CC. Wikimedia Foundation Design/Agora Icon Set goes for simple black icons and I don't see a reason not to follow that trend.
See media:How to hack on Wikipedia.pdf for other icons proposed.
Well, then you need to take out icons for "Support", "Translation", "Api" (as two gears), "Development" and "Documentation". Now overall look is feeble.
I need to finish this presentation for FOSDEM before Sunday and I'm spending one day basically flying in between. I'm planning to upload the related files to Commons, and then make changes here. But all the better if someone is faster than me. :)
Note: big b/w hammer may impress agressive.
Proposals for missing icons:
Development: http://thenounproject.com/noun/source-code/#icon-No1171 Support: http://thenounproject.com/noun/first-aid/#icon-No2208
Still searching for Documentation.
Proposal for Documentation: http://thenounproject.com/noun/book/#icon-No7656
As you have seen, I have changed the icons for API and Translation. I will wait an extra day for Development, Support and Documentation just in case.
Not-obvious metaphor for API :( Meshed gears would be better...
Meshed gears are being used for Browser testing = automated testing. You hook to an API, this is where the metaphor comes from. It has been under review during several days in the context of the presentation. Before we didn't aim to identify API with a screwdriver and a wrench either, a metaphor that could also work for Development (we have a school board, not an exact metaphor either) and many other technical tasks. These icons don't aim to substitute words but to go with them.
Okay. I do not like these icons as such, and I do not feel good idea to use them "as is" as design elements on this site. I will not longer intervene in this process - do as you know. Cheers!
We can use meshed gears for API and find something else for Browser / automated testing. Any ideas?
PS: our argument plus this page made me re-think. :)
Browser / automated testing may be identify as web-page with two checkboxes nearby and/or one gear.
I think the web page icon alone works perfectly for Browser testing! Deal.
I wanted to do the changes of icons today but I got dragged by other tasks. Starting my holidays - will be back on Feb 19. Thank you for your help, patience and the marking choosing the right icons. :)
I've uploaded all the required icons and set up Project:Visual identity to list them and the credits. There are a few other icons to find or discuss, but let's do it at Project talk:Visual identity.
The “Icons credits” link needs to be marked for translation.
Done. Thank you for catching that!
Support may be associated with this icon.
Note: I posted a similar comment at Thread:Project talk:Calendar/About consistent icons/reply. I'm copying it below:
- I hope that we'll come to a point where we have a set of reusable, consistent and recognizable icons across mediums (wiki pages, blog posts, slides, etc.).
- Don't forget to add the proper credits in your slides where required. It's easy to do in a presentation, but it's a bit trickier to show credits on wiki pages, because when we use them as icons, we usually use the
link=
parameter to hijack the image's link (that would otherwise have led to the image credits). For events and the calendar, I've found a good enough workaround (credits are listed on Template:Event/doc and linked to from Template:Event header), but we'll need to make sure we show or link to proper credits wherever we use those icons.
- Perhaps we should start listing the icons somewhere (other than the template's doc) to have a central place both to define our visual language, and also to list proper credits. Maybe Project:Visual identity?