Skip to content

GOVERNANCE.md

Latest commit

 

History

History
76 lines (50 loc) · 4.07 KB

GOVERNANCE.md

File metadata and controls

76 lines (50 loc) · 4.07 KB
Raw

Governance Mechanism

Mission

As an important component of the Triton ecosystem, the Triton-Ascend project is committed to providing an efficient and user-friendly Triton compilation framework for all Ascend NPU users, enabling Triton code to run efficiently on Ascend hardware and actively contributing to enriching the Triton and Ascend ecosystems.

Principles

  • Open and Transparent: All technical decisions and community discussions are conducted through public channels
  • Contribution-Oriented: Membership is based on individual capability and contribution, not tied to employers
  • Community-Driven: Encourage broad participation, respect diverse viewpoints, and reach consensus through discussion and voting

Governance Structure

Triton-Ascend is an open-source project under the Triton community, with role appointments ultimately decided by the Triton community. The project adopts a layered technical governance structure:

Contributor

Responsibilities:

  • Help new contributors integrate into the project
  • Handle and respond to community Issues
  • Review RFCs and code

Requirements:

  • Complete at least one contribution
  • Continuously and actively participate in the project through submitting Issues, code reviews, code submissions, and participating in community activities

Permissions: Granted the GitHub repository Triage role, including read and clone access, and permission to submit Issues and PRs.

Maintainer

Responsibilities:

  • Define the project's vision and mission, shape technical direction, and ensure long-term success
  • Have code merge permissions, lead roadmap planning
  • Review community contributions and continuously improve code
  • Responsible for code quality and architectural decisions of core modules
  • Participate in release decisions
  • Guide contributors in completing code contributions
  • Participate in community technical meetings, discuss and vote on technical direction, large-scale proposals, and Release matters

Requirements:

  • Deep understanding of the Triton and Triton-Ascend codebase
  • Commitment to continuous code contribution, with capabilities in design, development, and PR review workflows
  • Actively participate in community code reviews, deliver at least one major feature, and maintain continuous high-quality contributions
  • Actively handle Issues, respond to inquiries, and participate in discussions
  • Made significant technical contributions to the project (such as core feature development, architectural design, performance optimization, etc.)
  • Demonstrate good technical judgment and community collaboration skills

Permissions: Granted GitHub repository write permissions, including read, clone, and push code to the repository, core branch protection and merge permissions, release execution permissions, and management of Issues and Pull Requests.

Promotion is collectively reviewed by existing Maintainers, considering contribution quality, continuity, and community engagement.

Nomination and Removal

Principles

  • Membership is based on individual capability, demonstrated through contributions, reviews, and discussions
  • Candidates must agree with Triton-Ascend's principles and maintain consistent behavior
  • Maintainers who have not contributed to the project for 6 consecutive months may be transitioned to Emeritus status
  • Membership is granted to individuals, not tied to employers

Nomination Process

  • Nominations can be initiated by anyone, including self-nominations, through a community Issue
  • Nominations must include the candidate's contribution record and technical capability description
  • Existing Maintainers review and evaluate, requiring more than half of current Maintainers to agree with no objections

Regular Review

  • Monthly review of all Maintainers' activity during technical meetings
  • Maintainers who have not contributed to the project for 6 consecutive months may be transitioned to Emeritus status after discussion
  • Emeritus Maintainers can apply to restore their Maintainer status at any time by resuming active contributions