design/tickets
17
5
Fork 1
Code Issues 42 Pull requests Projects Activity

Update fedora-remix-logos with SVGs and better resolution PNGs #37

New issue
Open
opened 2026-03-11 20:43:27 +00:00 by niknikovsky · 11 comments
niknikovsky commented 2026-03-11 20:43:27 +00:00
Member
Copy link

What do you need?

This ticket was originally filed on GitLab by Timothée Ravier

Request type

Graphic Design / Artwork (logo, an icon, an infographic, swag design, etc.)

Problem Statement

Hey folks,
For Bootable Container images, we should recommend people switch out the logos to match Fedora's policy:

It would be good if we could recommend to users to use the fedora-remix-logos package to replace the Fedora one.
Right now this package only includes low quality PNGs. We would need SVG variants of those logos, good quality PNGs, logos for Anaconda, plymouth, etc. Essentially all the images provided for the normal Fedora logos package.
Could the design team help us update this package to make it ready for general use?
Thanks!

Contacts

Not provided

Deadline

Not provided

Who will benefit?

Not provided

Inspiration Examples

No response

Priority / Severity

Low (anything else e.g., trivial, minor improvements)

### What do you need? This ticket was originally filed on [GitLab](https://gitlab.com/fedora/design/team/requests/-/work_items/123) by [Timothée Ravier](https://gitlab.com/Siosm) ### Request type Graphic Design / Artwork (logo, an icon, an infographic, swag design, etc.) ### Problem Statement Hey folks, For Bootable Container images, we should recommend people switch out the logos to match Fedora's policy: - https://fedoraproject.org/wiki/Remix - https://fedoraproject.org/wiki/Legal:Secondary_trademark_usage_guidelines It would be good if we could recommend to users to use the [`fedora-remix-logos`](https://src.fedoraproject.org/rpms/fedora-remix-logos) package to replace the Fedora one. Right now this package only includes low quality PNGs. We would need SVG variants of those logos, good quality PNGs, logos for Anaconda, plymouth, etc. Essentially all the images provided for the normal [Fedora logos package](https://src.fedoraproject.org/rpms/fedora-logos). Could the design team help us update this package to make it ready for general use? Thanks! ### Contacts Not provided ### Deadline Not provided ### Who will benefit? Not provided ### Inspiration Examples _No response_ ### Priority / Severity Low (anything else e.g., trivial, minor improvements)
madelinepeck commented 2026-05-05 19:34:57 +00:00
Owner
Copy link

This is the new fedora remix logo, I think it would be good to transfer over these svgs from Nikita's work on the original ticket just for documentation sake.

This is the new fedora remix logo, I think it would be good to transfer over [these svgs](https://gitlab.com/fedora/design/team/requests/-/work_items/123#note_2937841766) from Nikita's work on the original ticket just for documentation sake.
fedora_remix_logo.svg
8 KiB
fedora_remix_logo.svg
👍 1
ekidney self-assigned this 2026-06-30 09:16:26 +00:00
ekidney commented 2026-07-13 10:47:57 +00:00
Owner
Copy link

Hi @siom! I think I understand your request properly.

I downloaded the fedora-logos package and swapped out any of the fedora logos there with the fedora remix logo. I did not touch the plymouth folder though as I can't figure out how to do it. If you have any insights for the progress and throbber effects that would be great. I tried it out but the results I'm getting look different to the files there.

I have only replaced the images I found and did not touch the text files or any other files out of fear of breaking something but if you need me to do anything else let me know! I also didn't zip back up any tar files I extracted so you can see the replacements.

I've never touched a package before so it's a learning curve 😆 I hope this is a step in the right direction

Hi @siom! I think I understand your request properly. I downloaded the fedora-logos package and swapped out any of the fedora logos there with the fedora remix logo. I did not touch the plymouth folder though as I can't figure out how to do it. If you have any insights for the progress and throbber effects that would be great. I tried it out but the results I'm getting look different to the files there. I have only replaced the images I found and did not touch the text files or any other files out of fear of breaking something but if you need me to do anything else let me know! I also didn't zip back up any tar files I extracted so you can see the replacements. I've never touched a package before so it's a learning curve 😆 I hope this is a step in the right direction
fedora-remix-logos.zip
2.5 MiB
ekidney commented 2026-07-13 13:41:26 +00:00
Owner
Copy link

Apologies, I found some icons I forgot to replace. I have attached the updated zip :)

