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

 * ArchCom Planning meeting 2016W22: 2016-06-01: E197 (E156/9)
 * Notes: Architecture committee/2016-06-01
 * ArchCom-RFC office hour 2016W22: 2016-06-01: E198 (E66/37)
 * Security discussion, including:
 * CSP - T135963

Upcoming RFC meetings

 * ArchCom Planning meeting 2016W23: 2016-06-08: E202 (E156/10)
 * Notes: Architecture committee/2016-06-08
 * ArchCom-RFC office hour 2016W23: 2016-06-08: E203 (E66/38)
 * T89331 Replace Tidy in MW parser with HTML 5 parse/reserialize

Entering Final Comment Period

 * None.

Recently Approved

 * none

RFC inbox

 * ArchCom RFC board:
 * T124569 RFC: Data namespace blob storage on wikidata.org

Shepherd status

 * Brion
 * Multi-content revisions (T107595) is interesting
 * Daniel
 * Software Quality working group?
 * Working on Multi Content Rev Spec with Brion
 * T113034 RFC: Overhaul Interwiki map, unify with Sites and WikiMap: checking in with Adam
 * T89733 (approved, with Stas driving implementation)
 * Gabriel
 * Working with BSitzmann on T132597 (no longer an RFC)
 * 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.
 * T123753 Establish retrospective reports for Security and Performance incidents
 * In scope for this group?
 * Forming ArchCom-affiliated working groups
 * RFCs
 * T124504 Transition WikiDev '16 working areas into working groups and
 * T123606 RFC: Implement ArchCom-affiliated working groups (process inspired by Rust's "subteams")
 * Testing Conpherence use for means of piloting ArchCom working groups. Still using Z425 as asynchronous ArchCom-RFC triage channel.  A Security/ArchCom quasi-working group discusses some issues in Z411.  I started renaming "subteams" to "working groups" on Requests for comment/Governance (with Nemo's help).
 * 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: (Update?)
 * Timo
 * Section anchors - will update T18691
 * CSP - T135963 - Will shepherd
 * Local storage abstraction T121646 working with Fundraising on this to move cookies into local storage; not an RFC yet, but may become one.

No activity in the last two weeks

 * 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)
 * T111588 RFC: API-driven web front-end (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