Skip to content

docs(governance): add Payments Tech Council to GOVERNANCE.md and MAINTAINERS.md - #64

Merged
amithanda merged 1 commit into
mainfrom
payments-tech-council
Sep 2, 2026
Merged

docs(governance): add Payments Tech Council to GOVERNANCE.md and MAINTAINERS.md#64
amithanda merged 1 commit into
mainfrom
payments-tech-council

Conversation

@amithanda

Copy link
Copy Markdown
Contributor

Description

Adds the Payments Tech Council specification and initial members:

  • GOVERNANCE.md: Adds the Payments Tech Council definition
  • MAINTAINERS.md: Adds the Payments Tech Council roster with 12 inaugural members and 4 open seats to be elected.

Category (Required)

Please select one or more categories that apply to this change.

  • Core Protocol: Changes to the base communication layer, global context, or breaking refactors. (Requires Technical Council approval)
  • Governance/Contributing: Updates to GOVERNANCE.md, CONTRIBUTING.md, or CODEOWNERS. (Requires Governance Council approval)
  • Capability: New schemas (Discovery, Cart, etc.) or extensions. (Requires Maintainer approval)
  • Documentation: Updates to README, or documentations regarding schema or capabilities. (Requires Maintainer approval)
  • Infrastructure: CI/CD, Linters, or build scripts. (Requires DevOps Maintainer approval)
  • Maintenance: Version bumps, lockfile updates, or minor bug fixes. (Requires DevOps Maintainer approval)
  • SDK: Language-specific SDK updates and releases. (Requires DevOps Maintainer approval)
  • Samples / Conformance: Maintaining samples and the conformance suite. (Requires Maintainer approval)
  • UCP Schema: Changes to the ucp-schema tool (resolver, linter, validator). (Requires Maintainer approval)
  • Community Health (.github): Updates to templates, workflows, or org-level configs. (Requires DevOps Maintainer approval)

Checklist

  • I have followed the Contributing Guide (including Conventional Commits title requirements and ! for breaking changes).
  • I have updated the documentation (if applicable).
  • My changes pass all local linting and formatting checks.
  • 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.
  • (For Core/Capability) I have included/updated the relevant JSON schemas.
  • I have regenerated Python Pydantic models by running generate_models.sh under python_sdk.

@amithanda
amithanda force-pushed the payments-tech-council branch from fce96b8 to 258d05a Compare September 1, 2026 23:21

@igrigorik igrigorik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

👍

@amithanda
amithanda merged commit 258bf34 into main Sep 2, 2026
13 checks passed
@amithanda
amithanda deleted the payments-tech-council branch September 2, 2026 13:18
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.

3 participants