Issue management

Status

This is work in progress. We are not looking to take additional requirements into account. When the system will be ready and tested, we'll invite additional users and requirements.

Background:

1. UA Guidelines issues list
2. TAG issues list
3. DOM issues list

The package would include: Schema, Transforms and style sheets, Template, Rationale

Demo

Issue list document structure

See XMLSpec DTD (header element)

Date format is defined in XML Schema datatypes, section 3.2.9.

Desired views of the data

We are interested in three summary views in particular:

1. Full view
   1. Issue id and title
   2. WG view: open or closed
2. WG agenda building view
   1. Issue id and title
   2. Show issues in states raised, accepted
   3. Actions view:
      1. Highlight if no associated actions, or if issue transition == raised | accepted and all action transitions == decided (since this means nobody is doing anything on this issue).
      2. For each action not in the decided state:
         • If accepted, then highlight.
         • If dependent, then muted but present.
   4. Decision ack cycle view (assumes transition == decided)
      1. No decision acknowledgment cycle started.
      2. Show announced (i.e., awaiting reply)
      3. Show ack'd with disposition == proposal (i.e., we need to review it).
      4. Show ack'd with disposition == objection
      5. Disposition == accepted [Illegal state]
3. Director view
   1. Issue id and title
   2. Issues raised, accepted, deferred. Highlight these in red since this means you shouldn't be talking to the Director.
   3. Actions accepted or dependent. Highlight these in red since this means you shouldn't be talking to the Director.
   4. For transition == decided, look at acknowledgment cycles:
      1. None started. Highlight these in red since this means you shouldn't be talking to the Director.
      2. Announced. Warning; show efforts to obtain ack from reviewer.
      3. Acknowledged.
         1. Disposition == proposed or objection. Highlight these in red since this means you shouldn't be talking to the Director.
      4. Decided:
         1. Disposition == maintained. Highlight objection.

Issues list

List of:

1. Issue title, unique id
2. Optional: Categories (container; up to WG to decide how they want to futher categorize their issues)
3. Optional: Context (list of resources such as important emails)
4. Optional: References (list of documents this issue concerns)
5. Type:
   1. Editorial
   2. Clarification
   3. Error
   4. Proposal (something not in specification)
   5. Request (of the group, not necessarily related to a spec)
6. Optional: Deadline
7. Transition history
8. Optional:History of meetings where discussed
9. Optional: Action history

1. Transition history

List of transitions:

• Common to all transitions:
  1. Type: raised | accepted | deferred | decided
  2. Optional context (list of resources)
  3. Date of the transition
• transition == raised:
  1. Description
  2. List of:
     1. Raised by (Name)
     2. URI of message from entity raising issue.
     3. Optional: URI identifying raiser
     4. On behalf of (Name)
     5. Optional: URI identifying group/individual
• transition == accepted | defer
  1. Optional: URI to message ack'ing transition.
  2. Optional description.
• transition == accepted
  1. Optional URI to group decision regarding transition type.

     [The TAG makes a decision to accept an issue; WGs have no choice.]

• transition == deferred | decided
  1. URI to group decision regarding transition type.
• transition == decided
  1. Boolean: substantial
  2. Disposition: declined | subsumed | moved | agreed
  3. Description (of decision)
  4. When disposition == subsumed
     1. URIs of destination issue(s).
  5. When disposition <> subsumed
     1. Decision acknowledgment cycle

1.1 Constraints

1. Two possible first states: raised (in which case next state must be either accepted), or accepted.
2. For substantial modifications to an issue, create a new one. The 'subsumed' disposition covers both:
   1. One issue that splits into several.
   2. One issue that is subsumed by another.
3. Issue is considered "closed" when:
   1. Latest issue transition is 'decided'
   2. For each decision ack cycle, last transition is 'decided'
   3. For each action, last transition is either "acknowledged/agreement" or "followup"
4. Since there may be several decisions as part of the life of an issue, it is useful to indicate in the context part of a decision transition whether the new decision is the result of a previous objection, of a suggestion from a reviewer or from within the WG, etc.

2. Decision acknowledgment cycle (transition == decided)

List of ack transitions:

• Description
• URI to transition message
• Status: announced | acknowledged | followup
• transition == acknowledged
  1. Disposition: agreement | proposal | objection

     Agreement may vary from "I love this" to "I hate this but do not object." The reviewer may propose a change that would make the reviewer happy (but stilll not object).

     1. disposition == objection
        1. objector name, optional URI (to identify objector)
        2. on behalf of, optional URI (to identify objector)
• transition == followup
  1. Disposition: declined | incorporated | maintained | accepted

2.1 Constraints

1. There must be one announced transition.
2. There may be N ack transitions, some in response to the announcement, others not.
3. There must be N followup transitions, one for each ack
4. Acknowledged with disposition = agreement is a final state.
5. After transition == ack'd AND disposition == proposal, two dispositions possible when transition == decided: declined, incorporated. These are both final states.
6. After transition == ack'd AND disposition == objection, two dispositions possible when transition == followup: maintained (the WG maintains its original decision), or accepted (the reviewer's objection).
7. Transition == followup AND disposition == accepted implies a new issue transition. (Accepted | Decided)

3. History of meetings where discussed

List of:

1. link title (optional; if absent, use date string)
2. URI: link to the meeting/teleconference minutes
3. date

4. Action history

List of:

1. Owner
2. Description (includes part of issue that addresses).
3. Optional: Deadline
4. Action transitions:
   1. status: accepted | dependent | decided

      Dependent means you have done your part, are awaiting action from another entity.

      This is different from "I'm still working on it" which we do not represent in this transition scheme.

   2. Date
   3. URI of transition message
5. status == decided:
   1. Disposition: dropped | subsumed | completed

Last modified: $Date: 2003/04/18 19:43:28 $ by $Author: ijacobs $