-
Notifications
You must be signed in to change notification settings - Fork 19
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
Added logo #669
Added logo #669
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logo design and execution are both fantastic. Brilliant work 💯
TLDR: I think we should decide the (related) logos for all other NCAS Data Tools libraries before committing to this very specific design for cf-python, so should get agreement on those after some input from Andy and Ros (and more from David too), maybe even the whole of CMS, before merging.
But before we merge this to christen the final logo, I am just wondering what the plan might be for logos for the other NCAS Data Tools libraries? Whilst obviously cf is of paprticular concern here, I think it would be wise to work out what logo we want across all such libraries before committing to one for a given library. From my opening comment on #508 (quoting myself!):
I think given the links between these libraries, including the dependency for some pairs, it would be best (and also most efficient) to create a set of logos together that are inter-related in some aspect. to highlight the grouping, but also with slight differences across the set to distinguish.
Assuming agreement and ultimate permission from the original developers, I think the following five would be a good group to include as the set, but with an underlying idea for a theme to relate the logos, it should be quite simple to readily create a new design that fits with the rest should one or more new NCAS CF Python tools ermege (so we can keep in mind extensibility):
cfdm;
cf-python;
cfunits;
cf-plot;
cf-checker.
(We can now add cf-view to the list!) Of course, we'd want input and permission from Andy and Ros as creators of some of those as to what they might want.
My main thought would be that we can use the precise logo shape and form as added here, but vary the colours a bit for the six different libraries to distinguish them, and also add some small text curving around the globe to type the name of the library, i.e. add '-python', ''dm', etc. in small letters in each case. But that's just one idea. I definitely think folk would be keen to use a variant of this particular logo, because it's great IMO, but we should ask to be sure (I don't think it will time-consuming or controversial, hopefully just a few quick discussions)...
What do you think Ankit and @davidhassell? (In particular Ankit are you happy to create several variants on the logo we can use across other libraries, and check the library originators are happy to use them?)
That's true Sadie, we should give it a thought because new NCAS CF Data Tools will keep growing (George's upcoming cf-store?) and it'll be great if they are all cohesive. Also, (not the main point but) this will make it easier to highlight the bunch of tools together when it comes to the next board meeting and stuff. We need to involve Bryan in this discussion too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, let's go!
Resolves #508.
A quick preview: