Lines Matching full:protocols

1 # Wayland protocols
3 wayland-protocols contains Wayland protocols that add functionality not
4 available in the Wayland core protocol. Such protocols either add
7 wayland-protocols.
9 A protocol in wayland-protocols consists of a directory containing a set
15 Protocols in general has three phases: the development phase, the testing
19 wayland-protocols, but is actively being developed, for example by
22 request](https://gitlab.freedesktop.org/wayland/wayland-protocols/merge_requests),
24 [issue](https://gitlab.freedesktop.org/wayland/wayland-protocols/issues).
32 2.3](GOVERNANCE.md#2.3-introducing-new-protocols) requirements have been
34 to `staging/` directory of wayland-protocols and made part of a release.
57 previously used by wayland-protocols, where protocols initially
63 stable protocols.
68 the toplevel directory containing the protocols with the same stage.
69 Stable protocols are placed in the `stable/` directory, staging protocols
70 are placed in the `staging/` directory, and deprecated protocols are
73 Unstable protocols (see [Legacy protocol phases](#legacy-protocol-phases))
81 explanation and motivation in the commit message. Protocols are
84 section 2](GOVERNANCE.md#2-protocols) for more information.
90 To propose changes to existing protocols, create a GitLab merge request.
100 All protocols should avoid using generic namespaces or no namespaces in
103 interface names from other protocols should also be avoided.
105 For generic protocols not limited to certain configurations (such as
109 For protocols allowing clients to configure how their windows are
112 For operating system specific protocols, the interfaces should be
197 [GOVERNANCE section 2.3](GOVERNANCE.md#23-introducing-new-protocols).
201 Each release of wayland-protocols finalizes the version of the protocols