[GH-ISSUE #78] logo needed #76

Closed
opened 2026-02-26 09:35:25 +03:00 by kerem · 15 comments
Owner

Originally created by @ThomasWaldmann on GitHub (Nov 6, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/78

for some purposes, it would be nice to have a good-looking logo, e.g. some social sites like to show some picture (and some even show a not-so-nice one if you don't provide one).

it should also be evaluated where that logo fits best into the userinterface of the software.

should be made in svg and we also need some pixel renderings of it in misc. sizes (including a new favicon).

so, if you have some artistic skills, help! :)

Originally created by @ThomasWaldmann on GitHub (Nov 6, 2013). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/78 for some purposes, it would be nice to have a good-looking logo, e.g. some social sites like to show some picture (and some even show a not-so-nice one if you don't provide one). it should also be evaluated where that logo fits best into the userinterface of the software. should be made in svg and we also need some pixel renderings of it in misc. sizes (including a new favicon). so, if you have some artistic skills, help! :)
kerem 2026-02-26 09:35:25 +03:00
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 23, 2014):

see commit comment there: b0c797f34d

<!-- gh-comment-id:41157116 --> @ThomasWaldmann commented on GitHub (Apr 23, 2014): see commit comment there: b0c797f34deb66a6fad03ed1dc98016a2b98749d
Author
Owner

@mirzazulfan commented on GitHub (Apr 4, 2019):

Hi @ThomasWaldmann i've designed a logo for your your project. If you need something else or change it, i'll fix it. Waiting you feedback.
nsupdate

<!-- gh-comment-id:479737634 --> @mirzazulfan commented on GitHub (Apr 4, 2019): Hi @ThomasWaldmann i've designed a logo for your your project. If you need something else or change it, i'll fix it. Waiting you feedback. ![nsupdate](https://user-images.githubusercontent.com/36124339/55527998-89aeef80-56c5-11e9-8d6c-a323f587b145.png)
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 4, 2019):

Looks pretty, thanks!

Just in case someone is asking: what does it show / what is the idea behind it?

<!-- gh-comment-id:479875099 --> @ThomasWaldmann commented on GitHub (Apr 4, 2019): Looks pretty, thanks! Just in case someone is asking: what does it show / what is the idea behind it?
Author
Owner

@mirzazulfan commented on GitHub (Apr 4, 2019):

Thanks for your response. I combine the server icon and update. and make the server icon form the initial letter 'ns'. if you need anything else I will make it.

<!-- gh-comment-id:479910136 --> @mirzazulfan commented on GitHub (Apr 4, 2019): Thanks for your response. I combine the server icon and update. and make the server icon form the initial letter 'ns'. if you need anything else I will make it.
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 4, 2019):

@elnappo can you do a PR adding the logo?

<!-- gh-comment-id:480031659 --> @ThomasWaldmann commented on GitHub (Apr 4, 2019): @elnappo can you do a PR adding the logo?
Author
Owner

@mirzazulfan commented on GitHub (Apr 5, 2019):

@ThomasWaldmann what color do you prefer?

<!-- gh-comment-id:480120191 --> @mirzazulfan commented on GitHub (Apr 5, 2019): @ThomasWaldmann what color do you prefer?
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 5, 2019):

From the ones shown above, the blue/white one seems to be most appealing to me.

OTOH, the nsupdate.info site is currently a rather black/grey dull thing, so not sure what's best for it and whether we can make it more pretty in future.

A minor issue with the text: nsupdate is the name of a command line tool to update a nameserver (which we do not even use internally).

So if we want to point out the difference of our software / service to that tool, guess we must talk about nsupdate.info.

<!-- gh-comment-id:480282313 --> @ThomasWaldmann commented on GitHub (Apr 5, 2019): From the ones shown above, the blue/white one seems to be most appealing to me. OTOH, the nsupdate.info site is currently a rather black/grey dull thing, so not sure what's best for it and whether we can make it more pretty in future. A minor issue with the text: `nsupdate` is the name of a command line tool to update a nameserver (which we do not even use internally). So if we want to point out the difference of our software / service to that tool, guess we must talk about `nsupdate.info`.
Author
Owner

