This somewhat circuitously brings us back to the subject. We have a
chance to rollout Flow the right way. There are some questions that
come to mind that might tell us if we're headed for a big win or a
bigger debacle:

1) Is the WMF working with the community as closely and substantially
as possible to make sure Flow is ready for primetime?

2) Is the community preparing itself for a major change, not only in
interface, but to some degree in wiki-philosophy about how discussions
are conducted- not to mention the notion that, while wiki software can
do almost anything involving asynchronous online communication, it
can't do everything as well as other interfaces?

I think Flow will be particularly challenging. I deployed Liquid
Threads on another site. I liked the threaded interface, as did
others. But overall it was roundly rejected because it was harder to
search (I only found out you have to add the namespace to the
searchable namespace in LocalSettings.php later), and it invasively
took over all discussion pages, among other headache. Problems like
these could easily be addressed before a rollout, but they should be
addressed as early as possible. It is notable, however, that the more
our users used it, the more they seemed to like it.

What can we do to make the Flow rollout as smooth as starting '''now'''?


On Fri, Sep 5, 2014 at 9:34 AM, Marc A. Pelletier <> wrote:
> On 09/05/2014 11:12 AM, Yaroslav M. Blanter wrote:
>> On 25.08.2014 06:07, Marc A. Pelletier wrote:
>> FLOW?
> Last I checked, Flow isn't deployed except as experiments in a handful
> of places, and is still in active deployment.
> But you're correct that this would constitute a replacement rather than
> a new method alongside the old.  A long, long overdue and desperately
> needed replacement -- but a replacement nonetheless.
> That also explains the very deliberate development and feedback loop.
> -- Marc
> _______________________________________________
> Wikimedia-l mailing list, guidelines at: 
> Unsubscribe:, 
> <>

Wikimedia-l mailing list, guidelines at:

Reply via email to