Proposal: add exception for intent signals for Khronos APIs

[Ken Russell]

Hi Blink API owners,

I'd like to propose adding an exception to the "Signals from other implementations in an intent-to-ship" document:

https://bit.ly/blink-signals

for Khronos APIs. The motivation for this is specifically WebGL, which has been managed under Khronos' processes for over a decade.

Khronos' working group guidelines are documented here:

https://www.khronos.org/members/#membership_standardization_policy_and_process_documents

https://www.khronos.org/files/working-group-guidelines.pdf

The WebGL working group operates under Khronos' rules of unanimous consensus - see Section 9, "Building Consensus and Making Decisions". It has been extremely rare that topics have come to a formal vote. Apple, Google, Microsoft and Mozilla regularly attend the biweekly meetings.

Specification changes that are committed to:

https://github.com/KhronosGroup/WebGL/tree/main/specs/latest/1.0

https://github.com/KhronosGroup/WebGL/tree/main/specs/latest/2.0

and reflected in:

https://www.khronos.org/registry/webgl/specs/latest/1.0/

https://www.khronos.org/registry/webgl/specs/latest/2.0/

can be trusted to have been agreed upon - with no objections - from all of these browser vendors.

Thanks for considering this.

-Ken

[Chris Harrelson]

Makes sense to me. I've added this to the list of exceptions in the signals document. Other API owners, please comment if you disagree.

--
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/CAMYvS2fk1-MRP93OijqZxU5%3D0A68DrwOT0VwvTyX7kA7Z-KYyA%40mail.gmail.com.