Wikimedia Technical Committee/Minutes

This page provides status update for ArchCom-RFCs, with an emphasis on ArchCom team member. As of this writing on 2016-04-29, this update is an experiment discussed weekly ArchCom update discussion on the "ArchCom/Team practices" talk page.

Recent RFC meetings
2016W28: 2016-07-13 (Wednesday)
 * ArchCom Planning meeting: E227
 * Notes: Architecture committee/2016-07-13
 * ArchCom-RFC office hour: E228
 * T589 - image and oldimage tables

Upcoming RFC meetings
2016W29: 2016-07-20 (Wednesday)
 * ArchCom Planning meeting: E234
 * Notes: Architecture committee/2016-07-20
 * ArchCom-RFC office hour: E235
 * Agenda: T126641: [RFC] Devise plan for a cross-wiki watchlist back-end

Entering Final Comment Period

 * None

Recently Approved

 * T137926 - Changed from "Require 'curl' PHP extension for MediaWiki" to "Support running MediaWiki without 'curl' PHP extension"
 * Don't require curl, keeping existing non-curl codepath
 * Add a non-parallel MultiHttpClient fallback
 * Special:Version should let users know if the wiki is running without curl

RFC inbox

 * ArchCom RFC board:

Brion

 * T107595 Multi-content revisions is interesting, needed for various things in multimedia land
 * Brion & Daniel doing a work sprint first week of July -- get the patch in better shape, make sure we have some documentation describing how the content slots work and show some examples of working with them
 * T66214 - predictable thumb URLs
 * Break this out into:
 * Define set of core & extensible media file options for Handler extensions (high prio)
 * Predictable thumb URLs (high prio)
 * Improve InstantCommons perf by reducing need to run thumbnail URL lookups (low prio)
 * Iframe-based rich media embedding for InstantCommons (low prio)
 * plan to write up new RfCs for:
 * In-browser SVG rendering (pick up existing bug & mailing list notes) (high prio)
 * iframe+CSP-isolated JS widgets for rich content (low prio)
 * & extend that to InstantCommons via embedding
 * iframe+CSP-isolated JS gadgets for UI plugins (low prio)
 * Build these out from ideas from hackathon project T131436

Daniel
Wish list:
 * Working on Multi Content Rev Spec with Brion
 * T114640 Improve semantics of Parser::getTargetLanguage
 * T113034 RFC: Overhaul Interwiki map, unify with Sites and WikiMap: checking in with Adam
 * T89733 Expose structured data to search (approved, with Stas driving implementation)

Gabriel

 * Looking into content composition working group, possibly kick-off at Wikimania
 * Discussing Multi Content Rev / RB interaction with Daniel; follow-up at Wikimania

Roan

 * T108655 RFC: Standardise JavaScript interfaces: I need to start the second part, but the recent comments have me confused. I'll need to talk to Timo and figure out what the subject of part two should be.

RobLa

 * Working with DPatrick on Wikimedia Security Team issues in an attempt to be useful there.
 * see https://phabricator.wikimedia.org/Z411 for more
 * Forming ArchCom-affiliated working groups
 * Testing Conpherence use for means of piloting ArchCom working groups (see T123606). Trying to use Z425 as asynchronous ArchCom-RFC triage channel, but not seeing much engagement
 * I'm starting to put my action items from weekly security call in Z411.
 * Things he wants to get around to:
 * Prodding on Programming languages, T136866
 * T112999 Parsoid/MediaWiki DOM spec
 * Update T137946 per E218.
 * T123753 Establish retrospective reports for Security and Performance incidents
 * SVG sanitization strategy? See T138783#2414978

Tim

 * T89331 (Replace Tidy in MW parser with HTML 5 parse/reserialize) - should meet to discuss migration rather than implementation plan
 * T114444 RFC: Introduce notion of DOM scopes in wikitext: Scott has implementation work in progress.

Timo

 * T589 RFC: image and oldimage tables: Last weeks' meeting simplified the problem statement, and clarified which direction we want to go in. Option 1 was rejected. We'll continue to flesh out the details of option 2 (schema migration). Option 3 (Multi-content revisions) was positively received, but will be reevaluated once that system is available in core. The improved schema will solve several problems in the short term and simplify migration to MCR in the future.
 * T111588 RFC: API-driven web front-end: Discussed at Wikimania 2016. Proposing to first build a MVP for a non-MediaWiki use case - meanwhile work continues on a more stateless MediaWiki skin system.
 * T135963 RFC: Implement CSP in MediaWiki: Later stages still under discussion. First stage approved and being implemented by Brian Wolff.

Other

 * ?? reviving the installer ‘beacon’ idea (Tim? Brion?) https://gerrit.wikimedia.org/r/#/c/296699/

No activity in a while (e.g. the last two weeks)

 * TODO: come up with more sustainable way to maintain this section


 * T18691 RFC: Section headings should have a clickable anchor (Timo)
 * T122942 RFC: Support language variants in the RESTBase (Gabriel)
 * T39902 RFC: Implement rendering of redlinks in Parsoid (no shepherd)
 * T18691 RFC: Section headings should have a clickable anchor (Timo)
 * T122825 Service ownership and minimum maintenance requirements (Gabriel)
 * T105766 RFC: Dependency graph storage (Gabriel)
 * T66214 Use content hash based image / thumb URLs & define an official thumb API (Brion)
 * T91162 RFC: Shadow namespaces (Brion)
 * T128351 RFC: Notifications in core (Brion)
 * T122825 Service ownership and minimum maintenance requirements (Gabriel)
 * T54807 Identify and remove legacy preferences from MediaWiki core (no shepherd)
 * T88596 Improving extension management (Daniel)

Useful Phab links

 * Query for shepherd assignments
 * Query for all ArchCom RFCs
 * ArchCom-RfCs board