8000 Limit the involvement of Tim Berners-Lee to the TAG proper by frivoal · Pull Request #792 · w3c/process · GitHub
[go: up one dir, main page]

Skip to content

Conversation

frivoal
Copy link
Collaborator
@frivoal frivoal commented Oct 12, 2023

As the Council's purpose is to replace his former role as Director in resolving Formal Objections, this removes him from being part of the Council. This way, he does not take part in the Council's deliberations, and is not on the critical path for Council votes or quorum questions, notably the Council's Unanimous Short Circuit.

This is one possible solution to #784, with #791 and #793 being alternatives.


Preview | Diff

@frivoal frivoal added FO/Council Issues related to the W3C Council and Formal Objection Handling Director-free (all) All issues & pull request related to director-free. See also the topic-branch labels Oct 12, 2023
As the Council's purpose is to replace his former role as Director in
resolving Formal Objections, this removes him from being part of the
Council. This way, he does not take part in the Council's deliberations,
and is not on the critical path for Council votes or quorum questions,
notably the Council's Unanimous Short Circuit.

See w3c#784
@frivoal frivoal changed the title Limit the involvement of Tim Berners Lee to the TAG proper Limit the involvement of Tim Berners-Lee to the TAG proper Oct 12, 2023
Co-authored-by: chaals <chaals@users.noreply.github.com>
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.

@frivoal's change LGTM. No need to make any dependency on other PRs.

Copy link
Member
@hober hober left a comment

Choose a reason for hiding this comment

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

I'd prefer wording that doesn't get personal; see my suggestion.

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.

Approve with @hober's suggested edits. Tess's version also has the benefit of not adding a new explicit reference to Tim by name in the Process.

Co-authored-by: Theresa O'Connor <hober0@gmail.com>
Copy link
@torgo torgo left a comment

Choose a reason for hiding this comment

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

this is my preferred approach

@torgo
Copy link
torgo commented Dec 16, 2024

In addition to my positive review, just recording here that the TAG discussed in breakout (and async, in chat) and the upshot is that the TAG supports this PR.

@frivoal frivoal added the Agenda+ Marks issues or pull requests that are ready for discussion or consideration at the next meeting label Dec 23, 2024
@frivoal
8000
Copy link
Collaborator Author
frivoal commented Dec 23, 2024

Agenda+ to propose adopting this based on the TAG's recommendation.

@frivoal
Copy link
Collaborator Author
frivoal commented Jan 16, 2025

AB Resolution:

RESOLUTION: Adopt the proposed text in Process PR #792, as recommended by the TAG.

@frivoal frivoal merged commit 524b216 into w3c:main Jan 16, 2025
@frivoal frivoal deleted the timbl-B branch January 16, 2025 12:52
@frivoal frivoal added this to the Process 2024/2025 milestone May 19, 2025
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion AB Decision Closing this issue was done with an explicit AB decision and removed Agenda+ Marks issues or pull requests that are ready for discussion or consideration at the next meeting P2025 candidate labels May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AB Decision Closing this issue was done with an explicit AB decision Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Director-free (all) All issues & pull request related to director-free. See also the topic-branch FO/Council Issues related to the W3C Council and Formal Objection Handling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants
0