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

Open
martinthomson opened this issue Dec 18, 2023 · 0 comments
Open

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

martinthomson opened this issue Dec 18, 2023 · 0 comments
Labels
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Director-free: TAG Appointments Issues related to appointing TAG members in a director-free W3C
Projects
None yet
Development

No branches or pull requests

2 participants