Community Wishlist Survey 2017/Archive/Transwiki template

Random proposal ►◄ Archive

Transwiki template

N Out of scope for the team

Problem: Various same templates are used on different project usually imported a day from Wikipedia project. But template on Wikipedia where communities are more active are up dated while templates on other projects are not if administrator don't care about it.

Who would benefit: Every project users

Proposed solution: Creating a transwiki template function witch provide the use of Wikipedia's template on all project but without hindering template already present on projects to avoid traditional community protesting reaction to change.

More comments:

Phabricator tickets:

Proposer: Lionel Scheepmans ^{✉ Contact} _{French native speaker, sorry for my dysorthography} 18:44, 8 November 2017 (UTC)[reply]

Discussion

Other potentially related: phab:T22153, phab:T121470 Trizek (WMF). (talk) 09:27, 9 November 2017 (UTC)[reply]

Maybe close to 2017 Community Wishlist Survey/Wiktionary/Share conjugation (among other things) templates on www.wiktionary.org proposal? Noé (talk) 19:45, 9 November 2017 (UTC)[reply]

Yes please!! Centrally hosted templates and Lua modules will solve the decade-long jumble that Wikidata is persuading us to solve. Der yck C. 21:48, 11 November 2017 (UTC)[reply]
I was always a big fan of this idea, but as a community developer i've encountered so much inter wiki problems lately, that i'm beginning to doubt the value in this. I see an increasing demand for control within wiki's and centralising things will put a lot more burden on individual template and module authors to balance the requests of those communities. We will thus see many forks, which will just move the problem to an area with less clear governance structures. Instead, maybe we should create a tool or something that makes it easier to compare versions/age/differences of these between wikis ? —TheDJ (talk • contribs) 15:09, 15 November 2017 (UTC)[reply]
The biggest problem with having global gadgets/templates is the fact that it's currently not possible to localize them. I like TheDJ's idea. Even something to do easy exporting/importing of templates between wikis (one-click buttons to "Update" templates by copying them from another wiki, for example) seems like a better idea for now until someone comes up with a brilliant idea for how we can localize templates and gadgets without making the wikis totally unusable for everyone. -- NKohli (WMF) (talk) 01:25, 18 November 2017 (UTC)[reply]
Localization is not hard (just use messages; see also T156210), but the visual flexibility of templates would be lost through centralization. Maybe the way to go is to centralize Lua modules but not templates? Large wikis seem to be moving towards mostly Lua-driven templates for the more complex use cases anyway, and for a library there are good ways to handle local variations. --Tgr (WMF) (talk) 11:48, 18 November 2017 (UTC)[reply]

Hi Lionel Scheepmans: Unfortunately, this proposal is too big for our team; it's already been in the top 10 in a previous survey, and we had to decline. Sorry about that! Thanks for participating in the survey. -- DannyH (WMF) (talk) 19:32, 20 November 2017 (UTC)[reply]

Ok Danny thanks. Lionel Scheepmans ^{✉ Contact} _{French native speaker, sorry for my dysorthography} 19:56, 20 November 2017 (UTC)[reply]