Working Group Adoption

[sefeng211]

I'd like to propose a working group adoption (webperf?) for this spec, given we now have two implementations (Chrome and Firefox).

Not sure what the steps to make this happen. cc @yoavweiss @shaseley

[sefeng211]

We also need a clear path for upstreaming those HTML Standard changes

[shaseley]

Thanks Sean. The resolution at TPAC was to migrate this directly to HTML; I'm working on a PR for this, but keep getting distracted. I have the spec converted, but it's taking a bit of effort to reduce duplication, etc. I'll try to make some progress on this in the next couple of weeks.

[yoavweiss]

Thanks for proposing that, @sefeng211 !

@nicjansma @caribouW3 - we can discuss adoption at the next WebPerf call and then send a CFC. Does that make sense?

[sefeng211]

The resolution at TPAC was to migrate this directly to HTML

@shaseley Hey Scott, was the resolution to migrate the entire spec to HTML, or just https://wicg.github.io/scheduling-apis/#sec-patches-html?

[shaseley]

Hi @sefeng211, my understanding/intent is entire spec. I had positioned the WHATWG/WebPerfWG conversation as "migrating the spec" to WHATWG (see start of minutes, slides), which I had meant as the whole spec (vs. adding hooks). I thought the scope was clear in the discussion and follow-up conversations, but if anyone disagrees/objects with this plan, please let me know and we can discuss further!

[sefeng211]

Cool, yeah that sounds good