Change Details

This session is about evolving the system that allows us store and deliver our content. It's about the architecture of not just MediaWiki core, but also extensions, APIs, underlying services (like databases and job queues) as well as public services, such as RESTbase and the Wikidata Query Service. This is one of the 8 [[https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018 |Wikimedia Developer Summit 2018]] topics. Goals: * Identify risks to and needs for sustaining and scaling our current capabilities (aka services) * Identify opportunities, requirements and costs for supporting (anticipated or planned) future capabilities * Identify key questions that need to be answered in order to develop a strategy for evolving the MediaWiki architecture. Such answered should come from the product strategy process in the course of the year. * see also [[https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018/Purpose_and_Results|DevSummit purpose and results]] for guidance Structure (rough draft): * Discuss overall scope * Identify unanswered questions that block technical decision making. Make educated guesses as what the answers could be. (collect and cluster, be brief) * Identify planned or anticipated future features and products that we will have to support with tech in the future. (collect and cluster, be brief) * Identify key risks to sustaining and scaling current operations, including resource drains (collect and cluster) * Propose ways to support future needs; concrete solution, technologies to explore, etc (collect and cluster) * The session will NOT be used to discuss any of the topics in-depth. Concrete engineering questions are not in scope. Things to discuss on this ticket before the event: * What planned or anticipated future features or products should be taken into account when discussing the future of our technology stack? * Which important questions that impact the technology strategy are unanswered to date? Background reading: * **[[https://www.mediawiki.org/wiki/MediaWiki_Platform_team/Simplifying_the_Wikimedia_Foundation_technology_stack|Simplifying the WMF technology stack]]** (position paper by Tim Starling) * **[[https://www.mediawiki.org/wiki/Wikimedia_Audiences/Needs_from_APIs |Audiences needs from APIs]]** (Audiences Technical Working Group) * **[[https://docs.google.com/spreadsheets/d/1DDtO5v5GAtNSRiKHyii8Kv-kNsar25Ac5Z0WIrU_Mt4/|Problem Grouping]]** (Audiences Technical Working Group) (accessible to WMF staff, public access has been requested). * **[[https://wikifarm.wmflabs.org/devsummit/index.php/Session:2|Related position statements from summit participants]]** ---- **Topic Leaders** (@daniel) , please [x] Add more details to this task description, [x] Coordinate any pre-event discussions (here, IRC, email, hangout, etc), [x] Outline the plan for discussing this topic at the Developer Summit. [x] Optionally, include what it will //not// try to solve. [] Update this task with summaries of any pre-event discussions. [x] Include ways for people not attending to be involved in discussions before the summit and afterwards. ---- Post-event Summary: * ... Action items: * ...

