You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: chair/role.md
+12-12Lines changed: 12 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -3,23 +3,23 @@ title: W3C Working/Interest Group Chair
3
3
toc: true
4
4
---
5
5
6
-
The [W3C Team](https://www.w3.org/Process#ref-for-team%E2%91%A2%E2%91%A6) appoints (or re-appoints) a Chair (or more than one co-Chair) for every Working Group and Interest Group ("Group"). The Chair's primary role is to facilitate [consensus](/policies/process/#Consensus)-building among Group members. The Chair works together with the W3C [Staff Contact](../teamcontact/role.html). Key roles of the Group Chair are listed below. Additional information on the role of the Group Chair is in the [W3C Process Document](/policies/process/#general-requirements).
6
+
The [W3C Team](https://www.w3.org/policies/process/#ref-for-team%E2%91%A2%E2%91%A6) appoints (or re-appoints) a Chair (or more than one co-Chair) for every Working Group and Interest Group ("Group"). The Chair's primary role is to facilitate [consensus](https://www.w3.org/policies/process/#Consensus)-building among Group members. The Chair works together with the W3C [Staff Contact](../teamcontact/role.md). Key roles of the Group Chair are listed below. Additional information on the role of the Group Chair is in the [W3C Process Document](https://www.w3.org/policies/process/#general-requirements).
7
7
8
8
## Chair Buddy System
9
9
10
10
The [Working Group effectiveness Task Force](https://github.com/w3c/wg-effectiveness) helped establish a Chair Buddy System by which experienced buddy-mentors help buddy-mentees.
11
11
12
-
Interested parties should subscribe to [[email protected]](mailto:[email protected]) ([Member-only archive](https://lists.w3.org/Archives/Member/member-chairbuddies/)) and visit the dedicated [Chair Buddy System page](buddy.html).
12
+
Interested parties should visit the dedicated [Chair Buddy System page](buddy.md).
13
13
14
14
## Role of the Group Chair
15
15
16
16
### Creates Group charter and convenes Group
17
17
18
-
-[Develops Group charter](/policies/process/#WGCharterDevelopment) together with the Staff Contact.
19
-
- Is familiar with the [W3C Process](/policies/process/), the [W3C Code of Conduct](/policies/code-of-conduct/), the [Antitrust and competition policy](/policies/antitrust/), and [Guidebook](/Guide).
20
-
- Convenes Group and ensures Group members oriented to [W3C Process](/policies/process/)*with assistance of Staff Contact.*
18
+
-[Develops Group charter](https://www.w3.org/policies/process/#WGCharterDevelopment) together with the Staff Contact.
19
+
- Is familiar with the [W3C Process](https://www.w3.org/policies/process/), the [W3C Code of Conduct](https://www.w3.org/policies/code-of-conduct/), the [Antitrust and competition policy](https://www.w3.org/policies/antitrust/), and [Guidebook](..).
20
+
- Convenes Group and ensures Group members oriented to [W3C Process](https://www.w3.org/policies/process/)*with assistance of Staff Contact.*
21
21
- Schedules deliverables and sets milestones towards completion of deliverables.
22
-
- Appoints document editors. (NOTE: [Editors](https://www.w3.org/2003/Editors/) are responsible for ensuring that Group decisions are correctly reflected in Group documents, and for maintaining an issue list.)
22
+
- Appoints document editors. (NOTE: [Editors](../editor/) are responsible for ensuring that Group decisions are correctly reflected in Group documents, and for maintaining an issue list.)
23
23
- Proposes invited experts *with assistance of Staff Contact* (W3C staff must be involved in decisions regarding inclusion/exclusion of participants). Makes sure that all participants have filled out a call for participation and have disclosed their IPR in accordance with W3C process.
24
24
- (If there is a Co-chair) Establishes clear and close coordination with Co-chair.
25
25
@@ -39,8 +39,8 @@ Interested parties should subscribe to [[email protected]](mailto:chairbuddies
39
39
- Judges items in or out of scope for the Group.
40
40
- Generally stays neutral in discussion but can participate in technical discussions if announces in advance that will remove their chair "hat" at that time.
41
41
- Keeps Group's charter compliant with W3C Process, and initiates charter update as needed.
42
-
- Ensures participants abide by the terms and spirit of the [W3C Code of Conduct](/policies/code-of-conduct/)
43
-
- Find suitable time slots for distributed meeting where most of the attendees are expected to participate from remote locations (e.g., by telephone, video conferencing, or IRC). (see also [Organizing a distributed meeting](../meetings/organize.html) ) and revisit those time slots on a regular basis.
42
+
- Ensures participants abide by the terms and spirit of the [W3C Code of Conduct](https://www.w3.org/policies/code-of-conduct/)
43
+
- Find suitable time slots for distributed meeting where most of the attendees are expected to participate from remote locations (e.g., by telephone, video conferencing, or IRC). (see also [Organizing a distributed meeting](../meetings/organize.md) ) and revisit those time slots on a regular basis.
44
44
- Announces calls, meetings, events with appropriate advance time and through proper channels.
45
45
- Ensures minutes are taken and posted in due time.
46
46
- Defines meeting agendas.
@@ -57,17 +57,17 @@ Interested parties should subscribe to [[email protected]](mailto:chairbuddies
57
57
- Previous participation or technical contributions in related communities;
58
58
- Ability to satisfy the time commitment (from you and/or your organization/management);
59
59
- Familiarity or willingness to learn W3C Process and document formatting rules;
60
-
- Familiarity with the [W3C Code of Conduct](/policies/code-of-conduct/);
60
+
- Familiarity with the [W3C Code of Conduct](https://www.w3.org/policies/code-of-conduct/);
61
61
- Ability to keep the Working Group "in Charter", both for technical and IPR issues;
62
62
- Ability (both actual and perceived by the Working Group -- including potential competitors) to forge consensus fairly and without bias from your affiliation/employer and, sometimes, even your own technical positions.
63
63
64
64
* * *
65
65
66
-
The team contact should arrange for the Chair and the [W3C Team](https://www.w3.org/Process#ref-for-team%E2%91%A2%E2%91%A6) to meet (by phone if necessary) to make sure they're on the same wavelength about things like:
66
+
The Team contact should arrange for the Chair and the [W3C Team](https://www.w3.org/policies/process/#ref-for-team%E2%91%A2%E2%91%A6) to meet (by phone if necessary) to make sure they're on the same wavelength about things like:
67
67
68
-
- where the group's work fits into [Web Architecture](/TR/webarch/)
68
+
- where the group's work fits into [Web Architecture](https://www.w3.org/TR/webarch/)
69
69
- where does it fit with other groups
70
70
- testing, test suites ... generating tests as you come to each
71
71
- responsibility not just to the group -- working toward consensus of the whole community
72
72
- cost of delaying wider consensus - negotiating your reviews and really getting in touch with people - versus time to market and specification relevance
73
-
- formal objections, i.e. the tricky bits of W3C process
73
+
- formal objections, i.e. the tricky bits of W3C process
0 commit comments