Page MenuHomePhabricator

Allow local wiki to override info and discussion links for features included on BetaFeatures page.
Open, LowestPublic

Description

@Kvardek_du noticed fr.wikipedia has a good Flow documentation at https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Flow.

It would so be valuable to override a info or discussion link on a local wiki where a local discussion is organised and well curated, or a good documentation available.

Steps to reproduce

Go to Special:Preferences?uselang=qqx#mw-prefsection-betafeatures

Expected behavior

Link could be edited.

Actual behavior

Link is hardcoded in the extension code so can't be edited.

Plan

Currently an extension can only hardcode links to documetation, generally on mediawiki.org:

/**
  * Callback for GetBetaFeaturePreferences hook
  */
static function getPreferences( $user, &$prefs ) {
    global $wgExtensionAssetsPath;

    $prefs['my-awesome-feature'] = [
        []
        // Link to information on the feature - use subpages on mw.org, maybe?
        'info-link' => 'https://www.mediawiki.org/wiki/Extension:MyExtension/SomeFeature',
        // Link to discussion about the feature - talk pages might work
        'discussion-link' => 'https://www.mediawiki.org/wiki/Extension_talk:MyExtension/SomeFeature',
        []
    );
}

In addition to this setting, we could also allow something like:

/**
  * Callback for GetBetaFeaturePreferences hook
  */
static function getPreferences( $user, &$prefs ) {
    global $wgExtensionAssetsPath;

    $prefs['my-awesome-feature'] = [
        []
        // Link to information on the feature - use subpages on mw.org, maybe?
        'info-link-message' => 'myextension-beta-info-link',
        // Link to discussion about the feature - talk pages might work
        'discussion-link-message' => 'myextension-beta-discussion-link,
        […]
    );
}

The link to the global documentation should then be put to the myextension-beta-info-link value in i18n/en.json to provide a default for wikis not maintaing a valuable local documentation.

Event Timeline

Trizek-WMF renamed this task from Allow local wiki to override info and discussion links to Allow local wiki to override info and discussion links for features included on BetaFeatures page..Jun 10 2016, 1:39 PM

These links are a possible way for people to get information about a new feature. Have a link to the global documentation is the best practice imho, because it can be updated easily and then translated. That's not the case for the local one which can remain abandoned.

Concerning feedback, we trend to have it on a central wiki, where people can leave messages in any language. That's easier to watch.

@Kvardek_du could you prepare a list of the costs and benefits of having a local page for instead of a centralized one?

For information: as a starting point, as cost, we have this abandon risk, as benefit, the content especially adapted for the local project.

For discussion, as risk we have the complexity for the extension team to watch discussions.

(T96875 is slightly relevant here, if you can take some time to read the entire task.)

Imo that's important to have a page in the user's language.

Central page :
(+) Central page is more easily updated
(-) Specific information about what the extension changes in this specific wiki cannot be provided
(-) In the case of Flow, there is currently no translation. In the talk page, there is no message saying you're able to leave a message in your own language.

On wiki page :
(+) can be adapted and appropriated by the community
(-) can be abandoned and out-of-date
(-) the number of feedback pages may be too high

For "On wiki page", I think you can add:

(-) the devs won't know whether you created a local feedback page, so they won't be able to decide whether to follow it

There are 800+ WMF wikis, and a local link could be present temporarily (e.g., this week, during a discussion that an admin wants to promote, but not next week). Even if the team were to manually check every single wiki once a month – which I do not believe that any team will do – they could easily miss a temporary change.

Also, I suspect that you overestimate the value of these links. There are thousands of people using the visual editor each day, but there are only about 25 page views each day for the feedback page that's linked as "Discussion" in Beta Features. That same pages is also linked within the software, and many other places. Nearly all of the page views *aren't* from the link in Beta Features. Changing that link would have almost no effect.

In the case of Flow, there is currently no translation. In the talk page, there is no message saying you're able to leave a message in your own language.

Fixed concerning the talk page.
Concerning the documentation it is 100% translated in French.