"Trope shares the name of a work" is still grounds for a rename, if the following pertain:
- The trope was named after the work, not vice versa.
- There is evidence of confusion with people continually wicking to the wrong article.
"There is evidence of confusion with people continually wicking to the wrong article. " can easily be folded into "misuse".
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard FeynmanI rewrote that ridiculously over-specific Double Date ... thing.
Goal: Clear, Concise and WittyWow that was pretty bad. Why on earth was it under debate for 8 months?
Who watches the watchmen?Crowner stalled and no-one was watching the thread. The "debate" was where to put the trope that had been at Double Date. That is, "What's the new name for this subtrope?".
Link to TRS threads in project mode here.There are a lot of TRS threads that stalled out like that. I guess that since 2011, the TRS workforce has atrophied so much that issues that were resolved in the past no longer can be.
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard FeynmanI still think regular recruitment drives to replace burn outs and people leaving would go a long way to helping some of that.
Who watches the watchmen?How do you "recruit" people to participate in sausage making? Historically, IP and TRS have acquired new talent through volunteering after someone ventures in because of a specific topic and gets hooked.
"It's Occam's Shuriken! If the answer is elusive, never rule out ninjas!"As well as by people who come because there is a controversy, a change or - if you want to use this term - a revolution going on. Much like when in 2011 trope names in Japanese became a topic of contention.
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard FeynmanRight. So what we need is a big controversial policy change to get everyone on the wiki riled up.
"It's Occam's Shuriken! If the answer is elusive, never rule out ninjas!"Like spoilers! XD
Link to TRS threads in project mode here.Looks like this one is done. We can work out whether or not there is a "work force atrophy" problem elsewhere, as the posting frequency in the workshop threads doesn't support that theory. Seems like since 2011 there is plenty of workforce for debate (the number grows) and about the same (stable at "not enough") for taking action.
Goal: Clear, Concise and Witty
(1) To be honest, I think that is a relic from the times where namespace usage wasn't prevalent. It's fairly common for rules and procedures to outlive their warranty, and this seems to be a case of that. I would suggest to remove that from "reasons to rename".
(2) That falls under "misuse" or "ambiguous name" (if you can offer evidence that it leads to problems).
(3) I would put that under "not thriving", "misuse" or "ambiguous name" (depending upon the evidence available, of course).
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard Feynman