DRAFT - Community meeting 2026-07-15

[CsatariGergely]

Attendance

• @CsatariGergely
• @aravindtga
• @JamesMcDermott
• Anubhav Das
• Oisin Johnston
• @mozesl-nokia
• @liamfallon
• @Catalin-Stratulat-Ericsson
• Timo
• @rendre-greyling
• @Jaisheesh-2006
• @ahmadu2305

• If Ive missed you from here add your GitHub handle to the comments of the meeting notes

Architecture workshop

• We need some days together to come up with an architecture for the next 2-3 years.
• Let's try to do a face to face
• ~6 hours
• How about in Prague on Oct 5?
  • Part of the team will be there for Open Source Summit later the same week
  • Nokia has an office, maybe we can get a room.
• Topics
  • Parallel mutation pipelines
  • CRDs in Porch (should we keep the database for other than the resources?)
  • If you have more topic ideas add them as a comment here or propose them on Slack

GSoC project (Jaisheesh)

• There is a weekly meeting to follow up the GSoC project. If you want to join ping @CsatariGergely
• GitHub project to follow up the progress: https://github.com/orgs/kptdev/projects/5
• We proposed a tutorial about the OpenTelemetry demo to the Open Source Summit EU 2026
  • CFP Notifications: Friday, 24 July

Porch documentation

• Jump directly to the documentation page of Porch from the kpt and the function-catalog documentation (@Catalin-Stratulat-Ericsson )
  • PRs were done by Catalin
• Phase 2 is a full integration of the Porch documentation to the renewed kpt documentation

Sonarcloud / FOSSA

• Need a new sonarcloud project: Move relevant repo to new Sonarcloud project #4528
• https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1/CNCFSD-3528
• 2026-06-03 - 2026-06-10: Waiting for support
• 2026-06-17: We can use SonarCube free tier and Snyk. Porch was added to both. Should we add the rest of the repos?
  • A: Gergely to check if we run FOSSA on Porch
  • We should not block anything based on Snyk things
  • Let's keep running all the things now on Porch and see if we like them
• 2026-07-01
  • A: Gergely to check if we run FOSSA on Porch
  • All automation seems to working right in Porch
  • A: Gergely to propagate the same config to the rest of the repos. Define a composite action and refer to that in other repos.
• 2026-07-08
  • FOSSA badge on Porch Adding FOSSA badge porch#1090 -> merged
  • Config propagation was not done yet

Roadmap

• Let's use the Jun 24th Community Call timeslot
• Roadmap issues are marked in the kpt and Porch repost
• Gergely made an attempt to configure one GitHub Project which has all issues in the org labelled with Roadmap
• This needs a bit more research

CNCF Blogpost about kpt

• 2026-06-03 - 2026-07-01: Waiting for CNCF to publish it

kpt to v1.0.0

• 2026-05-20 - 2026-07-13: tracking under EPIC: Release kpt version 1.0.0 #4491, we can check weekly on status

Mutation pipelines

• For working on the pipeline we should not need Porch
• move the Porch mutation pipelines to kpt
  • Function execution environment
  • Render pipeline execution
  • The Porch multi executor should be moved to kpt
• 2026-04-01: Issue to follow up the whole activity: Rearchitect pipelines #4449. feat: add builtin runtime support #4430 touches a similar area. Let's pull all relevant pipeline related issues under Rearchitect pipelines #4449, @ciaranjohnston will create a discussion about the topic.
• 2026-04-08: No progress
• 2026-04-15: @efiacor did some housekeeping. There is a discussion for this: Pipeline and function execution considerations #4483

• 2026-04-22: Waiting for the v1.0.0 work to be done
• 2026-04-29 - 2025-07-08: still waiting ...

Developer guide

