User blog comment:Kirkburn/Technical Update: September 2, 2015/@comment-5973717-20150904162145/@comment-5065259-20150905081458

I seriously hope you are joking that staff would return the ability for admins to edit personal js or css! After what we have seen from the loopholes previously that allowed people to restore admin closed threads (resulted in the moderator group and change of permission rights), that is very unlikely and will most likely generate criticism. They are attempting to reduce security risks, by allowing any admin to edit that create new risks. Even when I ask for help in regards to JS scripts, I make sure to have competent users double check them. I would certainly not trust others to edit my JS or CSS. The only reasonable result is to create another global group like VSTF made up of highly trusted competent users from the dev wiki, might include some VSTF but that's the safest outcome. This should have been done in the beginning, have a special group double check other's personal js/css and to fix any glaring errors involving security or by user request if they manage to break something.

like i have brought up elsewhere, if a user leaves that created useful scripts in their user namespace; local admins should first have the dev wiki look over the script to double check it. if it has been working fine, there should be no issue. what admins should do after the dev wiki check is to move it to the mediawiki namespace and delete the old script. if they are unable to delete the script, request staff to. that is the simply and most effective solution, no need to panic!