Context
JSS now has two committers (@melvincarvalho project lead, @jjohare maintainer-onboarding). The repo already has CONTRIBUTING.md (workflow, code style, AI-assistance disclosure) and .github/CODEOWNERS (path-level review routing), but does not have a top-level MAINTAINERS.md.
A standalone MAINTAINERS.md makes the team structure visible to contributors and observers without duplicating CONTRIBUTING or CODEOWNERS content.
Proposed
Add MAINTAINERS.md at the repo root with:
- Current maintainers list with focus area
- Pointer to
.github/CODEOWNERS for path-level routing
- Pointer to
CONTRIBUTING.md for the contributor workflow
- Brief note on how new maintainers are added (by invitation, no formal vote)
- Security disclosure pointer (GitHub private security advisories)
One-screen, scannable, in the same register as CONTRIBUTING.md.
Not in scope (this issue)
- Formal governance structure / voting / charter
- Code of Conduct (separate work item if/when needed)
- Maintainer-emeritus or contributor-recognition sections (out of scope until there's substantive history)
Open questions
- @jjohare focus area description (or leave as "(onboarding)" for now?)
- Security contact: GitHub private advisories only, or also an email?
Context
JSS now has two committers (@melvincarvalho project lead, @jjohare maintainer-onboarding). The repo already has CONTRIBUTING.md (workflow, code style, AI-assistance disclosure) and .github/CODEOWNERS (path-level review routing), but does not have a top-level MAINTAINERS.md.
A standalone MAINTAINERS.md makes the team structure visible to contributors and observers without duplicating CONTRIBUTING or CODEOWNERS content.
Proposed
Add
MAINTAINERS.mdat the repo root with:.github/CODEOWNERSfor path-level routingCONTRIBUTING.mdfor the contributor workflowOne-screen, scannable, in the same register as
CONTRIBUTING.md.Not in scope (this issue)
Open questions