-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design a logo for the project #14
Comments
Hello @Daniel-Mietchen , I am Vasant Joseph. I am a class 12 student. I have skills in designing(Photoshop, premiere pro), presentation, and anything which is given to me, which I can do. I am sincere to my work. If there is anything which I can do to help, please inform me. This is my first time at Mozilla global sprint. |
Hello @daniellecrobinson , I am Vasant Joseph. I am a class 12 student. I have skills in designing(Photoshop, premiere pro), presentation, and anything which is given to me, which I can do. I am sincere to my work. If there is anything which I can do to help, please inform me. This is my first time at Mozilla global sprint. |
Hi @VasantJ3 @Kevin-Wangome - thanks for pitching in here. We're about to get going on the US East coast. The logo above is nice but it refers to a typo (JFrost) rather than our initiative's shorthand (JROST) but I like it nonetheless, since the snowflake image could be seen as a representation of a landscape. So what about dropping the J from the above and accentuating the nodes and edges of the snowflake with slight variations of colour, size and shape to represent individual tools or infrastructures in the open science landscapes, and the connections between them? Slightly morphing the overall shape of the snowflake to something a bit less symmetrical (perhaps as seen from an angle) might also make sense. |
@dwhly Can you put that up as a SVG as well, perhaps via Wikimedia Commons again? |
As folks are designing, it might be helpful to consider how logos are often needed in various contexts and think through how your design would work in all cases:
In case it's helpful for folks, here are SVG files for the initial logo used by the Joint Roadmap for Open Science Tools. Note that this logo is very provisional, made so the project would have something to use quickly as it started. The "design" was simply the project's initials in the Noto Sans font currently used on the website. |
Hello,
We followed your instructions and we tried our creative best to link all
images together. We hope that you like it and look forward to your feedback.
Regards,
Faith Mwanyolo
Kevin Kinyua
…On Thu, May 10, 2018 at 9:14 PM, Nate Angell ***@***.***> wrote:
As folks are designing, it might be helpful to consider how logos are
often needed in various contexts and think through how your design would
work in all cases:
- horizontally (eg, alongside other logos with similar horizontal
shapes)
- square (eg, GitHub avatars)
- circular (eg, Twitter avatars)
- very small (eg, favicons; logos with lots of detail don't work well
when they are very small)
- one color (eg, in one-color print materials)
- reversed (eg, on dark backgrounds)
- with a wordmark (eg, a logo alongside the initials or name of the
project)
In case it's helpful for folks, here are SVG files for the initial logo
used by the Joint Roadmap for Open Science Tools. Note that this logo is
very provisional, made so the project would have something to use quickly
as it started. The "design" was simply the project's initials in the Noto
Sans font <https://fonts.google.com/specimen/Noto+Sans> currently used on the
website <http://jrost.org/>.
- [JROST logo: black on white](https://commons.
wikimedia.org/wiki/File:JROST_Logo_(black_on_white).svg
<https://commons.wikimedia.org/wiki/File:JROST_Logo_(black_on_white).svg>
- [JROST logo: white on black](https://commons.
wikimedia.org/wiki/File:JROST_Logo_(white_on_black).svg
<https://commons.wikimedia.org/wiki/File:JROST_Logo_(white_on_black).svg>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUr1fq_RFu3m2it2rIzToOYavUarzxXbks5txIOigaJpZM4T5H3L>
.
--
*Kinyua Kevin Wangome*
*+254 723 052 500*
*[email protected] <[email protected]>*
*[email protected] <[email protected]>*
|
@Kevin-Wangome that sounds great, but where can we see your new version? |
Which one of these do you feel looks good?
…On Fri, May 11, 2018 at 1:27 PM, Daniel Mietchen ***@***.***> wrote:
@Kevin-Wangome <https://github.com/Kevin-Wangome> that sounds great, but
where can we see your new version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUr1fqoGoPVj2AhuB6-5FNN3Et4ON-H-ks5txWeTgaJpZM4T5H3L>
.
--
*Kinyua Kevin Wangome*
*+254 723 052 500*
*[email protected] <[email protected]>*
*[email protected] <[email protected]>*
|
@Kevin-Wangome I can't find anything like a logo to look at - please upload the images here or add links that point to them. |
The interim logo has been proposed for deletion on Commons: https://commons.wikimedia.org/w/index.php?title=File:JROST_over_Stonehenge-01.png&oldid=305624775 . I left a comment there but perhaps we should take this as an indication to get back to working on this logo. |
Hello @Daniel-Mietchen, I'm a graphic designer and i would love to make you a logo if you would have me. If you accept, I will make you a logo and it's free. |
This issue was moved to OpenScienceRoadmap/jrost#33 |
One thing to think about during and after the sprint is how a JROST logo might look like.
The image we are currently using in this repo's README is just a very first shot at visualizing what it is that we are aiming at. It captures some aspects of the project but not others, and it is not very usable as a logo.
Another starting point is the initial logo used over at https://twitter.com/OpenSciRoadmap (see archive).
It is usable as a logo but basically does not capture anything about the ideas of open science, a roadmap and doing it jointly.
The text was updated successfully, but these errors were encountered: