Onboarding: complete Falco .project setup

[ahmadqasembader]

Hi @FedeDP @jasondellaluce @leogr 👋

.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.

falcosecurity/.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

• 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.

Suggested maintainers (from your org's governance files)

These GitHub handles were found in your org's CODEOWNERS / OWNERS / MAINTAINERS files but are not yet in the CNCF foundation maintainers CSV. If they are current maintainers, please add them to project-maintainers.csv by opening a PR against cncf/foundation and maintainers.yaml. Otherwise, you can ignore this list - they won't be added to the maintainers.yml.

Handle	Role(s)	Found in
@ahmedameenaim	maintainer	falcosecurity/evolution — MAINTAINERS.md
@araujof	maintainer, approver, reviewer	falcosecurity/community — OWNERS falcosecurity/evolution — MAINTAINERS.md falcosecurity/libs-sdk-go — OWNERS
@bencer	reviewer	falcosecurity/charts — OWNERS
@cappellinsamuele	maintainer, approver	falcosecurity/evolution — MAINTAINERS.md falcosecurity/pigeon — OWNERS
@darryk10	maintainer, approver, reviewer	falcosecurity/evolution — MAINTAINERS.md falcosecurity/falco-actions — OWNERS falcosecurity/rules — OWNERS
@dwindsor	maintainer, approver	falcosecurity/driverkit — OWNERS falcosecurity/evolution — MAINTAINERS.md
@ewilderj	maintainer, approver	falcosecurity/evolution — MAINTAINERS.md falcosecurity/flycheck-falco-rules — OWNERS
@EXONER4TED	maintainer, approver	falcosecurity/driverkit — OWNERS falcosecurity/evolution — MAINTAINERS.md falcosecurity/kernel-crawler — OWNERS
@fjogeleit	maintainer, approver	falcosecurity/evolution — MAINTAINERS.md falcosecurity/falcosidekick-ui — OWNERS falcosecurity/falcosidekick — OWNERS
@hbrueckner	maintainer, reviewer	falcosecurity/elftoolchain — OWNERS falcosecurity/evolution — MAINTAINERS.md falcosecurity/libs — OWNERS
@IgorEulalio	maintainer, approver	falcosecurity/evolution — MAINTAINERS.md falcosecurity/falco-talon — OWNERS
@jonahjon	maintainer, approver	falcosecurity/evolution — MAINTAINERS.md falcosecurity/test-infra — OWNERS
@Kaizhe	reviewer	falcosecurity/community — OWNERS falcosecurity/falco — OWNERS falcosecurity/rules — OWNERS
@ldegio	maintainer, approver, reviewer	falcosecurity/evolution — MAINTAINERS.md falcosecurity/falco-aws-terraform — OWNERS falcosecurity/plugin-sdk-cpp — OWNERS falcosecurity/prempti — OWNERS
@leodido	maintainer, approver, reviewer	falcosecurity/driverkit — OWNERS falcosecurity/evolution — MAINTAINERS.md falcosecurity/plugin-sdk-cpp — OWNERS falcosecurity/rules — OWNERS
@Lowaiz	maintainer, approver	falcosecurity/driverkit — OWNERS falcosecurity/evolution — MAINTAINERS.md
@mrgian	maintainer, approver	falcosecurity/evolution — MAINTAINERS.md falcosecurity/plugin-sdk-rs — OWNERS
@rabbitstack	maintainer, approver	falcosecurity/evolution — MAINTAINERS.md falcosecurity/falco-rustlings — OWNERS
@Rohith-Raju	maintainer, approver	falcosecurity/evolution — MAINTAINERS.md falcosecurity/falco-playground — OWNERS
@sboschman	maintainer	falcosecurity/evolution — MAINTAINERS.md
@scraly	maintainer	falcosecurity/evolution — MAINTAINERS.md
@terror96	reviewer	falcosecurity/libs — OWNERS
@terylt	maintainer, approver, reviewer	falcosecurity/community — OWNERS falcosecurity/evolution — MAINTAINERS.md falcosecurity/libs-sdk-go — OWNERS
@vjjmiras	maintainer, reviewer	falcosecurity/evolution — MAINTAINERS.md falcosecurity/falco-website — OWNERS

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

[leogr]

Hi @ahmadqasembader

Thanks for taking care of this. As previously mentioned, the transition to this new approach will take a bit since our governance currently mandates that we centralize everything in https://github.com/falcosecurity/evolution
However, this isn't a big deal; we will evolve it accordingly to new requirements :)

To kick this off, I start with a few questions:

1. I noticed the automated tool created a https://github.com/falcosecurity/.project/blob/main/CODEOWNERS file in this repository. Per our governance, we rely only on the OWNERS file. So, can we migrate the CODEOWNERS file to the OWNERS format in this repo?
2. Our governance defines the requirements and responsibilities of the Core Maintainers team. Per our policy, only core maintainers have been considered maintainers of The Falco Project as per CNCF interpretation and, for this reason, they are the only maintainers listed in https://github.com/cncf/foundation/blob/main/project-maintainers.csv Thus, the https://github.com/falcosecurity/.project/blob/main/maintainers.yaml file should populated with the members of the Core Maintainers team only. Can you confirm this?
3. This is more general guidance. Since this repository overlaps with some content we already have in https://github.com/falcosecurity/evolution, I'm wondering whether we can move other metadata here. Is there any strict requirement for how we should manage https://github.com/falcosecurity/.project?

Thanks 🙏

[ahmadqasembader]

Hi @leogr

1. Feel free to migrate it to the OWNERS format. Although I'd prefer to keep it just for consistency's sake. You can have both CODEOWNERS and OWNERS as well.

2. Correct. The maintainers.yml in this repo has been populated strictly from the cncf/foundation CSV Sheet, and then we scanned your Org for governance files to surface any possible maintainers who were not added to the CSV sheet (surfaced above in the "Suggest Maintainers List"), so please double-check your Core Maintainers list and update the maintainers.yml accordingly. Once this repo has been created and updated, you don't have to update the cncf/foundation anymore, we'll take it from there.

3. yes feel free to add whatever metadata docs you might have. What matter is to not breack the schema of the maintainers.yml and the project.yml and the rest is fair game. An example: https://github.com/containerd/.project - Most of these docs were added by the project