See also: IRC log
<fjh> Approve minutes from 17 November 2016
<fjh> https://lists.w3.org/Archives/Public/public-device-apis/2016Nov/att-0019/minutes-2016-11-17.html
<fjh> proposed RESOLUTION: Minutes from 17 November 2016 are approved
RESOLUTION: Minutes from 17 November 2016 are approved https://lists.w3.org/Archives/Public/public-device-apis/2016Nov/att-0019/minutes-2016-11-17.html
<Andrey_Logvinov> https://github.com/w3c/wake-lock/issues/87
Andrey: I have outlined a sketch of the new version API based on the feedback received on the current version
... I'll turn that into an actual spec before the next meeting
Frederick: based on the thread with sensors, one of the messages about performance said that promises aren't going anywhere
Dom: probably an allusion to async/await, but that doesn't mean promises are going nowhere
Kenneth: agreed; there is a Promise.try proposal at early stage in ES which also indicates promises aren't going away
Frederick: thanks Andrey for your work on this, we'll look at the concrete proposal at the next call then
<fjh> Tests updated, Tobie reviewing, test results https://lists.w3.org/Archives/Public/public-device-apis/2016Nov/0020.html
Frederick: thanks Wanming for the good work you've been doing
... you need help with something from Dom?
Wanming: I've made PRs to align the tests with the latest spec; not sure if Tobie has any remaining comment
... generated test report, only 2 errors due to general WebIDL bug in Chrome
... I've started tests for the motion sensors which just landed in Chromium Canary
... I'll refactor some of it to put common sensor test code together
Frederick: so one of the issue has already been fixed; the other active/activated renaming - status?
Kenneth: that change has landed now
Frederick: the test results pull request needs to be merged by Dom?
Wanming: indeed
Dom: I'll take a look
<scribe> ACTION: Dom to review tets results pull request for ambient light https://github.com/w3c/test-results/pull/72 [recorded in http://www.w3.org/2016/12/01-dap-minutes.html#action01]
<trackbot> Created ACTION-778 - Review tets results pull request for ambient light https://github.com/w3c/test-results/pull/72 [on Dominique Hazaël-Massieux - due 2016-12-08].
Tobie: will focus back on sensors as of next week
... did a first pass review of the tests submitted in pull request
... one issue is that some of the tests need progress on the spec before approval
... once the spec is updated, I'll reflect that in the test review
... we could merge it right now, and have it updated later
Wanming: I'll make sure to update the tests when the spec changes
Tobie: so let's merge this
<fjh> Wanming will review update of Generic Sensor spec to see what additional test changes are needed, general agreement to merge PR now, Dom will take action
Frederick: several threads on motion sensors and fusion
... there is a discussion around having a global sensors object
Tobie: this is one of the issues that keeps coming up
... there is no WebIDL construct that enables namespaces
... no current plan to adding this due to possible conflicts with ES modules
... the module story operates on a much longer cycle than the sensors API
... this is also linked to the discovery API - knowing which sensors are on the device based on existence in a given namespace
... but supporting the gyroscope API doesn't imply the underlying device has a gyroscope
... for that, we need a discovery API which is a level 2 thing at the moment
Frederick: should we document that in our FAQ?
Tobie: yeah, maybe pointing to the issues that have been closed on this topic
... and maybe I should link from that from the spec as well
... on shared memory & garbage collection - I plan to look at this in more details next week
... it might have pretty serious design implications
... part of design was to fulfill use cases for reading both in events and on the sensor object - that design is what's causing the cost of garbage collection
... we may have to reconsider that approach as a result
... we could put all the property of the reading directly on the sensor object
... I'll write up something
... the idea is to avoid creating new objects and just update primitive values
... but we'll need an API for the snapshot value
Tobie: have you played with the project system of github?
... it allows to keep track of stuff across multiple repos
... we could use it e.g. for keeping track of x-repos issues in DAS
... In general, it's much easier for me to manage issues in github than actions in a different system
... The GH project management system allows to organize issues across multiple repos
<fjh> ACTION: tobie to propose changes to address garbage collection issues [recorded in http://www.w3.org/2016/12/01-dap-minutes.html#action02]
<trackbot> Created ACTION-779 - Propose changes to address garbage collection issues [on Tobie Langel - due 2016-12-08].
<fjh> ACTION: dom to accept pull request for ambient light [recorded in http://www.w3.org/2016/12/01-dap-minutes.html#action03]
<trackbot> Created ACTION-780 - Accept pull request for ambient light [on Dominique Hazaël-Massieux - due 2016-12-08].
<fjh> ACTION: wanming to track changes in Generic Sensor API and update ambient light tests accordingly [recorded in http://www.w3.org/2016/12/01-dap-minutes.html#action04]
<trackbot> Created ACTION-781 - Track changes in generic sensor api and update ambient light tests accordingly [on Wanming Lin - due 2016-12-08].
Frederick: next meeting on Dec 15, we'll look at Wake Lock and Generic Sensors updates
... we'll cancel the call on Dec 29
RESOLUTION: Call on Dec 29 is canceled
<fjh> dom: when adding new material like geolocation API or web bluetooth or web NFC would need to re-charter
<fjh> dom: current charter until end of 2017