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:= Keep in mind: =
* Urgent Focus for Scal* Architecture impacts 3rd parties, supporting and Sustaining3rd parties impacts architecture
** Identify risks to and needs for sustaining and scaling our current capabilities (aka services)
* Strategic Direction for Improvement Top-down (vision) vs. bottom-up (issues)
** Key Questions blocking Development Decisions (decision tree)* Scale and sustain vs. evolve and explore
** Strategic Direct* Session and Technological Visions (with justification and dependency on key questions)outcomes should inform annual plan as well as movement strategy
* S* How do we develop a tech strategic Planning Processy of there is no product strategy yet?
= Desired Outcomes: =
** Define further process and responsibility* **Urgent Focus for decision making for each focus area / key questionScaling and Sustaining**
** Define convergence points that ensure product** Identify risks to and needs for sustaining and tech strategy match
Structure (rough draft):scaling our current capabilities (aka services)
* Define session scope, clarify desired outcomes, present agenda* **Strategic Direction for Improvement**
* Urgent Focus for Scaling and Sustaining:** **Key Questions blocking Development Decisions** (decision tree)
** Propose 3 Focus Areas, along ** **Strategic Direction and Technological Visions** (with blockingjustification and dependency on key questions)
** Discuss and Adjust* **Strategic Planning Process**
** Propose** **Define further process and responsibilitiesy for answering the blocdecision making questions and specifying solufor each focus area / key questions**
* Strategic Direction for Improvement** **Define convergence points that ensure product and tech strategy match**
= Session Structure =
** Propose 3 technological visions* **Define session scope, clarify desired outcomes, along with blocking questionspresent agenda**
*** Discuss and AdjustFocus Areas
** Propose process and responsibilities for answering the blocking questions and specifying solutionsDiscuss and Adjust. ''Note that we are not trying to come to a final agreement, we are just prioritizing and assigning responsibilities!''
* Wrap up
Things to discuss on this ticket before the event:** For each proposition <https://etherpad.wikimedia.org/p/devsummit18-evolvingmediawikiarchitecture>
* What planned or anticipated future features or products should be taken into account when discussing the future of our technology stack?** Decides whether there is (mostly) agreement or disagreement an the proposition(s).
* 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)** Decide whether there is more need for discussion on the topic, and how urgent or important that is.
* **[[https://www.mediawiki.org/wiki/Wikimedia_Audiences/Needs_*** Identify any open questions that need answering from_APIs |Audiences needs others, and from APIs]]** (Audienceswho (product, ops, etc)
* The //Goals// and //Questions// tabs on **[[https://docs.google.com/spreadsheets/d/1DDtO5v5GAtNSRiKHyii8Kv-kNsar25Ac5Z0WIrU_Mt4/|Problem Grouping]]** (Audiences Technology Working Group)** Decides who will drive the further discussion/decision process. A four months deadline is suggested.
* **[[https://wikifarm.wmflabs.org/devsummit/index.php/Session:2|Related position statements from summit participants]]**Discuss additional strategy questions <https://etherpad.wikimedia.org/p/devsummit18-evolvingmediawikiarchitecture>. For each question:
* [[https://en.wikipedia.org/wiki/User:Cscott/2030_Vision|CScott’s 2030 Vision ]]** Decide whether it is considered important, blocking tech strategy.
* [[https://www.mediawiki.org/wiki/User:Tgr_(WMF)/Turn_MediaWiki_core_into_an_embeddable_library|Turn MediaWiki Core into a Library]] (Gergo)* Discuss who should answer it.
**Session notes**:** Decide who will follow up on it.
* https://etherpad.wikimedia.org/p/devsummit18-evolvingmediawikiarchitecture
* **Wrap up**
----
**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:
* ...