Problem/Motivation
Pointed out by @xjm in Slack:
"We need to update the styling/logo here for D9"

Proposed resolution
Fix the branding for this.
We can use the new "evergreen" Drupal logo - see #3134326: Adopt the 2020 (evergreen) Drupal logo in Drupal core
Remaining tasks
Decide what we should do.Do it.Reviews/improvements.RTBC.- Commit.
User interface changes
Change the branding on the status report:

API changes
N/A
Data model changes
N/A
Release notes snippet
N/A
| Comment | File | Size | Author |
|---|---|---|---|
| #32 | 3137414.28_32.interdiff.txt | 848 bytes | dww |
| #32 | 3137414-32.patch | 8.09 KB | dww |
Comments
Comment #3
dwwComment #4
shaalI removed the old logo
d8-logo.svgand added the new onedrupal-evergreen-logo.svg.I replaced all instances that the old logo appeared with the new one.
Discussion about Drupal evergreen logo's license can be found here: #3134326: Adopt the 2020 (evergreen) Drupal logo in Drupal core
Screenshot after this patch applied:

Comment #5
xjmComment #6
gábor hojtsyMy understanding is this would need a switch resolution of #3134326: Adopt the 2020 (evergreen) Drupal logo in Drupal core (the legal parts) first?
Comment #7
hestenetWorking on a usage policy for brand elements that can be included in core, so that we can make this change and update the new brand elements. Hope to have that policy ready tomorrow.
See #3134326: Adopt the 2020 (evergreen) Drupal logo in Drupal core
Comment #8
dwwScreenshot from #4 looks great, thanks!
It appears that the legal policy stuff is moving forward nicely, such that this is a legit use of the evergreen logo. Draft policy: https://www.drupal.org/about/media-kit/copyright-and-trademark
Seems like mentioning the Drupal version inside Drupal in the status report is somewhat similar to this quoted use case. IANAL, but it looks like we can proceed here.
One question on implementation details of #4: Do we really want duplicate copies of the evergreen svg in each core (admin) theme? Why not put it in core/misc or something and have all the admin themes re-use the same copy?
Thanks!
-Derek
Comment #9
shaal@dww, re:
I think that would be a question for @lauriii, I just kept the file structure the way it is.
Comment #10
codersukanta commentedTested the patch #4 on theme seven and claro. It looks great.
Comment #11
dwwRe: #9: When I asked in Slack, @xjm pasted these two links:
#3107186: Add a test to ensure that image assets are copied to Stable when a module or misc asset is updated
#3105209: [policy, no patch] as of Stable 9, do not copy image assets unless they have changed.
To which I replied:
Comment #12
gábor hojtsy@gisle in #3134326: Adopt the 2020 (evergreen) Drupal logo in Drupal core suggests to ship the logo in a distinct directory with a license.txt or license.md file that points to the https://www.drupal.org/about/media-kit/copyright-and-trademark URL (possibly not the final URL). I think that would only be practical if the file would indeed only appear once in core for this purpose at least and not in every single theme.
Comment #13
jungleShould the 9.0 logo be used in the 9.0.x branch to celebrate the release of Drupal 9, especially?
Comment #14
gábor hojtsy@jungle: I don' think that would make sense in the context of this issue, the version number is displayed right alongside it. If this image would be used, we would need to change it in each minor branch (there is already 9.1 and 9.0 open).
Comment #15
dww@Gábor Hojtsy: Re: #12 👍
@jungle Re: #13: Agree with Gabor in #14 that we want the "evergreen" version of the logo for this, not a versioned version. ;)
Thanks,
-Derek
Comment #16
shaalThe following changes were made:
system-status-general-info__item-icon--drupalcore/misc/logo/drupal-evergreen-logo.svglicense.txtfile, that should be updated with the right content.@todo: finalize the content of license.txt
Comment #17
jungle#14, #15, thanks for disagreement! :)
Can we remove
evergreenfrom the filename? Change it tocore/misc/logo/drupal-logo.svgorcore/misc/logo/drupal.svg?As a non-native English speaker, It's my first time to know the word
evergreenwhen the new logo released, never know it before. And before checking the dictionary and got the explanation from @Gábor Hojtsy on slack, at first glance, I thought it's the name of the new logo -- a name similar to Druplicon. 🤦I do not think I am the only one got confused :p
Comment #18
shaalIn the official Drupal logos pack file it is called
Evergreen Logo.I'll be happy to change it if a different name would be better.
Comment #19
sja112 commented@jungle agreeing to your point,
It should be changed back to
drupal-logo.svg,drupal.svgor to some other better name.Comment #20
sja112 commentedCan we change the file name to
d9-evergreen-logo.svgordrupal9-logo.svg?Comment #21
dww@sja112: The point of "evergreen" is that it's not version-dependent. So "9" anywhere in the name is definitely not what we want.
Comment #22
sja112 commented@dww, Thanks for the quick response.
Can we remove evergreen from the name of the file? In my view, it should be changed to
drupal-logo.svg.Comment #23
jungleRe #20, well, a good exmple of misunderstanding
evergreen, no offense :)evergreen === long live/forever, see similar replies in #14 and #15.
Both
d9-evergreen-logo.svgordrupal9-logo.svgare inapplicable here, to me.Comment #24
dww@sja112 Re: #22:
Perhaps. Not up to me. I'll defer to @hestenet, @xjm, @Gábor Hojtsy et al on that...
Comment #25
sja112 commentedI am adding a patch here with the name
drupal-logo.svg.Keeping the issue status to needs work till the name is confirmed or new suggestion pops up.
Adding the patch for the testing.
Thanks!
Comment #26
gábor hojtsyDrupal logo is fine. Drupal has the wordmark, the (software) logo and the mascot (Druplicon). So we can just call this the logo :) Looks like otherwise as well.
Comment #27
gábor hojtsyActually we can use sensible text that is not a problem if we don't come around to change it later. :) Also referencing it from COPYRIGHT.txt. Now I am not eligible to RTBC it though.
Comment #28
dwwThe updated LICENSE.txt text is great for now. We can always refine it later.
Very happy to see this in core/misc/logo now as its own thing. New filename is fine, happy to drop "evergreen" since it's obviously leading to confusion.
Tested manually. Looks great.
RTBC. Updating summary to cross off remaining tasks, clarify proposed resolution, and put the final screenshot in the UI changes section.
Thanks everyone!
-Derek
Comment #29
xjmNice, glad to see this sorted!
I find myself counting relative path segments in
url()again... flashbacks to the theme decoupling work we did 4-5 months ago. I confirmed that only Seven and Claro have this branding with the D8 logo to begin with.Comma splice, missing a period, and also wrapping too early ("see" can go on the previous line). So all together:
Additionally, I'd like to have signoff from someone in legal or at the DA before committing this. Calling that a "subsystem" maintainer for lack of a better term. :) I'll ask in a DA channel.
Comment #30
jungleOne more similar to #29. Even without moving
Seeto the previous line,licenseshould be.Comment #31
hestenetConsider it approved from your friendly neighborhood DA representative, as well as per Dries.
Note that in our other issue about drafting this language it was suggested to make the canonical language the text on Drupal.org itself so that additional tweaks can be easily made.
Therefore a suggested license.txt like @jungle'sabove should work.
Alternately, if we prefer to be extra safe, we could include the full text of the Drupal.org copyright and trademark policy for brand materials page, with a note at the top making it clear that the most current and official canonical version resides on D.O
Comment #32
dwwRe: #29 Fixed core/COPYRIGHT.txt per your suggestion. I wonder if we still want 'core' in the paths reference there, since this is core/COPYRIGHT.txt, so if you're reading that file, presumably you're already in the core subdir. But I left it as-is, since it seems fine this way, too.
Re: #30 Good catch. While I was at it, I figured I'd wordsmith that a little myself. "... do not fall under the [GPL]" seemed a bit informal and clumsy of a formulation. I went with:
Hope that's a "friendly amendment" as we say in Robert's Rules of Order. ;)
Re: #31:
- Yay for sign-off. Removing the tag @xjm added for that.
- Re: "if we prefer to be extra safe, we could include the full text of the..." -- that seems extra dangerous, not extra safe. Then we'll have N copies of this text, and lots of friction and trouble to change most of them. Plus stale versions already released that we can never change. A pointer to the One True Copy(tm) seems way safer and easier to maintain going forward. That's definitely the sense I get from reading #3134326: Adopt the 2020 (evergreen) Drupal logo in Drupal core, especially Dries's reply. So yeah, let's definitely not include any more text in core/misc/logo/LICENSE.txt than we have to. ;)
Comment #33
gábor hojtsyThe text is good and resolves @xjm's concerns as well which I agree with. Also @hestenet signed off.
Comment #36
xjmYay! Glad to see us fixing this before RC (and in a way that meets our licensing needs without any real overhead for core). No egg on our face branding it as D8. And in some ways I'm glad we had this bug because this is at least one thing in the UI that's new, even though we weren't ready to turn on new themes etc.
Since this is changes to the internal themes, deleting the old logo is OK.
Committed to 9.1.x and cherry-picked to 9.0.x. Thanks!
Comment #37
dwwExcellent, thanks!
Moving this as a direct child of #3134326: Adopt the 2020 (evergreen) Drupal logo in Drupal core so that issue can more easily track children for specific uses of the new logo...