search

w3c / process

W3C Process Document
https://www.w3.org/policies/process/drafts/
186 stars 124 forks source link

Introduce path to shortcut the Council #703

Closed frivoal closed 1 year ago

frivoal commented 1 year ago

To be used in cases that can be resolved unanimously without debate solely based on the Team's report and proposed resolution.

See #678

Preview | Diff

cwilso commented 1 year ago

LGTM

chrisn commented 1 year ago

I would suggest changing "absurd" ... Also, what is "repetitive" intended to mean here - that an FO can be short-circuited on the basis of precedent from a previous FO?

dwsinger commented 1 year ago

I would suggest changing "absurd" ... Also, what is "repetitive" intended to mean here - that an FO can be short-circuited on the basis of precedent from a previous FO?

I don't think similar is enough; essentially identical would be repetitive.

chrisn commented 1 year ago

I don't think similar is enough; essentially identical would be repetitive.

I agree. So if "repetitive" means "based on precedent from previous FO conclusions", I'd suggest we say that, for clarity.

But, I have a general concern with this change that we're designing process for situations that haven't happened yet, so would prefer to see us gain more experience before adding this.

dwsinger commented 1 year ago

I don't think similar is enough; essentially identical would be repetitive.

I agree. So if "repetitive" means "based on precedent from previous FO conclusions", I'd suggest we say that, for clarity.

But, I have a general concern with this change that we're designing process for situations that haven't happened yet, so would prefer to see us gain more experience before adding this.

perhaps duplicative would be a better word?