This is a working area for Wikimedia-Developer-Summit-2016.
How to we make our software beautiful and joyful to use? How can we allow more fluid collaboration between designers and user interaction experts, and provide for safe experimentation as well as providing a smooth glidepath for successful experiments to graduate to mainstream usage in our deployed software?
Main session: Robertson 1: Monday, 11:30am
General discussion of our 2016 strategy for dealing with our central problem.
The goal of this session will be to capture a document that can be the first wiki draft as a charter for this area.
Summary of the other session priorities
- T111588: RFC: API-driven web front-end (and related T106099). Need to better separate business logic from skin formatting. Motivation: Improved performance for logged-in users and ability to effectively do Edge Side Includes (ESI) embedding for updates to the skin HTML at a global level. Thus skin variants wouldn't linger in varnish.
- T114065: The future of MobileFrontend
Nice to have:
- T114071: Let's discuss the skin creation process. Developers in the community have been repeatedly asking for it. Resolution on T111588 would provide flexibility to consider non-PHP skins. Either way, a possible abstraction layer could be supported in both PHP and Node.
- T112996: A vision for templates / wikitext 2.0. Interesting to raise awareness, but seems too generic at the moment. T114445 is related (also by @cscott) and worth discussing at the summit (also covered by "Content format" working area).
- T112984: Real Time Collaborative Editing. Summit plan sounds good. Medium priority.
- T113004: Make it easy to fork, branch, and merge pages (or more). Brainstorm session about UX solutions. Related to T90948 – alternative diff visualisation.
- T114454: [RFC] Visual Templates: Authoring templates with Visual Editor. Not sure editors want this. Could be interesting for a breakout session though.
Not at summit:
- T120414: RFC: MediaWiki should provide a pluggable registry for editor interfaces. Already on-track with little controversy. If further consensus or guidance is needed, can use the regular RFC process for finalizing it.
- T112991: Semantic image styles / beautiful layout. Not actionable at the moment. If we have progress on a clear proposal, we can bring it back in. @Volker_E to catch up with May (@violetto) and @cscott. The summit would be a good venue for this!
Other working areas (and the meta conversations about the idea of working areas) can/should be found here: T119018: Working groups/areas for macro-organization of RfCs for the summit