Feature Overview

Currently koji-image-builder allows koji to build images without relying on separate infra maintained by the image-builder team.  Brew is still reliant on infrastructure to build its images.  By making koji-image-builder work with brew, we'd get them onto newer technology (image-builder-cli) and wouldn't need to maintain as much infra ourselves.

Background and Strategic Fit

< Any additional, background or high-level context that would describe or frame how this feature fits into the product strategy. >

Goals

< Who benefits from this feature, and how? What is the difference between today's current state and a world with this feature? Provide high-level goal statements, providing user context and expected user outcome(s) for this feature. >

Requirements

<A list of specific needs or objectives that a Feature must deliver to satisfy the Feature. Note: Any requirements that are not flagged as MVP, should be evaluated and considered for another feature. >

Non-Functional Requirements

< Please take a look at this nice guide talking about NFRs: Top 10 Architecture Characteristics/Non-Functional Requirements with Cheatsheet. Non-Functional Requirements (NFR)s should be considered when planning and are considered Acceptance Criteria for this Feature. >

Use Cases (User Experience & Workflow)

< High-level steps, describing the use case(s) as success scenario(s) for this persona, along with any alternate paths. Describe the experience/interaction/steps of this specific persona as a workflow with expected outcomes (acceptance criteria) at each step. What is the end-state and how will they be able to verify a successful (or otherwise) outcome?

< Explicitly list or describe any pre-conditions or prerequisites the user must perform before executing the following use case(s). Which users will use this and when will they use it? What will the user interaction “look” like? >

Customer Considerations

< Enumerate any customer considerations that would add further clarification and context for this feature. Are there assumptions being made regarding prerequisites and dependencies? Are there assumptions about hardware, software or specific skill sets needed to deliver?>

Customer Information/Supportability

< What information do we need to collect to inform further decision making - SRE metrics. Enumerate aspects of customer feedback, information, metrics and other information that is needed for the Data Driven development, including expectations on user observability. >

Documentation Considerations

• <New Content, Updates to existing content, Release Notes, or No Doc Impact>

• <How do we expect customers will use the feature? For what purpose(s)?>

• <What reference material might a customer want/need to complete [action]?>

• <Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available. >