Originally posted by ryao
View Post
Wayland is a protocol based heavily on extensions. The core is very small and fairly universal, and even that is divided into parts that might be left unimplemented in some circumstances. When conflicting cases appear, they are separated into different extensions, so everyone can live happily together. If upstream does not approve of some extension, that extension can perfectly well live outside of Wayland upstream, and everyone willing can use it. There is no way to really prevent that, either. It is up to individual toolkits (Wayland clients) and compositors (Wayland servers) to decide which parts they implement and rely on.
Whether some piece of software (as opposed to protocol) that needs active maintenance supports some particular features is a completely different matter.
On another note, patches written by people with an Intel email address have been rejected.
Comment