This session is about evolving the system that allows us store and deliver our content. It's about the architecture of not just MediaWiki core, but also extensions, APIs, underlying services (like databases and job queues) as well as public services, such as RESTbase and the Wikidata Query Service. This is one of the 8 [[https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018 |Wikimedia Developer Summit 2018]] topics. Goals: * Identify risks to and needs for sustaining and scaling our current capabilities (aka services) * Identify opportunities, requirements and costs for supporting (anticipated or planned) future capabilities * Identify key questions that need to be answered in order to develop a strategy for evolving the MediaWiki architecture. Such answered should come from the product strategy process in the course of the year. * see also [[https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018/Purpose_and_Results|DevSummit purpose and results]] for guidance Structure (rough draft): * Discuss overall scope * Identify unanswered questions that block technical decision making. Make educated guesses as what the answers could be. (collect and cluster, be brief) * Identify planned or anticipated future features and products that we will have to support with tech in the future. (collect and cluster, be brief) * Identify key risks to sustaining and scaling current operations, including resource drains (collect and cluster) * Propose ways to support future needs; concrete solution, technologies to explore, etc (collect and cluster) * The session will NOT be used to discuss any of the topics in-depth. Concrete engineering questions are not in scope. Things to discuss on this ticket before the event: * What planned or anticipated future features or products should be taken into account when discussing the future of our technology stack? * Which important questions that impact the technology strategy are unanswered to date? Background reading: * **[[https://www.mediawiki.org/wiki/MediaWiki_Platform_team/Simplifying_the_Wikimedia_Foundation_technology_stack|Simplifying the WMF technology stack]]** (position paper by Tim Starling) * **[[https://www.mediawiki.org/wiki/Wikimedia_Audiences/Needs_from_APIs |Audiences needs from APIs]]** (Audiences) * **[[https://docs.google.com/spreadsheets/d/1DDtO5v5GAtNSRiKHyii8Kv-kNsar25Ac5Z0WIrU_Mt4/|Problem Grouping]]** (Audiences Technical Working Group) (accessible to WMF staff, public access has been requested). * **[[https://wikifarm.wmflabs.org/devsummit/index.php/Session:2|Related position statements from summit participants]]** ---- **Topic Leaders** (@daniel) , please [x] Add more details to this task description, [x] Coordinate any pre-event discussions (here, IRC, email, hangout, etc), [x] Outline the plan for discussing this topic at the Developer Summit. [x] Optionally, include what it will //not// try to solve. [] Update this task with summaries of any pre-event discussions. [x] Include ways for people not attending to be involved in discussions before the summit and afterwards. ---- Post-event Summary: * ... Action items: * ...

This session is about evolving the system that allows us store and deliver our content. It's about the architecture of not just MediaWiki core, but also extensions, APIs, underlying services (like databases and job queues) as well as public services, such as RESTbase and the Wikidata Query Service. This is one of the 8 [[https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018 |Wikimedia Developer Summit 2018]] topics. Goals: * Identify risks to and needs for sustaining and scaling our current capabilities (aka services) * Identify opportunities, requirements and costs for supporting (anticipated or planned) future capabilities * Identify key questions that need to be answered in order to develop a strategy for evolving the MediaWiki architecture. Such answered should come from the product strategy process in the course of the year. * see also [[https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018/Purpose_and_Results|DevSummit purpose and results]] for guidance Structure (rough draft): * Discuss overall scope * Identify unanswered questions that block technical decision making. Make educated guesses as what the answers could be. (collect and cluster, be brief) * Identify planned or anticipated future features and products that we will have to support with tech in the future. (collect and cluster, be brief) * Identify key risks to sustaining and scaling current operations, including resource drains (collect and cluster) * Propose ways to support future needs; concrete solution, technologies to explore, etc (collect and cluster) * The session will NOT be used to discuss any of the topics in-depth. Concrete engineering questions are not in scope. Things to discuss on this ticket before the event: * What planned or anticipated future features or products should be taken into account when discussing the future of our technology stack? * Which important questions that impact the technology strategy are unanswered to date? Background reading: * **[[https://www.mediawiki.org/wiki/MediaWiki_Platform_team/Simplifying_the_Wikimedia_Foundation_technology_stack|Simplifying the WMF technology stack]]** (position paper by Tim Starling) * **[[https://www.mediawiki.org/wiki/Wikimedia_Audiences/Needs_from_APIs |Audiences needs from APIs]]** (Audiences Technical Working Group) * **[[https://docs.google.com/spreadsheets/d/1DDtO5v5GAtNSRiKHyii8Kv-kNsar25Ac5Z0WIrU_Mt4/|Problem Grouping]]** (Audiences Technical Working Group) (accessible to WMF staff, public access has been requested). * **[[https://wikifarm.wmflabs.org/devsummit/index.php/Session:2|Related position statements from summit participants]]** ---- **Topic Leaders** (@daniel) , please [x] Add more details to this task description, [x] Coordinate any pre-event discussions (here, IRC, email, hangout, etc), [x] Outline the plan for discussing this topic at the Developer Summit. [x] Optionally, include what it will //not// try to solve. [] Update this task with summaries of any pre-event discussions. [x] Include ways for people not attending to be involved in discussions before the summit and afterwards. ---- Post-event Summary: * ... Action items: * ...