Add CONTRIBUTING.md with guidelines for joining stolostron org and su…

[FilipB]

…bmitting PRs

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: FilipB

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [FilipB]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[FilipB]

Depends on openshift/release#80885

[FilipB]

/hold

[coderabbitai]

Warning

Review limit reached

@FilipB, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 56 minutes and 6 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 374e749b-8622-43f6-905b-5ff038c88e64

📥 Commits

Reviewing files that changed from the base of the PR and between ae3c2f0 and 7f2ad71.

📒 Files selected for processing (1)

• CONTRIBUTING.md

📝 Walkthrough

Walkthrough

A new CONTRIBUTING.md file was added at the repository root. It includes contribution overview text, getting started steps, organization onboarding information, pull request and review requirements, DCO sign-off guidance, a fork/clone/branch/test/commit/push workflow, and an Apache License 2.0 contribution statement.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 8

✅ Passed checks (8 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the main change: adding CONTRIBUTING.md with contribution and org-joining guidance.
Description check	✅ Passed	The description is related to the change and mentions submitting PRs, which fits the new contribution guide.
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.
No-Sensitive-Data-In-Logs	✅ Passed	Only CONTRIBUTING.md was added; it contains contribution guidance and no log statements or secret-bearing values.
Stable And Deterministic Test Names	✅ Passed	Only CONTRIBUTING.md changed vs parent; no test files or Ginkgo titles were added or modified.
No-Weak-Crypto	✅ Passed	PR only adds CONTRIBUTING.md, which contains no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons.
Container-Privileges	✅ Passed	PR only adds CONTRIBUTING.md; no container/K8s manifests were changed, so no new privileged/root settings were introduced.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CONTRIBUTING.md`:
- Around line 28-43: Update the contributor guidance in CONTRIBUTING.md to use
consistent DCO terminology and the correct license name: change the commit
requirement wording from generic “signed” to “DCO sign-off,” and replace “Apache
Public License 2.0” with “Apache License, Version 2.0.” Keep the existing intent
intact while aligning the review process and Developer Certificate of Origin
section with the project’s actual contribution/compliance rules.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 42d67ecb-25c2-41b5-92c7-812189a21e62

📥 Commits

Reviewing files that changed from the base of the PR and between 4287d1c and d847ee3.

📒 Files selected for processing (1)

• CONTRIBUTING.md

[mkolesnik]

Thanks, a few small comments otherwise LGTM