Merge pull request ppy#10652 from Hiviexd/nat-simplifications

Update various BN/NAT articles

wiki/People/Beatmap_Nominators/Becoming_a_Beatmap_Nominator/en.md

@@ -10,7 +10,7 @@ Applicants are required to meet a minimum [kudosu](/wiki/Modding/Kudosu) thresho
 
 Modders aiming to apply to the Beatmap Nominators must fulfil the following criteria:
 
-- They have accumulated at least 200 [kudosu](/wiki/Modding/Kudosu) for [osu!](/wiki/Game_mode/osu!) modders, or 150 kudosu for [osu!taiko](/wiki/Game_mode/osu!taiko)/[osu!catch](/wiki/Game_mode/osu!catch)/[osu!mania](/wiki/Game_mode/osu!mania) modders.
+- They have accumulated at least 150 [kudosu](/wiki/Modding/Kudosu).
 - They provide 3 of their mods which they think qualify them to be a part of the Beatmap Nominators.
   - Previous members of BN/NAT are allowed to submit a minimum of 2 mods for their application.
 
@@ -82,30 +82,27 @@ Depending on your status, the cooldown before you can apply again may vary.
 
 ### Failed applications
 
-You have these requirements if you failed a Beatmap Nominator application and apply again.
+If you failed a Beatmap Nominator application, you will be subjected to one of the following cooldowns before you can apply again:
 
-| Type | Cooldown |
-| :-- | :-- |
-| Standard | 90 days |
-| Reduced | 45–60 days |
-| Failed the [Beatmap Nominator Test](/wiki/People/Beatmap_Nominators/Beatmap_Nominator_Test) | 30 days |
-
-The cooldown may be reduced for applicants with relatively few issues they need to work on before becoming a Beatmap Nominator.
+| Type | Cooldown | Usage |
+| :-- | :-- | :-- |
+| Reduced | 30 days | Applications with relatively few issues, or [Beatmap Nominator Test](/wiki/People/Beatmap_Nominators/Beatmap_Nominator_Test) fails |
+| Standard | 60 days | Normal fails |
+| Extended | 120 days | Applicants with major behaviour concerns |
 
 ### Rejoining after being removed from the Beatmap Nominators
 
-Users who have recently left the Beatmap Nominators may have different requirements to rejoin compared to when they first joined. For users who have performed well prior to leaving, they may be able to rejoin with relaxed requirements, or no requirements at all. The NAT will inform the user if they have the opportunity to fast-track their way back into the Beatmap Nominators.
+Users who have recently left the Beatmap Nominators may have different requirements to rejoin compared to when they first joined. For users who have performed well prior to leaving, they may be able to rejoin with no requirements at all for a period of time. The NAT will inform the user if they have the opportunity to fast-track their way back into the Beatmap Nominators.
 
-If you were a Beatmap Nominator before, these requirements apply unless you have failed an application since last time you were a Beatmap Nominator.
+If you were a Beatmap Nominator before, the following requirements apply unless you have failed an application since last time you were a Beatmap Nominator:
 
-| Type | Cooldown | Activity Requirements |
+| Type | Cooldown | Application process |
 | :-- | :-- | :-- |
-| Standard | 60 days | *None* |
-| Activity | 30 days | 8 mods in 60 days |
-| Good | 30 days | *None* |
-
-The 8-mod requirement for those applying after being removed for activity is shared across all modes.
+| Good | *None* | *None*[^good-terms] |
+| Standard | 60 days | Normal |
+| Activity | *None* | Normal[^activity-terms] |
 
-Former beatmap nominators who resigned on good terms within the past 6 months are given the option to instantly request a rejoin as a full member, without having to take the [Beatmap Nominator Test](/wiki/People/Beatmap_Nominators/Beatmap_Nominator_Test), nor provide mods for evaluation.
+## Notes
 
-Former Beatmap Nominators who resigned on good terms within the past year still have to reapply properly in order to rejoin, and they will become full members immediately upon getting accepted.
+[^good-terms]: A Beatmap Nominator who resigned on good terms will be treated with standard terms after 1 year.
+[^activity-terms]: Applicants will have to provide 3 mods in applications, instead of at least 2.

wiki/People/Beatmap_Nominators/Becoming_a_Beatmap_Nominator/ru.md

@@ -1,3 +1,8 @@
+---
+outdated_translation: true
+outdated_since: 7f3d36e6b49bb725e7322e516a47fedfb186fb6c
+---
+
 # Как стать номинатором
 
 За зачисление в [номинаторы](/wiki/People/Beatmap_Nominators) отвечает [команда оценки номинаций](/wiki/People/Nomination_Assessment_Team) (NAT).

wiki/People/Beatmap_Nominators/Becoming_a_Beatmap_Nominator/zh.md

