Wikimedia Developer Summit/2016/T112991
This page is currently a draft.
More information and discussion about changes to this draft may be on the discussion page.
Mediawiki is lacking tools to generate truly beautiful layouts across a range of devices. As a result, our articles look so-so on the web (but we are continually challenged to do better) and often broken on mobile and print (although we make heroic efforts to workaround our limitations).
This topic at the developer summit would include features which attempt to provide better tools for describing the way images are laid out in our articles, but hopefully we could expand the scope to include design input: what would a truly beautiful presentation on web/mobile/print/etc look like? What are the features we're missing to enable that?
- Collect a portfolio of media usage, to inform the scope of the work.
- Create an aspirational "design for mediawiki", which can inform specific implementation work to enable it.
- Identify specific focus tasks for the coming year, for example support for cropping, or for bounding boxes, or for semantic style tagging.
- 20 minutes: session introduction (may, cscott)
- 60 minutes: discussion
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.
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
- Assign meeting roles:
- 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
- Scribe(s): Document the session
- Copy https://etherpad.wikimedia.org/p/WikiDev16-YourSession to https://etherpad.wikimedia.org/p/WikiDev16-[SESSION NAME]
- Fill out the information in the template, including
- Link to Phabricator task describing session
- Goal as described by facilitator
- Topics of discussion as laid out by facilitator
- Action items and who is responsible for them
- Create new Phabricator tasks as needed
- At end of session, copy meeting notes into Phabricator as appropriate
- 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
- 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