https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-04-04
= 2018-04-04 =
== Callouts ==
* Fundraising campaigns
https://meta.wikimedia.org/wiki/CentralNotice/Calendar - next up:
Netherlands 2018-04-03 through 2018-05-01
* Language -> VE/Editing https://phabricator.wikimedia.org/T188072 and
review of: https://gerrit.wikimedia.org/r/#/c/419402/
* Need help from RelEng with WDQS GUI build automation:
https://phabricator.wikimedia.org/T189811
* Wikidata selenium test stability problems:
https://phabricator.wikimedia.org/T189762
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by:
* Blocking:
* Updates:
** Reading Lists sync in beta since 03/29, finishing up 5.8 (
https://phabricator.wikimedia.org/tag/ios-app-v5.8.0-manatee-on-a-skateboar…
)
==== Android native app ====
* Blocked by:
* Blocking:
* Updates:
** Reading List syncing in Beta for a couple of weeks, currently running
survey to gather feedback from Beta users.
** Will begin initial rollout to production (10%) this week.
==== Readers Web ====
* Blocked by:
** Cached page previews not shown on refresh (services+Brandon Black)
https://phabricator.wikimedia.org/T184534. We'd like to fix this but it's
outside the scope of projects we usually work on. How can we move this
along?
* Blocking:
* Updates:
**
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome
1, Objective 4]]: Continue improving the ways that users can download
articles of interest for later consumption
* Preparing for deploy. Deploy of VirtualPageViews is being finished today,
switching focus to working out a site config deploy task. Thank you
Analytics!
*** Reading Web depends on SRE, RelEng, Reading Infra
==== Readers Infrastructure ====
* Blocked by:
* Blocking:
* Updates:
** TemplateStyles will be enabled on German Wikipedia on Wednesday
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome
1, Objective 4]]: Continue improving the ways that users can download
articles of interest for later consumption
*** Reading Web depends on SRE, RelEng, Reading Infra
**[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of
client apps by coalescing and moving more logic to the server.]]
***Reading Infra depends on Parsing, Services
===== Maps =====
* Blocked by:
* Blocking:
* Updates:
** Unblocked on ops today
** Gehel back from vacation this week
** Planning release to enwiki
==== Multimedia ====
* Updates
** File page MediaInfo display prototype: Slow progress
** Search prototype: Up on wmflabs instance, some kinks to work out
** UploadWizard multi-lingual captions: Patch up, working through review
*Quarterly goal dependency update:
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 3.1]] Prepare
for launch of the first Structured Data on Commons feature (multilingual
file captions)
***SDC depends on Multimedia,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
*** Most dependencies fulfilled, prototypes moving quickly through review
** [[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 2.1]]
Integrate structured file captions into search
*** SDC depends on Search Platform, Multimedia
*** Dependencies pretty much fulfilled, prototype up for perusal on wmflabs
instance
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Structured_Data#Segment_4:_Programs|Segment
4, Outcome 2]]: Develop a better understanding of existing needs for
Structured Commons- https://phabricator.wikimedia.org/T171252
*** Research depends on Multimedia
*** Haven't heard anything, happy to help
=== Contributors ===
==== Community Tech ====
* Blocked by:
* Blocking:
* Updates:
** Still working on GlobalPreferences
** Discussing the outcome of ACTRIAL with the community
==== Anti-Harassment Tools ====
* Blocked by:
* Blocking:
* Updates:
**
==== Editing ====
* Blocked by:
* Blocking:
** Updates: None
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.1]] Improve and consolidate our unified editing platform so that it's
great on all devices
***Editing depends on Parsing.
==== Parsing ====
* Blocked by:
* Blocking:
* Updates:
** Tidy replaced on a bunch more wikis today (all wikiquotes except
frwikiquote, all wikimedia wikis). More being replaced next week (ref.
announcement on wikitech-l & ambassadors-l)
** Today, at noon PT, we are going to be discussing with TTO about the
<poem> extension in #mediawiki-parsoid. We are trying to figure out whether
to merge <poem> into core ( https://phabricator.wikimedia.org/T54061 ) with
a different tag, or make other fixes to the poem extension. If you have an
interest in this extension, please show up in #mediawiki-parsoid.
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.6]] Support work towards unifying MediaWiki's parser implementations, in
liaison with Technology's MediaWiki team
***Parsing depends on MediaWiki Platform, Services
**[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing]] of
client apps by coalescing and moving more logic to the server.
***Reading Infra depends on Parsing, Services
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.1]] Improve and consolidate our unified editing platform so that it's
great on all devices
***Editing depends on Parsing
** Program 7, Outcome 2: Objective 1: Revision storage scaling
*** Services depends on SRE, Parsing
**[[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better
data|Outcome 2: Objective 1]]: Revision storage scaling
***Services depends on SRE, Parsing
==== Collaboration ====
* Blocked by:
* Blocking:
* Updates:
** Still dealing with fallout from the OOUI icon changes, need more
follow-ups from Volker (will talk to him)
** Deployed maps i18n code to maps-test, still working out issues before
prod deployment
==== Language ====
* Blocked by:
** Requesting review of https://gerrit.wikimedia.org/r/#/c/419402/ from
VE/Editing.
* Blocking:
* Updates:
** ContentTranslation version 2 work continue
** apertium upgrade done except fra-cat pair
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.1]] Improve and consolidate our unified editing platform so that it's
great on all devices
***Language depends on Editing
=== Audiences Design ===
* Blocked by:
* Blocking:
* Updates:
**
==== UI Standardization ====
* Blocked by:
* Blocking:
* Updates:
** OOUI – v0.26.2 released:
https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v…
*** Two icon deprecations: 'userActive'/'userInactive' & 'find' icon
*** 10 more icon and sizing patches as follow-ups to
https://phabricator.wikimedia.org/T97631 &
https://phabricator.wikimedia.org/T177432 rel in 0.26.0
** Work on size unification aftermath in different products (Notifications,
Flow, RevisionSlider)
** Style Guide technical and contents improvements ongoing with 4 open PRs
currently
** Transparency Report: Wrapping up accessiblity measurments
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
** Improved MediaWiki history reconstruction performance, less than half (7
hours now with spark 2)
** Preparing the migration of all Spark jobs to Spark2
** Lots of small-medium Wikistats2 front-end bug-fixes
** Ongoing: Aggregation of new Audiences EL events VirtualPageViews
(Popups) into pageview_hourly format.
=== Cloud Services ===
* Blocked by:
** Labvirt1021/22 still having initial install issues, working with DC Ops:
https://phabricator.wikimedia.org/T183937
** Labvirt1019/1020 still have RAID issues, working with DC Ops & HP ticket
open: https://phabricator.wikimedia.org/T187373
* Blocking:
* Updates:
** Madhu moved Dumps content hosting to new servers managed by Cloud
Services team.
*** Toolforge, Cloud VPS, Analytics NFS moved Monday 2018-04-02 with no
incident and minimal outage
*** dumps.wikimedia.org web interface & rsync moving on Wednesday 2018-04-04
*** More details at <https://etherpad.wikimedia.org/p/dumps-migration>.
** Tool catalog project led by James Hare has been branded "Toolhub" and
initial use cases published on meta <https://meta.wikimedia.org/wiki/Toolhub
>
** Chase got a functioning high availability OpenStack Neutron layer 3
network up in labtestn! There is more work to do, but this is a big Neutron
project milestone.
** Q4 goals posted on mediawiki.org
=== Fundraising Tech ===
* Blocked by:
* Blocking:
* Updates:
** EventLogging for fundraising landing page views:
https://gerrit.wikimedia.org/r/423952
** Short-term response to banner that loaded 3rd party script: add CSP only
on forced banner previews: https://gerrit.wikimedia.org/r/420754
** Looking at new bitcoin payment processor, as our current one is stopping
USD cashouts at the end of the month
** More work on new API for main CC processor
** CiviCRM custom data enhancements
=== MediaWiki Platform ===
* Blocked by:
* Blocking:
* Updates:
** MW 1.31 release planning
*** considering additional bundled extensions (
https://phabricator.wikimedia.org/T178349 )
** Pingback heartbeat patch merged
** MCR:
*** API updates for query modules are in Gerrit:
https://gerrit.wikimedia.org/r/#/c/413223/
*** Code review
** Actor table:
*** Further deployment is waiting on the schema change (
https://phabricator.wikimedia.org/T188299 )
*** 17 extension updates still need review:
https://gerrit.wikimedia.org/r/#/q/status:open+topic:bug/T167246-actor-migr…
** Comment table:
*** Follow up schema change is still in progress
https://gerrit.wikimedia.org/r/#/c/417039/
*** Toolforge view updating patch is merged and pending updates
*** The image_comment_temp merging patches are in Gerrit
**** All except one are blocked on the schema change
** Improving API test coverage:
*** 6 changes merged and 6 changes outstanding
** Code review and bug fixes
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.6]] Support work towards unifying MediaWiki's parser implementations, in
liaison with Technology's MediaWiki team
***Parsing depends on MediaWiki Platform, Services
**** MWPT working on relevant planning for Platform Evolution CDP to
prepare for next FY and will coordinate with Parsing as this progresses
**Prepare for launch of the first Structured Data on Commons feature
(multilingual file captions)
***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
**** MWPT meets weekly with SDC and WMDE
** [[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 1.1]] Assist
with deploying MultiContent Revisions on Commons
[[phab:T174022|T174022]] Implement multi-content revisions,
[[phab:T174023|T174023]] Implement MCR storage layer,
[[phab:T174045|T174045]] DB schema migration for MCR,
[[phab:T174044|T174044]] Deploy MCR storage layer,[[phab:T174043|T174043]]
Deploy Multi-Content Revisions
* SDC depends on MediaWiki Platform, WMDE
** MWPT meets weekly with SDC and WMDE
=== Performance ===
* Blocked by:
**
* Blocking:
**The train :-(
* Updates:
** Continuing to monitor SG datacenter rollout, looking great. Working on
a blog post.
** Thumbor patches, adding WebP support
** Safemode support for Visual Editor is out for review
** Coal has been updated to use Kafka
** Waiting on SRE for a rebuild of the mcrouter package (they're aware,
just haven't had time yet)
** Tons of ongoing CR
=== Release Engineering ===
* Blocked by:
* Blocking:
* Updates:
**
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome
1, Objective 4]]: Continue improving the ways that users can download
articles of interest for later consumption
*** Reading Web depends on SRE, RelEng, Reading Infra
=== Research ===
* Blocked by:
* Blocking:
* Updates:
*Quarterly goal dependency update:
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the
first Structured Data on Commons feature]] (multilingual file captions)
***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Structured_Data#Segment_4:_Programs|Segment
4, Outcome 2]]: Develop a better understanding of existing needs for
Structured Commons- T171252
***Research depends on Multimedia
=== Scoring Platform ===
* Blocked by:
** git-lfs support, we've tried deploying a git-lfs submodule and it
doesn't work. git-lfs is still lacking on the deployment node, but that
shouldn't affect the deployment itself. See task
https://phabricator.wikimedia.org/T180627
* Blocking:
* Updates:
=== Search Platform ===
* Blocked by:
* Blocking: https://phabricator.wikimedia.org/T190958 needs re-deploy
* Updates:
** Wikidata fulltext search is fully enabled, so there should be
improvements there
** Slovak stemmer analysis done:
https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Slovak_Stemmer_Analy…
** Next step - creating proper analysis plugin:
https://phabricator.wikimedia.org/T190815
** Fixed an issue with Wikidata RDF dumps:
https://phabricator.wikimedia.org/T185589
** Evaluating feature generation by `query_explorer` functionality of LTR
plugin: https://phabricator.wikimedia.org/T187148
** Working on query parsing refactoring:
https://phabricator.wikimedia.org/T185108
** Working on Lexeme completion search:
https://phabricator.wikimedia.org/T189745
** Need help with WDQS GUI build automation:
https://phabricator.wikimedia.org/T189811
** Wikidata selenium test stability problems:
https://phabricator.wikimedia.org/T189762
*Quarterly goal dependency update:
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the
first Structured Data on Commons feature]] (multilingual file captions)
***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 2.1]]
Integrate structured file captions into search
*** SDC depends on Search Platform, Multimedia
=== Security ===
* Blocked by:
* Blocking:
* Updates:
**
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.6]]: Support work towards unifying MediaWiki's parser implementations, in
liaison with Technology's MediaWiki team
***Parsing depends on MediaWiki Platform, Services
=== Services ===
* Blocked by: search on updating CirrusSearch jobs
* Blocking: none
* Updates:
** Moved a big bulk of jobs to kafka
** Resetting the restbase-dev environment
*Quarterly goal dependency update:
**<nowiki>*</nowiki>[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase
code sharing of client apps by coalescing and moving more logic to the
server.]]
***Reading Infra/Parsing, Services
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.6]] Support work towards unifying MediaWiki's parser implementations, in
liaison with Technology's MediaWiki team
***Parsing depends on MediaWiki Platform, Services
** [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for
better data|Outcome 2: Objective 1:]] Revision storage scaling
*** Services depends on SRE, Parsing
=== Site Reliability Engineering ===
* Blocked by:
** None
* Blocking:
** None
* Updates:
** Holiday week, really slow stuff not much to report
** HHVM CVE-2018-6334 patch rolled out this week
**
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome
1, Objective 4]]: Continue improving the ways that users can download
articles of interest for later consumption
*** Reading Web depends on SRE, RelEng, Reading Infra
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the
first Structured Data on Commons feature]] (multilingual file captions)
***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
** [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for
better data|Outcome 2: Objective 1]]: Revision storage scaling
*** Services depends on SRE, Parsing
== Wikidata ==
* Blocked by:
* Blocking:
* Updates:
**
*Quarterly goal dependency update:
**Prepare for launch of the first Structured Data on Commons feature
(multilingual file captions)
***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
** Objective 1.1 Assist with deploying MultiContent Revisions on Commons
T174022 Implement multi-content revisions, T174023 Implement MCR storage
layer, T174045 DB schema migration for MCR, T174044 Deploy MCR storage
layer,T174043 Deploy Multi-Content Revisions
***SDC depends on MediaWiki Platform, WMDE
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
** Following up on OOUI changes influencing AdvancedSearch
** Going to focus on FileImporter (a.k.a. MoveToCommons) again
== SoS Meeting Bookkeeping ==
* Updates:
**
...with apologies for cross-posting, but this is cool stuff! :)
--
deb tankersley
Program Manager, Engineering
Wikimedia Foundation
---------- Forwarded message ----------
From: Léa Lacroix <lea.lacroix(a)wikimedia.de>
Date: Thu, Apr 5, 2018 at 1:35 AM
Subject: [Wikidata] Improvements on the search results
To: "Discussion list for the Wikidata project." <
wikidata(a)lists.wikimedia.org>
Hello all,
Some improvements have been made by the Search team at WMF on Special:Search
<https://www.wikidata.org/wiki/Special:Search> (the page that is loaded
when you type something in the search field and press enter, for example).
- The string that you typed is highlighted in bold in the label of the
results
- The number of bytes is no longer displayed, instead you can see the
number of sitelinks and statements
- The code is now using the same indexing as completion search, which
should improve relevancy and better control over ranking
If you have any question or find a bug, feel free to ping user:Smalyshev
(WMF) <https://www.wikidata.org/wiki/User:Smalyshev_(WMF)>.
Cheers,
--
Léa Lacroix
Project Manager Community Communication for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
2018-04-04 23:41 GMT+03:00 Brad Jorsch (Anomie) <bjorsch(a)wikimedia.org>:
> On Wed, Apr 4, 2018 at 3:18 PM, Strainu <strainu10(a)gmail.com> wrote:
>
>> Skipping navboxes is a decision that was taken by the WMF team
>> responsible for the mobile site (whatever it was called at the time)
>> and can be solved cleanly only at the skin level, but I don't expect
>> this to happen as long as it will break the mobile site.
>>
>> Your proposal would be the ideal argument for reversing the current
>> "solution", yes, but realistically, it's not going to happen
>> throughout the hundreds of wikis that implemented navboxes.
>>
>
> Here we're talking about Isarra's very interesting project to make the
> Monobook skin responsive, not whatever decisions WMF's mobile teams may
> have made in the past for their mobile-only skin. She is not obligated to
> follow their lead just because they led, and I'd recommend she doesn't in
> this case.
Maybe I wasn't clear, but that's exactly what I meant as well: I'm
very curious to see how *Mobile MonoBook* handles that particular
issue. I most certainly hope Isarra *doesn't* follow Minerva's
(mis)behavior. If the solution is acceptable, perhaps it can then be
adapted to Minerva. However, I haven't found any navboxes in the demo
wiki.
Strainu
>
> Note that's my personal recommendation and not any sort of official WMF
> position. I likely won't even be involved in the code review for her patch.
>
>
> --
> Brad Jorsch (Anomie)
> Senior Software Engineer
> Wikimedia Foundation
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Folks,
As you'll have seen from previous email, we are now using a new beefier
webserver for your dataset downloading needs. And the old server is going
away on TUESDAY April 10th.
This means that if you are using 'dataset1001.wikimedia.org' or the IP
address itself in your scripts, you MUST change it before Tuesday, or it
will stop working.
There will be no further reminders.
Thanks!
Ariel
Hi everyone,
The Wikimedia Foundation is asking for your feedback in a survey. We want
to know how well we are supporting your work on and off wiki, and how we
can change or improve things in the future. The opinions you share will
affect the current and future work of the Wikimedia Foundation.
If you are volunteer developer, and have contributed code to any pieces of
MediaWiki, gadgets, or tools, please complete the survey. It is available
in various languages and will take between 20 and 40 minutes to complete.
*Follow this link to the Survey:*
https://wikimedia.qualtrics.com/jfe/form/SV_5ABs6WwrDHzAeLr?aud=DEV
If you have already seen a similar message on Phabricator, Mediawiki.org,
Discourse, or other platforms for volunteer developers, please don't take
the survey twice.
You can find more information about this survey on the project page
<https://meta.wikimedia.org/wiki/Community_Engagement_Insights/About_CE_>
and see how your feedback helps the Wikimedia Foundation support
contributors like you. This survey is hosted by a third-party service and
governed by this privacy statement
<https://wikimediafoundation.org/wiki/Community_Engagement_Insights_2018_Sur…>.
Please visit our frequently asked questions page
<https://meta.wikimedia.org/wiki/Community_Engagement_Insights/Frequently_as…>
to find more information about this survey.
Feel free to email me directly with any questions you may have.
Thank you!
Edward Galvez
--
Edward Galvez
Evaluation Strategist, Surveys
Learning & Evaluation
Community Engagement
Wikimedia Foundation
Hello dumps.wikimedia.org users,
The servers that host the dumps.wikimedia.org site are being replaced with
shiny new hardware! The web service migration is set to happen at 14:30 UTC
on Wednesday, April 4 2018. If you are trying to connect to
dumps.wikimedia.org around the migration window, you might experience a
short downtime. The switchover should ideally only take a few minutes, and
we'll keep you posted once it's all done, or if anything changes!
As always, please feel free to reach out to us with any questions or
concerns.
Best,
Madhumitha Viswanathan & Ariel Glenn
Wikimedia Foundation
Those of you that rely on the abstracts dumps will have noticed that the
content for wikidata is pretty much useless. It doesn't look like a
summary of the page because main namespace articles on wikidata aren't
paragraphs of text. And there's really no useful summary to be generated,
even if we were clever.
We have instead decided to produce abstracts output only for pages in the
main namespace that consist of text. For pages that are of type
wikidata-item, json and so on, the <abstract> tag will contain the
attribute 'not-applicable' set to the empty string. This impacts a very few
pages on other wikis; for the full list and for more information on this
change, see https://phabricator.wikimedia.org/T178047
We hope this change will be merged in a week or so; it won't take effect
for wikidata until the next dumps run on April 20th, since the wikidata
abstracts are already in progress.
If you have any questions, don't hesitate to ask.
Ariel
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **today, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
As we shared in October, Facebook has been testing a new feature that uses English Wikipedia content.[1] When users see news articles in their News Feed, the new feature provides more context about the article's source by pulling information about the publishers from English Wikipedia.[2]
The feature was initially made available to a limited number of users based in the United States as a part of their product testing. Today, Facebook will begin making this feature available to all of its users in the United States.
The Wikimedia Foundation first learned of the integration of Wikipedia content into Facebook’s Article Context feature ahead of its initial beta launch in October 2017. This new feature did not come from a partnership with the Wikimedia Foundation, though we were in contact with Facebook’s product and engineering teams ahead of this week’s launch.
During their test, Facebook was utilizing (and regularly updating) XML dumps to get the Wikipedia content. As a part of the full rollout of this feature, they will begin utilizing our API service - which provides them with more up-to-date content. According to Facebook, the results of their tests resulted in ~500 views a day. We are confident that we will be able to handle the scaling up of this feature. However, we will remain in contact with Facebook should any performance tweaks become necessary.
We are always happy to see people, companies, and organizations recognize Wikipedia’s value as a repository of free knowledge. At the same time, we are encouraging companies who use Wikipedia’s content to give back in the spirit of sustainability. Hopefully, Facebook will feel compelled to do so given their increased recognition of the amazing free knowledge repository you all have built together.
In the meantime, we are going to be tracking the impact of this new feature on English Wikipedia. Including looking at how many people click on the link to Wikipedia and seeing which pages are getting the most traffic. We will continue to keep you updated on our conversations with Facebook and impact of this new feature.
[1] https://lists.wikimedia.org/pipermail/wikimedia-l/2017-October/088791.html <https://lists.wikimedia.org/pipermail/wikimedia-l/2017-October/088791.html>
[2] https://newsroom.fb.com/news/2018/04/news-feed-fyi-more-context/ <https://newsroom.fb.com/news/2018/04/news-feed-fyi-more-context/>
_____________________
Joe Matazzoni
Product Manager
Wikimedia Foundation, San Francisco