design/tickets
18
5
Fork 1
Code Issues 39 Pull requests Projects Activity

Badge for serving on the EPEL Steering Committee #60

New issue
Open
opened 2026-04-29 15:54:31 +00:00 by rcallicotte · 3 comments
rcallicotte commented 2026-04-29 15:54:31 +00:00
Copy link

What do you need?

This is a request for a new badge for people that serve as members of the EPEL Steering Committee.

Badge description:

  • "You were a member of the EPEL Steering Committee"

Request type

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

Problem Statement

There has never been a badge awarded to members of the EPEL Steering Committee. All elected members should receive a badge for serving.

Contacts

robby@redhat.com
carl@redhat.com
dherrera@redhat.com
Team: EPEL

Deadline

July 2026.

Who will benefit?

This will benefit all current and past members of the EPEL Steering Committee.

Inspiration Examples

This issue was previously filed in pagure, see issue-829.

Priority / Severity

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

### What do you need? This is a request for a new badge for people that serve as members of the EPEL Steering Committee. Badge description: - "You were a member of the EPEL Steering Committee" ### Request type Graphic Design / Artwork (logo, an icon, an infographic, swag design, etc.) ### Problem Statement There has never been a badge awarded to members of the EPEL Steering Committee. All elected members should receive a badge for serving. ### Contacts robby@redhat.com carl@redhat.com dherrera@redhat.com Team: EPEL ### Deadline July 2026. ### Who will benefit? This will benefit all current and past members of the EPEL Steering Committee. ### Inspiration Examples This issue was previously filed in pagure, see [issue-829](https://pagure.io/fedora-badges/issue/829). ### Priority / Severity Low (anything else e.g., trivial, minor improvements)
34277aaf9bbba66d116acdc0f5d8d4edcd1dbaaba0a71f72b4b9da91af3c2c79-antmember3.png
48 KiB
b01c3b880334c85db6a41745878926128f108048b26843ad209261bbc50b9678-epel-council-ants.png
51 KiB
e5f63e3989c1e5ad6d519ae62b25f8fd7a06693c98e1bd9400f76e6e657ee82e-epel-council-badger.png
45 KiB
13f42cd2686de18b846361ec79021e9eca05ba0b722f081d4f19976ff30e8e28-antmember4.png
50 KiB
34277aaf9bbba66d116acdc0f5d8d4edcd1dbaaba0a71f72b4b9da91af3c2c79-antmember3.png b01c3b880334c85db6a41745878926128f108048b26843ad209261bbc50b9678-epel-council-ants.png e5f63e3989c1e5ad6d519ae62b25f8fd7a06693c98e1bd9400f76e6e657ee82e-epel-council-badger.png 13f42cd2686de18b846361ec79021e9eca05ba0b722f081d4f19976ff30e8e28-antmember4.png
👀 2
madelinepeck commented 2026-05-05 19:13:55 +00:00
Owner
Copy link

Just leaving this bit of knowledge from @ekidney in case anyone works on this from the community!

"In Pagure if an asset is showing a 404 you just need to remove the '/files' from the url and then it should download 🙂

eg: https://pagure.io/Fedora-Badges/issue/raw/files/eaf64b272fb6dcc88910a35b177c585258c746d1e88fef75aa23cc328329313a-security2.svg shows a 404 but https://pagure.io/Fedora-Badges/issue/raw/eaf64b272fb6dcc88910a35b177c585258c746d1e88fef75aa23cc328329313a-security2.svg downloads the SVG"

Just leaving this bit of knowledge from @ekidney in case anyone works on this from the community! "In Pagure if an asset is showing a 404 you just need to remove the '/files' from the url and then it should download :slightly_smiling_face: eg: https://pagure.io/Fedora-Badges/issue/raw/files/eaf64b272fb6dcc88910a35b177c585258c746d1e88fef75aa23cc328329313a-security2.svg shows a 404 but https://pagure.io/Fedora-Badges/issue/raw/eaf64b272fb6dcc88910a35b177c585258c746d1e88fef75aa23cc328329313a-security2.svg downloads the SVG"
rcallicotte commented 2026-05-18 15:06:33 +00:00
Author
Copy link

Hello! I'm just following up on this issue. Is there any more information needed from my end?

Hello! I'm just following up on this issue. Is there any more information needed from my end?
ekidney commented 2026-05-25 08:33:04 +00:00
Owner
Copy link

@rcallicotte wrote in #60 (comment):

Hello! I'm just following up on this issue. Is there any more information needed from my end?

Hi Robby! I don't think we need more info for now - this is just on our backlog at the moment. Hoping to plan it into one of our sprints soon :)

@rcallicotte wrote in https://forge.fedoraproject.org/design/tickets/issues/60#issuecomment-713071: > Hello! I'm just following up on this issue. Is there any more information needed from my end? Hi Robby! I don't think we need more info for now - this is just on our backlog at the moment. Hoping to plan it into one of our sprints soon :)
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

  
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
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
3 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#60
No description provided.