Tsc issue review process

The following is the stawman process provided by Karen for discussion on the call 15/10/07 -- it does not reflect changes agreed since them

Assumptions:

1. The submission/tracking process will be manual at least until the new web site is launched. At that time, the TSC will access the tools available for issues tracking and select the tools that best meets their needs. Consideration should be given to the following tools:
   1. GForge
   2. MOSS (Microsoft Office SharePoint Server) – this is the platform for the new web site. It provides issue tracking (can be exported to Excel)
   3. Wiki
   4. Other as identified by TSC
2. All issues will be submitted via the issues submission procedure, regardless of whether they come directly from a member or up through the SIG/TC and Steering Division.

Process:

1. Submitter submits issue through TSCissues@lists.hl7.org currently or through selected tool in the future. Additional files such as mission/charter for new SIGs or project proposals can be submitted with the issue.
2. HQ logs the issue, ensuring all fields on the submission form have been entered, follows up with submitter should information be missing (i.e. ,mission/charter statement, etc).
3. The status of the issue is automatically set to Submitted. This alerts the TSC that the issue has not been discussed.
4. HQ and TSC Chair/CTO will meet weekly to triage issues and determine which shall be discussed on the next call.
5. TSC discussion will result in the following:
   1. Change to status. Status codes and their meanings are as follows:
      1. Submitted – the issue has been logged but not discussed
      2. Approved – the issues has been logged and discussed by the TSC, and is being worked on.
      3. Approved/Transferred – the issues has been discussed by the TSC and transferred to another body (e.g., ARB, MnM, SD, CTO, etc).
      4. Completed – the body to which the issues was referred has responded and the issue is ready for review by the TSC.
      5. Closed/Rejected – the issue was reviewed and rejected by the TSC (as in the case of creating a new TC/SIG or request for out-of-cycle ballot).
      6. Closed/Duplicate – the issue was reviewed by the TSC and closed as it is a duplicate issue.
      7. Closed – the TSC has discussed, resolved, and closed the issue.
   2. Assignment of TSC Steward –all issues will be assigned to a TSC steward. This TSC member keeps the issue moving forward toward resolution and will be responsible for communication of issue resolution to submitter. He/she may need to be work with others (i.e., committee, individual or other body to whom the issue has been transferred) to bring the issue to closure.
6. TSC resolves the issue, which results in the following:
   1. Capture of resolution – issues whose status is CR, CD or CC are required to have documented resolution. Resolution should state the decision of the TSC and how that decision will be implemented (e.g., Implementation Note to be distributed on V2.6 CD ROM, announced via eNews, and posted to the web site for download.)
      1. Capture of date on which resolution was achieved
      2. Communication of resolution by TSC Steward to submitter.

Questions:

1. Would a priority field be useful?
2. Would a target date for discussion/resolution be helpful?