Wikisource:Scriptorium/Archives/2016 - Wikisource
Jump to content
From Wikisource
Wikisource:Scriptorium
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)
reply
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)
reply
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)
reply
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)
reply
The mailing list:
Wikisource-l - November
;--
C.R.
talk
14:41, 9 December 2015 (UTC)
reply
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)
reply
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)
reply
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)
reply
I tried again to link
Author:Eduardo Scarpetta
to its wikidata item, I failed. Here my talk about M&S tool & mul.wikisource:
. 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)
reply
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)
reply
(minor additional comment)--
C.R.
talk
17:57, 9 December 2015 (UTC)
reply
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)
reply
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)
reply
Again, two cents:
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...;
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;
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)
reply
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)
reply
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)
reply
Re-reading, you are right I formulated point 1 in a very straight way :D --
C.R.
talk
17:49, 10 December 2015 (UTC)
reply
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)
reply
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)
reply
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)
reply
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)
reply
Alex brollo
: Do we really
want
interwiki links to mulws, betawv, and incubator? —
Justin (
ko
vf
05:20, 12 December 2015 (UTC)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
Hi, I don't think your edit shows the reality. Regards,
88.182.181.224
13:17, 21 February 2016 (UTC)
reply
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)
reply
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)
reply
Yann, is this the right screenshot? --
Zyephyrus
talk
10:32, 22 February 2016 (UTC)
reply
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)
reply
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)
reply
No consensus either on French WS
for the time being. Ideas? --
Zyephyrus
talk
10:13, 22 February 2016 (UTC)
reply
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)
reply
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)
reply
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)
reply
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)
reply
PS. could sb. move this discussion to Scriptorium, please?
Done
--
Zyephyrus
talk
18:19, 23 February 2016 (UTC)
reply
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)
reply
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:
(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
after that updates the article count
UpdateArticleCount.php
Zdzislaw
talk
14:24, 25 February 2016 (UTC)
reply
Hi, Sorry for replying so late.
Whether there is an internal link should be completely irrelevant when we use transclusions with
Yann
talk
07:40, 20 March 2016 (UTC)
reply
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
[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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
-jkb-
: It's hardly a perfect solution but we could encourage users who have CC-NC/ND texts to go to
and users who want to publish their own works to
Justin (
ko
vf
03:20, 1 February 2016 (UTC)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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:
. 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)
reply
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)
reply
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
Moreover, once the move is done www.wikisource.org can be re-used to become a true portal site, like Wikipedia has at
. 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)
reply
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)
reply
Support
--
Candalua
talk
15:58, 25 February 2016 (UTC)
reply
Support++ c' 'a pala
:D --
C.R.
talk
16:39, 25 February 2016 (UTC)
reply
--
Mizardellorsa
talk
16:51, 25 February 2016 (UTC)
reply
--
Aleator
17:41, 25 February 2016 (UTC)
reply
--
Micru
talk
11:17, 26 February 2016 (UTC)
reply
--
Alex brollo
talk
22:23, 26 February 2016 (UTC)
reply
--
Accurimbono
talk
11:57, 27 February 2016 (UTC)
reply
--
Jberkel
talk
15:05, 4 March 2016 (UTC)
reply
obviously,
VIGNERON
talk
14:34, 8 March 2016 (UTC)
reply
Strongly Support
Let's just use this wiki as the second white mouse for
phab:T21986
. --
Liuxinyu970226
talk
00:45, 3 April 2016 (UTC)
reply
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
and
).
John Vandenberg
talk
06:19, 20 April 2016 (UTC)
reply
NMaia
talk
03:16, 15 May 2016 (UTC)
reply
Oppose
Is the move absolutely needed? Our Main Page already points to many language subdomains.--
Jusjih
talk
23:51, 29 March 2016 (UTC)
reply
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)
reply
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)
reply
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
reply
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)
reply
probably
not
yes, butthis is not the only point: since more than 10 years everybody knows the
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)
reply
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)
reply
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)
reply
well the linking from outside (probably quite often) would be another question to solve.
-jkb-
talk
15:08, 27 February 2016 (UTC)
reply
Candalua
:Could the renaming into mul.wikisource.org help to solve the wikidata trouble?
Alex brollo
talk
16:20, 29 February 2016 (UTC)
reply
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)
reply
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
are redirected to
with first priority
if
the page exists in mul.wikisource.org
A variation of this may be redirecting all the traffic pointing to
pages to
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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)
reply
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
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)
reply
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)
reply
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)
reply
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.
will parse as
instead of
as it used to. Please use
or
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
and
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)
reply
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)
reply
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)
reply
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)
reply
Matiia
Done
Ankry
talk
13:10, 22 March 2016 (UTC)
reply
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 draft idea:
Module:testo
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)
reply
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)
reply
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)
reply
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
and
to mean
and
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
and
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
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
US