- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Mon, 15 Jun 2020 19:40:39 +0200
- To: public-webauthn-adoption@w3.org
Hi, My notes from our call today available below. Next call on June 29. Action items: * ACTION: Dom to figure out what kind of patent licensing are needed for the wireframe project (based on Tony's concerns) * ACTION: David to reserve webauthn.how for "practical webauthn" [DONE] * ACTION: Nick to work with Matt on a design document for managing backend hosting ACTION: Nick to bring up UX resources/guidance for Practical WebAuthn * ACTION: Dom to set up a slack channel for the CG ---- Present: Dom, Anthony_Nadalin, David_Turner, Luke_Walker, Matthew_Miller, Andrew_Shikiar, Nick_Stelle, Alex_Seigler, John_Fontana, Nick_Mooney, Bart_de_Water Nick: I've looked into webauthn.guide - doesn't look like we can transfer that one ... there are other TLDs available, .help or .how ... Luke, any news on .dev? Luke: same as for .guide at this point # Wireframe project Nick: Tony in the WebAuthn WG meeting mentioned discussions around licensing/IPR if this group is shared between FIDO/W3C Tony: want to make sure the contributions made to a Web site gets made under the W3C CG CLA ACTION: Dom to figure out what kind of patent licensing are needed for the wireframe project (understand Tony's concerns) Matthew: are we talking about making patent licensing for contributions to the wireframe repo? Dom: hope not, but need to clarify this Nick: hope we don't need that John: useful to double check Nick: any inspiration on the name for the project/org? Matthew: practical-webauthn Dom: I like it Nick: me too repo was created for the wireframe project Andrew: it's fine - sounds appropriate for developers Matthew: howto-dot-webauthn-dot-dev John: webauthn-dot-how sounds neat and tidy ACTION: David to reserve webauthn.how for "practical webauthn" Nick: was imagining starting with a set of static pages generated via hugo David: FIDO can host the web site Nick: hopefully this can be updated via GH pushes Matthew: you could use github actions for this what kind of site are we talking about? Nick: similar to todomvc landing page Matthew: there is hosting the landing page, but also hosting the backend of the wireframe projects - how are we planning to deal with this? Nick: not clear yet David: so this would be hosting the various backends of the wireframe projects? Nick: if we host attestations, we need something like this Luke: I agree this would needs to be end-to-end implementations (per Bart's description) could be a list of showcases there are various options we could go Matthew: maybe the backend side of things is not hosted, available for download for testing David: re hosting, we had not been thinking of hosting live services - we need to think some more about that aspect Matthew: I can imagine the security concerns - maybe let's instead figure out a sane way to get https for local development; e.g. I use a subdomain Nick: there are various ways; we could provide a docker/container with certbot Matthew: we could have a pre-defined DNS entry for localhost to help with that integrating the backend in the project is useful given what we want to demonstrate (e.g. on user management) ACTION: Nick to work with Matt on a design document for managing backend hosting Bart's notes https://lists.w3.org/Archives/Public/public-webauthn-adoption/2020Jun/0007.html Bart: someone mentioned having access to UX designers? Nick: I do - I'll schedule some time with them, and one of the UX designers from my team will be joining the CG Bart: that'd be useful to get started ACTION: Nick to bring up UX guidance for Practical WebAuthn # Community Matthew: do we want to set up any kind of community forum to chat real-time? ACTION: Dom to set up a slack channel for the CG
Received on Monday, 15 June 2020 17:40:44 UTC