Skip to content

Conversation

@frivoal
Copy link
Collaborator

@frivoal frivoal commented Apr 28, 2025

Based on feedback recently received.

This keeps things largely as they were, but reworks the text to be more explicit about a few things:

  • The Team is actually supposed to make a decision at the end of the refinement phase; de-facto abandonment is a way to handle accidentally forgetting to do so, not a valid deliberate choice
  • The Team has to announce (and give rationale) for its decisions
  • If the Team (accidentally) abandons a refinement by letting it expire, they can still issue a (different) decision when they notice, without having to start a whole new refinement.

Preview | Diff

@frivoal frivoal added Agenda+ Recommends to the Chairs that this issue or pull request be discussed at the next meeting Topic: Chartering labels Apr 28, 2025
Copy link
Contributor

@tantek tantek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. Added a minor rewording suggestion for readability and clarity. Editor's discretion to reject, incorporate, or iterate as preferred.

frivoal and others added 4 commits May 13, 2025 09:31
This keeps things largely as they were, but reworks the text to be more explicit about a few things: * The Team is actually supposed to make a decision at the end of the refinement phase; de-facto abandonment is a way to handle accidentally forgetting to do so, not a valid deliberate choice * The Team has to announced (and give rationale) for its decisions * If the Team (accidentally) abandons a refinement by letting it expire, they can still issue a (different) decision when they notice, without having to start a whole new refinement. Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Tantek Çelik <46418+tantek@users.noreply.github.com>
@frivoal frivoal force-pushed the refinemment-conclusion-tweaks branch from 2c03b21 to d0cbbc4 Compare May 13, 2025 00:31
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion and removed Agenda+ Recommends to the Chairs that this issue or pull request be discussed at the next meeting labels May 14, 2025
@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed Tweaks to how charter refinement concludes, and agreed to the following:

  • RESOLVED: Merge #1037 to refine conclusion of charter refinement ;)
The full IRC log of that discussion <fantasai> Subtopic: Tweaks to how charter refinement concludes
<fantasai> github: (
<fantasai> github: https://github.com//pull/1037
<fantasai> Lots of approvals already in GH
<fantasai> RESOLVED: Merge #1037 to refine conclusion of charter refinement ;)
@frivoal frivoal merged commit c13ed73 into w3c:main May 14, 2025
2 checks passed
@frivoal frivoal added this to the Process 2024/2025 milestone May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Topic: Chartering

8 participants