Defining developer roles, responsibilities, and privileges and leadership process

MAINTAINERS.md

@@ -1,6 +1,129 @@
 # Introduction
 
-This document provides a list of the maintainers for each area of development in the oneDPL project.
+This document defines the roles available in the oneDPL project and provides a list of the
+[current maintainers](Current Maintainers) for each area of development in oneDPL. The document also defines the
+process for maintainers to [Leave the Role](leave the role) in the project.
+
+# Roles and Responsibilities
+
+The oneDPL project defines three primary roles:
+* [Contributor](#contributor)
+* [Code Owner](#codeowner)
+* [Maintainer](#maintainer)
+
+[permissions]: https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization#permissions-for-each-role
+
+|                                                                                                                                             |       Contributor       |       Code Owner        |       Maintainer        |
+| :------------------------------------------------------------------------------------------------------------------------------------------ | :---------------------: | :---------------------: | :---------------------: |
+| _Responsibilities_                                                                                                                          |                         |                         |                         |
+| Follow the Code of Conduct                                                                                                                  |            ✓            |            ✓           |            ✓            |
+| Follow Contribution Guidelines                                                                                                              |            ✓            |            ✓           |            ✓            |
+| Enforce Contribution Guidelines                                                                                                             |            ✗            |            ✓           |            ✓            |
+| Co-own component or aspect of the library,<br>  including contributing: bug fixes, implementing features,<br> and performance optimizations |            ✗            |            ✓           |            ✓            |
+| Co-own on technical direction of component or<br> aspect of the library                                                                     |            ✗            |            ✗           |            ✓            |
+| Co-own the project as a whole,<br> including determining strategy and policy for the project                                                |            ✗            |            ✗           |            ✓            |
+| _Privileges_                                                                                                                                |                         |                         |                         |
+| Permission granted                                                                                                                          |   [Read][permissions]   |   [Write][permissions]  | [Maintain][permissions] |
+| Eligible to become                                                                                                                          |       Code Owner        |       Maintainer        |            ✗            |
+| Can recommend Contributors<br> to become Code Owner                                                                                         |            ✗            |            ✓           |            ✓            |
+| Can participate in promotions of<br> Code Owners and  Maintainers                                                                           |            ✗            |            ✗           |            ✓            |
+| Can suggest Milestones during planning                                                                                                      |            ✓            |            ✓           |            ✓            |
+| Can choose Milestones for specific component                                                                                                |            ✗            |            ✓           |            ✓            |
+| Choose project's Milestones during planning                                                                                                 |            ✗            |            ✗           |            ✓            |
+| Can propose new RFC or<br> participate in review of existing RFC                                                                            |            ✓            |            ✓           |            ✓            |
+| Can request rework of RFCs<br> in represented area of responsibility                                                                        |            ✗            |            ✓           |            ✓            |
+| Can request rework of RFCs<br> in any part of the project                                                                                   |            ✗            |            ✗           |            ✓            |
+| Can manage release process of the project                                                                                                   |            ✗            |            ✗           |            ✓            |
+| Can represent the project in public as a Maintainer                                                                                         |            ✗            |            ✗           |            ✓            |
+
+These roles are merit based. Refer to the corresponding section for specific
+requirements and the nomination process.
+
+## Contributor
+
+A Contributor can invest their time and resources in several different ways to improve oneDPL
+* Answering questions from community members in Discussions on Issues
+* Providing feedback on RFC pull requests and Discussions
+* Reviewing and/or testing pull requests
+* Contribute code, including bug fixes, new examples of oneDPL use, and new feature implementations
+* Contribute design proposals as RFCs
+
+Responsibilities:
+* Follow the [Code of Conduct](CODE_OF_CONDUCT.md)
+* Submit issues, feature requests, and code in accordance with the [Contribution Guidelines](CONTRIBUTING.md)
+
+Privileges:
+* Code contributions recognized in the oneDPL [credits](CREDITS.txt)
+* Eligible to become a Code Owner
+* Read permissions granted to the repository
+* Can suggest Milestones during planning
+
+## Code Owner
+
+A Code Owner is an established contributor that is recognized by active code owners and maintaininers as capable of
+taking on additional activities and the responsibilities and privileges that come with them. A Code Owner is
+responsible for a specific oneDPL component or functional area of the project. Code Owners are collectively responsible,
+with other Code Owners, for developing and maintaining their component or functional areas, including reviewing all
+changes to the corresponding areas of responsibility and indicating whether those changes are ready to be merged. Code
+Owners have a track record of code contribution and reviews in the project.
+
+Requirements:
+* Track record of accepted code contributions to a specific project component.
+* Track record of contributions to the code review process.
+* Demonstrated in-depth knowledge of the architecture of a specific project
+  component.
+* Commits to being responsible for that specific area.
+* Can propose new RFC or participate in review of existing RFCs
+
+Responsibilities in addition to those of Contributors:
+* Enforce the Contribution Guidelines
+* Co-own a component or aspect of the repository, including contributing bug fixes, implementing features, and performance optimizations
+
+Privileges:
+* Eligible to become a Maintainer
+* Write permissions granted to the repository
+* Can recommend Contributors to become Code Owners
+* Can suggest Milestones during planning
+* Can chose Milestones for a specific component
+* Can propose new RFC or participate in review of existing RFCs
+
+The process of becoming a Code Owner is:
+1. A Contributor is nominated by opening a PR modifying the MAINTAINERS.md file including name, Github username, and
+affiliation.
+2. At least two specific component Maintainers approve the PR.
+3. MAINTAINERS.md file is updated to represent corresponding areas of responsibility.
+
+## Maintainer
+
+A Maintainer is one of the most established contributors who are responsible for the project technical direction and
+participate in making decisions about strategy and priorities of the project.
+
+Requirements:
+  * Experience as a Code Owner.
+  * Track record of major project contributions to a specific project component.
+  * Demonstrated deep knowledge of a specific project component.
+  * Demonstrated broad knowledge of the project across multiple areas.
+  * Commits to using privileges responsibly for the good of the project.
+  * Is able to exercise judgment for the good of the project, independent of
+    their employer, friends, or team.
+
+Responsibilities in additionto those of Code Owners:
+* Co-own the technical direction of a component or aspect of the library
+* Co-own the project as a whole, including determining strategy and policy for the project
+
+Privileges:
+* Maintain permissions granted to the repository
+* Can participate in promotions of Code Owners and Maintainers
+* Choose project's Milestones during planning
+* Can request rework of RFCs in any part of the project
+* Can manage release process of the project
+* Can represent the project in public as a Maintainer
+
+## Code Owners
+
+There are currently no Code Owners identified for oneDPL.
+
+## Current Maintainers
 
 | Feature               | Maintainer          | Github ID |
 | --------------------- | ------------------- | -------- |
@@ -15,3 +138,9 @@ This document provides a list of the maintainers for each area of development in
 | Random Number Generators | Pavel Dyakov | @paveldyakov |
 | Dynamic Selection API | Anuya Welling | @AnuyaWelling2801 |
 | Kernel Templates API | Sergey Kopienko<br>Dmitriy Sobolev | @SergeyKopienko<br>@dmitriy-sobolev |
+
+## Leaving the Role of Code Owner or Maintainer
+
+Active code owners and maintainers of the oneDPL project may leave their current role by submitting a PR removing their
+name from the list of current maintainers or code owners and tagging two or more active maintainers to review and
+approve the PR.