Agenda

Antitrust Policy

• Action Items Review

• Nephio R6

• Planning for H1 2026/Nephio R7

• Quick Demo on EPIC: Allow storage of draft PackageRevision resources when the mutation pipeliine is failing · Issue #1009 · nephio-project/nephio - @Aravindhan Ayyanathan

• AOB

Minutes

From last week

• Add Function Evaluator PIP from @Istvan Kispal @Liam Fallon

• @Fiachra Corcoran and @Laszlo Mozes (Nokia) to coordinate on repository event based sync

  • Fiachra will touch base with @Laszlo Mozes (Nokia) before next week’s meeting

  • @Fiachra Corcoran will present his PR at next weeks meeting

• PIP on the PackageRevision CRD, built on https://github.com/nephio-project/nephio/issues/598

Nephio R6

• Please prioritize review of documentation PRs here: https://github.com/nephio-project/porch/issues?q=state%3Aopen%20label%3Adocumentation

• There are oner or two small PRs that might make it into R6 if they are reviewed in time for the release

Nephio R7

• Board is OK from a Porch point of view

• Need input from other Nephio people on the non-porch items

PR Storage when Pipeline fails

• Remove RenderStatus from PackageRevisionRseources

• Check if Validation failures can be handled like mutation failures (Resources stored and status updated)

• Output in RenderStatus should be the same as “kpt fn render”

• Should the conditions and/or rendering status be stored in the kpt file? In the async solution, this is stored in the kpt file. As well as or instead of RenderStats on PR?

  • We will follow up on a group chat on slack or at a future meeting.

• Also what is the overlap with https://github.com/nephio-project/porch/pull/194

• We need to synchronize the order in which we drop functionality into kpt and porch

Action items