Structured Discussions/Project information/status

Last update on: 2014-08-monthly

2012-04-01
Brandon Harris and Andrew Garrett are doing an assessment of experiences learned in LiquidThreads 3.0.

2012-07-01
Official start date of Flow (messaging pages).

2012-07-monthly
Infrastructural work for Flow only until January 2013. Work there can be found in the Database_sharding page. Unrelated but there is an active discussion concerning the differences between Flow and LiquidThreads.

2012-08-monthly
Work on Flow will officially start in January. In the meantime, preparatory work will focus on Database sharding.

2012-09-monthly
Development work for Messaging on MediaWiki (code-named 'Flow') will start officially in January 2013 (after Echo first deployment). This new user-to-user messaging infrastructure tool will be developed by Wikimedia's editor engagement team, including Fabrice Florin, Vibha Bamba, Ryan Kaldari, Benny Situ, Matthias Mullie, Brandon Harris, Oliver Keyes, Howie Fung and Terry Chay. In the meantime, Performance engineering + Matthias Mullie are doing the underlying prep work with the RDB store (database sharding) on AFTv5 (and proper abstraction).

2012-11-monthly
The official start of Flow will follow Echo development. An initial team will be forming next month to explore solutions here.

2013-01-monthly
Flow entered the product design phase in early January. OPW intern Kim Schoonover began user research regarding how user-to-user talk pages are handled, and collected data about the difficulties that new (and existing) users have when using them. Engineering discussions started about potential back-end and scaling difficulties, the possible use of Wikidata's ContentHandler, and the evaluation of Wikia's MessageWall. A plan for community engagement was proposed and accepted, with a consultation about the problems faced planned for early February, with experienced and newer users alike.

2013-02-monthly
In February, we analyzed and collated user research concerning talk pages. Early designs were shown to members of the Board of Trustees to ask for their input. Jeff Atwood (from StackOverflow and Discourse) came in to give us a brain dump of his work. Design work was done on secondary "modules" as examples for how existing workflows can be rebuilt within the Flow system. Community engagement strategies saw the beginnings of implementation with the creation of a "Portal" that will engage discussion about Flow at three locations (mediawiki.org, meta, and the English Wikipedia).

2013-03-monthly
<section begin="2013-03-monthly"/>Design work continued on Flow. We continued creating a "Portal" that will engage discussion about Flow at three locations (mediawiki.org, meta, and the English Wikipedia), and performing research.<section end="2013-03-monthly"/>

2013-04-monthly
<section begin="2013-04-monthly"/>Design work continues and several discussions were had about what constitutes a minimum viable product for the first iteration of Flow. Brandon Harris is now building an interactive prototype to help describe multiple functions.<section end="2013-04-monthly"/>

2013-05-monthly
<section begin="2013-05-monthly"/>Discussion portals were announced and opened on three wikis: the English Wikipedia, Meta-Wiki, and mediawiki.org. An interactive prototype was released to the public for discussion. Discussion is on-going, and the definition of the "minimum viable product" is being worked on.<section end="2013-05-monthly"/>

2013-07-monthly
<section begin="2013-07-monthly"/>This month, we released two new prototypes to showcase some ideas around Flow-enabled user-to-user discussion. We continued to collect user feedback and prioritize use-cases for a potential minimum viable product.<section end="2013-07-monthly"/>

2013-08-monthly
<section begin="2013-08-monthly"/>In August, we continued development of the Flow prototype by implementing revisioning, moderation, and display code, on top of the storage and block abstractions. We have deployed this prototype to an internal labs instance to encourage the full team's involvement in development. Additionally, we participated in an agile workshop run by Arthur and Tomasz from the mobile team. This workshop facilitated planning the Flow MVP and setting goals for the team's first development sprint, along with providing information about agile guidelines and practices that have worked well for the mobile team.<section end="2013-08-monthly"/>

2013-09-monthly
<section begin="2013-09-monthly"/>This month, we continued back-end work on the Flow first release – integrating with the recent changes table (to ensure that users will be able to monitor Flow boards via the watchlist and Special:Recentchanges, in the same way they monitor wiki pages), mentions and notifications, and an early experiment with VisualEditor-enabled posting. We also kicked off a sprint to create a new visual design treatment for the board and discussions that will work across desktop and mobile platforms. We are aiming to implement this design next month, in preparation for several rounds of new user and experienced user feedback before the first onwiki release.<section end="2013-09-monthly"/>

2013-10-monthly
<section begin="2013-10-monthly"/>In October, the Flow team implemented a new visual design treatment on the Flow prototype (currently hosted on WMF Labs), and we continued to work through the set of features needed for a minimum viable product (MVP) on Wikipedia. We held an in-office User Experience workshop, primarily with users new to Wikipedia, to get feedback on the usability of the new design. We're planning to demo the Flow MVP to interested WikiProjects in November to get more feedback on what's needed for a first on-Wikipedia trial.<section end="2013-10-monthly"/>

2013-11-monthly
<section begin="2013-11-monthly"/>This month, the Flow team finished out the feature set for our minimum viable product. We added watchlist integration, the ability to see board, topic, and post histories, and did a first round of community feedback and testing with our product to date. We also prepared for release to production wikis in December by working on Operations and Security needs.<section end="2013-11-monthly"/>

2013-12-monthly
<section begin="2013-12-monthly"/>In December, we deployed Flow to a few selected pages in production (Talk:Flow and Talk:Sandbox on mediawiki.org) and collected feedback about the features and design to date from the community. The results of the feedback period are summarized at Flow/Research. Throughout the feedback period, we worked on implementing design changes – such as a more compact view of the board and different affordances for topic and post actions, as well as different visualizations of history information – based on the comments of users testing the software.

