As part of his new [1]hope for helping to accelerate Wayland protocol development , Mike Blumenkrantz with Valve proposed an "experimental" protocol development area within Wayland-Protocols. He's also laid out a proposal for seeking to solidify the means by which suggested protocol changes can be rejected.

Blumenkrantz is working to lay out clear policy how protocol changes can be rejected with NACK'ed (negative acknowledgement). In particular, making it clear that only Wayland Protocol members have the authority to NACK a protocol and that NACK'ing a proposal does require "extreme circumstances" and that there can be negative consequences if they are improperly used.

He's hoping to make the details surrounding NACKs on patches clear and ensure they are seldom used and not abused to prevent developers from stalling development of new protocols without sufficient technical cause.

Mike has laid out his suggested governance changes around NACKs via [2]this merge request . He also has a brief write-up on [3]his blog with more details on this latest effort for helping to advance upstream Wayland faster.



[1] https://www.phoronix.com/news/Blumenkrantz-Faster-Wayland

[2] https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/341

[3] https://www.supergoodcode.com/gettin-nacky/