Talk:Average directional movement index

The following discussion is an archived discussion of a

requested move

. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the move request was: Await Arbcom decision before proceeding with this debate. Since almost all participants below are mentioned in the arbcom case, solving this issue first is a pre-requesite to this discussion. Graeme Bartlett (talk) 11:13, 18 February 2012 (UTC) Graeme Bartlett (talk) 11:13, 18 February 2012 (UTC)[reply]

• Process objection – this is not a good time or a good process for dealing with this. The page was stable enough at lower case when Amatulic moved it back and protected it (a violation of
  WP:TITLE and me and Tony, in which he seeks an exception for technical market indicators. It would be best to put things back for now and consider an RM after that case settles out. Dicklyon (talk) 20:49, 3 February 2012 (UTC)[reply
  ]

  It was also stable enough in uppercase until Dicklyon moved it, in spite of knowing it would be contentious. Other editors besides me (including a respected expert in the field) disagrees with the MOS:CAPS promoters named in the ArbCom case regarding that guideline's application to technical analysis articles. I fully agree, this is not a good time for continuing to move such articles to lowercase, seeing that an ArbCom case involving DickLyon, not me, is pending (I merely volunteered a comment), so why continue beating this horse when it has already been well established that such moves are contentious? Please

  talk) 21:03, 3 February 2012 (UTC)[reply

  ]

As I've pointed out on your talk page, your flagrant breach of

wp:admin policy is the issue, not the casing of the title. When are you going to unprotect it and ask an uninvolved admin to look into the matter? Tony (talk) 02:01, 4 February 2012 (UTC)[reply

]

You are wrong. Preventing disruption is the job of an admin, and your insistence on unprotection suggests that you intend to continue your disruptive activity even after being aware of the controversial nature of your renamings. The capitalization is the issue here in light of the disruptive renaming you and DickLyon have engaged in. The article is unprotected now that this discussion has been initiated — which is something I should not have had to do; you should have done that in the first place. ~

talk) 04:38, 4 February 2012 (UTC)[reply

]

Yes, preventing disruption is the job of admins. But not you, in this case, since you are involved (involved up to your ears, actually). I'm concerned that you don't seem to have understood this basic tenet of admin policy. If you want me to explain it, I will. If you persist, the matter might have to be taken elsewhere. You should not have the tools if you're going to wilfully misuse them—that is, to act administratively while you're involved in the article and/or issue in question. The simple thing is to undo the admin action and ask another, uninvolved admin to review the matter. I'm surprised you don't understand this. Tony (talk) 07:23, 4 February 2012 (UTC) Ah, I see from your talk page, of all places, that you have undone the policy-breaching action. Please do not do this kind of thing again. And for the record, I don't give a fig about the article title—that's for the community to decide. I just care that you understand how to be a good admin. Tony (talk) 07:28, 4 February 2012 (UTC)[reply]

• Move to close – An uninvolved admin can decide whether to also undo the recent move by the involved admin. If he doesn't undo, we can consider a move request later. I don't want to argue this while the people who care are arguing elsewhere about more general issues. Dicklyon (talk) 06:49, 4 February 2012 (UTC)[reply]
• comment the article is unprotected against moves at the moment. I will close this without prejudice. Graeme Bartlett (talk) 11:13, 18 February 2012 (UTC)[reply]

The above discussion is preserved as an archive of a

requested move

. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

The following discussion is an archived discussion of a

requested move

. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the move request was: page moved -- JHunterJ (talk) 21:46, 24 April 2012 (UTC)[reply]

- Renominated by Dicklyon (talk) 17:18, 16 April 2012 (UTC)[reply]

Nomination to rename the article title to lowercase consistent with

Talk:Relative Strength Index#Requested move, Talk:True strength index#Requested move, as well as a pending ArbCom case Wikipedia:Arbitration/Requests/Case/Article titles and capitalisation

), and therefore should not have been made without prior discussion. In that spirit, I have restored this article to its original uppercase version, protected it to prevent further move-warring, and initiated this proposal to rename it to lowercase.

Participants may feel free to adjust my summary of the arguments above if I missed anything. ~

talk) 17:39, 3 February 2012 (UTC)[reply

]

• Support – as re-nominator – I don't know if Amatulic still stands behind his proposal above, but I've copied it here verbatim, along with his Feb 3 signature. This article stands out as an outlier of over-capitalization. It's quite often lower-case in books, and where it's not it's usually because it's used to define an acronym. Dicklyon (talk) 17:18, 16 April 2012 (UTC)[reply]

• Support. A straight case of applying Wikipedia style, as we have been doing in similar RMs. Noetica^Tea? 03:51, 17 April 2012 (UTC)[reply]

The above discussion is preserved as an archive of a

requested move

. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.