From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search
Project portals — live Template, Sandbox template is the raw, live HTML source code of a Wikimedia project portal. Changes made there are seen by millions of people within an hour – sooner to anyone who clears their browser's cache. Do not edit this code unless you know what you're doing, and do not edit it by hand – intelligent Scribunto modules are ready to assist you. You can experiment with the template in the sandbox. To change language names, romanizations, etc., edit Module:Project portal/wikis. Then get the attention of a Meta administrator who can deploy your changes: place an {{Edit Protected}} notice at template or Meta:Requests for help from a sysop or bureaucrat. Administrators: Always follow the instructions on the edit page of template to a tee.

Current issues[edit]

Module:Project portal identified the following issues in template:

  • Change de: article count from 1,879,000+ to 1,880,000+ in top 10 ring.
  • Change en: article count from 5,017,000+ to 5,019,000+ in top 10 ring.
  • Change es: article count from 1,214,000+ to 1,215,000+ in top 10 ring.
  • Change fr: article count from 1,698,000+ to 1,699,000+ in top 10 ring.
  • Change ja: article count from 992,000+ to 993,000+ in top 10 ring.
  • Change ru: article count from 1,269,000+ to 1,270,000+ in top 10 ring.

This report was automatically generated based on article counts in List of Wikipedias/Table (last updated 86 minutes ago) and page view statistics in Module:Project portal/views (last updated 16 days ago). Administrators: See instructions for updating the portal.

By topic:

By year:

Deprecation of bits server[edit]

The bits server is officially deprecated now, so we need to update the portal templates to switch to a different URL for the stylesheet ASAP. We can use meta instead. I've already updated the wikimedia portal template, which went smoothly. Unless anyone has any concerns, I'll update the others soon as well. Kaldari (talk) 21:39, 2 June 2015 (UTC)

Wikipedia portal updated. Kaldari (talk) 22:18, 2 June 2015 (UTC)

Add EventLogging[edit]

For T100673, I added some stand-alone EventLogging code to m:Www.wikipedia.org_template/temp, and would like to get it reviewed and merged into m:Www.wikipedia.org_template.

Jdouglas (WMF) (talk) 18:41, 10 June 2015 (UTC)

@Mxn: could you take a look at this? Ironholds (talk) 17:26, 11 June 2015 (UTC)
@Jdouglas (WMF): needs to be rebased since the code has diverged. The diff shows many unrelated changes that essentially undo recent revisions to the template. To aid future changes and allow actual code review, the script should be maintained on a separate page without minification. I assume the original has some helpful inline comments explaining the logic? Why is this compiled from TypeScript? We don't currently use TypeScript or CoffeeScript, makes it hard to review out of the blue. –Krinkletalk 00:07, 12 June 2015 (UTC)
@Jdouglas (WMF): I did a partial review.
  • It replaces all important anchor links with href="javascript:;". This makes the page less accessible, obfuscates the target url from the browser status bar when users hover the url, and impairs the user's ability to Copy URL or Open in new tab. It may also break search engine index since Google is capable of evaluating basic javascript. I'd recommend to instead leave the href in tact, terminate the event with return false, and re-assign location.href from the callback as usual. You may also want to race the event against a setTimeout (e.g. 2 seconds) since a small class of HTTP errors do not propagate to Image.onerror, and just in general because networks can be flaky and/or slow (including mobile).
  • In browsers that support it, you may want to use navigator.sendBeacon. This way modern browsers aren't penalised with slow fallbacks for old browsers. This portal is the first entry for some users. Being slowed down here could have negative impact. To keep code small, the beacon call could even re-use the same callback by invoking it directly.
  • The JSON serialisation looks unsafe. It probably works for the common case, but it's incorporating many external values that aren't always free of quotes or other invalid syntax. A micro quote library (e.g. jQuery.JSON/quoteString) may be justified. E.g. var quote = JSON.stringify || function quoteString; .. push('"referer": ' + quote(document.referrer)). --–Krinkletalk 03:51, 12 June 2015 (UTC)
@Jdouglas (WMF): What do you think of Krinkle's comments? My only further comment is that the final JavaScript code should live in MediaWiki:Gadget-wm-portal.js, which is minified automatically and benefits from syntax highlighting. Since we've been using /temp to stage routine updates, feel free to iterate on this proposal on separate sandboxes, such as template/EventLogging and User:Jdouglas (WMF)/Gadget-wm-portal.js. Alternatively, perhaps it's time to bite the bullet and move development of this portal to someplace more code-friendly, like GitHub. (We still have to deploy the static portal code here, but writing HTML in a plain text box is no one's idea of fun.) – Minh Nguyễn 💬 15:26, 18 July 2015 (UTC)
@Mxn: Sounds great! Jdouglas (WMF) (talk) 16:20, 20 July 2015 (UTC)

Goan Konkani transliteration[edit]

I added a partial transliteration of Goan Konkani (gom:) into the Kannada script, since 12% of that wiki's articles are in Kannada script. (Generally, this portal includes all the scripts that a particular wiki features articles in, whether manually or via an automatic converter.) I temporarily settled on ಕೊಂಕ್ಣಿ (Konknni), but ideally there would be a full equivalent of Gova Konknni. Here's what I found so far:

  • ಕೊಂಕ್ಣಿ is used on gom:मुखेल पान as an equivalent to कोंकणी and Konkani.
  • gom:Kd/ಕೊಂಕ್ಣಿ ಭಾಸ್ (= en:Konkani language) uses ಕೊಂಕ್ಣಿ but translates "Goan Konkani" as ಗೋಂಯಕಾರ ಕೋಂಕಣೀ, which doesn't appear to be quite the same thing.
  • ಗೋವಾ ಕೊಂಕ್ಣಿ appears to be closer to Gova Konknni, but there are few occurrences of it on the Internet.