@@ -1,3 +1,8 @@
+---
+outdated_translation: true
+outdated_since: 7f3d36e6b49bb725e7322e516a47fedfb186fb6c
+---
+
 # 成为 BN
 
 想要加入[谱面审核团队 (BN)](/wiki/People/Beatmap_Nominators) 的玩家需要在[审核评估团队 (NAT)](/wiki/People/Nomination_Assessment_Team) 成员的监管下通过 BN 申请程序。

wiki/People/Beatmap_Nominators/Rules/en.md

@@ -40,13 +40,6 @@ Each mode has its own required minimum for monthly activity.
 | osu!catch, osu!mania[^multi-key-mode] | 2 nominations |
 | Hybrid | 3 nominations, with at least 1 per proficient game mode |
 
-Probationary Beatmap Nominators are expected to meet different activity requirements in order to better showcase their capabilities to the NAT, and if they fail to do so in their first month of probation, their probation will automatically be extended by another month in order to allow them to meet said requirements.
-
-| Game mode | Requirement |
-| :-- | :-- |
-| osu, osu!taiko | 6 nominations |
-| osu!catch, osu!mania[^multi-key-mode] | 4 nominations |
-
 ## Nomination
 
 - **Do not nominate beatmaps with unrankable issues.** The [General Ranking Criteria](/wiki/Ranking_criteria) and additionally all mode-specific Ranking Criteria apply to all sets with mode-specific difficulties.

wiki/People/Beatmap_Nominators/Rules/fr.md

@@ -44,13 +44,6 @@ Chaque mode a son propre minimum requis pour l'activité mensuelle.
 | osu!catch, osu!mania[^mode-multi-key] | 2 nominations |
 | Hybride | 3 nominations, dont au moins 1 par mode de jeu compétent |
 
-Les Probationary Beatmap Nominators sont censés satisfaire à différentes exigences en matière d'activités afin de mieux présenter leurs capacités à la NAT. S'ils n'y parviennent pas au cours de leur premier mois de probation, leur période probatoire sera automatiquement prolongée d'un mois afin de leur permettre de satisfaire aux exigences en question.
-
-| Mode de jeu | Exigence |
-| :-- | :-- |
-| osu, osu!taiko | 6 nominations |
-| osu!catch, osu!mania[^mode-multi-key] | 4 nominations |
-
 ## Nomination
 
 - **Ne nominez pas des beatmaps dont les problèmes ne sont pas classables.** Les [critères de classement généraux](/wiki/Ranking_criteria) et tous les critères de classement spécifiques à un mode s'appliquent à tous les sets dont les difficultés sont spécifiques à un mode.

wiki/People/Nomination_Assessment_Team/Evaluations/en.md

