Skip to content

docs: address repo-health audit nits in README and CONTRIBUTING - #1193

Open
lbliii wants to merge 2 commits into
mainfrom
lbliii/repo-health-nits
Open

lbliii wants to merge 2 commits into
mainfrom
lbliii/repo-health-nits

Conversation

@lbliii

@lbliii lbliii commented Apr 30, 2026

Copy link
Copy Markdown
Contributor

Summary

Addresses the missing must-haves flagged by the GitHub repo-health dashboard audit (Mar 25, 2026). The audit had README at 5/9 must-haves (Yellow) and CONTRIBUTING at 4/7 must-haves (Yellow).

README — adds the three missing items

  • License section linking to LICENSE (Apache-2.0), with a note about per-environment third-party licenses and ATTRIBUTIONS.md
  • Getting Help section with channels (Discussions, Issues, SECURITY, CoC) and explicit response expectations
  • Roadmap with checkbox priorities and a link to GitHub milestones
  • Refreshed Community & Support to surface CONTRIBUTING.md, Code of Conduct, and a good first issue filter

CONTRIBUTING — adds the four missing items

  • Code of Conduct callout at the top of the doc (CoC was previously not referenced from CONTRIBUTING)
  • Finding a First Issue section with good first issue / help wanted links and a claiming process
  • Contribution Workflow — explicit fork → clone → branch → test → PR steps with upstream remote and rebase commands
  • Pull Request Expectations — tests required, docs update policy, focused PRs, DCO + GPG signing, CI, review etiquette referencing the CoC

⚠️ Placeholders pending PM approval

Some content was synthesized to satisfy the audit's must-haves but has not been confirmed by product management. These are explicitly marked with [!NOTE] callouts in the rendered docs:

  • Roadmap bullets (illustrative — derived from existing README/CLAUDE.md hints, not from an authoritative roadmap doc)
  • Response-time targets ("few business days" for triage, "one week" for initial PR review)
  • Issue claim stall window (two weeks before unassign)

These should be replaced with the official targets before the next audit run.

Test plan

  • Render README.md and CONTRIBUTING.md on GitHub and verify all anchor links resolve
  • Confirm https://github.com/NVIDIA-NeMo/Gym/milestones and https://github.com/NVIDIA-NeMo/Gym/discussions exist or are appropriate to link (enable Discussions if not yet enabled)
  • Confirm good first issue and help wanted labels exist on the repo
  • PM review of the placeholder content (roadmap bullets, response-time SLAs, claim-stall window) and replace with official values
  • Re-run the repo-health audit to verify README and CONTRIBUTING flip from Yellow to Green

🤖 Generated with Claude Code

Adds the missing must-haves flagged by the GitHub repo-health audit:

README:
- License section linking to LICENSE (Apache-2.0)
- Getting Help section with channels and response expectations
- Roadmap section with milestones link (placeholder, pending PM review)
- Refreshed Community & Support links (CoC, good-first-issues)

CONTRIBUTING:
- Code of Conduct callout at the top
- Finding a First Issue section with claim process
- Fork -> branch -> test -> PR workflow
- Pull Request expectations (tests, docs, signing, CI, review etiquette)

Roadmap items and response-time targets are explicitly marked as
placeholders pending product management review.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Signed-off-by: Lawrence Lane <llane@nvidia.com>
@lbliii
lbliii requested review from cmunley1 and cwing-nvidia April 30, 2026 13:30
Comment thread CONTRIBUTING.md Resolved
Comment thread README.md Resolved
Signed-off-by: Lawrence Lane <llane@nvidia.com>
@cwing-nvidia

Copy link
Copy Markdown
Contributor

@anwithk can you help address these two points

Response-time targets ("few business days" for triage, "one week" for initial PR review)
Issue claim stall window (two weeks before unassign)

Comment thread README.md
- **[Training Tutorials](https://docs.nvidia.com/nemo/gym/main/training-tutorials)** - Train with NeMo Gym environments
- **[API Reference](https://docs.nvidia.com/nemo/gym/main/api/reference/api-reference)** - Complete class and function reference

- **[Roadmap](https://github.com/NVIDIA-NeMo/Gym/issues/1526)** - Plans for the next NeMo Gym release

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@lbliii we have a separate pinned issue for each next release. should we keep updating it in the README (which has a risk of becoming stale) or we could consider linking to the projects which have boards for each release? https://github.com/NVIDIA-NeMo/Gym/projects

Comment thread README.md

- **[Roadmap](https://github.com/NVIDIA-NeMo/Gym/issues/1526)** - Plans for the next NeMo Gym release

## 💬 Getting Help

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

do we need separate Getting Help and Community & Support sections? they seem related, can we consolidate?

@github-actions github-actions Bot added the sla:review-overdue Review response is over the one-business-day SLA label Jul 17, 2026
@svcnvidia-nemo-ci svcnvidia-nemo-ci added area:docs Generic documentation without another dominant domain docs Documentation-only updates or documentation debt needs-review PR is ready for code review and waiting on a reviewer labels Oct 20, 2026

This branch has not been deployed

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

Labels

area:docs Generic documentation without another dominant domain docs Documentation-only updates or documentation debt needs-review PR is ready for code review and waiting on a reviewer sla:review-overdue Review response is over the one-business-day SLA

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants