Skip to content

.project Integration List #401

New issue
New issue
Closed
Task
Closed
.project Integration List#401
Task
Assignees
RobertKieltyjeefymfahlandtriaankleinhansahmadqasembader
Labels
area/dot-projectutilities/dot-project scaffolding and bootstrap toolingkind/choreChore or maintenanceneeds-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)priority/mediumMedium prioritystatus/in-progressCurrently being worked ontriage/validIssue or PR is valid with enough information to be actionable

Description

@ahmadqasembader
ahmadqasembader
opened on May 10, 2026

Tracking the rollout of .project repos across CNCF sandbox projects.

Priority: We are provisioning incubation-bound projects first:
https://github.com/cncf/toc/issues?q=is%3Aissue%20state%3Aopen%20label%3Alevel%2Fincubation

This issue will be updated as the integration progresses.

cc @riaankleinhans

Progress (166 total): 156 completed · 10 still in progress.

Checklist

Completed

Activity

  1. ahmadqasembader
    assigned
    ahmadqasembader
    ,
    jeefy
    ,
    mfahlandt
    and
    riaankleinhans
    on May 10, 2026
  2. ahmadqasembader
    added
    area/dot-projectutilities/dot-project scaffolding and bootstrap tooling
    on May 10, 2026
  3. ahmadqasembader
    added the
    Task
    issue type on May 10, 2026
  4. github-actions
    added
    needs-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)
    needs-kindIndicates an issue or PR that is missing an issue type or kind (a kind/foo label)
    needs-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)
    needs-priorityIndicates an issue or PR missing a priority label
    needs-statusIndicates an issue or PR missing a status label
    on May 10, 2026

  5. ahmadqasembader commented on May 10, 2026

    @ahmadqasembader
    ahmadqasembader
    on May 10, 2026
    ContributorAuthor

    @jeefy @riaankleinhans

    I found another org for Meshery — Meshery Extension. Should that count as a separate .project integration?
    My understanding it should not. Since .project tracks the project, not the GitHub Org

  6. riaankleinhans commented on May 11, 2026

    @riaankleinhans
    riaankleinhans
    on May 11, 2026
    Contributor

    @jeefy @riaankleinhans

    I found another org for Meshery — Meshery Extension. Should that count as a separate .project integration? My understanding it should not. Since .project tracks the project, not the GitHub Org

    @ahmadqasembader this seem to be just a another org of the same project. LF Project Control Center only show the main project. A good record of project names in PCC is the CNCF calendar.
    .project should be a 1:1 match for projects on the calendar.

  7. RobertKielty
    self-assigned this
    on May 11, 2026

  8. ahmadqasembader commented on May 12, 2026

    @ahmadqasembader
    ahmadqasembader
    on May 12, 2026
    ContributorAuthor

    @riaankleinhans

    All projects from incubation list has been onboarded with .project except for:

    • Tektoncd since I cannot find it on the CNCF Enterprise account.
    • Podman project, it seems that the core project lives in Containers Org so it's not part of CNCF Enterprise.
      However, I found Podman Desktop Org and Podman IO in the Enterprise account which the latter seems to be an experimental Org?! Not sure.

    Let me know if there's another list to priotrize for onboarding.

  9. 298 remaining items

  10. github-actions
    added
    needs-kindIndicates an issue or PR that is missing an issue type or kind (a kind/foo label)
    needs-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)
    needs-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)
    needs-priorityIndicates an issue or PR missing a priority label
    and removed
    needs-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)
    needs-kindIndicates an issue or PR that is missing an issue type or kind (a kind/foo label)
    needs-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)
    on May 21, 2026

  11. riaankleinhans commented on May 27, 2026

    @riaankleinhans
    riaankleinhans
    on May 27, 2026
    Contributor

    @ahmadqasembader is their other projects ready that we can add to this issue?

  12. ahmadqasembader commented on May 27, 2026

    @ahmadqasembader
    ahmadqasembader
    on May 27, 2026
    ContributorAuthor

    No. Will onboard a few more probably next week.

  13. Udaytaneja commented on Jul 11, 2026

    @Udaytaneja
    Udaytaneja
    on Jul 11, 2026

    Hi mantainers , I'd like to work on this . Please assign one of the tasks to me .

  14. riaankleinhans commented on Jul 13, 2026

    @riaankleinhans
    riaankleinhans
    on Jul 13, 2026
    Contributor

    Hi mantainers , I'd like to work on this . Please assign one of the tasks to me .

    @Udaytaneja this issue require privileged access and is handled by CNCF staff.

    You can have a look here for issue where help is needed or good first issues:
    https://clotributor.dev/

  15. riaankleinhans commented on Jul 29, 2026

    @riaankleinhans
    riaankleinhans
    on Jul 29, 2026
    Contributor

    Batch update — audit report repo_vs_project_file_maintainers_Jul28.md complete. All 11 projects triaged; the outreach emails for each are drafted and ready to send.

    PR opened — needs project merge + LF profile setup

    Each PR syncs the .project/maintainers.yaml roster to the upstream MAINTAINERS file. Where the upstream has an Emeritus section, the PR preserves it in a separate emeritus-maintainers team (informational only; not used by automation).

    Project PR Change
    open-gitops .project#2 +4 current maintainers, new emeritus-maintainers team (6)
    piraeus-datastore .project#2 Populate placeholder with 4 handles from upstream
    oauth2-proxy .project#2 +2 current, new emeritus-maintainers team (3)
    modelpack .project#2 +1 (caozhuozi)
    ovn-kubernetes .project#2 +2 current (npinaeva, kyrtapz); move dcbw to new emeritus-maintainers team
    pixie-io .project#2 +2 (jamesmbartlett, ddelnano)

    No PR needed — LF profile setup only

    .project/maintainers.yaml already matches upstream, but one or more maintainers still need to link their GitHub handle to their LF profile on OpenProfile.

    Project Notes
    kubeslice Upstream MAINTAINERS.md lists names/emails only (no GH handles), but the 5 .project handles align 1:1 with the upstream roster. 3 of 5 need to link their GH handle to their LF profile.
    opentofu All 7 handles match upstream. Gogotchuri needs to link GH handle to LF profile.

    Handle discrepancy — awaiting project decision

    Project Notes
    kubeovn Upstream MAINTAINERS lists bobz965; .project/maintainers.yaml lists zbb88888. Both handles resolve to the same person (Bingbing Zhang); zbb88888 is the one currently connected to their LF profile. Emailed the project to pick whichever handle Bingbing prefers and reconcile the two files.

    100% match — no action needed

    Project Notes
    KubeElasti Upstream and .project match; all 3 handles PCC-linked.
    project-akri Upstream OWNERS current maintainers match .project (4 handles, all PCC-linked). Upstream also lists 7 Emeritus Maintainers; no PR opened for these — can be added as an emeritus-maintainers team later if the project would like history preserved.

    Outreach emails will go out shortly to each project. Once PRs are merged and profiles updated, we can proceed to enable automation for these projects.

    Update (2026-07-29): Mailing lists provisioned in projects.csv for 3 projects from this batch:

    Project Mailing list ID Automation gate
    KubeElasti cncf-KubeElasti-maintainers@lists.cncf.io 146092 Ready — 100% match, all handles PCC-linked
    kubeovn cncf-kube-ovn-maintainers@lists.cncf.io 90174 Awaiting project decision on bobz965 vs zbb88888
    opentofu cncf-opentofu-maintainers@lists.cncf.io 138893 Awaiting Gogotchuri LF profile link

  16. ahmadqasembader commented on Sep 13, 2026

    @ahmadqasembader
    ahmadqasembader
    on Sep 13, 2026
    ContributorAuthor

    @riaankleinhans
    All PRs have been merged in this issue. If nothing else we need to do for the above projects, closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/dot-projectutilities/dot-project scaffolding and bootstrap toolingkind/choreChore or maintenanceneeds-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)priority/mediumMedium prioritystatus/in-progressCurrently being worked ontriage/validIssue or PR is valid with enough information to be actionable

Type

Task

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions