James,
Thanks. I have a follow up question regarding project management in general. When the length of time for development and testing are unbounded so that product quality is the principal goal, how do you forecast needs for human resources and financial resources?
Thanks,
Pine On Jul 27, 2015 12:07 PM, "James Forrester" jforrester@wikimedia.org wrote:
[Un-duplicate posting. Unless it's an announcement or critically-urgent, please don't ever do that.]
On 27 July 2015 at 11:27, Pine W wiki.pine@gmail.com wrote:
I'm happy to hear that VE is coming to mobile web.
It's not "coming" (it's been available for tablet users for 18 months); it's being improved . Once it's credible for phone users as opposed to just tablets, we'll remove the block that prevents them from using it .
I'd like to know more about what the plans are for user testing of VE on mobile.
Specifics are for the User Research team, but in general we're doing broad testing of all editing features on desktop and mobile, not looking at silos. The things that matter are meeting users' expectations simply and consistently, and solving issues as we identify them.
Would that happen in late Q2 at the earliest, and how much emphasis will
there be on user testing mobile VE while it's in beta?
It's ready when it's ready. There's no point (and a great deal of potential harm) in releasing things before they have a positive effect. Putting arbitrary dates (even as vague as "Q2") on improving things for our users means prioritising a deadline over making things better for them.
Yours, -- James D. Forrester Lead Product Manager, Editing Wikimedia Foundation, Inc.
jforrester@wikimedia.org | @jdforrester _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l