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

Yeesh, I somehow completely missed the notification on this response, sorry.

I think your (C) and (D) are completely reasonable, and I share those goals.  On (A), of course we want the reviews to be useful, which is part of what pushed them later in the steps (when the ideas are better baked, rather than just a collection of use cases - please note that there is a definite goal of getting the Chromium process to encourage early engagement with the community, rather than waiting to drop a fully-formed idea of an API on the public community's plate.  (Another way to read this is "the old de facto process was frequently well into prototyping (mid-late step 2) before it got announced publicly.)

The motivation for TAG review request being at the start of step 3 is that the entry to step 2 ideally doesn't have a design yet - you would be requesting a TAG review on a design that doesn't accomplish the goals, or is missing significant pieces.  I'd already planned for if the TAG wants to be engaged when the ideas are first coming up, we can easily hook that in - we already have notification (at least in most cases) via the incubation path (the latter part of step 1 drives a WICG proposal, which will send new-incubation-repo notifications to public-review-announce@w3.org, which we could ensure is more systematic).  I think that's a different request than the "there is a fleshed-out design that should achieve the goals, could you take a look" review, and that's probably what having a discussion would be good for.

The reason TAG review is mentioned in step 6, not step 4, BTW, is because it's a completion - if you haven't gotten a TAG review and responded to the feedback by the time you send an intent-to-ship, the API owners are going to be looking very askance.  Perhaps it would be a good idea for me to add an explicit "you should really be wrapping up your TAG review!" to step 4?

If you have some time to discuss during your next plenary session, let me know (preferably not between 3 and 6 AM in Pacific time.  :P )

The exit criteria for each step are captured in the Chromestatus tool, and 

-- 
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#issuecomment-703855358