We also began a straw poll about launching Flow as a beta trial in the discussion spaces of WikiProject Breakfast, WikiProject Hampshire, and WikiProject Video Games on English Wikipedia. Based on the outcome of these polls, we hope to deploy Flow to those pages in January.<section end="2013-12-monthly"/>

2014-01-monthly
<section begin="2014-01-monthly"/>This month, the Core Features team worked on integrating MediaWiki tools for dealing with spam and vandalism (AbuseFilter and Spam Blacklist) into Flow. We also launched an updated visual design and UI, based on the first round of experienced user feedback last month, as well as ongoing user testing with new users. Lastly, we created a script to disable Flow and return Flow discussions back into unstructured wikitext, so that we can begin trialing Flow in production in an extremely safe-to-fail manner. We are set to deploy our first trial on February 3, 2014 to two WikiProjects that volunteered on the English Wikipedia.<section end="2014-01-monthly"/>

2014-02-monthly
<section begin="2014-02-monthly"/>This month, Flow was launched on the talk pages of two English Wikipedia WikiProjects that volunteered to be a part of the first trial, WikiProject Breakfast and WikiProject Hampshire. We've continued to iterate on the front-end design of the discussion system based on user feedback, releasing a new visual treatment during the trial and starting work on a front-end rewrite for better cross-browser and mobile compatibility (to be released sometime in March). We also spent time making sure Flow integrates better with vital MediaWiki tools and processes (e.g., suppression and checkuser) and improving the handling of permalink URLs.<section end="2014-02-monthly"/>

2014-03-monthly
<section begin="2014-03-monthly"/>This month the Core Features team focused on improvements to how Flow works with key MediaWiki tools and processes. We made changes to the history, watchlist, and recent changes views, adding more context and bringing them more in line with what experienced users expect from these features. We also worked on improvements to the API and links tables integration. On the core discussion side, we released a Flow thank feature, allowing users to thank each other for posts, and began work on a feature to close and summarize discussions. Lastly, we continued work on rewriting the Flow front-end to make it cleaner, faster, and more responsive across a wide number of browsers/devices, which will be ongoing over the next month.<section end="2014-03-monthly"/>

2014-04-monthly
<section begin="2014-04-monthly"/>This month, the Flow team focused on back-end changes to improve moderation and history viewing, as well as implementing new front-end JavaScript templating to make Flow more responsive and easier to add new features onto. On the user-facing features side, we released the ability to close and summarize topics. This will allow users to manage active discussions and end ones that have come to a resolution. Flow is now the default discussion experience for many Beta Features discussions on mediawiki.org, and the team is accepting requests to enable Flow on more pages on that wiki for the purpose of testing complex multi-user discussion interactions.<section end="2014-04-monthly"/>

2014-05-monthly
<section begin="2014-05-monthly"/>In May, the Flow team prepared the new front-end redesign for expected release in mid-June. We completed work on sorting topics on a board by most recent activity, also for mid-June release. We changed hidden post handling so that everyone can see hidden posts, including anonymous users.

Back-end improvements include optimizations on UUID handling and standardized URL generation. We also merged Special:Flow for release; it's a community-created improvement that makes it easier to create redirects to Flow boards. We also made no-JS fixes for topic submission and replies.

Bug fixes include: Firefox errors, WhatLinksHere fixes, special characters in topic titles, topic creation on empty boards, curr and prev links in board history for topic summaries, and cross-wiki issues with user name lookup. <section end="2014-05-monthly"/>

2014-06-monthly
<section begin="2014-06-monthly"/> In June, the Flow team finished an architectural re-write for the front-end, so Flow will be easier to keep updating in the future. This will be released to mediawiki.org the first week of July, and Wikipedia the following week.

The new feature in this release is the ability to sort topics on a Flow board. There are now two options for the order that topics appear on the board: you can see the most recently created threads at the top (the default), or the most recently updated threads. This new sorting option makes it easier to find the active conversations on the board.

We've also made a few changes to make Flow discussions easier to read, including: a font size now consistent with other pages; dropdown menus now easier to read; the use of the new button style, and the WikiGlyphs webfont.<section end="2014-06-monthly"/>

2014-07-monthly
<section begin="2014-07-monthly"/>In July, the Flow team built the ability for users to subscribe to individual Flow discussions, instead of following an entire page of conversations. Subscribing to an individual thread is automatic for users who create or reply to the thread, and users can choose to subscribe (or unsubscribe) by clicking a star icon in the conversation's header box. Users who are subscribed to a thread receive notifications about any replies or activity in that thread. To support the new subscription/notification system, the team created a new namespace, Topic, which is the new "permalink" URL for discussion threads; when a user clicks on a notification, the target link will be the Topic page, with the new messages highlighted with a color. The team is currently building a new read/unread state for Flow notifications, to help users keep track of the active discussion topics that they're subscribed to. <section end="2014-07-monthly"/>

2014-08-monthly
<section begin="2014-08-monthly"/>In August, the Flow team created a new read/unread state for Flow notifications, to help users keep track of the active discussion topics that they're subscribed to. There are now two tabs in the Echo notification dropdown, split between Messages (Flow notifications) and Alerts (all of the other Echo notifications). Flow notifications stay unread until the user clicks on the item and visits the topic page, or marks the item as read in the notifications panel. The dropdown is also scrollable now, and holds the 25 most recent notifications. Last, subscribing to a Flow board gives the user a notification when a new topic is created on the board.<section end="2014-08-monthly"/>