Story (Required)

As a customer trying to install builds for Red Hat OpenShift I want the operator to use a technology icon in the catalog so that the product can be distinguished from the project

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

The upstream Shipwright operator uses its own icon that is trademarked by the Linux Foundation - see its License. We cannot use it in a Red Hat product legally.

Out of scope

<Defines what is not included in this story>

• Update icon for the operator - will be done in a follow-up story.

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

• Branding & product management draft technology icon
• Technology icon added to our branding catalog - see technology icons portfolio

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

• None

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

• Branding publishes technology icon in icons portfolio
• Technology icon must be provided in one of the following media type formats:
  • SVG
  • PNG

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met