Skip to content

Latest commit

 

History

History
113 lines (91 loc) · 4.88 KB

MAINTAINERS.md

File metadata and controls

113 lines (91 loc) · 4.88 KB
Raw

Introduction

This document defines roles in oneMKL Interfaces project.

Roles and responsibilities

oneMKL Interfaces project defines three main roles:

These roles are merit based. Refer to the corresponding section for specific requirements and the nomination process.

Contributor

A Contributor invests time and resources to improve oneMKL Interfaces project. Anyone can become a Contributor by bringing value in one of the following ways:

  • Answer questions from community members.
  • Submit feedback to design proposals.
  • Review and/or test pull requests.
  • Test releases and report bugs.
  • Contribute code, including bug fixes, features implementations, and performance optimizations.
  • Contribute design proposals.

Responsibilities:

Privileges:

  • Eligible to join one of the maintainer groups.

Domain Maintainer

Domain maintainer has responsibility for a specific domain in the project. Domain maintainers are collectively responsible for developing and maintaining their domain, including reviewing all changes to their domain and indicating whether those changes are ready to merge. They have a track record of contribution and review in the project.

Responsibilities:

  • Follow the Code of Conduct.
  • Follow and enforce the project contributing guidelines.
  • Co-own with other domain maintainers a specific domain, including contributing bug fixes, implementing features, and answering domain specific questions in #onemkl Slack channel.
  • Review pull requests in their specific domain.
  • Monitor testing results and flag issues in their specific areas of responsibility.
  • Support and guide Contributors.

Requirements:

  • Experience as Contributor in the specific domain for at least 6 months.
  • Commit at least 25% of working time to the project.
  • Track record of accepted code contributions to a specific domain.
  • Track record of contributions to the code review process.
  • Demonstrated in-depth knowledge of the specific domain.
  • Commits to being responsible for that specific domain.

Privileges:

  • PR approval counts towards approval requirements for a specific domain.
  • Can promote fully approved Pull Requests to the develop branch.
  • Can recommend Contributors to become Domain maintainer.
  • Eligible to become an Architecture maintainer.

The process of becoming a Domain maintainer is:

  1. A Contributor requests to join corresponding Domain maintainer GitHub team.
  2. At least one specific Domain maintainers approve the request.

List of GitHub teams for Domain maintainers

GitHub team name Domain maintainers
@oneapi-src/onemkl-blas-write oneMKL Interfaces BLAS maintainers
@oneapi-src/onemkl-dft-write oneMKL Interfaces DFT maintainers
@oneapi-src/onemkl-lapack-write) oneMKL Interfaces LAPACK maintainers
@oneapi-src/onemkl-rng-write oneMKL Interfaces RNG maintainers
@oneapi-src/onemkl-sparse-write oneMKL Interfaces Sparse Algebra maintainers
@oneapi-src/onemkl-vm-write oneMKL Interfaces Vector Math maintainers

Architecture Maintainer

Architecture maintainers are the most established contributors who are responsible for the project technical direction and participate in making decisions about the strategy and priorities of the project.

Responsibilities:

  • Follow the Code of Conduct.
  • Follow and enforce the project contributing guidelines
  • Co-own with other Domain maintainers on the technical direction of a specific domain.
  • Co-own with other Architecture maintainers on the project as a whole, including determining strategy and policy for the project.
  • Support and guide Contributors and Domain maintainers.

Requirements:

  • Experience as a Domain maintainer or Contributor with focus on the project architecture for at least 12 months.
  • Commit at least 25% of working time to the project.
  • Track record of major project contributions.
  • Demonstrated deep knowledge of the project architecture and build.
  • Demonstrated broad knowledge of the project across multiple domains.
  • Is able to exercise judgment for the good of the project, independent of their employer, friends, or team.

Privileges:

  • Can represent the project in public as a Maintainer.
  • Can recommend Contributor or Domain maintainer to become Architecture maintainers.

Process of becoming a maintainer:

  1. A Contributor or Domain maintainer requests to join oneMKL Interfaces Architecture maintainers GitHub team (@oneapi-src/onemkl-arch-write).
  2. At least one of Architecture maintainers approves the request.