Give the Advisory Board a mission statement
Tries to tie together the various roles of the AB under a coherent mission statement, similar to the TAG.
Based on discussions captured in
- https://github.com/w3c/AB-memberonly/issues/248
- https://www.w3.org/2025/03/26-ABpurpose-minutes.html
- https://www.w3.org/2025/Talks/AC/ab-wendy-reid/slides.pdf
Those </li> may be optional. I do not feel that such optionality means they should always be left out. To my eye, they help keep the source coherently readable, which is important since that is where the document is edited. (So far as I'm aware, there's no user-focused editing tool for .bs documents that shows the rendered result along the way.)
About the optional </li> tags, I think this is an editorial question that should be left to the editor(s). More over, the editor(s) have documented their preference in this matter for the whole document: https://github.com/w3c/process/blob/main/index.bs#L21
The reason for electing an Advisory Board is to provide guidance to the Team in the areas indicated on behalf of the membership, i.e. without having to poll the entire membership. That serves the Team, in enabling them to have regular input, and the members in enabling them not to have to give it as a body so often.
I think it would be helpful if that were clarified in working out this PR.
The reason for electing an Advisory Board is to provide guidance to the Team in the areas indicated on behalf of the membership, i.e. without having to poll the entire membership.
That's no longer always the case since 2023.
- the AB acts as the Working Group to revise the W3C Process, and related documents. It is no longer guiding the Team on how to revise the Process.
- the AB is part of W3C Councils, where Team and W3C decisions can be affirmed or overturned.
So, with the exception of those 2 cases, the AB only has a guidance role, per Process 2025.