I welcome feedback from the gom: community for placing the correct language name on this page.

 – Minh Nguyễn 💬 15:07, 18 July 2015 (UTC)

  • First of all, the existing "Gova Konknni" and "गोवा कोंकणी" is incorrect. They should be "Gõychi Konknni" and "गोंयची कोंकणी" respectively. There's an open discussion on the community page of the Konkani Wikipedia to build the community consensus on what "Goan Konkani" should be called in Konkani.
  • I don't think it's a good idea to have an almost identical discussion both here and on the community page, about what the language should be called. I suggest waiting till there's a conclusion of the community discussion, and then just following that conclusion here.
  • I don't know how you you arrived at the figure of 12% for Kannada articles, I would estimate it to be around 5%. One reason for your figure to be off might be that while Devanagari and Kannada articles have completely been imported, Roman articles are still being imported from Incubator.
  • Given the small number of Kannada articles and the marginal activity in the Kannada script, it seems to be kind of taken for granted by the community that the label for "gom" should contain only the Devanagari and Latin names. This isn't to imply that there are fewer people who use the Kannada script in real life or that Kannada is less important in some way than the other two, just that Devanagari and Latin names are more representative of what the Konkani Wikipedia is today. However, if you still feel that Kannada should be included in the label for "gom", then I think it would be better to put this before the community and see what they have to say about this.
The Discoverer (talk) 18:52, 18 July 2015 (UTC)
Thanks for your comments, The Discoverer:
  • If and when there is consensus that the Latin and Devanagari names should be changed in MediaWiki, I'll be happy to update the portal accordingly. I'm aware of the discussion at gom: and will be monitoring it. In the meantime, we need some link text for the link to gom:, rather than omitting mention of this 100+-article wiki entirely.
  • There are 45 articles beginning with "Kd/" (versus 226 beginning with "Dn/") and 372 articles total, thus 12%. However, I was unaware that the Latin script articles are still being imported. If the gom: community is unable to come up with a full Kannada transcription of the language name, then we should remove the partial transliteration from this portal.
 – Minh Nguyễn 💬 04:41, 22 July 2015 (UTC)
The Konkani Wikipedia was begun in 2006 in Incubator as a Latin script Wikipedia and thus the Latin pages are unprefixed. Eventually, when Devanagari pages began to be added, they were prefixed Dn/, and similarly, Kannada pages were prefixed Kd/. A few years ago, the number of Devanagari articles overtook the number of Latin articles. Therefore after the Konkani Wikipedia was established, the trend is not to prefix Devanagari articles. Hence, you will find that there are far more than the 266 articles in Devanagari, and that the count of 372 on the statistics page is also way off the correct figure. It seems to me that the only way to get an accurate percentage would be to manually count the pages on gom:Special:AllPages :) My guess would be 55% Devanagari, 40% Latin, 5% Kannada. The Discoverer (talk) 07:04, 22 July 2015 (UTC)
Yes check.svg Done I've updated the link text according to the final proposal at gom:विकिपीडिया:समाजाचे मुखेल पान#Final Vote. Thanks for your help! – Minh Nguyễn 💬 10:36, 26 July 2015 (UTC)
In the discussion, the consensus was that the label should be "कोंकणी / Konknni". As explained above, we want to leave out the Kannada script for now. The Discoverer (talk) 09:41, 27 July 2015 (UTC)
Yes check.svg Done – Minh Nguyễn 💬 04:23, 28 July 2015 (UTC)
Thanks Minh Nguyễn! The Discoverer (talk) 11:10, 28 July 2015 (UTC)

South Azerbaijani transliteration[edit]

@Mjbmr: w:Azerbaijani language#South Azerbaijani currently gives a romanization of "Türki"; is this incorrect? I couldn't find any evidence of "Türkçe" being used for South Azerbaijani as opposed to Turkish, but please correct me if I'm wrong. – Minh Nguyễn 💬 21:27, 30 August 2015 (UTC)

@Mxn: In Persian, we call Turkish language: Turki, and South Azeri language in Iran is also called Turki; sometimes Turkish language is called Istanbulic Turkish to avoid conflict, Türkçe is how the way Turkish is spelled in South Azeri which is equal to تۆرکجه or تورکجه in Arabic script, see gerrit:209673, but you nailed it, I'm gonna put a code review to change it to گۆنئی آذریجه which means South Azeri not Turkish. Mjbmr (discussioncontribs) 21:33, 30 August 2015 (UTC)
How confusing! From your description, it sounds like speakers of South Azerbaijani wouldn't refer to their own language as گۆنئی آذریجه (South Azerbaijani); in that case, تۆرکجه or تورکجه would be preferable for this portal. If it's really the case that تۆرکجه is transliterated "Türkçe", it shouldn't be a problem that it matches the link text for Turkish. That surprised me, but if it doesn't surprise native speakers then there's no problem. The goal is to help speakers of both languages recognize their language from the list; the transliterations in title attributes are for computers with inadequate font support. – Minh Nguyễn 💬 21:56, 30 August 2015 (UTC)
The native name of South Azerbaijani language is تۆرکجه and international name is South Azerbaijani. --Ebrahimi-amir (talk) 05:39, 14 September 2015 (UTC)
@Ebrahimi-amir: What would the romanized (transliterated) form of تۆرکجه be? We put transliterations in the tooltips, not English translations. – Minh Nguyễn 💬 08:39, 14 September 2015 (UTC)
Ok. So "Türkçe" is wrong. ç=چ=ch and ج=j in english.--Ebrahimi-amir (talk) 09:24, 14 September 2015 (UTC)
According to basic logic "Türkce" is a better match.--Ebrahimi-amir (talk) 16:40, 14 September 2015 (UTC)