-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathrole.html
162 lines (158 loc) · 8.07 KB
/
role.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Role of the Team Contact</title>
<link rel="stylesheet" type="text/css" href="../assets/main.css">
<!-- $Id: staff-contact.html,v 1.27 2017/01/04 19:17:00 plehegar Exp $ -->
<!-- Changed by: Ian B. Jacobs, 9-Jul-1998 -->
</head>
<body lang="en" xml:lang="en">
<a href=".." title="W3C Home"><img src="/Icons/WWW/w3c_home" alt=
"W3C"></a> . <a href="/Guide/">Art of Consensus Guide</a>
<h1>Role of the Team Contact</h1>
<p><em>Note:</em> W3C designates a Team Contact to monitor the progress of
every <a href="../Project/Submission">Submission request</a>
and to write a Team Comment which is published as part of the Submission.
This document, however, discusses the Team Contact of a Working Group, rather than the Team Contact for a Submission.</p>
<p>W3C designates a Team Contact ("Contact") for every W3C Working
Group and Interest Group ("Group"). The Contact helps set the strategic
direction of the Group in the chartering phase. Many
of the Contact's tasks involve helping the Chair
complete his or her <a href="chair-roles.html">roles</a>,
such as ensuring that the group runs smoothly, actively aiding consensus building, ensuring wide review of specifications, tracking feedback from implementors, and so forth. The Team Contact reports to the Project Lead.</p>
<h2>Technical coordination</h2>
<p>Coordination and communication is a primary role for the Team Contact,
who acts as the
interface between the Group Chair ("Chair"), Group Members, other Working Groups,
and the W3C Team:</p>
<blockquote><p>The team contact role is largely one of communication. This
involves becoming as aware as possible of the technical
requirements and issues in the group, and simultaneously being
aware of the general <a href="/TR/webarch">architecture of the Web</a>
as evolving in the
other work of W3C. This is of course a general responsibility of
the group - and the chair and group members have this duty too. The
staff contact has the benefit of being employed full time in W3C,
and having access to other team members. The team contact's
existence does not dilute in any way the group's obligation to
ensure the technology interoperates with that of other groups.
[<em>TimBL 2001-09-11</em>]</p></blockquote>
<p>The Team Contact is also charged with representing the views of the Team to the Working group. Just as all Members do not have the same views, neither does all the Team. The Team Contact collects the various viewpoints and summarizes them so that the Working Group benefits from the widest range of inputs. Where the Team does not have a single position, it is inappropriate to merely abstain. Instead, the various points of view should be summarized.
For a good example of Team input where the Team did not have consensus,
see <a href="https://lists.w3.org/Archives/Public/public-html/2007Nov/0449.html">
Team response on the 'canvas' element</a>.</p>
<h2>Assist Group organizers in creating charter and convening
Group</h2>
<ul>
<li><i>Assist</i> in creating the group charter. When rechartering, discuss the proposed charter with the existing Working group and with the Team.
See also the <a href=
"https://w3c.github.io/charter-drafts/charter-template.html">charter template</a> and
<a href="https://github.com/w3c/strategy/issues?q=label:charter">ongoing charters</a>.</li>
<li>Act as the <a href="../process/charter.html#charter-shepherd">charter shepherd</a>.
If approved, the Team will
announce the creation of the group and ensures a call for
participation is announced.</li>
<li><i>Assist</i> the organizers in understanding dependencies on
other groups, and act as coordinator when necessary.</li>
<li><i>Ensure</i> that the Chair is familiar with key documents,
including:
<ul>
<li><a href="/policies/process/">The Process Document</a>
<ul>
<li><a href="/policies/process/#GAGeneral">General Information
about Groups</a></li>
<li><a href="/policies/process/#GroupsWG">Working
Groups</a></li>
<li><a href="/policies/process/#GroupsIG">Interest
Groups</a></li>
</ul>
</li>
<li><a href="../">The Art of Consensus</a>
<ul>
<li><a href="/pubrules">Pubrules</a></li>
<li><a href="/invited-experts/">W3C Invited Experts</a> principles and review requirements</li>
<li><a href="https://lists.w3.org/Archives/Member/chairs/">Archive
of [email protected]</a> (member-only)</li>
</ul>
<li><a href="/policies/code-of-conduct/">Code of Conduct</a></li>
<li><a href="/policies/antitrust/">Antitrust and competition policy</a></li>
</ul>
</li>
<li><i>Ensure</i> that Chair is marked as such (checkbox) in the <a href=
"/groups/">group's homepage</a> (which
subscribes him/her to <a href=
"mailto:[email protected]">[email protected]</a>)</li>
<li><i>Ensure</i> that Group Members are oriented to W3C process
and their roles when Group convenes or new Group Members join.</li>
<li><i>Ensure</i> that Group sets milestones for document
development, charter renewals, etc.</li>
<li><i>Ensure</i> that Chair understands the different stages of
document development (Editor's Drafts, Working Drafts,
Candidate Recommendation, Proposed Recommendations, Recommendations), and
confidentiality and status issues for each stage.</li>
<li><i>Assist</i> Chair in assessing need for charter renewal
and/or closing of the Group.</li>
<li><i>Ensure</i> that previous Chair is removed in the <a href=
"/groups/">group's homepage</a>.</li>
</ul>
<h2>Monitor group participation and operations</h2>
<ul>
<li>[<i>Active Role</i>] Monitor levels of active participation and
address as needed.</li>
<li><i>Ensure</i> that attendance and minutes are kept.</li>
<li><i>Ensure</i> that Chair is aware of any problems and report
these problems to W3M when they persist.</li>
<li><i>Assist</i> Chair in moderating disputes between
participants.</li>
<li><i>Ensure</i> that Group page is up-to-date</li>
<li><i>Assist</i> in reservations for phone bridge as needed</li>
<li><i>Ensure</i> sufficient advance notice of meetings by proper
channels</li>
<li><i>Ensure</i> agendas posted in timely fashion</li>
<li><i>Ensure</i> minutes posted in timely fashion</li>
</ul>
<h2>Serve as Contact with W3C Team</h2>
<ul>
<li>[<i>Active Role</i>] Keep the Communications Team and Project
lead informed of group events, face-to-face meetings, anticipated
publication dates, etc.</li>
<li>[<i>Active Role</i>] Identify host and coordinate with host to
organize logistics for face-to-face meetings, events, etc.</li>
<li><i>Assist</i> the Communications Team and Chair in soliciting
testimonials for press releases.</li>
<li>[<i>Active Role</i>] Work with Communications Team to draft
press releases and/or review for accuracy.</li>
<li>[<i>Active Role</i>] Coordinate the act of publishing documents
with the Communications and Sys/Web Teams.</li>
<li>[Active Role] Follow communications with other W3C groups and
functions to identify areas where coordination is needed.</li>
<li><i>Assist</i> Chair in coordinating with other W3C groups as
needed.</li>
<li><i>Ensure</i> liaisons between Group and other W3C groups are
assigned as needed.</li>
<li>[<i>Active Role</i>] Coordinate with the Systems Team to ensure
that Chair and group Editors have appropriate access to the W3C
site, and that their access works, e.g. GitHub.</li>
<li><i>Ensure</i> that Group editors understand how to use <a href="https://w3c.github.io/">GitHub at W3C</a>.</li>
<li><i>Ensure</i>, before publishing any Group document in W3C/TR
space, that it is:
<ol>
<li>Being published properly (see <a href=
"/pubrules">Pubrules</a>).</li>
<li>Spell-checked</li>
<li>HTML validated (see, for example, the <a href=
"http://validator.w3.org/">HTML validator service</a>).</li>
<li>CSS validated (see, for example, the <a href=
"http://jigsaw.w3.org/css-validator/">CSS validator</a>).</li>
<li>Accessible (see <a href="/WAI/eval/Overview.html">Accessibility evaluation resources</a>)</li>
<li>Published in the appropriate places, using Team conventions for
document status information, naming schemes, etc.</li>
</ol>
</li>
</ul>
<hr>
<p>Feedback is to <a href="https://github.com/orgs/w3c/teams/guidebook">@w3c/guidebook</a>
and is welcome on <a href="https://github.com/w3c/Guide/issues">GitHub</a></p>
</body>
</html>