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

logo request: Artemis #71

New issue
Open
opened 2026-06-30 10:20:22 +00:00 by ivasilev · 0 comments
ivasilev commented 2026-06-30 10:20:22 +00:00
Copy link

What do you need?

The machine-provisioning heart of Testing Farm is missing a proper logo.

Request type

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

Problem Statement

Artemis is a machine provisioning service used internally in Testing Farm. It can provision machines from various clouds (aws, openstack, azure, ibmcloud, gcp, beaker) and is easily extensible via drivers (basically each cloud support is implemented as a separate driver).

Contacts

@ivasilev; Testing Farm team.

Deadline

No set deadline, Artemis has never had a truly recognizable (meaning giving the "oh, it is Artemis!" impression without "Artemis" written right next to it) logo.

Who will benefit?

Artemis is the functional heart of Testing Farm (no provisioner -> no testing as a service offering). It is our pride and joy and the light that attracts engineering talents, having a real logo is the first step to give Artemis the recognition it truly deserves.

Inspiration Examples

A thought I had on the train back home from DevConf - given that the Artemis provisioner is highly extensible via separate drivers and Artemis is goddess of hunt, maybe Artemis profile with a quiver of arrows with the arrows feathering resembling individual clouds' logos could capture the gist of it..

But that is just a thought, we completely trust the process! :)

Priority / Severity

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

### What do you need? The machine-provisioning heart of Testing Farm is missing a proper logo. ### Request type Graphic Design / Artwork (logo, an icon, an infographic, swag design, etc.) ### Problem Statement [Artemis](https://gitlab.com/testing-farm/artemis) is a machine provisioning service used internally in [Testing Farm](https://testing-farm.io/). It can provision machines from various clouds (aws, openstack, azure, ibmcloud, gcp, beaker) and is easily extensible via drivers (basically each cloud support is implemented as [a separate driver](https://gitlab.com/testing-farm/artemis/-/tree/main/server/src/tft/artemis/drivers)). ### Contacts @ivasilev; Testing Farm team. ### Deadline No set deadline, Artemis has never had a truly recognizable (meaning giving the "oh, it is Artemis!" impression without "Artemis" written right next to it) logo. ### Who will benefit? Artemis is the functional heart of Testing Farm (no provisioner -> no testing as a service offering). It is our pride and joy and the light that attracts engineering talents, having a real logo is the first step to give Artemis the recognition it truly deserves. ### Inspiration Examples A thought I had on the train back home from DevConf - given that the Artemis provisioner is highly extensible via separate drivers and Artemis is goddess of hunt, maybe Artemis profile with a quiver of arrows with the arrows feathering resembling individual clouds' logos could capture the gist of it.. But that is just a thought, we completely trust the process! :) ### Priority / Severity Medium (This will bring a good increase in performance/productivity/usability)
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
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#71
No description provided.