Updated URLs, we're in R37
on air stream: http://youtu.be/RcE2kecrsIk Max of 15 users: https://plus.google.com/hangouts/_/hoaevent/AP36tYdub-Rs4mI_4UjTEzTgU7GKBkgj...
On Tue, Jun 23, 2015 at 12:18 PM, Vibha Bamba vbamba@wikimedia.org wrote:
This sounds fairly dev centric with Front end/ UX implications. Will the discussion be fairly technical? Let us know if Design should attend.
Vibha Bamba Senior Designer | WMF Design
On Tue, Jun 23, 2015 at 11:12 AM, Gabriel Wicke gwicke@wikimedia.org wrote:
Reminder: This is today!
When: *Tuesday, June 23rd, 13:00 - 14:30 PT* [3] Where:
https://plus.google.com/hangouts/_/wikimedia.org/contentplatform*
- *room 37* in the office
On Fri, Jun 19, 2015 at 12:00 PM, Gabriel Wicke gwicke@wikimedia.org wrote:
Hi all,
a few of us have recently collected and roughly prioritized some open architectural questions [1]. The area that stood out as needing most urgent attention is adapting our content platform to long-term changes in the way users interact with our site [2]. People are using a wider range of devices, from feature phones to multi-core desktops. Many users are looking for short factoids and definitions, while others prefer to immerse themselves in detailed articles with rich multimedia content.
MediaWiki is currently not very optimized to support such a diverse set of use cases. To address this, we see a need to improve our platform in the following areas:
- Storage: To better separate data from presentation, we need the
ability to store multiple bits of content and metadata associated with each revision. This storage needs to integrate well with edits, history views, and other features, and should be exposed via a high-performance API.
- Change propagation: Edits to small bits of data need to be
reliably and efficiently propagated to all content depending on it. The machinery needed to track dependencies should be easy to use.
- Content composition and caching: Separate data gives us the
freedom to render infoboxes, graphs or multimedia elements dynamically, depending on use case and client. For performance and flexibility, it would be desirable to assemble at least some of these renders as late as possible, at the edge or on the client.
We don't expect to tackle all of this at once, but are starting to look into several areas. If you are interested in helping, then we would like to invite you to join us for a kick-off meeting:
*When: Tuesday, June 23rd, 13:00 - 14:30 PT [3]* *Where: *A *hangout* link will be posted here before the meeting; room 37 in the office.
If you can't attend, then please have a look at our current notes and let us know what you think [2].
Gabriel Wicke, Daniel Kinzler, Brion Vibber, Tim Starling, Roan Kattouw, Ori Livneh
-- Gabriel Wicke Principal Engineer, Wikimedia Foundation
Engineering mailing list Engineering@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering
Engineering mailing list Engineering@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering