Skip to content

Commit

Permalink
Forbid the Team from AB/TAG service
Browse files Browse the repository at this point in the history
The Team already has a clearly defined role in the process.
Being responsible for appointments to the TAG, for instance,
would make service on the TAG a bit of a conflict.
Another example is the role of the Team in Councils,
for which clearer rules would be clarifying.

I believe that this was a bit of a problem in the distant past,
but during my involvement with the organization,
this has never come up.
This is offered as a clarification,
not as a reaction to a particular situation.

This is part 2 of the recommendations in w3c#921.
  • Loading branch information
martinthomson committed Oct 8, 2024
1 parent c165854 commit 2f862fb
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -1119,6 +1119,11 @@ Elected Groups Participation Constraints</h5>
to choose one person for continued participation and declare the other seat(s) vacant.
<li>
An individual <em class="rfc2119">must not</em> participate on both the TAG and the AB.
<li>
Members of the [=Team=] <em class=rfc2119>must not</em> participate on the AB or TAG,
except as defined by this process.
In particular, the role of Team Contact is defined for both
[[#ABParticipation|AB]] and [[#tag-participation|TAG]].
</ul>

<h5 id="AB-TAG-elections">
Expand Down

0 comments on commit 2f862fb

Please sign in to comment.