@mirzazulfan commented on GitHub (Apr 6, 2019):

Blue and white look good. If you like it, I'll send all files and create a pull request if needed.
mockup

<!-- gh-comment-id:480515096 --> @mirzazulfan commented on GitHub (Apr 6, 2019): Blue and white look good. If you like it, I'll send all files and create a pull request if needed. ![mockup](https://user-images.githubusercontent.com/36124339/55671869-c8f46080-58be-11e9-88ff-3611b822b54f.png)
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 6, 2019):

@elnappo what do you think?

<!-- gh-comment-id:480518894 --> @ThomasWaldmann commented on GitHub (Apr 6, 2019): @elnappo what do you think?
Author
Owner

@elnappo commented on GitHub (Apr 8, 2019):

I really like the proposed logo :) Regarding the color, we should chose the color of the website based on the logo not the other way around. But I like your last proposal @mirzazulfan :)

<!-- gh-comment-id:480832138 --> @elnappo commented on GitHub (Apr 8, 2019): I really like the proposed logo :) Regarding the color, we should chose the color of the website based on the logo not the other way around. But I like your last proposal @mirzazulfan :)
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 8, 2019):

ok, so we'll go with the blue one. :-)

@mirzazulfan when doing the PR, it would be great if you could specifically note that your works are released under the same license as the rest of the project (BSD 3-clause).

i sometimes had the case in other projects where somebody wondered 10y later where all the icons came from and whether they are legally used.

<!-- gh-comment-id:480945630 --> @ThomasWaldmann commented on GitHub (Apr 8, 2019): ok, so we'll go with the blue one. :-) @mirzazulfan when doing the PR, it would be great if you could specifically note that your works are released under the same license as the rest of the project (BSD 3-clause). i sometimes had the case in other projects where somebody wondered 10y later where all the icons came from and whether they are legally used.
Author
Owner

@mirzazulfan commented on GitHub (Apr 9, 2019):

I don't really understand how to make a license, can you make it? I've created a pr #419 and you can download all editables files here , If you need anything change in the future, dont hesitate to cantact me. Thanks guys :) Best regard!

<!-- gh-comment-id:481183450 --> @mirzazulfan commented on GitHub (Apr 9, 2019): I don't really understand how to make a license, can you make it? I've created a pr #419 and you can download all editables files [here](https://drive.google.com/drive/folders/12TygV_t9vNedVA5zXNcujEN1111zXpSE) , If you need anything change in the future, dont hesitate to cantact me. Thanks guys :) Best regard!
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 9, 2019):

You just need to say in your commit comment "i created these logos myself and license them under the same license as the nsupdate.info project's license".

This is somehow the default assumption when someone contributes stuff via a PR, but in my experience, graphics seems to raise suspicions in people looking at licensing compliance / (c) issues.

<!-- gh-comment-id:481198121 --> @ThomasWaldmann commented on GitHub (Apr 9, 2019): You just need to say in your commit comment "i created these logos myself and license them under the same license as the nsupdate.info project's license". This is somehow the default assumption when someone contributes stuff via a PR, but in my experience, graphics seems to raise suspicions in people looking at licensing compliance / (c) issues.
Author
Owner

@ThomasWaldmann commented on GitHub (May 9, 2019):

fixed by #431, thanks to @mirzazulfan and @elnappo!

<!-- gh-comment-id:491097652 --> @ThomasWaldmann commented on GitHub (May 9, 2019): fixed by #431, thanks to @mirzazulfan and @elnappo!
Author
Owner

@ThomasWaldmann commented on GitHub (May 9, 2019):

live on https://www.nsupdate.info/ now! :-)

<!-- gh-comment-id:491100287 --> @ThomasWaldmann commented on GitHub (May 9, 2019): live on https://www.nsupdate.info/ now! :-)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nsupdate.info-nsupdate-info#76
No description provided.