Wikisource:Scriptorium/Archives/2016

How to revitalize mul.source

I re-opened an old issue into wikisource-l, titled "Errare humanum est, perseverare diabolicum", about the real need to split wikisource into language specific projects. I realize that different families of languages need different software settings and good translations of help pages, and differences in alphabet are a terrible obstacle, but.... as a matter of fact, some basic knowledge of latin alphabet and of English language is needed dealing with html and any programming language, isnt't it?

To revert that decision, it probably impossible; nevetheless mul.source IMHO should be strengthened as much as possible, and best users should be strongly encouraged to work into it. This could be done removing any language-related limitation, allowing to load here any text into any language, in particular multi-language texts; hopefully, this would encourage those users to import here best scripts, best templates, best policies from their language-specific projects. --Alex brollo (talk) 09:14, 9 December 2015 (UTC)

mul.source is strengthened by use and support, it has still an active role on PD works for some of the active communities (like pl.source). About language-related limitations: there is certainly no limitation other than the technical. This is the multilingual wikisource, so we accept PD-US & CC-BY-SA source texts in all the languages... check the Wikisource:Language_policy... Sure, we need, we encourage, and we import policies / manuals / templates /ideas from other projects at our pace and speed... but I don't get the point on how to improve other than keeping alive and working this community... ... I hope the response is not going in a direction that forces any community to stay here (or being expelled from here)... if they don't want to...--C.R. (talk) 10:35, 9 December 2015 (UTC)

• • po pierwsze primo, próba realizacji w ten sposób dyskusji o "rewitalizacji" projektów językowych dyskryminuje osoby nieanglojęzyczne. W mojej ocenie takie postawienie sprawy ma spowodować osłabienie projektów językowych, w których z takim trudem budowano społeczność, zasady, itd...., - z zasady na mul zamieszczamy teksty, które są PD według prawa w us, a nie weszły do PD w kraju, co do tekstów wielojęzykowych, to społeczności także wypracowały swoje zasady ich obróbki. Takie propozycje przedstawiane i prowadzone w ten sposób, w jaki robi to Alex będą skutkować jedynie "rozrzedzeniem" projektów językowych (szczególnie małych) i w efekcie ich osłabieniem, nie wspominając o dezorientowaniu wolontariuszy, problemach ze zrozumieniem (szczególnie dla nie znających j. ang.), redudancji prac nad tekstami i ogólnym bałaganem. W mojej ocenie pomysł utopijny, podkopujący piękne dziedzictwo Żródeł, mający na celu jedynie osłabienie projektu Wikiźródeł jako całości.  Oppose Zdzislaw (talk) 10:50, 9 December 2015 (UTC)

As it is probably evident, English is not my language. Far from weaking minor projects, my aim was to avoid the pain of "rediscovering the wheel" more and more times, centralyzing here the best from major projects. So perhaps I'd like to weak the major ones, not the minor ones. Please take a look to the discussion in wikisource-l for pro and cons; my aim here is only to let mul.source users known about that discussion. --Alex brollo (talk) 14:24, 9 December 2015 (UTC)

The mailing list: Wikisource-l - November;--C.R. (talk) 14:41, 9 December 2015 (UTC)

Thanks C.R. About oldwikisource-mul.wikisource: how can I link mul.source pages (work or author item) to wikidata? I tried some time ago and I failed; where I was wrong? And I tried Match & split tool, and I failed; where was I wrong? Have been these troubles solved by now? Alex brollo (talk) 15:46, 9 December 2015 (UTC)

The link to oldwiki-mulwiki is not implemented yet in wikidata, as far as I know... however T73406... Match & split tool is new for me... try the guidelines here, that seem quite cross-wiki to me :)--C.R. (talk) 16:25, 9 December 2015 (UTC)

I have read this discussion. The thesis posed by Alex totally not appeal to me. The matter is... turned upside down. The point of view of readers is totally disregarded! I maintain everything I wrote before. Such movements confuse readers and position in the local (language) "reading market" built over the years - eg building awareness among e-book readers users (currently approx. 6k downloads per months in e-book formats). Moving texts to mul also cause clutter, confusion and blurring of volunteers communities painstakingly built over the years. Zdzislaw (talk) 16:17, 9 December 2015 (UTC)

I tried again to link Author:Eduardo Scarpetta to its wikidata item, I failed. Here my talk about M&S tool & mul.wikisource: https://fr.wikisource.org/wiki/Discussion_utilisateur:Phe#M.26S_bot. I'd simply like that any new template, Lua script, wikidata setting, export tool..... would be tested first here, so converting mul.source into a "idea incubator" too; @C.R.:, how you can imagine to export & effectively use M&S tool into nap.source, if you never tried it here (and you can't!)? How train users using minor languages hosted here to wikidata linking, if linking to wikidata is impossible? In my vision, I'd like that this project - being an "incubator" for new local projects - was the best one from any point of view, and that best developers should feel themselves obliged to test here their best ideas. I'd like to find here, i.e., the marvellous "mise en page" of fr.source, the hOCR tool by Phe, the beautiful FreedImage from en.source, the memoRegex from it.source.... and what about policies and marvellous works of de.source, that I can't study at all, since German language is too hard for me? But I imagine too, that lots of unknown, useful tools have been developed into minor projects. What's a better place to share ideas, tools, templates, but here? --Alex brollo (talk) 17:17, 9 December 2015 (UTC)

The place is good and all the languages, tools and people are welcome. Pre-1923 works can be, without any doubt, prepared here until the details of the license are clear for the target-country readers. So mul.wikisource is not only a good incubator but a good buffer -and a good front-page for the neapolitan-speaking US community (sorry)-... On why some communities kept it as a low priority, without helping to exploit the tools and synergies, I don't know... I can tell you the main obstacle right now for napsource is that we've been on-hold without discussion for 4 years... as if we were invisible... we have enough workload on pre-1923 unclassified works to continue working here, just see Category:Napulitano, so right as our polish counterpart, we will keep visiting the place... -C.R. (talk) 17:40, 9 December 2015 (UTC)

(minor additional comment)--C.R. (talk) 17:57, 9 December 2015 (UTC)

The opening of this thread is not only OK but necessary. Since years we did not talk about this, about the very profund questions of this project. We have a chaos here now. Thousands of copyvio pages. Every ip can edit here in pages, whose languages nobody understand. Yes, let's talk about it. -jkb- (talk) 01:16, 10 December 2015 (UTC)

I contributed here a little bit, both into multi-language works and into neapolitan, but I wasn't aware of troubles mentioned by -jkb-. Really anonymous contribution into unknown language could be a major trouble - copyvio being one from less alarming features. Here a rather bold suggestion (considering that here best practices should be implemented and encouraged and that there are serious safety issues): to allow only proofreading procedure based on Commons printed, well-sourced images. --Alex brollo (talk) 08:31, 10 December 2015 (UTC)

Again, two cents:

1. In order to solve effectively the question that alex is posing: I suggest you to open a decision process on every wikisource with a clear proposal to achieve a consensus on the convenience of coming back to the oldsource. For sure you will find new arguments apart from those given: -we rather need small & motivated communities devoted to the language; -we serve our minority community of readers/contributors/researchers; -the license restrictions of commons impedes you to load e.g. copyrighted Italian material even if it is PD-US, ecc...;
2. In order to revitalize wikisource, I suggest you to use it, to help to solve bugs... etc..., copyvios may exist in all the wikis... templates may be broken as well... I am sure the detection time is lower in the active and expert wikis ... and if this is a chaos, maybe some motivated sourcer can help us to categorise and put everything in order... I wanted to make the point that we are open and alive, even if some communities don't know that we are still operating. In fact, we serve the original scope of putting all the source-PD-texts available to any person, in any language... For example: this scope has been trunked in itsource, where even simple translations are forbidden. I agree with the final aim of making this wiki active, but i strongly disagree that the domain separation is a failure;
3. If it is of use for you: I came here for research, to discover the neapolitan iceberg. I feel empathy with other colleagues in our situation. I came here because google-books/internet/IA is a mess, and I want as much PD texts as I can get in the same platform, with a good frontpage and in my language, so I can contribute/read from the first day even if I have an US locale setting: this must be an Out Of the Box Feature... and not only... domain separation allows it to be available even before you enter here (search unification vs search in language specific wiki: FYI... there are 111> neapolitan targeted words but they are again on the lowest part of the iceberg between a bunch of 2000 multilingual entries). I want the domain to be able to source nap.pedia also.... The domain is a great tool, that may help researchers/readers/learners in order to appreciate the literature (sources are literature) in my language... OOTB... so why should I renounce to it only because, technically, the unification "seems" better? Have you ever tried in google to search texts in minority languages? --C.R. (talk) 16:43, 10 December 2015 (UTC)

ad. #1: Putting such proposals "in bulk" "on every wikisource", as a result of "the idea of" one user (I have not noticed that such a proposal he put on his local it wiki), in my opinion, is an highly detrimental action to the project. The only effect of such actions include: unnecessary divisions between local users, leaving volunteers, stratification of local language projects (for oldwiki and local) and endless discussions - especially in small and medium-sized projects, in which the community, the principles and the content has been built over the years. It's a very bad strategic decision (after many years of hard work on the development of local communities opening a decision process on every wikisource), if you want to weaken the local sources, do not make the atmosphere of "artificial willingness", but say it openly. Zdzislaw (talk) 17:24, 10 December 2015 (UTC)

Sorry Zdzislaw, from my ignorant opinion... I see much more dangerous targetting the question in english to mulsource & the mailing list (biased towards a naturally multilingual community)... and then get the wrong impression/consensus...--C.R. (talk) 17:44, 10 December 2015 (UTC)

Re-reading, you are right I formulated point 1 in a very straight way :D --C.R. (talk) 17:49, 10 December 2015 (UTC)

Alex, the main thing which is missing here is to precise which goals you wish to achieve by wikisource merge. Then we can gather advantages and disadvantages of the merge and perform a reasonable discussion. As billinghurst pointed you in the mailing list, without such information we discuss about pure ideas or just about nothing. So if you seriously think about the merge, a discussion about the merge should be performed here, and likely in all other wikisources (communities decissions are even required by WMF rules), but not at the moment.

I agree that your idea of multilingual library is good but this idea should be done in a way that is not destructive for existing projects (is it is ever possible). However, my first thought about it was: it should not be done by merging projects, but by creating a new one that gathers necessary information from others (sth like "reverse" commons). But don't treat this as a serious proposal; I am even not sure if it is technically possible.

Separate projects has their own rules. Eg. in plwikisource we decided to require the uploaded texts to pe also PD in Poland, not only in US; we require new texts to have strict bibliographic source (which is difficult to require here, partially because of the language barier), etc. Recently, we also had a vote to go in opposite direction than yours: separate old-Polish texts out of plwikisource. They have their own communities (in most cases, except dead or almost dead projects) and I, personally, doubt if they all can share your point of view (that is required for full merge).

But for your initial sentence: "This could be done removing any language-related limitation, allowing to load here any text" I say: NO. Allowing a user to choose whether they want to upload a text into a separate lang.wikisource or here is the worst idea. The rules concerning this should be strict. Otherwise users will come here with texts that were rejected elsewhere. Ankry (talk) 19:32, 10 December 2015 (UTC)

Ok, I see that there's no agreement about the hypotetical (and, I admit, utopic) goal of reversing the long-standing wikisource split, nor about the freedom to upload here texts of any language. There's perhaps some agreement about the need to share (and centralyze, since "if you are repeating yourself you are going wrong") best wikisource tols, gadgets, templates, scripts? Have a multi-language contributor to study local, fastly changing complex settings any time he contribute to a different project? Does this fastly growing difference between projects make simpler to implement new extensions? Are mul.source users happy from being excluded from wikidata? Is so fuzzy idea, to ask strongly that, as an incubator, mul.source should offer the best from wikisource skills and experiences? And if this is not a fuzzy idea.... how do it? Alex brollo (talk) 21:16, 10 December 2015 (UTC)

That is not exactly what I meant: If local wikisource has extra limitations concerning eg. copyright of texts except US copyright, the texts that do not fit language-specific wikisource requirements but are PD in US can be uploaded here. Eg. pre-1923 texts copyrighted in home country in some cases. Note, that in such cases, source DjVu files are likely also incompatible with commons requirements, so they are uploaded locally (if ProofreadPage is used).

Also, there were requests to add support for mul.wikisource in wikidata, but AFAIR they were rejected. I do not remember why; you should dig in phabricator to find the precise reason. So whether we are happy or not is irrelevant: we can do nothing with wikidata support at the moment, I am afraid. However, If you find wikisource as a suitable place for handling scripts, etc. you are welcome. Ankry (talk) 22:19, 10 December 2015 (UTC)

@Ankry: About wikidata: what about shouting, if asking turned out ineffective? IMHO the wikidata issue is the proof of a deep, severe trouble into mul.source settings; it should be fixed as soon as possible. --Alex brollo (talk) 00:36, 12 December 2015 (UTC)

@Alex brollo: Do we really want interwiki links to mulws, betawv, and incubator? —Justin (koavf)❤T☮C☺M☯ 05:20, 12 December 2015 (UTC)

@Alex brollo: I realize that 1-1 interwiki mechanism is a solution not suitable for wikisource. So while I find it potentially usefull for mul.ws (even if only a single link is allowed) I do not think it is worth "shouting". However it seems to me thare's nobody skilled enough/interested enough/having enough time to develop an acceptable alternative to 1-1 interwiki for wikisource (I think it is worth shouting; but where?).

@Koavf: unsure about incubator and copletely no idea about betawv (as I do not know these projects). But in mul.ws we have many texts in languages that will never have their own subdomain and the texts are worth to be linked some way to other ws. Thre are likely some conflicts like the same text in more than one minority language, but they are rather rare. I much more often encounter conflicts inside large ws sites (en/fr/ru/pl) that provide more than one edition/translation of the same text and they need to be linked some way together using interwiki-like mechanism. The Bible is the key example (eg. you are here and wish to find translations of this section to English/Swedish/Russian/Arabic and/or the Latin original; especially difficult if you do not know these languages). Ankry (talk) 10:14, 12 December 2015 (UTC)

