https://bugzilla.wikimedia.org/show_bug.cgi?id=60178
--- Comment #22 from Maryana Pinchuk <[email protected]> --- There's a lot of speculating and conjecture going on in this thread, and, ironically, the only way to clear most of it up is to let real users try Flow in a real setting, aka a highly limited enwiki trial deploy :) Please, let's separate the concerns around Flow being deployed globally, 100%, to all users (which won't happen for a year at the least, after a ton of community-feedback-soliciting, bug-fixing, feature-building, and design-revamping) and the concerns around deploying Flow to https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Hampshire and https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Breakfast as a reversible opt-in trial. As it stands, I see no reason to block deployment to those two pages -- no critical workflows will be disrupted, we passed security review, and in the extremely unlikely event that anything goes wrong, we can easily turn Flow off. As a sidenote, I appreciate that most people's concerns are coming from a good place, but marking a flurry of bugs as blockers like this at the last minute, when a new feature has been live in a production environment for over a month, is unhelpful. In the future, if any of you feel that a critical issue is not being adequately addressed by a features team, please reach out to the product owner (in this case, me) over email, IRC, or in person (especially in those rare, magical moments when we're all in the office together and have ample opportunity to talk face-to-face, as was the case all of last week). -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
