Completing a ticket

Design requests come in as tickets on the Fedora Design Team’s ticket queue. Anyone in the community can pick up a ticket and contribute. If you are new to the team, look for tickets labeled Newbie: Well-documented or Newbie: Needs research. These are specifically suited for new contributors. See Agile Workflow for a full breakdown of what each label means.

Claiming a Ticket

Before starting work, ask to be assigned to the ticket so that other contributors know it is being worked on and effort is not duplicated. If you are unable to finish a ticket you have claimed, unassign yourself and leave a comment explaining where you left off so someone else can pick it up.

Workflow

Here is the general workflow we typically follow:

  1. Read through the ticket carefully and consider the timeline and requirements. Do you have the capacity to contribute given the deadline? Do you have enough technical skill? If unsure, reach out! We would be happy to advise.

  2. If the ticket is to produce a design like a logo or a poster, sketch out multiple ideas in different directions. Pencil or pen sketches are perfect for this stage. The goal is to explore a range of approaches quickly, not to produce polished work. If anything in the request is unclear, ask clarifying questions on the ticket. Then share your first round of ideas for feedback.

  3. Once the requester provides feedback on which idea they want to pursue, develop that concept further. This typically involves bringing the sketch into Inkscape and vectorising it.

    You can find Inkscape tutorials on our resources page. [Link to be added once resource page is made]

  4. Take the elements of design (contrast, balance, hierarchy, alignment, repetition, proximity, color, space, typography) into consideration at each stage. Share progress and don’t be afraid to ask for feedback.

  5. Upload final files to the ticket in the format required. If unsure, ask the requester or a member of the team and they can advise you. Make sure the source files (e.g., SVGs) are included so future contributors can edit the work.

Communication

Keep the ticket updated as you work. Post progress, ask questions, and respond to feedback on the ticket itself so there is a clear record of the conversation. If you are waiting on feedback from the requester, it is okay to follow up after a reasonable amount of time. However, be mindful that feedback can take some time and isn’t always immediate.

When posting updates, be sure to included some information on what you did and why you did it. It makes giving feedback easier and helps others understand your thinking.

Good communication keeps the project moving and helps the rest of the team know where things stand.

Want to help? Learn how to contribute to Fedora Docs ›