From dbc9bd24d7067c8b2cc6d52d32fea614dbc3a8da Mon Sep 17 00:00:00 2001 From: Walavouchey <36758269+Walavouchey@users.noreply.github.com> Date: Thu, 9 Jan 2025 22:11:52 +0100 Subject: [PATCH 1/4] move table of contents to top --- wiki/Ranking_criteria/en.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/wiki/Ranking_criteria/en.md b/wiki/Ranking_criteria/en.md index 7bd485e7ad84..320e0183a29b 100644 --- a/wiki/Ranking_criteria/en.md +++ b/wiki/Ranking_criteria/en.md @@ -5,17 +5,6 @@ This article sets rules and guidelines that [beatmaps](/wiki/Beatmap) must follo - **Rules must not be broken under any circumstance.** - **Guidelines may be ignored and broken under exceptional circumstances.** When doing so, a sufficient explanation should be provided by the mapper either upfront or when prompted during the modding process. -## Proposing changes - -Changes to any part of the ranking criteria are proposed through the [Ranking Criteria forum](https://osu.ppy.sh/community/forums/87). - -1. **Create a proposal in the [Ranking Criteria forum](https://osu.ppy.sh/community/forums/87).** Try to be as detailed as possible while explaining your idea and the change's impact. -2. **Come to a consensus.** If you think you are at that point, reach out to a member of the [NAT](/wiki/People/Nomination_Assessment_Team) to see if your proposal can be implemented. To an extent, the NAT can act as the arbiter in contentious cases, but proposals without a general consensus will likely not pass. -3. **Create a pull request on the osu!wiki GitHub repository.** Usually, this is done by a member of the NAT involved in finalising the discussion. -4. **Wait on approval from [peppy](https://osu.ppy.sh/users/2).** - -Changes that do not alter the meaning or intention of the ranking criteria, such as improvements to spelling, grammar, or organisation, may not need a forum proposal. It is still recommended to check with experienced community members that the changes are helpful and welcome. - ## Table of contents Parts of the Ranking Criteria have their own articles while still applying to all beatmaps regardless of game mode, length, or any other restrictions. @@ -44,6 +33,17 @@ In addition, each [game mode](/wiki/Game_mode) has specific ranking criteria tha - **[osu!catch](osu!catch)** - **[osu!mania](osu!mania)** +## Proposing changes + +Changes to any part of the ranking criteria are proposed through the [Ranking Criteria forum](https://osu.ppy.sh/community/forums/87). + +1. **Create a proposal in the [Ranking Criteria forum](https://osu.ppy.sh/community/forums/87).** Try to be as detailed as possible while explaining your idea and the change's impact. +2. **Come to a consensus.** If you think you are at that point, reach out to a member of the [NAT](/wiki/People/Nomination_Assessment_Team) to see if your proposal can be implemented. To an extent, the NAT can act as the arbiter in contentious cases, but proposals without a general consensus will likely not pass. +3. **Create a pull request on the osu!wiki GitHub repository.** Usually, this is done by a member of the NAT involved in finalising the discussion. +4. **Wait on approval from [peppy](https://osu.ppy.sh/users/2).** + +Changes that do not alter the meaning or intention of the ranking criteria, such as improvements to spelling, grammar, or organisation, may not need a forum proposal. It is still recommended to check with experienced community members that the changes are helpful and welcome. + ## Tools It is highly recommended that you use [Mapset Verifier (MV)](https://github.com/Naxesss/MapsetVerifier) to aid in checking these criteria. [AiMod](/wiki/Client/Beatmap_editor/AiMod) from the old client (stable) is outdated and unmaintained, and beatmap verification in [osu!(lazer)](/wiki/Client/Release_stream/Lazer) is [work in progress](https://github.com/ppy/osu/issues/12091#issuecomment-878760791). From 8e5bc6e72b4fc464eaf434db2fcad33961f6a24d Mon Sep 17 00:00:00 2001 From: Walavouchey <36758269+Walavouchey@users.noreply.github.com> Date: Thu, 9 Jan 2025 22:13:10 +0100 Subject: [PATCH 2/4] some quick clean-up --- wiki/Ranking_criteria/en.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/wiki/Ranking_criteria/en.md b/wiki/Ranking_criteria/en.md index 320e0183a29b..ad366af80733 100644 --- a/wiki/Ranking_criteria/en.md +++ b/wiki/Ranking_criteria/en.md @@ -7,7 +7,7 @@ This article sets rules and guidelines that [beatmaps](/wiki/Beatmap) must follo ## Table of contents -Parts of the Ranking Criteria have their own articles while still applying to all beatmaps regardless of game mode, length, or any other restrictions. +Parts of the ranking criteria have their own articles while still applying to all beatmaps regardless of game mode, length, or any other restrictions. ### Summary @@ -35,11 +35,11 @@ In addition, each [game mode](/wiki/Game_mode) has specific ranking criteria tha ## Proposing changes -Changes to any part of the ranking criteria are proposed through the [Ranking Criteria forum](https://osu.ppy.sh/community/forums/87). +Changes to any part of the ranking criteria are proposed through the [Ranking Criteria forum](https://osu.ppy.sh/community/forums/87). 1. **Create a proposal in the [Ranking Criteria forum](https://osu.ppy.sh/community/forums/87).** Try to be as detailed as possible while explaining your idea and the change's impact. 2. **Come to a consensus.** If you think you are at that point, reach out to a member of the [NAT](/wiki/People/Nomination_Assessment_Team) to see if your proposal can be implemented. To an extent, the NAT can act as the arbiter in contentious cases, but proposals without a general consensus will likely not pass. -3. **Create a pull request on the osu!wiki GitHub repository.** Usually, this is done by a member of the NAT involved in finalising the discussion. +3. **Create a pull request on the [osu! wiki GitHub repository](https://github.com/ppy/osu-wiki).** Usually, this is done by a member of the NAT involved in finalising the discussion. 4. **Wait on approval from [peppy](https://osu.ppy.sh/users/2).** Changes that do not alter the meaning or intention of the ranking criteria, such as improvements to spelling, grammar, or organisation, may not need a forum proposal. It is still recommended to check with experienced community members that the changes are helpful and welcome. From 3886d64b367ec3787cd5caf8db4b5033321852ed Mon Sep 17 00:00:00 2001 From: Walavouchey <36758269+Walavouchey@users.noreply.github.com> Date: Thu, 9 Jan 2025 22:23:36 +0100 Subject: [PATCH 3/4] update translations --- wiki/Ranking_criteria/es.md | 22 +++++++++++----------- wiki/Ranking_criteria/zh.md | 22 +++++++++++----------- 2 files changed, 22 insertions(+), 22 deletions(-) diff --git a/wiki/Ranking_criteria/es.md b/wiki/Ranking_criteria/es.md index b3cdb9b5c8d4..06848d602f39 100644 --- a/wiki/Ranking_criteria/es.md +++ b/wiki/Ranking_criteria/es.md @@ -5,17 +5,6 @@ Este artículo establece las reglas y pautas que los [beatmaps](/wiki/Beatmap) d - **Las reglas no deben romperse bajo ninguna circunstancia.** - **Las pautas pueden ignorarse y romperse en circunstancias excepcionales.** Al hacerlo, el mapper debe proporcionar una explicación adecuada, ya sea por adelantado o cuando se le solicite durante el proceso de modding. -## Cómo proponer cambios - -Los cambios en cualquier parte de los criterios de clasificación se proponen a través del [foro Ranking Criteria](https://osu.ppy.sh/community/forums/87). - -1. **Crea una propuesta en el [foro Ranking Criteria](https://osu.ppy.sh/community/forums/87).** Intenta ser lo más detallado posible al explicar tu idea y el impacto del cambio. -2. **Llega a un consenso.** Si crees que estás en ese punto, ponte en contacto con un miembro del [NAT](/wiki/People/Nomination_Assessment_Team) para ver si tu propuesta puede implementarse. Hasta cierto punto, el NAT puede actuar como árbitro en casos contenciosos, pero es probable que las propuestas que no cuenten con un consenso general no se aprueben. -3. **Crea una solicitud de cambios en el repositorio de la osu! wiki en GitHub.** Por lo general, esto lo hace un miembro del NAT que participa en la finalización de la discusión. -4. **Espera la aprobación de [peppy](https://osu.ppy.sh/users/2).** - -Los cambios que no alteren el significado o la intención de los criterios de clasificación, como las mejoras ortográficas, gramaticales o de organización, pueden no necesitar una propuesta en el foro. Sin embargo, es recomendable que consultes con los miembros más experimentados de la comunidad si los cambios son útiles y bienvenidos. - ## Índice Algunas partes de los criterios de clasificación tienen sus propios artículos, pero siguen aplicándose a todos los beatmaps, independientemente del modo de juego, la duración o cualquier otra restricción. @@ -44,6 +33,17 @@ Cada [modo de juego](/wiki/Game_mode) tiene criterios de clasificación específ - **[osu!catch](osu!catch)** - **[osu!mania](osu!mania)** +## Cómo proponer cambios + +Los cambios en cualquier parte de los criterios de clasificación se proponen a través del [foro Ranking Criteria](https://osu.ppy.sh/community/forums/87). + +1. **Crea una propuesta en el [foro Ranking Criteria](https://osu.ppy.sh/community/forums/87).** Intenta ser lo más detallado posible al explicar tu idea y el impacto del cambio. +2. **Llega a un consenso.** Si crees que estás en ese punto, ponte en contacto con un miembro del [NAT](/wiki/People/Nomination_Assessment_Team) para ver si tu propuesta puede implementarse. Hasta cierto punto, el NAT puede actuar como árbitro en casos contenciosos, pero es probable que las propuestas que no cuenten con un consenso general no se aprueben. +3. **Crea una solicitud de cambios en el repositorio de la osu! wiki en GitHub.** Por lo general, esto lo hace un miembro del NAT que participa en la finalización de la discusión. +4. **Espera la aprobación de [peppy](https://osu.ppy.sh/users/2).** + +Los cambios que no alteren el significado o la intención de los criterios de clasificación, como las mejoras ortográficas, gramaticales o de organización, pueden no necesitar una propuesta en el foro. Sin embargo, es recomendable que consultes con los miembros más experimentados de la comunidad si los cambios son útiles y bienvenidos. + ## Herramientas Se recomienda encarecidamente usar [Mapset Verifier (MV)](https://github.com/Naxesss/MapsetVerifier) como ayuda para comprobar estos criterios. [AiMod](/wiki/Client/Beatmap_editor/AiMod) del antiguo cliente (estable) está desactualizado y sin mantenimiento, y la verificación de beatmaps en [osu!(lazer)](/wiki/Client/Release_stream/Lazer) está [en progreso](https://github.com/ppy/osu/issues/12091#issuecomment-878760791). diff --git a/wiki/Ranking_criteria/zh.md b/wiki/Ranking_criteria/zh.md index 8f1740d42aa2..fa9413ed3c9b 100644 --- a/wiki/Ranking_criteria/zh.md +++ b/wiki/Ranking_criteria/zh.md @@ -5,17 +5,6 @@ - **任何情况下，都不允许违反规定。** - **在例外情况下，可以忽视或违反准则。** 如果这么做，谱师必须事先或者在摸图流程中提供充分的解释。 -## 提出修改 - -对于上架标准的任何修改建议，应通过[上架标准论坛](https://osu.ppy.sh/community/forums/87)提出。 - -1. **在[上架标准论坛](https://osu.ppy.sh/community/forums/87)中创建提案。** 尽量详细地解释你的新想法和修改造成的影响。 -2. **达成共识。** 如果你认为时机已经成熟，请联系[谱面审核团队 (NAT)](/wiki/People/Nomination_Assessment_Team) 的成员，来让他们决定修改提案是否可以实施。在一定程度上，NAT 可以在含有争议的情况下仲裁。但是如果提案没有达成普遍共识，则这个提案很可能无法通过。 -3. **在 osu!wiki GitHub 仓库中创建拉取请求 (PR)。** 通常，这由参与讨论并确定提案的 NAT 成员完成。 -4. **等待 [peppy](https://osu.ppy.sh/users/2) 批准。** - -如果不改变上架标准文章中的意思或意图，仅仅是修改文中的拼写、语法或组织结构时，无需发贴至上架标准论坛。但仍旧建议先咨询有经验的社区成员，来确定你的修改是否有帮助或受大家欢迎。 - ## 目录 部分上架标准有单独的文章，并且适用于所有谱面，不论游戏模式、长度或任何其他限制。 @@ -44,6 +33,17 @@ - **[osu!catch](osu!catch)** - **[osu!mania](osu!mania)** +## 提出修改 + +对于上架标准的任何修改建议，应通过[上架标准论坛](https://osu.ppy.sh/community/forums/87)提出。 + +1. **在[上架标准论坛](https://osu.ppy.sh/community/forums/87)中创建提案。** 尽量详细地解释你的新想法和修改造成的影响。 +2. **达成共识。** 如果你认为时机已经成熟，请联系[谱面审核团队 (NAT)](/wiki/People/Nomination_Assessment_Team) 的成员，来让他们决定修改提案是否可以实施。在一定程度上，NAT 可以在含有争议的情况下仲裁。但是如果提案没有达成普遍共识，则这个提案很可能无法通过。 +3. **在 osu!wiki GitHub 仓库中创建拉取请求 (PR)。** 通常，这由参与讨论并确定提案的 NAT 成员完成。 +4. **等待 [peppy](https://osu.ppy.sh/users/2) 批准。** + +如果不改变上架标准文章中的意思或意图，仅仅是修改文中的拼写、语法或组织结构时，无需发贴至上架标准论坛。但仍旧建议先咨询有经验的社区成员，来确定你的修改是否有帮助或受大家欢迎。 + ## 工具 非常推荐您使用 [Mapset Verifier (MV)](https://github.com/Naxesss/MapsetVerifier) 来辅助检查谱面是否符合上架标准。传统客户端 (stable 版) 内的 [AiMod](/wiki/Client/Beatmap_editor/AiMod) 工具已经过时且不再维护。同时，[osu!(lazer)](/wiki/Client/Release_stream/Lazer) 客户端内的谱面检查工具仍在[开发中](https://github.com/ppy/osu/issues/12091#issuecomment-878760791)。 From 7210fa5d1f9ca76af7ebf0677cd50dbf907a7374 Mon Sep 17 00:00:00 2001 From: Walavouchey <36758269+Walavouchey@users.noreply.github.com> Date: Thu, 9 Jan 2025 22:24:23 +0100 Subject: [PATCH 4/4] terminology --- wiki/Ranking_criteria/zh.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/Ranking_criteria/zh.md b/wiki/Ranking_criteria/zh.md index fa9413ed3c9b..562fd24ed193 100644 --- a/wiki/Ranking_criteria/zh.md +++ b/wiki/Ranking_criteria/zh.md @@ -39,7 +39,7 @@ 1. **在[上架标准论坛](https://osu.ppy.sh/community/forums/87)中创建提案。** 尽量详细地解释你的新想法和修改造成的影响。 2. **达成共识。** 如果你认为时机已经成熟，请联系[谱面审核团队 (NAT)](/wiki/People/Nomination_Assessment_Team) 的成员，来让他们决定修改提案是否可以实施。在一定程度上，NAT 可以在含有争议的情况下仲裁。但是如果提案没有达成普遍共识，则这个提案很可能无法通过。 -3. **在 osu!wiki GitHub 仓库中创建拉取请求 (PR)。** 通常，这由参与讨论并确定提案的 NAT 成员完成。 +3. **在 osu! wiki GitHub 仓库中创建拉取请求 (PR)。** 通常，这由参与讨论并确定提案的 NAT 成员完成。 4. **等待 [peppy](https://osu.ppy.sh/users/2) 批准。** 如果不改变上架标准文章中的意思或意图，仅仅是修改文中的拼写、语法或组织结构时，无需发贴至上架标准论坛。但仍旧建议先咨询有经验的社区成员，来确定你的修改是否有帮助或受大家欢迎。