chore: point project_lead at current leads and align the roster

[Andrei Kvapil (kvaps)]

What this PR does

Brings the CNCF-facing metadata back in step with the project.

project_lead names an emeritus maintainer. It still carries the value the bootstrap scaffold auto-detected in May, with its TODO: AUTO-DETECTED — please verify comment intact. The person it names moved to emeritus status, so anything reading this file — the landscape, dot-project automation, a Due Diligence reviewer — is pointed at someone who no longer leads the project. The schema accepts string | string[], so both current leads are recorded.

Roster. Adds the three maintainers being added in cozystack/cozystack#3462, and a reviewers team for the area-scoped role that CONTRIBUTOR_LADDER.md defines and .github/CODEOWNERS has been carrying since 2024 — it simply had no representation in the roster or in this metadata. The schema requires only project-maintainers; additional teams are allowed.

Governance paths. Fills in roles_and_teams, contributor_ladder and decision_making_process, which the schema defines and Due Diligence asks for directly. sub_project_list is deliberately left empty: GOVERNANCE.md has no sub-project section yet, and pointing at one that does not exist would be worse than leaving the field unset.

Depends on

cozystack/cozystack#3462, which makes MAINTAINERS.md say the same thing. Merging this first would leave the metadata ahead of the roster it mirrors.

Summary by CodeRabbit

• Documentation
  • Updated maintainer and reviewer information to reflect current project responsibilities.
  • Expanded project leadership details to support shared ownership.
  • Added references to documentation covering roles and teams, contributor progression, and decision-making processes.
• Chores
  • Improved project metadata consistency with the repository’s governance and code ownership information.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[coderabbitai]

Warning

Review limit reached

@kvaps, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 50 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0d8e59ab-37f8-4e92-bdfe-e8ebf06b141f

📥 Commits

Reviewing files that changed from the base of the PR and between 85716ba and 6a4a9c1.

📒 Files selected for processing (1)

• maintainers.yaml

📝 Walkthrough

Walkthrough

Project metadata now documents the upstream maintainer source, expands maintainer membership, adds reviewers, lists two project leads, and references governance documentation for roles, contributor progression, and decision-making.

Changes

Project governance

Layer / File(s)	Summary
Maintainer and reviewer roster maintainers.yaml	Adds upstream source comments, updates the project-maintainers membership, and introduces a reviewers team.
Project leads and governance references project.yaml	Changes project_lead to a two-entry list and adds three governance documentation paths.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• cozystack/.project#2: Overlaps in the maintainers.yaml project-maintainer membership configuration.

Suggested reviewers: tym83

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main metadata update: switching project_lead to current leads and aligning the maintainer roster.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/align-roster-and-project-lead

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[Aleksei Sviridkin (lexfrei)]

LGTM. The roster matches cozystack/cozystack#3462 on both sides — the same nine maintainers, and the reviewers team is the same three people the Reviewers table names. Both CNCF validators pass on the list form of project_lead, which was the part I expected the schema to be picky about.