Page MenuHomePhabricator

Should technical support for skins be identified in Special:Preferences?
Open, Needs TriagePublic

Description

Some skins on WMF-supported wikis are supported by the WMF dev teams (MonoBook and Vector) and some are supported by volunteer devs (CologneBlue, Modern, Timeless).

In practice, volunteer-supported skins are often supported by just one or two people. Thus, as a practical matter, people using a volunteer-supported skin may encounter more skin-related bugs, especially if something in MediaWiki changes suddenly, before the volunteer dev is aware of the change/back from holiday/has time to update its code.

Should the "Skin" section of Special:Preferences#mw-prefsection-rendering contain a note about support levels?

This is somewhat related to T171070: Which skins are supported and which should be supported?.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 17 2017, 6:27 PM
Jdforrester-WMF added a subscriber: Jdforrester-WMF.

Tagging this for Readers Web as they might want to weigh in (it's mostly their support work, after all).

Kghbln added a subscriber: Kghbln.Oct 17 2017, 7:32 PM

This should not just be about skins but also about extensions. In either case I basically only see two markers: Supported by WMF and Not supported by WMF however this would be called in the end. More fine-graned markers would need a continuous assessment I do not see will happen, neither for skins nor for extensions. Even when looking at extensions supported by WMF there are some which only get critical fixes. So this does not help much since we are still up for interpretation about every piece of software. As much as I would love to see something like this become reality I do not see how.

Jdlrobson added subscribers: ovasileva, Nirzar, Jdlrobson.

cc @Nirzar and @ovasileva

From a technical perspective, I'm not sure what the goal would be. If a skin is available in the preferences the user should expect it to be of a certain standard. If it's experimental it should probably be in the gadgets panel e.g. "Enable unsupported skins". The average user should not be expected to comprehend that a skin that looks nice might have bugs. It should just work. All code should be assumed to have bugs and if the bugs are serious it shouldn't be made an option.

Thus, as a practical matter, people using a volunteer-supported skin may encounter more skin-related bugs,

I'm not sure this is true or fair. I think we hold all code contributors to an equal standard.

especially if something in MediaWiki changes suddenly, before the volunteer dev is aware of the change/back from holiday/has time to update its code.

If this happens then whoever is making those MediaWiki changes should probably be asked why they are introducing bugs to the production ecosystem. If this is happening I'd also expect ReleaseEngineering to appear with a big stick.

Generally when reading web build things now, we provide mechanisms to disable features on skins we do not support. For example the RelatedArticles extension maintains a skin whitelist: https://github.com/wikimedia/mediawiki-extensions-RelatedArticles/blob/master/extension.json#L165 to avoid enabling the feature on a skin we do not support. It would be good to standardise this in some way, as increasingly we are seeing compatibility problems between skins and new feature and this doesn't seem like a good pattern.

Whatamidoing-WMF added a comment.EditedOct 18 2017, 2:39 AM

From the end-user perspective, disabling features in certain skins is the same thing as a skin-related bug. Imagine that I hear about a cool new feature, and enable it. But it's not there, because I'm using the "wrong" skin. From my point of view, that's a "bug": I enabled a feature that didn't work.

<s>BTW, Related Pages worked just fine for me at the Haitian Wikipedia on Vector last year, but now it's disappeared (and I'd like it back, please).</s> (Never mind, it's working today. Maybe I just didn't wait long enough for it to load yesterday.)

Should the "Skin" section of Special:Preferences#mw-prefsection-rendering contain a note about support levels?

For consistency, I wonder if that's already the case in other areas. When installing and choosing the MSSQL backend, is there any note about its support level?

We already have beta features.
If a <skin/functionality/extension/insert-other-word-here> isn't 'mature/maintained enough [anymore?]', I'd expect it to be under "beta".
Nothing specific about skins here IMHO and no need for a skin-specific solution.
The problem is agreeing on a definition of 'mature/maintained enough', of course.

Related (but for MW extensions only): T173544: High quality extension levels tagging

Similar suggestion in [excerpt]

I was meaning an inline information where it currently appears that identifies it as beta. If there is scope to add leads to information about the skin, its trial, and where feedback is welcomed. At the moment there is simply no context to the skin, it has appeared as a new skin with the same level of importance and permanence as others.

Kghbln removed a subscriber: Kghbln.Nov 27 2017, 9:13 PM