Structured Discussions/FAQ

This page hopes to answer several frequently asked questions about Flow.

Nomenclature
The following nomenclature is used in this document to avoid confusion. This nomenclature is development-facing, not user-facing, and terms may change when visible to the user.


 * Board - a collection of topics, equivalent to a talkpage. There may be only one Board per page.
 * Header - content at the top of a Board (introductory text and such). There are/will be limitations on what can go in the header.
 * Topic - a "workflow instance". In the discussion space, this is a single discussion.  This document concerns itself primarily with discussion workflows; however it should be noted that workflow instances can take many forms.  Topics may be subscribed to by multiple Boards.
 * Summary - a Topic can be summarized. Other workflows might be more elaborate, e.g. "Closed. Answer #7 to this question was accepted by the originator on 2013-10-15".
 * Post - an atomic reply, comment, or object whose parent is a Topic.
 * Comment - synonymous with Post.
 * Reply - a child Post of another Post. In the October prototype, there is only one level of replies and these are called "Tangents".
 * Branch - a series of Posts that are all ultimately children of a single Post.
 * MVP - an acronym standing for "Minimum Viable Product".
 * Flow team - WMF staff working on the Flow project (including developers, designers, analysts, and product managers)
 * Core Features team - WMF development team that builds and maintains features like PageCuration, Echo notifications, and Flow. This team will primarily be focused on Flow this fiscal year (July 2013-July 2014)
 * Extension:Flow, aka "Flow" - the software product, which has two components: a discussion system and a workflow engine. The Flow team will be working primarily on the former this fiscal year (July 2013-July 2014).
 * w:WP:Flow or Flow Portal - the Flow Portals, or homepages.

Is this replacing talkpages?
The short answer is "yes" – the long answer is "yes, but not for a long time". Talkpages are incredibly complex, with the number of processes they have to support (discussion closing, unblocking, requested moves) and the number of things a user can do on them – there's some research into this at Flow Portal/Use cases. Because of this, we've decided to start small: we don't have all the answers yet, and don't want to act as if we do.

The first release (in early December 2013) will be to a couple of Wikiproject talkpages, where the Wikiproject has volunteered to test the software. Work after that will also go into the Wikipedia talk namespace and its various workflows, before switching to focusing on places like user and article talkpages. Conversations on Wikimedia projects are very complex things. We need to start with the "simplest" use cases first.

Given this plan, we're not going to be offering Flow as an option for most users until mid to late 2014. When we start rolling it out more actively, it will be opt-in for existing users (and the default for new ones). At some point in the future, once the software is stable and a significant portion of active Wikimedians have had a chance to trial it and offer their feedback, we may mandate Flow on all discussion pages, but that's a long way away.

What about places like AN/I and the Village Pumps?
Places like the Village Pumps are natural candidates for Flow, but we're not planning on rolling out there in the first release. The idea is to deploy in a slow and steady fashion, working from simple, lower-traffic talkpages up to more complex ones.

Something like the Administrator's Noticeboard, however, is far more complicated. It's a high-velocity system with many user-created shortcuts and complex social conventions, and starting there would probably be asking for trouble.

Can I opt-out?
Sort of. In terms of using Flow on talk pages, it won't be an option on user talkpages for quite a while. When it becomes one, it will be opt-in for existing users – you won't be forced to have it on your talkpage if you don't want it. If you convert to using Flow during the trial period (in a WikiProject discussion space), we'll be able to convert the content back into a normal talkpage if needed.

At some point in the future, after a great deal of community testing and feedback, we may want to convert all remaining wikitext talkpages into Flow talkpages. That's a long way away, and it won't happen without a great deal of discussion and gradual iteration of the product. If you're concerned about how Flow will look and behave, your best bet is to trial the software early, so you can give us feedback on what needs changing well before we begin discussion on whether or not it should become the default on all discussion pages.

In terms of viewing, you won't be able to opt out of seeing Flow. If other users have converted their talkpages to Flow pages, or reached consensus that a Wikipedia or article talkpage should be converted, there's not going to be a way to avoid using Flow if you want to contribute to that page.

What will happen to current talkpage discussions?
The current plan is to archive the talkpage and link to the archives from the talkpage header. Obviously this complicates deployments somewhat – what do people do if they'd like to try Flow but have discussions actively occurring on their talkpage? – but it's the least-bad option. Ultimately, we plan to have a search feature for Flow that allows users to go through the pre-Flow archives and find content from there, too, but that probably won't be a part of the very first release to Wikipedia.

