14:01:11 RRSAgent has joined #wpwg 14:01:11 logging to http://www.w3.org/2017/06/22-wpwg-irc 14:01:11 AdrianHB has joined #wpwg 14:01:13 RRSAgent, make logs public 14:01:13 Zakim has joined #wpwg 14:01:15 Zakim, this will be 14:01:15 I don't understand 'this will be', trackbot 14:01:16 Meeting: Web Payments Working Group Teleconference 14:01:16 Date: 22 June 2017 14:01:22 Chair: AdrianHB 14:01:26 Agenda: https://github.com/w3c/webpayments/wiki/Agenda-20170622 14:01:28 Scribe: Ian 14:01:34 rouslan has joined #wpwg 14:01:40 present+ 14:01:46 present+ 14:02:30 present+ 14:02:40 present+ 14:03:56 present+ 14:04:08 zakim, who's here? 14:04:08 Present: rouslan, dezell, michel_cc, oyiptong, Ian 14:04:10 On IRC I see rouslan, Zakim, AdrianHB, RRSAgent, dezell, alyver, michel_cc, MikeSmith, natasha, adamR, dlehn, dlongley, manu, hober, nicktr, oyiptong, Dongwoo, ShaneM, mkwst, 14:04:10 ... slightlyoff, JakeA, emschwartz, adrianba, trackbot, Ian 14:04:14 present+ AdrianHB 14:04:19 present+ Mike5 14:04:29 present+ alyver 14:04:34 topic: Testing 14:05:01 mike5: Marcos sent an email the other say summarizing some progress on testing 14:05:11 https://lists.w3.org/Archives/Public/public-payments-wg/2017Jun/0023.html 14:05:24 ...he estimated we are at about 20% complete as far as the number of tests we have in the test suite and the coverage 14:05:32 ...I agree with the assessment 14:05:41 Ken has joined #wpwg 14:05:47 present+ michel_foucault 14:05:58 Mike: We need to get to 100% to get out of CR 14:06:10 -> http://web-platform-tests.org/ Start here for test suite info 14:06:37 present+ Roy 14:06:52 Mike5: Our focus is payment request API at this time 14:07:28 ..I also want to mention that while the test suite is useful for W3C's process requirements, its primary benefits are improving implementations and the spec 14:07:44 regrets+ NickTR 14:07:58 ...Marcos pointed out that some of the tests caused browser crashes in multiple browser. 14:08:12 ...that's good! 14:10:00 ...we want to keep doing this. 14:10:16 ....so far the effort has been modest (only a small number of people) the benefits have been important 14:10:27 ...we need people to write tests and people to review those tests 14:11:59 ....if you would like to author tests: 14:12:03 #testing on irc.w3.org 14:12:05 ...we have a test channel on IRC 14:12:14 ...and please coordinate work so we don't overlap in effort 14:13:07 ...it takes (IMO) as much time to review tests as to write them 14:14:10 q? 14:14:23 ...would like to get a pool of reviewers 14:14:34 ...and when tests come in, we get people from the pool to review the tests. 14:14:41 ...and this is done on github 14:15:27 present+ Max 14:15:34 +Q 14:15:39 ack Ken 14:15:48 present+ Ken 14:16:53 Ken: Would it be helpful for me to reach out to testing people in orgs we work with in financial services industry? 14:17:46 q+ to comment 14:17:57 ack Mik 14:17:57 MikeSmith, you wanted to comment 14:18:07 IJ: Thank you for the offer, Ken. 14:18:23 Mike5: As far as getting people in as IEs for testing, that's do-able and I would support that. 14:18:33 ...we'd need to discussing within the staff but I support the idea. 14:19:00 ...we have had some very successful experiences with hiring external resources to work on testing 14:19:12 ...e.g., on Javascript 14:19:51 ...we've had other experiences with mixed results. 14:20:11 ...one indicator I think of future success is how familiar testers are with JavaScript. 14:20:17 ...our test harness is in JavaScript 14:20:35 q+ 14:20:48 ...best would be to align with orgs that have experience with testing 14:21:11 Perfect. 14:21:27 Concur 14:21:39 IJ: Let's write down requirements, let Ken use them to do outreach, and see who is interested 14:21:41 Ken: +1 14:22:15 ACTION: Mike5 to write down requirements /skills for potential testers that would help ensure success and share with the WG 14:22:16 Created ACTION-62 - Write down requirements /skills for potential testers that would help ensure success and share with the wg [on Michael[tm] Smith - due 2017-06-29]. 14:22:19 Max has joined #WPWG 14:22:26 AdrianHB: What takeaways for people on the call? 14:22:31 Mike5: Please volunteer to review. 14:22:45 (Ian volunteers; have not done this before but am interested in getting that level of experience) 14:23:20 Mike5: The second takeaway is - if you have testing experience and you have some skill in JavaScript, we can make it easy for you to write tests and get them submitted 14:24:13 ...remember the goal is to enable you to build on solid foundations for your users 14:25:12 AdrianHB: I also want to say that we should do this so that we don't get to the end of the process and are unable to proceed to REC 14:25:33 (IJ asks any other volunteers to say "I volunteer" on IRC) 14:25:57 adrianhb: It's often easier to review a spec if you have a goal. One goal could be to review the spec with a specific test in mind. 14:26:37 I have made the request to generate http://www.w3.org/2017/06/22-wpwg-minutes.html Ian 14:26:38 Topic: PR API 14:26:49 Status of pull request 536 14:26:54 https://github.com/w3c/browser-payment-api/pull/536 14:28:02 AdrianHB: Progress. My concern right now is that if the data is invalid, the entire payment request is rejected rather than the specific data 14:28:07 q+ to comment 14:28:10 ack Mike 14:28:10 MikeSmith, you wanted to comment 14:28:13 q- 14:28:25 MikeSmith: The comment from Domenic (https://github.com/w3c/browser-payment-api/pull/536#discussion_r123521267) 14:28:31 ...is that he doesn't understand what "discard" means 14:29:23 AdrianHB: Marcos' text says, as you go through the loop, if data is invalid, you abandon the whole algorithm. 14:29:30 ...my suggestion is you reject that particular identifier. 14:29:32 Ian: +1 14:31:15 AdrianHB: Let's take to GitHub 14:31:30 IJ: What is the updated timetable for getting to CR? 14:31:35 ian: What is the updated estimate on going to CR from editors? 14:31:35 Roy: Don't have that information. 14:31:58 [No other editors on the call] 14:32:02 IJ: Please ask Editors for an estimated revised timeline 14:32:04 Roy: Will do 14:32:12 ACTION: Roy to check with PR API editors to get a revised timeline to CR 14:32:13 Created ACTION-63 - Check with pr api editors to get a revised timeline to cr [on Roy McElmurry - due 2017-06-29]. 14:32:41 Topic: TPAC 14:32:44 Ian: Please register 14:32:54 Topic: Payment Handler API 14:32:59 IJ: We are moving to auto-publication 14:33:19 https://www.w3.org/TR/payment-handler/ 14:33:45 https://github.com/w3c/payment-handler/issues 14:33:56 ian: good implementation experience coming in from Samsung and Google 14:33:59 https://github.com/w3c/payment-handler/pull/170 14:34:05 ... lots of activity on the TF 14:34:23 ... want to darw particular attention to this proposal from rouslan 14:34:59 ... revisiting idea of a canMakePayment event and still address privacy concerns 14:35:27 ... also added abort event to notify app if browser has requested abort (possibly on behalf of website) 14:35:46 ... won't be merged into spec until some impl experience has been gathered 14:36:06 ... good progress also on window opening and discussion around default payment instrument 14:36:27 ... possibly bring payment handler discussion into main meeting soon (as implementations roll out) 14:36:32 Topic: Tokenization 14:36:34 https://github.com/w3c/webpayments-methods-tokenization/wiki/gateway_params 14:36:45 ian: great conversations in tokenization TF too 14:36:59 ... updated gateway token spec (looking like payment method spec) 14:37:28 ... waiting on some feedback from Amex on network tokenization and whether both can be handled in a single payment method 14:37:37 ... will bring back to group after 14:37:46 Topic: Credit Transfer 14:37:49 See also => http://w3c.github.io/webpayments-methods-credit-transfer-direct-debit/ 14:37:49 :) 14:38:17 ian: also progressing well... 14:38:40 Topic: Next meeting 14:39:00 alyver has left #wpwg 14:39:28 6 July 14:39:36 (No objections) 14:39:39 RRSAGENT, make minutes 14:39:39 I have made the request to generate http://www.w3.org/2017/06/22-wpwg-minutes.html Ian 14:39:42 RRSAGENT, set logs public 16:53:02 Zakim has left #wpwg