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

Are TAG Appointments mandatory for the Team to fill? #811

Closed
martinthomson opened this issue Dec 18, 2023 · 2 comments
Closed

Are TAG Appointments mandatory for the Team to fill? #811

martinthomson opened this issue Dec 18, 2023 · 2 comments
Labels
Closed: Question answered Used when the discussion has reached a conclusion, but wasn't an actual issue against the Process. Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice Director-free: TAG Appointments Issues related to appointing TAG members in a director-free W3C

Comments

@martinthomson
Copy link
Member

In #810, it seems like there is some lack of clarity about whether the Team is required to appoint TAG members or whether they are simply given the option of doing so (and maybe encouraged to do it).

(Most of the text below is from this section of the current process document.)

The case for a mandatory appointment is made implicitly, with statements like this one:

The TAG consists of [...] Three participants appointed by the Team;

And

The Team is responsible for appointing 3 of the participants to the Technical Architecture Group.

And this one in this later section:

When an appointed TAG seat is vacated, the Team appoints a replacement.

That all seems unequivocal, if not a direct requirement, but then there are statements like:

The Team should actively seek candidates for appointment to the TAG, [...]

And maybe even subtle nods like:

The Team's choice of appointee(s)

Though that last one might just be in recognition of the staggered nature of appointments, noting that some years the Team will only have a single appointment to make.

@fantasai
Copy link
Collaborator

fantasai commented Dec 6, 2024

My understanding of the Process is that is mandatory to appoint, and the phrasing supports this as you note. Regarding the ones you're unsure of:

The Team should actively seek candidates for appointment to the TAG

This recommendation is about the Team actively looking for candidates, not just passively taking nominations.

The Team's choice of appointee(s)

As you note, this optional pluralization is about the staggered number of appointees; not about whether the Team gets to choose how many.

@frivoal frivoal added the Closed: Question answered Used when the discussion has reached a conclusion, but wasn't an actual issue against the Process. label Dec 6, 2024
@frivoal frivoal added this to the Process 2024/2025 milestone Dec 6, 2024
@plehegar
Copy link
Member

Unless there is new information by December 20, this issue will get closed.

@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice and removed Commenter Response Pending Proposed to close Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion labels Dec 23, 2024
@frivoal frivoal closed this as completed Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Question answered Used when the discussion has reached a conclusion, but wasn't an actual issue against the Process. Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice Director-free: TAG Appointments Issues related to appointing TAG members in a director-free W3C
Projects
None yet
Development

No branches or pull requests

4 participants