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

Fedora Design Team Docs: Revamp FAQ section #20

New issue
Closed
opened 2026-02-24 22:31:11 +00:00 by niknikovsky · 4 comments
niknikovsky commented 2026-02-24 22:31:11 +00:00
Member
Copy link

This ticket has been migrated from Gitlab. See: https://gitlab.com/fedora/design/team/requests/-/issues/137

Originally filed by: @ekidney
Part of this project: https://forge.fedoraproject.org/design/tickets/projects/356

As part of &13 we are revamping https://docs.fedoraproject.org/en-US/design/ to include more information and make it look more inviting 😃 taking inspiration from our old Wiki page: https://fedoraproject.org/wiki/Design. We are going to break it down into sections and work on one part at a time.
Tickets for other sections can be found in the Fedora Team Resources epic: &13
For this ticket, we need to have what our FAQ section will say. This just needs to be a text draft for now.
Some points and subheadings to include:

FAQ

  • Usage of AI & photos
  • Where can I find the logo?
  • Why should I use FOSS design software?
  • Can my request be expedited?
  • Can we implement UX work?

We can add to this list as we think of more questions that people usually ask us.

This ticket has been migrated from Gitlab. See: https://gitlab.com/fedora/design/team/requests/-/issues/137 Originally filed by: @ekidney Part of this project: https://forge.fedoraproject.org/design/tickets/projects/356 > As part of &13 we are revamping https://docs.fedoraproject.org/en-US/design/ to include more information and make it look more inviting 😃 taking inspiration from our old Wiki page: https://fedoraproject.org/wiki/Design. We are going to break it down into sections and work on one part at a time. Tickets for other sections can be found in the Fedora Team Resources epic: &13 For this ticket, we need to have what our FAQ section will say. This just needs to be a text draft for now. Some points and subheadings to include: > ## FAQ > - Usage of AI & photos > - Where can I find the logo? > - Why should I use FOSS design software? > - Can my request be expedited? > - Can we implement UX work? > We can add to this list as we think of more questions that people usually ask us.
niknikovsky added this to the (deleted) project 2026-02-24 22:31:11 +00:00
ekidney removed this from the (deleted) project 2026-05-07 10:35:34 +00:00
ekidney self-assigned this 2026-08-04 09:51:16 +00:00
ekidney commented 2026-08-27 15:13:52 +00:00
Owner
Copy link

Here is my current draft! Note that I used Claude Sonnet 4.5 to help me format the info.

Frequently Asked Questions

Can I use AI-generated images or photos in my designs?

AI can be used during the idea generation and concept phase to help explore directions, but should not be used for final designs. Significant use of AI must be disclosed in accordance with the Fedora AI-Assisted Contributions Policy.

The official Fedora logos and brand assets are available in the Branding and Logos folder within the Fedora Design Team Assets repository. There you will find official Fedora branding assets including logos, mascots, and the Fedora brand guidelines. If you need help finding a specific logo, feel free to reach out in the Fedora Design chat or log a ticket on the Fedora Design ticket tracker.

Why should I use FOSS design software?

The Fedora Design Team uses free and open source software to lower the barrier of entry and ensure our work can be edited by anyone. See Tools We Use for more on the software we use and why.

Can I use Adobe Illustrator, Figma, or other proprietary tools?

You are welcome to use whatever tools you are comfortable with, but final deliverable source files must be provided in open formats (primarily SVG) that can be opened and edited in open source software like Inkscape. If you use proprietary tools, be mindful when exporting — embedded assets, certain effects, or non-standard features may not translate properly. If you encounter issues, you will need to work with us to find a solution, but we cannot take responsibility for troubleshooting problems that arise from using proprietary software.

Do I need to know how to use Inkscape or other FOSS tools to contribute?

No. If you are new to open source design tools, there are tutorials and resources available online to help you get started. The team is happy to provide support and answer questions to the best of our ability. Some tasks are straightforward enough that you can learn as you go, and the community is supportive of beginners.

Do I need to attend meetings to be part of the team?

No. Meetings are open to everyone and are a great way to stay connected, but attendance is not required. You can contribute at your own pace through tickets and chat. See Meetings for the schedule if you would like to join.

Can I contribute if I am not a designer?

Yes. While most of our work is design-focused, there are other ways to contribute, such as helping with documentation or providing feedback. If you are interested in contributing but are not sure how, ask in the Fedora Design chat.

