| TheresNoTime | |
| Jun 1 2023, 5:37 PM |
| F37089717: Wikimedia Foundation QueERG icon white.png | |
| Jun 1 2023, 9:20 PM |
| F4414835: Wikimedia-Phabricator-logo.png | |
| Jun 1 2023, 9:14 PM |
| F37089224: Wikimedia_Foundation_QueERG_icon_white_80px | |
| Jun 1 2023, 5:56 PM |
| F37089231: image.png | |
| Jun 1 2023, 5:56 PM |
| F37089177: image.png | |
| Jun 1 2023, 5:37 PM |
| F37089176: image.png | |
| Jun 1 2023, 5:37 PM |
| F37089183: image.png | |
| Jun 1 2023, 5:37 PM |
The current phabricator logo appears to be https://commons.wikimedia.org/wiki/File:Wikimedia_logo_white.svg (going by Wikimedia-Phabricator-logo.png) — could we please change it to Wikimedia LGBT+ logo - without text.svg or Wikimedia Foundation QueERG icon white.svg for Pride Month (June)?
I believe this is done from within the UI via;
→ User Interface → ui.custom-header
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| phabricator: June 2023 pride month logo variant | operations/puppet | production | +1 -1 |
This would be https://phabricator.wikimedia.org/config/edit/ui.logo/
I don't think we've done this before.
I'm not a fan of temporary logos in general. See also https://meta.wikimedia.org/wiki/Logo#Temporary_logo_variants
I don't believe it's been done previously either — I would normally find myself agreeing with the points raised here, as I'm also not a fan of temporary logos on our public-facing projects.
There are no overwhelming arguments I could make in defence of this request, so will summarize as;
Thank you for the consideration, and I trust the judgement of the Phabricator admins in weighing up this request.
We could do this permanently which would solve any issues with it being a temporary thing. (/s)
The currently deployed configuration uses the image from F4414835. The samples given in the task description are missing a transparent background that would be needed for usage assuming we can figure out how to find consensus for a temporary or permanent logo change. The samples are done correctly; I was confused by the in-page renderer.
F37089717 is in theory the correct size and transparency. It's also coincidentally the variant that I would personally favor for use.
Change 925970 had a related patch set uploaded (by BryanDavis; author: Bryan Davis):
[operations/puppet@production] phabricator: June 2023 pride month logo variant
Change 925970 abandoned by BryanDavis:
[operations/puppet@production] phabricator: June 2023 pride month logo variant
Reason:
life found another way ;)
Recognizing that this kind of thing can be a can of worms on large wikis and is discouraged there, I think Phabricator is a different sort of space and it feels like a positive gesture with support from admins here. I went ahead and overrode the setting in the database, which seems best for a temporary change since it doesn't require a deploy. Lemme know if sizing needs tweaked. Leaving this "In Progress" and assigned to self so I remember to switch back end-of-month.
Thanks <3 Maybe a bit smaller? I feel it's lacking a bit of padding between the logo and end of the page
Edit: Maybe simply I'm not used to it. NBD. If it's not fixable easily.
I'm wondering if this is an example of unintentional logo misuse? The WMF brand guidelines discourage modifying the Foundation logo's black-and-white colors. Perhaps the Brand Studio team could weigh in. I do understand that this is a low-impact display and subtle change.
I'm wondering if this is an example of unintentional logo misuse? The WMF brand guidelines discourage modifying the Foundation logo's black-and-white colors. Perhaps the Brand Studio team could weigh in.
Per File:Wikimedia_Foundation_QueERG_icon.svg this is a logo variant developed by the Foundation and uploaded by a senior WMF employee in the Communications Department. I think we're good.
Not sure how to switch back as it seems I need to upload (?) a "new" file with the previous logo from... somewhere (?)
I uploaded the old logo as the "new" one. Although now the ui.logo setting is set both in the database and in the config file, but I'm not sure how to unset the database value? Otherwise having it set twice is surely going to cause confusion later on.