What about IP/anonymous editors?
Anonymous users will be able to use Flow-enabled talkpages as any other user, although there will be some restrictions: they'll be unable, for example, to hide posts. Generally these will align with the restrictions existing talkpages have. When Flow is more widely enabled, they'll have Flow-enabled talkpages (again, like any other user).

Why don't we use a pre-built system, like PHPBB or Discourse?
The simple answer is that "they won't cut it". The complex answer is that pre-built systems are designed around singular use cases, and Wikimedia projects do not have "singular" use cases. On the English Wikipedia alone, the following are discussions that take totally different forms: The list goes on and on. A singular package will not and cannot cover these cases. So we have to build our own.
 * User talk
 * Article talk
 * Requests for Comment
 * Request for Adminship
 * Deletion discussions
 * Merge discussions
 * Village pump discussions
 * AN/I
 * Arbcom cases

Why not use LiquidThreads?
LiquidThreads (LQT) was an early attempt at creating a structured discussion system. It has both strengths and weaknesses. After exploration and discussion, LQT was abandoned as a solution going forward for several reasons.

First, LiquidThreads has incredibly poor performance, especially when run at scale. This has to do with the way that individual comments or posts are stored, parsed, rendered, cached, and assembled. If a thread has 50 responses, and the user reading it is logged in, then all 50 responses must be re-rendered, parsed, and assembled every time. There is no way to cache them. This is terribly slow. Second, Flow is designed to be interwiki from the beginning. This requires that it have a completely different data model (one that supports globally unique identifiers). LiquidThreads cannot (and could never) provide support for this.

Third, Flow is designed to be future proof. Since the roadmap for Wikimedia projects is heavily invested around the VisualEditor, the data that Flow creates must be able to work with that. Upgrading LiquidThreads would require that we provide an agonizing level of backwards compatibility.

Finally, LiquidThreads was only designed to be a discussion system and as such is hamstrung by being less flexible than is required for discussions on Wikimedia projects. Flow is designed to be a workflow facilitation system. The difference may seem subtle on the surface but deeper examination into the way various Wikimedia projects use the collaboration space will quickly show that simple forum software is insufficient to meet the needs of the community. In fact, very few discussions actually match the pure conversation model that LiquidThreads is designed to answer. Flow is designed to be flexible with regards to workflows and collaboration techniques in a way that LQT could never be.

What is the MVP, and what will the initial release incorporate?
It's important to understand that the MVP (or minimum viable product) is not an unpolished version of the full product; it's a proof of concept.

We're building a single-feature MVP that we think our early adopters (users that discuss content within WikiProjects) will understand, find useful, and get excited about enough to ask for more of. That single MVP feature is structured, atomic discussion elements that can be interacted with (replied to, moderated) separately, as opposed to a single unstructured talk page that must be edited in its entirety.

The goal of the MVP, which we are building on a test wiki, is to invite users to try it and see if it's ready for a real trial on Wikipedia. The goal of the first release on Wikipedia (on a couple of WikiProject discussion pages) is to deploy the MVP in a real discussion environment and iron out any bugs that occur. But it's also to go beyond the single-feature MVP and, together with the community, identify additional features and functionality that we need to add in order to make Flow suitable for more complex discussions and collaboration, as well as changes that will bring it more in line with users' needs and expectations.

The benefit of this approach is that we won't have sunk a ton of time and resources into our product before showing it to our community. If users don't find the MVP suitable for onwiki release, we can add functionality that they identify as crucial. Once Flow is in trial on Wikipedia, each new release will be an opportunity for staff and the community to discuss and collaboratively prioritize work on new features.

How will Flow handle spam and vandalism?
Each topic and individual post will come with a set of moderation features. These are:
 * 1) Hide (equivalent to reversion/rollback);
 * 2) Delete (equivalent to revision-deletion), and
 * 3) Suppress (equivalent to oversight or, well, suppression ;p)

Handling spam and vandalism in Flow should actually be easier than dealing with it on existing talkpages. Because Flow topics and comments exist as discrete elements, a specific post can be removed with a single set of actions: there's no need to go through the page history removing intervening comments, for example.

Will Flow support wikitext or the VisualEditor?
Both. Flow will be linked into Parsoid, which is the software that the VisualEditor uses to read and write wikimarkup. Hooked into that will be both a wikitext editor and the VisualEditor: users can pick which they want to use. Whatever markup Parsoid supports, Flow can support. There may be some restrictions put in – so, for example, it might be a bad idea to have magic words usable if we use a magic word to trigger Flow: we don't really want people embedding a Flow board in a Flow board in a Flow board. Complex templates that use parser functions might be limited for performance reasons. But, generally speaking, anything users commonly need to use (mathematical symbols, references, templates) will be available before any widespread deployment. Users can use subpages for wiki text or templates incompatible with Flow, since subpages of Flow-enabled pages won't themselves be Flow-enabled (unless someone requests it).

