Wikimedia Developer Summit/2016/User interface


T119162 - This is the session pad for the User-interface presentation area session, slated to begin at 11:30am on Monday, January 4.


This area is focused on the following questions: "How to we make our software beautiful and joyful to use? How can we allow more fluid collaboration between designers and user interaction experts? How do we provide for safe experimentation and provide a smooth glidepath for successful experiments to graduate to mainstream usage in our deployed software?"


  • 5-20 minutes - introductory comments
  • 60-75 minutes - open discussion




Let's use this time to discuss the answers to these questions:

  • Do we have the questions right?
  • Who are the stakeholders?
    • E.g.
      • Wikimedia software developers (and enumeration of various categories)
      • Wikimedia editors (with or without elevated privs, experience, etc)
      • Casual users (various categories of language, connectivity, device support)
  • What qualities are important to the stakeholders?
  • Do any of these deserve unconference time? How about time during this session?
    • T114065: The future of MobileFrontend
    • T112996: A vision for templates / wikitext 2.0
    • T112984: Real Time Collaborative Editing
    • T113004: Make it easy to fork, branch, and merge pages (or more)
  • Highlight upcoming session (10:00 AM Tuesday)
    • T114071: Let's discuss the skin creation process. Any prediscussion needed for this?
  • Possible followup from T114542 - Next Generation Content Loading and Routing
    • Related: T111588: [RFC] API-driven web front-end (and related T106099)


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[edit]

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