Give the Advisory Board a mission statement #1021
Conversation
fantasai
force-pushed
the
ab-mission-scope
branch
from
367e9ce to
4f5b430
Compare
Tries to tie together the various roles under a mission statement and organizes the roles as bullet points, similar to the TAG. Based on discussions captured in w3c/AB-memberonly#248 https://www.w3.org/2025/03/26-ABpurpose-minutes.html https://www.w3.org/2025/Talks/AC/ab-wendy-reid/slides.pdf
fantasai
force-pushed
the
ab-mission-scope
branch
from
4f5b430 to
1ec310e
Compare
| As part of a [=W3C Council=], | ||
| members of the [=Advisory Board=] hear and adjudicate on [=Submission Appeals=] | ||
| and [=Formal Objections=]. | ||
| <li>Managing the <a href="#GAProcess">evolution of the Process Document</a>. |
There was a problem hiding this comment.
I thought the role was stronger than this with respect to the process?
There was a problem hiding this comment.
| <li>Managing the <a href="#GAProcess">evolution of the Process Document</a>. | |
| <li>Managing the <a href="#GAProcess">evolution of the Process Document</a>.</li> |
| Note: While the [=AB=] as such does not have decision-making authority, | ||
| its members do when sitting as part of a [=W3C Council=]. | ||
| However, as part of a [=W3C Council=], | ||
| members of the [=Advisory Board=] hear and adjudicate on [=Submission Appeals=] |
There was a problem hiding this comment.
| members of the [=Advisory Board=] hear and adjudicate on [=Submission Appeals=] | |
| members of the [=Advisory Board=] hear and adjudicate [=Submission Appeals=] |
| on issues of strategy, | ||
| management, | ||
| legal matters, | ||
| process, | ||
| community engagement, | ||
| and conflict resolution. |
There was a problem hiding this comment.
| and conflict resolution. | |
| and conflict resolution.</li> |
There was a problem hiding this comment.
That's unnecessary. <li> is a self-closing tag.
| and conflict resolution. | ||
| The Advisory Board also serves the Members | ||
| <li>Serving the Members | ||
| by tracking issues raised between Advisory Committee meetings, | ||
| soliciting Member comments on such issues, | ||
| and proposing actions to resolve these issues. |
There was a problem hiding this comment.
| and proposing actions to resolve these issues. | |
| and proposing actions to resolve these issues.</li> |
There was a problem hiding this comment.
That's unnecessary. <li> is a self-closing tag.
|
Those |
|
|
||
| The [=Advisory Board=] is distinct from the [=Board of Directors=] | ||
| and has no decision-making authority within W3C; | ||
| and has no decision-making authority over W3C; | ||
| its role is strictly advisory. |
There was a problem hiding this comment.
| its role is strictly advisory. |
Given the AB's role in managing the Process document (and now also The Vision, and facilitating the Code of Conduct, which can be a separate PR), and FO Councils, it's high time to remove this legacy phrase which causes more confusion than clarity in practice.
|
|
||
| The [=Advisory Board=] is distinct from the [=Board of Directors=] | ||
| and has no decision-making authority within W3C; | ||
| and has no decision-making authority over W3C; |
There was a problem hiding this comment.
| and has no decision-making authority over W3C; | |
| and has no decision-making authority over W3C. |
Punctuation consistent with the prior suggestion.
Tries to tie together the various roles of the AB under a coherent mission statement, similar to the TAG.
Based on discussions captured in