From Meta, a Wikimedia project coordination wiki

Autopatrollers group - Autoverificado

Quisiera que me informaran como se habilita tal grupo, ya que un usuario me ha solitado la inclusión en el mismo. Como burócrata no estoy habilitada a realizarle el cambio que me pide.

En Wikisource en español no se encuentra habilitado (ver: [1]) mientras que en inglés si existe: [2].

Agradecería cualquier ayuda que pueden brindarme. Saludos cordiales, --LadyInGrey (talk) 03:54, 26 May 2014 (UTC)

Hi I took the liberty to translate the prior message, hope to be accurate:

I would like to be informed how to enable this group, because a user has requested his inclusion on it. As a bureocrat I'm not enabled to make the change he requests.
In Spanish Wikisource is not enabled (check: [3]) while in English it exists: [4].
I would gladly appreciate any help on this matter. King Regards, --LadyInGrey (talk) 03:54, 26 May 2014 (UTC)
In order to enable new groups, you need to make a request on bugzilla: (after community consensus has been established). I suggest you look at Special:ListGroupRights on en.wikisource to see which rights are assigned to the autopatrollers there (in contrast to, maybe, meta or other wikis). --MF-W 23:21, 1 June 2014 (UTC)

Hello! Earlier this year at the foundation, the Program Evaluation and Design team joined Grantmaking. We would like to reflect this change in the meta namespace by moving everything in the Programs:Evaluation_portal to the Grants namespace. We plan to begin this transition on Tuesday May 27, 2014. Please comment if you have questions/thoughts/concerns/etc before this change occurs. Thanks! EGalvez (WMF) (talk) 14:53, 19 May 2014 (UTC)

Hi Edward, unfortunately this move broke links in various places. I know that this is ultimately the fault of bug 60920/bug 39023 and that you and Haitham and Jonathan have already been fixing the missing redirects manually, but five days after the move there are still a lot of these broken links (e.g. in the Wikimedia Conference programme or in the March WMF report - also its blog and mailing list versions -, or on Jonathan's own user page ;). Any plans to fix them as well? Regards, Tbayer (WMF) (talk) 22:23, 3 June 2014 (UTC)
For your information I have fixed the most important linking errors in pages of the portal, that were using the old page names, as well as some needed changes in Langcat parameter for categories, for properly handling the new base page name ("Evaluation portal" reduced to "Evaluation") and not just the namespace name (the change from "Programs:" to "Grants:" does not influence Langcat which is only interested in the pagename without the namespace).
Note that Langcat in many places require feeding correctly the base page name of translations, but only to detect if we are in a subpage with a language code, and if pages are translated with standard language codes (notably all those supported by the Translate extension) we can safely use the pagelang template to retrieve the needed language code to append to the category. May be later I will remove the need of this parameter in Langcat, so that it will infer the missing language code using pagelang directly, which can then be used to generate the suffix to add to the category name where we want to list a page. This will avoid maintenance problems each time pages are renamed as the language code will still work. Note also that Langcat works with pages still not trnaslated with the transalte extension (because their content is not an exactly matching translation) and this includes pages whose source is not English (notably pages made by local chapters whose work original language is not English)
I hope that in some future we'll have a MediaWiki keyword allowing to tag a page with metadata to state in which content language it is written, and that the Translate extension will be able to read that metadata so that other languages than the wiki default English will be used as the source of translations (in that case the base page name will remain in another language, and English will be translated in a "/en" subpage like other languages). Also, it should be possible to initially design a page in another language than English, then translate it to English with the English extension, then have an Adminsitrator option make that translation becoming the new editable base page for translations. This should be discussed as improvements for the Translate extension and then a feature request could be made.
Finally there remains problems with some legacy language codes (like "als", "zh-hant", and "zh-hans") which are no longer translatable by the Translate tool due to a local config, but still blocked from editing, even thugh the Translate tool overwrite them: this is a problem because these uneditable and untransaltable page now contain English default (all its translation units are missing byt we cannot add/edit them in the Translate tool), and these Englush default forbid to use fallbacks (such as "als" fallbacking to "gsw", or "zh-hans" and "zh-hant" fallbacking to "zh"). For now the only solution to that problem is to completely delete these pages. But my opinion is that the Translate tool should never overwrite any subpage for a language code that it does not allow us to translate, and should not protect them against normal wiki edits.The Translate extension should also expose in a parser function or Lua API the "translated" status of a language subpage: if it rejects that language code it should not block that page; but it blocks it if the language code is one "supported" by MediaWiki for its UI, regardless of local settings of the extension only meant to deprecate old codes that it should then never overwrite and block). verdy_p (talk) 03:52, 4 June 2014 (UTC)

Global CU policy

Hi all, with SUL finalization fast approaching (yay!) and the current situation of stewards checking on the loginwiki, I think now is a good time to update the 9 year old CheckUser policy to deal with a global CU. I've created a draft at CheckUser policy/Global CheckUser draft; if you have concerns or comments (or any feedback at all!), please indicate so on the talk page! This includes whether it should exist in the first place, etc. Thanks, Ajraddatz (talk) 04:41, 12 June 2014 (UTC)

Migrate Main Page to Translate extension?

Please see Talk:Main_Page#Migrating_to_translate_extension. PiRSquared17 (talk) 16:58, 12 June 2014 (UTC)

Scores for Wikisource

I've opened a new RfC on Scores for Wikisource. Please comment! --Rezonansowy (talk) 20:42, 13 June 2014 (UTC)

Integration of Wikidata with Meta-wiki

Please take a look at a discussion wikidata:Wikidata:Project chat#Integration of Wikidata with Meta-wiki.--Abiyoyo (talk) 09:24, 22 June 2014 (UTC)

Leaflet For Wikimedia Meta-Wiki At Wikimania 2014 (updated)

Please note: This is an updated version of a previous post that I made.

Hi all,

My name is Adi Khajuria and I am helping out with Wikimania 2014 in London.

One of our initiatives is to create leaflets to increase the discoverability of various wikimedia projects, and showcase the breadth of activity within wikimedia. Any kind of project can have a physical paper leaflet designed - for free - as a tool to help recruit new contributors. These leaflets will be printed at Wikimania 2014, and the designs can be re-used in the future at other events and locations.

This is particularly aimed at highlighting less discoverable but successful projects, e.g:

• Active Wikiprojects: Wikiproject Medicine, WikiProject Video Games, Wikiproject Film

• Tech projects/Tools, which may be looking for either users or developers.

• Less known major projects: Wikinews, Wikidata, Wikivoyage, etc.

• Wiki Loves Parliaments, Wiki Loves Monuments, Wiki Loves ____

• Wikimedia thematic organisations, Wikiwomen’s Collaborative, The Signpost
The deadline for submissions is 1st July 2014
For more information or to sign up for one for your project, go to:
Project leaflets
Adikhajuria (talk) 09:39, 25 June 2014 (UTC)