Skip to content

Commit e5f7239

Browse files
Update links
1 parent d3c18b3 commit e5f7239

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

chair/role.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -3,23 +3,23 @@ title: W3C Working/Interest Group Chair
33
toc: true
44
---
55

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).
77

88
## Chair Buddy System
99

1010
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.
1111

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).
1313

1414
## Role of the Group Chair
1515

1616
### Creates Group charter and convenes Group
1717

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.*
2121
- 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.)
2323
- 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.
2424
- (If there is a Co-chair) Establishes clear and close coordination with Co-chair.
2525

@@ -39,8 +39,8 @@ Interested parties should subscribe to [[email protected]](mailto:chairbuddies
3939
- Judges items in or out of scope for the Group.
4040
- Generally stays neutral in discussion but can participate in technical discussions if announces in advance that will remove their chair "hat" at that time.
4141
- 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.
4444
- Announces calls, meetings, events with appropriate advance time and through proper channels.
4545
- Ensures minutes are taken and posted in due time.
4646
- Defines meeting agendas.
@@ -57,17 +57,17 @@ Interested parties should subscribe to [[email protected]](mailto:chairbuddies
5757
- Previous participation or technical contributions in related communities;
5858
- Ability to satisfy the time commitment (from you and/or your organization/management);
5959
- 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/);
6161
- Ability to keep the Working Group "in Charter", both for technical and IPR issues;
6262
- 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.
6363

6464
* * *
6565

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:
6767

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/)
6969
- where does it fit with other groups
7070
- testing, test suites ... generating tests as you come to each
7171
- responsibility not just to the group -- working toward consensus of the whole community
7272
- 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

Comments
 (0)