00:22:27 <betehess> betehess has joined #wpwg
01:36:39 <Max> Max has joined #wpwg
01:41:51 <Max> Max has joined #wpwg
02:06:24 <betehess_> betehess_ has joined #wpwg
16:52:11 <RRSAgent> RRSAgent has joined #wpwg
16:52:11 <RRSAgent> logging to http://www.w3.org/2017/01/20-wpwg-irc
16:53:08 <Ian> Meeting: Merchant Adoption Strategy
16:53:25 <Ian> Agenda: https://github.com/w3c/webpayments/wiki/Adoption2017
16:53:35 <Ian> Chair: Ian
16:54:05 <Ian> rrsagent, pointer?
16:54:05 <RRSAgent> See http://www.w3.org/2017/01/20-wpwg-irc#T16-54-05
16:54:28 <koalie> koalie has joined #wpwg
16:59:39 <Ian> present+ Ian
16:59:52 <Ian> present+ Alan
17:00:02 <Ian> present+ AndrewPelehach
17:00:34 <adamR> present+
17:01:36 <Ian> present+ MaheshK
17:01:42 <kayakalan> kayakalan has joined #wpwg
17:02:14 <MaheshK> MaheshK has joined #wpwg
17:02:52 <zkoch> zkoch has joined #wpwg
17:02:59 <Ian> present+ Evgeny
17:03:07 <Ian> present+ zkoch
17:03:30 <Ian> present+ Javed
17:03:41 <Evgeny> Evgeny has joined #wpwg
17:03:43 <Ian> present+ KOalie
17:03:48 <koalie> present+ Coralie
17:03:54 <Ian> present- KOalie
17:04:00 <Evgeny> present +Evgeny
17:04:13 <Ian> https://github.com/w3c/webpayments/wiki/Adoption2017
17:04:33 <koalie> -> https://lists.w3.org/Archives/Public/public-payments-wg/2016Dec/0034.html Preparing for conversations about merchant adoption of Payment Request API
17:05:14 <Ian> present+ AndrewF
17:05:23 <mathp> mathp has joined #wpwg
17:05:44 <Ian> present+ Thao
17:05:56 <mathp> sorry having trouble with webex
17:06:06 <afitz> afitz has joined #wpwg
17:06:09 <koalie> koalie has changed the topic to: 20-Jan agenda https://github.com/w3c/webpayments/wiki/Adoption2017
17:06:45 <rouslan> rouslan has joined #wpwg
17:06:51 <rouslan> present+
17:07:38 <Ian> scribe: Koalie
17:07:39 <mathp> present+
17:07:42 <koalie> scribenick: koalie
17:07:49 <Ian> https://github.com/w3c/webpayments/wiki/Adoption2017
17:08:17 <koalie> Ian: My understanding from plementers is that there are a lot of conversations havening already about adoption for the API
17:08:25 <koalie> ... good to hear challenges to adoption
17:08:31 <koalie> ... getting starting in the ecosytem is one
17:08:51 <koalie> ... one is merchants want users, users want lots of merchants to accept this
17:09:06 <koalie> ... another is cross platform deployment
17:09:20 <koalie> ... the API supports transition; communicating that is a path forward
17:09:27 <koalie> ... communication strategy will be helpful
17:09:47 <koalie> ... work groups focus on gory details but not the shiny details that appeal to other audiences
17:10:01 <zkoch> q+
17:10:12 <koalie> Zach: I'd agree with those
17:10:16 <koalie> ... another one is
17:10:27 <koalie> ... API probably more effective at converting users
17:10:48 <Ian> zkoch: "newness of this approach"
17:10:55 <Ian> ...internally we've called it a branding problem
17:11:00 <Ian> ...the world right now is "pay with X"
17:11:08 <Ian> ...applepay, chase pay, etc.
17:11:16 <Ian> ...there is a user education problem for payment request API
17:11:25 <koalie> i|... internally|scribenick: Ian|
17:11:27 <thaotran> thaotran has joined #wpwg
17:11:35 <koalie> s/... internally/Zach: internally/
17:11:36 <koalie> scribenick: koalie
17:12:06 <zkoch> (sorry koalie, i speak too quickly!)
17:12:07 <koalie> Ian: Google spearheaded an HTML5 logo and we made an awareness campaign
17:12:16 <koalie> ... see outreach in the wiki
17:12:36 <koalie> ... Understanding all the implications when you click on the pay button is a deeper question
17:12:43 <koalie> ... Thanks for mentioning this explicitely
17:12:53 <koalie> ... Any other challenges, problems people want to raise?
17:13:11 <kayakalan> q+
17:13:15 <koalie> ... I'll update the wiki after the meeting
17:13:16 <zkoch> ack zkoch
17:13:40 <koalie> AndrewP: as an org, it's not our core focus to do market outreach
17:13:51 <koalie> ... any way we can structure that in a way
17:14:30 <Ian> MESSAGE: (1) technical simplicity (2) consistency
17:14:36 <koalie> ... technical simplicity offered to merchant; consistent acrosse browsers and payment types
17:14:44 <koalie> ... outreach on the marketing side collectively
17:15:07 <mathp> q+
17:15:10 <Ian> QUESTION: What merchants to target
17:15:32 <koalie> Ian: tectic question, but first an audience question
17:15:48 <koalie> ... I don't know that we have answers today but we need to identify those
17:15:58 <Ian> q?
17:16:02 <koalie> s/those/the people we want to reach/
17:16:12 <Ian> ack kay
17:16:17 <Ian> s/AndrewP/Javed
17:16:23 <Ian> ack mat
17:16:32 <koalie> Mathieu: I agree with Javed
17:16:44 <Ian> mathp: I think technical simplicity is covered by the API
17:16:44 <koalie> ... the API takes care about the simplicity aspect
17:16:54 <koalie> ... consistency on merchant side is something I'd like to see
17:17:00 <Ian> ...what I would like to see is on the merchant side...they can choose to brand this experience however they want "instant checkout" or "express checkout"
17:17:09 <Ian> ..there is no indication to the user that they are now using the API
17:17:17 <Ian> ....there is no education for the user...
17:17:25 <Ian> ...guidance here for merchants would be helpful
17:17:31 <Ian> ...I hesitate to call it branding
17:17:38 <Ian> ...suggested presentation of the buttons
17:17:38 <Ian> q?
17:17:40 <koalie> i|...what I|scribenick: Ian|
17:17:52 <koalie> s/...what/Mathp: What|
17:17:54 <koalie> scribenick: koalie
17:18:55 <koalie> Ian: Engaging users to payment apps isn't a priority topic but part of the value proposition of this ecocystem
17:18:59 <Ian> Goals
17:18:59 <Ian>     Raise awareness about Payment Request API and encourage merchant adoption.
17:18:59 <Ian>     Gauge interest in merchant payment apps
17:19:05 <koalie> s/ecoc/ecos/
17:19:14 <koalie> ... Any ideas on reaching merchants differently?
17:19:26 <koalie> Ian: As far as audience
17:19:28 <koalie> ... two questions
17:19:49 <koalie> ... are we really thinking about convincing the strategists, in companies, or the developers, or both
17:20:21 <Ian> IJ: Big or small merchants or all?
17:20:25 <koalie> ... has size of merchant informed your thoughts?
17:20:31 <zkoch> q+
17:20:40 <koalie> ... would it be more effective to do demos to developers?
17:20:46 <kayakalan> q+
17:20:47 <koalie> ... or show people shiny experience?
17:20:51 <Ian> ack zk
17:20:59 <koalie> ... given limited resources, I'd like to prioritise
17:21:35 <koalie> Zach: how can we go from talking to merchants to empower developers but also the BD inside companies
17:21:38 <Ian> zkoch: I view this as "what can the WG do to empower developers" but also the teams inside of companies so that collectively we provide tools to aid in those conversations
17:21:47 <koalie> ... second half of what you're proposing
17:21:56 <Ian> ...examples
17:21:58 <koalie> ... e.g. "how to deal with coupon codes?"
17:21:59 <Ian> ..common ux patterns
17:22:05 <Ian> ...we should put up tools
17:22:19 <Ian> ...advice on branding, ux flows
17:22:21 <koalie> ... advice on brandinc, on UX flows
17:22:28 <Ian> ...at google we have sample code and integration guide
17:22:40 <Ian> ..but it would be good to show a collaborative effort among vendors
17:22:55 <koalie> ... devs need example codes, but they aren't the one who need to be convinced.
17:22:56 <Ian> ...I think we don't as much need to convince devs, rather convince CMOs and product owners
17:23:04 <Ian> q?
17:23:08 <Ian> ack kay
17:23:19 <koalie> Alan: I'd agree with Zach
17:23:39 <koalie> ... perhaps we should think in terms of event
17:23:42 <koalie> ... or time-frame
17:23:51 <koalie> ... a goal we share: e.g. interop
17:24:17 <koalie> ... good milestone
17:24:23 <Ian> ...one time to raise awareness --- some interop among browsers and apps
17:24:27 <Ian> ..have a marketing event around that
17:24:28 <koalie> ... have a marketing event around that
17:24:36 <koalie> Andrew: I'm on the BD team
17:24:42 <koalie> ... a challenge we're facing
17:24:57 <Ian> [Another interesting topic: success metrics]
17:25:01 <koalie> ... larger education effort
17:25:01 <Ian> q+
17:25:14 <koalie> ... shop top, March 19, is a big event coming up
17:25:22 <koalie> ... to introduce what we're working on
17:25:28 <koalie> s/shop top/shop talk/
17:25:33 <koalie> ack ian
17:25:51 <koalie> Ian: When at Money 2020, I asked and heard it was too late already for Shop Talk
17:26:04 <koalie> ... maybe a collective effort might encourage us for a panel, for example
17:26:20 <koalie> ... Tuesday afternoon, chat with Andrew Moris, CCO about Money2020
17:26:30 <koalie> ... which might be an option for our collaborative effert
17:26:38 <koalie> ... I'll keep up these conversations
17:26:43 <Ian> ack me
17:26:44 <Ian> q?
17:26:55 <koalie> ... state of implementation and interop might determine which event is better.
17:27:01 <koalie> ====
17:27:19 <koalie> Ian: I'm hearing that product owners is the place we should prioritise
17:27:30 <koalie> ... it may involve materials for developers
17:27:34 <adamR> +1
17:27:35 <koalie> ... can people +1?
17:27:43 <MaheshK> +1
17:27:45 <kayakalan> +1
17:27:59 <koalie> Ian: What about merchant size?
17:28:15 <koalie> ... big small, any size?
17:28:26 <koalie> ... it's great that shopify is in the group
17:28:34 <koalie> ... could help us reach merchants quickly
17:28:44 <koalie> ... other names were suggested to me
17:28:53 <koalie> ... any others would help us achieve scale in this effrt?
17:28:56 <koalie> s/ffrt/ffort/
17:29:00 <koalie> RRSagent, make minutes
17:29:00 <RRSAgent> I have made the request to generate http://www.w3.org/2017/01/20-wpwg-minutes.html koalie
17:29:10 <koalie> Adam: We could grab someone like Amazon
17:29:16 <koalie> ... that would be a high profile
17:29:23 <koalie> ... we have reasonable contacts
17:30:07 <koalie> Ian: It would be great indeed. I'm in conversation with Best Buy
17:30:13 <koalie> ... also Walmart and Target are aware of the work
17:30:16 <koalie> ... closely following it
17:30:25 <koalie> ... I haven't had many detailed discussion about their adoption
17:30:37 <koalie> ... any help with messaging tooling would be very helpful.
17:30:44 <koalie> ======
17:30:53 <koalie> Ian: A big visible merchant would help.
17:31:06 <koalie> ... any other thoughts on what size merchant would be most amenable to this
17:31:19 <koalie> q?
17:31:39 <koalie> ... or what could we help you do that outreach?
17:31:47 <koalie> ... what could we produce?
17:31:54 <kayakalan> q+
17:32:01 <Ian> ack ka
17:32:15 <koalie> Javed: we can target tier one merchants
17:32:19 <koalie> ... that would get us to scale
17:32:28 <koalie> ... and bring attention to the broader industry
17:33:02 <koalie> ... we need to show that it's not individual but a bigger scale that merchant investment would benefit
17:33:08 <Ian> MESSAGE: Once you implement this  you can reuse across new payment methods
17:33:29 <koalie> ... challenge today is to sell how the implementation will outbrand
17:33:36 <Ian> ...marketing documentation should show brands of participants in the WG
17:33:38 <koalie> ... what the merchant support enables
17:33:43 <Ian> ...and that gives scale
17:34:08 <Ian> ...questions about (1) when supported (2) which devices and systems (3) which payment mehtods
17:34:13 <koalie> ... if we can collectively give a bigger message, beyond individual road-maps
17:34:19 <Ian> ...message that there's a commitment to future suport
17:34:52 <koalie> ... early day but different partners are actively driving the effort
17:34:52 <Ian> "industry effort, early days but already some things supported"
17:35:05 <koalie> ... "it's an investment"
17:35:11 <koalie> ... "will lead to success over time"
17:35:16 <koalie> Ian: great, thank you
17:35:16 <mathp> q+
17:35:21 <Ian> ack ma
17:35:27 <koalie> Mathieu: I agree completely
17:35:50 <koalie> ... as we write, it doesn't make sense for each of us to rewrite our own versions
17:35:55 <koalie> ... let's write it collectively
17:36:12 <koalie> ... "here's what supported now and what is coming"
17:36:25 <koalie> Ian: Thank you
17:36:34 <koalie> ... what do you label that sort of resource?
17:36:43 <koalie> Mathieu: maybe a website that is source don GH
17:36:50 <koalie> ... that people contribute to
17:36:51 <koalie> ... share code
17:37:12 <koalie> ... "such and such browsers added support for payment"
17:37:24 <koalie> Ian: code sample and business cases and implementations are helpful
17:39:46 <Ian> https://www.webplatform.org/
17:40:06 <betehess> betehess has joined #wpwg
17:40:58 <Ian> IJ: w3.org or some other domain?
17:41:12 <Ian> AdamR: I think the people who will work on this will be different and from that perspective does not need to be closely associated with the WG
17:41:29 <Ian> ...new domain may help
17:42:16 <koalie> Ian: not a big deal from an admin perspective, but the least maintenance the better
17:42:26 <koalie> ... trying to gauge what people think
17:42:42 <koalie> ... how serious marketing do we need
17:43:16 <koalie> Mathieu: +1 to GH
17:43:39 <koalie> ... I'm not an expert in marketing but custom domain is probably preferable than github.io
17:43:51 <koalie> ... in terms of collaboration, GH is great
17:45:07 <thaotran> q+
17:45:26 <mathp> adamR: Github pages doesn't support HTTPS certs for custom domains, but +1 to GH source control.
17:45:32 <koalie> Ian: if we acquire such a resource, we need to figure out a plan for it
17:45:51 <koalie> ... I'd turn to those present to find out about commitment levels
17:46:47 <koalie> ... Coralie Mercier, head of marcomm is on the call today
17:47:03 <koalie> ... we could start to build a plan and circulate it among the WG
17:47:15 <koalie> ... develop it in e-mail or on calls
17:47:28 <koalie> q+
17:47:36 <koalie> ack th
17:47:37 <Ian> ack thao
17:48:08 <koalie> Thao: given we are talking to early adopters at this point
17:48:29 <koalie> ... a single slide, just to give a sense of where that stands in the various browsers
17:48:32 <koalie> ... and links
17:48:59 <koalie> ... for now
17:49:08 <koalie> ... we may want to convert it to a website later
17:49:16 <koalie> ... all of use can use that slide with our respective logo
17:49:22 <koalie> q-
17:49:37 <Ian> https://github.com/w3c/webpayments/wiki#experimentation-and-implementation
17:49:40 <koalie> Ian: I had started to put together a public common space in wiki:
17:50:10 <koalie> ... a more structured approach could be more interested
17:50:17 <koalie> ... people would need to give us update
17:50:21 <koalie> ... lest it's outdated
17:50:25 <adamR> mathp: There’s a… partial solution. It’s not awesome, but still pretty good: https://konklone.com/post/github-pages-now-sorta-supports-https-so-use-it#using-a-custom-domain-with-cloudflare
17:50:27 <koalie> ... I agree it's useful
17:50:57 <Ian> koalie: I wanted to say that I'll be happy to include plans in the broader web payments communications plan and strategy
17:50:58 <adamR> mathp: (Requires attackers to effectively be in network core or on premise at cloudflare or github)
17:51:32 <Ian> adamR: (Side discussion on github-backed domains)
17:51:33 <koalie> Adam: there are ways to host domains on Github
17:51:42 <mathp> adamR: Thanks
17:51:55 <koalie> Ian: that would be one way to go
17:51:57 <koalie> q+
17:52:05 <Ian> ack koalie
17:52:24 <Ian> koalie: I would support an approach to using GitHub
17:52:32 <Ian> ...instead of a new domain name
17:52:47 <koalie> Ian: we could start simply
17:52:58 <koalie> ... and find we may want to package it differently
17:52:59 <koalie> +1
17:53:04 <koalie> [Coralie: +1]
17:53:22 <koalie> Ian: do people think a name would help to talk about it in a consistent way?
17:53:23 <rouslan> +1
17:53:28 <koalie> ... and how about a visual identity?
17:53:31 <koalie> q?
17:53:33 <kayakalan> q+
17:53:35 <MaheshK> +1
17:53:39 <Ian> ack kay
17:54:22 <koalie> Alan: Who woud be interested in an event or cross-interop demo?
17:54:29 <koalie> ... that's when critical mass will happen
17:54:33 <koalie> ... with this initiative
17:54:36 <koalie> ... re: name and logo
17:54:41 <koalie> ... name is first
17:54:52 <koalie> ... we call it W3C pay internally and to partners
17:54:58 <koalie> ... for lack of a better name
17:55:14 <koalie> s/is first/is first before visual identity/
17:55:18 <koalie> ... then get a logo if you can
17:55:20 <koalie> ... start slow
17:55:23 <koalie> Ian: "k
17:55:27 <koalie> s/"k/'k
17:55:34 <Ian> q?
17:55:37 <Ian> ===
17:55:46 <koalie> Alan: expectation for after end of Q2
17:55:47 <Ian> summarizing some shorter term tactics
17:55:55 <Ian> * Web site with useful resources
17:56:00 <Ian> * Name to call this thing
17:56:11 <Ian> * An event
17:56:16 <Ian> * Status information
17:56:50 <Ian> * Highly visible adoption
17:57:24 <Ian> (status = implementation + adoption)
17:57:30 <koalie> ======
17:57:38 <koalie> Ian: any other things people had in mind?
17:57:51 <koalie> Mathieu: great list
17:58:08 <Ian> https://github.com/w3c/webpayments/wiki/Adoption2017
17:58:27 <koalie> Mathieu: we need to be able to contribute now
18:00:02 <koalie> Ian: 'name to call this thing' isn't the domain name we may choose
18:00:14 <koalie> ... what do we call it from a marketing perspective
18:00:20 <koalie> ... then what do we do to support it
18:00:44 <mathp> mathp: will have to think about names! Good homework :)
18:00:46 <Ian> ======
18:01:05 <koalie> Topic: next call
18:01:12 <koalie> Ian: same time in two weeks?
18:01:37 <MaheshK> +1
18:01:48 <Ian> ACTION: Ian to set up a w3c mailing list for discussions about this topic
18:01:48 <trackbot> 'Ian' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., ijacobs, ijmad).
18:02:03 <Ian> ...and subscribe people on this call to that list
18:02:09 <Ian> ...and tell the WG about it
18:02:55 <koalie> Ian: shall we find a GH repo?
18:03:00 <koalie> ... or use the existing vision wiki
18:03:11 <mathp> Not familiar with existing repos...
18:03:14 <Ian> https://github.com/w3c/webpayments/wiki/Adoption2017
18:03:22 <koalie> ... or wiki on gh
18:03:23 <betehess> betehess has joined #wpwg
18:03:33 <koalie> ... where the WG people have write acces
18:03:38 <koalie> s/cces/ccess/
18:03:52 <koalie> ... people can start collaborating, including ideas for names
18:04:03 <Ian> Topic: Next meeting
18:04:14 <Ian> 3 Feb at noon ET for 1 hour
18:04:19 <Ian> ACTION: Ian to send around meeting logistics
18:04:19 <trackbot> 'Ian' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., ijacobs, ijmad).
18:04:29 <koalie> Ian: Thanks everybody
18:04:33 <koalie> ... it's been helpful
18:04:40 <RRSAgent> I have made the request to generate http://www.w3.org/2017/01/20-wpwg-minutes.html Ian
18:04:48 <Ian> rrsagent, set logs public
18:04:54 <koalie> RRSagent, make minutes
18:04:54 <RRSAgent> I have made the request to generate http://www.w3.org/2017/01/20-wpwg-minutes.html koalie
18:05:35 <Ian> rrsagent, set logs public
18:06:07 <koalie> s/<koalie> ->/<koaliie> ->/G
18:06:08 <koalie> RRSagent, make minutes
18:06:08 <RRSAgent> I have made the request to generate http://www.w3.org/2017/01/20-wpwg-minutes.html koalie
18:06:37 <koalie> koalie has left #wpwg
18:36:13 <betehess> betehess has joined #wpwg
20:49:02 <betehess> betehess has joined #wpwg
22:02:18 <betehess> betehess has joined #wpwg
22:48:45 <betehess> betehess has joined #wpwg
23:03:00 <betehess> betehess has joined #wpwg
23:47:52 <betehess> betehess has joined #wpwg