Voting for new logo #1516
Comments
lunny
added
the
type/proposal
|
Logo by @kolaente #1312 (comment) |
|
Logo by @qdbdbp #1260 (comment) |
|
Just a quick heads-up on both though... Using the Git-logo in our logo is actually not legal: https://git-scm.com/trademark ... And technically neither is using the term "Git" in the name 🙄 So before starting to use this logo, we should send an email to trademark@sfconservancy.org asking if it's okey... |
|
But the SF are more or less nice people, they allowed the usage for gitolite, GitLab, but one should ask for the written permission |
|
@strk please comment after that two vote replies. So I deleted your comment. |
|
@agaida Both of those have been Grandfathered, and none of them use the git-logo in their logo (and never have) Also from Gitolites website: http://gitolite.com/gitolite/index.html#license
|
|
So, I think we will have to rewrite the tea tag to remove the Git reference. Is there any other generic symbol that refer to VCS? |
|
I would wait for the response from SF first. |
|
I think VS Code changed git icon to this one because of license issues
|
Do you have a source for this? I think it was because they added support for other VCSs, e.g. SVN. |
|
@jhasse No I have no source of this icon 😞 |
|
@alexmironof i think he means a proof, not a source file |
|
@jhasse They just improved it. No license issue. Source: microsoft/vscode#18675 (comment) |
|
|
So, we need a new name? |
Or Conservancy's written permission. |
|
@jhasse @geek1011 @kolaente Just to clarify, I'm not saying we should change the name. I'm just saying that we should not put the git-logo in our logo, since that would just put us more in violation with their trademark. And the "punchline" |
|
Like for many things, the name is an important aspect of an application. A name definitely can influence its development and future, in some ways, practical or more subtle. "Gitea" is a nice name, still it seems to me it does not reflect the broader and deeper aspect of what it offers. In my humble opinion, "Gitea" is cute and entertains of course an echo of culinary culture, perhaps also hinting to its possible social nature, but it does not fully convey its potential. I am afraid an application of a much broader nature and so promising like this is would be negatively affected by a wrong name. Unfortunately, to some cultures, even the name gogs might have been not a good choice. This project would deserver a name deeply connected with its nature, with a short and nice sound (although two syllables do help form a rhythm), and it should have a unique feeling, charged with newness and enthusiasm , like its vision and its community. Please consider changing the name of gitea. This is the right time, the beginning of a new phase, when the application is allowed to unfold more of its potential. Or, at least allow for more choices to come in, so that a freer deliberation could be made by the maintainers. In any case, thank you so much for this wonderful app. It is truly a first-class app. |
|
Another way would be to just take a branch of tea leafs, but I have no idea how to make that into a nice flat icon ;D |
|
@priyadarshan even now, changing the name will require a lot of work, since that would mean a lot of code changes, a new domain, moving this repo, and so on. |
|
A name is such a vital aspect to an application, that perhaps should be seen as a long term investment, worth the extra work. Of course, the more the wait, the more work it would require. Still, it should not be taken lightly, or hurriedly. As per the domain name change, I pledge to donate $100 to support an eventual domain change, just let me know, in due time, where to donate. I am just a very new, grateful user of gitea. I will be happy with whatever decision the maintainers will support. |
|
I forgot the hardest part: Coming up with a good name. Anyone got any suggestions? |
|
Thank you for the chance. A possibility: As far as I know, it does not seem to be used by a commercial company. Edit: Other possibilities:
GitGo being my favourite. |
|
FWIW: I like the current name of the project.
|
|
I propose to write an official inquiry to trademark@sfconservancy.org @priyadarshan Git in reverse?? Poor concept. |
|
Sorry you did not like the first attempt. What do you think about the others? It seems to me my initial comment is still pertinent. Perhaps others would like to put more ideas on the table. Edit: After searching, it seems the name |
|
Ya, @whilei designs are really badass! |
|
I don't mean to butt-in or cause confusion, but thought I would add a separate poll in case it may be helpful. My designs were posted 4 and 5 days (respectively) after the initial logo proposals.
|
|
@whilei but still your designs got less votes than @qdbdbp so it was decided to use it and just modify not to have copyright issues with git logo. |
|
In my opinion, I lost the original idea of the logo that I designed. |
|
@qdbdbp @whilei design is nice but somehow I don't like shades in background |
|
Which is the new logo? When we will have a decision? I think posting more logos will not make it easier to determine which logo is "the best". |
|
see #2194 |
|
@lunny I think @whilei logos looks more modern and more professionally designed than @qdbdbp and why community doesnt choose them? The answer is simple - 2 days delay. People opened this issue and choosed from two logos first, voted and then never opened this issue again. I think good idea to start voting from scratch and post all logos at once so everybody have some more options to choose from |
|
3 issues with 6 logos, nice 🤣 Why not to gather them all in one place? And this is proof that in #1516 people just vote for 2 well known logos. Also @qdbdbp mentioned @whilei logo is more modern and interesting. |
|
Also if you subtract downvotes from upvotes - the winner is @kolaente |
|
At some point you'll have to settle on a logo.
Yes, because those were the two most popular suggestions at the time.
Voting is over, the current state isn't representative anymore (for example people who dislike the logo on try.gitea.io might come here and downvote it). |
The state of downvotes was correct at the time when pull request arrived, it doesn't changed so much through time.
If you think rationally not only community votes makes good choice |
|
Also only clear thinking mades my decision to move from gogs to gitea, because it seems unmaintained, but community choose gogs(it has about 20k stars) |
I didn't know that. I guess if down-votes were to be substracted from the voting, that should have been made clear in the beginning. Without explicit mentioning I wouldn't expect it.
Yes, so?
Gogs was around a lot longer that's why it has more stars. |
|
GOGS is a older project - compared to him, the new project is stupidity. |
It has more start because of nice logo 😉 |
No, it didn't even have the current logo from the beginning. |
|
Yes, previous logo seems more popular 😄 |
|
Why do you think that? I don't see any decline of the gradient since July. |
|
From start up it has a huge gain. So I think we should stop flooding about personal decisions. My decision is good looking, professianally designed and modern logo |
|
@alexmironof The decision was made to use the logo with the most votes. If you think it's so bad that there needs to be a new vote, open a new issue with objective arguments against the current logo. If enough people agree with you, a new vote could be proposed, but I don't see it happening. |
|
@lesderid If anythings is bad for brand identity it is only a bad brand identity position. |
|
Isn't it very simple to override the logo in custom/ ? Please focus your effort on getting a new release out instead of logo bikeshedding. |
|
Please suggest some modern logo that you think is correct. If you have a problem with this, maybe it's better to be with Gogs because it has a better logo. I think Gitea is already bright years ahead of Gogs with an "ugly" logo ... |
|
Ive suggested it before |
|
The vote is over and a logo have been taken and integrated. |
and others
@qdbdbp @kolaente Let's vote for Gitea's new Logo. First reply is for @kolaente and the second is for @qdbdbp and other replies before that will be deleted. The vote duration is from now until v1.2 release (about 10 days) I think or we have to put this to v1.3.
The text was updated successfully, but these errors were encountered: