#326 Discord using unapproved logo
Closed: resolved 2 years ago by bcotton. Opened 3 years ago by bcotton.

Noticed while looking at #325 that the Discord channel uses an unapproved Fedora logo. Opening a ticket here for visibility.


Emailed the listed contact.

Metadata Update from @bcotton:
- Issue priority set to: Waiting on External (was: Next Meeting)

3 years ago

Fedora community Discord server is using our own logo designed based on the proposals by a member of our community as part of larger collaboration with other Linux communities on Discord:

2020-09-14_16-09-21.png

(This isn't a complete exhaustive "list" of collaborators.)

Should the Fedora Council insist on changing it back to the old logo, we'd stick out like a sore thumb.

@rhea Hi! Do you know if there other places where the Fedora logo could appear prominently in the Discord? If not the server icon, are there other places the Fedora trademark could appear visibly, like in a pinned message? I'm a Discord noob, not sure if there is something like that or not.

@jflory7 o/

We actually LOST a Banner art like today or yesterday due to the changes in their partner&verified programe (it's now a benefit only for partners) so I was thinking how to remedy that hit as well. I'll send you my ideas on IRC

Here is the solution for our missing banner art - the idea is to place it at the top of our #info channel like this: https://cloud.rhea.dev/s/CiqMC3jj9HTsKit

This #info channel further contains information on where to find docs, downloads and other Fedora info; and references on how to contribute. Oh and a little bit of a CoC "don't do these things."

Then on the topic of the server logo/icon, we'd very much like to keep it as-is because it's matching other distributions and we have other art around it that we occasionally use, for example for Pride day/month we use this one. But if it's a problem we can try to come up with a different solution.

Repeating myself from the IRC conversation for the record:

The solution proposed in the previous comment works for the info channel as far as I'm concerned.

I'm still mixed on the server icon. Right now it's very much not our logo, so I guess we don't have much to say about it. However, once our new logo is in place, that becomes very close and thus we might have some concern about it. I understand the "this is the style" argument, but I'm not sure what a good solution is.

For the time being, I'll check with the lawyers to see if the Council can authorize an alternate version that fits the visual style common on Discord, or if that would be considered a separate mark.

Excuse my ignorance please but was a final version for the new logo chosen and approved and is this happening? When? There is an option to creating a new one that would fit it (i.e. a square of Fedora blue with the new logo in alpha in the middle)

(Most people I know dislike the asymmetric version from the proposal, I was hoping it will end up being even, hence the one we got is even.)

Excuse my ignorance please but was a final version for the new logo chosen and approved and is this happening? When?

A design was approved by Council and it is currently being worked on with Red Hat Legal. The timeline is...uncertain.

Hi @rhea -Please provide image specifications and the currently used files for all of the different logos that are being used on Discord. Please attach the files here instead of links. From there the design team can review and make any adjustments needed. Thanks!

fedora-splash-cut.png

Background needs to be #2f3136 and therefor the little shadow around the table would need to be a bit darker as well.

(I don't have svg handily available but it does exist, somewhere...)

Hi folks. Since we are actively in the process of updating the Fedora logo across many places, is there a follow-up to this ticket? Do we need to engage the Fedora Design team in a new ticket? How can we best move this forward?

No this should have been closed half a year ago :p

Metadata Update from @bcotton:
- Issue close_status updated to: resolved
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Attachments 2
Attached 3 years ago View Comment
Attached 3 years ago View Comment