[jsdl-wg] Tracker status values proposal

[Donal K. Fellows]

Andreas Savva wrote:
> This is a procedural proposal about the specification tracker settings:
[...]
> The meaning of these values would be as follows:
> Pending: the issue has been accepted and is still pending
> 	resolution by the WG

Actually, this has a pre-defined meaning in the GridForge software. That
meaning is that "response from the artifact author is due" and IIRC,
this item automatically migrates to Closed if no response is received
within a certain amount of time.

Indeed, both Open and Closed also have pre-defined meanings. It seems to
me like you are trying to sub-class these states (which is not a bad
thing as such, but say what you mean.)

> Resolved: The WG has decided and accepted a resolution, but the
> 	actions are still pending
> 
> Fixed: The editor has completed the proposed actions, but the
> 	actions are awaiting verification.
> 
> Closed: The issue has been resolved and is reflected in the
> 	 work products of the WG. The completion of the changes
> 	must be reported by the primary editor and verified by
> 	the secondary editor (or other WG member).

It's not clear to me why you have these two with these meanings. It
seems that in practice, tracker items don't get fixed or closed for
ages, even when the issues themselves have been long resolved. :^)

> Deferred: The WG has decided that the issue has some merit
> 	but that it should not be addressed in the upcoming
> 	revision of the spec.

Could also do with "Rejected", with the meaning of "We are never going
to do this". An example might be a suggestion that JSDL specifies job
instance state, which I remember as being something that moved out of
scope very rapidly early in the group's lifetime. :^)

Donal.