• We should have a developers guide for the KRM functions
• @CsatariGergely to create an issue
• 2026-04-29: we need better support given that people will still need to write their own functions - our support is non-existent. Starlark is very powerful but needs a deep understanding - we need a discussion on the SDK strategy. @efiacor has started looking at a list of issues around this
• 2026-05-06: ties into the SDK discussion - need to look at old PRs in that discussion
• 2026-05-13: @CsatariGergely will check for the old PR
• 2026-05-20 - 2026-07-08: no update

Clean up the kpt repo

• EPIC: Clean up the kpt repo #4552

kpt docs versioning

• Use the same approach as with Porch
• We need a kpt 1.0.0 first
• This should be part of the v1.0.0. epic
• 2026-04-08 - 2025-06-17: No progress

Docs reorg

• Remove the book structure - @CsatariGergely
• 2026-04-08 - 2026-07-08: No progress

.project repo rollout

• Keep Maintainer Data Up to Date - @CsatariGergely
• Link GitHub Handles to LFID (@CsatariGergely to post a slack about how to do this)
• Verify Email Settings
• Review and Merge Your PR

Dosu

• Dosu is disabled in Porch
  • feed the Porch data into the kpt Dosu space - Done
  • We should enable commenting and PR creation for Porch and the rest of kpt repos - @CsatariGergely
  • Gergely discussed with Dosu developers and there was a bug related to kpt what prevented the creation of pr-s. This bug supposed ot be fixed now.
• 2026-07-01
  • Dosu is creating PR-s now
  • Is there a way to ask Dosu to create a pr ? -> Gergely to ask
• 2026-07-08
  • We can ask Dosu in an issue or in the Dosu App to start a pr

Maintainers and pr process

• CODEOWNERS are turned off
• If we keep using the groups we should have the groups in the CODEOWNERS
• We should document the process A: @CsatariGergely to draft a process
• We should have a cleanup process A: @CsatariGergely to draft a process
• We can use this as an example https://docs.porch.nephio.org/docs/12_contributing/code-contribution/#reviews-of-your-pr
• We should allow to have one approval from maintainers and one approval from contributors
• We allow only squash commits
• Let's try the 1 + 1 on Porch for 2 weeks and decide how to move forward
• 2027-07-01
  • Contributors team only has read access to the repos. They need write access for approvals
  • @liamfallon created an approvers team with write access
  • 1 maintainer + 1 approver
  • Let's use rulestes in all the repos with the same rules -> @CsatariGergely
    • If possible use org level rulesets
• 2027-07-08
  • No progress

Disable Copilot for additional commits

• AGENTS.md pr needs reviews in kpt
• Gergely will add AGENTS.md-s to the rest of the repos after this one is merged
• 2025-07-01
  • Implemented on Porch by @efiacor and will be moved to the rest of the repos
  • After the kpt AGENTS.md is merged @CsatariGergely will work on a Porch one
  • Utilize copilot.yaml also in the AGENTS.md
• 2025-07-08
  • No progress

Triaging of issues - in progress, start next week's meeting

• Kill issues obviously non replaceable or Porch related
• Prioritize new issues
• 2025-11-19: PRs were cleared down - the ones left were unknown or should be merged. Still need to triage issues - will do that next week's meeting
• 2026-02-04: Did some triaging - Avoid the use of external diff tools for the kpt pkg diff command #1808 is next to be done
• 2026-02-11: @liamfallon checked all the prs. There are new functions in the catalog, there is one documentation pr in kpt ([WIP] Function SDK guide #3367)
• 2026-02-18: Got to Docs: 1.2 Quickstart: Show kubeconform catching some issues #1855
• 2026-05-06: Got to Design and implementation of "built-in" functions #1905
• 2026-05-13: Next one is kpt fn should show progress when downloading an image #1948 on Page 13
• 2026-05-20: Next one is Parallelize image pulling before running the pipeline #2026 on Page 13
• 2026-05-27: Next one is Create library for common utils in kpt functions catalog #2043 on Page 13
• 2026-06-03: Next one is Feature request: Function that sets setter values #2099 on Page 13
• 2026-07-08: Next one is Move kpt live command logs to stderr #2191 on Page 13