Will Flow support all the templates and other markup we need in discussions?
Yes. You can see and test templates and other markup in the prototype, eg this thread has some examples. Note that we've only imported a few hundred test templates – more can be requested at w:Wikipedia:Flow/Top templates. As mentioned above, there may be some markup that isn't supported, but things that are necessary shouldn't be on that list.

What happens to my custom signature?
Flow will not directly support custom signatures, for a couple of reasons. The first is that they're disruptive from a UI point of view. Custom signatures are great for letting people know who said what; they allow for a specific user to be easily, visually distinguishable in discussions. The problem is that the way this comes about is by allowing refactoring of where links live, how they're displayed, and so on. As a result, there's a complete lack of consistency, which hurts the ability of users to navigate easily. One user might have their talkpage link in one place – another in a different place, and with a signature that doesn't actually reveal their username. The second is technical; allowing people to add raw HTML formatting into Flow boards could cause serious issues and errors in how the page is displayed.

Having said that, we appreciate the advantages of custom signatures; it allows for some distinguishing elements, it allows for forms of identification that extend beyond username. We're going to be working a "preferred name" field into the interface to allow for the latter; while it won't be as malleable as the status quo, it will allow for some originality. Your own posts will be visually highlighted to be more easily findable.

Will we be able to edit other people's posts?
There's a common design argument that users being allowed to edit the posts of others is atypical and unexpected: a discussion medium does not work without the certainty that the comment you are replying to is genuine, and that your comment will not  itself be tweaked or corrupted by others. Accordingly, the argument is for Flow to not permit modification of posts, with the exception of a  user trying to modify their own contribution.The problem with this is that the community has developed various  workflows in discussions and in the talk namespaces that are dependent  on that kind of editing and interleaving: a list of examples can be  found here, although it's not canonical. Removing the ability to edit the comments of others undermines these workflows. At the moment we're trying to build a list of situations where users need to be able to edit comments, so we can see whether this is an insurmountable obstacle. If you can think of any not listed, please add them. What's probably going to happen is that we'll build Flow so that comment editing is a configuration setting, and then make the initial deployment to a couple of wikiprojects with it turned off. If it turns out there are situations where comment editing is necessary, we can easily enable it, either for everyone or just for a subset of editors (autoconfirmed, say, or administrators).

How will you support all of the processes Wikipedia uses?
It's a complex problem. In line with the philosophy of a wiki, Wikipedia (and other Wikimedia sites) have developed their own workflows, based on social conventions and templates, inside talkpages. An example of this on the English-language Wikipedia would be the unblocking process; a user edits a template to add a rationale, which adds a category, which admins can see, and an admin closes it one way or the other...and that's one of the simpler workflows. There are thousands of others, many of which are more complex, and many of which we're unaware of. It'd be silly of us to assume that we could fit all of them into Flow at our end. Instead, what we plan on doing is working on a workflow engine – a structured language that editors can use to describe a workflow and incorporate it into Flow, for a specific action or a specific page. This sounds a lot like templates in some ways, and we hope that the same people who write templates will be interested in working on this, but there are a couple of differences: Due to the complexity of the customizable workflow piece of Flow, we're not focusing on it just yet. Our first priority is to tackle user-to-user discussions and build workflows on top of that.
 * 1) First, the language will actually be integrated into MediaWiki. At the moment, one user has to write the unblocking template, which is somewhat complex, and every other user has to be very careful to use it in a specific way, fill out the template just-so, and so on. With workflows, one user can write an unblocking workflow...and to everyone else, it will look like it's part of the software itself, and be fully integrated into Flow.
 * 2) Second, this is something we can use in other projects, too. In the above example of an unblock template, if another language or sister project wants to adopt this template, they have to copy over the template code, documentation, and all its dependencies to their project, which is time-consuming and prone to error. With a common workflow language across MediaWiki, we could standardize not only simple workflows, but also more complex software like Page Curation and Echo notifications, making it easier for users to configure and create custom messages for these tools.

Questions about the design or layout
The initial design is experimental in nature and intent, and will be changing based on feedback and onwiki testing, over the coming months. You can read about the decisions that went into the current design at w:Wikipedia:Flow/Design FAQ, and discuss them at its talkpage. [Reminder: As of October 2013, the design on the prototype site is still full of holes.]