Jump to content

Stewards/Elections 2015/Coordination

From Meta, a Wikimedia project coordination wiki

The steward elections are coordinated on #wikimedia-stewards-electionsconnect, users interested in helping out should consider joining the channel to better coordinate and receive the feed or relevant recent changes.


  • Agree on a wording for the candidate banner
  • Agree on a wording for the vote banner
  • Notify translators
  • Create campaigns and add to calendar
  • Update the javascript for the candidate banner


The german translation of the months in the dates ("Januars", "Februars") has an extra trailing "s". I don't know enough Mediawiki-foo to fix that, though.--Oneiros (talk) 18:44, 8 February 2015 (UTC)[reply]
I've fixed it in the original site Stewards/Elections_2015/Introduction [1] (click here for explanation of these parameters), but the German translation still uses the old source apparently. I don't know how to refresh translated sites, purge does not help.--Berita (talk) 21:19, 15 February 2015 (UTC)[reply]
Marked the latest version for translation and updated the German translations. --Glaisher (talk) 05:04, 16 February 2015 (UTC)[reply]
  • LangSelect is ugly in these pages, imo.. We discussed about migrating (or completely creating a new template) to the extension last month but it doesn't make the current situation any better (but would work nicely if the date/time is same every year). Also I noticed while updating the template today, some translations were for 2012.. We should remove the year from this one too. But simply removing all instances of year from the text would mess up the translations, I think? --Glaisher (talk) 15:52, 1 January 2015 (UTC)[reply]
  • LangSelect is a very old solution. LangSwitch is far better, and user friendly (no need to select a language, the most accessible translation is directly displayed according to the prefered user language for the UI of the wiki (using the Universal Language selector, or appending temporarily a "?uselang=code" query parameter to the URL of the current page, something that the language bar could also offer for temporarily viewing another language, withut having to create a navbox in all pages with the necessary links). LangSwitch also supports the standard language fallbacks (so if there's no translation in Wallon, the French version can still be displayed, or English if there's no French.
  • This is a great improvement for users that prefer their minority or regional language, for which many things are not translated , but at least the major language understood has a translation that they can read : they don't need to click anywhere to see the best fallback, they don't have to change theur prefered language in the ULS or in their preferences page).
  • LangSwitch uses by default the user language as returned by {{int:lang}}. Many useful templates are now using LangSwitch (see for example on Commons, where much efforts have been made using LangSwitch to offer a very international content, for example in images descriptions and many pages, or in category pages and galleries)
  • LangSelect is very ugly, and generates too huge pages when there are many translations (and it requires the support of Javascript, otherwise all translations will be displayed at the same time and pages are then difficult to design, because all translations will stack vertically (this forbids using it for small spans of text, but LangSwitch does not have this defect and can localize even the smallest part in the middle of a paragraph). It is not compatible with small devices. LangSwitch generates only the content for a single language (it profits from the MediaWiki server cache which is now caching different views of the same pages, depending on the user's language or the "?lang=*" query parameter (that can override it temporarily).
  • All translation problems can be solved with LangSwitch which is really universal. Look for example at the current state of the candidatures that I have fixed (A request was made by a MetaWiki admin to assist in correcting it, and the work is done).
  • Note that when using LangSwitch you must be very careful at not confusing the language codes used by your contents (such as template parameters names) and the user language: you must NOT attempt to create a static fallback resolution by testing if some parameters are set or not: pass all lanauges to LangSwitch, it will correctly select the appropriate content and will use the possible fallbacks according to the requested user language, but not according to mutual relations linking languages (if you do it,you will limit the capabilities of LangSwith. LangSwitch is supported now by a Lua module (which is easier to maintain, notably because it can use the standard fallbacks and support many more locale variants. So in summary there's no need of any other module. verdy_p (talk) 17:59, 20 February 2015 (UTC)[reply]

Candidate statements


See candidate statements page for the full list of candidates.

Confirmation statements


See confirmation statements page for the full list of candidates.

During vote