design/tickets

Fork 1

Move over Gitlab assets and reorganise folders #6

New issue

Closed

opened 2026-02-23 14:24:51 +00:00 by ekidney · 1 comment

ekidney commented

2026-02-23 14:24:51 +00:00

Owner

Design Request

What do you need?

We have moved over our event-kit, backgrounds, docs, and tickets repo. We now need to bring over everything else, which is mainly logos, event assets (different from the evergreen event-kit, these are event specific), and ad-hoc stuff like social media graphics. I would like to take this as an opportunity to reorganise our file structure, as it can be difficult to navigate at the moment.

I propose one repository called design-assets where we would store the majority of our stuff, so we dont have to click around different repos. This would involved folding in the event-kit too.

After looking at what we have left to bring over, my suggested file structure is:


├── fedora-brand
│   ├── brand-book
│   ├── logos
│   │   ├── 00-official-logo
│   │   ├── applications
│   │   ├── editions
│   │   ├── events
│   │   ├── fedora-teams
│   │   └── platforms
│   └── mascots
│       ├── badger-assets
│       ├── beefy-assets
│       ├── colur-assets
│       └── panda-assets
├── events
│   ├── event-kit
│   ├── appreciation-week
│   │   └── 2023
│   ├── flock
│   │   ├── 2023
│   │   ├── 2024
│   │   ├── 2025
│   │   └── 2026
│   ├── release-parties
│   │   ├── F39
│   │   ├── F40
│   │   └── F43
│   ├── fosdem
│   ├── hatch
│   ├── mentor-summit
│   ├── nest
│   └── week-of-diversity
├── marketing-social
│   └── templates
├── LICENSE
└── README.md

Problem Statement

We need to bring over the remaining assets from GitLab to as part of our migration.

Contacts

Me or the Design team :)

Deadline

ASAP

Who will benefit?

The Design team and those who need to find an asset

Priority/Severity

High (This will bring a huge increase in performance/productivity/usability cover)

# Design Request ## What do you need? We have moved over our event-kit, backgrounds, docs, and tickets repo. We now need to bring over everything else, which is mainly logos, event assets (different from the evergreen event-kit, these are event specific), and ad-hoc stuff like social media graphics. I would like to take this as an opportunity to reorganise our file structure, as it can be difficult to navigate at the moment. I propose one repository called `design-assets` where we would store the majority of our stuff, so we dont have to click around different repos. This would involved folding in the event-kit too. After looking at what we have left to bring over, my suggested file structure is: ``` ├── fedora-brand │ ├── brand-book │ ├── logos │ │ ├── 00-official-logo │ │ ├── applications │ │ ├── editions │ │ ├── events │ │ ├── fedora-teams │ │ └── platforms │ └── mascots │ ├── badger-assets │ ├── beefy-assets │ ├── colur-assets │ └── panda-assets ├── events │ ├── event-kit │ ├── appreciation-week │ │ └── 2023 │ ├── flock │ │ ├── 2023 │ │ ├── 2024 │ │ ├── 2025 │ │ └── 2026 │ ├── release-parties │ │ ├── F39 │ │ ├── F40 │ │ └── F43 │ ├── fosdem │ ├── hatch │ ├── mentor-summit │ ├── nest │ └── week-of-diversity ├── marketing-social │ └── templates ├── LICENSE └── README.md ``` ## Problem Statement  We need to bring over the remaining assets from GitLab to as part of our migration. ## Contacts  Me or the Design team :) ## Deadline   ASAP ## Who will benefit?  The Design team and those who need to find an asset ## Priority/Severity  - [ ] High (This will bring a huge increase in performance/productivity/usability cover)

ekidney added the

labels

2026-02-23 14:24:51 +00:00

ekidney self-assigned this

2026-02-23 14:24:51 +00:00

ekidney added this to the Sprint 2026-02-23 to 2026-03-08 project

2026-02-23 16:48:46 +00:00

ekidney commented

2026-03-05 17:22:07 +00:00

Author

Owner

All assets from Gitlab have been moved over to Forgejo here:

https://forge.fedoraproject.org/design/design-assets

as part of PR: design/design-assets#1

As part of the PR:

Assets from the GitLab repositories were imported
Additional design files attached to GitLab tickets (but not committed to the repositories) were gathered and included where possible
A new directory structure was introduced to organize assets by purpose:
- branding-and-logos/
- event-kit/
- misc/
- past-events/

Documentation was also added to improve discoverability:

A top-level README describing the purpose of the repository
README files in each main directory explaining what assets belong there
Links to the Fedora Brand Guidelines where relevant

This should represent the most complete collection of Fedora design assets :)

To keep the repo up-to-date, we will need to document a process of how to upload completed assets once a ticket is complete, but that can be part of #16 - Revamp How We Work / Processes section.

All assets from Gitlab have been moved over to Forgejo here: https://forge.fedoraproject.org/design/design-assets as part of PR: https://forge.fedoraproject.org/design/design-assets/pulls/1 As part of the PR: - Assets from the GitLab repositories were imported - Additional design files attached to GitLab tickets (but not committed to the repositories) were gathered and included where possible - A new directory structure was introduced to organize assets by purpose: - `branding-and-logos/` - `event-kit/` - `misc/` - `past-events/` Documentation was also added to improve discoverability: - A top-level README describing the purpose of the repository - README files in each main directory explaining what assets belong there - Links to the Fedora Brand Guidelines where relevant This should represent the most complete collection of Fedora design assets :) To keep the repo up-to-date, we will need to document a process of how to upload completed assets once a ticket is complete, but that can be part of https://forge.fedoraproject.org/design/tickets/issues/16 - Revamp How We Work / Processes section.

ekidney closed this issue

2026-03-05 17:22:07 +00:00

ekidney referenced this issue

2026-03-05 17:32:17 +00:00

Write a better README for the Event Kit repo, its contents, and important usage notes #31

No milestone

No project

No assignees

1 participant

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#6

No description provided.

Rows
Columns