Looks like the only change here was to the Wikimedia config, not the MediaWiki software defaults (and thus be subject to a normal release schedule). Instead, this seems to have been done quickly just for the purpose of enforcing something against the wishes of the community.
On Mon, Aug 11, 2014 at 10:18 AM, Brian Wolff <[email protected]> wrote: > > > > Now, having observed that not only user Eloquence (aka Erik Moeller) > > himself engaged in the enforcement of <superprotect> right on de.wp > > [1] but soon after a workaround was published a change was deployed > > [2, 3] as counter measurement to block any possible interference can > > no longer be interpret as acting in good faith but rather strikes me > > as a form of oppression (or worst as censorship). > > > > [Putting the purely mw dev hat on] > > It was a bug in mediawiki, and thus it should be fixed. MediaWiki is used > by many different groups and in general we [mw devs] do not judge people > for how they use the software. If some non wmf entity reported the bug, it > would still be fixed. > > So dont complain that mw fixes a bug in how page protection. If you are > unhappy with current events you should direct your anger at how the wmf > decided to use hard security to enforce its dictates, not at the software > for "working". > > --bawolff > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > -- Lojjik L. Braughler B.S., Computer Science/Applied Indiana University of Pennsylvania, 2017 _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
