[admin] Agenda - DAP Distributed Meeting 17 March 2016
[admin] Agenda - DAP Distributed Meeting 3 March 2016
[admin] Reminder: no DAP call today
[ambient-light] Add bikeshed index file.
[battery] implementation testing report
[battery] Next steps to PR (was: implementation testing report)
[minutes] DAP Distributed Meeting 17 March 2016
[sensors] Add solution for cached value readings
[sensors] Add solution for one-shot readings
- Marcos Caceres via GitHub (Wednesday, 16 March)
- Tobie Langel via GitHub (Thursday, 10 March)
- Anne van Kesteren via GitHub (Thursday, 10 March)
- Tobie Langel via GitHub (Thursday, 10 March)
- Tobie Langel via GitHub (Thursday, 10 March)
- Tobie Langel via GitHub (Thursday, 10 March)
- Domenic Denicola via GitHub (Monday, 7 March)
- Anne van Kesteren via GitHub (Monday, 7 March)
- Robin Berjon via GitHub (Monday, 7 March)
- Tobie Langel via GitHub (Sunday, 6 March)
- Rick Waldron via GitHub (Sunday, 6 March)
- Tobie Langel via GitHub (Sunday, 6 March)
- Tobie Langel via GitHub (Sunday, 6 March)
- Robin Berjon via GitHub (Sunday, 6 March)
- Rick Waldron via GitHub (Sunday, 6 March)
- Tobie Langel via GitHub (Sunday, 6 March)
- Tobie Langel via GitHub (Sunday, 6 March)
- Tobie Langel via GitHub (Sunday, 6 March)
- Anssi Kostiainen via GitHub (Sunday, 6 March)
- Rick Waldron via GitHub (Sunday, 6 March)
- Tobie Langel via GitHub (Sunday, 6 March)
- Tobie Langel via GitHub (Sunday, 6 March)
- Tobie Langel via GitHub (Sunday, 6 March)
[sensors] Adding a sensor.activated attribute
[sensors] Allow for async permission request when first accessing sensor data
[sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors
[sensors] Clarify terminology
[sensors] Define behavior when multiple instances of a sensor set different settings
[sensors] Define behavior when visibilityState != "visible"
[sensors] Discreet sensors must fire an event with their current state on instantiation
[sensors] Discrete vs continuous reporting modes
[sensors] Handling fatal vs. transient errors
[sensors] Is there a need for a oncalibrationneeded event
[sensors] Prepare licensing change in spec
[sensors] Setup echidna for continuous deployment
[sensors] Should sensors be singleton?
[sensors] Spec should allow user agents to reduce or disable sensor read for power saving purposes
[sensors] start() to return a cancellable promise that resolves on first reading
[sensors] Typos.
[sensors] What if requested polling frequency is > time it takes to read data out of the sensor?
[wake-lock] Wake Lock API Security & Privacy Questionnaire self-review
[wake-lock] Wake Lock API status update
[wake-lock] Wide review of Wake Lock API
Battery API is a W3C Proposed Recommendation
Call for Consensus to transition Battery API to Proposed Recommendation (PR) completed successfully
CfC: Call for Consensus to transition Battery API to Proposed Recommendation (PR) : deadline 10 March
Closed: [sensors] Allow for async permission request when first accessing sensor data
Closed: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors
Closed: [sensors] Clarify terminology
Closed: [sensors] Define behavior when multiple instances of a sensor set different settings
Closed: [sensors] Define behavior when visibilityState != "visible"
Closed: [sensors] Discreet sensors must fire an event with their current state on instantiation
Closed: [sensors] Discrete vs continuous reporting modes
Closed: [sensors] Handling fatal vs. transient errors
Closed: [sensors] Should sensors be singleton?
Closed: [sensors] Spec should allow user agents to reduce or disable sensor read for power saving purposes
Closed: [sensors] What if requested polling frequency is > time it takes to read data out of the sensor?
DAP-ACTION-746: Update pr draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html
DAP-ACTION-747: Create pr publication draft, updating status section to note that there were no new issues since cr, that there were no features marked as at risk
DAP-ACTION-748: Put tentative date of 3 may 2016 in battery pr draft
DAP-ACTION-749: Send transition request
DAP-ACTION-750: Create draft security and privacy considerations section for vibration api
DAP-ACTION-751: Prepare new vibration editors draft including errata and security and privacy consideration material from lukasz and others
DAP-ACTION-752: to review wake lock with respect to privacy and security https://w3ctag.github.io/security-questionnaire/
DAP-ACTION-753: Update Web IDL Level 1 reference to reference new WebIDL CR publication in editors draft and PR draft
Draft minutes 3 March 2016 and Action summary
Exiting CR Re: [wake-lock] Wake Lock API status update
ISSUE-172: Anssik update pr draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html
ISSUE-173: Anssik to create pr publication draft, updating status section to note that there were no new issues since cr, that there were no features marked as at risk
ISSUE-174: Anssik to put tentative date of 3 may 2016 in battery pr draft
New charter approved; rejoin the group
New generic sensor API WD out
New WD of Ambient Light API
Privacy report on sensors, for generic sensors API.
Summer Time! (was: [admin] Agenda - DAP Distributed Meeting 17 March 2016)
Wake Lock API Security & Privacy Questionnaire self-review
Last message date: Thursday, 31 March 2016 10:59:33 UTC