Apologies, I found some icons I forgot to replace. I have attached the updated zip :)
fedora-remix-logos.zip
2.5 MiB
siosm commented 2026-07-13 15:13:57 +00:00
Copy link

Hey @ekidney, thanks a lot! This looks exactly like what we need from a quick look on my phone. I'll be back in two weeks and I can take a closer look. Otherwise maybe @ngompa can take a look. Thanks again!

Hey @ekidney, thanks a lot! This looks exactly like what we need from a quick look on my phone. I'll be back in two weeks and I can take a closer look. Otherwise maybe @ngompa can take a look. Thanks again!
siosm commented 2026-07-13 15:26:05 +00:00
Copy link

For the packaging, we would like to make https://src.fedoraproject.org/rpms/fedora-remix-logos work as a replacement for the official https://src.fedoraproject.org/rpms/fedora-logos package. We don't need the "classic" variant and sub packages so a lot of the duplication from the fedora-logos package can be dropped. Feel free to give it a try if you want and I'll take a look in a few weeks.

We might want to host those logo sources in a proper repo under the Fedora design org here on the forge. It could look like the Fedora logo one, which is still on pagure (https://pagure.io/fedora-logos) and should be migrated to the new forge, maybe in this org?

For the packaging, we would like to make https://src.fedoraproject.org/rpms/fedora-remix-logos work as a replacement for the official https://src.fedoraproject.org/rpms/fedora-logos package. We don't need the "classic" variant and sub packages so a lot of the duplication from the fedora-logos package can be dropped. Feel free to give it a try if you want and I'll take a look in a few weeks. We might want to host those logo sources in a proper repo under the Fedora design org here on the forge. It could look like the Fedora logo one, which is still on pagure (https://pagure.io/fedora-logos) and should be migrated to the new forge, maybe in this org?
ekidney commented 2026-07-15 08:33:58 +00:00
Owner
Copy link

@siosm wrote in #37 (comment):

For the packaging, we would like to make https://src.fedoraproject.org/rpms/fedora-remix-logos work as a replacement for the official https://src.fedoraproject.org/rpms/fedora-logos package. We don't need the "classic" variant and sub packages so a lot of the duplication from the fedora-logos package can be dropped. Feel free to give it a try if you want and I'll take a look in a few weeks.

Sounds good! I'll be honest I don't know how I would go about knowing what needs to be dropped. Is there a way I can test the package myself and see if everything is ok and what is being used where?

We might want to host those logo sources in a proper repo under the Fedora design org here on the forge. It could look like the Fedora logo one, which is still on pagure (https://pagure.io/fedora-logos) and should be migrated to the new forge, maybe in this org?

There's a ticket #70 from @kevin asking about adopting the fedora-logos to our org here too which I'm in support of. We can have them as their own repos here - or maybe a 'packages' repo under our org and have them both live in there if that works? I'm unfamiliar with the process given it's a package and if it's linked up anywhere. Also would I need to port these over myself or would someone be the one to do it? Any guidance would be appreciated.

@siosm wrote in https://forge.fedoraproject.org/design/tickets/issues/37#issuecomment-1061678: > For the packaging, we would like to make https://src.fedoraproject.org/rpms/fedora-remix-logos work as a replacement for the official https://src.fedoraproject.org/rpms/fedora-logos package. We don't need the "classic" variant and sub packages so a lot of the duplication from the fedora-logos package can be dropped. Feel free to give it a try if you want and I'll take a look in a few weeks. Sounds good! I'll be honest I don't know how I would go about knowing what needs to be dropped. Is there a way I can test the package myself and see if everything is ok and what is being used where? > We might want to host those logo sources in a proper repo under the Fedora design org here on the forge. It could look like the Fedora logo one, which is still on pagure (https://pagure.io/fedora-logos) and should be migrated to the new forge, maybe in this org? There's a ticket #70 from @kevin asking about adopting the fedora-logos to our org here too which I'm in support of. We can have them as their own repos here - or maybe a 'packages' repo under our org and have them both live in there if that works? I'm unfamiliar with the process given it's a package and if it's linked up anywhere. Also would I need to port these over myself or would someone be the one to do it? Any guidance would be appreciated.
siosm commented 2026-07-15 09:22:48 +00:00
Copy link

Kevin can likely do the repo migration work for you. The move will not impact the package itself as its definition (specfile) is in another place. Once I get back I can take a look at the package updates if no one got to it before me.

Kevin can likely do the repo migration work for you. The move will not impact the package itself as its definition (specfile) is in another place. Once I get back I can take a look at the package updates if no one got to it before me.
kevin commented 2026-07-15 22:07:09 +00:00
Copy link

Yeah, I can do the migration if you want, or I can add you as a admin on the pagure side and you can do the migration at your leisure. Just let me know...

and yeah, this would just be the upstream/source of the logos, the fedora package itself would still stay at src.fedoraproject.org/rpms/fedora-logos

Yeah, I can do the migration if you want, or I can add you as a admin on the pagure side and you can do the migration at your leisure. Just let me know... and yeah, this would just be the upstream/source of the logos, the fedora package itself would still stay at src.fedoraproject.org/rpms/fedora-logos
ekidney commented 2026-07-20 08:54:52 +00:00
Owner
Copy link

@kevin wrote in #37 (comment):

Yeah, I can do the migration if you want, or I can add you as a admin on the pagure side and you can do the migration at your leisure. Just let me know...

and yeah, this would just be the upstream/source of the logos, the fedora package itself would still stay at src.fedoraproject.org/rpms/fedora-logos

Yah if you add me as an admin on pagure side I can move over everything! Thanks :)

@kevin wrote in https://forge.fedoraproject.org/design/tickets/issues/37#issuecomment-1062926: > Yeah, I can do the migration if you want, or I can add you as a admin on the pagure side and you can do the migration at your leisure. Just let me know... > > and yeah, this would just be the upstream/source of the logos, the fedora package itself would still stay at src.fedoraproject.org/rpms/fedora-logos Yah if you add me as an admin on pagure side I can move over everything! Thanks :)
kevin commented 2026-07-20 14:36:05 +00:00
Copy link

Done!

Done!
❤️ 1
ekidney commented 2026-07-21 10:41:31 +00:00
Owner
Copy link

Thanks Kevin! I added the fedora-logos and fedora-remix-logos from this ticket here: https://forge.fedoraproject.org/design/packages

Let me know @siosm once you're back if things look okay for this ticket :)

Thanks Kevin! I added the fedora-logos and fedora-remix-logos from this ticket here: https://forge.fedoraproject.org/design/packages Let me know @siosm once you're back if things look okay for this ticket :)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
Acceptance
Fedora Design
 This is a valid ticket that should be addressed and has been accepted by the Fedora Design Team

  
Acceptance
Needs Info
 This ticket needs additional info in order for us to triage it.

  
Acceptance
Wont fix
 Ticke is rejected for various reasons: budget approval needed, mindshare approval needed, duplicate / already completed, already part of a larger-scoped plan, redirected to another team, no resources.

  
Design Docs Revamp
Revamping the Design Docs with new updated info and moving from the wiki to docs site.

  
Engagement
Long-term
 Ticket that might require weeks to months to work on.

  
Engagement
Medium-term
 Ticket that might take days to weeks to engage on.

  
Engagement
Short-term
 Ticket that might require hours to days to work on.

  
F45 Wallpaper
All tickets correlated to F45 wallpaper process

  
F46 Wallpaper
All tickets correlated to the F46 wallpaper process

  
Flock 2026
All tickets correlated to Flock process

  
needs review
Ticket needs to be reviewed and triaged by the Fedora Design Team.

  
Newbie
Needs research
 A ticket that someone new to the team could complete, but will require them to get some help/background.

  
Newbie
Well-documented
 A ticket that someone new to the team could complete and is well-documented.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
 This is for work that is critical and needs to be addressed next sprint. It's often for tickets that are time-sensitive, align to Fedora Strategic Initiatives, or is a leadership request.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Status
Backlog
 Items that have been triaged and that we aren't actively working on.

  
Status
In Progress
 Items being actively worked on.

  
Status
In Review
 Ticket is awaiting review by a team member or the requester.

  
Type
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Type
Request
 A ticket related to an incoming external request (not filed by a designer.)

  
Type
Sub Epic
 A smaller segment of work that falls under a larger epic, helping designers break down complex tasks into more manageable parts.

No labels
Acceptance
Fedora Design
Acceptance
Needs Info
Acceptance
Wont fix
Design Docs Revamp
Engagement
Long-term
Engagement
Medium-term
Engagement
Short-term
F45 Wallpaper
F46 Wallpaper
Flock 2026
needs review
Newbie
Needs research
Newbie
Well-documented
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Status
Backlog
Status
In Progress
Status
In Review
Type
Epic
Type
Request
Type
Sub Epic
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
ekidney
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
design/tickets#37
No description provided.