PSA: intent-to-experiment needs a draft spec

[Chris Harrelson]

In response to recent requests for clarification, the API owners have decided that an intent-to-experiment requires a draft spec. The updated guidance has been adopted here. The new text reads:

Your feature must...

Have a draft spec for your feature

• Ideally this would be in the form of an actual spec -- or PR against an existing spec -- in the format expected by the eventual standards body (although the draft might be hosted elsewhere while discussions are ongoing), but a detailed explainer laying out all the details may suffice. The level of detail needs to be enough so that (a) developers participating in the Origin Trial know how it works, and (b) spec editors for the relevant eventual specifications can see exactly how it would affect that spec when added.

[Joe Medley]

FYI, in the new interface, the spec link field is located in the "Start prototyping" phase. 

Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195

If an API's not documented it doesn't exist.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-hQzss0wLcM7sHhxvd_ZWzOwJR-nr2iT1%2ByazYT4346A%40mail.gmail.com.