@@ -18,11 +18,11 @@ Every BN is reviewed regularly by members of the NAT.
 
 For Nominators on [probation](/wiki/People/Beatmap_Nominators#probationary-beatmap-nominators), or that have been issued an [activity](/wiki/People/Beatmap_Nominators/Rules#activity) warning, their next evaluation will be scheduled for roughly 1 month after being placed on probation or receiving their warning.
 
-For full Beatmap Nominators without recent warnings, their evaluations will be scheduled to occur every 3 months. If a Beatmap Nominator has passed 2 evaluations in a row without any issues, their evaluations get scheduled every 6 months instead. Any warning will reset the evaluation period back to every 3 months.
+For full Beatmap Nominators without recent warnings, their evaluations will be scheduled to occur every 3 months.
 
 The duration between evaluations is automatically scheduled by the [BN website](https://bn.mappersguild.com/). However, if there is a substantial cause for concern about a BN's performance at a sooner date, NAT members can also manually schedule an evaluation to happen sooner than normal.
 
-Just like applications, current BN evaluations are randomly assigned to 2–3 evaluators and will be announced in the respective mode's NAT Discord channels.
+Just like applications, current BN evaluations are randomly assigned to 3 evaluators and will be announced in the respective mode's NAT Discord channels.
 
 ### Individual phase
 
@@ -42,7 +42,7 @@ Warnings and being placed on probation due to subpar performance as a full Beatm
 
 Each Beatmap Nominator's activity is checked automatically by the BN website on the 1st of every month. If it has found that there are nominators not meeting the activity requirements, they will be flagged and posted in their respective mode's NAT channel for NAT members to review by the "bnsite" Discord bot. Review will include whether the BN has posted an absence notice recently, and a double check to ensure the website check is accurate to the BN's activity status.
 
-If it is found the BN is indeed not meeting activity, they will be either warned or removed depending on severity. Beatmap Nominators who were removed for activity in this way may apply again in 30 days, provided they have at least 8 mods to show they have come back to being active as a modder again.
+If it is found the BN is indeed not meeting activity, they will be either warned or removed depending on severity. Beatmap Nominators who were removed for activity in this way may apply again without any cooldowns, provided they apply with 3 mods instead of 2 to show they have come back to being active as a modder again.
 
 ### Resignations
 

wiki/People/Nomination_Assessment_Team/en.md

@@ -5,7 +5,7 @@ tags:
 
 # Nomination Assessment Team
 
-*See also: [Beatmap Nominator evaluations](Evaluations), [SEV rating](SEV_rating)*
+*See also: [Beatmap Nominator evaluations](Evaluations)*
 
 The **Nomination Assessment Team** (***NAT***) is a team that moderates the [Beatmap Nominators](/wiki/People/Beatmap_Nominators) (*BN*) and ensures the beatmapping side of osu! stays functional.
 
@@ -39,7 +39,7 @@ NAT members assigned to the structural category are not responsible for any spec
 - **Miscellaneous maintenance**: Included but not limited to:
   - Handling [vetoes](/wiki/People/Beatmap_Nominators/Beatmap_Veto).
   - Maintaining the [RC Test](/wiki/People/Beatmap_Nominators/Beatmap_Nominator_Test).
-  - Judging nomination reset [severity](SEV_rating).
+  - Judging impact of nomination resets.[^impact-rating]
 
 NAT members who are primarily handling this category make sure that BNs and other members of the mapping/modding community remain informed and feel heard, in addition to maintaining the components required to keep everything running in the mapping/modding scene. Users belonging to this category are made up of experienced evaluators that prefer to focus on managerial matters regarding the mapping/modding scene.
 
@@ -142,7 +142,6 @@ The [Nomination Assessment Team group page](https://osu.ppy.sh/groups/7) lists a
 | ::{ flag=US }:: [Noffy](https://osu.ppy.sh/users/1541323) |  |
 | ::{ flag=HK }:: [Petal](https://osu.ppy.sh/users/7354729) | Cantonese, Chinese |
 | ::{ flag=CN }:: [Ryuusei Aika](https://osu.ppy.sh/users/7777875) | Chinese |
-| ::{ flag=US }:: [StarCastler](https://osu.ppy.sh/users/12402453) |  |
 | ::{ flag=CL }:: [Uberzolik](https://osu.ppy.sh/users/1314547) | Spanish, French |
 | ::{ flag=BE }:: [yaspo](https://osu.ppy.sh/users/4945926) | Dutch |
 
@@ -189,16 +188,19 @@ The following NAT members are primarily evaluators, but also contribute to struc
 | User | Task |
 | :-- | :-- |
 | ::{ flag=BR }:: [Dada](https://osu.ppy.sh/users/9119507) | BN Mentorship organisation |
-| ::{ flag=DE }:: [FuJu](https://osu.ppy.sh/users/10773882) | Handling user reports and osu! [SEV ratings](/wiki/People/Nomination_Assessment_Team/SEV_rating) |
+| ::{ flag=DE }:: [FuJu](https://osu.ppy.sh/users/10773882) | Handling user reports |
 | ::{ flag=CN }:: [Garden](https://osu.ppy.sh/users/2849992) | Handling content reports |
 | ::{ flag=NL }:: [Greaper](https://osu.ppy.sh/users/2369776) | [Nomination Planner](https://bnplanner.greaper.net/beatmaps) and [osu!catch MV plugin](https://github.com/Darius-Wattimena/MapsetChecksCatch) development |
 | ::{ flag=TN }:: [Hivie](https://osu.ppy.sh/users/14102976) | NAT Leadership, [BN Management website](https://bn.mappersguild.com) and [osu!taiko MV plugin](https://github.com/Hiviexd/MVTaikoChecks) development |
 | ::{ flag=US }:: [Noffy](https://osu.ppy.sh/users/1541323) | BN events organisation |
 | ::{ flag=ES }:: [RandomeLoL](https://osu.ppy.sh/users/7080063) | [osu!mania MV plugin](https://github.com/MChecaH/ManiaCheck) development |
-| ::{ flag=US }:: [StarCastler](https://osu.ppy.sh/users/12402453) | [Ranking criteria test](/wiki/People/Beatmap_Nominators/Beatmap_Nominator_Test) maintenance |
 | ::{ flag=DK }:: [Tailsdk](https://osu.ppy.sh/users/6751666) | [osu!mania MV plugin](https://github.com/MChecaH/ManiaCheck) development |
 | ::{ flag=BE }:: [yaspo](https://osu.ppy.sh/users/4945926) | Handling user reports |
 
 ---
 
 In addition, the [Nomination Assessment Team bot](https://osu.ppy.sh/users/6616586) acts as a proxy for the NAT to collectively deliver messages under one user account without directly attributing them to anyone. It may be used for evaluation responses, mock evaluations, mediations, reports, and content reviews, along any other miscellaneous purposes.
+
+## Notes
+
+[^impact-rating]: This process involves checking each nomination reset and assigning it a "minor" or "notable" label for future reference in evaluations.

wiki/People/Nomination_Assessment_Team/es.md

@@ -1,4 +1,6 @@
 ---
+outdated_translation: true
+outdated_since: d42b79173c261bb7282e3a7e7c86ba5ccff7c749
 tags:
   - NAT
 ---