Still have questions? Join us in the Fedora Design chat or open a ticket on the Fedora Design ticket tracker. We're here to help you get started.

Here is my current draft! Note that I used Claude Sonnet 4.5 to help me format the info. # Frequently Asked Questions ## Can I use AI-generated images or photos in my designs? AI can be used during the idea generation and concept phase to help explore directions, but should not be used for final designs. Significant use of AI must be disclosed in accordance with the [Fedora AI-Assisted Contributions Policy](https://docs.fedoraproject.org/en-US/council/policy/ai-contribution-policy/). ## Where can I find the Fedora logo? The official Fedora logos and brand assets are available in the [Branding and Logos folder](https://forge.fedoraproject.org/design/assets/src/branch/main/branding-and-logos) within the [Fedora Design Team Assets repository](https://forge.fedoraproject.org/design/assets). There you will find official Fedora branding assets including logos, mascots, and the Fedora brand guidelines. If you need help finding a specific logo, feel free to reach out in the [Fedora Design chat](https://matrix.to/#/#design:fedoraproject.org) or log a ticket on the [Fedora Design ticket tracker](https://forge.fedoraproject.org/design/tickets/issues). ## Why should I use FOSS design software? The Fedora Design Team uses free and open source software to lower the barrier of entry and ensure our work can be edited by anyone. See [Tools We Use](https://docs.fedoraproject.org/en-US/design/tools-we-use/) for more on the software we use and why. ## Can I use Adobe Illustrator, Figma, or other proprietary tools? You are welcome to use whatever tools you are comfortable with, but final deliverable source files must be provided in open formats (primarily SVG) that can be opened and edited in open source software like Inkscape. If you use proprietary tools, be mindful when exporting — embedded assets, certain effects, or non-standard features may not translate properly. If you encounter issues, you will need to work with us to find a solution, but we cannot take responsibility for troubleshooting problems that arise from using proprietary software. ## Do I need to know how to use Inkscape or other FOSS tools to contribute? No. If you are new to open source design tools, there are tutorials and resources available online to help you get started. The team is happy to provide support and answer questions to the best of our ability. Some tasks are straightforward enough that you can learn as you go, and the community is supportive of beginners. ## Do I need to attend meetings to be part of the team? No. Meetings are open to everyone and are a great way to stay connected, but attendance is not required. You can contribute at your own pace through tickets and chat. See [Meetings](https://docs.fedoraproject.org/en-US/design/meetings/) for the schedule if you would like to join. ## Can I contribute if I am not a designer? Yes. While most of our work is design-focused, there are other ways to contribute, such as helping with documentation or providing feedback. If you are interested in contributing but are not sure how, ask in the [Fedora Design chat](https://matrix.to/#/#design:fedoraproject.org). --- **Still have questions?** Join us in the [Fedora Design chat](https://matrix.to/#/#design:fedoraproject.org) or open a ticket on the [Fedora Design ticket tracker](https://forge.fedoraproject.org/design/tickets/issues). We're here to help you get started.
faq.md
3.2 KiB
madelinepeck commented 2026-09-02 17:27:03 +00:00
Owner
Copy link

I feel like this checks off everything! Right now I can't think of anything to change or add. I don't think... its necessary to include information of us as employees of Red Hat as paid members of the Fedora Design Team, but that you can contribute from the community, because I think that'll be explained in the About section. That's the only thing I could think of.

I think the amount of links included and repeated are helpful and the information is laid out in a clear way! Awesome job Emma!

I feel like this checks off everything! Right now I can't think of anything to change or add. I don't think... its necessary to include information of us as employees of Red Hat as paid members of the Fedora Design Team, but that you can contribute from the community, because I think that'll be explained in the About section. That's the only thing I could think of. I think the amount of links included and repeated are helpful and the information is laid out in a clear way! Awesome job Emma!
niknikovsky commented 2026-09-03 05:52:32 +00:00
Author
Member
Copy link

+1 for implementing the current version

+1 for implementing the current version
ekidney commented 2026-09-09 14:40:45 +00:00
Owner
Copy link

Created and pushed PR: design/docs#8

Site should update in awhile :)

Created and pushed PR: https://forge.fedoraproject.org/design/docs/pulls/8 Site should update in awhile :)
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
2026-08-24 to 2026-09-14
Assignees
Clear assignees
No assignees
ekidney
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#20
No description provided.