jellyfin/jellyfin-meta
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin-meta.git synced 2024-11-23 05:59:49 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #14 from thornbill/team-formatting

Browse Source 
Fix formatting for team nomination
This commit is contained in:
Joshua M. Boniface 2021-01-22 13:04:33 -05:00 committed by GitHub
commit 682724c9ea
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
policies-and-procedures/new-team-member-nominations.md
View File

@ -10,10 +10,13 @@ This document outlines the steps that should be taken to nominate and accept a n
1. Nominations should reflect the following 4 goals:
a) Nominees should demonstrate a consistent, high-quality contribution to the project, e.g. in supporting users, contributing good code, or making & improving clients. While a specific threshold of contributions is not always possible, the nominee should have displayed at least several notable acts, and at least a few successfully merged pull requests or comparable activity in other places.
b) Nominees should demonstrate respect for our values, a commitment to FLOSS development and a desire to see Jellyfin succeed.
c) Nominees should be in good standing with the team and community and respect for the rules and community guidelines of the project.
d) Nominees should be willing to contribute to the more mundane tasks (e.g. PR reviews) if they have not already demonstrated a desire to do so - with power comes responsibility.
a) Nominees should demonstrate a consistent, high-quality contribution to the project, e.g. in supporting users, contributing good code, or making & improving clients. While a specific threshold of contributions is not always possible, the nominee should have displayed at least several notable acts, and at least a few successfully merged pull requests or comparable activity in other places.
b) Nominees should demonstrate respect for our values, a commitment to FLOSS development and a desire to see Jellyfin succeed.
c) Nominees should be in good standing with the team and community and respect for the rules and community guidelines of the project.
d) Nominees should be willing to contribute to the more mundane tasks (e.g. PR reviews) if they have not already demonstrated a desire to do so - with power comes responsibility.
1. Once a contributor has selected a nominee, the issue should be put to a discussion in #jellyfin-support-team. At least one Core team member should approve the decision, though this may be waived with overwhelming team support (barring blatant violations of the conditions of #2). Please include details of why this nominee and what you think they bring to the team.