W3C Web Crypto WG - classifying issues

FYI, I have been implemented the suggested changes.
Note that the WG and editors will decide if we close/postpone/close issues.
Regards,
Virginie

From: GALINDO Virginie
Sent: jeudi 7 février 2013 12:56
To: 'public-webcrypto@w3.org'
Subject: W3C Web Crypto WG - classifying issues

Dear all,

With respect to our discussions during our call this week, I would suggest the following categorization of ISSUES, taking into account the following tools :

-          Associate ISSUES with appropriate PRODUCT (and we have 4 products at the moment, the low level PI, the high level API, the use case, the Key Discovery)

-          Put some issues in the POSTPONED mode to highlight the fact that it seems to be important for the group, but there is no contribution at the moment.

ISSUE-40 : Move ISSUE to product Key Discovery.
ISSUE-34 : Remove product reference and Associate POSTPONE state.
ISSUE-30 : Associate with Key Discovery product
ISSUE-26 : No change, but expecting proposal and change state to POSTPONED, if no contribution in the coming 3 weeks.
ISSUE 25 : Associate with Key Discovery product
ISSUE 24 : Remove any product associated.
ISSUE-19 : No change, but expecting proposal and change state to POSTPONED, if no contribution in the coming 3 weeks.
ISSUE-15 : Remove product associated and mark as POSTPONED.

This mail does not address the discussion for closing or not issues, but rather classifying it correctly.
Discussion about closing issues is under the responsibility of the WG and editors of the product associated (if any).

Regards,
Virginie