Meeting minutes
<matthewmiller> https://
agl: sounds good to me
… I'll make that change
<matthewmiller> https://
agl: got an update from Mozilla
… saying they're unlikely to formally object
dveditz: we're working actively on it
… we still think it's lower-level than webauthn should be
… but might as well go with what people are working on
agl: I'd prefer to have more than grudging acceptance
dveditz: thanks, we'd probably implement, not a current priority
jfontana: 4 reviewers have signed off. ok to merge
matthewmiller: Tim has done some work with issue templates to help people direct their issues to the right audience
… including suggestions to use other forums, e.g. the fido-dev mailing list
https://
https://
timcappalli: are those the right categories?
… if you think there should be more scripted prompts, categories, please suggest
https://
elundberg: sounds good.
… is there a big difference between technical change/new use case or feature?
nsteele: I think it's different in level of detail
… flesh out abstract ideas in the issue before getting to technical proposal
… helps in routing people with implementation-specific questions to the right place too
timcappalli: is it OK to add links to implementations' bug trackers?
wseltzer: that's fine, add any that are relevant
https://
jfontana: ok to merge?
… please do
https://
elundberg: draft for discussion
… I don't expect it to be merged, just to prompt discussion
… if no discussion, ok to close
https://
agl: 1462 can be closed
<matthewmiller> https://
<kaiju> nsteele: 1633 closed out
<matthewmiller> https://
<kaiju> nsteele: 1633 closed reopened
https://
timcappalli: I opened an issue in the Web Extensions repo
… I don't think there's anything to do in WebAuthn
https://
<matthewmiller> An easy one to merge: https://
matthewmiller: can we close out 1770?
elundberg: should merge
agl: want people to look at the DPK PR
… it's complicated, because logic is throughout the spec
https://
[adjourned]