Interwii linking is now possible using the prefix "mul" (see cross linking between it:Indice:Basile - Lu cunto de li cunti, Vol.I.djvu and Index:Lo cunto de li cunte - Tomo I.djvu manually adding links. --Alex brollo (talk) 14:55, 12 December 2015 (UTC)

@Alex_brollo:, minor comment: for that specific case, maybe the interwiki should be used pointing the itsource namespace Opera... those are different editions... it may be ok for the moment, since iw provides cross-wiki awareness--C.R. (talk) 22:09, 12 December 2015 (UTC)

@C.R.: Excellent idea! I don't know id mul.surce is aware of subtle reasons (mainly related to wikidata) inspiring the idea of a Work: namespace, nor I know if such a namespace has been activated here, but we could too to use a "pseudo-namespace" Work: and link its items with it.source Opera: .... perhaps someone will ask us for details. --Alex brollo (talk) 13:04, 13 December 2015 (UTC)

We have many useful pages here. Subdomain coordination seems good. A few language subdomains ban Wikisource translations, so how about adding separate translation namespace to revitalize here?--Jusjih (talk) 00:03, 30 March 2016 (UTC)

Wikimania 2016 Scholarships - Deadline soon!

Please help translate to your language

A reminder - applications for scholarships for Wikimania 2016 in Esino Lario, Italy, are closing soon! Please get your applications in by January 9th. To apply, visit the page below:

• Wikimania 2016 Scholarships

Patrick Earley (WMF) via MediaWiki message delivery (talk) 01:49, 5 January 2016 (UTC)

Tech News: 2016-02

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Wikimedia no longer uses visitor statistics from comScore. [1]
• You can make interactive graphs with the Graph extension. There is now a tutorial for how to do this. [2]

Problems

• Some pages do not turn in up in categories where they should be. This is because link tables are sometimes not populated. [3]

Changes this week

• The Nuke extension will work with Flow. This will make it easier to handle spam in Flow. [4]
• New file uploads will now be patrollable. [5]
• Internet Explorer 8 will no longer have JavaScript support. You will still be able to browse and edit Wikipedia if you use Internet Explorer 8, but will not be able to use some features. This can be solved by upgrading to a newer version or switching to a different browser. [6][7]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 12 January at 20:00 (UTC). See how to join.

Future changes

• URLs in the recent changes IRC feed will no longer be rewritten to unencrypted HTTP. This could be a breaking change for bots dependent on the IRC feed. [8]
• The edit tabs for the wikitext editor and the visual editor will be combined to one single edit tab. You will be able to choose which one you prefer. If you are not logged in, your choice will be saved as a cookie in your browser. You can test the single edit tab. [9][10]
• There is a beta feature that adds links to the subject on other Wikimedia projects. This works much like the links to for example Wikipedia articles in other languages. It will go out of beta testing and be enabled for everyone in January. Wikis that don't want this can decide to have it disabled. [11][12]
• The difference between "alerts" and "messages" notifications is unclear to some. The developers want feedback at the Phabricator task or on MediaWiki.org so they can make this better. You can give feedback in your language if you can't write in English.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:59, 11 January 2016 (UTC)

Please help to settle harassment by admins on Czech Wikisource

Hi, in May 2015 I saw an act of harassment by admins on Czech Wikisource (a user got a week ban for replying "don't troll" after an admin interrupted a discussion with a totally unerelevant post - the admin was indeed trolling). In response to this harassment I posted a question to the local Village pump if the site has any admin vote rules and admin election archive. My question was never answered and I was promptly banned indef (!!!) for it. Yes, I'm not kidding, I was banned indef for posing a question on site rules. Please note that I was never doing any vandalisms or something like this on Czech Wikisource. I was a problem user on Czech Wikipedia many years ago (2006) but all of this ended a long time ago. I edited Czech Wikisource from several accounts but I did constructive edits only. I added more than 20 entries from Otto's encyclopedia, corrected typos and pointed out some page names may be misspelled (which was proven). There is absolutely no reason for me to be banned indef on the site.

Why I was banned? Because local admins hate me. 1) -jkb- hates me because many years ago (2006) I supported his archenemy VZ on Czech Wikipedia. (-jkb- managed to drive away the "founder" of Czech Wikipedia from the project) 2) Milda hates me because I started the vote on his desysop on Czech Wiktionary (and he was eventually really desysopped). 3) Danny B. hates me because because I started 2 votes on his desysop on Czech Wiktionary - both of them showed that there was no consensus for him to be an admin but he keeps his "buttons" anyway.

You can see more details on this case in a RfC on meta: meta:Requests for comment/cs.wikisource admins. Thanks to all!! --Auvajs (talk) 16:01, 17 January 2016 (UTC)

This seems to be a pretty entangled and complex situation. It's seems to me that the block was maybe a bit rough and unfair but I don't see what oldwikisource has to do with it. I feel like it should be settled either on cswikisource or on meta. Cdlt, VIGNERON (talk) 18:21, 20 January 2016 (UTC)

1) m:Requests for comment/cs.wikisource admins, 2) cs:Wikizdroje:Nástěnka správců/Poznámky k blokům, trully -jkb- (talk) 23:00, 20 January 2016 (UTC)

I have no blind confidence on admins. Neither on users. But if we compare (a) a banned user who confesses having had multiple accounts, and having been "harassed" and/or banned several times by several admins in several wikis (Wikipedia, Wiktionary, Wikisource), and who spams against the admins who blocked him, and (b) 3 admins who don't disagree with the ban (and keep in mind what being an admin implies, and the rules that apply to them), then I have a very much more confidence on cs.source admins. -Aleator 00:46, 31 January 2016 (UTC)

Tech News: 2016-03

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You will be able to find or mark bugs and suggestions in Phabricator that are specific for your language or wiki. [13]
• Notifications have been upgraded with more detailed and easier-to-access information. See the documentation. Cross-wiki notifications will be available soon on the two test wikis. [14]

Changes this week

• The visual editor uses the TemplateData extension to make editing templates easier. You will now get a warning when you edit a TemplateData form and leave it without saving. [15]
• MediaWiki will get a new authentication and authorization system called AuthManager. This is planned to happen in a month or two. Some bots will need to change how they log in. Two new and more stable authentication methods will be available now: Owner-only OAuth credentials and bot passwords. You can read more about the change. [16]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 19 January. It will be on non-Wikipedia wikis and some Wikipedias from 20 January. It will be on all Wikipedias from 21 January (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 19 January at 20:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is governance model. The meeting will be on 20 January at 22:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:55, 18 January 2016 (UTC)

2016 WMF Strategy consultation

Please help translate to your language

Hello, all.

The Wikimedia Foundation (WMF) has launched a consultation to help create and prioritize WMF strategy beginning July 2016 and for the 12 to 24 months thereafter. This consultation will be open, on Meta, from 18 January to 26 February, after which the Foundation will also use these ideas to help inform its Annual Plan. (More on our timeline can be found on that Meta page.)

Your input is welcome (and greatly desired) at the Meta discussion, 2016 Strategy/Community consultation.

Apologies for English, where this is posted on a non-English project. We thought it was more important to get the consultation translated as much as possible, and good headway has been made there in some languages. There is still much to do, however! We created m:2016 Strategy/Translations to try to help coordinate what needs translation and what progress is being made. :)

If you have questions, please reach out to me on my talk page or on the strategy consultation's talk page or by email to mdennis@wikimedia.org.

I hope you'll join us! Maggie Dennis via MediaWiki message delivery (talk) 19:07, 18 January 2016 (UTC)

Main Page

Just FYI: I have made the numbers there consistent with statistics on meta. It seems that for about a month only main and Author namespaces are counted in these statistics (while Page and Index are no more). IMO, this is a resonable change. Ankry (talk) 10:09, 24 January 2016 (UTC)

I respectfully disagree; IMHO nsIndex and nsPage are the most important ones, really NPOV, while ns0 are merely derived works/derived editions; but I realize that my opinion isn't so much shared, most wikisourcians see nsIndex and nsPage simply as "transcription tools". --Alex brollo (talk) 11:07, 25 January 2016 (UTC)

@Alex brollo: I generally agree with you, but I also think that statistics should be kept in a consistent way. If some Wikisource projects use ProofreadPage as the main tool, the pages in main namespace may be even created by bot basing on page/metadata information. However not all Wikisource use actively ProofreadPage extension (eg. Russian, Hebrew, Chinese) and while different technology is used to create content I see no better way than to compare number of pages in main/Author namespace (which is still not the best way as pages may be tiny and large). While user contribution should be counted basing on Page/Index contribution also (here it is not). However, maybe the best way is just to count content in bytes?

I also noticed that eswikisource people place books' pages content directly in the main namespace. I wonder why. Ankry (talk) 07:16, 28 January 2016 (UTC)

