Workflow request - Please let PRs slated for discussion remain in "Draft" status

[ajnelson-nist]

PR #254 was merged while a group discussion about its backing Issue ( #212 ) on a call was pending.

I'd like to request that PRs remain in "Draft" status until the submitter believes it's down to getting final approvals from just the target resources' owners (editors). PRs in Draft status can't be merged (disallowed by GitHub interface) until the PR submitter designates it ready.

For the sake of managing PRs on GitHub, I've found it helpful in other projects to use a PR template with checkboxes, including one that reads something like this:

- [ ] PR in Draft status until discussions have concluded sufficiently for just final editor approval.

It's an easy box to check by the PR submitter or one of the eventually-reviewing editors. And other boxes can be added ad-hoc to track other implementation details.

[caribouW3]

Indeed, @VladimirAlexiev merged after his review, which should not have been done. Let's discuss on Monday whether we want to revert the entire PR, or some commits, or create an independent PR to make new changes eventually.

Only editors should merge, after group consensus (once there's a resolution during a call, preferably). If other mistakes happen, I'll make a different GH team for editors and remove rights from the WG team.

[tpluscode]

Indeed, @VladimirAlexiev merged after his review, which should not have been done. Let's discuss on Monday whether we want to revert the entire PR, or some commits, or create an independent PR to make new changes eventually.

Only editors should merge, after group consensus (once there's a resolution during a call, preferably). If other mistakes happen, I'll make a different GH team for editors and remove rights from the WG team.

Then only editors should have merge rights?
Can this be further fine-tuned with CONTRIBUTORS.md?

[ajnelson-nist]

There's also CODEOWNERS.

[tpluscode]

Ah yes, I think I had that in mind 😇

[afs]

It's an easy mistake to make and we have a protected branch.

+1 to the suggestion that editors do the merge. (This doesn't eliminate the problem entirely!)

"draft" can also be used for "work in progress" to let people see what's upcoming without meaning complete-for-review; then coming out of draft is a signal is ready for WG review.

Two possible uses of "draft" but only one word; we need to be clear which one we use here.

[ajnelson-nist]

@PapoutsoglouE - I suspect this issue can be handled with the same disposition as #320 . I'm fine with you closing this as Completed if you think it appropriate.