Value Statement

In upstream, OCM has an integration with Kueue/MultiKueue. As MultiKueue gains more users in the community, an increasing number of user cases arise, and with them, more problems that need to be solved. Today we manually discover the new issues, trace it, log an Epic to plan it https://docs.google.com/document/d/1F-8EhOPJQcJAucLOHWyzejLbfyKLd_Y6qNg2eX2TsWo/edit?tab=t.0#heading=h.nmkmu1f4o4mm .

We need a way to increase our productivity upstream and enhance our influence in MultiKueue. The answer may be to leverage AI. This includes tracking community issues, proposing solutions, submitting code, more efficient workflow and so on. We can use AI to make these things happen faster.

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.