[W3C Web Crypto] CfC to get back to conf call working method ? --> yes and next call on 15th of february

Dear all,

This is to announce that the Web Crypto WG will now operate on a bi-weekly call basis, which will happen every two  Mondays @ 20:00 UTC.
Our first call is scheduled on the 15th of February, open to WG members only.

The provisioned agenda will be :

-          Test suite status

-          State of browser implementations, gap with Web Crypto API

-          Possible timeline the group can reach on the rec track

-          Charter renewal / extension



Let me also welcome the new members of the WG, Tim from Mozilla and Rob and Jatinder from Microsoft. This call will also be the opportunity to reinforce our implementers community.



Best regards,

Virginie Galindo

Chair of the Web Crypto WG






From: GALINDO Virginie [mailto:Virginie.Galindo@gemalto.com]
Sent: mardi 26 janvier 2016 18:13
To: public-webcrypto@w3.org
Cc: Harry Halpin
Subject: [+SPAM+]: [W3C Web Crypto] CfC to get back to conf call working method ? (please answer before the 2nd of february)

Dear all,

It we have experienced several strong discussions which have affected the roadmap of our working group, Harry and I are proposing that we go back on a bi-weeks conference call. The proposal here is to start meeting every two weeks, starting on the 15th of February.
The rationale for coming into a more active mode is to share on tests suite development and implementers debug progress and align the specification around a real interoperable set of feature. We will keep our call time to Monday @ 20:00 UTC.

Thanks for confirming support or raising objection to that working mode prior to the 2nd of February.

Regards,
Virginie

// please ignore the following statement.
________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.