Closed blokhin closed 4 years ago
(Draft, to be polished.)
Here is my proposal.
Small version:
Large version:
Explanation: Outside there are the various databases (various colors), possibly more of them for every provider and connected among them, but only partially. Inside there is the full network (same color) generated by Optimade that connect all entries.
Below are some variations of Giovanni's logo, which I actually find very pointful.
I like @giovannipizzi 's draft for the logo, including the font chosen.
As suggested by @blokhin , we should choose the OPTiMaDe capitalization (unless we decide to drop this capitalization entirely)
Yes, I agree we should agree on the capitalisation - personally, I think the current one OPTiMaDe
is a bit cumbersome to remember and write, see also e.g. this commit where we had to fix it in a few places (and also it does not really much the tagline "Open Databases Integration for Materials Design"...) and I would favour simplifying it to one of the following three variants - and uniform this everywhere:
Optimade
optimade
OPTIMADE
I would probably go for 3, but I'm happy to listen to other opinions
personally, I think the current one
OPTiMaDe
is a bit cumbersome to remember and write
I'm already quite used to it to the point of having no problems in typing it correctly :) So my personal opinion would be to stick to it as it is.
Edit: changing the capitalization means renaming of the repository. So there's one more advantage in retaining the old name.
Great work with the logos! I particularly like @giovannipizzi's version, and I do like that font. Regarding the capitalization, would it be ok to ask for a version of the large one with the OPTiMaDe capitalization so we can compare? (I suspect that you are right that all caps look better, but it is difficult to know for sure without having seen it rendered in the same font.)
PS here's the archive with the font and the editable source in vectors for Inkscape, please, feel free to play: optimade_logo.zip
@rartino I think the point Giovanni is trying to make is not that OPTiMaDe
does not look good (I think it looks perfectly fine - one could even argue that it looks a bit more interesting than OPTIMADE
). In practice, however, it's easy to get wrong and it requires every outsider who wants to mention it (in a paper, press release, ...) to look up the spelling.
I just know from experience that the "Quantum ESPRESSO" people already have a hard time getting people to use the right capitalization while theirs is arguably quite a bit easier to remember.
I would personally vote for OPTIMADE
.
@gmrigna Can I ask what the original reasoning for the particular choice of capitalization was?
The original reasoning starts from "Open Databases Integration for Materials Design" using "Op" from "Open", "t" from "Databases", "I" from "Integration", "Ma" from "Materials", and "De" from "Design". Then, consonants are all capitalized and vowels all small letters (except from the first letter "O"): hence, OPTiMaDe. I personally do not have a strong opinion about this. I perfectly get the point of @giovannipizzi
Based on Giovanni's logo, I have one more suggestion. optimade_logo.pdf
I like @gmrigna's logo, probably even more than mine! A few more comments/notes:
.txt
): optimade2.svg.txtI am not sure that I perfectly got what @giovannipizzi meant with the circle sizes. So, here is the svg file (which actually use the "Raleway" font) optimade_logo.svg.txt
I like @gmrigna's latest one (but maybe without a color gradient.) However, the overall shape did lead my mind a bit to the biohazard symbol; if others see the same thing, then perhaps it is something to be careful with. I'll try an alternative that takes the design away from that. Here is what I arrived at:
However, the overall shape did lead my mind a bit to the biohazard symbol
I see it too. I'm happy with @rartino's suggestion, but could you just adjust all the "connections" to make them regularly spaced (120 degrees)?
The original red hexagon of @giovannipizzi was meant to represent the OPTiMaDe API, while the purple, green, and blue branches symbolized the APIs of the different projects. The whole idea was that OPTiMaDe is creating a connection. I had simply rounded everything and added a few more projects (using other colors and adopting the gradient to show the unity, note that this could be change into a unique color). All this has completely disappeared in @rartino proposal. I do not perceive what the colors are and where OPTiMaDe is. @rartino some explanation maybe?
It reminds me the Olympic games
I don't see them as so different, but perhaps visually it connects more to @blokhin's original proposal.
It shows providers (colors + hollow circles) that provide databases (solid circles) interconnected and communicating via a common protocol, OPTiMaDe. Some of the databases organize as parts of a shared OPTiMaDe network which forms the "three leaf lily shape" of interconnectedness in the center. Some other databases (the other solid circles) are provider subdatabases which are one step removed from that network. The overall shape is meant to illustrate the providers interconnected in a three-way "handshake" as a very abstract version of @blokhin's design but with three participants.
@blokhin I see what you are saying about olympic rings. That may not be a good thing for this design.
Is the plan still to hand off these as a starting point to someone with real design experience?
Yes. But may be let's vote for all the options posted here, so that we could at least determine the favorite(s)? Let me select an appropriate voting mechanism, ideally, integrated into GitHub...
How about the number of :heart: emoticons on each post with a concrete suggestion? (I opt for :heart: because so far none have been placed on any posts here yet, and we don't want to count an old thumbs up as a vote from someone who left the discussion.)
I ❤️ ed @blokhin's Jun 11 draft because I love the cartooniness and the clear anthropomorphic cooperation. But I also ❤️ ed @giovannipizzi's latest, which I like because I see the outermost nodes as non-OPTiMaDe dbs that nevertheless benefit from OPTiMaDe by connecting to OPTiMaDe-interfacing dbs.
It seems that @giovannipizzi proposal (https://github.com/Materials-Consortia/OPTiMaDe/issues/67#issuecomment-504884406) is clearly leading. @blokhin Is it still your intention to send it to a designer? Or shall we simply try to fine tune it ourselves?
Great, we now have the preferred candidate! I will send it to a designer for polishing. As expected, there will be several modifications, so we'll probably vote again (in a separate thread).
Please, see https://github.com/Materials-Consortia/materials-consortia.github.io/issues/1
PS sorry for cross-posting!