wayland-protocols scope and governance

[Emil Velikov]

Hi Drew,

On Mon, 6 May 2019 at 01:41, Drew DeVault <sir at cmpwn.com> wrote:
>
> Here's an updated governance document for everyone to consider. Changes
> from the first version:
>
> - Use wayland-devel instead of a dedicated mailing list
> - Use Gitlab for reviewing new protocols
> - Extend discussion period for governance amendments from 30 days to 60
> - Permit either 1 or 2 points of contact for a wayland-protocols member
> - Clarify who's affected by the cool-down period after a failed
>   membership removal vote
>
> I chose not to change the wording of the xdg namespace definition,
> despite Daniel's objection. I couldn't come up with a wording that I
> think would make everyone happy - feedback welcome. Under Daniel's
> proposed wording of "catch-all window management", a case is easily made
> for wlr-foreign-toplevel-management:
>
> https://github.com/swaywm/wlr-protocols/blob/master/unstable/wlr-foreign-toplevel-management-unstable-v1.xml
>
> I expect this would be controversial. Or perhaps it wouldn't be, and
> would fit into this namespace, but would just be NACK'd by some folks.
> Depends on how strongly integrated desktop folks want to gatekeep the
> XDG namespace. Thoughts?
>
>                           wayland-protocols governance
>
> This document governs the maintenance of wayland-protocols and serves to outline
> the broader process for standardization of protocol extensions in the Wayland
> ecosystem.
>
>                                  1. Membership
>
Disclaimer: I did not read through the prior discussion - the volume
was tad much :-(

What exactly is the goal of having membership?

At the end of the day if a project proposes a protocol and is willing
to tweak it based on community feedback - great.
If they don't well - not much one can do about it :-\

Thanks
Emil