- From: Harry Halpin <hhalpin@w3.org>
- Date: Mon, 13 Aug 2012 20:17:45 +0200
- To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Everyone, Note that before we go to FPWD, it is the *duty* of every WG member to give the spec thorough review. The process goes like this: 1) The editor(s) send an email to the WG mailing list signalling they believe the spec is ready for consensus. Note that, again, it is OK and at this stage even encouraged to publish with to open issues. 2) In that case, each Working Group member should read the spec and respond with comments, if any. In the case of open issues, you are determining if you agree how they phrased the open issues, including any discussion of alternatives. Also, note you may comment on grammatical and minor formatting issues as well. You should clearly delineate changes to the spec that require substantive changes and those that do not. 3) The editor should respond to each of the changes, either committing them or explaining why not. 4) At the next WG member, the WG proposes to have formal consensus on the spec. 5) If formal consensus is gained, then W3C staff check the formatting of the spec and begin working with W3C Communications Team to publish the spec. Specs are generally published Tuesday and Thursday. The FPWD will get a new directory home separate from the Editors draft. thanks everyone, harry
Received on Monday, 13 August 2012 18:17:54 UTC