Add owners

[dbasunag]

Description

How Has This Been Tested?

Merge criteria:

• The commits are squashed in a cohesive manner and have meaningful messages.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

Summary by CodeRabbit

• Chores
  • Updated project owner and reviewer assignments in configuration settings.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[github-actions]

The following are automatically added/executed:

• PR size label.
• Run pre-commit
• Run tox
• Add PR author as the PR assignee
• Build image based on the PR

Available user actions:

• To mark a PR as WIP, add /wip in a comment. To remove it from the PR comment /wip cancel to the PR.
• To block merging of a PR, add /hold in a comment. To un-block merging of PR comment /hold cancel.
• To mark a PR as approved, add /lgtm in a comment. To remove, add /lgtm cancel.
  lgtm label removed on each new commit push.
• To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
  verified label removed on each new commit push.
• To Cherry-pick a merged PR /cherry-pick <target_branch_name> to the PR. If <target_branch_name> is valid,
  and the current PR is merged, a cherry-picked PR would be created and linked to the current PR.
• To build and push image to quay, add /build-push-pr-image in a comment. This would create an image with tag
  pr-<pr_number> to quay repository. This image tag, however would be deleted on PR merge or close action.

Supported labels

{'/build-push-pr-image', '/verified', '/cherry-pick', '/hold', '/lgtm', '/wip'}

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the OWNERS configuration file by replacing placeholder approver and reviewer entries with three explicit users (dbasunag, jgarciao, lugi0) in both the approvers and reviewers sections.

Changes

Cohort / File(s)	Summary
Configuration Metadata OWNERS	Replaced placeholder approver and reviewer entries with explicit user identifiers; expanded both approvers and reviewers lists by adding three users (dbasunag, jgarciao, lugi0)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add owners' is directly related to the changeset, which replaces placeholder entries with explicit owner usernames in the OWNERS configuration file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

OWNERS (1)

6-8: Consider whether identical approvers and reviewers lists are necessary.

The same users appear in both the approvers and reviewers sections. In many projects, the reviewers list is broader than approvers to separate review from merge permissions. If this redundancy is intentional for your team structure, feel free to ignore this comment.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4592fa9 and a68173c.

📒 Files selected for processing (1)

• OWNERS

🔇 Additional comments (1)

OWNERS (1)

2-4: Ensure organizational approval before granting approver permissions.

These GitHub users (jgarciao and lugi0 are confirmed as active developers, dbasunag appears valid) exist, but approver access grants significant repository permissions and requires documented organizational approval before merging.

[SB159]

/lgtm

[fege]

/lgtm

[github-actions]

Status of building tag latest: success.
Status of pushing tag latest to image registry: success.