The 1.35.0-wmf.30 version of MediaWiki is blocked[0].
The new version can't proceed to group2 [1] until this issue is resolved:
* T251409: Argument 1 passed to Parser::fetchTemplateAndTitle() must be
an instance of Title, null given, called in
/srv/mediawiki/php-1.35.0-wmf.30/extensions/Quiz/includes/Quiz.php on
line 258
- https://phabricator.wikimedia.org/T251409
If all issues are resolved before Thursday's train window, the train can
proceed to group2 at the usual time.
Thank you for your assistance!
-- Your scattered train secondary
[0]. <https://phabricator.wikimedia.org/T249962>
[1]. <https://tools.wmflabs.org/versions/>
Hello Everyone,
It's time for Wikimedia Tech Talks 2020 Episode 3! *This talk will take
place on 29 April 2020 at 5 PM UTC*.
*Title:* The Basics of cryptography using OpenPGP and GnuPG
*Speaker:* Lars Wirzenius, Senior Software Engineer
*Summary:* OpenPGP is the prevalent standard for cryptography for secure
software distribution and GnuPG is its prevalent Open Source
implementation. This talk introduces things at a conceptual level: what
cryptography is for, why is it useful, and the basic use of GnuPG by
creating cryptographic keys, using digital signatures, and encryption. No
previous experience with GnuPG or OpenPGP is needed, but all examples will
be using the Linux command line.
The link to the Youtube Livestream can be found here:
https://www.youtube.com/watch?v=gedV-OScuQY
During the live talk, you are invited to join the discussion on IRC at
#wikimedia-office
You can browse past Tech Talks here:
https://www.mediawiki.org/wiki/Tech_talks
If you are interested in giving your own tech talk, you can learn more
here:
https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Te…
Note: This is a public talk. Feel free to distribute through appropriate
email and social channels!
Kindly,
Sarah R. Rodlund
Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org
Hi,
for HTML version see
https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-04-29
Željko
--
= 2020-04-29 =
== Callouts ==
* Release Engineering
** [All] Review guidance at [[wikitech:Deployments/Covid-19]] and Code
Deployment Office Hour at 17:00UTC in #wikimedia-office
== Product ==
=== Android native app ===
* Blocked by:
** [[phab:T249770]] (Core Platform / mobile-html caching issue)
* Updates:
** Release of mobile-html integration in Beta. Release to production is
pending resolution of caching issues.
=== Web ===
* Updates:
** '''Summary''': new header, collapsible sidebar, Vue.js tasking, and
continuing desktop improvements project (DIP).
** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project (Vector
/ DIP)]]:
*** [[phab:T251212|<nowiki>Drop VectorTemplate usage in Vector</nowiki>]]
*** [[phab:T250851|<nowiki>Allow skins to override mediawiki.page.ready
initialisation</nowiki>]]
*** [[phab:T249372|<nowiki>[Dev] DRY up the menu templating code</nowiki>]]
*** [[phab:T249073|<nowiki>[Spike 4hrs] Discuss and agree on nomenclature
and rules for template partial usage</nowiki>]]
*** [[phab:T246170|<nowiki>Build new logo for Desktop Improvements
Header</nowiki>]]
*** [[phab:T244481|<nowiki>Provide basic FeatureManagement in Vector
codebase</nowiki>]]
*** [[phab:T244392|Vue.js search case study]]:
**** [[phab:T249051|<nowiki>[Spike 12.75 hrs] Where does the
application-specific Vue.js search code live and what impact does this
decision have on the long term?</nowiki>]]
**** Onboarding
** Mobile website (MinervaNeue / MobileFrontend):
*** [[phab:T246767|<nowiki>Implement Tap to show for lazy loaded images
without MutationObserver - Scrolling on a Kai OS mobile device can be slow
on articles with lazy loading</nowiki>]]
*** [[phab:T246838|<nowiki>Avoid SEO performance and user experience
penalties by addressing our handling of lazy loaded images using
IntersectionObserver</nowiki>]]
** Miscellaneous
*** [[phab:T138401|<nowiki>Replace jsduck with JSDoc3 across all Wikimedia
code bases</nowiki>]]
=== Product Infrastructure ===
* Updates:
** Push notifications infrastructure RFC: [[phab:T249065]]
=== Structured Data ===
* Updates:
** working on MediaSearch prototype
** fixing MachineVision bugs
** prototyping a vue version of the MachineVision UI
== Technology ==
=== Fundraising Tech ===
* Updates:
** Fixing issues with backup processor's NL bank transfer integration
** More rounds of fixes & code review on CentralNotice features -
subnational targeting, banner templates & clone campaign
** Removing last direct DB link between front-end payments forms and
back-end DB
=== Core Platform ===
* Blocking:
** Search Platform: MW Job consumers sometimes pause for several minutes
[[phab:T224425]]
** Android native app - [[phab:T249770]] (Core Platform / mobile-html
caching issue)
=== Engineering Productivity ===
==== Release Engineering ====
* Updates:
** [All] Deployments/Covid-19 [[wikitech:Deployments/Covid-19]]
** Train Health
*** Last week: No Train/No Deploys Tuesday - Friday
*** This week: 1.35.0-wmf.30 - [[phab:T249962]]
*** Next week: 1.35.0-wmf.31 - [[phab:T249963]]
=== Search Platform ===
* Blocked by:
** Core: MW Job consumers sometimes pause for several minutes
[[phab:T224425]]
* Updates:
** Add mapping for ORES topic field in ElasticSearch [[phab:T240550]]
** Remove usage of MEDIAWIKI_JOB_RUNNER from CirrusSearch extension
[[phab:T247129]]
=== Site Reliability Engineering ===
* Updates:
** Looking into new push notification service request [[phab:T250452]]
Slow process, fast rendering
Imagine someone edits a page, and that editing hits a very slow
tag-function of some kind. You want to respond fast with something
readable, some kind of temporary page until the slow process has finished.
Do you chose to reuse what you had from the last revision, if it the
content of the function hasn't changed, or do you respond with a note that
you are still processing? The temporary page could then update missing
content through an API.
I assume that a plain rerender of the page will occur after the actual
content is updated and available, i.e. a rerender will only happen some
time after the edit and the slow process would then be done. A last step of
the process could then be to purge the temporary page.
This work almost everywhere, but not for collections, they don't know about
temporary pages. Is there some mechanism implemented that does this or
something similar? It feels like something that should have a general
solution.
There are at least two different use cases; one where some existing
information gets augmented with external data (without really changing the
content), and one where some external data (could be content) gets added to
existing content. An example of the first could be verification of
references, wile the later could be natural language generation.
/jeblad
Hello everyone,
I just switched Gerrit to new UI. And it looks well (I believe that newer
versions have much better interface).
But, I don't know how to manage patch made via web interface.
My test patch: https://i.snipboard.io/4HSdbK.jpg
I don't know how to add and edit some file. I can't find these buttons from
documentation
https://gerrit-review.googlesource.com/Documentation/user-inline-edit.html
Can someone help me?
Best regards,
Zoran Dori
volunteer, Wikimedia Serbia
s: zoranzoki21.github.io e: zorandori4444(a)gmail.com
Hi everyone,
The first weekend of May the Wikimedia Hackathon 2020 in Tirana was
supposed to happen. As an alternative, we're organizing a remote
hackathon. Please have a look at
https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2020/Remote_Hackathon
and sign up if you're interested in participating.
All of the sessions, projects, and initiatives are run by the
participants themselves and not overseen by a core organizing team. All
ideas including technical projects and sessions, non-technical projects
and sessions, and social events/socal time are very welcome.
Please spread the word!
Maarten
Hey,
"Wikimedia Meet" [0] (https://meet.wmcloud.org), is a project in Wikimedia
CloudVPS for Wikimedians to meet virtually instead of using commercial
services like Zoom which might have security and privacy implications
[1][2]. Currently it's a jitsi (jitsi.org) installation.
If you want to just use/test it, let me know and I create you a user and
password. You can share the username and password with anyone you want to
meet but please do not post it publicly. In your email you can also give me
your desired user and password. **Do not reuse any password**. You can also
contact any of the ticketmasters instead of me:
https://meta.wikimedia.org/wiki/Wikimedia_Meet#List_of_ticketmasters
In order to make this project more robust, I'm looking for Ticketmasters
too, Ticketmasters create accounts for others (It doesn't require any
technical knowledge, you fill a form in web for others)
If you want to help maintaining it (which would be greatly appreciated) let
me know and I give you the needed access. I put the technical documentation
in mediawiki.org [3]. There are several bits you can help with, like
puppetizing it, scalability, observability, improving authentication,
trying to see if BBB can be used as well, and so much more. You can find
the tickets in the phabricator board and assign a ticket to yourself if you
feel like helping out.
[0] https://meta.wikimedia.org/wiki/Wikimedia_Meet
[1] https://blogs.harvard.edu/doc/2020/03/27/zoom/
[2]
https://www.theguardian.com/technology/2020/apr/02/zoom-technology-security…
[3] https://www.mediawiki.org/wiki/Wikimedia_Meet
Hope that would be useful for our users :)
Best
--
Amir (he/him)
