OSPS-GV-04.01 fails when CODEOWNERS is missing even if the policy is documented elsewhere
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
Research direction
Locate the OSPS-GV-04.01 check and read how its CODEOWNERS file_exists step is evaluated. Review the policy language in GOVERNANCE.md, CONTRIBUTING.md, MAINTAINERS.md, and README, then determine how the check should recognize the required policy. Done means a missing CODEOWNERS file does not fail the check when the policy is documented elsewhere.
Written by the indexing model from the issue text.
Description
OSPS-GV-04.01 (Maturity Level 3) reads:
While active, the project documentation MUST have a policy that code collaborators are reviewed prior to granting escalated permissions to sensitive resources.
The first step is file_exists on CODEOWNERS / .github/CODEOWNERS / docs/CODEOWNERS, so a project without a CODEOWNERS file fails immediately, even when GOVERNANCE.md or CONTRIBUTING.md contains exactly this policy. CODEOWNERS is also not a policy about reviewing collaborators before escalating their permissions; it assigns reviewers to paths.
Suggested direction: drop the CODEOWNERS presence step as a FAIL condition and look for the policy in the governance documents (GOVERNANCE.md, CONTRIBUTING.md, MAINTAINERS.md, README), with the final say from a judgment of that content.
- Dominant language
- Python
- Stars
- 22
- Forks
- 27
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 35
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from darnitdevorg/darnit
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
darnitdevorg/darnit#587 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
darnitdevorg/darnit#585 ·
Maintainers usually reply within 1 day
-
quality
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
darnitdevorg/darnit#523 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
darnitdevorg/darnit#516 ·
Maintainers usually reply within 1 day
-
good first issue module-core
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
darnitdevorg/darnit#506 ·
Maintainers usually reply within 1 day
All issues in darnitdevorg/darnit
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lugassawan/swe-workbench#799 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
vllm-project/vllm#61131 ·
Maintainers usually reply within 1 day
-
Non-string form field names raise AttributeError when files are attachedPossibly taken @nightcityblade claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kubernetes-client/python#2735 ·
Maintainers usually reply within 1 day
-
desktop help wanted test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day