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 Wikimedia Developer Summit 2018 topics.
Position papers: https://wikifarm.wmflabs.org/devsummit/index.php/Session:2
Note: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018/Evolving_the_MediaWiki_Architecture (copied from https://etherpad.wikimedia.org/p/devsummit18-evolvingmediawikiarchitecture )
Keep in mind:
- Architecture impacts 3rd parties, supporting 3rd parties impacts architecture
- Top-down (vision) vs. bottom-up (issues)
- Scale and sustain vs. evolve and explore
- Session outcomes should inform annual plan as well as movement strategy
- How do we develop a tech strategy of there is no product strategy yet?
- Urgent Focus for Scaling and Sustaining
- Identify risks to and needs for sustaining and scaling our current capabilities (aka services)
- Strategic Direction for Improvement
- Key Questions blocking Development Decisions (decision tree)
- Strategic Direction and Technological Visions (with justification and dependency on key questions)
- Strategic Planning Process
- Define further process and responsibility for decision making for each focus area / key question
- Define convergence points that ensure product and tech strategy match
- Define session scope, clarify desired outcomes, present agenda
- Discuss Focus Areas
- Discuss and Adjust. ''Note that we are not trying to come to a final agreement, we are just prioritizing and assigning responsibilities!''
- For each proposition https://etherpad.wikimedia.org/p/devsummit18-evolvingmediawikiarchitecture
- Decides whether there is (mostly) agreement or disagreement an the proposition(s).
- Decide whether there is more need for discussion on the topic, and how urgent or important that is.
- Identify any open questions that need answering from others, and from who (product, ops, etc)
- Decides who will drive the further discussion/decision process. A four months deadline is suggested.
- Discuss additional strategy questions https://etherpad.wikimedia.org/p/devsummit18-evolvingmediawikiarchitecture. For each question:
- Decide whether it is considered important, blocking tech strategy.
- Discuss who should answer it.
- Decide who will follow up on it.
- Wrap up
- Simplifying the WMF technology stack (position paper by Tim Starling)
- Audiences needs from APIs (Audiences)
- Problem Grouping (Audiences Technology Working Group) (accessible to WMF staff, public access has been requested).
- Related position statements from summit participants
- Urgent Platform Topics (according to Daniel)
- CScott’s 2030 Vision
- Turn MediaWiki Core into a Library (Gergo)
- IRC session log
Topic Leaders (@daniel) , please
- Add more details to this task description,
- Coordinate any pre-event discussions (here, IRC, email, hangout, etc),
- Outline the plan for discussing this topic at the Developer Summit.
- Optionally, include what it will not try to solve.
- Update this task with summaries of any pre-event discussions.
- Include ways for people not attending to be involved in discussions before the summit and afterwards.