Outreach
Outreach
How to find the GovOps Working Group and take part in its work.
#Where the working group talks
| Channel | Use it for |
|---|---|
| GovOps LinkedIn Group | Announcements, discussion, and meeting notices |
| GitHub issues | Proposing metrics, catalog fields, and architecture changes |
| GitHub pull requests | Contributing document changes |
#How to contribute
Every deliverable in this repository is a plain Markdown file. You can edit one directly in the GitHub web editor, with no local toolchain. contributing.md has the details, including how to sign off a commit.
Good first contributions:
- Propose a metric using the template. The metric set has a documented parking lot of candidates held for v2, each with the reason recorded.
- Answer an open question. The ACC design and the metrics front matter both close with open questions.
- Report a gap. If the architecture does not cover a system you have to govern, open an issue describing it.
#Who the work is for
The proposal names the audiences the working group wants feedback from: application security teams, identity practitioners, authorization vendors, auditors, GRC professionals, cloud security teams, and AI governance practitioners. If you are one of those, your review is the contribution.
#Talking about GovOps
The one-line description:
The GovOps Working Group advances continuous, policy-driven governance for authorization, risk, and trust across open source, cloud, and agentic systems.
The three steering responsibilities GovOps names are risk management, accountability, and observability — measure risk, transparency, and accountability.