Proposal for Issue Process

["Murray, Bryan P." <bryan.murray@hp.com>]

In order to have the TC driven by issues we need a process which allows
any member to easily add a new issues to the issues list and a process
to resolve these issues. I propose the following process for handling
issues.

1) Any TC member can propose a new issue. This is done by sending email
to the list where the subject is "Issue: <title of issue>". The title of
the issue should be a short reminder of what the issue is about. The
body of the message should contain a description of the issue in detail
and if possible a proposed resolution. Updates to existing issues can be
done in the same way, just make sure the body of the message indicates
it is an update and include the issue number. The person sending the
email will be listed as the contact, unless noted otherwise in the
message.

2) The issues secretary will collect all new issues since the last TC
meeting as proposed issues. This list will be reviewed at the next TC
meeting so the TC can accept or reject the addition of the issue to the
issues list. Updates to issues should similarly be approved by the TC.

3) The issues secretary will post the entire issues list (including
those proposed) to the TC site 2 business days before the next TC
meeting. The document will have change tracking turned on so all changes
since the last TC meeting can easily be noted. All changes will be
accepted after the TC meeting as agreed by the members.

4) Issues on the list will have one of the following values for Status:
	- Proposed: the issue has been proposed but not yet accepted
	- Open: the issue has been accepted and is still pending
resolution by the TC
	- Resolved: The TC has decided and accepted a resolution, but
the actions are still pending
	- Closed: The issue has been resolved and is reflected in the
work products of the TC
Issues that have been closed will be shaded in the issues document to
obviously mark completed issues.

5) An issue is added to the list with a status of Proposed. It moves to
Open by agreement of the TC. If the TC chooses not to accept the issue
it will be removed from the list. An issue moves from Open to Resolved
after discussion and agreement of a resolution of the TC. A resolver
field will be assigned to the issue with the name of the person
responsible for the changes. Once the resolver has made the changes and
they are reflected in documents on the TC site the resolver sends a
message to the list indicating the issue is now closed.


We will discuss this process at the next TC meeting.

Bryan