It's time for Wikimedia Tech Talks 2020 Episode 8! This talk will take place
Tuesday 22 September 2020 at 17:00 UTC.
Title: (Modern) Event (Data) Platform
Speaker: Andrew Otto, Staff Site Reliability Engineer
Summary:
Wikimedia's Event (Data) Platform provides a foundation for building
loosely coupled event driven software systems. This talk will go over why
we built Event Platform and give an overview of its components and how they
work.
The link to the Youtube Livestream can be found here:
<https://www.youtube.com/watch?v=jNNy8ALGjaE>
https://www.youtube.com/watch?v=Tb_9gOYsWJQ
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
Senior Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org
Hi,
*Crossposting to Wikimedia-L, Wikitech-L, MediaWiki-L, and
Wikitech-Ambassadors. You can reply to the mailing list, but the ideal
place for further discussion is the talk pages of the wiki pages to which I
link below.*
There's a new proposal to localize Lua modules in a more modern, safe, and
convenient manner: https://www.mediawiki.org/wiki/Translatable_modules .
In the foreseeable future it will only affect multilingual sites, such as
Wikidata, Commons, Meta, and mediawiki.org, but at a later time it may also
be deployed on Wikipedias and other projects.
It will be great if experienced module developers could take a look at the
project page, https://www.mediawiki.org/wiki/Translatable_modules , and its
subpages, especially https://www.mediawiki.org/wiki/Translatable
modules/Proposed solutions . Your feedback will be very helpful in
implementing this project in a way that really benefits all the editors.
Thanks!
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Hello,
Recently, I stumbled upon a technical writing course which I found very
useful and I wanted to share it and thought of sending an email to
wikitech-l recommending it. Also, I've been looking for a resource about
VueJS with not much luck and wanted to send an email asking if anyone knows
any.
Instead, I have this idea to have a virtual library for developers so they
can share useful resources with each other. You go to a wiki page and see
list of courses, books, conference videos, on each topic and different
people recommanding them. You can also request a resource for a topic and
people respond to you. If the wiki page grows too big, we can split them to
sub pages based on topics, and so on.
I started the page in https://www.mediawiki.org/wiki/User:Ladsgroup/Library
but I'm planning to move it to the main namespace if no one objects. Please
take a look, add more recommandations, co-sign, request for a resource,
respond to a request for a resource, etc.
What do you think? Please let me know if you think it's a horrible idea or
you have feedback on details (mediawiki.org? maybe we should move it to
wikitech.wikimedia.org?)
Hope that'd be useful.
Best
--
Amir (he/him)
Hello,
The second round of voting for the new logo will start soon. In this round,
we are going to vote on different variants of the top design (Proposal
six). Given that 16 different variants of this logo exist (with different
wordmarks, colors, etc.), we need preferential voting instead of the
classic support/oppose. We will use Schulze method [1] for choosing the
final winner.
I hacked together a simple voting gadget that you can test in
https://www.mediawiki.org/wiki/User:Ladsgroup/Round_2?withJS=MediaWiki:Gadg…
Using that, you just order logos based on how much you like them (with drag
and drop), and then click save. The votes will be saved in another page.
Please test and let me know of any issues by the next couple of days (by
September 25). Any edits on the gadget is also welcome. Please put your
suggestions on its talk page if you don't have rights to edit it.
Of course, voting without the gadget will be also possible, it'll be just
slightly cumbersome.
One known issue so far: The gadget on mobile doesn't work because mobile
browsers don't listen to drag events.
[1] https://en.wikipedia.org/wiki/Schulze_method
Best
--
Amir (he/him)
Hello,
This email contains updates for September 16, 2020. For the HTML version,
see: https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-09-16
<https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-09-09>
Cheers,
Deb
------------------------
*= 2020-09-16 =*
== Callouts ==
* New quarter approaching. Reach out early to SRE if you plan to have
anything deployed in production in the next couple of quarters
== Product ==
=== Abstract Wikipedia ===
* Updates:
** Added label uniqueness editing constraints (thanks to colleagues in CPT
and WMDE)
** Now working on installing initial boot-strap ZType schemata on
installation, and validating edits against them
** Initial work on rich editing front end (in Vue) also proceeds, led by a
volunteer
== Technology ==
=== Search Platform ===
* Updates:
** Wikidata lexeme ttl dumps should be in a "predictable" folder -
https://phabricator.wikimedia.org/T261204
** Missing content in cirrus search dump -
https://phabricator.wikimedia.org/T260986
=== Site Reliability Engineering ===
* Updates:
** Wrapping up OKRs. Reach out early to SRE if you plan to have anything
deployed in production in the next couple of quarters
--
deb tankersley (she/her)
sr program manager, engineering
Wikimedia Foundation
This is the weekly TechCom board review in preparation of our meeting on
Wednesday. If there are additional topics for TechCom to review, please let us
know by replying to this email. However, please keep discussion about individual
RFCs to the Phabricator tickets.
Activity since Monday 2020-09-07 on the following boards:
https://phabricator.wikimedia.org/tag/techcom/https://phabricator.wikimedia.org/tag/techcom-rfc/
IRC meeting request:
* Public discussion TODAY: "PHP microservice for containerized shell execution"
Join us at 21:00 UTC (23:00 CEST, 2pm PDT) in the #wikimedia-office channel
on freenode. <https://phabricator.wikimedia.org/T260330>.
Other RFC activity:
* "Parsoid Extension API": Subbu documented status of outreach with
various stakeholders. <https://phabricator.wikimedia.org/T260714>
--
Daniel Kinzler
Principal Software Engineer, Core Platform
Wikimedia Foundation
The 1.36.0-wmf.9 version of MediaWiki is blocked[0].
The previous train blocker was resolved, and train moved to group1.
The new version is deployed to groups{0,1}[1], but can proceed no
further until these issues are resolved:
* T263034 PHP Notice: Trying to get property 'textContent' of non-object -
https://phabricator.wikimedia.org/T263034
* T263047 Uncaught TypeError: Cannot read property 'node' of undefined -
https://phabricator.wikimedia.org/T263047
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/T257977
[1]. <https://versions.toolforge.org/>
--
WMF release engineering team | he/him or they/them
"Imagine a world in which every single human being can freely share in
the sum of all knowledge."
Hi all!
This is a quick reminder that TechCom is hosting a meeting on IRC about the
following RFC:
"PHP microservice for containerized shell execution"
<https://phabricator.wikimedia.org/T260330>
You can join us at 21:00 UTC (23:00 CEST, 2pm PDT)
in the #wikimedia-office channel on freenode.
Problem
- For security, we need better isolation of external binaries from MediaWiki.
- If we run MediaWiki itself under Kubernetes, the resulting container should be
as small as possible, so it should ideally exclude unnecessary binaries.
- It's difficult to deploy bleeding-edge versions of external binaries when they
necessarily share an OS with MediaWiki.
Proposal
- Have a PHP microservice, accessible via HTTP, which takes POSTed inputs,
writes them to the container's filesystem as temporary files, runs a shell
command, and responds with gathered output files.
Tim has been working on this for a couple of weeks, and has been updating the
task in a steady monologue. Perhaps in the meeting today, we can get more eyes
on the nitty gritty of the proposal.
--
Daniel Kinzler
Principal Software Engineer, Core Platform
Wikimedia Foundation