> To better address the needs of our core contributors, we're now focusing > our strategy on the curation, collaboration, and admin processes that take > place on a variety of pages. Many of these processes use complex > workarounds -- templates, categories, transclusions, and lots of > instructions -- that turn blank wikitext talk pages into structured > workflows. There are gadgets and user scripts on the larger wikis to help > with some of these workflows, but these tools aren't standardized or > universally available. > > As these workflows grow in complexity, they become more difficult for the > next generation of editors to learn and use. This has increased the > workload on the people who maintain those systems today. Complex workflows > are also difficult to adapt to other languages, because a wiki with > thousands of articles may not need the kind of complexity that comes with > managing a wiki with millions of articles. We've talked about this kind of > structured workflow support at Wikimania, in user research sessions, and on > wikis. It's an important area that needs a lot of discussion, exploration, > and work. > > Starting in October, Flow will not be in active development, as we shift > the team's focus to these other priorities. We'll be helping core > contributors reduce the stress of an ever-growing workload, and helping the > next generation of contributors participate in those processes. Further > development on these projects will be driven by the needs expressed by wiki > communities.
This sounds a lot like PageTriage, which at best was a mixed success. I hope the team is able to extract lessons from that extension and apply them to whatever they intend to work on. -- bawolff _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
