c1e40bb3d5
prefix with numbers to get sorting based on usage. Most common files issue types should come first, with bugs being at the top. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
43 lines
1.3 KiB
Markdown
43 lines
1.3 KiB
Markdown
---
|
|
name: Contributor Nomination
|
|
about: Nominate a GitHub user for additional rights on the Zephyr Project
|
|
title: ''
|
|
labels: Role Nomination
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
# Background
|
|
|
|
The [TSC Project Roles] defines the main roles for the Zephyr Project, including
|
|
Maintainer, Collaborator, and Contributor.
|
|
|
|
By default anyone that contributes code or documentation is a Contributor, but
|
|
with the lowest [GitHub Permission Level] of Read. For example, Contributors
|
|
with Read permission do not have the permission to add reviewers to a pull
|
|
request.
|
|
|
|
Use this template to nominate a GitHub user for the Contributor role with
|
|
Triage permission level, which allows the user to add reviewers to a pull
|
|
request and be added as a reviewer by other users.
|
|
|
|
# Nomination
|
|
|
|
## GitHub User
|
|
|
|
Provide the following information about the GitHub user:
|
|
|
|
1. Full Name
|
|
1. GitHub username
|
|
1. Organization (optional)
|
|
|
|
## Supporting Documents
|
|
|
|
Add links to 3-5 GitHub pull requests, in the Zephyr project, authored or
|
|
reviewed by the GitHub user that demonstrate the user's dedication to the
|
|
Zephyr project.
|
|
|
|
|
|
[TSC Project Roles]: <https://docs.zephyrproject.org/latest/project/project_roles.html>
|
|
[GitHub Permission Level]: <https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization>
|