The road to shipping gets _even longer_ if the team in question is out ahead on a design (that is, not catching up). In these cases, we have an arduous process that involves soliciting broad feedback and often running experiments (which can and do keep us from shipping!)
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Could you comment on this?https://mobile.twitter.com/zcorpan/status/1139157542993637377 …
-
See the research background:https://github.com/jackbsteinberg/std-toast/tree/master/study-group …
- 4 more replies
New conversation -
-
-
“Hi TAG, please review this new thing that we wrote up in a google doc. We did an internal google security review and it’s fine. Thanks”
-
@sundress and I are pushing back on Google Docs, and there should be less of that going forward. - 1 more reply
New conversation -
-
-
That's fine. Now pick a better name for it that conveys this point.
-
You're not alone in the historical baggage of teams that implement late and don't iterate in public. We hear that. If you have a suggeted name, can you send it here for the OWNERS to discuss?https://groups.google.com/a/chromium.org/forum/#!forum/blink-api-owners-discuss …
- 5 more replies
New conversation -
-
-
Seems like a lot of people have misunderstood what you're saying is a fair and open process, perhaps the wording and communication could change to make sure people don't think Google is doing things underhand?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.