-
Notifications
You must be signed in to change notification settings - Fork 172
Give the Advisory Board a mission statement #1021
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
base: main
Are you sure you want to change the base?
Changes from all commits
1ec310e
6b4eee0
932d733
f4af86b
543fe67
d3c7420
06777d3
944302a
6890fdb
1b39671
ac8e110
af017e1
7b12155
c5dd87f
8b73b87
133bc57
7d674bb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -872,28 +872,34 @@ Advisory Board (AB)</h4> | |||||||||||||||||||||||||||||||||||
| <h5 id=ab-role> | ||||||||||||||||||||||||||||||||||||
| Role of the Advisory Board</h5> | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| The <dfn export lt="Advisory Board|AB">Advisory Board</dfn> provides ongoing guidance to the Team | ||||||||||||||||||||||||||||||||||||
| on issues of strategy, | ||||||||||||||||||||||||||||||||||||
| management, | ||||||||||||||||||||||||||||||||||||
| legal matters, | ||||||||||||||||||||||||||||||||||||
| process, | ||||||||||||||||||||||||||||||||||||
| and conflict resolution. | ||||||||||||||||||||||||||||||||||||
| The Advisory Board also serves the Members | ||||||||||||||||||||||||||||||||||||
| by tracking issues raised between Advisory Committee meetings, | ||||||||||||||||||||||||||||||||||||
| soliciting Member comments on such issues, | ||||||||||||||||||||||||||||||||||||
| and proposing actions to resolve these issues. | ||||||||||||||||||||||||||||||||||||
| The Advisory Board manages the <a href="#GAProcess">evolution of the Process Document</a>. | ||||||||||||||||||||||||||||||||||||
| As part of a [=W3C Council=], | ||||||||||||||||||||||||||||||||||||
| members of the [=Advisory Board=] hear and adjudicate on [=Submission Appeals=] | ||||||||||||||||||||||||||||||||||||
| and [=Formal Objections=]. | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| The [=Advisory Board=] is distinct from the [=Board of Directors=] | ||||||||||||||||||||||||||||||||||||
| and has no decision-making authority within W3C; | ||||||||||||||||||||||||||||||||||||
| its role is strictly advisory. | ||||||||||||||||||||||||||||||||||||
| The <dfn export lt="Advisory Board|AB">Advisory Board</dfn> | ||||||||||||||||||||||||||||||||||||
| is elected by the Membership to advance the effectiveness of W3C as a | ||||||||||||||||||||||||||||||||||||
| standards development organization (<abbr title="standards development organization">SDO</abbr>). | ||||||||||||||||||||||||||||||||||||
| The [=Advisory Board=]: | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| Note: While the [=AB=] as such does not have decision-making authority, | ||||||||||||||||||||||||||||||||||||
| its members do when sitting as part of a [=W3C Council=]. | ||||||||||||||||||||||||||||||||||||
| <ul> | ||||||||||||||||||||||||||||||||||||
| <li>Provides ongoing guidance to the Team | ||||||||||||||||||||||||||||||||||||
| on issues of strategy, | ||||||||||||||||||||||||||||||||||||
| management, | ||||||||||||||||||||||||||||||||||||
| legal matters, | ||||||||||||||||||||||||||||||||||||
| process, | ||||||||||||||||||||||||||||||||||||
| community engagement, | ||||||||||||||||||||||||||||||||||||
| and conflict resolution, | ||||||||||||||||||||||||||||||||||||
| that arise during the the work of the W3C community; | ||||||||||||||||||||||||||||||||||||
| <li>Serves the Members by | ||||||||||||||||||||||||||||||||||||
| tracking issues raised between Advisory Committee meetings, | ||||||||||||||||||||||||||||||||||||
| soliciting Member comments on such issues, | ||||||||||||||||||||||||||||||||||||
| and proposing actions to resolve these issues; | ||||||||||||||||||||||||||||||||||||
| <li>Owns the <a href="#GAProcess">Process Document</a>, | ||||||||||||||||||||||||||||||||||||
| which includes considering proposals, | ||||||||||||||||||||||||||||||||||||
| approving changes, | ||||||||||||||||||||||||||||||||||||
| and publishing new versions. | ||||||||||||||||||||||||||||||||||||
|
Comment on lines
+893
to
+896
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fair point @hober - I don't mind the idea of "owns the evolution" or "owns and steers the evolution", but it strikes me that in any Charter this would be described as a "Deliverable" of the group, hence:
Suggested change
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Suggested wording from the Process CG call
Suggested change
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the change in language helps the proposed text better align with section 10 which already describes the need to take the document to the AC for review and approval. I don't think we need to reiterate section 10 here.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. and section 10 is already linked to in the first line
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Right, thanks, I see that now, makes sense.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @hober @igarashi50 what do you think of this option? |
||||||||||||||||||||||||||||||||||||
| </ul> | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| Members of the [=AB=] also take part in [=W3C Councils=] | ||||||||||||||||||||||||||||||||||||
| to hear and adjudicate [=Formal Objections=] | ||||||||||||||||||||||||||||||||||||
| and [=Submission Appeals=]. | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| Details about the Advisory Board | ||||||||||||||||||||||||||||||||||||
| (e.g., the list of Advisory Board participants, | ||||||||||||||||||||||||||||||||||||
| mailing list information, and summaries of Advisory Board meetings) | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is quite right. The AB can't promulgate a new Process without the Membership's approval (via an AC vote). I think, instead, it's the Membership that owns the Process Document, and it's delegated the maintenance of it to the AB, subject to its review and ratification.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As its name indicates, the AB is an advisory body. For the sake of separation of powers, I believe it is better not to change this, even after becoming a Members Consortium.
While I think the @brentzundel proposal is reasonable, as a non-native English speaker, I feel that "owns " might be a bit too strong in this context. Though it would be acceptable to remove "owns and", I suggest the following:
Proposed wording:
owns and steers the evolution of the Process Document.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That works for me!