RE: lock the webauthn repo?

Locking the repository seems to be problematic as we did that last time, I suggest that we only lock it for non-editors and go from there

-----Original Message-----
From: Giridhar Mandyam <mandyam@qti.qualcomm.com> 
Sent: Thursday, July 26, 2018 3:07 PM
To: W3C Web Authn WG <public-webauthn@w3.org>
Subject: RE: lock the webauthn repo?

Obviously W3C staff should give their opinions.  

My view:  I would recommend avoiding any technical changes to the document during the new review period.  Editorial changes that will not affect declarations (e.g. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwebauthn%2Fissues%2F1015&amp;data=02%7C01%7Ctonynad%40microsoft.com%7C059bda987e3340f42d1b08d5f3443a10%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636682396710582281&amp;sdata=MaygUw1qfsOQS1z%2FnpWe9uQX%2Bsn61TDR4nwEWc87MKI%3D&amp;reserved=0) can be addressed.  Yes, the diffs will change.  But I think improving the readability of the spec is worth it.

-Giri Mandyam

-----Original Message-----
From: =JeffH <Jeff.Hodges@KingsMountain.com> 
Sent: Thursday, July 26, 2018 2:06 PM
To: W3C Web Authn WG <public-webauthn@w3.org>
Subject: lock the webauthn repo?

Given that any further merges-to-master will alter any diff rendered by the diff links sent out in the request to update CR messages -- <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-webauthn%2F2018Jul%2F0558.html&amp;data=02%7C01%7Ctonynad%40microsoft.com%7C059bda987e3340f42d1b08d5f3443a10%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636682396710582281&amp;sdata=MqL5JISLQAfh9zL%2BU3Lxz%2BaV%2F19Hy%2F%2BjfIwHeTnnDmg%3D&amp;reserved=0>
and
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-webauthn%2F2018Jul%2F0559.html&amp;data=02%7C01%7Ctonynad%40microsoft.com%7C059bda987e3340f42d1b08d5f3443a10%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636682396710582281&amp;sdata=Y9FGss%2FWM5Skjx0a8ebapLIoIC2HVO2CjKmXB90HQFM%3D&amp;reserved=0>
-- should we lock the repo during the review period?

though it appears the review lasts until 2018 08 30, so that's kinda a long time.

=JeffH

Received on Thursday, 26 July 2018 22:18:06 UTC