Skip to content
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

Logo #35

Open
Kiefersv opened this issue Aug 6, 2022 · 15 comments
Open

Logo #35

Kiefersv opened this issue Aug 6, 2022 · 15 comments
Labels
discussion Topics that we want to discuss

Comments

@Kiefersv
Copy link
Collaborator

Kiefersv commented Aug 6, 2022

gcmt_logo

My first draft and suggestion for a logo. Please feel free to comment and criticize.

@Kiefersv Kiefersv added the discussion Topics that we want to discuss label Aug 6, 2022
@AaronDavidSchneider
Copy link
Contributor

nice and easy logo! Really like it! Should we use gcmt as the name?

@Kiefersv
Copy link
Collaborator Author

Kiefersv commented Aug 7, 2022

gcmt_big_logo
gcmt_small_logo

Like this?

@AaronDavidSchneider
Copy link
Contributor

I think, I prefer the second one. But I don't mind :D
Thanks for the effort!

@Kiefersv
Copy link
Collaborator Author

Kiefersv commented Aug 8, 2022

I slightly prefer the upper of the two. @robinbaeyens you are the tie breaker now :D (or you can completely disagree of course)

Afterwards, we have to create the logo in a proper software since this is only done in libre office and has many small mistakes in it.

@robinbaeyens
Copy link
Collaborator

I actually preferred GCMtoolkit! It is much more descriptive than gcmt.
But from the gcmt-logo's I like the second a little bit more I guess, sorry Sven ;)

@AaronDavidSchneider
Copy link
Contributor

How about we name it GCMtoolkit and the python package is just called gcmt? Is this too confusing? We could also still name it gcmtoolkit? I agree with you @robinbaeyens that gcmt is less descriptive.

@robinbaeyens
Copy link
Collaborator

I don't think it's too confusing to have both GCMtoolkit and gcmt, although the preference would probably be to have everything named the same (i.e. GCMtoolkit). But is it worth it to go through the name changes in the code? Not sure :)

@AaronDavidSchneider
Copy link
Contributor

I honestly don't care... I can do it on Thursday, if you want me to?

@Kiefersv
Copy link
Collaborator Author

Kiefersv commented Aug 9, 2022

I like @robinbaeyens idea for the logo and the name change. It is helpful if it is descriptive (but also don't have a strong opinion on this). Only thing we then need to discuss is the camel case: GCMtoolkit, GCMToolKit, GCMToolkit or GCMtoolKit.

I will see that I can get a proper version of the logo and will write once I have a it :D

@AaronDavidSchneider
Copy link
Contributor

I think python is usually snakecase instead of camelcase. So how about gcm_toolkit ?

@robinbaeyens
Copy link
Collaborator

robinbaeyens commented Aug 9, 2022

So how about gcm_toolkit ?

Excellent!

I honestly don't care...

In Dutch we say: "Als 't kind maar een naam heeft" (as long as the child has a name... )

@Kiefersv
Copy link
Collaborator Author

I'm not a big fan of the underscore in the name, but gcm toolkit would be fine with me. We don't need to be precise with the python syntax in the name, but I had programmer friends of mine pointing it out when they first saw it. So how about this one:

gcmt_logo_v2
.

@AaronDavidSchneider
Copy link
Contributor

I guess you cant have a whitespace in a python package. But I am fine with the whitespace in the logo and maybe even the docs and stuff, and then just using the underscore for the pythonpackage? But this in the end would maybe again be kind of incoherent?!
What do you guys think?

@Kiefersv
Copy link
Collaborator Author

I think only in the logo it looks wired, everywhere else is the underscore fine

@robinbaeyens
Copy link
Collaborator

I would have underscore everywhere. The logo can be gcm toolkit or gcm_toolkit, I don't think either of them would be weird :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Topics that we want to discuss
Projects
None yet
Development

No branches or pull requests

3 participants