Verification of charter refinement

[frivoal]

Do we need to explicitly add team verification of a group decision to end charter refinement and move to the AC review in order to ensure that rules were followed (DoC compiled, wide review happened, all issues were formally addressed…)?

Can we instead assume that the Team's ability to participate in the charter refinement (and if #969 is accepted, to replace the facilitator) is sufficient to enable them to insist on those?

[css-meeting-bot]

The Revising W3C Process CG just discussed Verification of charter refinement, and agreed to the following:

• RESOLVED: Add Team verification, with Team discretion to enforce or skim over requirements as discussed here

The full IRC log of that discussion

<fantasai> Subtopic: Verification of charter refinement
<fantasai> github: https://github.com//issues/971
<fantasai> florian: In this Charter Refinement world, there's requirement for horizontal review, for addressing comments, and for disposition of comments
<fantasai> ... When taking decision to move to AC Review, if these things weren't done, can the Team refuse to initiate AC Review?
<fantasai> plh: Notion of Team verification
<fantasai> Ian: Need flexibility to say, despite not completing the requirements, moving forward for good reasons, e.g. timeliness
<fantasai> plh: Or e.g. we didn't request horizontal review of PSIG charter
<fantasai> florian: Having Team verification means that can skip things for good reason, rather than making them "must".
<fantasai> plh: And issue of timing out on review requests
<fantasai> florian: OK, hearing resolution to add team verification
<fantasai> PROPOSED: Add Team verification, with Team discretion to enforce or elide requirements
<fantasai> Ian: Does it make everything "should" or... ?
<fantasai> florian: I'll think about this
<fantasai> plh: In practice do that for transition requests
<cwilso> +1
<fantasai> fantasai: "wide review" per PRocess doesn't require horizontal review. "wide" is relative to what you're reviewing
<fantasai> florian: Yes, that's how Team gets its discretion
<fantasai> RESOLVED: Add Team verification, with Team discretion to enforce or skim over requirements as discussed here