slightly more formality for merges?

[cgwalters]

Thanks for creating this group! I would like my organization to participate more. I have a procedural comment/proposal related to this project.

Some specs like #199 and #202 went from "pull request opened" to "merged" in the span of ~a day.

I understand that both of these were viewed as "de-facto" standards, and I don't want to be seen as blocking, but it seems like even for a loose standards group like this at least some slightly more formal process - even just a "lazy consensus" of at least week or two week delay before merging specs would seem to make sense?

I think we could set up something like https://github.com/cncf/gitvote or equivalent based on a list of participating member groups, doesn't have to be heavyweight; I think having a process might even help boost engagement a bit.

[cgwalters]

Or to keep it very simple, we could start by change the Github settings on this repository to require at least 2 (probably 3 is better) approvers for a merge.

[poettering]

Or to keep it very simple, we could start by change the Github settings on this repository to require at least 2 (probably 3 is better) approvers for a merge.

note that the referenced spec actually did have 3+ positive reviews within a day of merging them. it's true though that the 2nd one only go them a few minutes after they were merged, and only had one before.

background: these specs were discussed in another forum before, and when it was suggested to move them to the uapi group it was already clear that they'd have enough approvals, so we sped up the process a bit.

Admittedly, this is a bit opaque if one wasn't part of those forums. but on the other hand for specs that already have more than one implementation, and non-trivial buy-in across projects I don't think we need to add an overly long waiting period...

The governance/decision making rules are documented here:

https://uapi-group.org/#governance

maybe we can extend that and suggest that completely new specs which are neither migrated here (and thus never have been approved before), nor have buy-in from multiple established projects we should wait a week before we consider merging them. does that make sense? if so, consider prepping a patch for that, the governance is in this repo