Template:RfC closure review - Wikipedia
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= |closer= |closer_discussion= |notification_closure_review= |reason= }}
Meaning of each parameter
|page=: Name the article or the main page about which the RfC discussion was held. Do not use wikisyntax, just paste the plain name.|rfc_close_page=: Give the 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 RfC: Should the lead mention DJT's engagement in Jan 6?. Do not use wikisyntax, just paste the plain name.|closer=: Type the username of the closer, withoutUser:or wikisyntax.|closer_discussion=: Name the 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 User talk:Example#I am not sure the closure is correct. 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 administators' noticeboard. You may use {{subst:AN-notice}} to notify the closer. Fill in 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". View Template:RfC closure review banner for ways NOT to file a closure review and for some resources that may help you.
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=, |closer=, |closer_discussion= and |reason= parameters are required to 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.
{{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:
- Coahuila (talk|edit|history|logs|links|cache|watch) (RfC closure in question) (Discussion with closer)
- Viktor Yanukovych (talk|edit|history|logs|links|cache|watch) (RfC closure in question) (Discussion with closer)
You are wrong!