👻 adding owners file to conform with community standards

[shawn-hurley]

fixes #82

Summary by CodeRabbit

• Documentation
  • Added project governance documentation outlining approver and maintainer roles.
  • Included community support channels and contributor involvement information.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

A new OWNERS.md file has been added to define project governance roles. The document lists three approvers and three maintainers with their GitHub profiles, includes a Slack channel contact reference, and links to the contributor ladder.

Changes

Cohort / File(s)	Change Summary
Governance Documentation OWNERS.md	New file establishing project governance structure with approvers, maintainers, contact information, and contributor pathway reference

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A governance scroll, so neat and bright,
With names and roles, all set just right,
The warren's order, now crystal clear,
Leadership mapped for all who steer! ✨

🚥 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 accurately describes the main change: adding an OWNERS.md file to establish project governance and conform with community standards.
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.}

[jmle]

@shawn-hurley I'm wondering if the maintainers need to have enough knowledge of the specific domain of the repo to be able to maintain?

[jmontleon]

I created konveyor/community#96 last week.

It seems Kubernetes community standards dictate that we should use a YAML formatted file called OWNERS rather than a markdown formatted OWNERS.md. I noticed in at least one repo we had a YAML formatted OWNERS.md, and perpetuated this in operator and tackle2-hub before realizing something was off. Please feel free to comment on the above as I'd like us to be consistent in which file/format we use and I think to adhere to Kubernetes we need OWNERS/YAML.