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

I never said anything about staff restoring the ability for any admin to edit these pages; I said "they might later be able to reenable admin editing of these pages, to some degree at least". While I neither speak for staff nor have any insight into future plans on staff's part, leaving the option open in the future for allowing certain admins to edit any user's JS and CSS pages makes a lot of sense. Obviously, this would not be an ability to be handed out part and parcel with the admin package, but would rather have to be an extra that would have to be specifically requested and a necessary level of technical competence and general trustworthiness demonstrated (though I have no comment on what the threshold there might be). That being said, the most realistic implementation of such a system would be via a new usergroup, which would have the added bonus that it could be applied to non-admins as well, hence my further observation of the possibility of "a more general system that could allow non-admins to edit these pages under specific circumstances".

And as for user JS that becomes unmaintained when the user leaves Wikia or otherwise stops editing, as has been stated in other comments here, exactly why would a wiki be using a user's personal JS to add functionality for all visitors? Any sitewide JS used on a wiki which is not being loaded from Dev Wiki should be located in the MediaWiki namespace, and any wiki which currently uses user JS sitewide should either move it to the MediaWiki namespace, or simply stop using it altogether, as soon as possible (whenever "as soon as possible" may be, considering the current lockdown of the MediaWiki namespace in general and JS interface pages in particular). While there are plenty of users who are willing and able to help out with JS as needed, it is no one's job to maintain or audit a user's personal JS except for that user and any other users who decide to use or fork it, and it should not be expected that any particular user or group of users should have that responsibility.