S-1: Registry Governance Documentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- go
- Domain
- documentation
Research direction
Read docs/design/azd-tool/plan.md and todos.md first, then review pkg/extensions/registry.go for the existing registry model. Create docs/design/azd-tool/registry-governance.md covering ownership, approval, SLA, required contribution fields, and PR-based ingestion with CI validation. Done means the document includes the template and acceptance criteria, then receives team review and approval.
Written by the indexing model from the issue text.
Description
Problem / User Value
Partner teams at Microsoft need a clear, documented process for submitting their tools to the azd registry. Without a governance model, the registry becomes ungoverned — either no one knows how to contribute, or tools are added without quality review, leading to stale or broken entries.
Definition of Done
Governance document published at docs/design/azd-tool/registry-governance.md with ownership, approval process, SLA, contribution template, and ingestion process.
Tasks
- S-1: Write registry governance documentation (S) — Create
docs/design/azd-tool/registry-governance.mddocumenting: registry ownership (azd team), approval process (PR review by azd maintainers), SLA for additions (<5 business days), ingestion model (PR with YAML entry + test validation), contribution template with all required fields. Referencepkg/extensions/registry.goas prior art for the extension registry model.- AC: Governance doc published; ownership/approval/SLA clearly defined; contribution template included with all required fields; ingestion process described (PR-based with CI validation); document reviewed and approved by team
Sequencing
No dependencies — can start immediately and run in parallel with any other work.
Dependencies
None. This is a standalone documentation task with no code dependencies.
Discussion Traceability
| Discussion Item | Task |
|---|---|
| S1 (registry curation) | S-1 |
Design References
docs/design/azd-tool/plan.md— Standalone Tasksdocs/design/azd-tool/todos.md— S-1 acceptance criteriapkg/extensions/registry.go— prior art for extension registry model
- Dominant language
- Go
- Stars
- 569
- Forks
- 365
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 132
Contributor 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 Azure/azure-dev
-
area/extensions
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
area/ux bug customer-reported ext-agents
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
area/docs engineering item ext-agents test automation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
enhancement ext-agents
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·