跳转到内容

Template:RfC closure review/doc

本页使用了标题或全文手工转换
维基百科,自由的百科全书

Usage

[编辑]

Always subst: this template.

Lists up to 10 pages for RfC closure review. Paste this code for the template when you want to challenge one RfC closure only:

{{subst:RfC closure review
|page=
|rfc_close_page=
|appealinguser=
|closer=
|closer_discussion=
|notification_closure_review=
|reason=
}}

Meaning of each parameter

[编辑]
  • |page=: Article or the main page about which the RfC discussion was held. Do not use wikisyntax, just paste the plain name.
  • |rfc_close_page=: Full path to the discussion that you can copy from your URL after /wiki/ (eg. Talk:Donald Trump#RfC: Should the lead mention DJT's engagement in Jan 6? and not simply Template:!tq. Do not use wikisyntax, just paste the plain name.
  • |appealinguser=: Your username, without User: or wikisyntax. You will not need to sign your edit with ~~~~.
  • |closer=: Username of the closer, without User: or wikisyntax.
  • |closer_discussion=: Heading on the user's talk page where you voiced your concerns about their closure (eg. I am not sure the closure is correct and not Template:!tq. Do not use any wikisyntax.
  • |notification_closure_review=: A diff, link to the diff or link to the section where you notified the user of the discussion that is going to happen at the administrators' noticeboard. You may use {{subst:AN-notice}} to notify the closer. Fill in immediately after filing this request for closure review.
  • |reason=: Explain in a neutral way why you want the community to review the closure. You should give a concrete description of how the closure did not interpret consensus correctly, violated or disregarded relevant policies and guidelines, or ignored some of the users' arguments. You are more likely to succeed in your AN request if you focus on 1. an "underlying policy/guideline" and 2. "strength of argument".

For each subsequent page you want to challenge, paste |pageX= and |rfc_close_pageX= to the template. |page1= is the second page you want to review, |page2= is the third page, |page3= is the fourth page and so on until |page9=.

|page=, |rfc_close_page=, |appealinguser=, |closer=, |closer_discussion= and |reason= parameters are required to properly deploy this template. If you fail to fill |closer_discussion= or |notification_closure_review=, you will see error messages urging that the discussion be closed immediately.

When

  • |closer= < closer's username > and
  • |closer_discussion= < section header on closer's talk page where there was discussion about the close >

are correctly filled in, the result will include a "Discussion with closer" link to that discussion.

If the "Discussion with closer" link lands at the TOP of the closer's talk page, then the closer's talk-page archives should be checked for the post-close discussion.

Example

[编辑]

{{Subst:RfC closure review |page=Coahuila |page1=Viktor Yanukovych |rfc_close_page = Huh? |closer=Example user |closer_discussion=Example header |reason=You are wrong! }}

will yield this:

RfC closure review request at Huh?

[编辑]
Coahuila (討論|編輯|歷史|日誌|鏈入|快取|監視) (受覆核的RfC關閉) (Discussion with closer)
Viktor Yanukovych (討論|編輯|歷史|日誌|鏈入|快取|監視) (受覆核的RfC關閉) (Discussion with closer)

Closer: Example user (討論 · 貢獻 · 刪除貢獻 · 日誌 · 過濾器日誌 · 封禁 · 封禁日誌)

User requesting review: Sekidoki (討論 · 貢獻 · 刪除貢獻 · 日誌 · 過濾器日誌 · 封禁 · 封禁日誌). Posted at 09:11, 21 February 2025 (UTC)

Notified: WARNING: THIS RFC CLOSURE REVIEW IS INVALID; CLOSER WAS NOT NOTIFIED OF THE DISCUSSION. GIVE SOME TIME FOR THE EDITOR REQUESTING REVIEW TO NOTIFY THE CLOSER. IF THEY DO NOT DO THAT IN A REASONABLE TIME, YOU SHOULD SHUT DOWN THIS REQUEST.

Reasoning: You are wrong!

Closer (Sekidoki)

[编辑]

Non-Participants

[编辑]

Participants

[编辑]

Discussion

[编辑]

See also

[编辑]

{{RfC closure review links}}