On 12 December 2012 11:57, Andre Klapper aklapper@wikimedia.org wrote:
On Tue, 2012-12-11 at 19:30 -0800, James Forrester wrote:
This is not the final form of the VisualEditor in lots of different ways. We know of a number of bugs, and we expect you to find more. We do not recommend people trying to use the VisualEditor for their regular editing yet. We would love your feedback on what we have done so far – whether it’s a problem you discovered, an aspect that you find confusing, what area you think we should work on next, or anything else, please do let us know.[1]
[1] - https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback
Playing the bad cop who's reading random feedback pages daily:
As https://www.mediawiki.org/wiki/VisualEditor/Feedback also exists I wonder if the VisualEditor deployment on en.wp and its related feedback is so different from upstream that it needs a separate feedback page (instead of e.g. a soft redirect to the mw: one), or other reasons. Or does the en.wp one somehow make it easier for testers to report issues? When we deploy VE to other Wikipedias, will there also be separate VE feedback pages (maybe due to the different languages)?
Note: I'm not criticizing it, I'm just trying to understand, and I'm picking VE as the most recent example.
Thanks in advance for explaining, andre --
You're after a different audience for this alpha test - not the technically confident user who wanders from wiki to wiki and instinctively understands just about any software variation thrown at them, but those whose focus is on editing. Mediawiki wiki uses Liquid threads, which pretty well everyone considers an unacceptable talk page method, and it creates an unnecessary communication barrier for those who just want to report their findings rather than having to figure out a different site's software. And a rather significant number of enwp editors avoid other WMF wikis like the plague for complex sociological reasons. Bottom line, the objective is getting a wide range of editors to test the software through its various functions, identify issues, and report them. Making it as easy as possible for them to do so will produce the best response.
Risker