edited 11th Dec '12 7:57:41 AM by ArcadesSabboth
edited 11th Dec '12 1:53:20 PM by FastEddie
edited 11th Dec '12 4:19:16 PM by Xtifr
edited 12th Dec '12 2:48:45 AM by MorganWick
edited 12th Dec '12 2:08:09 PM by Fighteer
edited 12th Dec '12 2:18:10 PM by Fighteer
edited 12th Dec '12 2:57:17 PM by Fighteer
edited 13th Dec '12 6:49:30 AM by Fighteer
- The main concern I have of any approval/queue process is that it will lead to a "black box" scenario where you don't get any idea on how input X leads to output (approval/disapproval) Y. This is still an issue with the Cut List and in lesser measure with hollers.
- We'll need to delimit which sort of page needs approval in form of YKTTW, thread or moderator one or are free to do. I think we could set the choice selection up along with a listing of approved namespaces/subpages (I assume we'll move them to a new system)
- I am not sure if requiring approval for new accounts is really that useful. From my sight on new pages, page creation issues strike even older accounts.
- We already have a new pages queue (which is already used for controlling) here. We don't need redundant lists, in other words.
- @91 brings up a valid point that the way our indexing system works isn't really suited for a selection in the page creation system. Rather, I'd suggest to create an unindexed pages list like the current untyped pages list that is filled with unindexed pages and emptied when the entries are indexed.
- There is also the question how to work with locked pages there. IMO these page creation controls could easily making autolocking unnecessary, especially since they are a bit hard to work with.
- If I were designing the system, feedback would be automated at all levels. You'd get a PM or some other form of notification when any request that you submitted is addressed.
- That's my thought as well.
- While it's true that even established accounts can do dumb things, most pure junk page launches are done by newbies. There's also the issue of namespacing, which this system is designed to address.
- That's not a queue, it's a report. To make it a queue, there would have to be some sort of "approve/deny" system accessible to people with a certain security level.
- Yes, we'd need to fix indexing for that idea to work. It's a proposal, but getting newly created pages indexed is one of our headaches.
- Locking a cut page would be redundant with this system, except that it might set up an auto-reject or at least force the request into the moderator-approval queue. "The article you're trying to create was previously cut. Your request must be evaluated by a moderator." Or some such.