Recommend changes YKTTWGuidelines.

So this is strictly about officially updating the "YKTTW Guidelines" page? Okay, that I can upvote.

But IMHO, the only way we're going to make YKTTW mandatory (in this sense) is tp place a YKTTW plug on the Editing form any time somebody tries to create a new Main/ page.

edited 17th Apr '12 8:04:59 AM by Stratadrake

So in practice, what does this mean? Are any tropes created without YKTTW to be automatically cutlisted? If so, does the Grandfather Clause apply? And do the cutmasters actually agree with that? Or are we just voting to change a line on a guideline page, with no changes in practice?

Any trope launched without a YKTTW should probably be cutlisted.

Then we should have a crowner that says "should we make it policy that any future trope page that doesn't go through YKTTW will be cut". The current crowner asks a very different question.

I think if we can get the administration to agree with the policy, then we can discuss with the admins and mods about what they think is the best way to enforce it.

The main thing I want to do write know is let people know that they have to take things to YKTTW first, rather then giving the impression it is okay to make trope pages on your own without providing the chance for other tropers to give feedback on your ideas.

Non-YKTTW pages that are good are rare but not unheard of. I would qualify any retroactive decision about existing pages with actual review of the page.

Just noticed that the Wiki Magic page will need to be revised if/when this change is confirmed. If anyone finds other pages that will need to be updated, it's probably a good idea to list them on this thread.

Calling crowner in favor of making YKTTW mandatory. (Yay!)

We still need to pimp it on the "edit article" page:

• IF editing something in the Main/ namespace,
• AND there is currently no article in that name,
• AND there is no (launched) YKTTW title linked to that name,
• THEN:
  • Display a notice to the tune of "If you're creating a new trope, please post it in the YKTTW area for discussion" on the editing form.
  • Do not actually block editing the article. (this wasn't part of the current decision)

Do we have a way of finding recently created non-YKTTW'ed articles, from people other than one's self?

Not that I'm aware of. Sometimes I find them when I'm typing pages, but they aren't that common there. I can also run across them going through recent edits with the large changes filter, but that doesn't catch everything either.

Any edit to create a new page on Main should bring up a page reminding editors to put works in namespaces and new tropes in YKTTW.

Agree on that point.

Are we also going to strictly require that every YKTTW get five hats before launching? Recommend, certainly, but I don't feel that requiring that all new tropes meet this formality is a good idea. If this is not the place to raise this point, my apologies and please disregard.

Are we also going to strictly require that every YKTTW get five hats before launching

If we did there would be many a perfectly good index and trope that would never gets launched. I've made indexes that never got more than two or three hats even thought they were ready to go on day one and I had them in YKTTW for over a week.

The big things I wanted to do with the change I proposed is encourage people to seek feedback before creating a trope. I don't necessarily think we need to be hardcore about the hat thing. I've seen excellent tropes otherwise ready to launch that would linger for weeks with only three hats, and stuff get 5 hats in a day or two even thought there were still serious issues with the description. For the moment, I think we'll have leave it to the discretion of the sponsor as to whether or not he or she thinks the trope is ready, based upon the feedback he/she is getting in the comments, comments, tags etc.

I would like to have a team of people to review proposed launches to make sure they are ready before the launch actually goes through, but that idea didn't meet with a positive response when I suggested it earlier.