[w3ctag/design-reviews] Blink Shipping Process (#516)

Hello TAG!

I'm requesting a TAG review of the Blink Process for Lunching Features to the Web. 

Given how closely we, TAG, work with teams from the Blink and Chromium community it will be great to review their process and consider if there are ways we could work more efficiently together.

  - Explainer¹ (minimally containing user needs and example code): https://www.chromium.org/blink/launching-features

  - Primary contacts (and their relationship to the specification):
      - Alex Russel @slightlyoff, Google
      - Chris Wilson @cwilso, Google
      - Chris Harrelson @chrishtr, Google
  - Organization(s)/project(s) driving the specification: Google, Chromium
  - Key pieces of existing multi-stakeholder review or discussion of this specification: N/A
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): N/A

Further details:
  - [] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)
  - Relevant time constraints or deadlines: none
  - The group where the work on this specification is currently being done:
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue):
  - Major unresolved issues with or opposition to this specification:
  - This work is being funded by: 

We'd prefer the TAG provide feedback as (please delete all but the desired option):
  💬 leave review feedback as a **comment in this issue**

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/516