Lines Matching full:protocols

1 # wayland-protocols governance
3 This document governs the maintenance of wayland-protocols and serves to outline
9 Membership in wayland-protocols is offered to stakeholders in the Wayland
17    protocols (e.g. compositors, GUI toolkits, etc), rather than special-purpose
32 4. A 14 day discussion period for comments from wayland-protocols members will
51 ## 2. Protocols
58 2. Protocols in a namespace may optionally use the namespace followed by a dash
60 3. The "xdg" namespace is established for protocols letting clients
63 4. The "wp" namespace is established for protocols generally useful to Wayland
64    implementations (i.e. "plumbing" protocols).
65 5. The "ext" namespace is established as a general catch-all for protocols that
70 1. All protocols found in the "xdg" and "wp" namespaces at the time of writing
72 2. Protocols in the "xdg" and "wp" namespace are eligible for inclusion only if
74 3. Protocols in the "xdg" and "wp" namespace are ineligible for inclusion if
76 4. Protocols in the "xdg" and "wp" namespaces must have at least 3 open-source
79 5. Protocols in the "ext" namespace are eligible for inclusion only if ACKed by
81 6. Protocols in the "ext" namespace must have at least one open-source client &
86 ### 2.3. Introducing new protocols
89    wayland-protocols Gitlab repository.
92 3. An indefinite discussion period for comments from wayland-protocols members
93    will be held, with a minimum duration of 30 days. Protocols which require a
99 5. Amendments to existing protocols may be proposed by the same process, with
110    implementation status of protocols included in wayland-protocols.
111 3. A statement from each member of wayland-protocols will be included on the
138    their update in the wayland-protocols repository.
144 2. A 30 day discussion period for comments from wayland-protocols members will
147    effective if it's ACKed by at least 2/3rds of all wayland-protocols members,
149    wayland-protocols repository at this point.