Onboarding: complete OpenFunction .project setup

Hi @benjaminhuo @tpiperatgod @wanjunlei 👋

.project (dot-project) is a CNCF initiative to centralize and automate metadata management for all CNCF projects. It lives in the cncf/automation repo, and the CNCF automation team is rolling it out to Sandbox projects first.

OpenFunction/.project was provisioned automatically. The tool collects project metadata from public sources (CNCF landscape, CLOMonitor, GitHub governance files) and populates the repo with it. Since this is best-effort automation, some fields need your verification.

Two things need your attention:

Checklist

• Set identity_type under legal (has_dco, has_cla)
• Add adopters list (ADOPTERS.md)
• Add package_managers if distributed via registries
• Ensure all project maintainers have a LFID at https://openprofile.dev/
• Update LFID so their GitHub ID is linked to the LFID, and correct their email address and company affiliation if needed.

Please open a PR against this repo to address each item. The validators will block merge until project.yaml and maintainers.yaml are complete.

These fields could not be auto-detected and must be filled in manually. Please open a PR against this repo to address each item. The validators will block merge until project.yaml and maintainers.yaml are complete.

Inline TODOs in YAML files

Some fields were auto-detected but are marked # TODO: AUTO-DETECTED — please verify directly in maintainers.yaml and project.yaml. These are best-effort guesses (e.g. project_lead, cncf_slack_channel, TOC issue URL) and should be confirmed or corrected before closing this issue. They won't appear in the checklist above.

This issue was auto-generated by the CNCF .project provisioning tool.

Review project.yaml and maintainers.yaml, including the inline TODOs, then check ADOPTERS.md and the CNCF .project requirements. Confirm the legal identity settings, adopters, package managers, maintainer LFIDs and metadata, and run the repository validators. Done means all checklist items and TODOs are verified and the validators accept both YAML files.