Replace the favicon with the D8 logo

Nope. We should wait for #2057767: [policy, no patch] Revise the Druplicon logo.

There is no reason for us to have a "version" specific logo. This issue starts off on the wrong foot.

This ship has sailed. Though the logo is much nicer;) Let's see there is more traction when that version comes around. Thanks for the idea @jcnventura I think it may be worth branding the versions.

hmm, why 9 and not 8.1, this is a great idea.

Could happen in 8.2.x yes.

Ah yeah this could happen in 8.2 as it shouldn't affect people. Sorry jumped to far on that one. Thanks @Jeff Burnz and @catch

I understand the reasons behind the idea, but I agree with #2 most. The logo is the logo for now.

What about the idea of incorporating the D8 logo into the default content feature instead? For example, display it on the default article.

#8 #2057767: [policy, no patch] Revise the Druplicon logo has been stuck for a year :/

In its current form, this is a duplicate of #2057767: [policy, no patch] Revise the Druplicon logo

Yup, I'd be happy to won't fix this.

It is not a duplicate, the other issue is a no patch policy adjustment, we'd have to then write patches to use it.

The drupalicon is horrible, even updated, just too old school and needs to be replaced with a more modern and relevant design.

I am wondering how switching to a version-specific favicon would solve the problem of an outdated project logo.

D8/Bartik ship with the Druplicon as the site logo. That would need changing too.

For the sake of argument, d.o. does not have the Druplicon in its design anymore except the favicon. That seems to be why the discussion on #2057767: [policy, no patch] Revise the Druplicon logo tapered. It is interesting that going to drupal.org today I see the wordmark, a modified D8 logo, and the old Druplicon in the favicon. It's a bit confusing. But what we need more than this is the new project logo for everywhere it is used.

(edited)

I think you are confused, we're saying switching the favicon to the new D8 logo would solve the problem of an outdated favicon. Thats what we're saying here.

Drupal.org has nothing to do with this, it's long been established that D.O has its own marketing objectives quite apart from Drupal core the software and is a totally different discussion.

Bartik logo, again different issue, feel free to open one, sounds like a good idea but a seperate discussion.

@cilefen Why do you keep bringing up changing logo, sticking logo in default content, d.o usage, Bartik etc - all that is out of scope, this is a simple change, so why the big effort to derail a focused discussion? What are you hoping to achieve here?

• Why do you keep bringing up changing logo: I wrote that because I don't see how it would make sense to change the favicon, which is a logo no matter what it's called, but not to swap it everywhere in the product.
• sticking logo in default content: I offered this as an alternative idea to fans. The issue summary reads: We also have a shiny Drupal 8 logo, that is not included anywhere in D8 itself.
• why the big effort to derail a focused discussion? What are you hoping to achieve here? This is a discussion, right? I don't think to call it a derailing is fair, considering the comment #2. I don't agree with this issue and I am not the only one. I really don't agree, thus the big effort. I offered alternatives and aired some of the reasons why I don't agree.

But I will take the advice and move on to better issues. There is nothing more to add.

I think we can close this as outdated, as we will move forward to replace the logo with the new Drupal logo in #3134326: Adopt the 2020 (evergreen) Drupal logo in Drupal core and #3178135: Change favicon to new Drupal logo
Thanks @cilefen for pointing out :)