A sound reason could be, to export book "as it is", i.e. saving pagination too (a very important TEI element, I'd like that nsPage could be exported too); an unsound, but probably true reason, could be to "win a statistics competition". :-( --Alex brollo (talk) 07:41, 28 January 2016 (UTC)

@Alex_brollo: is there a phabricator entry on the nsPage export need? it would be interesting!--C.R. (talk) 09:04, 28 January 2016 (UTC)

@C.R.: I don't know, but when I tried to underline the great significance of nsIndex and nsPage, I didn't found any enthusiasm about. "NsIndex and nsPage are transcription tools" is the largely prevailing opinion. Alex brollo (talk) 10:18, 28 January 2016 (UTC)

@Alex_brollo:: Using Page namespace for book presentation (instead of putting pages in the main namespace for this) and information from Index page about pagination may be a nice enhancement to the ProofreadPage; @Tpt, Phe, Zdzislaw: what do you think of this idea? The way es people has chosen has a disadvantage: at the moment they have not a full-text page nor an index page required to generate PDF/ePub/mobi ebook. But this is their choice... Ankry (talk) 13:50, 28 January 2016 (UTC)

Hi, I don't think your edit shows the reality. Regards, 88.182.181.224 13:17, 21 February 2016 (UTC)

@Yann: the changes are entirely consistent with official data, it is consistent with the definition of "articles": "$wgContentNamespaces exists to allow custom namespaces to be acknowledged as containing useful content for the purpose of Special:Random, Special:Statistics, and {{NUMBEROFARTICLES}}". Changes were discussed and carried out on phab:T54709#1735526. Zdzislaw (talk) 13:39, 21 February 2016 (UTC)

Sorry, I can't log in (some bug).

This is certainly closer to the real volume of content. Regards, 88.182.181.224 14:54, 21 February 2016 (UTC)

Yann, is this the right screenshot? --Zyephyrus (talk) 10:32, 22 February 2016 (UTC)

Phe's graph

Yann seemed to indicate the transclusions (not proofread (per day???)) - so, rather this graph. Zdzislaw (talk) 11:03, 22 February 2016 (UTC)

In 2009 the PageViews figures had been the chosen solution and some kind of criteria mix had seemed to be an interesting idea too. There were problems with articles (see here): what is a "good article" in the different wikisources and how can we count them? --Zyephyrus (talk) 20:06, 21 February 2016 (UTC)

No consensus either on French WS for the time being. Ideas? --Zyephyrus (talk) 10:13, 22 February 2016 (UTC)

@Zyephyrus: I really do not understand why did you undo an Ankry edit, who updated the statistics exactly according to the same source, they were updated previously in 2015? If the community (without any consensus), removed Page and Index namespaces from the variable defining the "contents" of wikisources for statistics (phab:T54709#1735526, [17]), why now "the circle" has to be updated using a different basis than so far? Zdzislaw (talk) 11:32, 22 February 2016 (UTC)

At the very least, if you change the numbers, you need to change what is shown (texts, not pages). IMHO, pages are a much more objective criteria. What is a page is quite similar in any language, where what is a text varies wildly across languages.

Now if we want to show the numbers of texts, this graph gives an indication (number of proofread texts), but incomplete as some languages have a large number of non-proofread texts.

Page views would be another objective criteria. This is quite independent of the volume, quality, and activity of a particular language. Yann (talk) 13:41, 22 February 2016 (UTC)

@Yann: what is shown? "text" is still a page in main NS. On the "circle" there was shown a number of good pages shown at column "good" of this table (see: 06.2015 table and this edit). Until November 2015 it was the sum of the wikisource "content" - a number of "pages" in Main (texts), Page, Author and Index namespaces. In November 2015 wikisource community decided to change the "content" for the Wikistats by removing a Page and Index namespaces from the variable (phab:T54709#1735526, [18]). So from November 2015 statistics includes only the sum of pages in Main and Author namespaces. But they are still "content pages". From 11.2015 these pages are shown in the statistics, on meta:Wikisource and by {{NUMBEROFARTICLES}} word. So, if we decided to remove Page and Index namespaces from statistics and leave only pages in Main and Author namespaces, consequently we should update the circle on the same way (from the same source of data).
I agree that the number of pages in Page namespace much better reflect the wikisource content, but... if so, why we removed them from the variable that defines "contents" of our statistics? Zdzislaw (talk) 14:58, 22 February 2016 (UTC)

@Yann, Zyephyrus, Zdzislaw: I am sorry for long delay to my response, but I am out of computer this week and mobile phone editing is not so easy... However I wonder why this discussion is held here instead of Scriptorium, where I did notify about the change and its rationale about a month ago and I am still awaiting feedback there. I think that there was consensus (nobody oposed strongly) that the main page numbers should be based on the official wikisource stats available on meta. @Yann, Zyephyrus: if you disagree with that, please suggest what the numbers should be based on (in your opinion) taking into account that many wikisources do not use ProofreadPage at all (eg. Chinese).

I strongly disagree that keeping outdated numbers on the main page is the best idea and I am suggesting to remove the numbers totally instead of reverting current values to outdated ones. Ankry (talk) 17:50, 23 February 2016 (UTC)

PS. could sb. move this discussion to Scriptorium, please?

Done --Zyephyrus (talk) 18:19, 23 February 2016 (UTC)

Hi, I don't understand how we have such differences between this table and this one. We should have similar figures for both if we add texts "with scans" and "w/o scans" for languages which use the proofread system. For en.wikisource, we have 566,972 vs. 334,207. What are these 232,735 pages which make the difference? For fr.wikisource, we have 251,220 vs. 193,781. Even including author pages (7,685) and disambiguation pages (1,899), we are far from the total. Regards, Yann (talk) 11:38, 25 February 2016 (UTC)

@Yann, Zyephyrus, Ankry, Tpt, Phe: Let me explain... Once again I looked through the mediawiki code and its ws onfiguration regard to statistics.
The present state after changes: [19], [20] and [21]:

• for wikisource statistics content, the namespaces which are considered generating a count of the number of articles in the ws are MAIN, PAGE, AUTHOR and INDEKS NS (and a few specific ns defined in initialiseSettings.php - e.g. Translation NS for en wikisource)
• to the page with all these NS were classified as "a good" (taken to stats) must satisfy the condition contained in the variable $wgArticleCountMethod - for all ws this is 'default' => 'link' condition - that is means "the page must contain a wiki link to be considered valid"

In summary, for the number of pages in the stats are taken into account almost all the pages of MAIN NS (such sites wikicode contain almost always at least a link to the category), and only the pages of the Page, Author NS which in its wikicode include a internal link (e.g. this page is counted as "good" for the stats because there is at least one wiki link in wikicode, but... this not -> in my opinion this is a "stupid" way of ws content calculation)

As a result, for fr ws now we have 251 369 such pages which is consistent with this table

• Therefore, I suggest that:

1. (as e.g. for scwikinews) to change the way of counting in $wgArticleCountMethod to 'any': all pages are considered as valid articles by opening Wikimedia-Site-Requests (to change InitialiseSettings.php for all ws) at Phabricator
2. after that updates the article count UpdateArticleCount.php.

Zdzislaw (talk) 14:24, 25 February 2016 (UTC)

Hi, Sorry for replying so late.

Whether there is an internal link should be completely irrelevant when we use transclusions with <pages>. IMHO, we should count all pages in MAIN NS and AUTHOR NS (and possibly others: Portail?). Regards, Yann (talk) 07:40, 20 March 2016 (UTC)

Tech News: 2016-04

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now follow when pages are added or removed from a category on German Wikipedia. The plan is to add it to Wikimedia Commons and other Wikipedias this week. [22][23]
• Administrators can hide individual entries of a page with RevisionDelete. There is now a button to choose "all", "none" or "inverse" in Special:Log. The article history will get the same buttons soon. Wikis that have done this locally with JavaScript will be able to remove that code. [24]

Changes this week

• You will be able to see the references when you preview a section you are editing. This will happen even if there is no <references /> tag in that section. [25]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 26 January. It will be on non-Wikipedia wikis and some Wikipedias from 27 January. It will be on all wikis from 28 January (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 26 January at 20:00 (UTC). See how to join.

Future changes

• There is now an extension called ArticlePlaceholder. It can automatically generate content on Wikipedia with data from Wikidata if there is no Wikipedia article. It will have a tag to remind the reader it is not an article and ask the reader to create one. The developer is now looking for smaller Wikipedias that want to try the extension. [26]
• The OTRS system will be upgraded. The plan is to do this on 3 February at 08:00 (UTC). It will probably take 6 to 8 hours. OTRS will be down during the upgrade. [27]
• Users will soon be automatically congratulated when they reach some edit count milestones. [28]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:38, 25 January 2016 (UTC)

OTRS

As Ankry has suggested on my talk page], and as I support this idea, we could rather need an access to OTRS dealing with (not very often) Problems here in this domain (see also the following thread on copyvios). If it should be an access for Oldwikisource only or for more / all Wikisources - no idea. I was several years ago in the OTRS team but then I left it. I see the following possibilities:

• if there are some OTRS members from the en-Wikisource, migt be they could take care off our problems as well
• we suggest somebody (how many users?) from us who do it
• combined both

But as Ankry suggested, the multilinguality shoud be established somehow. Opinions? -jkb- (talk) 15:15, 30 January 2016 (UTC)

can we use the template we use in meta for multilingual pages? I don't now how to import it, I am very bad at templates. OTRS understanding & clearance is a very powerful copyvio solving process. I am very interested in empowering the community to use it. It is very important to clarify our copyright needs and to solve any issue that involves the authors of the owners. I was actually working in the OTRS page in neapolitan (convergent evolution! :D), since I am working on the free release of some contents.--C.R. (talk) 20:05, 30 January 2016 (UTC)

I don't understand. I asked OTRS tickets for es.source in the past, and I found no problem.

Which template? meta:template:OTRS pending and meta:template:PermissionOTRS? (I see OTRS ticket is now being added here in license templates, as those pages in Category:Items with OTRS permission confirmed). Regards.-Aleator 01:03, 31 January 2016 (UTC)

Dealing with OTRS with users who speak at least one widely used language and know a bit about copyright is not a big problem. But the problem is that many people here do not even understand what copyright is what OTRS procedure is for and how does it work. The greater problem is if such people do not even understand any commonly used language. How to explain them anything? Where to redirect them to? Why should they look for information on another project, especially while this information is too general? Assume sb is ug-N, ar-2 and zh-1... I tried some time ago to explain OTRS permission requirement to a person who is kz-N, ru-2 and I failed with my ru-2. I asked for help a coleague who is kz-N, pl-4 and he also failed. It is difficult to explain new subjects to old people. And in most cases people will not tell you they do not understand a word. They will tell you nothing...

Note that most external OTRS pages are prepared to deal with images rather than with texts. Wikisource OTRS is a bit specific: we can choose only single license - CC-BY-SA 3.0. So all large sections about posible licenses and license choice have to be dropped and removed. Instead, we should explain why only this one licence is accepted. Also, if we do not have an OTRS information here, people often interprete this as "OTRS is not for this project" Ankry (talk) 11:17, 31 January 2016 (UTC)

As I can see we can import from meta, and we can change the template in the way we want (alternatively: we can create something like it here).

But I am not sure if we can produce a template in all minor languages we have here, it would be a chaos. Indeed, we should take some more main languages (like the meta template does), and if some people doesn't understand it, the must simply ask a person on their project for the help; possibly we could link such a text text to the google translator, as we can identify the language in the most cases. -jkb- (talk) 17:32, 31 January 2016 (UTC)

I think we can. If we have a reliable translation. OTRS agents may just compare ticket contents with the empty template. Ankry (talk) 17:46, 31 January 2016 (UTC)

Yo, actually (my confusion) I was meaning commons:Commons:OTRS. We can rely on that format or rather on a localisation split-phrased system like meta has. As long as the structure of the CC-BY-SA assertion response is similar to the "I hereby affirm that"..., fragment it should be possible to get it released. And yes, we need push-effort for translation on each language... if other wikis help us... then it's only win win.. :D--C.R. (talk) 21:44, 31 January 2016 (UTC)

Copyvios and how to deal with them

See first

• last entries in Wikisource:Proposed deletions, but alswo such elder ones like Wikisource:Proposed deletions#Pages created by User:Гүзәл Ситдиҡова
• last entries in Wikisource:Possible copyright violations, but also some elder ones like Wikisource:Possible copyright violations# Works of Firuza Abdullina and many others.

I am very sure that we have here a lot of copyvio pages. Some ones are clear copyvios (as especially users from amaller projects do not understand anything on copyright), and we have a lot of own works here, inserted by the authors or friends, wo claim "he/she is very important for the culture" etc. This is in contrary to one of the most important principle here "no original research no original works". If there are users who would like to change this, so there should be done a RFC or something like that, probably not only here but in a broader circle. I don't know, but I'm not very happy about this situation. Cheers - and give me some opinions. -jkb- (talk) 15:17, 30 January 2016 (UTC)

I agree, but it's very hard to counteract, as many of those languages are not understood (or in some cases even readable) by anyone except for those who add to them. The only thing that we can do, in my eyes, is be very strict about source indication and patrol all new pages to make sure that they either have a source or a copyright tag. --Ooswesthoesbes (talk) 12:42, 31 January 2016 (UTC)

Yep, that is our problem, more over multiplicated because even every IP can edit here without giving a summary for the edit. And Yes, the most users from small aand very small projects do not understand the principle of licence + source etc. For the future we could implementate a script that prevents saving the page without summary, and the footer should contain a very clear notice, that the page will be deleted if the licence, source is not given. Something like that.

But even so we have here the problem with the alredy created pages. I'm realy not happy with the sitaution, but how should we manage such problems like here or here? We are discussing with the authors, in one case a very long time, when they do not mind our questions and continue edititng? I deleted the malayan pages today as I do not think we can tolerate such copyright violations. (And yes, I know that we know a very small percentage of such pages, because we cannot read it... but if we find something, so we should act somehow.) -jkb- (talk) 17:45, 31 January 2016 (UTC)

@-jkb-: It's hardly a perfect solution but we could encourage users who have CC-NC/ND texts to go to http://wikilivres.ru/ and users who want to publish their own works to http://soulibre.ru/ —Justin (koavf)❤T☮C☺M☯ 03:20, 1 February 2016 (UTC)

Another way (a little bit hard) could be something similar to German wikisource policy, t.i. to allow proofread uploads of published, printed books only with a complete frontispiece image. It would be a great learning opportunity for users of smaller project and, on the same time, it would be simpler to check uploads by sysops.Alex brollo (talk) 08:01, 1 February 2016 (UTC)

I think a mandatory edit summary and better notice are very good ideas for a simple start.

I am not sure how to handle the pages that are already created. Obviously, it is impossible for us to check all the pages one by one. The best policy that we can have, in my eyes, is that when concerns are raised, we contact the uploader of the text, and if he does not respond, we consider it a copyvio and delete it.

I do not really feel something for the German policy, because it can really be a death warrant to smaller language projects. While I agree with your argument that it would be a great learning oppertunity and it would make things easier to check, I have a big objection. I am familiar with Limburgish publications, and in most cases they are self-published, which makes it very difficult to check whether they are copyvios or not. My other objection would be that it increases the threshold for users to get engaged with wikisource. --Ooswesthoesbes (talk) 22:28, 2 February 2016 (UTC)

Some thoughts to two points from above:

• how to deal with existing pages - I thin we could use a three step strategy: 1: we contact the uploader, i he doesn' answer (I'm sure many ones are not working here any more) 2: we try to contact an user in the home language Wikipedia just to ge an idea, what we are dealing with (is it a text? is it a hoax or fake?), 3: an the we delete it (or we use a template saying the page will be deleted on ... fix datum)
• German policy: the German Wikisource is a project where I can say I trust the texts extraordinary, because the possibility of copyvio / fake / other manipulations of the text are extremely marginal if not on the zero level; but this is not practicab le here on this multilanguage project, where we have big problems to judge what it is (today I deleted a page after using google translator, in this case very easy, but it was rather an exeption).

Regards -jkb- (talk) 23:13, 2 February 2016 (UTC)

Another idea, could be to actively search for one or more thrusted users for any language, and to get their help. Are presently contributions categorized for language in any automated way? Does it exist a script or a tool to "sniff" the language of uncategorized pages? Unicode mapping could help for sure, mainly into non-latin alphabets, but I imagine that it would not be unequivocal. --Alex brollo (talk) 14:15, 3 February 2016 (UTC)

Tech News: 2016-05

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• Sites with a wikimedia.org address were by mistake redirected to the Wikimedia Foundation wiki on 26 January. This included Meta and Wikimedia Commons. The mistake was fixed after an hour. [29]
• Some users had problems logging in and out around 22 January. Bots also had problems and edit previews did not work properly. This was because of problems related to the new component SessionManager. It was undone on 23 January. [30][31]
• Because of new problems with SessionManager the latest version of MediaWiki was removed from the Wikimedia wikis again on 31 January. The new version this week will be without SessionManager. [32]

Changes this week

• The page history will get a help link. This will go to Help:Page history on Meta. Wikis can exchange it for a link to their local pages. [33]
• Notifications will only show part of a page name if it is very long. You will also have another way to mark notifications as read. [34][35]
• The Universal Language Selector input methods are now available with the visual editor. This means many who write in non-Latin scripts can now use the visual editor. [36]
• The visual editor will now give you more tools to edit tables. You can move rows and columns in a table and copy parts of tables to make new ones. You can also copy and paste more than one cell at the same time. [37][38][39]
• The visual editor has a new warning message when you leave a page you are editing without saving. Non-English wikis might need to translate it. [40][41]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 2 February. It will be on non-Wikipedia wikis and some Wikipedias from 3 February. It will be on all wikis from 4 February (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 2 February at 20:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is expiring watch list entries. The meeting will be on 3 February at 22:00 (UTC). See how to join.

Future changes

• The rest.wikimedia.org domain will be shut down. This is planned to happen in March. You should use /api/rest_v1/ at each individual project domain instead. [42]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:02, 1 February 2016 (UTC)

DynamicPageList extension

Could be DynamicPageList extension useful here? Category intersection could be particularly interesting in this complex multilingual environment, IMHO; I just tried DynamicPageList to intersect Category:Innece napulitane and Category:Index - Text Layer Requested ... with no result ;-) .--Alex brollo (talk) 08:35, 3 February 2016 (UTC)

I'm trying to solve the issue with {{nap}}, that self-categorizes nsIndex from page raw contents into any way we nap-sourcers can imagine. Presently the template filters Language=..... nap.... pages, but the filter could be very easily removed if you like it. --Alex brollo (talk) 22:22, 5 February 2016 (UTC)

Tech News: 2016-06

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Syntax highlighting support is now available for 53 more computer languages. [43]
• When you get a notification that an edit has been reverted, the notification now quotes part of the edit summary. [44]
• RESTBase is now using scrub_wikitext instead of scrubWikitext. [45]

Changes this week

• Wikidata will have a new data type called "math". It will be used for formulas. [46][47]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 9 February. It will be on non-Wikipedia wikis and some Wikipedias from 10 February. It will be on all wikis from 11 February (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 9 February at 20:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is per-language URLs for pages of multilingual wikis. The meeting will be on 10 February at 22:00 (UTC). See how to join.

Future changes

• Other sites will be able to tell when visitors come from links on Wikipedia and other Wikimedia sites. They used to be able to do this until we started using forced HTTPS in June 2015. This is planned to happen on 15 February. [48][49]
• Wikidata will have a new data type called "external-id". It will be used for references to external resources. It will be enabled on February 16. Some properties will be changed to the new data type. [50][51][52]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:58, 8 February 2016 (UTC)

Tech News: 2016-07

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now edit pages on the mobile site version without JavaScript. [53]
• You can now use the Math extension to write chemistry formulas. [54]

Problems

• A few editors might have been logged in as someone else because of a bug. For security reasons everyone was logged out on 9 February. If you have seen this bug, you can report it. [55][56]

Changes this week

• There is a beta feature that adds links to the subject on other Wikimedia projects. The plan was to have it leave beta testing and be enabled for everyone in January. It will happen on 16 February instead. Wikis that don't want this can decide to have it disabled. [57][58]
• Cross-wiki notifications will be available as a beta feature on Wikidata, MediaWiki, Commons, and all Hebrew and French wikis on 19 February. [59]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 16 February. It will be on non-Wikipedia wikis and some Wikipedias from 17 February. It will be on all wikis from 18 February (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 16 February at 20:00 (UTC). See how to join.

Future changes

• The search function on Wikimedia wikis will get a completion suggester that tries to find the right pages as the user is typing. It will also recognize some typos. This will probably happen in March. It is currently in beta. [60]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:16, 15 February 2016 (UTC)

New framework Discourse as an alternative to wikisource-l

As you perhaps know if you follow the mail list wikisource-l, there's an ungoing test of another kind of talk, more similar to a forum, here: https://discourse.wmflabs.org/. I hope to find the time to share into discourse something I learned here, since I'm using mul.source to test new tools, templates and editing tricks into a "light" environment as mul.source, very different from "heavy" environment as it.source or other major wikisource projects and using only basic user privileges (and a bot with similar, basic user privileges). My experience here has been, so far, very interesting and exciting! --Alex brollo (talk) 16:57, 15 February 2016 (UTC)

I just opened a talk into Discourse about Module:Nap that naepolitan group is testing here; presently our bot is running for a mass edit of Neapolitan nsPage pages replacing "hard categorization" with a Scribunto dynamic self-categorization. --Alex brollo (talk) 01:32, 17 February 2016 (UTC)

Tech News: 2016-08

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Phabricator has been upgraded. [61][62]

Problems

• There was no new MediaWiki version last week. Changes that were planned to happen last week will happen this week instead. This is because of a bug that made saving pages take longer time. [63][64]

Changes this week

• After February 23, you can use Wikidata for inter-language links on Wikiversity. [65]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 23 February at 20:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is Assign RFCs to ArchCom shepherds. The meeting will be on 24 February at 22:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:22, 22 February 2016 (UTC)

Move www.wikisource.org to mul.wikisource.org

Hello everybody!

at phab:T64717 there is an open proposal about moving this wiki, now hosted at www.wikisource.org, to the new address mul.wikisource.org:

As per the original proposer: "Old Wikisource" at www.wikisource.org would be better served if moved to mul.wikisource.org. "Mul" is the official ISO-639 code for "multiple languages", which is appropriate to this project. This would allow full interwiki linking, easier support from Wikidata, standardisation of URLs, and recognition as an active project. There is informal support for this in the Wikisource community on scattered discussions and the mailing list.

Needless to say, I perfectly agree with that, and I would like to stress in particular the point about recognition as an active project. Still too many people think about this project as the "old wikisource", implying it to be something like an "incubator", or even worse, an abandoned dumping place where "old" junk is left to rot. But we all know that this is simply not true, and the work of many users is there to prove it: this is a living project actively developed, and deserves a proper name and a proper address, which cannot be other than: the Multingual Wikisource, at http://mul.wikisource.org.

Moreover, once the move is done www.wikisource.org can be re-used to become a true portal site, like Wikipedia has at http://www.wikipedia.org. This will provide easier access to the other Wikisources as well.

Other wikis have been recently moved (see phab:T21986), so it seems that this proposal may be actually feasible. Before it can be implemented, however, a formal community consensus must be gathered, so here we are :) Candalua (talk) 15:58, 25 February 2016 (UTC)

I think that leaving it as it is would not be bad. Anyway, "old" is not proper because of the meaning of English word "old". "Incubator" would not be accurate because we also have texts of wikis that have its own subdomain because of certain reasons (e.g. Wikisource:Subdomain_coordination#cite_note-2). I find it more standard, suitable, accurate, descriptive and intuitive to call it "multilingual", so "mul" seems the best for me. -Aleator 17:41, 25 February 2016 (UTC)

Support

• --Candalua (talk) 15:58, 25 February 2016 (UTC)
• Support++ c' 'a pala :D --C.R. (talk) 16:39, 25 February 2016 (UTC)
• --Mizardellorsa (talk) 16:51, 25 February 2016 (UTC)
• --Aleator 17:41, 25 February 2016 (UTC)
• --Micru (talk) 11:17, 26 February 2016 (UTC)
• --Alex brollo (talk) 22:23, 26 February 2016 (UTC)
• --Accurimbono (talk) 11:57, 27 February 2016 (UTC)
• -- Jberkel (talk) 15:05, 4 March 2016 (UTC)
• obviously, VIGNERON (talk) 14:34, 8 March 2016 (UTC)
•  Strongly Support Let's just use this wiki as the second white mouse for phab:T21986. --Liuxinyu970226 (talk) 00:45, 3 April 2016 (UTC)
•  Strongly Support - in addition to preferring this for Wikisource and language specification reasons, I also will appreciate this change because Pywikibot can then easily fix one messy set of code where we currently map '-.wikisource.org' to 'www.wikisource.org' (see https://github.com/wikimedia/pywikibot-core/blob/407babe/pywikibot/families/wikisource_family.py#L37 and https://github.com/wikimedia/pywikibot-core/blob/407babe8b8b10f5dce21baf12c7bfcbb369a3254/pywikibot/family.py#L942). John Vandenberg (talk) 06:19, 20 April 2016 (UTC)
• NMaia (talk) 03:16, 15 May 2016 (UTC)

Oppose

• Is the move absolutely needed? Our Main Page already points to many language subdomains.--Jusjih (talk) 23:51, 29 March 2016 (UTC)

• And is your comment senseful? Per Special:SiteMatrix there's only 65 Wikisources (which include the closed Wikisources, if minus those, then we only have 63). --Liuxinyu970226 (talk) 00:45, 3 April 2016 (UTC)

• Weak oppose. I don't see the necessity of this move. I'm also concerned that this will not make other wikisources more accessible. Instead, I'm afraid that if this domain becomes a portal site, we will lose the "Languages at Wikisource" section on our Main Page which is a beautiful linking section; not only to those languages that have their own subdomain, but also to languages which are only represented at this wiki. --Ooswesthoesbes (talk) 11:48, 3 April 2016 (UTC)

Neutral

• // moved here from oppose // -jkb- (talk) 15:16, 26 February 2016 (UTC) I would say it could be iritating for many user and visitors as the present address has been used more than 10 years

Comment: @Candalua:, is it feasible to add an automatic redirect from wikisource.org to mul.wikisource.org?--C.R. (talk) 16:32, 26 February 2016 (UTC)

probably not yes, butthis is not the only point: since more than 10 years everybody knows the https://wikisource.org/ address in the address line, and as I said it could be iritating to see there something else. But, I must say, it is not so important... Thus, I move to neutral :-) -jkb- (talk) 23:41, 26 February 2016 (UTC)

Yes, we can ask to keep wikisource.org a redirect to mul.wikisource.org at least for some time, while everybody gets used to it; and it can be transformed into a "portal" in some later moment. --Candalua (talk) 10:55, 27 February 2016 (UTC)

@Candalua:, but that later, will it be possible to leave (mainly for works in the main namespace) although soft redirects to mul - (many websites from outside links to our pages) - in order not to link back to non-existent pages? Zdzislaw (talk) 11:35, 27 February 2016 (UTC)

well the linking from outside (probably quite often) would be another question to solve. -jkb- (talk) 15:08, 27 February 2016 (UTC)

@Candalua:Could the renaming into mul.wikisource.org help to solve the wikidata trouble? Alex brollo (talk) 16:20, 29 February 2016 (UTC)

Well, I don't know the tech details, but apparently the main reason given so far was: "not a subdomain". So hopefully it will help. Candalua (talk) 12:49, 2 March 2016 (UTC)

Idea. I am quite convinced that is feasible. Shall we specify explicitly a requirement written as follows?:

• In order to prevent broken links: The wikisource server must be configured to back-redirect any item present in mul.wikisource.org.
  • The back-redirect must permit that users accessing to https://wikisource.org/wiki/NameOfPage are redirected to https://mul.wikisource.org/wiki/NameOfPage with first priority if the page exists in mul.wikisource.org

A variation of this may be redirecting all the traffic pointing to https://wikisource/wiki/xxx pages to https://mul.wikisource.org/wiki/xxx pages, but I am worried to be so general.

If we request it on this terms I guess there is no problem! :D--C.R. (talk) 08:09, 3 March 2016 (UTC)

Unsure if moving to mul.wikisource can help in any way to add the wikidata support. The main argument against (that nobody responded) was concerning multiple language versions of a text in this wiki. Ankry (talk) 10:04, 3 March 2016 (UTC)

@C.R.:: yes, seems a good idea. @Zdzislaw: i hope this answers your question.

@Ankry: the "multiple links" is not a problem of mul.ws only (albeit it's more evident here). In every subdomain you can have several versions of the same text, corresponding to different editions or translations. We need to be able to link all the editions on one subdomain with all the editions on all the other subdomains: there is phab:T128173 for that. In the meantime, we'll have to do with disambiguation pages. Candalua (talk) 10:31, 3 March 2016 (UTC)

@Candalua: I did not mean that this is a real problem for us. I suggest only that no response is a bad signal to devs and that they may think about it as a real problem. Ankry (talk) 11:32, 3 March 2016 (UTC)

@Ankry: I didn't get it that way, but you may be right. I posted on phab:T54971 to try to clarify the situation. Candalua (talk) 11:47, 3 March 2016 (UTC)

@Candalua:: Leaving a redirect from "wikisource.org" to "mul.wikisource.org" and then transforming it into a portal site is just postponing a change. If the move is done, I think, it would be best to create a portal site right away. --Ooswesthoesbes (talk) 11:52, 3 April 2016 (UTC)

Tech News: 2016-09

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Thanks to the Graph extension and Pageview API, we now have {{Graph:PageViews}} templates that can show pageviews for any wiki page for any of the wikis. See the examples.
• The Capiunto extension is installed on test wiki. Capiunto provides flexible infobox functionality for Scribunto and generates HTML for infobox features such as headers and rows. It is designed for clean and modern infoboxes that are driven by data from Wikidata, easily usable across different language versions, and easily extensible.
• The visual editor now follows the TemplateData format setting announced in November. When you edit or add a use of a template, the wikitext will be laid out in one of the two ways. [66][67]
• The order of parameters and format defined in a template's TemplateData will be now respected. [68][69]

Changes this week

• On wikis where the visual editor is available in single edit tab mode, red links may open the visual editor instead of the wikitext editor, depending on user preferences. [70]
• Anonymous editor warning is now displayed as a warningbox for consistency in both the visual editor and the wikitext editor. [71]
• Parsoid has been updated to fit some HTML 5 specifications. [72]

Meetings

• Resigning executive director Lila Tretikov is taking questions at Knowledge Engine FAQ regarding the much talked about project. [73]
• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 1 March at 20:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:12, 29 February 2016 (UTC)

A new problem into transcluded ns0 pages

A change into mediawiki software breaks the output of tag <pages..../>, when it contains the text fromsection= tosection= ; empty parameters fromsection= and tosection= should be removed or normalized into fromsection="" tosection="" . This evening I'll run BrolloBot to evaluate the number of broken ns0 pages, and to fix them. If any of you uses personal tools to add a pages tag with empty fromsection and tosection parameters, please fix it converting the code into normalized form. Empty parameters should be probably avoided everywhere. --Alex brollo (talk) 16:07, 3 March 2016 (UTC)

For further info, this problem is due to phab:T108134. The developers say they will look into it "later today". Also, Phe posted a script to fix it. Candalua (talk) 16:46, 3 March 2016 (UTC)

The bot found & fixed a small number of broken pages (the whole ns0 has been read)- just a few dozens. It was not so a serious issue here. :-) --Alex brollo (talk) 21:35, 3 March 2016 (UTC)

Tech News: 2016-10

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Files on Wikimedia Commons can now be 2 GB big. The old limit was 1 GB. [74]
• Welcome notifications now have a different symbol. English Wikipedia already had this one. [75]
• The Wikimedia memory cache servers in the Eqiad cluster have now been upgraded to Debian 8 (Jessie). Some users might have had to log in again because of this. [76]
• It is now easier to categorize images uploaded to Wikimedia Commons in the Commons Android app. [77]
• Bare attributes in tags now parse according to the HTML5 specifications. <pages from= to= section=1> will parse as <pages from="to=" section="1"> instead of <pages from="" to="" section="1"> as it used to. Please use <pages from="" to="" section=1> or <pages section=1> instead. This is mostly likely to affect pages on Wikisource projects. [78]

Problems

• Phabricator has been a bit unstable lately. This should be fixed now. [79]
• The PageView API shows wrong data between 23 February and 29 February for pages with special characters in their title. [80]
• The parsing change mentioned above caused a large number of pages to break, especially on Wikisource. [81]
• You may see falsely formatted edit links on both mobile and desktop devices. Mobile devices can also show incorrect formatted table of contents. This should be fixed soon. [82]
• Templates using TemplateData that were edited with the visual editor might have some problems in wikitext mode. This can be fixed by editing and saving the page by using the visual editor without making any changes. [83]

Changes this week

• Cross-wiki notifications will be enabled as a beta feature on all wikis on 10 March. You will be able to get notifications when something happens on another Wikimedia wiki. [84]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 March. It will be on non-Wikipedia wikis and some Wikipedias from 9 March. It will be on all wikis from 10 March (calendar).
• Wikivoyages will get the Kartographer extension. Kartographer will allow <mapframe> and <maplink> tags in an article to insert an interactive map and overlay it with different markers. You can add ideas and suggestions to the Maps talk page. If you find any bugs, you can report them in Phabricator. [85]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 8 March at 20:00 (UTC). See how to join.

Future changes

• The buttons in interfaces will be simplified. Instead of white, red, green and blue buttons, in future there will only be white, red and blue ones. [86]
• The Wikimedia technical operations team plans to do some server work on 22 March. This could cause some problems, for example make it possible to read but not edit the Wikimedia wikis for a short period of time. The date for this might change. [87]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

22:14, 8 March 2016 (UTC)

Tech News: 2016-11

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The mobile web interface no longer suggests HiDPI thumbnails. This is to take up less bandwidth on slow or expensive connections. [88]
• The search engine on wikipedia.org has been updated. [89]

Changes this week

• Wikimedia has a new backup data center in Dallas. Because of planned work on this, you will be able to read but not edit the wikis for a short period of time on both 22 March and 24 March. This could be postponed to April 18. You might lose edits if you try to save during this time. Because of a test, there will also be a couple of minutes where you can't edit the wikis on 15 March starting 07:00 UTC. You can read more about the server work. There will be more notifications and updates about this.
• Administrators and other users with advanced permissions will need to have an 8-byte long passwords. This change takes place on 15 March. Users with too short passwords will be asked to change password the next time they log in. This was decided in a discussion on Meta and is because they can use tools that can hurt the wikis. [90]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 March. It will be on non-Wikipedia wikis and some Wikipedias from 16 March. It will be on all wikis from 17 March (calendar).
• The buttons in interfaces will be simplified. Instead of white, red, green and blue buttons, in future there will only be white, red and blue ones. [91]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 15 March at 19:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topics this week are backlog and thumb API. The meeting will be on 16 March at 21:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:37, 14 March 2016 (UTC)

Bad & good news about IA djvu files

Bad news: IA stopped to derive djvu files for new items.

Good news: Phe and Tpt are already working to solve the problem, IA upload tool will hopefully upload the IA djvu file.... even if it doens't exists into IA :-) --Alex brollo (talk) 07:48, 17 March 2016 (UTC)

Any progress on this? Please let the Wikisources know if a bot / tool becomes available to create the djvu files. --EncycloPetey (talk) 00:09, 26 June 2016 (UTC)

Tech News: 2016-12

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• Wikimedia has a new backup data center in Dallas. The Wikimedia Technology department planned to test it this week. This will take place the week of April 18 instead. You can read more about the server work. There will be more notifications and updates about this.
• In Firefox, the visual editor would sometimes just jump down to the bottom of the page when you double-clicked on a table cell. This has now been fixed. [92]

Changes this week

• It will now be easier to list IP addresses that don't have to solve CAPTCHAs. [93]
• You will now be able to mark Echo notifications as unread. [94]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 21 March. It will be on non-Wikipedia wikis and some Wikipedias from 22 March. It will be on all wikis from 23 March (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 22 March at 19:00 (UTC). See how to join.

Future changes

• URLs in the recent changes IRC feed will no longer be rewritten to unencrypted HTTP. This could be a breaking change for bots dependent on the IRC feed. This will happen on May 2. [95]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:04, 21 March 2016 (UTC)

Hi, a minor correction: The MediaWiki deployment dates are March 22–24, not 21–23. My apologies. /Johan (WMF) (talk) 08:30, 22 March 2016 (UTC)

Categories created by Babel AutoCreate

Hi. I'm not sure whether this is the right place, but well. Could any admin please delete all categories created by Special:Contributions/Babel AutoCreate? all of them are wrong, created due to a bug. Matiia (talk) 04:25, 22 March 2016 (UTC)

@Matiia: Done Ankry (talk) 13:10, 22 March 2016 (UTC)

Tech News: 2016-13

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• MediaWiki now supports the semantic web standards of Microdata and RDFa 1.0. On Wikimedia projects, a configuration change must be requested in order to enable RDFa 1.0. [96] [97]

Problems

• Adding references with Citoid was broken for approximately 6 hours on 24 March. This was fixed. [98]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 29 March. It will be on non-Wikipedia wikis and some Wikipedias from 30 March. It will be on all wikis from 31 March (calendar).
• You will be able to remove the header and footer style from User language (babel) boxes. This will make it easier to use them with other userboxes. [99]

Meetings

• You can join the next meeting with part of the Architecture committee, which will discuss a few topics. The meeting will be on 30 March at 21:00 (UTC). See how to join.
• The Architecture committee has sent a summary of new and ongoing RFC discussions.

Future changes

• Commons will soon have improved access to Wikidata's data. It will then be possible to access data about any concept on any page on Commons. Assistance with testing this on the beta cluster is appreciated. [100]
• Wikibits.js will not be loaded by default anymore starting April 2016. Gadget and script authors should have already updated their code since the previous announcements, but there is another migration path available if needed. See wikitech-l for details.

Corrections

• Last week Tech News said the new MediaWiki version would come to wikis from 21 March to 23 March. The right dates were 22 March to 24 March.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:43, 28 March 2016 (UTC)

A new Module

Just to let you know about Module:Testo, a generalization of it:Modulo:Testo, vaguely coming from mul.source Module:Nap code. It recovers and shows medatata & links for a ns0 page title using data stored into related Index page.

A example:

* {{testo|O Panu Czorlińscim co do Pucka po sece jachoł}}

gives:

• O Panu Czorlińscim co do Pucka po sece jachoł

It runs decently on proofread works, with a well filled Index page form. --Alex brollo (talk) 09:02, 29 March 2016 (UTC)

Open Call for Individual Engagement Grants

Please help translate to your language:

Greetings! The Individual Engagement Grants (IEG) program is accepting proposals until April 12th to fund new tools, research, outreach efforts, and other experiments that enhance the work of Wikimedia volunteers. Whether you need a small or large amount of funds (up to $30,000 USD), IEGs can support you and your team’s project development time in addition to project expenses such as materials, travel, and rental space.

• Submit a grant request or draft your proposal in IdeaLab
• Get help with your proposal in an upcoming Hangout session
• Learn from examples of completed Individual Engagement Grants

With thanks, I JethroBT (WMF) 15:47, 31 March 2016 (UTC)

Tech News: 2016-14

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can filter Special:Log in more detail. [101]
• Wikimedia wikis have a new way of counting visitors. [102]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from April 5. It will be on non-Wikipedia wikis and some Wikipedias from April 6. It will be on all wikis from April 7 (calendar).

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

22:13, 4 April 2016 (UTC)

Tech News: 2016-15

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The visual editor can generate wikicode with image options in your language. Examples of image options are "thumb" or "left". You can ask to change to options in your language in Phabricator. [103][104]
• Wiktionaries and Wikisources can now use the visual editor. It is an opt-in beta feature. It still needs development to work better with these projects. [105][106]
• ORES is using new models. Tools that use ORES' predictions can behave strangely. ORES also has a new API. [107]
• The visual editor now supports classical Greek characters. [108]

Problems

• There was a bug when you used keyboard arrows in templates in the visual editor. This has now been fixed. [109]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 April. It will be on non-Wikipedia wikis and some Wikipedias from 13 April. It will be on all wikis from 14 April (calendar).
• The wikipedia.org portal will get many small bug fixes and improvements. Most will be for the search box and suggested results that were added in March. [110]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 12 April at 19:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topics this week are improving transclusion of templates for Parsoid and balanced templates. The meeting will be on 13 April at 21:00 (UTC). See how to join.

Future changes

• Wikimedia has a new backup data center in Dallas. Because of planned work on this, you will be able to read but not edit the wikis for a short period of time on both 19 April and 21 April. This will start at 14:00 UTC and last for 15 to 30 minutes. [111]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:44, 11 April 2016 (UTC)

Server switch 2016

The Wikimedia Foundation will be testing its newest data center in Dallas. This will make sure Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to conduct a planned test. This test will show whether they can reliably switch from one data center to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

They will switch all traffic to the new data center on Tuesday, 19 April.
On Thursday, 21 April, they will switch back to the primary data center.

Unfortunately, because of some limitations in MediaWiki, all editing must stop during those two switches. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

• You will not be able to edit for approximately 15 to 30 minutes on Tuesday, 19 April and Thursday, 21 April, starting at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT).

If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

• Background jobs will be slower and some may be dropped.

Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.

• There will be a code freeze for the week of 18 April.

No non-essential code deployments will take place.

This test was originally planned to take place on March 22. April 19th and 21st are the new dates. You can read the schedule at wikitech.wikimedia.org. They will post any changes on that schedule. There will be more notifications about this. Please share this information with your community. /User:Whatamidoing (WMF) (talk) 21:07, 17 April 2016 (UTC)

Tech News: 2016-16

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can filter Special:Log in more detail. You can filter different imports and new users. [112][113]
• You can use Telnet to read Wikimedia wikis. [114]
• MediaWiki wikis can handle bigger file uploads. The new limit is 4 GB. [115]

Changes this week

• Wikimedia has a new backup data center in Dallas. Because of planned work on this, you will be able to read but not edit the wikis for a short period of time on both 19 April and 21 April. This will start at 14:00 UTC and last for 15 to 30 minutes. [116]
• There is no new Mediawiki version this week. This is because of the data center test.

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on April 19 at 19:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is shadow namespaces. The meeting will be on 20 April at 21:30 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:40, 18 April 2016 (UTC)

Untitled message

• I put my proivedeniya, but for some reason erased. How can I restore? I registered.--Кинйә 17:36, 20 April 2016 (UTC) —unsigned comment by Азат Хәлилов (talk) .

Tech News: 2016-17

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• Wikimedia tested a new data center last week. This meant that the wikis could be read but not edited for 45 minutes on April 19 and for 20 minutes on April 21. [117]
• When the data center was tested, new edits were not shown in the recent changes log for 20 minutes. They are in the logs now. You can read more about how to find the edits.
• Unread notifications were sometimes counted incorrectly. This has now been fixed. [118]

Changes this week

• Wikimedia Commons will have better access to Wikidata. They can use data from any page on Wikidata on any page on Commons. This will happen on April 26. [119]
• It will be easier to choose if you want to watch files you have uploaded with the upload wizard. [120]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from April 26. It will be on non-Wikipedia wikis and some Wikipedias from April 27. It will be on all wikis from April 28 (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on April 26 19:00 (UTC). See how to join.

Future changes

• The "Save page" button when you edit will be called "Publish" instead. This is to help new editors understand what it does. It already works like this on some wikis. [121]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:02, 25 April 2016 (UTC)

Tech News: 2016-18

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The visual editor now works when you use Internet Explorer 9. [122]

Problems

• There was a security problem with the MobileFrontend extension. It showed information that had been oversighted. This has now been fixed. [123]

Changes this week

• You can now see which notifications are available on a wiki on Special:DisplayNotificationsConfiguration. [124]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from May 3. It will be on non-Wikipedia wikis and some Wikipedias from May 4. It will be on all wikis from May 5 (calendar).

Meetings

• You can join the next meeting with the Architecture committee. The topic this week is "PSR-6 Cache interface in Mediawiki core". The meeting will be on May 4 at 21:00 (UTC). See how to join.

Future changes

• Pages could be added to new users' watchlists by default when they edit them. New users could also by default get email notifications when pages they watch are edited. This is discussed on Meta. [125]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:09, 2 May 2016 (UTC)

Tech News: 2016-19

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Wikiversities now have better access to Wikidata. They can use data from any page on Wikidata on any page on Wikiversity. This happened on May 3. [126]
• You can use Wikipedia GapFinder to find missing articles between languages. [127]
• Users are invited to try Cross-wiki Notifications on all wikis. This is the last test session before the release by default, scheduled for May 12th at 23:00 UTC. [128][129]
• You can use keyboard shortcuts to open the visual editor (meta+V) or the wikitext editor (meta+E) (on certain wikis, even if you have chosen a favorite editor). [130]
• Uploading files bigger than 100 megabytes on Wikimedia Commons required to opt-in in your preferences. This is not necessary anymore. [131]
• The UploadsLink extension is now available on Wikimedia Commons. [132]
• Deleting a translation unit page didn't remove the corresponding content from the translation page. This is now solved. [133]
• Translation suggestions based on Apertium are now available on Mediawiki.org. [134]

Problems

• MediaWiki 1.27.0-wmf.23 has been rolled back from Wikimedia wikis, due to a performance issue. [135]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from May 10. It will be on non-Wikipedia wikis and some Wikipedias from May 11. It will be on all wikis from May 12 (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on May 10 at 19:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topics this week are Overhaul Interwiki map, unify with Sites and WikiMap. The meeting will be on May 11 at 21:00 (UTC). See how to join.
• 2017 European hackathon will happen on May 19 - 21, in Vienna (Austria).

Future changes

• Today, in categories, a page titled "11" comes before "2". We plan to reorder that: "2" will come before "11". Please tell the developers if the change will cause problems. [136]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

23:22, 9 May 2016 (UTC)

Tech News: 2016-20

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Some image thumbnails now load faster on mobile. They also take up less bandwidth. [137]

Problems

• Last week's MediaWiki version was late on some wikis. [138]

Changes this week

• Special:Notifications will have "mark as read" buttons for each day. The non-JavaScript version will get it this week. A JavaScript version will come later. [139]
• Wikis can now locally decide what wikitext they want the signature button to produce. [140]
• A one-time welcome message for users will now be shown in the wikitext editor. This will include existing users. [141]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from May 17. It will be on non-Wikipedia wikis and some Wikipedias from May 18. It will be on all wikis from May 19 (calendar).

Meetings

• You can join the next meeting with the Architecture committee. The topics this week are "Requirements for change propagation". The meeting will be on May 18 at 21:00 (UTC). See how to join.

Future changes

• Using self-closing tags like <div/> and <span/> to mean <div></div> and <span></span> will not work in the future. Templates and pages that use these tags should be fixed. When Phabricator ticket T134423 is fixed these tags will parse as <div> and <span> instead. This is normal in HTML5. [142]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:01, 16 May 2016 (UTC)

Tech News: 2016-21

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You now see a warning message on pages that try to use {{DISPLAYTITLE}} but it doesn't work because it doesn't match the page's actual title. [143]

Problems

• Commons had problems with server lag. This meant that it took longer time for files to turn up in categories. [144]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 May. It will be on non-Wikipedia wikis and some Wikipedias from 25 May. It will be on all wikis from 26 May (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on May 24 at 19:00 (UTC). See how to join.

Future changes

• All HTTP access to Wikimedia sites and APIs will stop working. Some bots still use HTTP. They will need to use HTTPS instead. This will happen on June 12. [145]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:40, 23 May 2016 (UTC)

Tech News: 2016-22

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• There is now a standard way to get the target of a redirect page from a Lua module. [146]

Problems

• A new way to handle rollback was introduced. It broke some tools and scripts and was reverted. This will be re-planned after review. [147][148]
• CentralNotice didn't work in some older browsers. This has now been fixed. [149]

Changes this week

• When you edit a file or category page with the visual editor the rest of the page will be shown in its normal place. [150]
• The Translate extension will get an edit summary field. [151]
• A change to the <charinsert> feature could break some user scripts. Contact Bawolff if the "click to insert special characters" links in the edit window break on your wiki. [152][153]
• Elasticsearch will be upgraded on Wikimedia wikis this week. This should not affect you, but if you have problems with the search function this is probably the reason. [154]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 31 May. It will be on non-Wikipedia wikis and some Wikipedias from 1 June. It will be on all wikis from 2 June (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 31 May at 19:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:18, 30 May 2016 (UTC)

Tech News: 2016-23

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• MathML/SVG is now the default <math> rendering mode on Wikimedia projects. [155][156]

Changes this week

• The history page can tell you if a page on your watchlist was updated since you last visited it. This now works the same way in Vector as in other skins. The change broke local designs on some wikis. This will be fixed this week. [157]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 June. It will be on non-Wikipedia wikis and some Wikipedias from 8 June. It will be on all wikis from 9 June (calendar).

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:51, 6 June 2016 (UTC)

help on formatting

Can anyone help me with formatting, for example this page? --Kumincir (talk) 03:39, 10 June 2016 (UTC)

@Kumincir: maybe I could help, but you need to clarify first: what is the trouble that you have? You have some trouble(s) with that alphabetical list on the left side of that page?

If yes — then what kind of the problem is that you are unable to resolve:

1) how to make alphabetical numbering instead of standard numeral;

2) how to deal with the occurence that the list is deployed on two pages and is splitted and divided between them — how to make correct displaying of these list's parts on the proofread page, and on the final transclusion (in order the list's parts were correctly joined into one single list) as well;

3) or do you have both problems at once? --Nigmont (talk) 19:05, 10 June 2016 (UTC)

@Nigmont: Yes, I mean both of them. It is nice to have the text have the exact appearance, but at least, good formatting should be fine. For the Poesaka Soenda, in the beginning, I thought I would just change the format into one column to avoid formatting problems. Any suggestion? --Kumincir (talk) 01:30, 13 June 2016 (UTC)

@Kumincir: Yes, I think — anyway you should refuse from using the multicol template in such a way, or else you would not get one contiguous text on a transcluded page: you would get text splitted to pieces corresponding to book pages and each of those page pieces would be separated into two columns, and the text would be swapped from right to left column at every next page.

I tried to change formatting on two pages of your book: Page # 18 and Page # 19, let me explain:

1. Regrading numbering as letters: I do not know to do this by means of the Wikimedia itself, so I did such formatting using html code:

<ol type="a">
<li>item a text</li>
<li>item b text</li>
...
</ol>

2. Regarding how to deal with continuation of list between pages: you should get accustomed with page sections "Footer" and "Header": their content is displayed while viewing the page (in the page namespace) but not transcluded; and this is very convenient. You may put in these sections intermediary starts and ends of a list, which (starts and ends) are needed while single page display (to avoid the text to be broken) but not needed (superfluous and excessive) on the final transcluded pages. Now let's see how I did this on that pages: # 18 — I put the intermediary end of the list in the 'Footer' section, and # 19 — I put the intermediary start in the 'Header' section.

And see the result how it was transcluded — on my sandbox.

Take a look on all of this and decide if such ideas are appropriate for you? Anyway if you do not like something of this — you are free to revert my two edits of that pages to their previous state and to continue to do formatting as you wish. Or if in my solutions some more fixes are needed (e. g. I see some slight issues with linebreaks) — I may try to help with this as well. Regards, Nigmont (talk) 10:07, 13 June 2016 (UTC)

@Nigmont: Many thanks for your suggestions. I'll figure it out what fit best for it. --Kumincir (talk) 02:50, 14 June 2016 (UTC)

Help is needed for the Mingrelian WS

There is a problem on the Mingrelian Wikisource (which is a local Wikisource here, at the Multi-lang. WS): there are many poetry pages in it, which's code contain opening tag <poem> but does not contain the complementary closing tag </poem>, and because of this these pages loose normal poetry formatting. Examples: *ათე სქანი, *ხამ შური, ხამ გური, *სისანდობა ვა რე, and lots of others. Additional details can be seen in the discussion: User talk:მარგალონა#Template:Header.

As I think: maybe some bot-owner could help with the problem, and might launch their bot to perform such a task:

• Pass through all the pages which are included in the Category:Mingrelian and its sub-categories,
• and for each of them where within its code — the tag <poem> presents but the closing tag code </poem> is missed:
  • to insert a line consisting entirely of needed </poem> tag — to place it at the end of the page just before the lines with categories (or maybe more precise: just after the last text line which is before the category lines)
• for all other pages (those ones where both tags present as required, as well as pages which haven't the tag <poem> at all) — to leave them untouched.

Can anyone help to Mingrelian contributor(s) to resolve the problem? --Nigmont (talk) 18:46, 10 June 2016 (UTC)

Done.

I have used this search query to find all the articles:

insource:/\<poem\>/ incategory:Mingrelian -insource:/\<\/poem\>/

and this source code to add missing enclosing tag:

User:Dixtosa/addMissingPoem.

I also changed |noauthor to |author parameter. I know it broke some stuff. For instance, Mingrelian authors are created in the mainspace and the links were to mainspace too. But yall don't worry. I'll move all the authors to the Author: namespace.--Dixtosa (talk) 18:31, 11 June 2016 (UTC)

The authors thing is also done. Dixtosa (talk) 19:42, 11 June 2016 (UTC)

@Dixtosa: Thank you very much for your great help! --Nigmont (talk) 20:40, 11 June 2016 (UTC)

Books to be added using bot on Sourcewiki Wikisource for Hindi

Dear Sourcewiki burocrats, I will be using my bot account RahmanuddinBot (not flagged as bot on this wiki) to add OCR'ed text to Hindi books' index pages. Please let me know if I need to do any pre-work before I do that! --రహ్మానుద్దీన్ (talk) 11:01, 13 June 2016 (UTC)

No one replied on this thread and no one added bot flag and User:Ankry has blocked my bot. In such case, I am using my own account to do the required tasks. --రహ్మానుద్దీన్ (talk) 14:29, 23 June 2016 (UTC)

I am not bureaucrat here, so I do not feel authorized to respond your request. However, massive automatic edits require a bot flag here. Please wait for a bureaucrat decission.

Note, in some cases the bot edits are broken as pages without text should be marked "without text" (or maybe, created manually to revise they are really without text) instead of "not proofread".

BTW, if you feel the block was unfair, feel free to ask another admin to revise it. I will accept their decission. Ankry (talk) 14:41, 23 June 2016 (UTC)

@రహ్మానుద్దీన్: requests for a bot flag should be placed here. I suggest you to ping bureaucrats when you make one. Ankry (talk) 14:49, 23 June 2016 (UTC)

@Ooswesthoesbes, Zyephyrus: Would you consider adding the bot flag here (for RahmanuddinBot) to avoid massive RC spamming? Ankry (talk) 15:06, 23 June 2016 (UTC)

Done --Ooswesthoesbes (talk) 15:29, 23 June 2016 (UTC)

Btw, I also unblocked the account. --Ooswesthoesbes (talk) 15:30, 23 June 2016 (UTC)

Tech News: 2016-24

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Wikimedia wikis now use AuthManager. If you have new problems related to logging in or being logged in, report them. [158]
• Visiting Special:Notifications doesn't automatically mark notifications as read anymore. You can go between read, unread or all notifications on Special:Notifications. Notifications on Special:Notifications are grouped by day. You can mark every daily group as read individually. Notifications are displayed by groups of 50 on Special:Notifications and you can find former notifications by using navigation arrows. [159][160][161][162]

Changes this week

• You can filter user contributions to hide minor edits. [163]
• It will be easier to edit galleries with the visual editor. [164]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 14 June. It will be on non-Wikipedia wikis and some Wikipedias from 15 June. It will be on all wikis from 16 June (calendar).

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:41, 13 June 2016 (UTC)

Tech News: 2016-25

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Notifications were not always marked as read when you followed a link from an email notification. This will now happen. [165]

Changes this week

• The list of other languages an article is available in will be shorter on small Wikipedias and non-Wikipedia projects. This is to make it easier to find the most relevant languages for each user. You will still be able to see the other languages. [166][167]
• Alerts (the red badge) will not be automatically marked as read when you open the Notifications popup. [168]
• When you get several thanks you can see them as one notification. This is instead of one notification for each thanks. [169]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 21 June. It will be on non-Wikipedia wikis and some Wikipedias from 22 June. It will be on all wikis from 23 June (calendar).

Meetings

• You can join the next meeting with the Architecture committee. The topic this week is develop Markdown support strategy for MediaWiki. The meeting will be on 22 June at 21:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:14, 20 June 2016 (UTC)

Providing help on js cleaning

Hey, tpt (talk • contribs • global contribs) proposed me to work on js cleaning task of Wikisource:Shared Scripts. Right now I don't have enough permissions to edit it, so I may propose some changes in a user subpage if you wish. Also tell if you have other similar tasks you might like to be done. :) --Psychoslave (talk) 16:43, 25 June 2016 (UTC)

Tech News: 2016-26

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The ORES service has now moved to a new location. This should make it easier to use ORES. The ORES review service is now available as a beta feature on Wikidata and Persian Wikipedia. ORES is an artificial intelligence system for Wikimedia wikis to help editors. [170]
• The order of wikis in collapsed cross-wiki notifications was different than when the list was expanded. This is now fixed. [171]
• A new category for tracking pages with math errors was added: Category:Pages with math errors. [172]

Problems

• The Wikimedia Etherpad crashed on June 23. Some edits done that day have been lost. They can be found at etherpad-restore.wikimedia.org for another few days. [173][174]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 28 June. It will be on non-Wikipedia wikis and some Wikipedias from 29 June. It will be on all wikis from 30 June (calendar).
• The way to mark notifications as read or unread will be changed to be more clear. [175]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 28 June at 19:00 (UTC). See how to join.

Future changes

• The Collaboration team at the Wikimedia Foundation will look at developing better tools for edit review. This is because research suggests we scare away newcomers who want to help. [176]
• An e-mail from the Editing Department explains the technical work that is planned and being researched for the future. Items include better wikitext and visual editing, prompts for edits, language improvements, annotations, and meta-data separation. [177]
• The sorting of Notifications into the two fly-out menus is going to change on July 5 to 7. Bundled notifications should be easier to explore and mark as read individually. [178][179][180]
• From 29 June git.wikimedia.org (running Gitblit) will redirect all requests to Phabricator. The vast majority of requests should be correctly redirected. [181]
• Catalan and Polish Wikipedias will have Wikidata descriptions added to articles in the mobile view by default. This is currently a beta option for the mobile versions. This might come to other wikis later. [182]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:42, 27 June 2016 (UTC)

Tech News: 2016-27

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• A daily email summary of notifications could be sent even when there were no notifications from the wiki. Now no email will be sent if there is no activity. [183]

Changes this week

• The "⧼citoid-citefromidtool-title⧽" button in the visual editor's toolbar will move into the "Insert" menu except for Wikipedias, Wikibookses and Wikiversities. This is to make it less prominent on wikis that don't use it as much. [184]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 July. It will be on non-Wikipedia wikis and some Wikipedias from 6 July. It will be on all wikis from 7 July (calendar).

Meetings

• You can take part in the next office hour for Wikidata on IRC on July 8 at 16:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:45, 4 July 2016 (UTC)

Open call for Project Grants

Please help translate to your language:

Greetings! The Project Grants program is accepting proposals from July 1st to August 2nd to fund new tools, research, offline outreach (including editathon series, workshops, etc), online organizing (including contests), and other experiments that enhance the work of Wikimedia volunteers.

Whether you need a small or large amount of funds, Project Grants can support you and your team’s project development time in addition to project expenses such as materials, travel, and rental space.

• Submit a grant request or draft your proposal in IdeaLab
• Get help with your proposal in an upcoming Hangout session
• Learn from examples of completed Individual Engagement Grants or Project and Event Grants

Also accepting candidates to join the Project Grants Committee through July 15.

With thanks, I JethroBT (WMF) 15:25, 5 July 2016 (UTC)

Tech News: 2016-28

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• A new image scaler fixed a number of bugs for showing SVG files. Some new problems turned up. [185][186][187]
• Notifications are grouped by types. They are now counted by number of notifications and not by unread groups. That change may increase the number of notifications displayed. The earlier way of counting was often incorrect. Unread notifications will also be displayed first. [188][189][190]
• Special:Notifications now has a maximum width for the notifications list on desktop computers. This allows long titles and descriptions to be cut properly. Notifications are now also better parsed. [191][192][193]

Problems

• On 5 July Wikimedia Commons had problems and could not be edited for 20 minutes. For a short while after that the recent changes log and some gadgets were not working properly. It affected administrative actions on other projects too. [194]
• Users who have multiple unread notifications can mark them as read by visiting Special:Notifications page on their wiki.

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 July. It will be on non-Wikipedia wikis and some Wikipedias from 13 July. It will be on all wikis from 14 July (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 12 July at 19:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:14, 11 July 2016 (UTC)

Tech News: 2016-29

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Due to the rollback, new sorting of Notifications on the Fly-Out Menus has been deployed with a delay. [195]
• Due to the rollback, the daily special patch deployment process has been changed. [196]
• In notifications, "Messages" are now called "Notices". [197]

Problems

• On July 12 all wikis were rolled back to MediaWiki 1.28.0-wmf.8 due to a problem in the log-in system. [198][199]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 19 July. It will be on non-Wikipedia wikis and some Wikipedias from 20 July. It will be on all wikis from 21 July (calendar).
• Special:Log now has a help link. [200]
• The RevisionSlider can be tested on the beta cluster. From 22 July, it will be available as a beta feature at: German Wikipedia, Arabic Wikipedia, Hebrew Wikipedia. [201][202][203]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 19 July at 19:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is "Devise plan for a cross-wiki watchlist back-end". The meeting will be on 20 July at 21:00 (UTC). See how to join. [204]

Future changes

• User scripts and bots can no longer use http:// to edit wiki pages. [205][206]
• Gerrit is going to be updated. Developers are invited to test it. [207]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:18, 18 July 2016 (UTC)

Tech News: 2016-30

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Interactive maps have been enabled for Meta wiki and the Catalan, Hebrew, and Macedonian Wikipedias. Learn how to add interactive maps to wiki pages.
• Last week's rollback is now documented. [208]

Problems

• Sometimes, the visual editor required saving twice. That problem is now fixed. [209]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 26 July. It will be on non-Wikipedia wikis and some Wikipedias from 27 July. It will be on all wikis from 28 July (calendar).
• It is now possible to mark all Notifications as read on Special:Notifications, by clicking on the cog icon. [210]
• Wikipedia search will now detect the language of your search if 2 or fewer results are found. It will then show results from the matching language Wikipedia, if any relevant article exists. It will start to roll out in 5 languages. [211]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 26 July at 19:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is "an extension that implements an authenticated key-value store". The meeting will be on 27 July at 21:00 (UTC). See how to join. [212]

Future changes

• The current icon for Notifications "Notices" (in English "Notices") will be changed from a bubble-speech icon to a tray icon for consistency. [213]
• Special:Notifications page code will be changed to be more Mobile friendly. [214]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:54, 25 July 2016 (UTC)

Tech News: 2016-31

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• A prototype for structured data on Commons is available now. [215]
• The RevisionSlider beta feature can now be tested on mediawiki.org, German Wikipedia, Arabic Wikipedia and Hebrew Wikipedia.

Problems

• Renamed users on some wikis were not connected to their account on other wikis between 20 July and 21 July. This has been fixed. [216]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 2 August. It will be on non-Wikipedia wikis and some Wikipedias from 3 August. It will be on all wikis from 4 August (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 2 August at 19:00 (UTC). See how to join.
• The next CREDIT showcase will be on 3 August at 18:00 (UTC). This is to present and comment on new gadgets, small projects and works in progress. See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is "notifications in core". The meeting will be on 3 August at 21:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:48, 1 August 2016 (UTC)

Tech News: 2016-32

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• In notifications, the icon for Notices has been changed from a speech-bubble icon () to a tray icon () for consistency. The Alerts icon has been redesigned too. The colors have been changed for accessibility. [217]

Problems

• If you use the wikEd gadget, changes you made were not kept when you switched from the wikitext editor to the visual editor while you were editing. This has now been fixed. [218]

Changes this week

• Wikimedia search will now ignore question marks at the end of the sentences or words you use when you search. Until now the question mark was just a wildcard. [219]
• On Commons, UploadWizard will now be available on mobile, rather than just the old upload form. This should reduce the workload for the community in reviewing images. [220]
• When you edit with the visual editor a puzzle symbol tells you there is an invisible template in the article. It will now mention the name of the template. [221]
• The button to read something in another language will move for mobile users. This will happen on 9 August. [222]
• When someone mentions you and links to your user page you get a notification. You will now get a notification when you mention yourself this way. [223]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 9 August. It will be on non-Wikipedia wikis and some Wikipedias from 10 August. It will be on all wikis from 11 August (calendar).
• A message on Notifications panel will invite users to try Special:Notifications page. [224]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on August 9 at 19:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:40, 8 August 2016 (UTC)

Save/Publish

The Editing team is planning to change the name of the “Save page” button to “Publish page” and “Publish changes”. “Publish page” will be used when you create a new page. “Publish changes” will be used when you change an existing page. The names will be consistent in all editing environments.[225][226]

This change will probably happen during the week of 30 August 2016. The change will be announced in Tech News when it happens.

If you are fluent in a language other than English, please check the status of translations at translatewiki.net for “Publish page” and “Publish changes”.

The main reason for this change is to avoid confusion for new editors. Repeated user research studies with new editors have shown that some new editors believed that “Save page” would save a private copy of a new page in their accounts, rather than permanently publishing their changes on the web. It is important for this part of the user interface to be clear, since it is difficult to remove public information after it is published. We believe that the confusion caused by the “Save page” button increases the workload for experienced editors, who have to clean up the information that people unintentionally disclose, and report it to the functionaries and stewards to suppress it. Clarifying what the button does will reduce this problem.

Beyond that, the goal is to make all the wikis and languages more consistent, and some wikis made this change many years ago. The Legal team at the Wikimedia Foundation supports this change. Making the edit interface easier to understand will make it easier to handle licensing and privacy questions that may arise.

Any help pages or other basic documentation about how to edit pages will also need to be updated, on-wiki and elsewhere. On wiki pages, you can use the wikitext codes {{int:Publishpage}} and {{int:Publishchanges}} to display the new labels in the user's preferred language. For the language settings in your account preferences, these wikitext codes produce “Publish page” and “Publish changes”.

Please share this news with community members who teach new editors and with others who may be interested.

Whatamidoing (WMF) (talk) 18:04, 9 August 2016 (UTC)

Mein Kampf in German

See Mein Kampf, started today. This problemfull text is in German and doesn't belong here - this is my oppinion. I will suggest to delete it here as "out of scope" - see German Wikisource. -jkb- (talk) 13:26, 10 August 2016 (UTC)

I suggest to stop these contributions untill we clear this problem. The German Wikisource has been informed. -jkb- (talk) 14:02, 10 August 2016 (UTC)

Well, it's a very important historical material, but unfortunately it's not allowed to be posted in German Wikisource due to the special German historical background. If you want an English description, I will add it. Wetitpig0 (talk) 15:25, 10 August 2016 (UTC)

I'm afraid to answer it with "no". If it is an important historical material - that is another question. But first of all it is a very shity and very troubled material. And, as the users on the German Wikisource told you, the text without a solid scientific commentary should not find a place in Wikimedia Foundation projects. But this is only one point: in the Oldwikisource it is out of scope because of the German Wikisource. -jkb- (talk) 15:42, 10 August 2016 (UTC)

BTW, I don't need any English description as I speak German and I studied the history. Anyway, thanks. -jkb- (talk) 15:43, 10 August 2016 (UTC)

I agree with the general point and the arguments of -jkb- and I think this work should be deleted. Also I could additionally say that, AFAIK, any material which belongs to any language which has own separate sub-domain of Wikisource, may be posted here, on the multi-lang WS, only in the case when:
that material may not be posted on the own language subdomain because of copyright restrictions of the main country of that language but may be posted here because such copyright restrictions does not exist according to laws of the US.
Any other reason of banning the material on the "national" WS (the German one as in this case) does not fit for transferring of publishing material here instead of the "national" WS, as I think. --Nigmont (talk) 18:39, 10 August 2016 (UTC)

btw. there still may be some copyright restictions in the US (see Commons:Village pump/Copyright#Mein Kampf) --WikiAnika (talk) 21:52, 10 August 2016 (UTC)

yepp, thank you; this was another point I wanted to ask in the deWS or deWP. -jkb- (talk) 22:29, 10 August 2016 (UTC)

According to this website, only the copyright of ENGLISH version was seized. Therefore, the German version is in public domain in the US.Wetitpig0 (talk) 07:48, 11 August 2016 (UTC)

Another website also found that the US government has transferred the copyright to the government of Bavaria.Wetitpig0 (talk) 07:58, 11 August 2016 (UTC)

The Bavarian State is the inheritor of the private person Adolf Hitler (no children to inherit). The Bavarian State is also the instance, that will use any possible legal force against any publication of that book. You believe they won't use the (in this case) more restrictive US copyright law for works published in 1923 and later to hinder anyone to publish it (without solid scientific notations)?

I don't know how to link it correctly, but have a look at the Public Catalog of the United States Copyright Office and search for Mein Kampf / By Adolf Hitler. --> Entire Copyright Document: V1798P254-255 (Houghton Mifflin Company) and Entire Copyright Document: V1786P346-347 (also Houghton Mifflin Company) --WikiAnika (talk) 09:22, 11 August 2016 (UTC) btw. according to "this website" Anne Franks Diary shall be in the PD as well, we all know what happend to the publication of it at nl.ws

Check this first: Wikisource:Possible copyright violations/archives/Mein KampfWetitpig0 (talk) 10:17, 11 August 2016 (UTC)

whats your point? --WikiAnika (talk) 10:25, 11 August 2016 (UTC)

Only the English Edition is copyrighed, but not the German version.Wetitpig0 (talk) 10:33, 11 August 2016 (UTC)

in the US? Why? --WikiAnika (talk) 11:03, 11 August 2016 (UTC)

@Wetitpig0, WikiAnika: Main Kampf is still copyrighted in US because of URAA. As it was NOT in Public Domain in Germany on 1.1.1996, it is copyrighted in US 95 years from publication date. So eg. a 1925 edition would be PD in US some day in 2020 (assuming exact publication date is known). It is clear copyright violation till this date. The fact it is PD in Germany is irrelevant for this project. Ankry (talk) 09:11, 12 August 2016 (UTC)

@Wetitpig0: The information in Wikisource:Possible copyright violations/archives/Mein Kampf is outdated as in 2004 we were not aware about URAA. Ankry (talk) 09:15, 12 August 2016 (UTC)

As stated above the question of copyright or copyvio is pretty secondary here anyway. The main point I made is the language problem - the work is not appropriate here (beside other points like copyright not clear, nazi propaganda etc.). See also my announcement in Wikisource:Proposed deletions#Mein Kampf. Regards, -jkb- (talk) 15:16, 12 August 2016 (UTC)

deleted, see my deletion notice in proposed deletions. -jkb- (talk) 23:31, 13 August 2016 (UTC)

Proofreadpage on the Norwegian Wikisource

Tracked in Phabricator
Task T142921

When editing a page in the "Index" namespace on the Norwegian Wikisource, the attributes of s:no:MediaWiki:Proofreadpage index attributes don't seem to be used. For example, try to edit s:no:Indeks:Nansen,Fridtjof-Fram over Polhavet I-1942.djvu. In the edit window, only 8 fields are shown, while a lot more are listed in "MediaWiki:Proofreadpage index attributes". Could anyone help us find out why? Kåre-Olav (talk) 21:02, 11 August 2016 (UTC)

Hi, Kåre-Olav! MediaWiki:Proofreadpage index attributes and MediaWiki:Proofreadpage js attributes can be deleted, if they exist, because they are substituted by MediaWiki:Proofreadpage index data config‎. More information in Wikisource:ProofreadPage/Improve_index_pages#Improvement_of_the_index_form. I suggest adding some short help text at "Help" field (e.g. mouse over "?" symbol in "language code" in multilingual Wikisource (e.g.)). Best regards! -Aleator 00:08, 12 August 2016 (UTC)

Thanks. I have deleted those two pages. Still, the index page form doesn't seem to actually use the attributes which are given on our s:no:MediaWiki:Proofreadpage index data config. As you can see, there are more than 15 attribute names on that page, while only 8 are shown in the index edit form... I tried to copy the one you have on this wiki, but still no changes in the form. Kåre-Olav (talk) 13:20, 12 August 2016 (UTC)

Mmm... I better would revert this edit in s:no:MediaWiki:Proofreadpage index data config because it must be coordinated with s:no:MediaWiki:Proofreadpage_index_template, and the first now has new and unpaired items, and the second the desired 18 items that we want to see in the form.

Now, if we try to edit one Index and click on "show changes" button, (without modifying nothing), there will be unwanted (?) changes: this index still turns from 18 items (still not appeareing on the form) to 8 items (still 8 fields in the form). But why we still see e.g. "Merknader" form field??? It has to come from the now deleted and hardcoded s:no:MediaWiki:Proofreadpage index attributes. But if s:no:MediaWiki:Proofreadpage index data config exists, and it exists, "Merknader" must not appear. The only explanation I can figure out is that we have to wait for some update or refresh. Let's see again in 24 hours (any other help comments will be welcome). -Aleator 01:45, 13 August 2016 (UTC)

I've reverted that edit. Nothing happened. It seems to me that our wiki is ignoring all pages in the MediaWiki namespace and using a default instead. Look at s:no:MediaWiki:Sidebar. Here we have included a link to our local Scriptorium (Kontoret), but it doesn't show up in the sidebar. What could be causing this? Kåre-Olav (talk) 19:11, 15 August 2016 (UTC)

Hi Kåre-Olav! I opened phab:T142921 because I don't know what is happening; let's wait for the help of the developers. Perhaps it has relation to some bugs (like phab:T126146) which afected some Norwegian wikis because of the no-nb language code confusion. In any case, if other users can have a look that would be great. Best regards! -Aleator 09:05, 16 August 2016 (UTC)

Great, thanks! Kåre-Olav (talk) 19:04, 16 August 2016 (UTC)

No feedback. Waiting... -Aleator 21:19, 5 September 2016 (UTC)

Tech News: 2016-33

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• Last week Tech News announced you will get a notification when you mention yourself the same way as if someone else had mentioned you. This caused some problems and will happen later instead. [227]
• Creating and editing links to sections on other pages on the wiki now works again in the visual editor. [228]
• For some users, cross-wiki notifications haven't been working properly. The count has been wrong when only cross-wiki notifications were present. The cross-wiki bundle has been showing only the names of wikis and not the actual notifications. This will be fixed soon. [229][230]

Changes this week

• The login session when you choose "Keep me logged in" will now last a year. Previously it was 30 days. This will happen on August 16. [231]
• Some abuse filters will have to be updated during the week. This is because a bug will be fixed. [232]
• In compact language links, two new kinds of languages will be shown in the shorter language list: Languages that are used in the article's text, and languages where the article has a badge like "featured article" or "good article". [233][234]
• The visual editor will be available by default for logged-out editors on Wikipedias that use the Arabic script. It is already default for logged-in editors. [235]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from August 16. It will be on non-Wikipedia wikis and some Wikipedias from August 17. It will be on all wikis from August 18 (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on August 16 at 19:00 (UTC). See how to join.

Future changes

• Starting the week of August 22 there will be three software deployment windows. They will be at 13:00, 18:00, and 23:00 UTC. This is to have more times when software of the wikis can be updated and make it easier for developers in different parts of the world. [236]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:37, 15 August 2016 (UTC)

Tech News: 2016-34

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The ORES review tool is now available on Special:Contributions as a beta feature. It can make it easier to find contributions that are probably damaging the wikis. The ORES review tool is available on Wikidata and Persian, Polish, Portuguese, Dutch, Turkish and Russian Wikipedia. [237]
• The norm and ccnorm functions have been updated to make it easier to write abuse filters. This also affects the TitleBlacklist extension. You don't have to transform "I" and "L" to "1", "O" to "0" and "S" to "5" anymore. [238]
• The old pageview data in the "pagecounts-raw" and "pagecounts-all-sites" files is no longer being updated. You can find the new pageview data here. This happened on August 5. [239]

Problems

• Some big image files could not be thumbnailed. This has now been fixed. [240]
• When you moved a page over a redirect it would delete the redirect without saving it in the logs. This has now been fixed. [241]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 23 August. It will be on non-Wikipedia wikis and some Wikipedias from 24 August. It will be on all wikis from 25 August (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 23 August at 19:00 (UTC). See how to join.

Future changes

• Sometimes when you mention another user they don't get a notification. You will be able to get a notification when you successfully sent out a mention to someone or be told if they did not get a notification. This will be opt-in. You can test this on the test wiki. [242][243]
• How you add text after an edit conflict might work in a different way in the future. You can test the prototype. [244]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:18, 22 August 2016 (UTC)

Tech News: 2016-35

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Wikimedia mobile sites now don't load images if the user doesn't see them. This is to save mobile data and make the pages load faster. [245]
• When you edit a table with the visual editor, pressing Tab in the last cell of a row will take you to the first cell in the next row. Pressing Shift and Tab in the first cell of a row will take you to the last cell in the previous row. [246]

Changes this week

• The name of the "Save page" button will change. The button will say "Publish page" when you create a new page. It will say "Publish changes" when you change an existing page. [247][248]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 30 August. It will be on non-Wikipedia wikis and some Wikipedias from 31 August. It will be on all wikis from 1 September (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 30 August at 19:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is "RfC: image and oldimage tables". The meeting will be on 31 August at 21:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:59, 29 August 2016 (UTC)

Tech News: 2016-36

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Word-level diffs now work in longer paragraphs. [249]
• Interactive maps now have a frame by default. This is to make them look like other multimedia objects. This affects all Wikivoyages, the Catalan, Hebrew, Macedonian Wikipedias and Meta. [250]
• When you preview the MediaWiki:Captcha-ip-whitelist page it will show a validation output of the listed IP addresses instead of the list of addresses only. This can help you to identify if your whitelist rules will work or not. [251]

Changes this week

• You will be able to use <maplink> on all Wikipedias. It creates a link to a full screen map. [252][253]
• Sometimes when you mention another user they don't get a notification. You will be able to get a notification when you successfully send out a mention to someone or be told if they did not get a notification. This will be opt-in. [254][255]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 6 September. It will be on non-Wikipedia wikis and some Wikipedias from 7 September. It will be on all wikis from 8 September (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 6 September at 19:00 (UTC). See how to join.

Future changes

• The CheckUser extension could work differently in the future. There is a Request for Comments to figure out how. [256]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:12, 5 September 2016 (UTC)

RevisionSlider

From September 13th on, RevisionSlider will be available as a beta feature in your wiki. The RevisionSlider adds a slider view to the diff page, so that you can easily move between revisions. The feature fulfills a wish from the German Community’s Technical Wishlist. Everyone is invited to test the feature and we hope that it will serve you well in your work!

Birgit Müller (WMDE) 15:08, 12 September 2016 (UTC)

Tech News: 2016-37

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Wikimedia Commons app for Android can now show nearby places that need photos. [257]
• <maplink> and <mapframe> can now use geodata from Open Street Map if Open Street Map has defined a region and given it an ID in Wikidata. You can use this to draw on the map and add information. [258][259]

Changes this week

• The RevisionSlider will be available as a beta feature on all wikis from 13 September. This will make it easier to navigate between diffs in the page history. [260]
• A new user right will allow most users to change the content model of pages. [261][262]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 September. It will be on non-Wikipedia wikis and some Wikipedias from 14 September. It will be on all wikis from 15 September (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 13 September at 19:00 (UTC). See how to join.

Future changes

• When you search on the Wikimedia wikis in the future you could see results from sister projects in your language. You can read more and discuss how this could work.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:04, 12 September 2016 (UTC)

Deceased user

moved from en:WS:AN by user:billinghurst

Eclecticology, who contributed thousands of edits here as early as 2002, has died; see [263]. This was announced over at w:en:WP:AN, the en:wp administrators' noticeboard. As a very infrequent visitor here, I'm unclear about the relationship between the English Wikisource and the non-language-affiliated version of Wikisource, but https://wikisource.org/wiki/User:Eclecticology was an administrator and bureaucrat over there, so I'd appreciate it if someone here would contact the folks over there. Nyttend (talk) 12:08, 14 September 2016 (UTC)

Sad news :(

I requested removal of his rights per standard procedure. Ankry (talk) 19:30, 14 September 2016 (UTC)

Sad news for me as well. Thank you Ankry for your action. -jkb- (talk) 07:10, 16 September 2016 (UTC)

Tech News: 2016-38

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• Last week's MediaWiki update was rolled back because of bugs. Creating new accounts did not work between 15 September 19:10 UTC and 16 September 12:50 UTC. [264][265]

Changes this week

• The new version of MediaWiki will hopefully be on test wikis and MediaWiki.org from 20 September. It will be on non-Wikipedia wikis and some Wikipedias from 21 September. It will be on all wikis from 22 September (calendar). This is the version that was meant to go out last week.

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 20 September at 19:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is multi-content revisions. The meeting will be on 21 September at 21:00 (UTC). See how to join.

Future changes

• Wikidata will start working on adding support for Wiktionary. The Wikidata development team is now taking one last look at the development plan. [266]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

22:08, 19 September 2016 (UTC)

Tech News: 2016-39

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• If your wiki wants numerical sorting in categories you can request it after a community decision. See how to request it. [267]
• When you edit text and mention a new username they are notified if you add your signature. Before this only happened under certain conditions. [268]
• Users are notified if they are mentioned in a section where you add your own signature even if you edit more than one section. Before, users were not notified if you edited more than one section in one edit. [269]

Problems

• The MediaWiki version that was supposed to come to the wikis two weeks ago was put on hold again because of new problems. The MediaWiki version after it is now on all wikis. [270][271]

Changes this week

• There will be no new MediaWiki version this week. [272]

Meetings

• You can join the next office hour with the Wikidata team. The meeting will be on September 27 at 16:00 (UTC). See how to join.

Future changes

• Abandoned tools on Tool Labs could be taken over by other developers. There is a new discussion on Meta about this. It will be discussed until 12 October and then voted on. [273]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:07, 26 September 2016 (UTC)

Grants to improve your project

Please help translate to your language:

Greetings! The Project Grants program is currently accepting proposals for funding. There is just over a week left to submit before the October 11 deadline. If you have ideas for software, offline outreach, research, online community organizing, or other projects that enhance the work of Wikimedia volunteers, start your proposal today! Please encourage others who have great ideas to apply as well. Support is available if you want help turning your idea into a grant request.

• Submit a grant request
• Get help: In IdeaLab or an upcoming Hangout session
• Learn from examples of completed Individual Engagement Grants or Project and Event Grants

I JethroBT (WMF) (talk) 20:11, 30 September 2016 (UTC)

Tech News: 2016-40

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 4 October. It will be on non-Wikipedia wikis and some Wikipedias from 5 October. It will be on all wikis from 6 October (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 4 October at 19:00 (UTC). See how to join.

Future changes

• Tidy will be replaced. Instead the HTML 5 parsing algorithm will be used to clean up bad HTML in wikitext. This would cause problems on a number of wikis. They need to be fixed first. [274]

• <slippymap> will not work on Wikivoyage after 24 October. You should use <mapframe> instead. If you need help to fix this before 24 October you should ask for it as soon as possible. [275]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:30, 3 October 2016 (UTC)

Creative Commons 4.0

Hello! I'm writing from the Wikimedia Foundation to invite you to give your feedback on a proposed move from CC BY-SA 3.0 to a CC BY-SA 4.0 license across all Wikimedia projects. The consultation will run from October 5 to November 8, and we hope to receive a wide range of viewpoints and opinions. Please, if you are interested, take part in the discussion on Meta-Wiki.

Apologies that this message is only in English. This message can be read and translated in more languages here. Joe Sutherland (talk) 01:34, 6 October 2016 (UTC)

Tech News: 2016-41

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can show Special:RecentChanges on a page by using {{Special:RecentChanges}}. You can now use tag filters by using {{Special:RecentChanges/tagfilter=tagname}}. [276]
• The notification badge is coloured if you have notifications. When you check the notification the badge will now turn grey on all wikis instead of just the local one. [277]
• Colours used in the Wikimedia wikis' main interface changed slightly. This is to make them easier to see for readers and editors with reduced eyesight. [278]

Changes this week

• Hidden HTML comments will be more visible when you edit with the visual editor. <!-- You write hidden HTML comments like this. --> [279]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 11 October. It will be on non-Wikipedia wikis and some Wikipedias from 12 October. It will be on all wikis from 13 October (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 11 October at 19:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topics this week is CREDITS files. The meeting will be on 12 October at 21:00 (UTC). See how to join.

Future changes

• Language converter syntax will soon no longer work inside external links. Wikitext like http://-{zh-cn:foo.com; zh-hk:bar.com; zh-tw:baz.com}- must be replaced. You will have to write -{zh-cn: http://foo.com ; zh-hk: http://bar.com ; zh-tw:http://baz.com }- instead. This only affects languages with Language Converter enabled. Examples of such languages are Chinese and Serbian. [280]

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:29, 10 October 2016 (UTC)

Tech News: 2016-42

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• There is a new newsletter from the Collaboration team at the Wikimedia Foundation. It will have more details about for example Flow and notifications. You can read the first issue.

Problems

• Some users got a warning about Wikipedia's security certificate last week. This was because of a problem GlobalSign had. This has now been fixed. Only a small number of users got the warning. [281]
• Editors couldn't edit semi-protected pages in the Wikipedia app for Android. This has now been fixed in the beta version. [282]

Changes this week

• There will be no new MediaWiki version this week. [283]

Future changes

• The Editing Department are working on a new wikitext editor. It will have tools that are in the visual editor but not in the wikitext editor today. You can read more about this. This is an early plan and things can change. The old wikitext editor will still exist.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:42, 17 October 2016 (UTC)

Tech News: 2016-43

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• The abuse filters had a problem and caught too many edits. This has now been fixed. [284]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from October 25. It will be on non-Wikipedia wikis and some Wikipedias from October 26. It will be on all wikis from October 27 (calendar).
• The "Search" text in the search box will show the name of the project. For example, on Wikipedia it will say "Search Wikipedia". [285]
• About a dozen wikis now have numerical sorting in categories. If your wiki wants numerical sorting in categories you can ask for it. [286]
• Some wikis that want numerical sorting in categories can also ask to use UCA to sort categories. The biggest difference is that characters with diacritics will be sorted together. For example, for most languages Ä will be sorted with A instead of at the end of the alphabet. This is not true for languages that have Ä as a character in their alphabet. Wikis that already use UCA are listed on Meta. Languages that can use UCA are listed on MediaWiki.org. You can test it.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:39, 24 October 2016 (UTC)

Tech News: 2016-44

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Now you can include Commons video films with subtitles in your wiki language. Before you could see translated videos on file page at Commons only. [287]
• Search now has an updated preference tab to configure the search completion suggester. [288]
• The visual editor is now available on all wikis using only one language script. [289]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from November 1^st. It will be on non-Wikipedia wikis and some Wikipedias from November 2^nd. It will be on all wikis from November 3^rd (calendar).
• Now you can use autocomplete for page names in "Preview page with this template" field when editing templates. [290]
• Special:NewPages can now be filtered by page size. [291]

Future changes

• New MediaWiki deployments will be now based on MediaWiki 1.29. [292]

Miscellaneous

• The Wikimedia Foundation's Technical Collaboration Guideline is available for community review. Any feedback welcome, in any language.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:18, 31 October 2016 (UTC)

Tech News: 2016-45

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Victoria Coleman is the new Chief technology officer for the Wikimedia Foundation. [293]
• First release candidate for MediaWiki 1.28 is now available. [294]
• .gitreview for MediaWiki branches and extensions switched from targeting a specific branch to using track=1. [295]
• Section numbers in Table of Contents boxes will use grey to improve readability. [296]

Changes this week

• The 2016 Community Wishlist Survey begins on 7 November.
• The new version of MediaWiki will be on test wikis and MediaWiki.org from November 8th. It will be on non-Wikipedia wikis and some Wikipedias from November 9th. It will be on all wikis from November 10th (calendar).
• Special:ActiveUsers will allow users groups selection. [297]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 8 November 2016 at 20:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topics this week are Image Thumbnail API and allow SVG files uploaded on MediaWiki to have XHTML namespaces. The meeting will be on 9 November at 21:00 (UTC). See how to join.

Future changes

• RevisionSlider will be enabled by default on all beta wikis, on testwiki, testwiki2, mediawikiwiki and de.wikipedia.org. [298][299][300]
• Upcoming holidays will impact deployments. The schedule has been published.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

23:01, 7 November 2016 (UTC)

Password reset

I apologise that this message is in English. ⧼Centralnotice-shared-help-translate⧽

We are having a problem with attackers taking over wiki accounts with privileged user rights (for example, admins, bureaucrats, oversighters, checkusers). It appears that this may be because of weak or reused passwords.

Community members are working along with members of multiple teams at the Wikimedia Foundation to address this issue.

In the meantime, we ask that everyone takes a look at the passwords they have chosen for their wiki accounts. If you know that you've chosen a weak password, or if you've chosen a password that you are using somewhere else, please change those passwords.

Select strong passwords – eight or more characters long, and containing letters, numbers, and punctuation. Joe Sutherland (talk) / MediaWiki message delivery (talk) 00:00, 14 November 2016 (UTC)

Adding to the above section (Password reset)

Please accept my apologies - that first line should read "Help with translations!". Joe Sutherland (WMF) (talk) / MediaWiki message delivery (talk) 00:11, 14 November 2016 (UTC)

Tech News: 2016-46

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• When you edit with the visual editor you can use meta + shift + k to add a reference. The meta key is often the control key or command key. [301]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from November 15. It will be on non-Wikipedia wikis and some Wikipedias from November 16. It will be on all wikis from November 17 (calendar).
• In Special:Preferences you can choose which language menus and buttons will be in. If there is no translation for that language, MediaWiki has a list of fallback languages. A fallback language is a language many will understand better than English. MediaWiki will now use English when there is no Ukrainian translation. [302]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 15 November at 19:00 (UTC). See how to join.

Future changes

• Magic links might not work in the future. [303]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:17, 14 November 2016 (UTC)

Tech News: 2016-47

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Administrators, bureaucrats, oversighters and checkusers can now use two-factor authentication. This makes their Wikimedia accounts more secure. This can be turned on in Special:Preferences. There are discussions on how to best turn it on for everyone. [304]
• You can now search for file properties. For example you can search for media type, how big a file is or what resolution it has. [305]
• The latest Collaboration team products newsletter has been published. It has more details about their work than Tech News has.

Problems

• A hacker group is hacking Wikimedia accounts. They can probably do this because users have the same passwords on Wikimedia wikis as on other sites. Please have a password you use only on the Wikimedia wikis and nowhere else. This is especially important for administrators, bureaucrats, oversighters and checkusers. These users can also turn on two-factor authentication. [306]

Changes this week

• There is no new MediaWiki version this week.
• RevisionSlider will be a default feature on German, Arabic and Hebrew Wikipedia. This will happen on 22 November. It will come to other wikis later. [307][308][309]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 22 November at 19:00 (UTC). See how to join.

Future changes

• It will be possible to do cross-wiki search. The developers who work on this are looking for communities that want to test this. [310]
• Hovercards will leave the beta stage. The Wikimedia Foundation Reading Web team wants communities to set Hovercards as a default option for readers who are not logged in. Communities that are interested can say so on the Hovercards talk page. [311]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:32, 21 November 2016 (UTC)

Tech News: 2016-48

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes this week

• When someone tries to log in to a blocked account they will be blocked by a cookie. This means their browser will be blocked even if they change their IP address. This makes it more difficult for returning vandals. [312]
• When you use Content Translation to adapt a template to a new translation it will work differently. You can adapt big templates such as infoboxes. Translators will have control over the template parameters. A first version of this is released this week. It is possible it will not work correctly with all templates. There will be more updates for this soon. [313]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 29 November. It will be on non-Wikipedia wikis and some Wikipedias from 30 November. It will be on all wikis from 1 December (calendar).
• Gadgets will have a new option called "hidden". This means you can register gadgets that can't be turned on or off from the preferences page. Hiding gadgets was already possible by using [rights=hidden]. You should now use [hidden] instead. [rights=hidden] in old gadgets should be changed to [hidden]. [314][315]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 29 November at 19:00 (UTC). See how to join.

Future changes

• Tool Labs could get two new policies. One would be to be able to adopt tools without an active developer. The other would be a right to fork. There is a request for comment on Meta.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:16, 28 November 2016 (UTC)

Tech News: 2016-49

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can choose to see users from specific user groups in Special:ActiveUsers. [316]
• Everyone can now see Special:UserRights. Previously only those who could change user rights could. Other users got an error message. [317]
• ORES can now show how likely an edit is to be damaging to the wiki with different colours. This only works for languages that have trained ORES to recognize damaging edits. [318]

Changes this week

• You will now see categories with 0 pages in Special:Categories. Previously you did not see empty categories there. [319]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 6 December. It will be on non-Wikipedia wikis and some Wikipedias from 7 December. It will be on all wikis from 8 December (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 6 December at 20:00 (UTC). See how to join.

Future changes

• The 2016 Community Wishlist Survey will decide what the Community Tech team will work on next year. You vote for wishes on the survey page until 12 December. You can see what has happened to last year's wishes on the 2015 results page.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:07, 5 December 2016 (UTC)

"copyvio invasion" from cawiki/commons

I found some users that uploaded a lot of copyvios and not appropriate files / audio files here:

• User:Francisco Mateus
• User:Francisco Esperança
• User:Joaquim villafane
• User:Orai Sebastião
• User:Luis Antonio Monsta
• User:Diego Lasvegah
• User:Luis Antonio Mãonsta
• User:Heidi Skill‎
• User:Moises Joaquim
• Evanildo Da Silva Tecnomant

I have found their accounts with the same uploads on cawiki and/or commons, mostly blocked there indef. I blocked the user and deleted the files, but might be there are some elder left or they will come in the next future. Pls have a look at this. Thanks -jkb- (talk) 21:40, 7 December 2016 (UTC)

@Aleator: you have some idea? -jkb- (talk) 21:44, 7 December 2016 (UTC)

@-jkb-: It seems to be related to some news that say Wikimedia and Facebook have given Angolans free access to their websites, but not to the rest of the internet. So, naturally, Angolans have started hiding pirated movies and music in Wikipedia articles (...) (e.g. w:en:Wikipedia:Wikipedia_Signpost/2016-03-23/In_the_media). In Angola the spoken language is Portuguese, which fits with some of their edits, but I cannot understand why they choose to edit on ca.wiki (it makes no sense). I'll have a look to uploaded files all around. Thanks for ping (that's a good invention :) -Aleator 16:03, 8 December 2016 (UTC)

Oh, thanks. OK, I am not admin on Facebook, and what WMF did concerning other projects ... OK, no comment. But all of the files and audio files were not sourced, not licenced / copyvios, fully out of scope here on sourceswiki. WMF should make an agreement where the kiddies can edit (yep, the most fotos were kids from Africa etc.); yep, the spoke portuguese so I don't know what they have been looking for in the dcatalan projets aölthough even editin in portuguese projets; the most blocks were on cawiki and commons (and now here). However, we have to delete the inputs. Thanks once more, -jkb- (talk) 01:01, 10 December 2016 (UTC)

I am a bit unhappy about the ongoing problems with the angolan kids. Yes, everybody knows the huge problems over there, not only with the education, internet and the situation of the youth. And everybody, me inclusive, must support the thought (see Aleators report above) to support the young people there with free access or whatever to WMF projects. But the people who are responsible for this had to instruct them what where when and how they can edit here. At present it seems to be a problem here, on commons and on ca.wiki because the angolan users supply us with a great amount of copyvios and other not suitable files. It costs us time to repair it, and more over, I do not delete the files and I do not block the users with pleasure, I'm sorry about it, but otherwise a chaos will uprise here soon. Any idea somebody? @Aleator: do you know what responsible person in the WMF could be contacted in this matter? Regards -jkb- (talk) 23:33, 11 December 2016 (UTC)

I've been searching and it seems the problems started December 2014. In wmf:Wikipedia Zero there is a mail to WZ team. I've also found this july 2015 link in Meta (m:Wikimedia_Forum/Archives/2015-07#Wikipedia_Zero_being_used_to_violate_copyright) which lists some WMF members that may be interested, so I ping them all 3: @AVrana (WMF), Dfoy (WMF), Jalexander-WMF: (I'll also ping them from Commons because 2 first user account don't exist here at Multilingual Wikisource). In any case it seems that it is a group of youngs (w:pt:Usuário(a) Discussão:Evanildo Da Silva Tecnomant has written a list of friends very close to the list above). I'm sure: they will get tired soon. Best regards! -Aleator 00:29, 12 December 2016 (UTC)

Tech News: 2016-50

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Users who have Yahoo email addresses could not use Special:EmailUser to send emails. This has now been fixed. Emails will now come from a @wikimedia.org address. Users who get an email from you will still reply to your email address and be able to see it. [320]
• You can now see how many categories and pages there are in the categories in Special:TrackingCategories. This is to help you find pages that could need attention. [321]
• Markup colours for reviewed and pending revisions in the page history and recent changes and logs now match Wikimedia standard colours. The "You have a new message on your talk page" notification will have a slightly different colour. [322]

Problems

• Because of work on cross-wiki watchlists global renaming is not working. The plan is to turn it on again on 16 December. Global renaming was turned off for a while in late November and early December as well. [323]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 December. It will be on non-Wikipedia wikis and some Wikipedias from 14 December. It will be on all wikis from 15 December (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on December 13 at 20:00 (UTC). See how to join.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:29, 12 December 2016 (UTC)

Numbers at the main page

What pages do you mean? I enter any language edition in the top ten and see completely different numbers... --Infovarius (talk) 10:45, 13 December 2016 (UTC)

@Infovarius: These are very old, outdated values based on these statistics. However, my attempt to update them almost a year ago was contested (see this discussion).

It seems there is no clear consensus which statistics should be used, if any. And it is a real problem as we have various statistics:

• official from meta
• ProofreadPage stats
• wikistats (being rebuild currently)

I can imagine many criteria that can be used. But, as various Wikisources are very different according to used technology, organization, encoding, etc., no single criterion allows to compare all Wikisources in a fair way. Just few examples:

	criterion	disadvantages
1.	number of "good articles"	definition of a good article varies among wikis: some wikis include pages from the Page namespace here, some do not; it is not fair to count a text from 50-page book as "1" when ProofreadPage is not used vs. as "51" when all 50 pages are "good articles"
2.	number of pages in the main namespace	in some wikis subpages are used to present short encyclopedic notes or dictionary entries; it is not fair to treat few-words entry in the same way as a novel; also some wikis use the Author ns, some present the same content in the main ns
3.	number of pages in the main namespace (without subpages)	in some wikis subpages are used for presenting content of large books; it is not fair to treat a multi-volume book in the same way as a short poem or large novel as a short poem; also some wikis use the Author ns, while others present information about authors in the main ns
4.	number of "proofread" / "validated" pages in the Page namespace	not all wikis use ProofreadPage; they would be discriminated
5.	number of pages in the Page namespace	as above + some wikis upload pure OCR which is not very valuable contribution
6.	number of bytes in all pages	some languages use mainly single-byte Unicode characters, some base on multi-byte characters; also in few wikis multiple copies of almost the same content may be present (various orthography / alphabet / presentation form versions etc.)
7.	number of bytes in the main ns pages	see above + in wikis using ProofreadPage the main ns contains almost no content
8.	number of characters in all pages	some languages are more compact, some are more verbose
9.	database size	each edit creates a new copy of the whole page in the database; so wikis with edits to large pages (not using ProofreadPage) would be preferred here
10.	number of pageviews per day/month/year	wikisource traffic is generally low and it is easy to falsify it; so not very reliable; our activity should be based on creating content, not on traffic generation

Maybe we should start the discussion again? I have no idea which criterion or which criteria are the best to be used on the main page. Ten of them seems to be too many. Ankry (talk) 15:28, 13 December 2016 (UTC)

Yeah, good review. So many criteria... I can propose a new one: a number of creative works (can be obtained by a query to Wikidata). --Infovarius (talk) 15:57, 13 December 2016 (UTC)

You are joking, aren't you? Ankry (talk) 20:53, 13 December 2016 (UTC)

New way to edit wikitext

Summary: There's a new opt-in Beta Feature of a wikitext mode for the visual editor. Please go try it out.

We in the Wikimedia Foundation's Editing department are responsible for making editing better for all our editors, new and experienced alike. We've been slowly improving the visual editor based on feedback, user tests, and feature requests. However, that doesn't work for all our user needs: whether you need to edit a wikitext talk page, create a template, or fix some broken reference syntax, sometimes you need to use wikitext, and many experienced editors prefer it.

Consequently, we've planned a "wikitext mode" for the visual editor for a long time. It provides as much of the visual editor's features as possible, for those times that you need or want wikitext. It has the same user interface as the visual editor, including the same toolbar across the top with the same buttons. It provides access to the citoid service for formatting citations, integrated search options for inserting images, and the ability to add new templates in a simple dialog. Like in the visual editor, if you paste in formatted text copied from another page, then formatting (such as bolding) will automatically be converted into wikitext.

All wikis now have access to this mode as a Beta Feature. When enabled, it replaces your existing wikitext editor everywhere. If you don't like it, you can reverse this at any time by turning off the Beta Feature in your preferences. We don't want to surprise anyone, so it's strictly an opt-in-only Beta Feature. It won't switch on automatically for anyone, even if you have previously checked the box to "Automatically enable most beta features".

The new wikitext edit mode is based on the visual editor, so it requires JavaScript (as does the current wikitext editor). It doesn't work with gadgets that have only been designed for the older one (and vice versa), so some users will miss gadgets they find important. We're happy to work with gadget authors to help them update their code to work with both editors. We're not planning to get rid of the current main wikitext editor on desktop in the foreseeable future. We're also not going to remove the existing ability to edit plain wikitext without JavaScript. Finally, though it should go without saying, if you prefer to continue using the current wikitext editor, then you may so do.

This is an early version, and we'd love to know what you think so we can make it better. Please leave feedback about the new mode on the feedback page. You may write comments in any language. Thank you.

James Forrester (Product Manager, Editing department, Wikimedia Foundation) --19:32, 14 December 2016 (UTC)

Abuse filter

@-jkb-, Jusjih, Satdeep Gill, Tpt, Yann:@Zyephyrus: To minimize recent problems with Angolan/Wikipedia_zero users using wikis as file-sharing sites, I just added a filter limitting file uploads by low-contribution users. Everybody is still authorized to upload djvu/pdf. Other files should mostly go to Commons. Let me know if you see any problem with this filter. Ankry (talk) 13:44, 15 December 2016 (UTC)

• just as I told you on your talk page: very good and useful idea, thanks. -jkb- (talk) 14:41, 15 December 2016 (UTC)

Amazing idea. Thank you. --Satdeep Gill (talk) 16:13, 15 December 2016 (UTC)

Tech News: 2016-51

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Tech News

• Because of the holidays the next issue of Tech News will be sent out on 9 January 2017.
• The writers of the technical newsletter are asking for your opinion. Did you get the information you wanted this year? Did we miss important technical news in 2016? What kind of information was too late? Please tell us! You can write in your language. Thank you!

Recent changes

• Administrators and translation administrators can now use Special:PageLanguage on wikis with the Translate extension. This means you can say what language a page is in. The Translate extension will use that language as the source language when you translate. Previously this was always the wiki's default language. This was usually English. [324]
• Wikis connected to Wikidata can now use the parser function {{#statements: }} to get formatted data. You can also use {{#property: }} to get raw data. You can see the difference between the two statements. There are also similar new functions in Lua. [325]

Problems

• Some abuse filters for uploaded files have not worked as they should. We don't know exactly which filters didn't work yet. This means some files that filters should have prevented from being uploaded were uploaded to the wikis. MediaWiki.org and Testwiki have been affected since 13 October. Commons and Meta have been affected since 17 October. Other wikis have been affected since 17 November. [326]

Changes this week

• There is no new MediaWiki version this week. There will be no new MediaWiki version next week either.

Meetings

• The next meeting with the VisualEditor team will be on 3 January at 20:00 (UTC). During the meeting, you can tell developers which bugs you think are the most important. See how to join.

Future changes

• The 2016 Community Wishlist Survey is done. It decides what the Community Tech team will work on during 2017. You can see the results.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:33, 19 December 2016 (UTC)

Using AWB on Multilingual Wikisource

Multilingual Wikisource is not available as an option on AWB. Can anyone suggest a solution ? --Satdeep Gill (talk) 01:41, 29 December 2016 (UTC)

@Satdeep Gill: Options→Preferences→Site→Project: Custom→https://wikisource.org/w/. —Justin (koavf)❤T☮C☺M☯ 06:15, 29 December 2016 (UTC)

@Koavf: Thanks a lot. --Satdeep Gill (talk) 06:26, 29 December 2016 (UTC)

@Satdeep Gill: No problem. You will probably have better luck in the future getting questions answered if you post to w:WT:AWB but I monitor this page as well. —Justin (koavf)❤T☮C☺M☯ 06:27, 29 December 2016 (UTC)

Removing gu

Wikisource:Languages I have edited this to remove Gujarati texts and requested that Category:Gujarati and Category:ગુજરાતી be deleted. s:gu: exists and no texts are hosted here (although the project page said otherwise until I edited it). —Justin (koavf)❤T☮C☺M☯ 16:09, 29 December 2016 (UTC)

OK. Done. Ankry (talk) 19:15, 31 December 2016 (UTC)