Erik, I'll be writing a longer post on the Meta RFC later, but can you confirm whether the idea is to "superprotect" key interface pages like [[Mediawiki:common.js]] on a permanent basis, or will this feature only be used to lock pages temporarily in the case of wheel warring or other circumstances like what happened on de.wp?
Thanks, Craig Franklin On 10 August 2014 23:27, Erik Moeller <[email protected]> wrote: > Hi folks, > > Admins are currently given broad leeway to customize the user > experience for all users, including addition of site-wide JS, CSS, > etc. These are important capabilities of the wiki that have been used > for many clearly beneficial purposes. In the long run, we will want to > apply a code review process to these changes as with any other > deployed code, but for now the system works as it is and we have no > intent to remove this capability. > > However, we've clarified in a number of venues that use of the > MediaWiki: namespace to disable site features is unacceptable. If such > a conflict arises, we're prepared to revoke permissions if required. > This protection level provides an additional path to manage these > situations by preventing edits to the relevant pages (we're happy to > help apply any urgent edits) until a particular situation has calmed > down. > > Thanks, > Erik > -- > Erik Möller > VP of Engineering and Product Development, Wikimedia Foundation > > _______________________________________________ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines > [email protected] > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:[email protected]?subject=unsubscribe> > _______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines [email protected] Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, <mailto:[email protected]?subject=unsubscribe>
