This message is a notice about forthcoming removal of a response field in
the REST API’s /page/summary endpoint. [1] This message is being cross
posted to wikitech-l and mediawiki-api-announce.
The endpoint is used in the Page Previews (“hovercards”) functionality on
the classic web (desktop) and Android & iOS experiences for Wikipedia, in
addition to numerous external experiences. We don't anticipate impacts on
the mainline Wikipedia experiences from this forthcoming field removal, as
the endpoint will still be operational.
The REST API's /page/summary endpoint provides an api_urls field in its
response with links to several other REST API endpoints supported by the
Page Content Service.
Three of the api_urls subfields refer to experimental endpoints that have
been removed from the REST API altogether in favor of newer API endpoints.
1. media (/page/media)
2. references (/page/references)
3. metadata (/page/metadata).
api_urls also contains subfields referring to stable endpoints that
continue to exist in the REST API:
1. summary (which is self referential)
2. edit_html (/page/html - the Parsoid HTML)
3. talk_html (/page/html/Talk:<title> - the Parsoid HTML for the
corresponding Talk page)
Wikimedia’s Product Infrastructure team intends to remove the api_urls
field of the /page/summary response.
A cursory review at https://codesearch.wmflabs.org/ and Wikimedia Git
mirrors suggests api_urls isn’t in use in consuming code.
Review of web logs suggests traffic for the following endpoints:
- The media endpoint is at about 5% of its original traffic before its
decommission and it appears to be from old Wikipedia for Android clients.
This is expected.
- The references endpoint’s Wikipedia for Android traffic does not seem
present and its other traffic appears to be from non-user application
software based on User-Agent header components.
-The metadata endpoint’s traffic seems to have all but stopped.
This change is being announced in advance of the change because the
endpoint is advertised as stable. [2]
Please update your clients if you rely on the presence of the api_urls
field. If this change poses a problem for your clients, please do let us
know as soon as possible at the tracking task:
https://phabricator.wikimedia.org/T247991
We plan to remove the api_urls field described here on or after 14 July
2020.
Thank you.
Adam Baso
Director of Engineering
Wikimedia Foundation
[1]
https://en.wikipedia.org/api/rest_v1/#/Page%20content/get_page_summary__tit…
[2] Refer to
https://www.mediawiki.org/wiki/API_versioning#End_point_stability and
https://www.mediawiki.org/wiki/Wikimedia_Product/Wikimedia_Product_Infrastr…
for more information on stability designations.
Hi - I hope this is the right list to ask this...
I've been working on an extension where I've been trying to create some
interactive form fields - basically allowing the user to click and add a
nested group of fields. The idea was to do this in Javascript using OOUI,
and I thought I could have the php side create the initial form and fields
and handle the results by extending the existing Mediawiki FormAction
(using HTMLForm etc.)
However, I'm getting lost in the documentation and I can't figure out
what is needed to make this work - or if I need a different approach? There
are a couple of things in particular I've got stuck on:
* having the $data provided to the onSubmit php method include any of the
added fields (if it's not in the original list from getFormFields() it
doesn't seem to be included)
* on the javascript side, finding the identifiers of particular DOM objects
(like a certain Field Layout) to use OOUI infusion on (when I try with
jquery selectors on classes for example I get errors, too many things seem
to match)
Is there a good example extension or part of Mediawiki itself that does
anything like this? Or any other hints? Do I just need to give up on
FormAction and use OOUI to create all the form fields and getRequest()
directly to parse the submitted data??
Arthur
Hello folks,
I am a Google Summer of Code student developer current working on the
task Evaluate
WebdriverIO replacements for our browser automation framework
<https://phabricator.wikimedia.org/T247835>. I have been trying to
replicate the tests in "mediawiki/core" using Puppeteer <https://pptr.dev> and
Cypress <https://cypress.io>. However a weird pop up on the CI breaks my
tests. I have created a separate task on Phabricator
<https://phabricator.wikimedia.org/T254775> addressing the same. The tests
run successfully on my local "mediawiki/core" setup. This pop up only
appears on the CI.
As a result of this, I am currently blocked on writing further code. It
would be awesome if someone could help me out with this issue or guide me
to setting up the CI environment on my local machine so that I can resolve
it.
Thank you,
Soham Parekh
Hello,
The committee has finished selecting new members and the new committee
candidates are (In alphabetical order):
- Amir Sarabadani
- Martin Urbanec
- MusikAnimal
- Tonina Zhelyazkova
- Tony Thomas
And auxiliary members will be (Also in alphabetical order):
- Huji
- Jayprakash12345
- Matanya
- Nuria Ruiz
- Tpt
You can read more about the members in [0]
The changes compared to last term are:
* Lucie has resigned in September 2019. Tpt (as one of auxiliary members)
filled her seat in the meantime and now Tpt is moving to be an auxiliary
member again.
* Martin Urbanec is joining the main committee to fill Lucie/Tpt seat
* Jay Prakash is joining auxiliary members
* Rosalie is leaving the auxiliary members.
This is not the final structure. According to the CoC [1], the current
committee publishes the new members and call for public feedback for *six
weeks* and after that, the current committee might apply changes to the
structure based on public feedback.
Please let the committee know if you have any concern regarding the members
and its structure until *09 June 2019* and after that, the new committee
will be in effect and will serve for a year.
[0]:
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Members/Candidates
[1]:
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee#Selection_of_new_m…
Amir, On behalf of the Code of Conduct committee
Best
Hi,
for HTML version seehttps://www.mediawiki.org/wiki/Scrum_of_scrums/2020-06-10
Željko
--
= 2020-06-10 =
== Callouts ==
* SRE moving various LVS microservices (e.g. termbox, citoid, mathoid)
into their TLS enabled LVS endpoints. Keep in mind
* Release Engineering
** [All] Review guidance at [[wikitech:Deployments/Covid-19]] and Code
Deployment Office Hour at 17:00UTC in #wikimedia-office
** "scap sync" will be renamed to "scap sync-world" in the next
release. If you use "scap sync" non-interactively, please add a note
to: [[phab:T250302]] (and also, explain why you're using it)
** Branch cut automation starts in 2 weeks with 1.35.0-wmf.37[0]!
Branches will be cut at 02:00 UTC every Tuesday starting June 16th.
Please yell if that's an issue: [[phab:T242446]]
== Product ==
=== Android native app ===
* Updates:
** In production: image tagging, mobile-html integration.
** Working on enhanced user contribution history screen.
=== Web ===
* Blocked by:
** language engineering + wikimedia DE. Trying to deprecate some skin
hooks for next MW release but blocked on the following changes
*** [[phab:T254565]] (ArticlePlaceholder)
*** [[phab:T253685]] (Wikibase)
*** [[phab:T252841]] (Wikibase)
*** [[phab:T253178]] (UniversalLanguageSelector)
* Updates:
** '''Summary''': continuing content width limiting for Desktop
Improvements Project (DIP), scaffolding Vue.js search.
** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project
(Vector / DIP)]]:
*** [[phab:T254295|<nowiki>WikidataPageBanner should no longer use
SkinTemplateOutputPageBeforeExec hook</nowiki>]]
*** [[phab:T254048|<nowiki>Render the FallbackSkin and SkinApi with a
simplistic SkinMustache class</nowiki>]]
*** [[phab:T254546|<nowiki>Language portlet no longer at the bottom of
sidebar</nowiki>]]
*** [[phab:T254391|<nowiki>Restore banners to skins (Vector)</nowiki>]]
*** [[phab:T253938|<nowiki>Future proof addPortletLink</nowiki>]]
*** [[phab:T246419|<nowiki>Build collapsible sidebar and sidebar
button </nowiki>]]
*** [[phab:T251212|<nowiki>[Dev] Drop VectorTemplate usage in Vector</nowiki>]]
*** [[phab:T244276|<nowiki>Add bandwidth tests for JavaScript and CSS
to Vector and component repo</nowiki>]]
*** [[phab:T234570|<nowiki>Tech debt: Drop Browser.supportsAnimations
method</nowiki>]]
*** [[phab:T60137|<nowiki>Deprecate the
SkinTemplateOutputPageBeforeExec hook</nowiki>]]
*** [[phab:T246420|<nowiki>Limit content width, and refine alignment &
styling of relevant elements</nowiki>]]
*** [[phab:T244392|Vue.js search case study]]:
**** See [[Reading/Web/Desktop Improvements/Vue.js case study/Status
log|weekly status updates]].
** Alex and Stephen in performance training last week.
=== Structured Data ===
* Updates:
** MachineVision updates
** preliminary work for SDAW
=== Language ===
* Blocking:
** Web - language engineering + wikimedia DE. Trying to deprecate some
skin hooks for next MW release but blocked on the following changes
*** [[phab:T254565]] (ArticlePlaceholder)
*** [[phab:T253685]] (Wikibase)
*** [[phab:T252841]] (Wikibase)
*** [[phab:T253178]] (UniversalLanguageSelector)
== Technology ==
=== Fundraising Tech ===
* Updates:
** Integrating lists of companies who match employee donations into
payments-wiki forms, building CiviCRM extension to sync the data.
[[phab:T249922]], [[phab:T251200]]
** Export Matching Gifts data to acoustic. [[phab:T254809]]
** Investigate donor data delivery tool. [[phab:T248699]]
=== Core Platform ===
* Blocking:
** WMDE/Wikidata would appreciate review/some thoughts on [[gerrit:603572]]
** Search Platform: MW Job consumers sometimes pause for several
minutes [[phab:T224425]]
=== Engineering Productivity ===
==== Release Engineering ====
* Updates:
** [All] Deployments/Covid-19 [[wikitech:Deployments/Covid-19]]
** Train Health
*** Train branch cut time is changing:
**** Starting with 1.35.0-wmf.37 on June 16th the wmf MediaWiki branch
cut will happen at 02:00 UTC every Tuesday…
*** Last week: 1.35.0-wmf.35 - [[phab:T253023]]
*** This week: 1.35.0-wmf.36 - [[phab:T254173]]
*** Next week: 1.35.0-wmf.37 - [[phab:T254174]]
=== Search Platform ===
* Blocked by:
** Core: MW Job consumers sometimes pause for several minutes [[phab:T224425]]
** DC-Ops: rack/setup/install relforge100[34] [[phab:T241791]]
* Updates:
** Fix CirrusSearch maint scripts call sites to use file names
compliant with autoloader [[phab:T250806]]
=== Site Reliability Engineering ===
* Blocking:
** Search Platform - DC-Ops: rack/setup/install relforge100[34] [[phab:T241791]]
* Updates:
** SRE moving various LVS microservices (e.g. termbox, citoid,
mathoid) into their TLS enabled LVS endpoints. Keep in mind.
== Wikimedia DE ==
=== Wikidata ===
* Blocked by:
** Core Platform: We would appreciate review/some thoughts on [[gerrit:603572]]
* Blocking:
** Web - language engineering + wikimedia DE. Trying to deprecate some
skin hooks for next MW release but blocked on the following changes
*** [[phab:T254565]] (ArticlePlaceholder)
*** [[phab:T253685]] (Wikibase)
*** [[phab:T252841]] (Wikibase)
*** [[phab:T253178]] (UniversalLanguageSelector)
Can anyone recommend an example or tutorial that demonstrates how to use Pywikibot for template parameter maintenance? Given a page title, I'd like to: (1) look for a template on the page, (2) add the template if it's missing, (3) set template parameters to specified values. Thank you!
-Michael H.
As the last release of Python 2 is finally out, the July release of
Pywikibot is going to be the **last release that supports Python 2**.
Support of Python 3.4 and MediaWiki older than 1.19 is also going to be
dropped. After this release, Pywikibot is not going to receive any further
patches and bug fixes related to those Python and MediaWiki versions.
Functions and other stuff specific to Python 3.4, Python 2.x or MediaWiki
older than 1.19 will be removed.
For your convenience, this release is marked with a "python2"
git tag and it is also the last 3.0.x release. In case you really need it,
the Pywikibot team created /shared/pywikibot/core_python2 repository in
Toolforge and a python2-pywikibot package in software repositories of some
operating systems.
The Pywikibot team strongly recommends that you migrate your scripts from
Python 2 to Python 3. The migration steps were described in the previous
message, which can be found here:
https://lists.wikimedia.org/pipermail/pywikibot/2020-January/009976.html
Detailed
plan of Python 2 deprecation with dates is described here:
https://www.mediawiki.org/wiki/Manual:Pywikibot/Compatibility
If you encounter any problems with the migration, you can always ask us
here: https://phabricator.wikimedia.org/T242120
Best regards,
Pywikibot team
The 1.35.0-wmf.36 version of MediaWiki is blocked[0].
The new version can proceed no further until these issues are resolved:
* Undefined indexes: start and end in includes/TimedMediaHandler.php +392
- https://phabricator.wikimedia.org/T254824
Once these issues are resolved train can resume. If these issues are
resolved on a Friday the train will resume Monday.
Thank you for your help resolving these issues!
-- Your humble train toiler
[0]. https://phabricator.wikimedia.org/T254824
[1]. <https://tools.wmflabs.org/versions/>
--
Jeena Huneidi
Software Engineer, Release Engineering
Wikimedia Foundation