https://bugzilla.wikimedia.org/show_bug.cgi?id=70125
--- Comment #4 from Rainer Rillke @commons.wikimedia <[email protected]> --- (In reply to Bartosz Dziewoński from comment #2) Thank you, yes, there should be some notification on each of such pages how to propose changes to them and get these reviewed in a *timely manner*. (In reply to John F. Lewis from comment #1) > This is inappropriate. Please be specific about what is inappropriate. The bug's description contains multiple options. > The Foundation are not preventing every single administrator from editing > site-wide js pages. This was not true. And I see that in future, super protection might be used again which renders all non-staffers unable to edit pages with this protection level. > Erik has stated they are proposing a code-review sytle system Code review sounds good, though non-default gadgets should be still deployable without having someone reviewing them. There won't be enough resources. > a patch which separates site js and CSS from the editinterface package Cool. Gerrit #? > nor will superprotect from Wikimedia as visible by the 30 patches reverting > the change abandoned by operations Fine, then let's go with what Bartosz Dziewoński suggests. DMCA takedown notices from the legal team consist of comprehensive information about how to challenge them and often also why the DMCA requests were complied with. I think we should have something similar for super protection: * What will be the right channel to get emergency-changes quickly applied to super protected pages. * Why were pages super protected? * What is super protection? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
