-
Notifications
You must be signed in to change notification settings - Fork 306
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
Direwolf logo/icon #447
Comments
I didn't even realise this project had a logo. I can't see one linked from the README.md or the user guide. Do you mean the photo of the direwolf skeleton on the first page of the user guide PDF? |
The icon I'm referring to is https://github.com/wb2osz/direwolf/blob/master/cmake/cpack/direwolf_icon.png and the ico file |
I’d happily contribute funds to the effort! The icon is workable for sure, but definitely has a “made in MSPaint as a placeholder” vibe to it. Besides, every OSS project needs an awesome mascot. |
The icon is found in:
It is a possibility as long it is original and not just copied from the Internet. ( https://duckduckgo.com/?q=direwolf&t=ffab&atb=v345-1&iar=images&iax=images&ia=images ) What did you have in mind? |
What about this one: https://iconduck.com/icons/25068/direwolf? |
Thanks for the suggestion, but ... That is part of a generic collection and could be used many other places. We don't know where it came from originally and whether there could be a copyright violation. I want to have something original and unique so there is no confusion or other potential issues. |
Just to note: it uses the Creative Commons license so you don't need to worry about copyright. |
I'm working on getting some art work commissioned (no obligations if it ends up not suitable) but it'll take some time. This should satisfy the constraints of being unique and copyright would remain with wb2osz. |
I find the direwolf logo a little weird/creepy/scary. I was wondering if you'd be interested in replacing with something more cute a fluffy if I was to commission an artist?
The text was updated successfully, but these errors were encountered: