I2E requirements for Finch trials

[Mike Taylor]

Hi owners,

I'm wondering what the desired requirements are for running Finch
experiments where we enable a post-I2P / pre-I2S feature for some
percentage of (pre-)release users. Does this require an Intent to
Experiment? When I read
https://www.chromium.org/blink/launching-features, it seems to focus
entirely on Origin Trials.

Assuming other non-Chrome Chromium browsers have their own
experimentation frameworks, would we ask for I2Es for those as well?

thanks,
Mike

[Chris Harrelson]

Yes, a Finch experiment on stable requires an I2S or an OT variant w/I2E. And of course a Finch experiment is not the typical way to do things, so it would need an explanation of why Finch is the appropriate method in these cases. We have had examples of that in the past and that's what we decided. An experiment with API changes on beta needs approval from the API owners but not necessarily the blink-dev formalities.

Example.

Outreach to Chromium browsers is not required, but you can feel free to do it if you want.

Chris

p.s. If you are willing, could you add text to launching-features for this case?

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/b22341be-5c9f-6c3b-a7af-dcc01a8b2b9d%40chromium.org.

[Mike Taylor]

Thanks Chris.

And yes, happy to add some text to clarify this (in a few days, in case others want to comment).

[Alex Russell]

Clarification here would be helpful. Thanks for doing it, Mike!

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/fbab91c9-7ad9-804d-97c0-070f97cff37f%40chromium.org.