Wikimedia Developer Summit/2016/T112987
This page is currently a draft.
More information and discussion about changes to this draft may be on the discussion page.
T112987 - This is the session pad for the Separating infoboxes and navboxes from article content session, slated to begin at 3:40pm on Monday, January 4, 2016.
We now have a number of different proposals for revamping navboxes and infoboxes. The goal of this session is to separate out infoboxes and navboxes from article content, and to provide fluent editors for them. This would allow mobile (for example) to more easily tweak the presentation of infoboxes, without having to parse the article content, recognize them, and pull them out. A desirable side-effect is to make it more routine to source data and label texts for infoboxes/navboxes from wikidata, so that they can be shared among wikis in different languages. An extensible design would allow a local wiki to inherit most of an infobox, but still override, delete, or add fields, to empower local editors and account for political sensitivities.
- 20 minutes - introductory presentation
- (User:hoo will also present his work briefly)
- 60 minutes - open discussion
- Starting with 10 minutes for Q&A about the various existing implementations.
Leave with a unified plan for the future of infoboxes and navboxes, including buy-in from wikidata, the mediawiki-core team (for storage separate from article content), mobile (to replace their current display hacks), editing (to create the necessary tools), and analytics (to ensure that infoboxes remain easy to edit, but not significantly easier to vandalize).
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