TAG issue tracking policy
The section entitled "Issue Resolution" in the TAG charter states:
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.
The sections below describe TAG processes for addressing isues.
Note: These processes are in development as the
TAG is just getting underway.
- Issues should be addressed to the TAG at www-tag. Please refer
to information about using www-tag.
- Please review the www-tag@w3.org
archives and the issues list before sending your issue to the
TAG; it may have already been discussed or resolved.
- 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."
- In your request, please provide the following information:
- Are there a set of apparent alternative solutions to this
architectural issue? The TAG encourages you to propose
(alternative) solutions as a starting point.
- What are the use cases?
The TAG manages issues as follows:
- 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.
- When an issue is resolved, the TAG should explain how the
resolution will be manifest (e.g., a document update, an
Architecture Recommendation, etc.).
- The TAG will facilitate issue tracking through one or more
issues lists (such as the current document).
Ian Jacobs
Last modified: $Date: 2005/03/21 12:19:54 $