Wikimedia Developer Summit/2016/T114019

T114019 - This is the session pad for Dumps 2.0 for realz (planning/architecture), slated to begin at 11:30am on January 5



Make headway on the question: "what should the xml/sql/other dumps infrastructure look like in order to meet current/future user needs, and how can we get there?"


  • 10 minutes - introductory presentation
  • things we dump, how we dump them, known user complaints, 1 minute of known maintainer complaints (since I'm doing the session!)
  • 70 minutes - open discussion
  • use cases for the dumps, known and desired
  • where we currently fall short or are expected to fall short in the future
  • an ideal architecture for dumps that would address the main issues would look like... what?
  • example: if we want to run true incremental dumps rather than dumping the entire history of page content, asking MW only for changes, what would we need from MW core and what tools would we need to present to the user to update a previous dump based on the incremental data)?



Wiki page


Wikimedia Developer Summit 2016/T114019/Minutes



Moved to Wiki (was



Please prepopulate this section with the goals of the meeting, and anticipate that collaborative editing around fulfillment of goals. This is a great place to capture action items from the conversation.



This section is where an attempt is made to capture the gist of who said what, in what order. A transcript isn't necessary, but it's useful to capture the important points made by speakers as they happen.

Session guidelines


This checklist exists to help each session at WikiDev meet the following goals:

  • Have productive discussion about topics that need face-to-face time
  • Make progress towards agreement on a solution
  • Document what was discussed, including areas of agreement and disagreement
  • Create written list of action items for follow up
  • Update or create Phabricator tasks as appropriate

Specific tasks:

  1. Assign meeting roles:
    • Facilitator
    • Gatekeeper
    • Scribe
    • Timekeeper
  2. Facilitator: run session to achieve specific goals.
    • State or build consensus towards meeting goal and style, referencing one of these meeting types:
      • Problem-solving: surveying many possible solutions
      • Strawman: exploring one specific solution
      • Field narrowing: narrowing down choices of solution
      • Consensus: coming to agreement on one solution
      • Education: teaching people about an agreed solution
    • Identify agenda items and guide discussion to stay on topic
    • Redirect participants who begin venting or discussing things that can be done online
  3. Scribe(s): Document the session
  4. Gatekeeper: Actively manage participation
    • Interrupt people if they are dominating the discussion
    • Help people who are having difficulty being heard
    • If the gatekeeper is talking too much, someone else should interrupt them
  5. Timekeeper: Keep track of time left and point out time passing to facilitator
    • If possible, estimate time for each topic written by scribes
    • Let people know when a topic has gone over its time
    • Give a warning when 5-10 minutes are left