Support multiple origin trials per feature entry

[jrobbins]

Is your feature request related to a problem? Please describe. Features have always had the possibility of doing multiple origin trials, or extending an initially approved OT. However our data schema only has room for a single start and end date for each platform.

Describe the solution you'd like Multiple trials per feature entry.

[jpmedley]

@jpchase When an OT is extended, does it keep the same token?

I'm asking him because this may not be as straightforward as adding two new fields. I can think of multiple OT scenarios that may have implications for the data model.

@jrobbins I probably need to commit some stuff to paper before you start coding this.

[jpmedley]

Origin trial scenarios are described here. In general there are two scenarios:

• An extended origin trial continues without a gap and I believe uses the same OT token. Its intent is to continue information gathering.
• A second origin trial is started after first returning to 'in development', during which the feature's design changes in some way. I believe this requires a new token.

@jpchase Can you please confirm this?

[jrobbins]

When reviewing Intent-to-experiment and intent-to-extend-experiment emails, API owners have a policy about how long each one can be. We could surface those criteria here in help text, or provide a warning if the user violates them. See: https://www.chromium.org/blink/launching-features/#step-3-optional-origin-trial

[jpmedley]

That may be enforced when they apply for the token from @jpchase 's group. That might make anything we do superfluous.