Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

Streamline development for the OLMv1 project by optimizing developer efficiency with regards to dependency management and eliminating duplicated efforts.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

• More streamlined dependency management in the OLMv1 project
• More efficient development and management of the OLMv1 project by reducing duplicated efforts

Background

*The OLM(Operator Lifecycle Manager) v1 project is currently split into two component repositories; namely operator-controller and catalogd. Given the projects are closely related, maintaining separate repositories necessitates duplication of effort in certain circumstances (such as CI environments, code, documentation, etc) which is an inefficiency.

In addition, it makes dependency management a delicate dance since the versions of dependencies in both projects need to be kept in lock step.*

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

• OLMv1 project code is contained in a monorepo
• CI mechanisms continue to function as before and builds are green

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Not applicable as there should be no impact to customers as a result of this work.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

• Any references to catalogd as a separate repository will need to be updated

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>