w3c
Generalizing AC Appeals and using this procedure for recall.
This PR is a first draft attempting to address https://github.com/w3c/process/issues/886 and https://github.com/w3c/process/issues/882. Neither haveIt has not been resolved on at this point, but this shows what adopting themit could look like.
It can be reviewed as a whole, or commit by commit, to distinguish the effects of #886 from those of #882.
update: #886 has been handled separately, removing discussion of it from this pull request.
An alternative mid-ground would be stating a "supermajority" threshold: twice => > 2/3 or 67%, thrice => > 3/4 or 75%
@chaals, I'd rather not phrase it this way, because when you just say "supermajority of 2/3" or some such phrasing, it's ambiguous how you treat abstain ballots. You can make it clear, but that usually make the phrasing longer and clunkier, which is why I think "x times as many ballots for as against" or that sort of phrasing is better.
I've updated this draft PR to reflect my current take on this issue, as expressed in https://github.com/w3c/AB-memberonly/issues/237#issuecomment-2354297741.
The AB has not reached a conclusion on this topic. Temporarily removing agenda+
I think this PR needs some updating; and we should clean up the discussion to focus on the current proposal at hand, rather than on previous variations of trying to address this problem. @frivoal Would it make sense to do the clean-up here, or to summarize the open points of discussion into the issue and open a new PR?
The Revising W3C Process CG just discussed https://github.com/w3c/process/pull/888, and agreed to the following:
The full IRC log of that discussion
<brent> subtopic: https://github.com/w3c/process/pull/888<Ian> Brent: Say "merge", "continue", or "close"
<brent> Github: https://github.com/w3c/process/pull/888
<Ian> PLH: We have a "Needs AB feedback" label
<Ian> [We review the background of the pull request]
<Ian> Brent: I'm hearing it's not ready to merge; we need more AB and TAG feedback.
Merging into the ab-tag-discipline branch, as decided on the 2025-09-24 Process CG call. That branch itself is not being merged into main, and does not represent consensus, merely work in progress.