See also: IRC log
<scribe> ScribeNick: fjh
fjh: Privacy call (PING) to discuss Vibration API, https://lists.w3.org/Archives/Public/public-privacy/2016JanMar/0026.html
<anssik> +1 to approve
Approve minutes from 4 Feb 2016, https://lists.w3.org/Archives/Public/public-device-apis/2016Feb/att-0035/minutes-2016-02-04.html
RESOLUTION: Minutes from 4 Feb 2016 are approved, https://lists.w3.org/Archives/Public/public-device-apis/2016Feb/att-0035/minutes-2016-02-04.html
fjh: Tobie not on call so not much to discuss
anssik: tobie will put out update
by this month, also ambient light
... also publish updated WD
... cannot automate it yet
fjh: WD update
... need prepared editors draft including status section
update, once we have that not too difficult or slow to publish
WD
... would like to send CfC
... good practice, not much delay with 1 week CfC, so lets do a
CfC
... tue and thur are publication date
... need draft to see before deciding on specifics
... also need to understand what open issues remain, however
that should not block publishing WD as we can publish early and
often not block WD
fjh: where are we
anssi: identified root cause for
test failures, fixed the test cases
... root cause was that test case should not be run too early,
ordering of test cases
... update sent yesterday
<anssik> https://lists.w3.org/Archives/Public/public-device-apis/2016Feb/0061.html
anssi: one test remaining,
Zhiqiang will work on this starting next week
... once that is done we can move to PR
fjh: how did you see the issue
anssik: Zhiqiang had tool to watch variables
fjh: is that tool available to others
anssik: Zhiqiang will include in test suite
fjh: so the timing should work with Dom being back
fjh: lots of privacy discussion,
see PING call for next week
... I have a conflict but if you can attend it might be
useful
<anssik> https://github.com/w3c/vibration/pull/1
fjh: expect we can go to REC again without too much trouble, since we are not changing normative requirements that impact implementations
anssik: page visibility does not
impact implementations or testing, better language
... note migrated from CVS to git , easier to review
... this is what to review: https://github.com/w3c/vibration/pull/1/files
fjh: I did not see the github discussion regarding privacy, wasn’t aware
anssik: request to mirror to list but approval is awaiting for Dom until he is back
fjh: thanks for this work
... will review, shall we send message to list asking for
review
... I’ll ask for review by the WG
... need to check what PING is looking at, should be this
one
<anssik> https://rawgit.com/anssiko/vibration/rec-errata/index.html
fjh: excellent, will make sure PING sees this as well as WG
<scribe> ACTION: fjh to request review of Anssi update of Vibration from WG and PING (pull request version) [recorded in http://www.w3.org/2016/02/18-dap-minutes.html#action01]
<trackbot> Created ACTION-745 - Request review of anssi update of vibration from wg and ping (pull request version) [on Frederick Hirsch - due 2016-02-25].
Remaining issues; https://lists.w3.org/Archives/Public/public-device-apis/2016Jan/0077.html
Andrey_Logvinov: remaining issues
are feature requests as opposed to issues
... desires for control of timeouts etc
<scribe> … ongoing discussion, no consensus on how to deal with them
fjh: we have fast WD publication for this one, so the question is when to go to CR
anssik: behind flag in chromium?
Andrey_Logvinov: yes
anssik: other implementations?
Andrey_Logvinov: not yet
anssik: can we go to CR
fjh: can, since call for
implementation, but better to have more implementation
experience first, or confidence
... what about Mozilla, Marcos is involved
Andrey_Logvinov: not sure what they are doing
anssik: key use case was Firefox
OS, but now be refocused, so no longer under development, so
could be lower priority
... use case is for mobile
fjh: need two implementations at least to progress
anssik: what about iOS,
apple
... mobile feature, so that leaves Android and iOS
... maybe Firefox for Android, another question for Marcos
Andrey_Logvinov: not just mobile, can be for any platform
anssik: high value is for mobile, delay differences
fjh: who to ask?
... people in second screen group?
anssik: probably not right people
fjh: who in apple would be right person to ask, having reason to be interested
anssik: they tend to follow, not
doing early implementations
... start with Marcos and Mozilla
<anssik> proposed charter in review: https://www.w3.org/2015/11/DeviceSensorsCharter.html
anssik: we’ve been extended to end of march
fjh: I think we will be ok, haven’t seen issue, can work with Dom when he is back
none
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/review/review by the WG/ Succeeded: s/yues/yes/ Succeeded: s/not a too slow to publish/once we have that not too difficult or slow to publish WD/ Succeeded: s/before deciding/before deciding on specifics/ Succeeded: s/remain - does/remain, however that should not block publishing WD as we can publish early and often/ Succeeded: s/see discussion/see the github discussion/ Succeeded: s/awaiting/approval is awaiting/ Found ScribeNick: fjh Inferring Scribes: fjh Present: Frederick_Hirsch Andrey_Logvinov Anssi_Kostiainen Regrets: Tobie_Langel Dominique_Hazael-Massieux Agenda: https://lists.w3.org/Archives/Public/public-device-apis/2016Feb/0057.html Found Date: 18 Feb 2016 Guessing minutes URL: http://www.w3.org/2016/02/18-dap-minutes.html People with action items: fjh WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]