v6ops Issue Tracker

10 November 2003

Why an Issue Tracker:

The idea is to change the v6ops wg draft processes to enable open, traceable, and more effective wg draft efforts. This will hopefully speed up, facilitate and make easier the work of the document editors, and make sure all comments are addressed in the wg. To achieve this we are introducing an Issue Tracker for all WG drafts. We are using the issue tracker from psg.com (http://rt.psg.com/).

There has been good experience with the initial trial of an Issue Tracker on the 3GPP analysis draft. The v6ops chairs hope this will revive and focus the discussion on other v6ops wg drafts as well.

Overview of how the Issue Tracker works:

The Issue Tracker is going to be used for all documents when they get to WG draft status. The comments on these documents are sent as issues and the issues are registered with the Issue Tracker. For submitting issues a simple template is used (see below). To make sure that every issue is registered, only the issues submitted using the template are registered. The template also has space for proposing text to solve the issue. It is encouraged to use this section when submitting an issue.

The issues are registered with the Issue Tracker for your convenience by one of the chairs. The editor of the document will be responsible to propose actions/solutions for the individual issues. The action is to accept, accept with modification, and reject. The submission of issues and the discussion about the issues is, of course, done on the v6ops mail list. So, the issue tracker is mostly a documentation tool for the discussion and facilitating the work of the editor.

Template:

The Issue Tracker is going to be used for all documents when they get to WG draft status. The comments on these documents are sent as issues and the issues are registered with the Issue Tracker. For submitting issues a simple template is used (see below). To make sure that every issue is registered, only the issues submitted using the template are registered. The template also has space for proposing text to solve the issue. It is encouraged to use this section when submitting an issue.

[Document]<Subject>
Submitter name: <Your_Name_Here>
Submitter email address: <Your_Email_Address_Here>
Date first submitted: <Insert_Date_Here>
Reference: <URL to e-mail describing problem, if available>
Comment type: ['T'echnical | 'E'ditorial]
Priority: ['MUST' Must fix | 'SHOULD' Should fix | 'MAY' Nice to have ]
Section: <Insert_Section_Number_Here>
Rationale/Explanation of issue:
<Detailed explanation of the issue>
 
Requested change:
<Proposal of text>

 

[Questions and comments] [6bone Home Page] [v6ops Home Page]