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
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
 * Need to follow up on work sprint from earlier in July (got backlogged by sick pet). Patch is in better shape, needs updated docs & clearer presentation.
 * 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
 * BlobStore proposal on Gerrit: https://gerrit.wikimedia.org/r/#/c/299020/
 * Working on a proof-of-concept for the new DB layout, for Jaime to play with.
 * 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

 * Forming ArchCom-affiliated working groups (T123606)
 * Working with DPatrick on Wikimedia Security Team issues (Z411)
 * Public Conpherence activity logging continues on Z425
 * T123753 Establish retrospective reports for Security and Performance incidents
 * Greg is proposing some new Phab conventions for incidents in T141287 and T140207; see comments of T123753 starting July 25 for summary of activity related to this RFC
 * Backburner:
 * Alignment on Programming languages on Wikimedia cluster following inventory of current state (T136866)
 * T112999 (CScott's proposal for running MediaWiki without Wikitext) and making Parsoid/MediaWiki DOM spec easier to find/understand
 * T137946(Markdown support strategy for MediaWiki) followups from June 22 discussion (E218)
 * Figure out SVG sanitization strategy in wake of June conversation about intranet SVG use (T138783)

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: Problem statement and direction have been clarified. We're focussing on option 2 (major schema changes). Tim Starling and Jaime Crespo have formed some initial ideas about the schema migration (see RFC page on mediawiki.org). In the coming weeks we'll finalise the plan on Phabricator, after which we'll have another meeting to seek consensus.
 * T111588 RFC: API-driven web front-end: Initial work has begun on a minimal prototype for a non-MediaWiki use case (writing isomorphic JavaScript that does stream-based composition). Gabriel and I will be consolidating some existing proposals on Phabricator and identify what (minimal) changes may be required on the MediaWiki side .

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


 * T135963 RFC: Implement CSP in MediaWiki (Timo)
 * 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