Skip to content

AB Role in TAG Appointment #810

Description

@martinthomson

Decisions about TAG appointments are currently ratified by a two-thirds majority of both the TAG and the AB. I do not see a reason for the AB to be involved in this decision at that level.

For boards and groups operating at the level of the TAG, an appointment process is a good way to ensure that there is sufficient diversity of members available. Particularly when elections are used to fill seats, the process of filling seats can leave gaps in expertise or other qualities that would diminish the capacity of the group to function effectively.

A more regular process would be to give the group itself the ability to fill a small number of positions. For some reason, the W3C process gives this responsibility to the Team. That is somewhat irregular, but not really the subject of this issue.

The decision by the Team then needs to be approved by the TAG with a two-thirds majority, which is entirely appropriate. If the TAG believes that they cannot work with an appointed person, or the appointments do not address a diversity shortfall, then the TAG needs to be able to have a say.

The AB is given the same approval power, something that seems poorly justified. Obviously, the AB and TAG frequently work together, but while the two functions are complementary, the AB has no significant stake in the composition of the TAG or the technical work that the TAG does. The function of the AB is to advise the team, yes, but that is generally limited to procedural and operational matters.

Giving the AB input into TAG appointments at the same level as the TAG is unnecessary. I see no substantive reason that the AB needs a role that is significantly greater than any other consortium member.

If the goal of having the AB vote on appointments is to provide better accountability to the members of the organization, the formal objection process is a more appropriate way to ensure that membership has a way to object to particular appointments. That option is available to the AB just like any community member.

I propose that the process be amended to remove the AB from this process.

Metadata

Metadata

Assignees

No one assigned

    Labels

    AB DecisionClosing this issue was done with an explicit AB decisionClosed: AcceptedThe issue has been addressed, though not necessarily based on the initial suggestionTAG AppointmentsIssues related to appointing TAG members

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions