Agenda: W3C Process CG Telecon 11 October 2023

Sorry this is late. I'm happy to re-open for next time (or open a follow-up 
on) any discussion we resolve if someone unable to attend disagrees with the 
resolution. :)

Dial-in: 
https://www.w3.org/events/meetings/74b08985-d615-46d4-a52c-da0071b133c1/20231011T070000/
This meeting is at 7am Los Angeles, Wednesday 11 October 2023.

=== Follow-up on Process 2023 AC Review ===

As follow-up to the AC Review of Process 2023, the AB resolved on a few 
changes to recommend to the Director. The Director turned them down without 
prejudice given the timeline, deferring them to the Process 2024 cycle. Should 
we merge these PRs?

See Disposition of Comments
   https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-05-24-doc

Excluding TAG/AB from Council Decision votes on their own Decisions
Issue: https://github.com/w3c/w3process/issues/749
PR: https://github.com/w3c/w3process/pull/761

Require reporting of dismissal vote countes
Issue: https://github.com/w3c/w3process/issues/748
PR: https://github.com/w3c/w3process/pull/760

=== Substantive PRs to Review ===

CR Snapshots need to address wide review issues
Issue: https://github.com/w3c/w3process/issues/781
PR: https://github.com/w3c/w3process/pull/787

Default custodianship for Registries if custodian no longer available
Issue: https://github.com/w3c/w3process/issues/699
PR: https://github.com/w3c/w3process/pull/790

=== Editorial PRs to Review ===

Clarify what TAG+AB “approval” means:
Issue: https://github.com/w3c/w3process/issues/741
PR: https://github.com/w3c/w3process/pull/788

Clarify that registering an FO triggers process to address it
Issue: https://github.com/w3c/w3process/issues/739
PR: https://github.com/w3c/w3process/pull/789

=== Issues to Discuss ===

Maybe, if we have time?

Clarifying disciplinary actions and appeals
https://github.com/w3c/w3process/issues/786

~fantasai

Received on Wednesday, 11 October 2023 01:24:43 UTC