Discuss process and onboarding of new features (Stages proposal)

[cwilso]

We began a discussion this week about new functionality, incubation, and how to improve design principles, etc. to scale up design stewarding, and make the "design gestalt" less homed in a small number of people. We should continue that discussion

[Conan-Kudo]

Could this process be used to address some of the issues that were brought up in #89? In the past couple of years, the problems that were described in that issue have seemingly amplified with further browser engine consolidation.

The most recent case I know of is the effective stall-out of JPEG-XL support on the web by the Chromium folks. With Chromium pulling out, there is effectively no way for it to become useful for the web because seemingly Mozilla hasn't done anything to act to support JPEG-XL as many users and developers want. Apple WebKit has said nothing so far about JPEG-XL either.

It's getting more difficult to have productive evolution of the web without Chromium effectively controlling that development, and I think it's worth figuring out how to mitigate that.

[Conan-Kudo]

I should clarify that I do agree that it isn't useful to make standards that nobody will implement, but we're in a situation now where it's actually too hard for independent standards development to succeed.

Do we have any folks from Servo invited into the WHATWG? What about inviting @awesomekling (developer of Ladybird)?