On 11 August 2014 11:08, Martijn Hoekstra <[email protected]> wrote: > > I think this is where part of the problem lies. Will discussion on whether > or not to deploy it to a local wiki still be possible when the WMF decides > it is ready for wider deployment, with a possible no for an answer? >
I'm not in the senior management, so I don't have an answer to that question. What I can tell you, as a person who is in charge of the day-to-day decisions about what goes into the software the WMF produces, is that the best time to make sure the software meets your needs is not at the step where it's being deployed, but as the step where it's being developed! So, to make Flow meet your needs, get involved! Test the latest version of Flow (https://ee-flow.wmflabs.org). File bugs ( https://bugzilla.wikimedia.org). Take a look at the Flow team's Trello board (https://trello.com/b/lOh4XCy7/flow-sprint-f). Send the product manager of Flow an email ([email protected]). Maybe even ask to have a hangout with him to discuss your concerns. Speaking from experience, this kind of feedback is one of the highest priority things a product manager can do. And this kind of contact shapes decisions, and shapes priorities. This is the best way to be involved: early, and often. Dan -- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
