Skip to content

chore: add CODEOWNERS file#167

Open
nearlyforget wants to merge 8 commits intoUniversal-Commerce-Protocol:mainfrom
nearlyforget:owners
Open

chore: add CODEOWNERS file#167
nearlyforget wants to merge 8 commits intoUniversal-Commerce-Protocol:mainfrom
nearlyforget:owners

Conversation

@nearlyforget
Copy link

Description

Add CODEOWNERS file with ownership Logic:

  • Default: @Universal-Commerce-Protocol/maintainers
  • Protocol/Spec: @Universal-Commerce-Protocol/tech-council
  • Capabilities/Extensions: @Universal-Commerce-Protocol/tech-council & maintainers
  • Governance: @Universal-Commerce-Protocol/governance-council
  • Infrastructure: @Universal-Commerce-Protocol/devops-maintainers

Type of change

Please delete options that are not relevant.

  • Documentation update

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

@nearlyforget nearlyforget marked this pull request as ready for review February 12, 2026 03:00
@nearlyforget nearlyforget requested a review from a team February 12, 2026 03:00
@@ -0,0 +1,31 @@
# Universal Commerce Protocol (UCP) Codeowners
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we order from lowest level to highest level of governance, since "the last matching pattern takes the most precedence" in CODEOWNERS?

# Documentation
/docs/ @Universal-Commerce-Protocol/maintainers

# Governance
Copy link
Contributor

Choose a reason for hiding this comment

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

Won't these be in .github now?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants