Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

a role should be a role, not a task #615

Closed
TallTed opened this issue Aug 2, 2022 · 2 comments
Closed

a role should be a role, not a task #615

TallTed opened this issue Aug 2, 2022 · 2 comments

Comments

@TallTed
Copy link
Member

TallTed commented Aug 2, 2022

Originally posted by @TallTed in #614 (comment)

Lines 1958-1959 of index.bs currently read something close to —

	Note: The Director and CEO have the role of
	assessing consensus within the Advisory Committee.

— or —

	Note: The Director, COO, and CEO have the role of
	assessing consensus within the Advisory Committee.

COO is probably being removed from that text, via an issue-less PR from @tantek, which brought me to notice that the rest of that sentence doesn't quite agree with itself.

As I said there, I think that have the role of assessing consensus should be either have the role of consensus assessor or perform the task of assessing consensus, because as it stands, the role they have is not a role, but a task, which makes little sense.

@tantek wanted to keep that PR-without-an-issue focused on the deletion of COO, so I'm creating a new issue for discussion of the rephrasing I feel was and will remain necessary, regardless of PR #614's fate.

@TallTed TallTed changed the title As long as this is being massaged, have the role of assessing consensus should become either have the role of consensus assessor or perform the task of assessing consensus ... or something requiring a bit more bikeshedding. a role should be a role, not a task Aug 2, 2022
@frivoal frivoal added this to the Deferred milestone Jan 11, 2023
@frivoal
Copy link
Collaborator

frivoal commented Apr 19, 2024

I would suggest removing that note altogether. Assessing consensus of the AC through AC Reviews is well defined, and does not rely singularly on the CEO. More over, I don't believe we really have any process that relies on assessing the consensus of the AC other than through AC Reviews.

@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Apr 19, 2024
frivoal added a commit to frivoal/w3process that referenced this issue May 21, 2024
Assessing the consensus of the AC in AC reviews is overseen by the Team
as a whole, not by the CEO singularly. Assessing the consensus of the AC
outside of an AC Review is not something any of our processes depend on,
so discussing who is responsible for it is unnecessary (and the phrasing
is clumsy anyway).

See w3c#615
@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed #875, and agreed to the following:

  • ACTION: plh to check with the CEO
The full IRC log of that discussion <plh> subtopic: #875
<plh> Github: https://github.com//pull/615
<plh> --> https://github.com//pull/875/files Remove note about AC consensus assessment
<plh> Florian: outside of AV review, we don't have a process
<plh> ... so having a note saying that the CEO does it seems confusing/unecessary
<plh> plh: I'd like to get feedback from Seth
<plh> ACTION: plh to check with the CEO
<plh> Florian: can we agree to do this unless Seth says anything?
<plh> plh: sure
<plh> Resolved: unless we receive a comment from the CEO, this will get merged

frivoal added a commit that referenced this issue Jun 12, 2024
Assessing the consensus of the AC in AC reviews is overseen by the Team
as a whole, not by the CEO singularly. Assessing the consensus of the AC
outside of an AC Review is not something any of our processes depend on,
so discussing who is responsible for it is unnecessary (and the phrasing
is clumsy anyway).

See #615
@frivoal frivoal removed Agenda+ Marks issues that are ready for discussion on the call Proposed to close labels Aug 20, 2024
@frivoal frivoal modified the milestones: Deferred, Process 2024/2025 Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants