Skip to content

chore: populate project.yaml metadata - #4

Open
Timur Tukaev (tym83) wants to merge 1 commit into
mainfrom
chore/project-metadata-fix
Open

chore: populate project.yaml metadata#4
Timur Tukaev (tym83) wants to merge 1 commit into
mainfrom
chore/project-metadata-fix

Conversation

@tym83

Copy link
Copy Markdown
Contributor

What this PR does

Fills in the verified metadata in project.yaml and removes the AUTO-DETECTED placeholders that pointed at outdated values.

Changes

Why now

CNCF requested project teams populate .project metadata to support the TOC review for level-change applications. The cozystack Incubation application is in flight at cncf/toc#1916.

This PR is independent of #2 (different files); both can land in any order.

Release note

release-note NONE ​

- Set project_lead to @kvaps (the auto-detected value pointed at a
  maintainer who has since moved to Emeritus).
- Set cncf_slack_channel to #cozystack.
- Add the full list of sub-projects to the repositories section
  (matches MAINTAINERS.md and the Incubation application).
- Set package_managers.oci to ghcr.io/cozystack/cozystack.
- Drop AUTO-DETECTED TODO markers from fields that have been verified.
- Tidy the description (collapse double space).

Signed-off-by: Timur Tukaev <timur.tukaev@aenix.io>
@coderabbitai

coderabbitai Bot commented May 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@tym83, we couldn't start this review because you've used your available PR reviews for now.

Your plan currently allows 1 review/hour. Refill in 54 minutes and 36 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e78b7b5b-7fb7-463a-98c4-77ceab0e3390

📥 Commits

Reviewing files that changed from the base of the PR and between 6b6db8c and e9d9c61.

📒 Files selected for processing (1)
  • project.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/project-metadata-fix

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the project.yaml metadata for Cozystack, including the project lead, Slack channel, and an expanded list of repositories. It also adds OCI package manager information and cleans up auto-generated comments. Feedback was provided regarding the formatting of the Slack channel name (removing the # prefix), the inclusion of a repository outside the official organization, and the use of a non-standard oci key in the package manager configuration which should be replaced with docker for schema compatibility.

Comment thread project.yaml
# TODO: Set CNCF Slack channel
# cncf_slack_channel: "#cozystack"
project_lead: "kvaps"
cncf_slack_channel: "#cozystack"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The cncf_slack_channel field typically expects the channel name without the # prefix. Including the prefix may interfere with automated tools that generate Slack URLs or integrations that expect only the channel identifier.

cncf_slack_channel: "cozystack"

Comment thread project.yaml
- "https://github.com/cozystack/talos-bootstrap"
- "https://github.com/cozystack/cozystack-ui"
- "https://github.com/cozystack/blockstor"
- "https://github.com/aenix-io/etcd-operator"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The repository https://github.com/aenix-io/etcd-operator is hosted under the aenix-io organization, whereas all other repositories are under the cozystack organization. For CNCF project metadata, all listed repositories should ideally be under the project's official organization to ensure consistent governance and visibility. If this is a core component of the project, consider moving it to the cozystack organization; otherwise, if it is an external dependency, it should likely be removed from this list.

Comment thread project.yaml
# docker: "cozystack/cozystack"

package_managers:
oci: "ghcr.io/cozystack/cozystack"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The key oci is not a standard field in the .project schema used by CNCF automation. To ensure compatibility with automated tools (such as the CNCF landscape or project portal), the docker key should be used for container registries, even when hosting OCI-compliant images on GHCR.

  docker: "ghcr.io/cozystack/cozystack"

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant