- From: Harry Halpin <hhalpin@w3.org>
- Date: Thu, 13 Feb 2014 15:27:59 +0100
- To: GALINDO Virginie <Virginie.GALINDO@gemalto.com>, Web Cryptography Working Group <public-webcrypto@w3.org>
- CC: Bruno Oliveira <abstractj@redhat.com>
- Message-ID: <52FCD66F.1080508@w3.org>
On 02/13/2014 02:36 PM, GALINDO Virginie wrote: > > Hi all, > > As part of the 'for the future' ideas, I think that we should consider > the idea of moving to github. > > This is coming from request that Bruno from Redhat made some times ago > http://lists.w3.org/Archives/Public/public-webcrypto/2014Jan/0002.html > and reiterated recently on Twitter > https://twitter.com/abstractj/status/433630254062903297 > > It seems to be a general move in W3C to go github, and I'd like to get > the view of the WG participant on : could the WG manage its future > specifications on github ? (I am not talking about migrating the > existing specs as it could mean too much work, but rather preparing > the future). > Since Github does not provide indefinitely stable URIs, the Rec-track "snapshots" and the Rec itself will continue to be hosted on W3C itself. However, I'm fine with moving the editor's draft from dcvs.w3.org to Github if the editors agree. cheers, harry > Views are welcome... > > Virginie > > gemalto > > > ------------------------------------------------------------------------ > 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
Received on Thursday, 13 February 2014 14:28:10 UTC