TechCom board review 2020-09-07

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

TechCom board review 2020-09-07

Niklas Laxström
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-08-31 on the following boards:

https://phabricator.wikimedia.org/tag/techcom/
https://phabricator.wikimedia.org/tag/techcom-rfc/

Committee inbox:
* RFC: Parsoid Extension API <https://phabricator.wikimedia.org/T260714>
 - see TechCom weekly digest 2020-09-02

Committee board activity: none
New RFCs: none
Phase progression: none
IRC meeting request: none

Other RFC activity:
* MediaWiki's anonymous edit token leaves wiki installations (incl.
Wikipedia) open to mass anonymous spam we can't block
<https://phabricator.wikimedia.org/T40417>
 - dbarratt suggests to block anonymous POST requests with the Origin
header that contains a value that is not in the allowlist.
 - Bawolff thinks it could work if done correctly.

  - Niklas

_______________________________________________
Wikitech-l mailing list
[hidden email]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Reply | Threaded
Open this post in threaded view
|

Re: TechCom board review 2020-09-07

Krinkle
The minutes from TechCom's triage meeting on 2020-09-09.

Present: Daniel K, Dan A, Tim S, Timo T, Kate C.

== Liberate the @ for AtEase ==
* https://phabricator.wikimedia.org/T253461
* Checking in about next steps.
* As a coding convention, it doesn’t need our involvement unless there’s a
conflict, strategic impact, etc. Talk page?
* TT: Will reach out on the talk page as well.

== RFC: Parsoid Extension API ==
* https://phabricator.wikimedia.org/T260714
* TT: Concerning that the RFC was filed this late, but are not meaningful
comments and thinking about last call. Believe this is more perception than
an actual problem. The engagement hasn’t been captured on the task very
well. This is an initial attempt to be used for WMF maintained extensions
when get closer to this parser as the default will be more changes.
Different from usual processes, how do we accommodate that?
* DK: Establish a baseline, then will file another RFC later. Need to
clearly mark as unstable.

== RFC: PHP microservice for containerized shell execution ==
* https://phabricator.wikimedia.org/T260330
* Scheduled as IRC meeting for next week.

== Next week IRC office hours ==
RFC review meeting scheduled for next week: RFC: Containerized shell
execution service https://phabricator.wikimedia.org/T260330.
Meeting at 2020-09-10 21:00 UTC (14:00 PT, 23:00 CEST) on Freenode in the
#wikimedia-office channel.

You can also find our meeting minutes at
<https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes>

If you prefer you can subscribe to our newsletter here
<https://www.mediawiki.org/wiki/Newsletter:TechCom_Radar>

-- Timo
_______________________________________________
Wikitech-l mailing list
[hidden email]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l