Hi all,
The next CREDIT showcase will be Thursday, 12-May-2016 at 1800 UTC (1100
SF).
https://www.mediawiki.org/wiki/CREDIT_showcase
For this one we'll use Hangouts on Air for presenters, and the customary
YouTube stream for viewers.
See you next month!
-Adam
2016-04-12 14:01 GMT+03:00 Adrian Heine <adrian.heine(a)wikimedia.de>:
> Hi everyone,
>
> as some of you might know, I'm a software developer at Wikimedia
> Deutschland, working on Wikidata. I'm currently focusing on improving
> Wikidata's support for languages we as a team are not using on a daily
> basis. As part of my work I stumbled over a shortcoming in MediaWiki's
> message system that – as far as I see it – prevents me from doing the right
> thing(tm). I'm asking you to verify that the issue I see indeed is an issue
> and that we want to fix it. Subsequently, I'm interested in hearing your
> plans or goals for MediaWiki's message system so that I can align my
> implementation with them. Finally, I am hoping to find someone who is
> willing to help me fix it.
First of all, thanks for working on this issue. It is a real issue,
but not often requested. I think that is because manually checking in
every place whether the language code is unexpected (different from
the one in current context) would be cumbersome and always outputting
language codes on every tag would be bloaty. Best would be if this
checking was automated in a templating library, but so far templating
hasn't been much adopted in MediaWiki core. But of course this
information needs to be exposed first, which is what I understand you
are doing.
> == The issue ==
>
> On Wikidata, we regularly have content in different languages on the same
> page. We use the HTML lang and dir attributes accordingly. For example, we
> have a table with terms for an entity in different languages. For missing
> terms, we would display a message in the UI language within this table. The
> corresponding HTML (simplified) might look like this:
>
> <div id="mw-content-text" lang="UILANG" dir="UILANG_DIR">
> <table class="entity-terms">
> <tr class="entity-terms-for-OTHERLANG1" lang="OTHERLANG1"
> dir="OTHERLANG1_DIR">
> <td class="entity-terms-for-OTHERLANG1-label">
> <div class="wb-empty" lang="UILANG" dir="UILANG_DIR">
> <!-- missing label message -->
> </div>
> </td>
> </tr>
> </div>
> </div>
>
> This works great as long as the missing label message is available in the UI
> language. If that is not the case, though, the message is translated
> according to the defined language fallbacks. In that case, we might end up
> with something like this:
>
> <div class="wb-empty" lang="arc" dir="rtl">No label defined</div>
>
> That's obviously wrong, and I'd like to fix it.
>
> == Fixing it ==
>
> For fixing this, I tried to make MessageCache provide the language a message
> was taken from [1]. That's not too straight-forward to begin with, but while
> working on it I realized that MessageCache is only responsible for following
> the language fallback chain for database translations. For file-based
> translations, the fallbacks are directly merged in by LocalisationCache, so
> the information is not there anymore at the time of translating a message. I
> see some ways to fix this:
>
> * Don't merge messages in LocalisationCache, but perform the fallback on
> request (possibly caching the result)
> * Tag message strings in LocalisationCache with the language they are in
> (sounds expensive to me)
> * Tag message strings as being a fallback in LocalisationCache (that way we
> could follow the fallback until we find a language in which the message
> string is not tagged as being a fallback)
>
> What do you think?
The current localisation cache implementation quite obviously trades
space for speed. In this light I would suggest option two, to tag the
actual language the string is in.
However, this trade-off might not make sense anymore, as we have more
languages and more messages, resulting in almost gigabyte size caches.
See also for example https://phabricator.wikimedia.org/T99740. I added
wikitech-l to CC in hopes that people who have worked on localisation
cache more recently would comment on whether option one, to not merge
messages, would make more sense nowadays.
>
> [1] https://gerrit.wikimedia.org/r/282133
>
-Niklas
PhpStorm, InteliJ IDEA, Resharper and other JetBrain users, we just
received free upgraded licenses for all of their products.
Check your account at https://account.jetbrains.com/licenses and login with
that account inside your application to automatically use that license. If
you don't see the license, contact me or Sam Reed, and we will add you
right away. On IRC: yurik or reedy, or via email. We could also use a few
more admins for these licenses. You will no longer need to copy/paste any
licenses manually.
IDEA: use for PHP, JavaScript, Puppets, Ruby, and other web-related
technologies
https://www.jetbrains.com/idea/
Resharper: for C# and Microsoft Visual Studio C++
https://www.jetbrains.com/resharper/
CLion: for C++
https://www.jetbrains.com/clion/
Right now, MediaWiki has 2 pure-PHP engines to produce diffs (there's also
a native PHP extension wikidiff2, but we're not discussing it right now):
* DairikiDiff is what everybody uses, and
* Wikidiff3, and alternative implementation by Guy Van den Broeck that was
around for 8 years but required a configuration change
While less battle-tested, Wikidiff3 offers vastly improved performance on
heavy diffs compared to DairikiDiff. The price, however, is that it makes
certain shortcuts if the diff is too complex. I ran through 100K diffs from
English Wikipedia, and 6% of diffs were different. Lots of changes were
seemingly insignificant but I need your help with determining if it's
really so.
I've built this tool
<https://diff-forge.wmflabs.org/wiki/Special:DiffCompare>[1] to facilitate
the comparison. It displays two diffs from different algorithms side by
side (yeah, it can get too wide, I know:P). Which of them is which is
random. Parts with differences between the implementations are highlighted
in yellow. Below is the diff of differences for the reference. You can vote
with buttons above the diffs, no registration is required. If you see a
catastrophically bad diff please send me the link.
Unless the results are significantly worse, I'd like to go ahead and make
wikidiff3 the only implementation.
[1] https://diff-forge.wmflabs.org/wiki/Special:DiffCompare
--
Best regards,
Max Semenik ([[User:MaxSem]])
I am trying to work on https://ta.wikisource.org with python API.
This tamil wikisource has custom html option buttons to mention the edit status.
See a screenshot here.
https://snag.gy/f3aTBn.jpg
How to enable these custom option buttons via API?
Thanks.
--
Regards,
T.Shrinivasan
My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com
Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
http://FreeTamilEbooks.com
FYI
---------- Forwarded message ----------
From: Quim Gil <qgil(a)wikimedia.org>
Date: Thu, Apr 28, 2016 at 9:37 AM
Subject: Developer metrics workshop next to OSCON
To: "A mailing list for the Analytics Team at WMF and everybody who has an
interest in Wikipedia and analytics." <analytics(a)lists.wikimedia.org>,
Manrique Lopez <jsmanrique(a)bitergia.com>
Hi, is there anybody in this list planning to attend OSCON (Austin, May
16-19)?
http://conferences.oreilly.com/oscon/open-source-us
Next to that event there will be a workshop about Software Development
Analytics and the new Grimoire toolkit platform, on May 16th (10am - 1pm CDT
):
https://www.eventbrite.com/e/software-development-analytics-workshop-ticket…
The registration is not free, but the organizers (Bitergia, the developers
of http://korma.wmflabs.org/ ) are offering us a couple of invitations.
Andre and I are not attending OSCON (we have participated in the FOSDEM
edition of this workshop). If you or someone you know is interested,
contact me.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
FYI, the new models (BREAKING CHANGE) are now deployed.
On Sun, Apr 3, 2016 at 5:38 AM, Aaron Halfaker <aaron.halfaker(a)gmail.com>
wrote:
> Hey folks, we have a couple of announcements for you today. First is that
> ORES has a large set of new functionality that you might like to take
> advantage of. We'll also want to talk about a *BREAKING CHANGE on April
> 7th.*
>
> Don't know what ORES is? See
> http://blog.wikimedia.org/2015/11/30/artificial-intelligence-x-ray-specs/
>
> *New functionality*
>
> *Scoring UI*
> Sometimes you just want to score a few revisions in ORES and remembering
> the URL structure is hard. So, we've build a simple scoring user-interface
> <https://ores.wmflabs.org/ui/> that will allow you to more easily score a
> set of edits.
>
> *New API version*
> We've been consistently getting requests to include more information in
> ORES' responses. In order to make space for this new information, we needed
> to change the structure of responses. But we wanted to do this without
> breaking the tools that are already using ORES. So, we've developed a
> versioning scheme that will allow you to take advantage of new
> functionality when you are ready. The same old API will continue to be
> available at https://ores.wmflabs.org/scores/, but we've added two
> additional paths on top of this.
>
> - https://ores.wmflabs.org/v1/scores/ is a mirror of the old scoring
> API which will henceforth be referred to as "v1"
> - https://ores.wmflabs.org/v2/scores/ implements a new response format
> that is consistent between all sub-paths and adds some new functionality
>
> *Swagger documentation*
> Curious about the new functionality available in "v2" or maybe what the
> change was from "v1"? We've implemented a structured description of both
> versions of the scoring API using swagger -- which is becoming a defacto
> stanard for this sort of thing. Visit https://ores.wmflabs.org/v1/ or
> https://ores.wmflabs.org/v2/ to see the Swagger user-interface.
> Visithttps://ores.wmflabs.org/v1/spec/ or
> https://ores.wmflabs.org/v2/spec/ to get the specification in a
> machine-readable format.
>
> *Feature values & injection*
> Have you wondered what ORES uses to make it's predictions? You can now ask
> ORES to show you the list of "feature" statistics it uses to score
> revisions. For example,
> https://ores.wmflabs.org/v2/scores/enwiki/wp10/34567892/?features will
> return the score with a mapping of feature values used by the "wp10"
> article quality model in English Wikipedia to score oldid=34567892
> <https://en.wikipedia.org/wiki/Special:Diff/34567892>. You can also
> "inject" features into the scoring process to see how that affects the
> prediction. E.g.,
> https://ores.wmflabs.org/v2/scores/enwiki/wp10/34567892?features&feature.wi…
>
> *Breaking change -- new models*
> We've been experimenting with new learning algorithms to make ORES work
> better and we've found that we get better results with gradient boosting
> <https://en.wikipedia.org/wiki/Gradient_boosting> and random forest
> <https://en.wikipedia.org/wiki/Random_forest> strategies than we do with
> the current linear svc
> <https://en.wikipedia.org/wiki/Support_vector_machine> models. We'd like
> to get these new, better models deployed as soon as possible, but with the
> new algorithm comes a change in the range of probabilities returned by the
> model. So, when we deploy this change, any tools that uses hard-coded
> thresholds on ORES' prediction probabilities will suddenly start behaving
> strangely. Regretfully, we haven't found a way around this problem, so
> we're announcing the change now and we plan to deploy this *BREAKING
> CHANGE on April 7th*. Please subscribe to the AI mailinglist
> <https://lists.wikimedia.org/mailman/listinfo/ai> or watch our project
> page [[:m:ORES <https://meta.wikimedia.org/wiki/ORES>]] to catch
> announcements of future changes and new functionality.
>
> In order to make sure we don't end up in the same situation the next time
> we want to change an algorithm, we've included a suite of evaluation
> statistics with each model. The filter_rate_at_recall(0.9),
> filter_rate_at_recall(0.75), and recall_at_fpr(0.1) thresholds represent
> three critical thresholds (should review, needs review, and definitely
> damaging -- respectively) that can be used to automatically configure your
> wiki tool. You can find out these thresholds for your model of choice by
> adding the ?model_info parameter to requests. So, come breaking change,
> we strongly recommend basing your thresholds on these statistics in the
> future. We'll be working to submit patches to tools that use ORES in the
> next week to implement this flexibility. Hopefully, all you'll need to do
> is worth with us on those.
>
> -halfak & The Revision Scoring team
> <https://meta.wikimedia.org/wiki/Research:Revision_scoring_as_a_service>
>
Hello everyone,
The reading team's interaction consultation
<https://www.mediawiki.org/wiki/User_Interaction_Consultation> has been
wrapped up. Thanks for those who created new accounts in order to
participate and thanks to those who spent time writing proposals and adding
ideas. All in all we have 26 ideas. Some ideas are more relevant to the
topic of interaction than others, and some seemed more feasible than
others, so with these two parameters in mind, relevance and feasibility,
we have put together a shortlist, and added them as potential ideas for
brainstorming for Q1
https://www.mediawiki.org/wiki/Reading/Quarterly_planning/Q1. The
conversation can continue on the talk pages for each proposal or on the
talk page of Q1 planning. We added ideas to Q1 planning, which is the
earliest planning stage at the momet, however, ideas that don't get a
chance for further research or implementation in Q1, will be still be
considered for Q2, and other future plans, this is not the end of it :-).
This has been an interesting experiment, with lots of learning that
extended beyond the topic of interactivity, starting from how to avoid
jargon language on mailing lists, all the way, to how we really need to
enhance our mobile experiment to better serve our community engagement
through mobile.
Thanks to Wikimedia Foundation's communication team for their help with
promoting the consultation through our different non-wiki venues, and once
again thanks to all volunteers and staff who spent time in adding or
discussing ideas.
We are looking forward to the second phase of discussion, and to
possibilities of having proposals implemented starting Q1 or a distant
future to follow.
All the best,
Moushira
On Thu, Mar 17, 2016 at 2:12 AM, Derek V.Giroulle <
derekvgiroulle(a)wikimedia.be> wrote:
> Hello Moushira,
>
> Iḿ sorry i didn't say this explicitely , i was n persoanlly attacking you
> i was as you point out focussing the critic at jargon use in the WMF
>
> thanks
> derek
>
>
> On 16-03-16 17:58, Richard Symonds wrote:
>
>> Thanks Moushira :-)
>> On 16 Mar 2016 16:55, "Moushira Elamrawy" <melamrawy(a)wikimedia.org>
>> wrote:
>>
>> Hello again,
>>>
>>> I see that we have an interesting input here.
>>>
>>> Let me add further context, not to give any excuses but to put things in
>>> their perspective. This has nothing do to with corporate or jargon
>>> Silicon
>>> Valley culture, as I simply don't live in the US, and I don't have any
>>> corporate background :). I come from a design background, and while I am
>>> not a native English speaker, I didn't encounter any previous
>>> misunderstanding with using this word, in context, in the last decade,
>>> even
>>> with other non-native speakers.
>>>
>>> I now see the relevance of psychology in the use of the word "ideation"
>>> (where regardless of the article quality, we have the word used in both
>>> context
>>> <
>>>
>>> https://en.wikipedia.org/w/index.php?title=Special:WhatLinksHere/Ideation_%…
>>>
>>>> still)
>>>>
>>> . Given my non-medical background, and my previous use of the word,
>>> without
>>> failing to deliver what I needed to express at any point earlier, I,
>>> therefore, made a choice to include it in my email, which I wrote by
>>> myself
>>> without peer review.
>>>
>>> I see the point around the Foundation's seemingly repeated pattern of
>>> using
>>> words (or abbreviation) that aren't widely understood outside their
>>> context, or by a broader audience. While this is a valid concern, I just
>>> wanted to point out that our case here, is a matter of me failing to
>>> choose
>>> a term that isn't apparently jargon, because sometimes it is tricky to
>>> decide.
>>>
>>> Again, this is a good lesson on the importance of simplifying and
>>> globalizing my choice of words (oh, globalize could be jargon..no, not
>>> again ;).
>>>
>>> Point taken, thanks again everyone.
>>>
>>> Moushira
>>>
>>>
>>> On Wed, Mar 16, 2016 at 4:41 PM, Oliver Keyes <ironholds(a)gmail.com>
>>> wrote:
>>>
>>> While I agree with people that it's an uncommon and exclusionary
>>>> phrase (and a confusing one!) it seems like Moushira fully
>>>> acknowledges this and is going to work harder on this sort of problem
>>>> in the future, for which I laud her.
>>>>
>>>> If we want to have a general conversation about language choice at the
>>>> WMF, broadly-construed, it seems like it would be best to kick off a
>>>> new thread to avoid the appearance of a pileon.
>>>>
>>>> On Wed, Mar 16, 2016 at 9:13 AM, Derek V.Giroulle
>>>> <derekvgiroulle(a)wikimedia.be> wrote:
>>>>
>>>>> Hello everyone ,
>>>>>
>>>>> I agree with Fae and Craig,
>>>>> It's foreign jargon especially in this context , and on top of that
>>>>>
>>>> jargon
>>>>
>>>>> form a professional background where the term has been misused (imho)
>>>>> It has in my jargon the connotation of obsessively recurring idea ,
>>>>>
>>>> like
>>>
>>>> a
>>>>
>>>>> depressed patient
>>>>> always coming back to ideas of suicide : the suicidal ideation
>>>>> It would be the only place where i would allow fosuch reductive jargon
>>>>> because it has precise meaning
>>>>> i wouls never associate it with idea generation or brainstorming what
>>>>>
>>>> is
>>>
>>>> wrong with using those words
>>>>> as craig indicated : cringe worthy (business) jargon
>>>>> the mere fact that product design (business ing general) is stealing a
>>>>>
>>>> word
>>>>
>>>>> form other jargon
>>>>> show a lack of creativity of innovation
>>>>>
>>>>> I would like to call on the communications dept to start - and i can
>>>>>
>>>> just
>>>>
>>>>> picture someone for that task - a campaign
>>>>> at WMF to ban jargon "simply says it better"
>>>>>
>>>>>
>>>>> derek
>>>>>
>>>>>
>>>>>
>>>>> On 16-03-16 04:39, Craig Franklin wrote:
>>>>>
>>>>>> Hi Moushira,
>>>>>>
>>>>>> The problem when you use jargon like "ideation" in this context is
>>>>>>
>>>>> that
>>>
>>>> you're essentially excluding anyone who isn't familiar with the
>>>>>>
>>>>> particular
>>>>
>>>>> terminology used in the field. Especially so when there are plenty of
>>>>>> plain-English alternatives that can be used in its place. Note that
>>>>>>
>>>>> there
>>>>
>>>>> is a whole bunch of thought from experts that that word in particular
>>>>>>
>>>>> is a
>>>>
>>>>> particularly obnoxious piece of jargon:
>>>>>>
>>>>>> * http://money.cnn.com/2014/10/26/pf/corporate-jargon/
>>>>>> * https://hbr.org/2008/08/why-jargon-feeds-on-lazy-minds.html
>>>>>> *
>>>>>>
>>>>>>
>>>>>>
>>> http://www.lifed.com/10-cringeworthy-business-jargon-examples-that-should-b…
>>>
>>>> It's hardly the worst example I've seen out of the WMF, but while
>>>>>>
>>>>> we're
>>>
>>>> on
>>>>
>>>>> the topic it should be pointed out. Just because it's used elsewhere,
>>>>>>
>>>>> it
>>>>
>>>>> doesn't mean that the WMF has to fall into the same trap.
>>>>>>
>>>>>> Cheers,
>>>>>> Craig
>>>>>>
>>>>>> On 16 March 2016 at 10:07, Moushira Elamrawy <melamrawy(a)wikimedia.org
>>>>>> wrote:
>>>>>>
>>>>>> Hello Fae,
>>>>>>>
>>>>>>> Ideation phase [0], is a term widely used in product and design
>>>>>>>
>>>>>> context.
>>>>
>>>>> Now, I see your point around how volunteers who are not related to
>>>>>>>
>>>>>> these
>>>>
>>>>> fields, might not be familiar with it. Possibly something like, idea
>>>>>>> generation, or brainstorming could have replaced it.
>>>>>>>
>>>>>>> I am not sure though if the factors that you have listed are
>>>>>>>
>>>>>> relevant;
>>>
>>>> I
>>>>
>>>>> think it is a matter of using a word in a certain context where it
>>>>>>> actually
>>>>>>> fits, without realizing how a broader audience would perceive it.
>>>>>>>
>>>>>>> In any case, thanks for the note :-)
>>>>>>>
>>>>>>> [0] https://en.wikipedia.org/wiki/Ideation_%28creative_process%29
>>>>>>>
>>>>>>> Moushira
>>>>>>>
>>>>>>> On Wed, Mar 16, 2016 at 1:51 AM, Fæ <faewik(a)gmail.com> wrote:
>>>>>>>
>>>>>>> On 15 March 2016 at 22:33, Moushira Elamrawy <
>>>>>>>>
>>>>>>> melamrawy(a)wikimedia.org
>>>
>>>> wrote:
>>>>>>>> ...
>>>>>>>>
>>>>>>>>> The reading team is launching an experiment that supports early
>>>>>>>>>
>>>>>>>> engagement
>>>>>>>>
>>>>>>>>> in ideation phase, with a wide variety of users.
>>>>>>>>>
>>>>>>>> ...
>>>>>>>>
>>>>>>>> Hi, sorry to target your email with a more general observation,
>>>>>>>> however there seems to be a lot of odd jargon in Wikimedia
>>>>>>>> announcements over the last few months. It would be great to see
>>>>>>>>
>>>>>>> more
>>>
>>>> 'official' emails aimed at volunteers, written in plain and
>>>>>>>> grammatically complete English. Phrases like "ideation phase" may be
>>>>>>>> frequently used during meetings at the Wikimedia Foundation offices,
>>>>>>>> but are unlikely to be heard in real life by volunteer contributors,
>>>>>>>> and are unlikely to be easily understood outside of corporate
>>>>>>>>
>>>>>>> America,
>>>
>>>> especially by those without English as their first language.
>>>>>>>>
>>>>>>>> Sorry again about picking at your announcement rather than any
>>>>>>>>
>>>>>>> other,
>>>
>>>> it just stood out today.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Fae
>>>>>>>> --
>>>>>>>> faewik(a)gmail.com https://commons.wikimedia.org/wiki/User:Fae
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Wikimedia-l mailing list, guidelines at:
>>>>>>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>>>>>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>>>>>>> Unsubscribe:
>>>>>>>>
>>>>>>> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>>>
>>>> ,
>>>>
>>>>> <mailto:wikimedia-l-request@lists.wikimedia.org
>>>>>>>>
>>>>>>> ?subject=unsubscribe>
>>>
>>>> _______________________________________________
>>>>>>> Wikimedia-l mailing list, guidelines at:
>>>>>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>>>>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>>>>>> Unsubscribe:
>>>>>>>
>>>>>> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>>>
>>>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>> Wikimedia-l mailing list, guidelines at:
>>>>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>>>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>>>>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>>>>>>
>>>>> ,
>>>
>>>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>>>>>
>>>>>
>>>>> --
>>>>> Kind regards,
>>>>> *Derek V. Giroulle*
>>>>> Wikimedia Belgium vzw.
>>>>> Treasurer
>>>>> Troonstraat 51 Rue du Trône, BE-1050 Brussels
>>>>> M: derekvgiroulle(a)wikimedia.be
>>>>> T: +32 494 134134
>>>>> F: +32 3666 2700
>>>>>
>>>>> _______________________________________________
>>>>> Wikimedia-l mailing list, guidelines at:
>>>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>>>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>>>>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>>>>
>>>> _______________________________________________
>>>> Wikimedia-l mailing list, guidelines at:
>>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>>>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>>>
>>>> _______________________________________________
>>> Wikimedia-l mailing list, guidelines at:
>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>>
>> _______________________________________________
>> Wikimedia-l mailing list, guidelines at:
>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>
>
> --
> Kind regards,
> *Derek V. Giroulle*
> Wikimedia Belgium vzw.
> Treasurer
> Troonstraat 51 Rue du Trône, BE-1050 Brussels
> M: derekvgiroulle(a)wikimedia.be
> T: +32 494 134134
> F: +32 3666 2700
> _______________________________________________
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>
Howdy,
A few updates on the work of the Discovery team this week. Thanks to those
who sent something in, and thank you for reading.
* David, Erik, and Trey had a discussion with JustinO about improving
recall and improving search in general. Semi-readable notes are in an
etherpad <https://etherpad.wikimedia.org/p/Recall>. Additional thoughts and
comments are welcome.
* Deb and Moiz had discussions with Abbey, Daisy and Edward about upcoming
surveys planned for the Wikipedia portal; awaiting Legal approval.
* The updated Perl version of TextCat is now available on GitHub
<https://github.com/Trey314159/TextCat>. Reminder: the PHP version
<https://github.com/wikimedia/wikimedia-textcat> has been available for a
while.
* Analysis has been completed
<https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/TextCat_Optimization…>
on low-performing [search] queries (< 3 results) on French, Spanish, and
Italian Wikipedias, to optimize performance on language identification with
TextCat on those wikis. German is coming up next.
* Analysis is complete on recent Wikipedia.org portal page A/B test: Wikipedia
Portal Test of Language Detection and Primary Link Resorting
<https://commons.wikimedia.org/wiki/File:Wikipedia_Portal_Test_of_Language_D…>
* Maps servers now have 16 varnish servers instead of 2 in 4 different data
centers instead of 1.
* A new Wikipedia portal A/B test will be released next week - it will add
in descriptive text to the sister project links at the bottom of the page.
* Search for a new analyst (Oliver's replacement) is going along well. We
got 169 applicants and some of them have done or are scheduled to do the
take-home analysis task.
----
Feedback and suggestions on this weekly update are welcome.
The full update, and archive of past updates, can be found on Mediawiki.org:
https://www.mediawiki.org/wiki/Discovery/Status_updates
--
Yours,
Chris Koerner
Community Liaison - Discovery
Wikimedia Foundation
