In T97766#1251793, @Steinsplitter wrote:

No consensus need to switch it on, but consensus needed to switch it off. Simply a joke.

Allow me to be very clear here: This feature was added as a commit to MediaWiki, it was not a new extension. Such things which are deployed automatically on the MW train (i.e. changes to MediaWiki defaults) do not need consensus from $MY_FAVOURITE_WIKI, because otherwise we'd have Wikimedia wikis dictating MediaWiki development and affecting non-Wikimedia sites. Rights changes for specific wikis generally do.

[ Temporarily adding back Community-consensus-needed project pending a task edit with the URL of such consensus discussion. ]

In T97766#1251873, @Krenair wrote:

In T97766#1251793, @Steinsplitter wrote:

No consensus need to switch it on, but consensus needed to switch it off. Simply a joke.

Allow me to be very clear here: This feature was added as a commit to MediaWiki, it was not a new extension. Such things which are deployed automatically on the MW train (i.e. changes to MediaWiki defaults) do not need consensus from $MY_FAVOURITE_WIKI, because otherwise we'd have Wikimedia wikis dictating MediaWiki development and affecting non-Wikimedia sites. Rights changes for specific wikis generally do.

Sorry, but that is nonsense. There would be no problem to ship MediaWiki with a disabled default; and it would also no problem to disable this feature as default in the Wikimedia-Wikis (if MediaWiki REALLY needs this feature as default on).

In T97766#1252063, @DaBPunkt wrote:

In T97766#1251873, @Krenair wrote:

In T97766#1251793, @Steinsplitter wrote:

No consensus need to switch it on, but consensus needed to switch it off. Simply a joke.

Allow me to be very clear here: This feature was added as a commit to MediaWiki, it was not a new extension. Such things which are deployed automatically on the MW train (i.e. changes to MediaWiki defaults) do not need consensus from $MY_FAVOURITE_WIKI, because otherwise we'd have Wikimedia wikis dictating MediaWiki development and affecting non-Wikimedia sites. Rights changes for specific wikis generally do.

Sorry, but that is nonsense. There would be no problem to ship MediaWiki with a disabled default; and it would also no problem to disable this feature as default in the Wikimedia-Wikis (if MediaWiki REALLY needs this feature as default on).

It's no problem for MediaWiki to ship stuff to default off, but there's also nothing wrong in general with MediaWiki shipping with things default on.

Sure @Krenair, but why do we need a community-consensus to disable something, but not one to enable something?
And if MediaWiki really have something enabled on default because somewhere in the internet someone COULD use a feature: Why not disable it in the Wikimedia-config globaly and ASK first who (=which of our wikis) could need it?

In T97766#1252137, @DaBPunkt wrote:

Sure @Krenair, but why do we need a community-consensus to disable something, but not one to enable something?

Because you want wiki-specific config changes (i.e. specific sysadmin intervention), whereas the feature appeared on your wikis via the routine "train" deploys that simply bring the newest (or very close to newest) version of MediaWiki to Wikimedia's sites every week or so.

In T97766#1252137, @DaBPunkt wrote:

And if MediaWiki really have something enabled on default because somewhere in the internet someone COULD use a feature: Why not disable it in the Wikimedia-config globaly and ASK first who (=which of our wikis) could need it?

Why not have it enabled by default if it's a good feature that can be used productively by many people? New default-on things obvious to users aren't entirely forbidden, just quite rare.

Status: If not used = switched off (fixed in a other patch). Closing this bugreport?

In T97766#1252195, @Krenair wrote:

Because you want wiki-specific config changes (i.e. specific sysadmin intervention), whereas the feature appeared on your wikis via the routine "train" deploys that simply bring the newest (or very close to newest) version of MediaWiki to Wikimedia's sites every week or so.

Maybe you should look at the https://en.wikipedia.org/wiki/User:Jimbo_Wales/Statement_of_principles :-)

In T97766#1320715, @Steinsplitter wrote:

In T97766#1252195, @Krenair wrote:

Because you want wiki-specific config changes (i.e. specific sysadmin intervention), whereas the feature appeared on your wikis via the routine "train" deploys that simply bring the newest (or very close to newest) version of MediaWiki to Wikimedia's sites every week or so.

Maybe you should look at the https://en.wikipedia.org/wiki/User:Jimbo_Wales/Statement_of_principles :-)

Anything specific there you feel is relevant?

In T97766#1322472, @Krenair wrote:

In T97766#1320715, @Steinsplitter wrote:

In T97766#1252195, @Krenair wrote:

Because you want wiki-specific config changes (i.e. specific sysadmin intervention), whereas the feature appeared on your wikis via the routine "train" deploys that simply bring the newest (or very close to newest) version of MediaWiki to Wikimedia's sites every week or so.

Maybe you should look at the https://en.wikipedia.org/wiki/User:Jimbo_Wales/Statement_of_principles :-)

Anything specific there you feel is relevant?

Is this a rhetorical question?

Nope.