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

Adopt fedora-logos from pagure.io? #70

New issue
Closed
opened 2026-06-29 16:22:50 +00:00 by kevin · 6 comments
kevin commented 2026-06-29 16:22:50 +00:00
Copy link

What do you need?

We need to move fedora-logos off pagure.io ( https://pagure.io/fedora-logos/ )

This is the upstream repo that has all the fedora-logos in it and is used to build the fedora-logos package.

I think it would perhaps fit under https://forge.fedoraproject.org/design/assets

If you don't think it should be under your org, let me know so I can try and find another place for it.

I'm happy to keep doing packaging work for the package, but would prefer someone who can look after the icons handles the upstream repo.

Request type

Something not covered by the above.

Problem Statement

Our logos don't go into the ether after pagure.io is retired. ;)

Contacts

me

Deadline

before 2026-07-31

Who will benefit?

All users of fedora logos. ;)

Inspiration Examples

No response

Priority / Severity

Medium (This will bring a good increase in performance/productivity/usability)

### What do you need? We need to move fedora-logos off pagure.io ( https://pagure.io/fedora-logos/ ) This is the upstream repo that has all the fedora-logos in it and is used to build the fedora-logos package. I think it would perhaps fit under https://forge.fedoraproject.org/design/assets If you don't think it should be under your org, let me know so I can try and find another place for it. I'm happy to keep doing packaging work for the package, but would prefer someone who can look after the icons handles the upstream repo. ### Request type Something not covered by the above. ### Problem Statement Our logos don't go into the ether after pagure.io is retired. ;) ### Contacts me ### Deadline before 2026-07-31 ### Who will benefit? All users of fedora logos. ;) ### Inspiration Examples _No response_ ### Priority / Severity Medium (This will bring a good increase in performance/productivity/usability)
niknikovsky commented 2026-06-29 17:53:44 +00:00
Member
Copy link

I think most of those might be somewhere under https://forge.fedoraproject.org/design/assets/src/branch/main/branding-and-logos/logos (anaconda for example).

I think most of those might be somewhere under https://forge.fedoraproject.org/design/assets/src/branch/main/branding-and-logos/logos (anaconda for example).
jflory7 added the due date 2026-07-31 2026-06-30 01:04:26 +00:00
jflory7 added this to the (deleted) project 2026-06-30 01:04:36 +00:00
ekidney commented 2026-06-30 09:11:48 +00:00
Owner
Copy link

Hi @kevin - thanks for logging this!

I think having it as a separate repo in the Fedora Design Team space would work better since it's a package 🤔 I would be worried I would mess something up if it was within the assets repo 😆 we just use that repo for storage.

Would this be something I would need to port over myself, or would you be the one to do it? I'm unfamiliar with the process given it's a package.

Hi @kevin - thanks for logging this! I think having it as a separate repo in the Fedora Design Team space would work better since it's a package 🤔 I would be worried I would mess something up if it was within the assets repo 😆 we just use that repo for storage. Would this be something I would need to port over myself, or would you be the one to do it? I'm unfamiliar with the process given it's a package.
siosm commented 2026-07-15 09:20:21 +00:00
Copy link

+1 for moving the repo here. As it's the source for the package and not the package itself, there is little risk for mistakes as it won't impact Fedora until the package is actually updated.

I've been working on updates for the various logo packages so I'm happy to help on the packaging front as well but it's better if the sources are under the design team umbrella. Thanks!

+1 for moving the repo here. As it's the source for the package and not the package itself, there is little risk for mistakes as it won't impact Fedora until the package is actually updated. I've been working on updates for the various logo packages so I'm happy to help on the packaging front as well but it's better if the sources are under the design team umbrella. Thanks!
siosm commented 2026-07-15 09:20:44 +00:00
Copy link

We should also do the same with the generic and remix logos sources.

We should also do the same with the generic and remix logos sources.
siosm commented 2026-07-15 09:27:59 +00:00
Copy link

The generic logos are at https://pagure.io/generic-logos.

The Fedora remix specfile points at fedorahosted or the wiki page so we can likely create a new repo to put the sources from the work in #37.

The generic logos are at https://pagure.io/generic-logos. The Fedora remix specfile points at fedorahosted or the wiki page so we can likely create a new repo to put the sources from the work in https://forge.fedoraproject.org/design/tickets/issues/37.
ekidney commented 2026-07-21 10:43:24 +00:00
Owner
Copy link

@kevin I brought over the fedora-logos repo and have it stored here: https://forge.fedoraproject.org/design/packages :) I'll go ahead and close this for now but feel free to open if needed. Thanks for your help!

@kevin I brought over the fedora-logos repo and have it stored here: https://forge.fedoraproject.org/design/packages :) I'll go ahead and close this for now but feel free to open if needed. Thanks for your help!
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
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-07-31

Dependencies

No dependencies set.

Reference
design/tickets#70
No description provided.