Skip to content

Tweak definition of AC Rep Alternates. Fixes #1165.#1166

Merged
brentzundel merged 4 commits into
w3c:mainfrom
hober:alternate-power
Jun 24, 2026
Merged

Tweak definition of AC Rep Alternates. Fixes #1165.#1166
brentzundel merged 4 commits into
w3c:mainfrom
hober:alternate-power

Conversation

@hober

@hober hober commented Jun 10, 2026

Copy link
Copy Markdown
Member

@hober

hober commented Jun 10, 2026

Copy link
Copy Markdown
Member Author

Or maybe we should use this opportunity to just generally rework this sentence, maybe something like:

Each AC representative may designate an alternate,
who may exercise all of the rights and responsibilities of AC representatives,
except the ability to designate an alternate.

or:

Member organizations may also designate an alternate AC representative,
who may exercise all of the rights and responsibilities of AC representatives.

or:

Member organizations may also designate an alternate AC representative,
who exercise all of the rights and responsibilities of AC representatives
when the AC representative is unavailable.

Personally, while I think the original sentence is a bit awkward as currently phrased, I'd prefer the more surgical approach of this PR to something more ambitious.

@frivoal

frivoal commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

I think my favorite might be

Each AC representative may designate an alternate,
who may exercise all of the rights and responsibilities of AC representatives,
except the ability to designate an alternate.

Though maybe I'd tweak it so:

Each AC representative may designate an alternate,
who may concurrently exercise all of the rights and responsibilities of AC representatives,
except the ability to designate an alternate.

The original PR is fine too, though.

My least favorite is the last suggestion, since it implies the only valid us of an alternate is to stand in for the main rep when the main rep is absent. That's fine, but that's not the only thing alts can be used for. You could also do a division of labor, when one handles charters, PAGs, and exclusion opportunities, and the other handles the rest, or whatever makes sense for that particular set of people.

@css-meeting-bot

Copy link
Copy Markdown
Member

The Revising W3C Process CG just discussed https://github.com/w3c/process/pull/1166.

The full IRC log of that discussion <brent> subtopic: https://github.com//pull/1166
<brent> Github: https://github.com//pull/1166

Comment thread index.bs Outdated
Comment thread index.bs Outdated
Co-authored-by: Florian Rivoal <git@florian.rivoal.net>
@css-meeting-bot

Copy link
Copy Markdown
Member

The Revising W3C Process CG just discussed https://github.com/w3c/process/pull/1166.

The full IRC log of that discussion <brent> subtopic: https://github.com//pull/1166
<brent> Github: https://github.com//pull/1166
<Ian> s/merge this/merge 1166/
<Ian> Hober: I think that "any of" suggests overly strongly that distinct roles are backed up by tooling.
<Ian> ...I don't think the process should imply that division of labor is backed up by tooling.
<Ian> q+
<Ian> ack me
<Ian> Ian: Is the implication that only one person holds powers at a given moment?
<Ian> Brent: I think one can undelegate at any time.
<Ian> Hober: Tooling allows both to do anything at any time.
<Ian> Ian: would "Share" work?
<Ian> Hober: I don't hate that.
<Ian> Florian: Ok with Share
<Ian> Francois: Should we change "Delegate" elsewhere?
<Ian> (Support for "Share" in this context; postpone discussion of "share" elsewhere)
<Ian> Brent: I am hearing "share" may be clearer in 1166, and we can add more delegates later if there's more demand.
<Ian> (Growing support for not changing delegate to share around CEO roles)
<Ian> Proposed: Adopt 1116 changing "delegate" to "share"
<RRSAgent> I have made the request to generate https://www.w3.org/2026/06/24-w3process-minutes.html Ian

@brentzundel brentzundel merged commit b604518 into w3c:main Jun 24, 2026
2 checks passed
@frivoal frivoal added Type: Editorial improvements Editorial improvements or errors that do not affect interpretation of the document Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion labels Jun 24, 2026
@frivoal frivoal added this to the Process Next milestone Jun 24, 2026

@nhoyas-max nhoyas-max left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Approved

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 Type: Editorial improvements Editorial improvements or errors that do not affect interpretation of the document

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants