Skip to content

Onboarding: complete external-secrets .project setup #1

Closed

Description

@ahmadqasembader

Hi @caniszczyk @Flydiverny @gusfcarvalho 👋

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

external-secrets/.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 project_lead GitHub handle
  • Set slack_channels
  • Add package_managers if distributed via registries
  • No maintainers found in cncf/foundation project-maintainers.csv — add maintainer handles manually
  • 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
@Flydiverny maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@form3tech maintainer external-secrets/external-secrets — MAINTAINERS.md
@gusfcarvalho maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@IdanAdar maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@jonatasbaldin maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@knelasevero maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@mcavoyk maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@moolen maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@riccardomc maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@rodrmartinez maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@sebagomez maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@silasbw maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md
@Skarlso maintainer external-secrets/bitwarden-sdk-server — MAINTAINERS.md
external-secrets/external-secrets — MAINTAINERS.md

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

Activity

  1. Skarlso commented on Jul 4, 2026

    @Skarlso
    Contributor

    Yeah, most of these are emeritus or parsed completely incorrectly. :)

  2. Skarlso commented on Jul 15, 2026

    @Skarlso
    Contributor

    I was out of vacation, I will take a look at this come this Friday. :)

  3. ahmadqasembader commented on Jul 15, 2026

    @ahmadqasembader
    ContributorAuthor

    Hi @Skarlso

    Due to a bug in the automation tool, the tool didn't populate the maintainers.yml correctly upon onboarding. So I added the registered maintainers from the cncf foundation CSV Sheet manually.

    For the "suggested maintainers list", yes indeed it contains some false-positive and we'll try to handle these cases. Thanks for pointing them out.

  4. Skarlso commented on Jul 27, 2026

    @Skarlso
    Contributor

    No worries. 😌 I was on vacation last week so I'm going to take care of this this week. Thanks!🙏

  5. evrardjp commented on Jul 28, 2026

    @evrardjp

    Thanks @Skarlso . I can't do that on my own as interim.

  6. evrardj-roche commented on Sep 25, 2026

    @evrardj-roche
    Contributor

    Project lead handle is correct.

    Slack channel is good (we just have an extra slack channel, so I will propose a PR there).

    For package_managers: we are using ghcr: external-secrets/external-secrets -> @ahmadqasembader is that good enough? Or should we do docker: "ghcr.io/external-secrets/external-secrets" ? https://github.com/cncf/automation/blob/main/utilities/dot-project/SCHEMA.md is not very explicit , examples aren't either.

    cncf/foundation project-maintainers.csv -> https://github.com/cncf/foundation/blob/main/project-maintainers-.project.csv?plain=1 is up to date.

    Maintainers is up to date. I will double check if they have LFID linked to github.

    I think we can close this, if you agree @ahmadqasembader .

  7. ahmadqasembader commented on Sep 25, 2026

    @ahmadqasembader
    ContributorAuthor

    Hi @evrardj-roche

    docker: "ghcr.io/external-secrets/external-secrets is better imo. Both formats are okay though.

    Just a heads-up, you don't need to update the CSV file in cncf/foundation anymore. You can simply update the .project/maintainer.yml file, and CNCF automation will take it from there.

    Yes, we can close. Thanks

    Nitpicks:
    A TODO is still here in this file; if the value is corrected, please remove the comment so we know that the data has been verified.

    issue: "https://github.com/cncf/sandbox/issues/211" # TODO: AUTO-DETECTED — please verify

    Also, I noticed that the artwork link points to a blank page. Can you please update it?

    artwork: "https://landscape.cncf.io/logos/external-secrets.svg"

  8. evrardj-roche commented on Sep 25, 2026

    @evrardj-roche
    Contributor

    I will update this and close.

    Thanks for the reply.

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

Metadata

Metadata

Assignees

Labels

metadataProject metadataonboardingProject onboarding tasks

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions