|
| 1 | +# Introduction |
| 2 | + |
| 3 | +This document defines roles in oneMKL Interfaces project. |
| 4 | + |
| 5 | +# Roles and responsibilities |
| 6 | + |
| 7 | +oneMKL Interfaces project defines three main roles: |
| 8 | + * [Contributor](#contributor) |
| 9 | + * [Domain maintainer](#domain-maintainer) |
| 10 | + * [Architecture maintainer](#architecture-maintainer) |
| 11 | + |
| 12 | +These roles are merit based. Refer to the corresponding section for specific |
| 13 | +requirements and the nomination process. |
| 14 | + |
| 15 | +## Contributor |
| 16 | + |
| 17 | +A Contributor invests time and resources to improve oneMKL Interfaces project. |
| 18 | +Anyone can become a Contributor by bringing value in one of the following ways: |
| 19 | + * Answer questions from community members. |
| 20 | + * Submit feedback to design proposals. |
| 21 | + * Review and/or test pull requests. |
| 22 | + * Test releases and report bugs. |
| 23 | + * Contribute code, including bug fixes, features implementations, |
| 24 | +and performance optimizations. |
| 25 | + * Contribute design proposals. |
| 26 | + |
| 27 | +Responsibilities: |
| 28 | + * Follow the [Code of Conduct](CODE_OF_CONDUCT.md). |
| 29 | + * Follow the project [contributing guidelines](CONTRIBUTING.md). |
| 30 | + |
| 31 | +Privileges: |
| 32 | + * Eligible to join one of the maintainer groups. |
| 33 | + |
| 34 | +## Domain Maintainer |
| 35 | + |
| 36 | +Domain maintainer has responsibility for a specific domain in the project. |
| 37 | +Domain maintainers are collectively responsible for developing and maintaining their domain, |
| 38 | +including reviewing all changes to their domain and indicating |
| 39 | +whether those changes are ready to merge. They have a track record of |
| 40 | +contribution and review in the project. |
| 41 | + |
| 42 | +Responsibilities: |
| 43 | + * Follow the [Code of Conduct](CODE_OF_CONDUCT.md). |
| 44 | + * Follow and enforce the project [contributing guidelines](CONTRIBUTING.md). |
| 45 | + * Co-own with other domain maintainers a specific domain, including contributing |
| 46 | + bug fixes, implementing features, and answering domain specific questions |
| 47 | + in [#onemkl](https://uxlfoundation.slack.com/archives/onemkl) Slack channel. |
| 48 | + * Review pull requests in their specific domain. |
| 49 | + * Monitor testing results and flag issues in their specific areas of |
| 50 | + responsibility. |
| 51 | + * Support and guide Contributors. |
| 52 | + |
| 53 | +Requirements: |
| 54 | + * Experience as Contributor in the specific domain for at least 6 months. |
| 55 | + * Commit at least 25% of working time to the project. |
| 56 | + * Track record of accepted code contributions to a specific domain. |
| 57 | + * Track record of contributions to the code review process. |
| 58 | + * Demonstrated in-depth knowledge of the specific domain. |
| 59 | + * Commits to being responsible for that specific domain. |
| 60 | + |
| 61 | +Privileges: |
| 62 | + * PR approval counts towards approval requirements for a specific domain. |
| 63 | + * Can promote fully approved Pull Requests to the `develop` branch. |
| 64 | + * Can recommend Contributors to become Domain maintainer. |
| 65 | + * Eligible to become an Architecture maintainer. |
| 66 | + |
| 67 | +The process of becoming a Domain maintainer is: |
| 68 | +1. A Contributor requests to join corresponding Domain maintainer GitHub team. |
| 69 | +2. At least one specific Domain maintainers approve the request. |
| 70 | + |
| 71 | +### List of GitHub teams for Domain maintainers |
| 72 | + |
| 73 | +| GitHub team name | Domain maintainers | |
| 74 | +:-----------|:------------| |
| 75 | +| @oneapi-src/onemkl-blas-write | oneMKL Interfaces BLAS maintainers | |
| 76 | +| @oneapi-src/onemkl-dft-write | oneMKL Interfaces DFT maintainers | |
| 77 | +| @oneapi-src/onemkl-lapack-write) | oneMKL Interfaces LAPACK maintainers | |
| 78 | +| @oneapi-src/onemkl-rng-write | oneMKL Interfaces RNG maintainers | |
| 79 | +| @oneapi-src/onemkl-sparse-write | oneMKL Interfaces Sparse Algebra maintainers | |
| 80 | +| @oneapi-src/onemkl-vm-write | oneMKL Interfaces Vector Math maintainers | |
| 81 | + |
| 82 | +## Architecture Maintainer |
| 83 | +Architecture maintainers are the most established contributors who are responsible for the |
| 84 | +project technical direction and participate in making decisions about the |
| 85 | +strategy and priorities of the project. |
| 86 | + |
| 87 | +Responsibilities: |
| 88 | + * Follow the [Code of Conduct](CODE_OF_CONDUCT.md). |
| 89 | + * Follow and enforce the project [contributing guidelines](CONTRIBUTING.md) |
| 90 | + * Co-own with other Domain maintainers on the technical direction of a specific domain. |
| 91 | + * Co-own with other Architecture maintainers on the project as a whole, including |
| 92 | +determining strategy and policy for the project. |
| 93 | + * Support and guide Contributors and Domain maintainers. |
| 94 | + |
| 95 | +Requirements: |
| 96 | + * Experience as a Domain maintainer or Contributor with focus on the project architecture |
| 97 | +for at least 12 months. |
| 98 | + * Commit at least 25% of working time to the project. |
| 99 | + * Track record of major project contributions. |
| 100 | + * Demonstrated deep knowledge of the project architecture and build. |
| 101 | + * Demonstrated broad knowledge of the project across multiple domains. |
| 102 | + * Is able to exercise judgment for the good of the project, independent of |
| 103 | + their employer, friends, or team. |
| 104 | + |
| 105 | +Privileges: |
| 106 | + * Can represent the project in public as a Maintainer. |
| 107 | + * Can recommend Contributor or Domain maintainer to become Architecture maintainers. |
| 108 | + |
| 109 | +Process of becoming a maintainer: |
| 110 | +1. A Contributor or Domain maintainer requests to join oneMKL Interfaces Architecture maintainers GitHub team |
| 111 | +(@oneapi-src/onemkl-arch-write). |
| 112 | +2. At least one of Architecture maintainers approves the request. |
| 113 | + |
0 commit comments