https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-07-18
= 2018-07-18=
== Callouts ==
* Fundraising campaigns
https://meta.wikimedia.org/wiki/CentralNotice/Calendar
* [Perf] Seeking input on wmf-config variables that appear to be unused,
and which we'd like to remove:
https://wikitech.wikimedia.org/wiki/User:Krinkle/Unused_config
== Audiences ==
=== Readers ===
==== iOS native app ====
(Natalia H)
* Blocked by:
Question for Analytics: can we return an error code if event logging
validation fails? Right now we have to test menually using
https://wikitech.wikimedia.org/wiki/Analytics/Systems/EventLogging/TestingO…
** With the current system, no, because the endpoint you're sending to
is a fire-and-forget Varnish server. This is a good thing to bring up in
the Modern Event Platform Context.
^ thanks, that makes sense 👍 (let me know if you want to brainbounce the
problem that this causes ~~~~ milimetric)
* Blocking:
* Updates:
**User testing of feed redesign and navigation changes in progress (
https://phabricator.wikimedia.org/T198932)
**6.0.0 (
https://phabricator.wikimedia.org/tag/ios-app-v6.0-walrus-on-a-unicycle/)
feature-complete
by the end of this week
**Product at Wikimedia
==== Android native app ====
(Natalia H)
* Blocked by:
* Blocking:
* Updates:
**Finishing up prototypes of navigation updates:
https://phabricator.wikimedia.org/project/view/3367/
**Maintenance release this week to address minor analytics issues and audio
playback. https://phabricator.wikimedia.org/T198504
==== Readers Web ====
(Stephen N)
* Blocked by:
** New service request: chromium-render/deploy
https://phabricator.wikimedia.org/T186748
*** We're not blocked but we're ready to help as needed on:
****
https://gerrit.wikimedia.org/r/#/c/mediawiki/services/chromium-render/+/443…
(+1d but needs review by Petr when available!)
**** https://phabricator.wikimedia.org/T199264 (not sure what the status is)
* Blocking:
* Updates:
** RFC: Add a language agnostic build step to skins/extensions to our
deploy process https://phabricator.wikimedia.org/T199004
** Mobile website (MinervaNeue / MobileFrontend):
*** Page issues UI and instrumentation T191532 T191528 T197932 T197931
T199005
*** Special pages preferences T186760
*** Document existing JavaScript code coverage T197637
*** Other fixes and hygiene T193172 T197133 T198930
** WikidataPageBanner
*** Banners should display the same in RTL or LTR T198818
** PDF rendering (Proton):
*** Font configuration T199264
** Desktop website (Popups):
*** Identify aborted HTTP requests logged T199482
*** Some JSDoc improvements and other fixes T198663
** Wikipedia.org (Portals)
*** Extra spacing on article counts T199337
** Product and design at Wikimania
** Design finishing navigation prototypes for advanced contributors
==== Readers Infrastructure ====
* Blocked by: n/a
* Blocking: n/a
* Updates:
** Working on updating maps dependencies to use a more recent Mapnik
version (https://phabricator.wikimedia.org/T188674)
** Building a Docker Compose setup for maps stack (
https://phabricator.wikimedia.org/T193232)
** content-html endpoint:
*** new name tbd T199491
*** working on splitting up CollapseTable in wikimedia-page-library into
client and server portions
** Working on respecting the accept-language header in MCS (
https://phabricator.wikimedia.org/T197009)
==== Multimedia ====
* Blocked by:
* Blocking:
* Updates:
** Half the team is incommunicado for Wikimania; progress is minimal this
week I think
** Search prototype is progressing
** Designs coming through soon for other work
=== Contributors ===
==== Community Tech ====
* Blocked by:
*Security*: Need security review for TemplateWizard extension
https://phabricator.wikimedia.org/T198666
* Blocking:
* Updates:
** GlobalPreferences API is out on beta. There's a breaking change that
fixes a 'bug' that was introduced with blacklist notifications. Should not
affect anyone.
**
==== Anti-Harassment Tools ====
* Blocked by:
* Blocking:
* Updates:
**
==== Editing ====
* Blocked by:
* Blocking:
** Updates:
**
==== Parsing ====
* Blocked by:
* Blocking:
* Updates:
** Completed migration from Tidy to Remex, no major issues reported
==== Growth ====
* Blocked by:
* Blocking:
* Updates:
**
==== Language ====
* Blocked by: https://phabricator.wikimedia.org/T199011 -> VE:
https://phabricator.wikimedia.org/T196521
* Blocking:
* Updates:
** Progress on 'Progress Calculation' for CX2.
** Some annoying bug fixes for CX1.
** Fixed issues with cxserver and maintainance updates.
=== Audiences Design ===
==== UI Standardization ====
* Blocked by:
* Blocking:
* Updates:
** OOUI v0.27.5 released last week with accessible tabs, and standard
buttons in dialogs. No release this week
** Continuous work on Special:Preferences connected tasks and minor support
for Special:Log to OOUI preparation
** Design Style Guide: Color section/palette visual refresh, mobile
friendly: https://design.wikimedia.org/style-guide/visual-style_colors.html
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
** We had a kafka main outage due to a stale testing environment for rest
base, working with SRE teams to get more kafka expertise in ops teams so
analytics is not the main point of contact of tier-1 service:
https://wikitech.wikimedia.org/wiki/Incident_documentation/20180711-kafka-e…
** New maps on wikistats. See pageviews for portuguese wikipedia around the
world:
https://stats.wikimedia.org/v2/#/pt.wikipedia.org/reading/page-views-by-cou…
|map|2-Year~2016060100~2018071700|~total
** Added Historic data to UI, see legacy pageviews for portuguese
wikipedia:
https://stats.wikimedia.org/v2/#/pt.wikipedia.org/reading/legacy-page-views…
|bar|All~1980010100~2018071700|~total
** More friendly configuration on turnilo to explore datasets with numeric
dimensions, this will help SRE and perf team troubleshoot issues with
near-realtime data. See request-size for example:
https://turnilo.wikimedia.org/#webrequest_sampled_128
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
**
=== Fundraising Tech ===
* Blocked by:
* Blocking:
* Updates:
** Thanks to the core team for fixing the bug blocking CentralNotice
translatable message saves!
** More public testing of new API for main CC processor
** More work on email opt-in checkbox for selected countries
** More work on donor data export and expurgation
** More work on new data pipeline for banner and landing page views
** Working on support for es-419 (LatAm Spanish) in donation pipeline
=== MediaWiki Core Platform ===
* Blocked by:
* Blocking:
* Updates:
**
=== Performance ===
(Ian M)
* Blocked by:
**SRE - Waiting on several puppet reviews/merges related to the webperf
profile/roles
* Blocking:
** None
* Updates:
**Mcrouter writes config broke things when we deployed it last week,
resulting in a partial outage. Rolled back, and have since fixed that
issue, but have not scheduled the rollout of the fix. Incident report at
https://wikitech.wikimedia.org/wiki/Incident_documentation/20180710-MediaWi…
** Also found an issue with mcrouter not properly supporting Unicode keys.
Wrote a patch to address that which has landed on master, and has been
backported.
** fixed a few different unit tests that were sporadically failing
** Seeking input on wmf-config variables that appear to be unused, and
which we'd like to remove:
https://wikitech.wikimedia.org/wiki/User:Krinkle/Unused_config
=== Release Engineering ===
(Hashar)
* Blocked by:
* Blocking:
** webpack for extensions https://phabricator.wikimedia.org/T199004
** ORES CI patches fail https://phabricator.wikimedia.org/T198201
* Updates:
** {done} Mobile CI job to Docker:
https://gerrit.wikimedia.org/r/#/c/integration/config/+/442126/
** Flappy tests blocking PageTriage changes
https://phabricator.wikimedia.org/T198137
*** worked around by disabling a test on Friday 07/13
https://gerrit.wikimedia.org/r/445394
*** Test suite ongoing improvement to properly fix the underlying issue
** CI Jenkins to be upgraded to latest LTS
** Various wikimedia deployed extensions fail tests in CI. Antoine will
reach out to teams. (parent task https://phabricator.wikimedia.org/T183512 )
*** Eg: ArticlePlaceholder , Cognate, intersection,
LabeledSectionTransclusion, TrustedXFF, WikibaseLexeme
=== Research ===
* Blocked by: none
* Blocking: none
* Updates:
** Wikimania
** Analyzed the inital set of CitationUsage data. Making adjustments to the
code to collect more data.
** Working on re-running the UnsourcedStatements WikiLabels campaign.
=== Scoring Platform ===
* Blocked by:
** JADE storage discussion continues, latest twist is that we should go
back to TechCom.
* Blocking:
* Updates:
** wp10 storage enabled in euwiki
** Migrating to new library for abstraction of wikibase entities in ores is
going on (from pywikibase to mwbase)
=== Search Platform ===
* Blocked by:
* Blocking:
* Updates:
**
=== Security ===
* Blocked by:
* Blocking:
* Updates:
**
=== Services ===
* Blocked by:
* Blocking:
* Updates:
**
=== Site Reliability Engineering ===
* Blocked by:
* Blocking:
* Updates:
**
== Wikidata ==
* Blocked by:
* Blocking:
* Updates:
**
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
**
== Multi-Content Revisions ==
* Blocked by:
* Blocking:
* Updates:
**
== SoS Meeting Bookkeeping ==
* Updates:
**Would it help to schedule this meeting earlier in the day?
***Participants of the meeting said yes
***Proposal to experiment with holding meeting 2 hours earlier
Dear All,
back in June the Wikimedia Technical Committee (TechCom) began a process to
recruit two new members to broaden the committee’s area of expertise[1]. After
some deliberation, we have now concluded our process and would like to welcome
Niklas Laxström and Dan Andreescu to TechCom. Congratulations, we are looking
forward to you bringing your expertise to the committee!
For those who wonder what this is about: TechCom is the guardian of the
integrity, consistency, stability, and performance of all software supporting
the Wikimedia projects. It acts as the senior advisor and the convergence point
of all decisions related to technical work that is strategic, cross-cutting,
and/or hard to undo. You can find more information in the TechCom Charter[2].
To those who applied or were nominated, but were not selected, I want to say:
thank you for offering your time and brain power! It was a difficult decision to
make. We evaluated all candidates based on the following criteria:
- Activity on RFCs and other Phabricator tickets
- Area(s) of expertise
- Having a unique engineering perspective
- Experience working in and with the Wikimedia movement and community
It was a challenge to balance these criteria, especially with candidates who
have a lot of experience, but whose expertise and perspective is similar to that
of existing members. In such cases, we aimed to improve the diversity of
perspective and knowledge on the committee by picking candidates that would help
us cover any blind spots.
We plan to do another round of nominations again soon, and hope to have
continued interested from others in joining TechCom.
Thank you all,
[1] https://lists.wikimedia.org/pipermail/wikitech-l/2018-June/090068.html
[2] https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Charter
Hi!
Striving for operational excellence, here's a summary of recent issues in
production that can currently affect end-users.
## Statistics
* 124 fatals. (channel=fatal)
* 3,986 exceptions. (channel=exception)
* 34,559 PHP errors. (channel=error)
* 42,222 errors in total. (channel=*, level=ERROR)
>From logstash.wikimedia.org, last 7 days, having type=mediawiki.
## Higher impact
These caused users (of web or api) to see errors. From
logstash.wikimedia.org, ordered by frequency:
* [Babel extension] https://phabricator.wikimedia.org/T199941 - MWException
"Language::isValidBuiltInCode must be passed a string".
* [Flow extension] https://phabricator.wikimedia.org/T70526 -
InvalidDataException "Flow workflow is for different page".
* [Page deletion] https://phabricator.wikimedia.org/T195692 - Undelete for
certain pages aborted by IncompleteRevisionException.
* [Special pages] https://phabricator.wikimedia.org/T199044 -
Special:ActiveUsers aborted by DBQueryTimeoutError.
* [MobileFrontend] https://phabricator.wikimedia.org/T199066 -
Special:MobileContributions shows "Special:Badtitle" (Revision::ensureTitle
error).
* [AbuseFilter extension] https://phabricator.wikimedia.org/T187153 -
Special:Abuselog throws BadMethodCallException on details/examine.
## Noise
These are caused by code not behaving unexpectedly, but with limited impact
due to graceful recovery by PHP or other code. These harm our ability to
detect and prevent higher impact issues (through in Scap).
They may also be symptoms of deeper issues.
* [CirrusSearch extension] https://phabricator.wikimedia.org/T180807 -
Undefined index: _score and _id in CompSuggestQueryBuilder.
* [Collection extension] https://phabricator.wikimedia.org/T189636 -
Undefined 'subtitle' and 'title' indexes in CollectionPageTemplate.
* [WMF-JobQueue] https://phabricator.wikimedia.org/T199594 - Exception "Job
queue is read-only".
* [CentralAuth extension] https://phabricator.wikimedia.org/T170971 - iconv
Detected an illegal character.
* [Cite extension] https://phabricator.wikimedia.org/T182929 - Undefined
index: "" in Cite.php.
## Thank you
Thanks to the following people who recently helped investigate and/or
resolve similar issues.
* Jdforrester (James Forrester)
* Marostegui (Manuel Aróstegui)
* jcrespo (Jaime Crespo)
* SBisson (Stephane Bisson)
* Tpt (Tpt)
* Anomie (Brad Jorsch)
* Joe (Giuseppe Lavagetto)
* Legoktm (Kunal Mehta)
* Aaron (Aaron Schulz)
* mobrovac (Marko Obrovac)
And everyone else I forgot to mention, thank you!
-- Timo
Hello and thank you. Does it mean I can add some code to my user common.js,
so that VE will work in edit window on all namespaces?
Igal (User:IKhitron)
On Jul 18, 2018 03:29, "Yaron Koren" <yaron(a)wikiworks.com> wrote:
Hi everyone,
I'm very excited to announce the release of a new MediaWiki extension:
VEForAll. Its name stands for "VisualEditor For All", and it provides
something that some people have been asking about for a long time - a way
to incorporate the VisualEditor interface into textarea inputs other than
the one in the standard VisualEditor tab.
The VEForAll extension works by providing a JavaScript function that, when
called on a textarea input, adds the VisualEditor interface to it (if the
VisualEditor extension is already installed). So the extension itself
doesn't actually do anything - instead, it provides an API for other
extensions to use. At the moment, two extensions can already make use of
VEForAll if it's there: CommentStreams and Page Forms. (You need to use the
latest version of either extension to get it working.)
You can read more about VEForAll, and download it, here:
https://www.mediawiki.org/wiki/Extension:VEForAll
This extension has five credited authors, although most of the credit goes
to the first two: Pierre Boutet and Clément Flipo of the consulting company
Dokit, and the site Wikifab. I feel like I should give both the company and
site a plug, in their honor:
http://www.dokit.io/en/about-ushttps://wikifab.org/wiki/Accueil
Please feel free to try out the extension, and let us know on the talk page
if you run into any problems.
-Yaron
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
As part of work on T198935[1], the representation of preferences
`email-blacklist` and `echo-notifications-blacklist` returned by API
meta=userinfo has changed. Previously, they were by mistake returned as
arrays, which is unheard of in the API and resulted in weird output,
especially in XML:
<email-blacklist>
<_v>123</_v>
<_v>456</_v>
</email-blacklist>
At the same time, to change these preferences, you still had to use the
same format as DB storage, strings with newline-separated numbers. To
address this as well as a few other problems with conversion of preferences
on the storage-HtmlForm boundary, a fix[2] has been implemented that turned
these preferences newline-separated strings everywhere.
This fix will be deployed to WMF production next week. According to our API
usage analysis, there are unlikely any users this might affect, however
still please make sure you're ready.
----
[1] https://phabricator.wikimedia.org/T198935
[2] https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/444273/
--
Best regards,
Max Semenik ([[User:MaxSem]])
Hi All,
A friendly reminder that TechCom is hosting a Public IRC Discussion on
Unify various deletion systems <https://phabricator.wikimedia.org/T20493>
Currently there are two systems for deletion of revisions: Page deletion
and Revision delete. This RFC proposes to unify these methods. Currently
the proposal is exploring to see if we can re-implement the logic behind
"Page deletion" by using the same code and database logic that is used
by "Revision delete".
If this topic is of interest to you join us on 2018-07-18 in the
#wikimedia-office channel at 2pm PST(22:00 UTC, 23:00 CET) you can find
more information on how to connect and participate here:
<https://meta.wikimedia.org/wiki/IRC_office_hours#How_to_participate>
If you are not familiar with the overall TechCom RFC process there is
info here: <https://www.mediawiki.org/wiki/Requests_for_comment/Process>
Thanks,
Kate
--
Kate Chapman TechCom Facilitator (Contractor)
Hey all,
a quick reminder: The deadline for nominations for the Wikimedia Technical
Conference (Portland, USA, October 22-25, 2018) is tomorrow, *Thursday June
14, 2018. *So if you are a volunteer (or staff member) and think you (or
the person you nominate) might be able to provide valuable feedback for the
program, please use this form: https://goo.gl/forms/MKF682BE1OVI0pe63 to
nominate yourself or someone else.
You can find more information on the nomination process in the FAQ:
https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2018/FAQ
If you haven't heard about the conference at all by now, please see:
https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2018 for more
information.
Questions are very welcome on the talk page there:
https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018
Thanks to everyone who already has taken the time to nominate someone -
your support is much appreciated :-)
The Wikimedia Technical Conference Team
2018-06-02 1:36 GMT+02:00 Rachel Farrand <rfarrand(a)wikimedia.org>:
> Hello!
>
> As per the email below we are now opening up the nomination process for the
> Wikimedia Technical Conference (WMTechConf), to be held in Portland, OR,
> USA on October 22-25, 2018.
>
> *Please fill out the survey using this link to nominate yourself or someone
> else to attend: *https://goo.gl/forms/MKF682BE1OVI0pe63 This nomination
> form will remain open between June 1 and June 14, 2018.
>
> This survey is conducted via a third-party service, which may make it
> subject to additional terms. For more information on privacy and
> data-handling, see this survey privacy statement: https://
> wikimediafoundation.org/wiki/Wikimedia_Technical_
> Conference_Survey_Privacy_
> Statement
>
> *If you have any questions, please post them on the event's talk page
> <https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018>.
> *
> Thanks!
>
> The Wikimedia Technical Conference Team
>
>
> On Mon, May 21, 2018 at 3:47 PM, Deborah Tankersley <
> dtankersley(a)wikimedia.org> wrote:
>
> > *Hello,We recently announced the new Wikimedia Technical Conference
> > (TechConf) during the closing session of the Barcelona Hackathon on May
> 20,
> > 2018. We are sending this email to give an update on the planning and
> > organization, and to also let everyone know how the nomination process
> will
> > work for those interested in attending. The Wikimedia Technical
> Conference
> > will take place in Portland, OR, USA on October 22-25, 2018. And, as
> > mentioned in previous emails [1][2] and on the wiki page [3], this
> > conference will be focused on the cross-departmental program called
> > Platform Evolution. We will be providing more information and context as
> we
> > go along in the process.For this conference, we are looking for diverse
> > stakeholders, perspectives, and experiences that will help us to make
> > informed decisions for the future evolution of the platform. We need
> people
> > who can create and architect solutions, as well as those who actually
> make
> > decisions on funding and prioritization for the projects.Later this week,
> > we will send out a form to provide more detailed information on the
> > nomination process and how to nominate people (or it can be yourself) to
> > attend this conference, along with the skills, experiences, and/or
> > backgrounds that we are looking for. Due to the time needed for visa
> > application and other constraints, the deadline for nominations will be
> > June 8th. Please make sure that you don’t miss the deadline!If you have
> any
> > questions, please post them on the talk page [4][1]
> > https://lists.wikimedia.org/pipermail/mediawiki-l/2018-April/047367.html
> > <https://lists.wikimedia.org/pipermail/mediawiki-l/2018-
> April/047367.html>
> > [2] https://lists.wikimedia.org/pipermail/wikitech-l/2018-
> > April/089738.html
> > <https://lists.wikimedia.org/pipermail/wikitech-l/2018-April/089738.html
> >
> > [3] https://mediawiki.org/wiki/Wikimedia_Technical_Conference/2018
> > <https://mediawiki.org/wiki/Wikimedia_Technical_Conference/2018> [4]
> > https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018
> > <https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018
> >
> > *
> >
> > *Cheers from the Program Committee:*
> > *Kate, Corey, Joaquin, Greg, Birgit and TheDJ*
> >
> > --
> >
> > deb tankersley
> >
> > Program Manager, Engineering
> >
> > Wikimedia Foundation
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
>
> --
> Rachel Farrand
> Events Program Manager
> Technical Collaboration Team
> Wikimedia Foundation
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Birgit Müller
Community Communications Manager
Software Development and Engineering
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.
Hi. Is there a way to get caterization edits data from more than month ago?
I found the last month in recentchanges SQL table, but that's all. I need
to find pages that were added by specific user to specific category,
doesn't matter when. Thank you.
Igal (User:IKhitron)
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
This time with a Wikimedia Special[1] in English and German!
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)
[1]: https://phabricator.wikimedia.org/T199093
--
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.
Hi All,
Here are the minutes from this week's TechCom meeting:
* IRC Meeting postponed until next week on 2018-07-18 in the
#wikimedia-office channel at 2pm PST(22:00 UTC, 23:00 CET): Unify
various deletion systems <https://phabricator.wikimedia.org/T20493>
Currently there are two systems for deletion of revisions Page deletion
and Revision delete. The current proposal would like to explore
implementing the logic behind “Page deletion” by using the same code and
database logic that is used by “Revision delete”.
* Finalized selection of new committee members (public announcement
coming soon)
* IRC Meeting scheduled for 2018-08-01 in the #wikimedia-office channel
at 2pm PST(22:00 UTC, 23:00 CET) RFC: Modern Event Platform - Choose
Schema Tech <https://phabricator.wikimedia.org/T198256> This RFC is
looking at if Apache Arvo or JSONSchema should be used for the event
schema and serialization method.
You can also find our meeting minutes at
<https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes>
See also the TechCom RFC board
<https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>.
If you prefer you can subscribe to our newsletter here:
<https://www.mediawiki.org/wiki/Newsletter:TechCom_Radar>
Thanks,
Kate
--
Kate Chapman TechCom Facilitator (Contractor)