Improve Beatmap_ranking_procedure and Beatmap_ranking_procedure/Ranking_queue

[SisypheOvO]

Main Changes:

• The two articles improved. Details:
  • Beatmap_ranking_procedure:
    • Added two See also for readers to better understand two frequently mentioned concept below Article Title.
    • Improved how "how many nominations are needed for qualification" is explained with article content and Notes at the bottom.
    • Moved things unrelated to "Qualification" to right places ( e.g. things about DQ changing the rank timer are moved to /Ranking_queue, things about problems are moved to #nomination-resets, things about "qua to rank" are moved to #rank )
    • This article is about all "moments" through out the ranking process. So the Nomination reset/DQ/Veto moments need to be clarified. Explained quality assurance as a target for the Qualified category.
    • The Nomination resets part is improved: tell what it is and then what it ensures. Also improved explanation in more details.
    • Created a sub -ection for briefly explaining veto.
    • Changed #ranked to #rank to emphasize it as a process.
    • Added more Wiki links for readers to click for more information.
  • Beatmap_ranking_procedure/Ranking_queue:
    • Things about DQ changing the rank timer are moved here from Beatmap_ranking_procedure
    • Explain clearly how the qualified time works counting down for the beatmaps to get ranked.

Other Changes:

• Fixed links pointing to Beatmap_ranking_procedure#ranked which is changed to #rank by me.
• Improved Beatmap/Category slightly: nominations needed to qualify a map need clarification.

[osu-wiki-observatory]

Someone else has edited same files as you did. Please check their changes in case they conflict with yours:

• Implement multiple osu!taiko ranking criteria proposals #13958, files:
  • wiki/Ranking_criteria/Simplified_ranking_criteria/en.md

[github-actions]

Thank you for contributing to the osu! wiki.

Please take note of the following:

• Make sure you've read this self-check checklist.

• Translations that have not been reviewed by a native speaker will be merged after a minimum of 1 week. If there are no reviewers for your language, please mention it explicitly.

• Refrain from spamming the Update branch button. A maintainer will do this before merging anyway.

• Apply review suggestions in batches from the Files changed tab like this:

  

See the contribution guide for more information.

All changes are run through continuous integration checks, which provide automatic detection of common errors. If you need help with decrypting CI check error messages, or with any other issues, ask in the #osu-wiki channel on the osu! Discord server.

[SisypheOvO]

Reminder: articles that are changed alot need their translations edited as"outdated-translation" and give the commit hash😌

[Hiviexd]

manually outdating translations is no longer needed and is automated, so no need to worry about it.

[SisypheOvO]

manually outdating translations is no longer needed and is automated, so no need to worry about it.

ok thanks for that info! I learnt that from commits from like four years ago sorry abou that 🥲

[peppy]

Seems fine? Would want a second opinion though.

[MChecaH]

Think the changes are neat, and probably update some of the "technical debt" built up by changing some parts of the wiki while leaving other similar ones unchanged. This brings all of those articles somewhat all in line with each other. Giving it one last look before pushing, but all in all the direction taken is A-Okay.

[MChecaH]

First pass.

[SisypheOvO]

Think the changes are neat, and probably update some of the "technical debt" built up by changing some parts of the wiki while leaving other similar ones unchanged. This brings all of those articles somewhat all in line with each other. Giving it one last look before pushing, but all in all the direction taken is A-Okay.

sorry for the late reply.. Im currently busy but i will check out soon !!

[MChecaH]

Believe this is good to go. @Hiviexd Pulling you in, in case there's anything more to add.

[MChecaH]

Reminder to remove ..._OUTDATED_... from the PR. This update should definitely out-date all modified articles.

[SisypheOvO]

@Hiviexd Can I make a little further change to this?

I want to

1. add a thing to ranking queue: stamps in discussion will not stop the timer.
2. move the first sentence in the third section of # Beatmap ranking queue to the second section, making it smoother to read and understand.

things after will go like this:

# Beatmap ranking queue

The **ranking queue** manages blablabla blablabla

A timer of 7 days is set when a beatmap enters Qualified. It counts how many days a beatmap should stay in Qualified before it can be ranked. When the timer of a beatmap reaches zero, it is eligible to be ranked on that day. The exact time of day that beatmaps get ranked is random.

Problem/Suggestion stamps posted under a beatmap's discussion page will not stop the timer from counting down, but will stop beatmaps from being ranked after the timer reaches zero in 7 days and pause. Once all problems and suggestions are resolved, the beatmap will be able to continue ranking. Additionally, beatmaps may went through [disqualification](/wiki/Beatmap_ranking_procedure#nomination-resets) if issues are found and need to be addressed, which may change the timer.

it was before like this to compare:

# Beatmap ranking queue

The **ranking queue** manages blablabla blablabla

A timer counts how many days a beatmap should stay in Qualified before it can be ranked. When the timer of a beatmap reaches zero, it is eligible to be ranked on that day. The exact time of day that beatmaps get ranked is random.

7 days is the default waiting time that is set when a beatmap enters Qualified. But beatmaps may be [disqualified](/wiki/Beatmap_ranking_procedure#nomination-resets) if issues are found during their time in Qualified, which may change the timer.

[Hiviexd]

@Hiviexd Can I make a little further change to this?

changes sound good, go ahead

[SisypheOvO]

changes sound good, go ahead

may need a recheck. Thanks alot

[MChecaH]

New changes look good.