Owners, admins, and maintainers for Slinky Containers: governance, triage, reviews, releases, and technical direction. Update the roster when membership changes.
| Name | GitHub | Role | Areas / notes |
|---|---|---|---|
| Marlow Warnicke | @catblade | Owner/Admin, Maintainer | Slinky dev team |
| Tim Wickberg | @wickberg | Owner/Admin | Slinky dev team |
| Skyler Malinowski | @SkylerMalinowski | Maintainer | Slinky dev team |
| Alan Mutschelknaus | @alanmutsch | Maintainer | Slinky dev team |
| Vivian Hafener | @vivian-hafener | Maintainer | Slinky dev team |
Roles (summary)
- Owner/Admin — Organization and repository administration (access, policy, branch protection, and cross-cutting decisions). Listed owners may overlap with maintainer duties where noted.
- Maintainer — Reviews and approves changes, cuts releases, owns roadmap for this repo, and keeps docs and issue templates accurate.
Use this order so the right channel gets the request first.
- Community / product issues and feature discussion — Open or comment on
GitHub Issues (see
CONTRIBUTING.md). Maintainers handle this on a best-effort basis. - Security vulnerabilities — Follow
SECURITY.mdonly. Do not use public issues or PRs for security reports. - Conduct concerns — See
CODE_OF_CONDUCT.mdfor reporting and enforcement contacts.
- Issues and code: github.com/SlinkyProject/containers/issues
- Security:
SECURITY.md - Contributing:
CONTRIBUTING.md
Keep this file in sync with the roster and with CODEOWNERS at
the repository root (when present).