Board Thread:News and Announcements/@comment-11733175-20150728100346/@comment-5590118-20150728111007

Tjcool007 wrote: Protecting the entire namespace or having a new protected namespace would be counter-productive. People would have to ask for codeeditor rights before even being able to contribute anything, which definitely doesn't help. That said, leaving things unprotected is not ideal either.

If there wasn't already a codeeditor protection level I would have suggested to use the AuthorProtect extension and give the codeeditor group the "author" right. The only real advantage it would have now is that people could protect their own pages and you wouldn't have to put everyone with a script in the codeeditor group. Overall might not be worth the trouble.

Another idea would be using something ala Approved Revs, which would require importArticles to be modified to use only "approved" revisions. Might be a bit of a PITA to implement. It would also obviously need people to approve stuff (the codeeditors I guess). Approved revisions aren't a bad idea but seems like something staff most likely would not like to implement.