issues-about
3.68 KB
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
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>TAG issue tracking policy</title>
<meta name="generator" content="amaya 5.3, see http://www.w3.org/Amaya/" />
<link href="style/default.css" rel="stylesheet" type="text/css" />
</head>
<body>
<h1><a href="http://www.w3.org/" title="W3C Home"><img alt="W3C" height="48"
src="http://www.w3.org/Icons/w3c_home" width="72" border="0" /></a> TAG issue
tracking policy</h1>
<map id="topnav">
<p><a href="#howto">how to raise an issue</a> · <a href="#manage">issue
management</a> </p>
</map>
<map id="nearbynav">
<p>Nearby: <a href="group/track/">issues list</a> · <a href=".">public TAG
home page</a> · <a
href="http://lists.w3.org/Archives/Public/www-tag/">www-tag@w3.org
archives</a></p>
</map>
<p>The section entitled "Issue Resolution" in the <a href="/2001/07/19-tag">TAG
charter</a> states:</p>
<blockquote>
<p>In addition to the production of Recommendations, the TAG will help
resolve technical issues having architectural impact. The process for issue
resolution is likely to evolve over time.</p>
</blockquote>
<p>The sections below describe TAG processes for addressing isues.
<strong>Note</strong>: These processes are in development as the TAG is just
getting underway.</p>
<h2><a name="howto">How to raise an issue with the TAG</a></h2>
<ul>
<li>Issues should be addressed to the TAG at <a
href="mailto:www-tag@w3.org">www-tag</a>. Please refer to <a
href="./#mail">information about using www-tag</a>.</li>
<li>Please review the <a
href="http://lists.w3.org/Archives/Public/www-tag/">www-tag@w3.org
archives</a> and the issues list before sending your issue to the TAG; it
may have already been discussed or resolved.</li>
<li>Please ask the TAG specific questions about Web architecture, rather than
requesting general review of documents. The TAG is more likely to answer
specific questions than to review large documents. The charter states: "The
TAG is not expected to review every document on the W3C Recommendation
track, only those that include Architectural Recommendations or that are
brought to the attention of the TAG." </li>
<li>In your request, please provide the following information:
<ul>
<li>Are there a set of apparent alternative solutions to this
architectural issue? The TAG encourages you to propose (alternative)
solutions as a starting point.</li>
<li>What are the use cases?</li>
</ul>
</li>
</ul>
<h2><a name="manage">TAG issue management</a></h2>
<p>The TAG manages issues as follows:</p>
<ol>
<li>When an issue is brought to the TAG, the TAG decides whether to accept
it. Whether accepted or rejected, the issue is assigned an identifier, and
the issue is "registered" via a message to www-tag from the TAG (ensuring
that person who raised the issue is also cc'd). Subsequent email concerning
this issue should use the issue identifier in the Subject line. The
definitive state of an issue should be determined by the messages about it
on www-tag.</li>
<li>When an issue is resolved, the TAG should explain how the resolution will
be manifest (e.g., a document update, an Architecture Recommendation,
etc.).</li>
<li>The TAG will facilitate issue tracking through one or more issues lists
(such as the current document).</li>
</ol>
<hr />
<address>
<a href="/People/Jacobs/">Ian Jacobs</a><br />
Last modified: $Date: 2011/03/09 14:10:53 $
</address>
</body>
</html>